10.1.73.16 Release

In parallel to the introduction of support for L2TP in SAP-5285 (see below) we made a significant improvement regarding the corresponding configuration tarball URL handling, which can be vital regarding your VoIP endpoint operation continuity:

• SAP-4950: The OpenVPN tarball is now downloaded only if the URL is changed via setting vpn_tarball_url
• SAP-2738: During reprovisioning the 802.1x EAP-TLS WPA configuration .tar file is now only downloaded, if the URL did change #Radius/NPS networks SCPP-8598
• SAP-5285: As a subset of the L2TP feature intro, - the download of the L2TP tarball is only downloaded if the l2tp_tarball_url did change

Conclusion:
Due to the improvement, the phone will not just repeatedly download the tar file on every reprovisioning / check-sync as in former FW versions. This change significantly reduces network congestion, the load on the device and mitigates the wear out of the flash storage due to only required re-/write cycles.  But you need to consider that any time you intend to provision the phone with a new configuration via the tar file, you need to change the corresponding tar file URL. Changing just the content of the tar file (e.g. a new 802.1.x EAP-TLS certificate) will not lead the phone to perform the download and processing the new/updated configuration info. One way to ensure continuous reprovisioning changes of content could be the usage of a time-stamp inside the file name and of course updating the tar-file-URL in provisioning XML file accordingly.

These changes are very important to take into consideration and to integrate into your operational workflow, especially when you think about endpoint certificate and updating such frequently due to their period of validity.

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 a 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. 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-5633: After the download of an XCAP directory from XCAP server into the local phonebook the contact entries show extra information composed of odd number sequences, - the issue is under investigation.

→ No workaround. Please make sure that you do not use this version if you need XCAP server directory support

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