We are happy to announce the new 126.96.36.199 firmware release.
Please note that this release is tested on the following models only:
Having upgraded only 6 Snom 760's to 188.8.131.52, all exhibit the following behaviour:
Phone completes update and reboots, then downloads provisioning.
Notification "SW-Update Failed" on every phone.
Every phone "successfully" upgraded - Settings/Maintenance/System Info shows "snom760-SIP 184.108.40.206"
Selecting "info" "info" "X" to remove failed notification. At some point, phone will reboot and attempt to do another firmware update.
"Check SW Update" from maintenance menu results in "File Not Found" "Error:99"
My suspicion is that an auto-firmware check has been introduced in the new 220.127.116.11, and that the incorrect parameter for this check is generating an Error:99.
Any advice received gratefully ?
Is there an auto-check ?
Can it be disabled ?
New problem with BT-Headset:
There seems a headset problem to be introduced in 18.104.22.168.
With 22.214.171.124 the behavior was half way fine, not with 126.96.36.199 anymore.
Incoming call, phone rings.
In both versions there is NO ring tone in the BT-Headset, even if "Ringer Device for Headset: Use Headset" or "Use Headset and Speaker" is set.
188.8.131.52: Answering the call by headset is no problem, light in Headset button on Phone is all time active.
184.108.40.206: Answering with the headset is NOT possible. User has to press the Headset button on the phone to answer the call. This is annoying if the user is not near to the desk.
Hardware: snom 760, snom BT-Dongle, Plantronics BT-Headset
To Ben Crosby, which PBX are you using for your phones? Some PBX's are using auto update and that needs to be disabled. Otherwise phones will keep trying to "update" to the firmware version from the PBX
After upgrading a 720 to 220.127.116.11, the telephone doesn't boot.
When I connect it, it doesn't show anything on the screen and all the button lights are solid (See attached image).
I tried to recover via TFTP but stays the same even after a successful recovery.
What about this firmware for the remaining devices like Snom 370?