Release Date: 09. February 2023

Important advice regarding upcoming hardware revisions of D717 & D735 (new LCD's), the D385N & D785N variants (without Bluetooth support) and the D713, D717, D735 (new network PHY)

Important Notes

  • Please make sure you read ALL of the information below before installing the software on your device.
  • Please install and test the software in your environment before mass deployment.
  • We encourage you to read and follow our security advisories.
  • This release does NOT directly include the OpenVPN feature in the firmware file anymore. If you wish to use this feature please make sure to download and install the VPN feature.
  • The models D345, D712, D725 are End of Sale (EOS) according to Snom Product Lifecycle and tested automatically. Please check out the Snom PLC for corresponding replacements!

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.

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.


Clarification regarding the pullback of Release 10.1.141.11

Please be informed that we had to pull back the former D862 and D865 exclusive Release 10.1.141.11 because of the blocking issue:

SAP-6968: Noise fencing feature had to be deactivated as in its current state did led to distorted / overdriven audio in handset use cases @D862 @D865

which is corrected with this Release 10.1.141.13 here (listed under corrections below)

NOTE:

For the new D8xx series, starting with D862 and D865 this is our Second Release deprecating the initial one. Please note: As the D8xx series is based on a substantially modernized software / software architecture you may find limitations & functional gaps compared to D3xx & D7xx series. The severity of such depends on the scope and complexity of your specific PBX solution. But no worries, if you will find your solution not yet fully supported as known from D3xx & D7xx: By upcoming development we will not only strive to close such potential gaps in comparison to D3xx & D7xx series asap, but even surpass these series in the future. Please make sure you review the known issues and limitations section below and see our PBX Partner overview in regards of D8xx series interoperability scope.

               


You will find a great start line in these D8xx Instructions. For additional information, datasheets, and how-to's please visit the product specific sites for D862 and D865.

Known issues and limitations:

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.

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.

XQI-2885: In case an incoming call is accepted via a supported EHS headset the audio does not switch automatically to headset @D865 @D862

→ Workaround: You need to perform an additional press on the headset audio key on the phone to have the audio on the EHS connected headset.

XQI-2914: Multicast / Auto-Answer scenarios requiring audio device activation and or Multicast RTP event detection are not supported yet @D865 @D862

→ No workaround.

XQI-2873: On D8xx series phones - users experience a missing of local ringback with early media @D865 @D862  , despite the setting rtp_early_media_muted is recovered.

→ No workaround - This is D8xx specific (while the original regression, XQI-2870 aka SAP-5942, is solved @D3xx & D7xx - see Corrections section below ) pending an audio device switching rework.

Error rendering macro 'wiki-markup'

org/apache/commons/lang/StringUtils


Error rendering macro 'wiki-markup'

org/apache/commons/lang/StringUtils