CISCO 800 Series Unified Communications Manager IM Presence Service

Product Information

Compatibility Matrix for Cisco Unified Communications Manager and the IM and Presence Service, Release 12.5(X)

• The Compatibility Matrix provides information on the compatibility of Cisco Unified Communications Manager and the IM and Presence Service. This document is applicable to Release 12.5(X) and includes compatibility information for subsequent SU releases as well, unless indicated otherwise.

Revision History

The following is the revision history of the Compatibility Matrix:

• August 30, 2023
• August 03, 2023
• January 31, 2023
• November 29, 2022
• December 08, 2022
• February 15, 2022
• May 05, 2022
• August 03, 2021
• February 22, 2021
• March 25, 2021
• April 28, 2021
• August 13, 2020
• October 19, 2020
• December 13, 2020
• June 19, 2019

Compatibility Matrix for Cisco Unified Communications Manager and the IM and Presence Service, Release 12.5(X)

• Compatibility Matrix for Cisco Unified Communications Manager and the IM and Presence Service 2 Revision History 2
• Purpose of this Document 3
• Supported Upgrade and Migration Paths 4
• Supported Versions 6
• Unified Communications Manager Compatibility Information 8
• IM and Presence Service Compatibility Information 25

Revised: August 31, 2023
Compatibility Matrix for Cisco Unified Communications Manager and the IM and Presence Service

Revision History

Purpose of this Document

• This document contains compatibility information for 12.5(x) releases of Cisco Unified Communications Manager (Unified Communications Manager) and the Cisco Unified Communications Manager IM and Presence Service (IM and Presence Service). This includes subsequent SU releases as well, unless indicated otherwise.

Supported Upgrade and Migration Paths
The following table highlights supported upgrade paths to upgrade to 12.5(x) releases of Unified Communications Manager and the IM and Presence Service.

Note

• Unless indicated otherwise, each release category includes the SU releases within that category. For example, 12.5(x) includes 12.5(1)SU releases. In addition, releases like 10.5(x) and 11.x include any SU releases within those categories as well.

Table 1: Supported Upgrade Paths for Cisco Unified Communications Manager and the IM and Presence Service

•  Version switching refers to the ability to install the new version as an inactive version and switch to the new version, and revert to the old version, whenever you want. This capability is supported with most direct upgrades, but not with migrations.
• PCD Upgrades and Migrations—Use Cisco Prime Collaboration Deployment Release 12.6 or later for all PCD tasks. If you want to upgrade or migrate to Unified CM Release 12.5(1)SU6 and above, ensure that you use the Release 14 version of the Cisco Prime Collaboration Deployment.

Required COP Files

• The tables below lists the upgrade paths that require COP files. You must install COP files on each node before you begin an upgrade using the Cisco Unified OS Administration interface, or before you begin an upgrade or migration using the Prime Collaboration Deployment (PCD) tool.
• If you are using PCD, you can perform a bulk installation of the COP files before you begin the upgrade.
• You can download COP files for Cisco Unified Communications Manager and the IM and Presence Service at https://software.cisco.com/download/home/268439621. After you select the destination version for the upgrade, choose Unified Communications Manager Utilities to see the list of COP files.

Note

You should run the Upgrade Readiness COP file prior to the upgrade in order to maximize upgrade success. If you do not run this COP file, you increase the risk of an unsuccessful upgrade due to undetected issues on the source release. Cisco TAC may require that you run this COP file to provide effective technical support.

Table 2: Required COP Files

Supported Versions

• The following table outlines which Unified Communications Manager and IM and Presence Service versions are supported with each release:

Version Compatibility Between Unified CM and the IM and Presence Service

• Version compatibility depends on the IM and Presence Service deployment type. The following table outlines the options and whether a release mismatch is supported between the telephony deployment and the IM and Presence Service deployment. A release mismatch, if it is supported, would let you deploy your Unified Communications Manager telephony deployment and your IM and Presence Service deployment using different releases.

Note

• Any respin or ES that is produced between Cisco.com releases is considered part of the previous release. For example, a Unified Communications Manager ES with a build number of 12.5.1.18[0-2]xx would be considered part of the 12.5(1)SU7 (12.5.1.17900-x) release.
• For Release 12.5(1)SU7a, a Unified Communications Manager ES with a build number of 12.5.1.181xx would be considered part of the 12.5(1)SU7a (12.5.1.18100-x) release.
• For Release 12.5(1)SU8a, a Unified Communications Manager ES with a build number of 12.5.1.19[0-2]xx would be considered part of the 12.5(1)SU8a (12.5.1.18901-1) release.

Table 3: Version Compatibility between Unified Communications Manager and the IM and Presence Service

Unified Communications Manager Compatibility Information

Cisco Collaboration System Applications

• The 12.5.x release of Cisco Unified Communications Manager and the IM and Presence Service is a part of the Cisco Collaboration Systems Release 12.5 through 12.8 and is compatible with the other Cisco Collaboration applications and versions in Cisco Collaboration Systems Release 12.5.
• Note Note that Release 12.5(1)SU3 is compatible with the 12.8 version of the Cisco Collaboration Systems.
• For a full list of Cisco Collaboration applications that are a part of Cisco Collaboration Systems Release 12.5(x), and the supported versions for each, see the Cisco Collaboration Systems Release Compatibility Matrix at:
• https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/unified/communications/system/Compatibility/CSR-Compatibility-Matrix-InteractiveHTML.html.

Android Push Notifications Compatibility Recommendations

• Android Push Notification feature is supported from the following software versions:
• Unified Communications Manager 12.5(1)SU3
• IM and Presence Service 12.5(1)SU3
• Cisco Jabber 12.9.1
• Cisco Expressway X12.6.2

Note This compatibility information isn’t applicable for Cisco WebEx.

Table 4: Recommended Release Requirements for Android Push Notifications Support

IM and Presence Stream Features/Services Advertisement Compatibility Recommendations

• IM and Presence Service supports the advertisement of XMPP stream features/services to the clients connecting over Cisco Expressway’s Mobile and Remote Access.
• Depending on your current IM and Presence Service version mix, you may need to enable or disable push notifications feature using FCM service flag on the Expressway as per the information given in the following table:
• configuration XCP Config FcmService: On/Off

Note Apple Push Notification Service (APNS) is not affected by the FCM service flag status.

Table 5: Solution Matrix from the Perspective of Expressway CLI Enable/Disable Command for Android Push Notifications (FCM)

Cisco Endpoint Support

• All end of Life and End of Sale announcements are listed here: https://www.cisco.com/c/en/us/products/eos-eol-listing.html.

Supported Cisco Endpoints

• The following table lists Cisco endpoints that are supported with this release of Cisco Unified Communications Manager. For endpoints that have reached End of Sale (EOS), or End of Software Maintenance, click the EOS link to view support details.

Note

Unless they are specified in the “Deprecated Phone Models” list, phone models that are End of Software Maintenance will continue to be supported on the latest Unified Communications Manager releases. However, they will not take advantage of any new Unified Communications Manager or firmware features associated with that release.

Table 6: Supported Cisco Endpoints

• Cisco Unified Communications Manager Release 12.5(1) is a part of Cisco Collaboration Systems Release 12.5. For a list of firmware versions that are used for each Cisco endpoint, see the Cisco Collaboration Systems Release Compatibility Matrix at
• http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/uc_system/unified/communications/system/Compatibility/
• CSR-Compatibility-Matrix.html.
• For information about Device Pack compatibility to support the phones, see the Cisco Unified Communications Manager Device Package Compatibility Matrix at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/matrix/CMDP_BK_CCBDA741_ 00_cucm-device-package-compatibility-matrix.html.

End of Support

• The following table lists Cisco endpoints that have reached the End of Support date, but which are not yet deprecated. Unlike deprecated endpoints, you can still deploy these endpoints in the latest release, but they are not supported actively, are not tested, and may not work.
• Click the links to view support announcements for each endpoint.
• For information on all of the End of Support and End-of-Life products, see https://www.cisco.com/c/en_ca/products/eos-eol-listing.html.

Table 7: Cisco Endpoints at End of Support

Cisco Endpoints at End of Support

• Cisco Unified SIP Phone 3911, 3951
• Cisco Unified IP Phone 6911, 6921, 6941, 6945, 6961, 7906G, 7911G, 7931G, 7940G, 7941G, 7960G, 7961G, 8941
• Cisco Unified IP Phone Expansion Module 7925G, 7925G-EX, 7926G
• Cisco Unified IP Conference Station 7935, 7936, 7937G
• Cisco Tele Presence EX60
• Cisco Tele Presence MX200-G1, MX200-G2, MX300-G1, MX300-G2
• Cisco Tele Presence 500-32, 500-37, 1000 MXP, 1100, 1300-65, 1300-47, 3000 Series

Deprecated Phone Models

• The following table lists all the phone models that are deprecated for this release of Unified Communications Manager, along with the Unified CM release where the phone model first became deprecated. For example, a phone model that was first deprecated in Release 11.5(1) is deprecated for all later releases, including all 12.x releases.
• If you are upgrading to the current release of Unified Communications Manager and you have any of these phone models deployed, the phone will not work after the upgrade.

Table 8: Deprecated Phone Models for this Release

• For additional information, refer to Field Notice: Cisco Unified Communications Manager Release 11.5(x) does not support some deprecated phone models at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/fieldNotice/cucm_b_ fn-deprecated-phone-
• models-1151.html.
• For additional information refer to the Field Notice: Cisco Unified Communications Manager Release 12.0(x) does not support some deprecated phone models at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/12_0_1/deprecated_phones/cucm_
• b_deprecated-phone-models-for-1201.html.
• Upgrades that Involve Deprecated Phones
• If you are using any of these phones on an earlier release and you want to upgrade to this release, do the following

1. Confirm whether the phones in your network will be supported in this release.
2. Identify any non-supported phones.
3. For any non-supported phones, power down the phone and disconnect the phone from the network.
4. Provision a supported phone for the phone user. You can use the following methods to migrate from older model to newer model phones
   Migration FX tool
5. Once all the phones in your network are supported by this release, upgrade your system.

Note

• Deprecated phones can also be removed after the upgrade. When the administrator logs in to Unified Communications Manager after completing the upgrade, the system displays a warning message notifying the administrator of the deprecated phones.

Licensing

• You do not need to purchase a new device license to replace a deprecated phone with a supported phone. The device license becomes available for a new phone when you either remove the deprecated phone from the system, or when you switch to the new Unified Communications Manager version, and the deprecated phone fails to register.

Virtualization Requirements

• This release of Unified Communications Manager and the IM and Presence Service supports virtualized deployments only. Deployments on bare-metal servers are not supported. For more information, see http://www.cisco.com/go/virtualized-collaboration.  See the following table for virtualization requirements.

Table 9: Virtualization Requirements

Supported LDAP Directories 12.5(x)

The following LDAP directories are supported

• Microsoft Active Directory 2008 R1/ R2
• Microsoft Active Directory 2012 R1/ R2
• Microsoft Active Directory 2016
• Microsoft Active Directory 2019—Supported for 12.5(1)SU2 and later
• Microsoft Lightweight Directory Services 2008 R1/ R2
• Microsoft Lightweight Directory Services 2012 R1/ R2
• Microsoft Lightweight Directory Services 2019—Supported for 12.5(1)SU2 and later
• Oracle Directory Services Enterprise Edition 11gR1 (11.1.1.7.x or newer)
• Oracle Unified Directory 11gR2 (11.1.2.2.0 or 11.1.2.3.0)
• Open LDAP 2.4.45 or later
• Other LDAPv3 Compliant Directories—Unified Communications Manager uses standard LDAPv3 for accessing the user’s data. Ensure that the supported control attribute is configured in the LDAPv3 compliant directory servers to be used with DirSync.(The supported control attribute may return the pagecontrolsupport and persistent  control  support sub attributes, if configured.)

Supported Web Browsers

The following web browsers are supported

• Chrome with Windows 10 (64 bit)
• Firefox with Windows 10 (64 bit)
• Internet Explorer 11 with Windows 7 (64 bit)
• Internet Explorer 11 with Windows 10 (64 bit)
•  Microsoft Edge browser with Windows 10 (32 bit/64 bit)
• Safari with MacOS (10.x)

Note We recommend that you use the latest version for all the web browsers supported.

SFTP Server Support

• For internal testing, we use the SFTP Server on Cisco Prime Collaboration Deployment (PCD) which is provided by Cisco, and which is supported by Cisco TAC. Refer to the following table for a summary of the SFTP server options:

Table 10: SFTP Server Support

SAML SSO Support
Although Cisco Collaboration infrastructure may prove to be compatible with other IdPs claiming SAML 2.0 compliance, only the following Dips’ have been tested with Cisco Collaboration solutions:

• Microsoft® Active Directory® Federation Services 2.0, 3.0, 4.0, and 5.0
• Microsoft Azure AD
• Okta
• OpenAM
•  Pin federate®
• F5 BIG-IP

For additional information on SAML SSO, see the SAML SSO Deployment Guide for Cisco Unified Communications Applications.

API Development

• The following table provides information on the API Development package that is supported with this release.

Table 11: Supported API Package

Secure Connections

TLS 1.2 Support

• Unified Communications Manager and the IM and Presence Service support the use of TLS 1.2. For detailed information on TLS 1.2 support, see the TLS 1.2 Compatibility Matrix for Cisco Collaboration Products.

SSL Connections

• For Secure Sockets Layer (SSL) connections, this release supports both Cisco SSL and Cisco SSH:
• Cisco OpenSSL 1.0.2zf.6.2.511 and Cisco’s 1.0.2zf.6.2.511
• Cisco OpenSSH client version 7.5.14i.1.5.18 and Cisco’s 7.5.14i.1.5.18

Supported Ciphers for Unified Communications Manager

• The following ciphers are supported by Unified Communications Manager:

Table 12: Unified Communications Manager Cipher Support for TLS Ciphers

Supported Ciphers for SSH

The following ciphers are supported by SSH

Table 13: Cipher Support for SSH Ciphers

Supported Platforms for Cisco Unified JTAPI and TAPI

Cisco Unified JTAPI

• For a detailed breakdown of supported Windows, Linux, and VMware platforms for Cisco Unified JTAPI, see
• https://developer.cisco.com/site/jtapi/documents/cisco-unified-jtapi-supported-jvm-versions/.
• For additional information that is related to Cisco Unified JTAPI, see Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager.

Cisco Unified TAPI

• For a detailed breakdown of supported Windows platforms for Cisco Unified TAPI, see https://developer.cisco.com/site/tapi/documents/supported-windows-os/.
• For additional information that is related to Cisco Unified TAPI, see Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager.
• IM and Presence Service Compatibility Information

Platform Compatibility

• The IM and Presence Service shares a platform with Unified Communications Manager. Many of the compatibility topics for Unified Communications Manager double as support topics for the IM and Presence Service. You can refer to the Unified Communications Manager compatibility chapter for information on the following items
• Secure Connections
• Virtualization Requirements
• Supported Web Browsers

External Database Support

• Many IM and Presence Service features such as Persistent Chat, High Availability for Persistent Chat, Message Archiver, and Managed File Transfer require that you deploy an external database. For information on database support, see the Database Setup Guide for the IM and Presence
• Service.

Supported LDAP Directories 12.5(x)

The following LDAP directories are supported

• Microsoft Active Directory 2008 R1/ R2
• Microsoft Active Directory 2012 R1/ R2
• Microsoft Active Directory 2016
• Microsoft Active Directory 2019—Supported for 12.5(1)SU2 and later
• Microsoft Lightweight Directory Services 2008 R1/ R2
• Microsoft Lightweight Directory Services 2012 R1/ R2
• Microsoft Lightweight Directory Services 2019—Supported for 12.5(1)SU2 and later
• Oracle Directory Services Enterprise Edition 11gR1 (11.1.1.7.x or newer)
• Oracle Unified Directory 11gR2 (11.1.2.2.0 or 11.1.2.3.0)
• Open LDAP 2.4.45 or later
•  Other LDAPv3 Compliant Directories—Unified Communications Manager uses standard LDAPv3 for accessing the user’s data. Ensure that the supported control attribute is configured in the LDAPv3 compliant directory servers to be used with DirSync.(The supported control attribute may return the pagecontrolsupport and persistent control support sub attributes, if configured.)

Federation Support

• SIP Federation/SIP Open Federation Support
• SIP Open Federation is supported as of 12.5(1)SU3.
• The following table lists supported SIP Controlled and SIP Open Federation integrations:

Table 14: Supported SIP Controlled and Open Federations

• The Single Enterprise Network can be partitioned intradomain federation or interdomain federation as the support values are the same for each. Business to Business integrations are always interdomain federation.

Supported XMPP Federations

• This release of IM and Presence Service supports XMPP Federation with the following systems:
• Cisco Weber Messenger
• IM and Presence Service Release 10.x and up
• Any other XMPP-compliant system

Intercluster Peering Support

• This release of the IM and Presence Service supports intercluster peering with the following IM and Presence Service releases:
• Note Intercluster peering is not supported if the IM and Presence Service version has gone EOL/EOS.
• Release 11.x
•  Release 12.x

Calendar Integration with Microsoft Outlook

• The IM and Presence Service supports Microsoft Outlook Calendar Integration with either an on-premise Exchange server or a hosted Office 365 server. See the table below for support information

Note For technical support on any third-party products, contact the respective organization.

Table 15: Support Information for Calendar Integration

Supported Ciphers for the IM and Presence Service

IM and Presence Service supports the following ciphers:

Table 16: Unified Communications Manager IM & Presence Cipher Support for TLS Ciphers

Remote Call Control with Microsoft Lync

Microsoft Remote Call Control (RCC) allows enterprise users to control their Cisco Unified IP Phone or Cisco IP Communicator Phone through Microsoft Lync, a third-party desktop instant-messaging (IM) application. When a user signs in to the Microsoft Lync client, the Lync server sends instructions, through the IM and Presence Service node, to the Cisco Unified Communications Manager to set up, tear down and maintain calling features based on a user’s action at the Lync client.

Note

• SIP federation and Remote Call Control (RCC) do not work together on the same IM and Presence Service cluster. This is because for SIP federation a user cannot be licensed for both Cisco IM and Presence Service and Microsoft Lync/OCS, but for RCC a user must be licensed for Cisco IM and Presence Service and Microsoft Lync/OCS at the same time.

Note

• An IM and Presence Service cluster that is used for RCC does not support Jabber or other IM and Presence Service functionality.

Software Requirements
The following software is required for integrating IM and Presence Service with Microsoft Lync Server:

• IM and Presence Service, current release
• IM and Presence Service Lync Remote Call Control Plug-in
• Cisco Unified Communications Manager, current release
• Microsoft Lync Server 2013 Release 4.x, Standard Edition or Enterprise Edition
• Lync Server Control Panel
• Lync Server Deployment Wizard
• Lync Server Logging Tool
• Lync Server Management Shell
• Lync Server Topology Builder
• Microsoft 2013 Lync Client
• (Optional) Upgraded Skype for Business 2015 Client

Note

The Skype for Business 2015 client must have been upgraded from a Lync 2013 client and must be registered to a Lync 2013 server.

• (Optional) Cisco CSS 11500 Content Services Switch
• Microsoft Domain Controller
• Microsoft Active Directory
• DNS
• Certificate Authority

Configuration

For additional details, including configuration information, see Remote Call Control with Microsoft Lync Server for the IM and Presence Service at https://www.cisco.com/c/en/us/support/unified-communications/unified-presence/
products-installation-and-configuration-guides-list.html.

© 2021 Cisco Systems, Inc. All rights reserved.

• Americas Headquarters Cisco Systems, Inc. San Jose, CA 95134-1706 USA
• Asia Pacific Headquarters Cisco Systems(USA)Pte. Ltd. Singapore
• Europe Headquarters Cisco Systems International lava Amsterdam, The Netherlands
• Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco Website at www.cisco.com/go/offices.

Documents / Resources

CISCO 800 Series Unified Communications Manager IM Presence Service [pdf] User Guide 800 Series Unified Communications Manager IM Presence Service, 800 Series, Unified Communications Manager IM Presence Service, Communications Manager IM Presence Service, Manager IM Presence Service, Presence Service, Service

References

• User Manual