10.1.101.11 Release

The phone models D717 and D735 will get new LCDs in an upcoming hardware revision. This release here is the second public 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 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. Same downgrade / potential brick protections as for D717/D735 new HW do apply. The recently introduced compatibility check in the firmware update process is now extended to this revisions.

SAP-4680: For refactoring purposes the maximum amount of entries in the local phone book is temporarily reduced from 2000 to 1000 @D715 @D717 D725 @D735

→ No workaround. Please make sure that you do not use this version if you need > 1000 local phone book entries with the affected models.

SAP-5086: The warm dialing is not working as expected, if a number is entered before the configured timeout in setting auto_dial (3s in this case) the number entered is not dialed automatically - press OK key is needed.

→ No workaround.

SAP-5424 / SAP-5427: Executing an action in an XML definition via the ".../settings.htm?settings=save..." leads to a significant performance loss (blocked phone) or even an apparent crash (caused by watchdog timeout). Due to a regression, the entire settings.htm is parsed by the XML minibrowser during action execution slowing down the phone up to the point when the watchdog timeout resets it. The issue can be confirmed in log review, e.g. by statements like: "Malformed xml (near HTML) and Action URL returned non-minibrowser data"

→ Workaround: instead of /settings.htm? the alternative /dummy.htm? (dummy.htm has no content) can be used inside the action as described e.g. in: Remote phone control or Can I set or change phone settings via HTTP requests

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-5899: It is not possible to stop receiving multicast paging with the corresponding fkey.

→ Workaround: Pressing the Cancel / X key.

SAP-5916: Support for call recording to USB sticks, see USB Recording is broken @D715 and @D315. The setting  The setting phone_features: "UsbRecordPlayback" cannot be set on that models.

→ No workaround: Please make sure that you do not use this version if you need USB call recording support with D715 or D315

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

SAP-6386: In context of recent E911 emergency call requirement implementation, enforced by law like Ray Baums Act & Kari's Law, a new status message was introduced: EmergencyCallNumbersMisconfigured and added per default to: status_msgs_that_are_essential. It is mandatory in the US to show the warning message: "Emergency numbers misconfigured" if the value 911 is removed or edited in setting: keyboard_lock_emergency. Everywhere these requirements are not applicable, the message is usally not wanted / misleading.

→ Workaround: By adding the new status message EmergencyCallNumbersMisconfigured to the setting: status_msgs_that_are_blocked (supported by usual XML Auto-provisioning and via Right-Click in setting.htm of the phone webserver - no reboot required).

SAP-6741: The XML Mini-browser's support for handling "401 Authentication required" challenges is broken.

→ Workaround: The required correction is available in 10.1.119.10.