Toggle sidebar Toggle sidebar

Solved Upgrading Snom D315

Status
Not open for further replies.

kaeslin

Forum User
Advanced Certified
Joined
Aug 13, 2020
Messages
14
Reaction score
2
Hi,
I'm struggling while updating a snomD315 from version 10.1.46.16 to the current version 10.1.54.16.
Updating with 3CX management console doesn't work.
I know that it could be problematic if you miss a firmware, but I can't find older firmware updates for snomD315 for 3CX. (Only the onces from https://service.snom.com/display/wiki/Firmware+Update+Center - there i can find versions like:
- 10.1.46.16,
- 10.1.46.19,
- 10.1.51.12 and
- 10.1.54.13
but no 10.1.54.16 or something in between.)
Am I missing all this listed firmwares??? Do I have to update them manually through the webinterface of each phone?
 
try to push manually the previous 10.1.54.13 from snom site and then try to update from 3CX console for the latest
 
  • Like
Reactions: kaeslin
Hi aws2p,
I'm currently doing it on my phone.
- Factory reset.
- Update manually through the web interface. (3 times, 1.10.46.19 is not for D315)
- Update through management console
Will let you know whether it works.
 
Phone: snomD315, managed to get on firmware version 10.1.54.13
Version 16.0.5.611 Professional Annual
Server OS: Debian 9
Hosted in house
Firewall Checker passed
Own template: no.

Error message on reboot:
"Software Update
Downloading Firmware
Could not resolve host
Error: 6"
-> Reboot

Error code decrypted by snom
 
Ok if your phone could not resolve the host then you have an issue either with DNS or provisioning.

Please check the extension's Provisioning tab and tell us the below too

Provisioning Method: Local / VPN / STUN / SBC
 
Provisioning Method: Local LAN
Select Interface: FQDN
 
Are you using a local FQDN (ie mynetwork.local) or your public FQDN (ie. something.3cx.com) ?

If using the 2nd, then your phone probably cannot reach the public FQDN from inside the network, and you would need a split DNS entry in your local DNS server.

Otherwise, simply change the interface and pick the PBX LAN IP and then reprovision your phone. After this, the firmware upgrade should succeed.
 
  • Like
Reactions: kaeslin
I changed to the local IP.
I get the same error.
When I log into the phones gui I see in the software update tab, that there is a wrong path in it for firmware updates. I try to change it, but no success so far.
 
Ok now that you have changed the Interface to the LAN ip of the PBX on your provisioning settings, please go ahead and reset the phone to factory settings.

Once it goes back to factory, look for it in your Phones tab, select it and press "Assign Ext" , select the correct extension then OK. Then Press OK again when you are taken to the extension provisioning page.

The phone should now provision, and all the necessary parameters will be correctly set. You may now send the update via the management console, and let us know how it goes (or if it fails, what error you see)
 
It works as discribed up to "assign ext" and ok. Then it tells me that a restart is required.
After the reboot it tries to update the firmware which fails with the same message.
I press "x" so that the message disapears and the phone reboots.
I still have the wrong url in the phones gui in the software update tab.
 
What URL do you see, and if you use that URL in your web browser, will the file download?
 
When I log in quickly after the reset from "error 6: couldn not resolve host" I can see in the system informations that the url links to the previously phone system (no more in use). This url is similar to the old interface/fqdn. In the 3cx/phones/provisioning tab it could be selected as interface but is not chosen! Also the provisioning link given just above is with my local PBX-IP.

So when I insert in the snom web gui in software-update/firmware last firmware from https://www.3cx.com/support/phone-firmwares/ which goes to https://downloads.3cx.com/downloads...areupdates/snom/snomD315-10.1.54.16-SIP-r.bin I will have after the failure and after the reboot in the phone web gui/system info: http://[old-fqdn]:5000/provisioning/mrfy4lzeq0megd/firmware/snom/snomD315-10.1.54.16-SIP-r.bin
(old-fqdn is also in local DNS)


After some seconds (definitely less than 2min), the system info tab updates (maybe through some provisioning?) to "firmware url: " its empty/null! I expecte to be my 3cx server or the url from downloads.3cx.com/downloads...
 
Are you using some other method of provisioning like SRAPS or DHCP Option 66?

You should not be receiving the link of an old system if that system no longer exists, so if the phone is finding it from somewhere then you have too look and find where it is getting in from.

Of course, it could also be your web browser auto-completing the empty URL box and tricking you into thinking that there was something written there (although usually the box would be highlighted to indicate this).
 
We use DHCP Option 66.

I mean that in the phone web gui there is a tab system information which gives me text (like labels, i can't change the text there). After about 30-50 seconds after booting this firmware-url disapears.
 
If you use option 66 then you may have to disable it and try again.

I'm not 100% sure what happens in your case, but if the option 66 gives the phone a different URL it might cause a problem. Note that option 66 is not just for provisioning, it also works for firmware deployment. You may have to adjust it or disable before you can succeed in your goal.
 
Is there another firmware version between 10.1.54.13 and 10.1.54.16 ?
 
I followed the hint where the old fqdn comes from. I was looking in the 3cx management console under settings/parameters and entered the old fqdn als search string. I found several entries e.g. SIPDOMAIN2, WEB_ROOT_LOCAL, MY_PHONE_LINK_LOCAL, PROVISIONING_LINK_LOCAL, ...

Anyway, the following did the trick:
- Add a DNS entry so that the old fqdn point to the IP of the 3cx pbx.
- There was a misconfigured nameserver entry on my debian (host os of 3cx). Only one of two entries were correct.
After these corrections I could update to the current version ;-)
 
  • Like
Reactions: AWS2P
Good Morning,

During the night some phones have upgraded to the correct firmware version. I expect that a forgotten and totally outdated phone has interrupted the rollout (according to the event log it was the last unregistered phone which reregistered after about 5min).

In an other thread (https://www.3cx.de/forum/threads/firmware-upgrade-snom-über-konsole-fehler.57840/#post-241723) I found the hint, that network troubles could be linked to the xml stored in
/var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioning/mrfy4lzeq0megd/firmware/snom/snomD315.xml
In my case, I can find there the link which looks like oldfqdn:5000/path/to/snomD315v10.1.54.16.bin.

@JohnS_3CX:
Could these be the source of the wrong propagated firmware-url?
Should I substitue the oldfqdn with the new fqdn or with the local IP? Or comes this information from the DNS and will be updated if DNS entries change?
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,956
Messages
589,928
Members
164,860
Latest member
maxpcc
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom