Snom problems after update to 10.1.169.13

[Alessio.Hsyde]

Hi everyone,

after updating to firmware version 10.1.169.13.
All D710, D717 and D785 phones randomly, without warning reboot.
In some cases it happens that they don't provision correctly and get stuck.
Obviously if I try to put version 10.1.169.15 (which seems to solve the problem), 3CX returns it to its latest certified 10.1.169.13 recreating the problem.

Is there any workaround for this problem? Has this happened to others?

Thank you.

 

[RJansen]

I have also a problem with the firmware 10.1.169.13
i did make a support ticket this morning at snom because we are a snom partner.
i did notice that snom released 10.1.169.15 Maintenance update which corrects some issues.

Changelog​

Changes since release version 10.1.169.13

Corrections:​

XQI-2476: Partial Number Lookup was extended to find numbers in the local TBook @D3xx @D7xx @D86x
XQI-4205: US number formatting is disregarding the timezone. @D86x
XQI-4368: The termination tones were not played @D1xx @D3xx @D7xx
XQI-4434: CPU Load increases abnormally with call duration @D1xx @D3xx @D7xx
XQI-4513: Provisioning was triggered to often but should be triggered only, if really needed, like: on check-sync, boot, refresh timer, URL change @D1xx, @D3xx, @D7xx, @D86x

Perhaps the CPU load increase makes your phones reboot or the provisioning trigger.

 

[Alessio.Hsyde]

Ok, thanks for the reply.

Now I have to find a way to force the update to 10.1.169.15 via 3CX. Currently if I manually update the first reboot/provisioning it automatically returns me to 10.1.169.13.

 

[RJansen]

Im not sure but i think 3cx doesnt revert a higher firmware then is available on the 3CX pbx.
So a manual upgrade (snom gui) to 10.1.169.15 wont revert back to 10.1.169.13

 

[Alessio.Hsyde]

I have already tried with a 3CX lab pbx and unfortunately it goes back.

 

[RJansen]

Ok, than winscp into your pbx and remove/delete the firmware file from the provisioning firmware folder.
And manual update the snom phone to the desired firmware.

 

[Alessio.Hsyde]

I try to download on "firmware" and "firmware_new" folders with WGET the 10.1.169.15 and change the firmwares.json without any positive result!

 

[RJansen]

Meanwhile is it possible if you can update your snom template and change auto_update to value to settings_only?
<update_policy perm="">auto_update</update_policy>

This way you should manage to upgrade manually.

 

[JohnS_3CX]

Hi,

Snom has been informed (both by us and Snom customers) regarding the issues.
They are working on a newer firmware which should resolve these problems.

As always, we will not be able to release any new firmware before the manufacturer fully tests it with 3CX and releases it to us, so currently no ETA is provided.

 

[JohnS_3CX]

The snom firmware v10.1.175.0 has been released today on V18 and V20 for the affected models:

• D335
• D345
• D385
• D712
• D713
• D715
• D717
• D725
• D735
• D785

 

[Roopnarine]

The snom firmware v10.1.175.0 has been released today on V18 and V20 for the affected models:

• D335
• D345
• D385
• D712
• D713
• D715
• D717
• D725
• D735
• D785

John I am unable to update SNOM affected devices to this firmware. I am getting SW Update failed.

I am hosting 3CX in Azure

 

[NikolasA_3CX]

John I am unable to update SNOM affected devices to this firmware. I am getting SW Update failed.

I am hosting 3CX in Azure

Download the firmware from the below website and try updating it manually, to rule out any issues with the IP Phones.
https://www.3cx.com/docs/phone-firmwares/