In Unified Communications Manager, you can auto provision the Webex App or Cisco Jabber devices when new LDAP users are synchronized from Microsoft Active Directory. The Write back to LDAP option allows you to write the Primary DN chosen from Unified CM back to the LDAP server. LDAP attributes available for write back are: telephoneNumber, ipPhone, and mobile.

With this release, Webex Calling for Microsoft Teams users can view the call history for their shared devices which are registered to the Unified Communications Manager. For more information, see Webex Call Integration with Microsoft Teams for On-prem UCM.

To use this feature, the Unified Communications Manager node must be onboarded through Webex Cloud-Connected UC.

Microsoft Teams users must use Webex Calling integration for Microsoft Teams. For more information, see Webex Calling integration with Microsoft Teams.

Unified Communications Manager supports certificate revocation list, where the CA will have a list of digital certificates that have been revoked before their actual or assigned expiration date. To enable this feature you have to check the Enable CRL check box and enter the CRL Distribution Point URI from where the CRL files are downloaded.

For detailed information on the certificate revocation list support, see the 'Certificate Revocation Configuration' section in the Security Guide for Cisco Unified Communications Manager.

Unified Communications Manager now makes it easier to specify where cluster nodes will find their ISO files for upgrade or COP files, using the Cluster Software Location menu from the Cisco Unified OS Administration user interface.

In this release, you can centrally manage the Software Location settings for all cluster nodes from the publisher instead of locally on each cluster node.

From Release 12.5(1)SU7a, Unified Communications Manager supports thin-client IPs to be used for device mobility instead of Hosted Virtual Desktop (HVD) IPs for Webex client. However, from Release 14SU3 onwards, the Cisco Unified CM Administration UI displays the HVD IP address, in addition to the thin-client IP address for the Webex Virtual Desktop Infrastructure (VDI) clients. This feature is supported from Webex App VDI version 43.2 onwards. The display of HVD IP address on the UI enables better serviceability and debugging.

OAuth feature is now enhanced to eliminate refresh token dependency on Unified Communications Manager publisher node by providing access to the subscriber node to update the refresh token.

For more information, see the 'System Parameters Task Flow' section of the "Configure Enterprise Parameters and Services" chapter in the System Configuration Guide for Cisco Unified Communications Manager.

Webex App is not notified of incoming VoIP call notifications when an iOS device operates in a Wi-Fi constrained network with no internet connection such as, hospitals, cruise ships, airplanes, and so on. Due to lack of internet connectivity, the device does not have access to the Apple Push Notification Service (APNS). Users expect to receive calls without any delay. However, with APNS a call can be delayed for a few seconds when there is a network latency.

With this release, Local Push Notification Service (LPNS) for calls has been introduced for iOS devices. It helps to minimize any delay as the push message is sent to the client through a persistent connection. For more information, see the ‘Local Push Notification Service’ section in the Push Notifications Deployment Guide.

To know the minimum required iOS version for Webex App, see System requirements for Webex services.

The IM and Presence Service is enhanced to support OpenSSH 8.x and extends the public key length support to 4096 bits, for establishing connections with the External File Server.

For configuration information, see the "Configure Managed File Transfer" chapter in the Configuration and Administration of the IM and Presence Service Guide.

Currently, Unified Communications Manager inserts MTP for a DTMF mismatch in both secure and non-secure calls. But for secure calls, though MTP is inserted for a DTMF mismatch, it just passes through the media between the parties. Hence, the DTMF events are not sent between the parties. Before Unified CM Release 14SU3, DTMF translation worked only for non-secure calls when there was an MTP allocated for a DTMF mismatch.

With this release, Unified CM can invoke a hardware MTP (with SRTP DTMF interwork support) for a DTMF mismatch between secure endpoints. For more information, see the 'SRTP DTMF Interworking' section in the "Configure Media Resource" chapter of the System Configuration Guide for Cisco Unified Communications Manager.