In the existing Unified Communications Manager, CTI applications had to have a direct TCP connection to CTI Manager to leverage CTI control. As a result, Webex Apps could not be used in Desk Phone Control Mode or Extend and Connect Mode when the client was off-premises.

With this release, Webex App supports Desk Phone Control Mode/Extend and Connect Mode for clients connecting remotely. To use this feature, the Unified Communications Manager node must be onboarded through Cloud-Connected UC.

For more information, see Borderless CTI.

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.

You can:

• Add, edit, or modify any of the existing configurations for any node in the same cluster from the Unified Communications Manager publisher as a one-stop shop.

• Apply the same software location details to all the other nodes in the cluster, including the publisher.

Unified Communications Manager supports dialing '988' calls, that are 3-digit dialing codes that will be routed to the National Suicide Prevention Lifeline centers. All telecommunication carriers and interconnected voice over Internet Protocol (VoIP) service providers will offer this service to connect with suicide prevention and mental health crisis personnel. This is in support of the FCC mandate of supporting a 3-digit dial code for Suicide Prevention Hotline that comes into effect from July 22, 2022.

For more information, see: https://www.fcc.gov/suicide-prevention-hotline.

In Unified Communications Manager, the External Phone Number can be masked for all configured line numbers for the latest phone models. Existing phone models continue to display the External Phone Number Mask for the primary line.

Note	The supported phone models are 78xx and 88xx series.

From Unified Communication Manager 14 SU2 release onwards, the Organization Unit field is removed by default from the Certificate Signing request. From this release onwards you can choose Include OU in CSR option to include the Organization Unit field in the Certificate Signing Request.

For more information, see the section 'Self-Signed Certificate Fields' of the Security Guide for Cisco Unified Communications Manager

Unified Communications Manager now includes Certificate Authority Proxy Function (CAPF) Online CA type “EST Supported CA” to support the automatic enrollment of certificates with CAs having inbuilt EST server mode.

The RedSky solutions integrated with Unified Communications Manager allow the clients to have an active location URI for 9-1-1 emergency calling coverage for their entire workforce, whether on campus or remote, and send the calls to emergency responders. For more information, see the "Emergency Call Handling with RedSky" chapter in the Feature Configuration Guide for Cisco Unified Communications Manager.

In the existing Unified Communications Manager, when a secure call is placed to a Hunt Pilot and all the Line Groups are busy, the call is temporarily placed on hold. If the endpoint does not support Secure Real-Time Transport Protocol (SRTP) fallback, the call that is placed to Parking Lot (non-secure device) drops off due to crypto mismatch.

With this feature, the Unified CM handles the originating SRTP-only call as a secure call throughout, irrespective of the SRTP fallback option status. For more information, see the 'Secure Call Queuing' section in the "Configure Call Queuing" chapter of the Feature Configuration Guide for Cisco Unified Communications Manager.

Unified Communications Manager now supports all crypto ciphers while exchanging call capabilities post Cisco IP Voice Media Streaming (IPVMS) devices (MOH, IVR, or Annunciator) after mid-call events, such as transfer or hold, from the remote side. With this feature, the current active secure calls or security is not impacted. For more information, see the 'SRTP Cipher Mismatch with Media Streaming Devices' section in the "Default Security" chapter of the Security Guide for Cisco Unified Communications Manager.

Unified Communications Manager's FIPS Mode constraints have now been upgraded (CiscoSSL, CiscoFOM, and CiscoSSH to 7. X) and that limits the use of the SSH-RSA algorithm in the FIPS mode. The older version of Unified CM uses OpenSSH 5. X which does not support the latest SSH algorithms. You must deploy the COP files before upgrading the clusters in FIPS mode. If you are upgrading any of your older Unified CM or IM and Presence Service versions to Release 14SU2 in FIPS mode, install the COP file ciscocm.ciscossl7_upgrade_CSCwa48315_CSCwa77974_v1.0.k4.cop.

For more information, see the 'Supported Upgrade and Migration Paths with COP Files' section in the Upgrade and Migration Guide for Cisco Unified Communications Manager and the IM and Presence Service.

If your 14SU2 version of Cisco Prime Collaboration Deployment is in FIPS mode and you are using any of the Pre-12.5 UC clusters to perform cluster discovery, upgrade, or migration, you must first switch your Cisco Prime Collaboration Deployment to work in the non-FIPS mode before proceeding with any of these tasks. For Direct Standard Upgrade or Migration of UC clusters in FIPS mode with the Pre-14SU2 releases, install the COP file ciscocm.ciscossl7_upgrade_CSCwa48315_CSCwa77974_v1.0.k4.cop on the UC clusters.

For more information, see the 'Supported Tasks for Applications and Versions' section in the Prime Collaboration Deployment Administration Guide, Release 14.

The IM and Presence Service supports Windows authentication for MSSQL external database.

When this feature is enabled, Windows groups can be created at the domain level and a login can be created on MSSQL Server for the entire group. For more information, see the 'Windows Authentication for MSSQL Database for Persistent Chat' section in the Configuration and Administration of the IM and Presence Service Guide.