upgrade snom d15

[Kellermeister]

I have upgraded to V20 and have a couple of snom D315 which are working fine, they are showing a need to upgrade the firmware.
in v18 you cliecked on "upgrade fimrware" and this worked. In V20 nothing happenes. I get a warning that the phone might be unavailable for a couple of minutes, but it actually is not getting a firmware upgarde.

how to trigger the firmware upgrade?

 

[Kellermeister]

The issue is with an incomplete provisioning. I checked the firmware-path in the webconsole of the phone, this is normally provisioned by the 3cx. here the entry of the old V18 installation is still visible, but it is not updated to reflect the v20.

I manually copied the string from the snom homepage: https://downloads.snom.com/fw/10.1.169.13/bin/snomD315-10.1.169.13-SIP-r.bin and triggered the updated manually, this worked of course.

automatic provisioning was wokring, but not fpr the firmware: I rebooted the phones and deleted them and reassigned them. nothing. the only thing i didnt test is a complete reset of the phone.

 

[JohnS_3CX]

If the PBX was local you will need to have split DNS.

 

[Kellermeister]

If the PBX was local you will need to have split DNS.

It is on premise. I have split DNS. name resolution is working fine, the correct internal ip is delivered. The V18 installation used port 5001 the v20 installation uses 443 so itsa easy to see the the path was not updated in the hardphone. Resetting the hardphone cleans this entry and afterwards its properly populated -> QED splitdns is working. For a large installation this will be very unfortunate to have to reset all hardphones. Might be good to investigate.

 

[JohnS_3CX]

Note that if the PBX IP and SIP port remained the same, the phone will still be able to register and make calls. But provisioning will be broken. If you change the PBX provisioning ports then this was expected, I'm not sure it can be avoided.

The phone has no method of learning the new URL (it is a new URL due to the port change). Reprovisioning from 3CX will not fix that because the reprovision command relies on the fact that the phone is provisioned correctly to begin with (which it isnt as of changing the ports).

In this case I don't think any investigation is needed. All phones will need to be factory reset and reprovisioned so they can learn the new URL.

 

[Kellermeister]

I understand why this happens, I havent monitored the Migration process as closely, but to my mind the port-migration was unannounced. 5001 was the deafult for v18 and 443 seems to be the default for v20. Obviously the port-setting is not in the export package (everything else was) so it would be good to give at least a warning that the port-migration will break your installation....just my 5 cents....

 

[JohnS_3CX]

Hmm how did you upgrade exactly?

1. Upgrade in place via V18 management console on Debian? (this will not change ports)

2. Reinstall using ISO and pick setupconfig.xml option, then later restore backup on top? (this will take the ports from xml and won't ask you)

3. Reinstall using ISO and choosing the restore backup option? (this will ask you to select ports during the wizard since there is no XML with predefined answers for the ports)

 

[Kellermeister]

The V18 was a HyperV Windows-Installation, V20 tehre is no Windows release available, so I decided to migrate to a HyperV-Debian Installation. This was a restore from backup on a fresh-system installation. I was not aware that the ports were not in the export pacakage, so I assumed the ports were correct (In making a restore this is typically granted that everything will be as before). I'd like to have the port-information in the xml please.