Snom firmware update failure after upgrade to 15.5

[DalbyCC]

Hi Folks,

Got a strange problem with my system after the upgrade to 15.5.
I have 4 types of handsets, Snom 720, Snom 715, Snom M300 and Yealink W25P. After the 3CX upgrade I had to upgrade the handset firmware of all the handsets, the 720 and M300 handsets upgraded automatically with no issues. The W25P handsets can only be done manually but the 715 handsets had issues.

The 715 handsets would not upgrade, stating something about bad firmware. I deleted and re-downloaded the firmware from 3CX but got the same error. So I manually downloaded updated the firmware on every handset. Now 3CX is happy and showing the correct firmware version on the 715 handsets, but any time the handset is restarted I get the following error;

Software Update
Downloading Firmware
Failed to connect to host.
Error 7

I've checked he handset and it is pointing to the 3CX server as the provisioning host and the 3CX server is showing the correct interface for the phone. I've changed the Advanced setting - Update Policy on the handset from 'Update Automatically' to 'Never update, load settings only' and the firmware error has stopped coming up each day, but still comes up after a reboot.

Any ideas on how to fix this so the error message stops?

 

[CentrexJ]

I would suggest a factory reset on the 715 upgraded handsets. Then reprovision them. It should clear up any issues.

 

[JohnS_3CX]

Do you have any DHCP options defined on the network?

 

[DalbyCC]

Yes, the 3CX server has DHCP on it with reserved IPs for each handset, plus the Boot Server option for provisioning.

I'll try the factory reset during school vacations in a week, see if that works.

 

[DalbyCC]

Just tried the factory reset on a spare handset, the error still comes up after the reboot. So that tells me the error is coming from the server, not the handset.

I'll try wireshark next to see if I can pick up the fault.

 

[JohnS_3CX]

Yes, go ahead with the packet capture, but also consider disabling the boot server option on your network and testing again. Can you check if the error goes away when disabling it?