10.1.137.15 Release

With enrollment of this firmware release in your specific PBX / phone deployment(s) users may experience one or both of the following changes:

1. The common audio LED behavior can potentially be changed, if led_on was changed either by provisioning or locally on the phone
2. New status messages can occur in PUI, if status_msgs_that_are_blocked was changed either by provisioning or locally on the phone

Technical background: New customization options for the audio LED behavior were introduced by XQI-1167, as referenced below in section New features. By this change, several new settings were introduced and default values added, that may cause the changes of user experience. But this will happen only if  the setting led_on is changed from initial default values and/or if the setting status_msgs_that_are_blocked is changed from initial default values.

→ To do:

1. By adding the newly introduced values
   
       AudioIsMuted AudioDeviceIsHeadsetRTP AudioDeviceIsSpeakerRTP AudioDeviceIsHeadsetMulticast AudioDeviceIsSpeakerMulticast HeadsetIsActiveNoAudio AudioDeviceIsHeadsetRinging AudioDeviceIsSpeakerRinging AudioDeviceIsHeadsetDialtone AudioDeviceIsSpeakerDialtone AudioDeviceIsHeadsetDTMF AudioDeviceIsSpeakerDTMF AudioDeviceIsHeadsetRingback AudioDeviceIsSpeakerRingback AudioDeviceIsHeadsetMisc AudioDeviceIsSpeakerMisc
   
       regarding Audio Indicator LED's to the setting led_on 
   
   
2. By adding the newly introduced status messages
   
       HeadsetIsActiveNoAudio AudioDeviceIsHeadsetRinging AudioDeviceIsHeadsetRingback AudioDeviceIsHeadsetDialtone AudioDeviceIsHeadsetDTMF AudioDeviceIsHeadsetRTP AudioDeviceIsHeadsetMulticast AudioDeviceIsHeadsetMisc AudioDeviceIsSpeakerRinging AudioDeviceIsSpeakerRingback AudioDeviceIsSpeakerDialtone AudioDeviceIsSpeakerDTMF AudioDeviceIsSpeakerRTP AudioDeviceIsSpeakerMulticast AudioDeviceIsSpeakerMisc
   
       to the setting: status_msgs_that_are_blocked
   

Note : you can make custom adjustments to the value collections above depending on your user specific requirement - basically leveraging the new feature. Please be reminded to also take a look into the new settings: led_speaker_usage, led_headset_usage, led_mute_usage.

The phone models D717 and D735 will get new LCDs in an upcoming hardware revision. This release here is the fifth publicly available firmware that supports the new hardware revision and all the previous ones. But to prevent the new revision from being potentially bricked by downgrade attempts to older firmware releases, we introduced a compatibility check in the firmware update process (see SAP-6152 at 10.1.84.12 Release). In addition, new settings / setting values are integrated in this release here to facilitate identifying the new hardware revision to support e.g. it's handling in provisioning or other related maintenance-, inventory- management tasks.

• a new setting hardware_version 
• the value of hardware_version is shown in WUI (web user interface) section System Information /info.htm and PUI System Info screen
• a new "X-snom-" custom HTTP header is added providing the value of setting hardware_version in phone web requests (e.g. provisioning data requests)

The new phone models D385N and D785N are basically HW revisions of D385 and D785 without the Bluetooth chip. In upcoming hardware revisions of D713, D717 and D735 the network PHY is changed.
The same downgrade / potential brick protections as for D717/D735 new HW (new LCD's) do apply. The recently introduced compatibility check in the firmware update process is now extended to this revisions.

XQI-2180: In case the phone is handling 2 or more calls and starts a remote/server conference it will always switch into speaker/handsfree mode instead of keeping the current preferred audio device @D8xx series

→ No workaround, but a beta FW version with the required correction can be made available on request (please see: How to submit a support request on Snom Helpdesk)

SAP-6326: The new WUI, web userinterface is far advanced, esp. technically compared to D3xx & D7xx but does not yet support the entire scope of options & features known from its predecessor @D8xx series

→ Workaround: You can still access  the predecessor webinterface via http:// IP address of the phone:3112 (please note the http instead of http*s* and the port 3112) Hint: the screenshot feature opening /screen.bmp is also supported for D862 & D865.

XQI-1101: While LDAP is generally supported as in the D3xx or D7xx, like e.g. for inbound / outbound name & Call ID picture resolution & presentation, the search for LDAP contacts is not yet supported in the new PUI, phone user interface of the @D8xx series

→ No workaround.

XQI-713: While the configuration or provisioning of the Keypad/-board Lock related settings, like e.g.: enable_keyboard_lock is supported as in the D3xx or D7xx series it is not yet supported in the new PUI, phone user interface of the @D8xx series

→ No workaround.

XQI-523: While the configuration or provisioning of a Dialplan is supported as in the D3xx or D7xx series it is not yet supported / not yet effective in the new PUI, phone user interface of the @D8xx series

→ No workaround.

SAP-5625: The MJPEG support (e.g. for door phone integration) is limited to work correctly only in idle state, but not in Ringing or Connected, - the issue is under investigation.

→ No workaround. Please make sure that you do not use this version if you need MJPEG support for Ringing and/or Connected state

SAP-5942: Due to a regression the setting rtp_early_media_muted is broken, - no local ringback with early media. Related log statement: "[DEBUG0] MEDIA: RTP: no incoming early media packets, play ringtone instead".

→ No workaround, but a known last known good with 10.1.37.11

XQI-2295: Due to a regression reassigning of context sensitive function keys via WUI is impossible @D3xx @D7xx. Assigment via provisioning is not affected, as well as changing settings incl. reassignment of fkeys via HTTP GET requests or the Right-click in Setting page.

→ Workaround: In case provisioning or HTTP GET requests are no option, please use the Right-click in Setting page to assign the desired function to the context sensitive function keys.