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, 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 3
Supported Versions 6
Unified Communications Manager Compatibility Information 7
IM and Presence Service Compatibility Information 22
Revised: August 3, 2021
Compatibility Matrix for Cisco Unified Communications

Manager and the IM and Presence Service
Revision History
Date Revision
June 19, 2019 Added OpenJDK version for 12.5(1)SU1 release.
Updated for 12.5(1)SU1. Changed title to 12.5(x)
February 03, 2020 Updated upgrade paths, LDAP support, version support for 12.5(1)SU2.
February 20, 2020 Updated LDAPv3 Compliant Directories.
March 09, 2020 Updated Cisco Endpoint Support section.
March 11, 2020 Added Cisco Headsets to Endpoint Support.
April 06, 2020 Removed non-supported Cisco endpoints.
May 12, 2020 Added JTAPI Support information.
July 8, 2020 Updated SSL Connections and SSH Clients.
July 27, 2020 Updated supported ciphers list for IM and Presence Service.
August 13, 2020 Updated version support for 12.5(1)SU3.
August 13, 2020 Added support for Microsoft® Active Directory® Federation Services 3.0, 4.0,
and 5.0, and Microsoft Azure.
October 19, 2020 Corrected list of Webex endpoints.
November 18, 2020 Corrected dates.
December 13, 2020 Renamed Cisco Webex Teams to Cisco Webex.
February 22, 2021 Initial release version for 12.5(1)SU4.
February 22, 2021 Updated upgrade paths and version support for 12.5(1)SU4.
February 22, 2021 Added IM and Presence Service support for the advertisement of XMPP stream
features/services over Mobile and Remote Access.
February 22, 2021 Added support for Cisco VG420 Analog Voice Gateway and Cisco Catalyst 8300
Series Edge Platforms.
March 25, 2021 Fixed the 7941 G Series EOS URL.
2
Date Revision
April 28, 2021 Added support for Ciphers for Application and OS End Users.
August 03, 2021 Initial release version for 12.5(1)SU5.
August 03, 2021 Updated upgrade paths and version support for 12.5(1)SU5.
August 03, 2021 Added Microsoft Exchange Server 2019 support for the IM and Presence Service
Calendar Integration with Microsoft Outlook.
Purpose of this Document

This document contains compatibility information for 12.5(x) releases of Cisco Unified Communications Manager and the 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 Cisco 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 8.6(5) 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
Source Destination Supported Upgrade Method Version Switching*

(Source to
Destination and
Vice Versa)
Cisco Unified Communications Manager Upgrade Paths
Any Unified CM 12.5(x) Legacy upgrade. Direct upgrade and migration is not supported. Version switching
release prior to Do the following: not supported
6.1(5)
1. Upgrade to 6.1(5), 7.1(3) or 7.1(5)—See information on
legacy upgrades
2. PCD Migration** to 12.5(x)
Unified CM 6.1(5), 12.5(x) PCD Migration** Version switching

7.1(3), 7.1(5), 8.x, not supported
9.x, 10.0(x)
3
Source Destination Supported Upgrade Method Version Switching*
(Source to
Destination and
Vice Versa)
Unified CM 10.5(x), 12.5(x) Unified OS Admin upgrade (direct refresh) Version switching
11.x, 12.0(x) supported for
CLI upgrade (direct refresh)
upgrades, but not for
PCD Upgrade (direct refresh)** migrations
PCD Migration**
Fresh Install only to destination 12.5(1)SU5 or later.
Unified CM 12.5(x) 12.5(y) Unified OS Admin upgrade (direct standard) Version switching
supported for
CLI upgrade (direct standard)
upgrades, but not for
PCD Upgrade (direct standard)** migrations
IM and Presence Service Upgrade Paths
Cisco Unified IM and Presence Direct upgrade or Migration is not supported. Do the following: Version switching
Presence 8.0(x) 12.5(x) not supported
1. Direct upgrade to 8.5(4)—See information on legacy upgrades
2. PCD Migration** from 8.5(4) to 12.5(x)
Cisco Unified IM and Presence PCD Migration** Version switching

Presence 8.5(4), 12.5(x) not supported
8.6(3), 8.6(4), and
8.6(5),
IM and Presence 9.x,
10.0(x)
IM and Presence 12.5(x) Unified OS Admin upgrade (direct refresh) Version switching
10.5(x), 11.x or supported for
CLI upgrade (direct refresh)
12.0(x) upgrades, but not
PCD upgrade (direct refresh)** supported for
migrations.
PCD Migration**
IM and Presence 12.5(y) Unified OS Admin upgrade (direct standard) Version switching
12.5(x) supported for
CLI upgrade (direct standard)
upgrades, but not
PCD upgrade (direct standard)** supported for
migrations.
* 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.
4
Limitations
The above table does not include direct upgrades and PCD migrations from the following systems. For these systems, we recommend
a fresh installation as direct upgrades and PCD migrations are not supported:
• Cisco Business Edition 3000 on MCS 7816-C1
• Cisco Business Edition 5000 on MCS 7828
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 Admin 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 Although it is not mandatory, Cisco strongly recommends that you run the Upgrade Readiness COP file prior to the upgrade
in order to maximize upgrade success. Cisco TAC may require that you run this COP file to provide effective technical support.
Table 2: Required COP Files
From To COP Files
Cisco Unified Communications Manger Upgrades
Unified CM 8.6(x), 12.5(x) Required COP files:

9.x
• ciscocm.version3-keys.cop.sgn
Optional COP files:

• ciscocm.vmware-disk-size-reallocation-<latest_version>.cop.sgn)
• ciscocm.free_common_space_v<latest_version>.cop.sgn
Unified CM 10.5(x), 12.5(x) Direct Refresh upgrade; no COP file required.

11.0(x)
Unified CM 11.5(x) 12.5(x) Direct Refresh upgrade; COP file is required to increase the disk space.
• ciscocm.free_common_space_v<latest_version>.cop.sgn. To download the COP
files and the Readme files, go to https://software.cisco.com > click Software
Download link under Download & Upgrade section, and then, navigate to the
Unified Communications > Call Control > Cisco Unified Communications
Manager (CallManager) > <Version> > Unified Communications
Manager/CallManager/Cisco Unity Connection Utilities.
5
From To COP Files
Unified CM 12.0(1) 12.5(x) PCD Migrations require a COP file:

• ciscocm-slm-migration.k3.cop.sgn
Note This requirement applies only for Prime Collaboration Deployment migrations
from Release 12.0(1) of Unified Communications Manager (build
12.0.1.10000-10). If you are migrating from a higher release, such as Unified
Communications Manager 12.0(1)SU1, you don't need to install the COP
file.
Unified CM 12.5(x) 12.5(y) Direct Standard upgrade; no COP file required.
IM and Presence Service Upgrades
CUP 8.5(4) through 12.5(x) Required COP files:

8.6(1)
• cisco.com.cup.refresh_upgrade_v<latest_version>.cop
9.1(x) 12.5(x) Requires following COP File:

10.5(x), 11.x, 12.x 12.5(x) No COP files required
Supported Versions
The following table outlines which Cisco Unified Communications Manager and IM and Presence Service versions are supported
with each release:
For this Release... The Following Versions are Supported...
12.5(1) • Cisco Unified Communications Manager 12.5.1.10000-22

• IM and Presence Service 12.5.1.10000-22
12.5(1)SU1 • Cisco Unified Communications Manager 12.5.1.11900-146



6
For this Release... The Following Versions are Supported...


Version Compatibility Between Unified CM and the IM and Presence Service

Version compatibility depends on the IM and Presence deployment. The following table outlines the options and whether a release
mismatch is supported between the telephony deployment and the IM and Presence deployment. A release mismatch, if it is supported,
would let you deploy your Unified Communications Manager telephony deployment and your IM and Presence deployment using
different releases.
Table 3: Version Compatibility between Unified Communications Manager and the IM and Presence Service
Deployment Type Release Mismatch Description
Standard Not supported Unified Communications Manager and the IM and Presence Service are in the same
Deployment of IM cluster and must run the same release—a release mismatch is not supported.
and Presence
Centralized Supported The IM and Presence deployment and the telephony deployment are in different clusters
Deployment of IM and can run different releases—a release mismatch is supported.
and Presence
Note The IM and Presence central cluster also includes a standalone Unified CM
publisher node for database and user provisioning. This non-telephony node
must run the same release as 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 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.
7
Android Push Notifications Compatibility Recommendations
Android Push Notification feature is supported only on 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
Unified Communications Expressway Version Unified Communications On-Premises Deployments

Manager and IM and Mobile and Remote Access
Presence Service Version
All clusters on: X12.6.2 Android Push Notification is not Android Push Notification is not
supported supported
• 11.5(1)SU8 or earlier
• 12.5(1)SU2 or earlier
All clusters on: X12.6.2 Enable Android Push Android Push Notification is
Notification using the CLI supported
• 12.5(1)SU3
xConfiguration XCP Config
FcmService: On on
Expressway for messaging only
Cluster with mixed versions X12.6.2 Android Push Notification for Android Push Notification is
(11.5(1)SU8 or earlier, OR Messaging is not supported supported with Release
12.5(1)SU2 or earlier, AND 12.5(1)SU3
VOIP is supported on Release
12.5(1)SU3)
12.5(1)SU3
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:
xConfiguration XCP Config FcmService: On/Off
Note Apple Push Notification Service (APNS) is not affected by the FCM service flag status.
8
Table 5: Solution Matrix from the Perspective of Expressway CLI Enable/Disable Command for Android Push Notifications (FCM)
Mixed Versions IM and Presence Expected Status of FCM Flag on Comment

Clusters Expressway X12.7
Any 11.5(1)SU with OFF Android Push (FCM) NOT supported.

12.5(1)SU2 and lower
11.5(1)SU8 (and lower) or 12.5(1)SU2 (and OFF Android push (FCM) NOT supported
lower) with 12.5(1)SU3
11.5(1)SU8 (and lower) or 12.5(1)SU2 (and OFF Android push (FCM) supported on
lower) with 12.5(1)SU4 (and higher) 12.5(1)SU4 (or newer) versions
11.5(1)SU9 (and higher) or 12.5(1)SU4 ON Android push (FCM) supported on version

(and higher) with 12.5(1)SU3 12.5(1)SU3 and higher
11.5(1)SU9 (and higher) with 12.5(1)SU4 Flag not required Android push (FCM) supported on
(and higher) 12.5(1)SU4 (or newer) versions
(Expressway 12.7 relies fully on the new
discovery mechanism)
Cisco Endpoint Support
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
Device Series Device Model
Cisco Unified SIP Phone 3900 Series Cisco Unified SIP Phone 3905
Cisco Unified IP Phone 6900 Series Cisco Unified IP Phone 6901
Cisco IP Phone 7800 Series Cisco IP Phone 7811

Cisco IP Phone 7821
Cisco IP Phone 7841
Cisco IP Phone 7861
Cisco IP Conference Phone 7832
9
Cisco Unified IP Phone 7900 Series Cisco Unified IP Phone Expansion Module 7915—EOS Notice
Cisco Unified IP Phone Expansion Module 7916—EOS Notice
Cisco Unified IP Phone 7942G—EOS Notice
Cisco IP Phone 8800 Series Cisco IP Phone 8811, 8831, 8841, 8845, 8851, 8851NR, 8861, 8865, 8865NR
Cisco Wireless IP Phone 8821, 8821-EX
Cisco Unified IP Conference Phone 8831—EOS Notice
Cisco IP Conference Phone 8832
Cisco Unified IP Phone 8900 Series Cisco Unified IP Phone 8945—EOS Notice
Cisco Unified IP Phone 8961—EOS Notice
Cisco Unified IP Phone 9900 Series Cisco Unified IP Phone 9951—EOS Notice
Cisco Unified IP Phone 9971—EOS Notice
Cisco Jabber Cisco Jabber for Android

Cisco Jabber for iPhone and iPad
Cisco Jabber for Mac
Cisco Jabber for Windows
Cisco Jabber Softphone for VDI - Windows (formerly Cisco Virtualization Experience
Media Edition for Windows)
Cisco Jabber Guest
Cisco Jabber Software Development Kit
Cisco Jabber for Tablet
Cisco Headset Series Cisco Headset 520

Cisco Headset 530
Cisco Headset 560
Cisco Headset 730
Cisco IP Communicator Cisco IP Communicator—EOS Notice
10
Cisco Webex Cisco Webex App

Cisco Webex Room Phone
Cisco Webex Desk Camera
Cisco Webex Desk Pro
Cisco Webex Desk Limited Edition
Cisco Webex Share
Cisco Webex Board 55, 55s, 70, 70s, 85, 85s
Cisco Webex Room Panorama
Cisco Webex Room 70 Panorama
Cisco Webex Room 70 Panorama Upgrade
Cisco Webex Room 70
Cisco Webex Room 70 G2
Cisco Webex Room 55
Cisco Webex Room 55 Dual
Cisco Webex Room Kit Pro
Cisco Webex Room Kit Plus
Cisco Webex Room Kit
Cisco Webex Room Kit Mini
Cisco Webex Room Kit Plus Precision
Cisco Webex Room USB
Cisco Webex Meetings Cisco Webex Meetings for iPad and iPhone
Cisco Webex Meetings for Android
Cisco Analog Telephony Adapter Cisco ATA 190 Analog Telephone Adapter—EOS/EOL Notice
Cisco ATA 191 Analog Telephone Adapter
Cisco DX Series Cisco DX70—EOS Notice

Cisco Webex DX80
Cisco DX650—EOS Notice
Cisco TelePresence IX5000 Cisco TelePresence IX5000
Cisco TelePresence EX Series Cisco TelePresence System EX60—EOS Notice

Cisco TelePresence System EX90—EOS Notice
11
Cisco TelePresence MX Series Cisco TelePresence MX200 G2—EOS Notice

Cisco TelePresence MX300 G2—EOS Notice
Cisco TelePresence MX700D—EOS Notice
Cisco TelePresence MX800S—EOS Notice
Cisco TelePresence MX800D—EOS Notice
Cisco TelePresence SX Series Cisco TelePresence SX10—EOS Notice

Cisco TelePresence SX20—EOS Notice
Cisco TelePresence SX80—EOS Notice
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 TelePresence MX200-G1, MX200-G2, MX300-G1, MX300-G2
• Cisco TelePresence 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.
12
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
Deprecated Phone Models for this Release First Deprecated as of Unified CM...
• Cisco Unified Wireless IP Phone 7921 12.0(1) and later releases

• Cisco Unified IP Phone 7970
• Cisco IP Phone 12 S 11.5(1) and later releases

• Cisco IP Phone 12 SP
• Cisco IP Phone 12 SP+
• Cisco IP Phone 30 SP+
• Cisco IP Phone 30 VIP
• Cisco Unified IP Phone 7902G
• Cisco Unified IP Phone 7910+SW
• Cisco Unified IP Phone 7910G+SW
• Cisco Unified Wireless IP Phone 7920
• Cisco Unified IP Conference Station 7935
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.
13
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 Cisco Media Convergence Servers are not supported. See the following table for virtualization requirements.
Table 9: Virtualization Requirements
Virtualization Requirements For information, go to...

for...
Unified Communications For information about Unified Communications Manager virtualization requirements, go to
Manager https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/
virtualization-cisco-unified-communications-manager.html.
IM and Presence Service For information about the IM and Presence Service virtualization requirements, go to
https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/
virtualization-cisco-ucm-im-presence.html.
Cisco Business Edition For information on the virtualization requirements for Unified Communications Manager in a
Deployments collaboration solution deployment such as Cisco Business Edition, go to https://www.cisco.com/
c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/
collaboration-virtualization-hardware.html.
Supported LDAP Directories 12.5(x)

The following LDAP directories are supported:
• Microsoft Active Directory 2019—Supported for 12.5(1)SU2 and later
• Microsoft Active Directory 2016
• Microsoft Active Directory 2012 R1/ R2
• Microsoft Active Directory 2008 R1/ R2
14
• Microsoft Lightweight Directory Services 2019—Supported for 12.5(1)SU2 and later
• Microsoft Lightweight Directory Services 2012 R1/ R2
• Microsoft Lightweight Directory Services 2008 R1/ R2
• 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 supportedcontrol attribute is configured in the LDAPv3 compliant directory servers to be used with DirSync.
(The supportedcontrol attribute may return the pagecontrolsupport and persistentcontrolsupport sub attributes,
if configured.)
Supported Web Browsers

The following web browsers are supported:
• Firefox with Windows 10 (64 bit)
• Chrome with Windows 10 (64 bit)
• Internet Explorer 11 with Windows 10 (64 bit)
• Internet Explorer 11 with Windows 8.1 (64 bit)
• Internet Explorer 11 with Windows 7 (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
SFTP Server Support Description
SFTP Server on Cisco Prime Collaboration This server is the only SFTP server that is provided and tested by Cisco, and fully
Deployment supported by Cisco TAC.
Version compatibility depends on your version of Emergency Responder and Cisco
Prime Collaboration Deployment. See the Cisco Prime Collaboration Deployment
Administration Guide before you upgrade its version (SFTP) or Emergency Responder
to ensure that the versions are compatible.
15
SFTP Server Support Description
SFTP Server from a Technology Partner These servers are third party provided and third party tested. Version compatibility
depends on the third-party test. See the Technology Partner page if you upgrade their
SFTP product and/or upgrade Unified Communications Manager for which versions
are compatible:
https://marketplace.cisco.com
SFTP Server from another Third Party These servers are third party provided and are not officially supported by Cisco TAC.
Version compatibility is on a best effort basis to establish compatible SFTP versions
and Emergency Responder versions.
Note These products have not been tested by Cisco and we cannot guarantee
functionality. Cisco TAC does not support these products. For a fully tested
and supported SFTP solution, use Cisco Prime Collaboration Deployment
or a Technology Partner.
SAML SSO Support

Although Cisco Collaboration infrastructure may prove to be compatible with other IdPs claiming SAML 2.0 compliance, only the
following IdPs have been tested with Cisco Collaboration solutions:
® ®
• Microsoft Active Directory Federation Services 2.0, 3.0, 4.0, and 5.0
• Microsoft Azure AD
• OpenAM
®
• PingFederate
• F5 BIG-IP
• Okta
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
Package Type Details
API Development Cisco Unified Communications Manager and the IM and Presence
Service support OpenJDK for application development.
• Release 12.5(1) uses OpenJDK version 1.7.0.191.
• Release 12.5(1)SU1 uses OpenJDK version 1.7.0.201.
16
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 TLS 1.2 Compatibility Matrix for Cisco Collaboration Products at:
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/uc_system/unified/communications/system/Compatibility/TLS/
TLS1-2-Compatibility-Matrix.html.
SSL Connections
For Secure Sockets Layer (SSL) connections, this release supports both Cisco SSL and Cisco SSH:
• Cisco OpenSSL 1.0.2y.6.2.403 and CiscoSSL 1.0.2y.6.2.403
• Cisco OpenSSH client version 7.5.14i.1.5.18 and CiscoSSH 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
Application / Protocol Port Supported Ciphers

Process
Cisco CallManager TCP / TLS 2443 ECDHE-RSA-AES256-GCM-SHA384:

ECDHE-RSA-AES256-SHA384:
ECDHE-RSA-AES256-SHA:
AES256-GCM-SHA384:
AES256-SHA256:
AES256-SHA:CAMELLIA256-SHA:
ECDHE-RSA-AES128-GCM-SHA256:
AES128-GCM-SHA256:
AES128-SHA256:AES128-SHA:
CAMELLIA128-SHA
DRS TCP / TLS 4040 ECDHE-RSA-AES256-GCM-SHA384:

DHE-RSA-CAMELLIA256-SHA:
AES256-GCM-SHA384:AES256-SHA256:
AES128-SHA:CAMELLIA128-SHA
17
Process
Cisco Tomcat TCP / TLS 8443 / 443 ECDHE-RSA-AES256-GCM-SHA384:

DHE-RSA-AES256-GCM-SHA384:
DHE-RSA-AES256-SHA256:
DHE-RSA-AES256-SHA:
DHE-RSA-AES128-SHA:
ECDHE-RSA-DES-CBC3-SHA:
EDH-RSA-DES-CBC3-SHA:
DES-CBC3-SHA
ECDHE-ECDSA-AES256-GCM-SHA384:
ECDHE-ECDSA-AES256-SHA384:
ECDHE-ECDSA-AES256-SHA:
ECDHE-ECDSA-DES-CBC3-SHA
Cisco CallManager TCP / TLS 5061 ECDHE-RSA-AES256-GCM-SHA384:

ECDHE-ECDSA-AES256-GCM-SHA384
ECDHE-RSA-AES256-SHA
ECDHE-ECDSA-AES128-GCM-SHA256
ECDHE-RSA-AES128-SHA256
ECDHE-RSA-AES128-SHA
Cisco CTL Provider TCP / TLS 2444 AES256-GCM-SHA384:AES256-SHA256:

Cisco Certificate TCP / TLS 3804 AES256-GCM-SHA384:AES256-SHA256:

Authority Proxy
Function AES128-SHA:CAMELLIA128-SHA:
18
Process
CTIManager TCP / TLS 2749 ECDHE-RSA-AES256-GCM-SHA384:

Cisco Trust TCP / TLS 2445 AES256-GCM-SHA384:AES256-SHA256:

Verification Service
Cisco Intercluster TCP / TLS 7501 ECDHE-RSA-AES256-GCM-SHA384:

Lookup Service
ECDHE-RSA-AES256-SHA:AES256-GCM-SHA384:
CAMELLIA256-SHA:
Secure TCP / TLS 6971, 6972 ECDHE-RSA-AES256-GCM-SHA384:

Configuration
download DHE-RSA-CAMELLIA256-SHA:
(HAPROXY) AES256-GCM-SHA384:AES256-SHA256:
ECDHE-ECDSA-DES-CBC3-SHA:
19
Process
Authenticated TCP / TLS 9443 ECDHE-RSA-AES256-GCM-SHA384:

Contact Search
Supported Ciphers for SSH

The following ciphers are supported by SSH:
Table 13: Cipher Support for SSH Ciphers
Service Ciphers/Algorithms
SSH Server • Ciphers

aes128-ctr
aes192-ctr
aes256-ctr
aes128-gcm@openssh.com
• MAC algorithms:
hmac-sha2-256
hmac-sha1
• Kex algorithms:
ecdh-sha2-nistp521
ecdh-sha2-nistp384
ecdh-sha2-nistp256
diffie-hellman-group14-sha1
diffie-hellman-group-exchange-sha256
20
SSH Client • Ciphers:

aes128-ctr
aes192-ctr
aes256-ctr
• MAC algorithms:
hmac-sha2-256
hmac-sha1
• Kex algorithms:
ecdh-sha2-nistp521
ecdh-sha2-nistp384
ecdh-sha2-nistp256
DRS Client • Ciphers:
aes256-ctr
aes256-cbc
aes128-ctr
aes128-cbc
aes256-ctr
blowfish-cbc
• MAC algorithms:
hmac-md5
hmac-sha2-256
hmac-sha1
hmac-sha1-96
hmac-md5-96
• Kex algorithms:
ecdh-sha2-nistp256
ecdh-sha2-nistp384
ecdh-sha2-nistp521
21
SFTP client • Ciphers:

aes128-ctr
aes192-ctr
aes256-ctr
• MAC algorithms:
hmac-sha2-256
hmac-sha1
• Kex algorithms:
ecdh-sha2-nistp521
ecdh-sha2-nistp384
End Users (Linux OS) SHA-256 – Hashing (salted)
DRS Backups / RTMT SFTPs AES-128 – Encryption
Application Users AES-256 – Encryption
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
22
• 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.
LDAP Directory Servers Supported

IM and Presence Service integrates with these LDAP directory servers:
• Microsoft Active Directory 2000, 2003, 2008, 2012, 2016, and 2019—The minimum 12.5(x) release for AD2019 is 12.5(1)SU2.
For 11.5.x, the minimum supported version for AD2019 is 11.5(1)SU7.
• Microsoft Lightweight Directory Services 2019 (Minimum supported release is 11.5(1)SU7)
• Netscape Directory Server
• Sun ONE Directory Server 5.2
• OpenLDAP
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
Third-Party System Single Enterprise Network* Business to Business

(Intradomain or Interdomain Federation) (Interdomain Federation)
Direct Federation via Expressway via Expressway
Skype for Business 2015 Y Not supported Y (Traffic Classification)

(on-premise)
Office 365 (uses a Not applicable Not applicable Y (Traffic Classification)

cloud-hosted Skype for
Business)
* 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:
23
• IBM Sametime
• Cisco Webex Messenger
• IM and Presence Service Release 9.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:
• Release 10.x
• 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
Component Install Compatible Version
• Service Packs for Windows Server 2008 (SP2)

• Service Packs for Windows Server 2012 (Standard)
• Windows Server 2016
Windows Server
• Windows Server 2019—With 11.x releases, the minimum IM and Presence Service Release
is 11.5(1)SU7. With 12.x releases, the minimum IM and Presence Service Release is
12.5(1)SU2.
Microsoft Exchange Server Service Packs for Microsoft Exchange 2010 (SP1)
2010
Microsoft Exchange Server Service Packs for Microsoft Exchange 2013 (SP1)
2013
Microsoft Exchange Server Microsoft Exchange 2016

2016
Microsoft Exchange Server Microsoft Exchange 2019

2019
24
Component Install Compatible Version
Refer to your Microsoft documentation for details on deploying a hosted Office 365 server.
Note As of October 2020, Microsoft is changing the authentication mechanism that is supported
Microsoft Office 365 by Exchange Online to use OAuth-based authentication only. After the change, if you
want to deploy calendar integration between the IM and Presence Service and Office
365, you will need to upgrade the IM and Presence Service to Release 12.5(1)SU2. This
change will not affect integration with an on-premises Exchange server.
• Active Directory 2008 with Windows Server 2008 (SP2)

• Active Directory 2012 with Windows Server 2012
Active Directory • Active Directory 2016 with Windows Server 2016
Note User names configured in Active Directory must be identical to those names defined in
Unified Communications Manager.
One or the other of these are required to generate the certificates.

A Third-Party Certificate OR
Note Microsoft Exchange integration with IM and Presence Service supports certificates
Certificate Server
using RSA 1024 or 2048-bit keys and SHA1 and SHA256 signature algorithms.
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

Process
Cisco SIP Proxy TCP / TLS 5061 ECDHE-RSA-AES256-GCM-SHA384:

AES128-GCM-SHA256:
AES128-SHA256:
DES-CBC3-SHA
25
Process

AES256-GCM-SHA384:
CAMELLIA256-SHA:
DES-CBC3-SHA

DES-CBC3-SHA
26
Process
Cisco Tomcat TCP / TLS 8443, 443 ECDHE-RSA-AES256-GCM-SHA384:

DHE-RSA-AES256-SHA:
DHE-RSA-AES128-SHA:
AES128-GCM-SHA256:
CAMELLIA128-SHA:
EDH-RSA-DES-CBC3-SHA:
DES-CBC3-SHA
Cisco XCP XMPP TCP /TLS 5269 ECDHE-RSA-AES256-GCM-SHA384:

Federation
Connection Manager ECDHE-ECDSA-AES256-SHA384:
DES-CBC3-SHA
27
Process
Cisco XCP Client TCP / TLS 5222 ECDHE-RSA-AES256-GCM-SHA384:

Connection Manager
DES-CBC3-SHA
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 2010 or 2013 Release 4.x, Standard Edition or Enterprise Edition
• Lync Server Control Panel
• Lync Server Deployment Wizard
• Lync Server Logging Tool
28
• Lync Server Management Shell
• Lync Server Topology Builder
• Microsoft 2010 Lync Client, or, 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.
29
© 2021 Cisco Systems, Inc. All rights reserved.
Americas Headquarters Asia Pacific Headquarters Europe Headquarters
Cisco Systems, Inc. CiscoSystems(USA)Pte.Ltd. CiscoSystemsInternationalBV
San Jose, CA 95134-1706 Singapore Amsterdam,TheNetherlands
USA
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.

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

Uploaded by

Copyright:

Available Formats

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

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

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

Uploaded by

Copyright:

Available Formats

Compatibility Matrix for Cisco Unified Communications Manager and the

IM and Presence Service, Release 12.5(X)

Compatibility Matrix for Cisco Unified Communications

June 19, 2019 Added OpenJDK version for 12.5(1)SU1 release.

Updated for 12.5(1)SU1. Changed title to 12.5(x)

February 20, 2020 Updated LDAPv3 Compliant Directories.

March 09, 2020 Updated Cisco Endpoint Support section.

March 11, 2020 Added Cisco Headsets to Endpoint Support.

April 06, 2020 Removed non-supported Cisco endpoints.

May 12, 2020 Added JTAPI Support information.

July 8, 2020 Updated SSL Connections and SSH Clients.

August 13, 2020 Updated version support for 12.5(1)SU3.

October 19, 2020 Corrected list of Webex endpoints.

November 18, 2020 Corrected dates.

December 13, 2020 Renamed Cisco Webex Teams to Cisco Webex.

February 22, 2021 Initial release version for 12.5(1)SU4.

March 25, 2021 Fixed the 7941 G Series EOS URL.

August 03, 2021 Initial release version for 12.5(1)SU5.

Purpose of this Document

Supported Upgrade and Migration Paths

Source Destination Supported Upgrade Method Version Switching*

Cisco Unified Communications Manager Upgrade Paths

Unified CM 6.1(5), 12.5(x) PCD Migration** Version switching

IM and Presence Service Upgrade Paths

Cisco Unified IM and Presence PCD Migration** Version switching

Required COP Files

Table 2: Required COP Files

From To COP Files

Cisco Unified Communications Manger Upgrades

Unified CM 8.6(x), 12.5(x) Required COP files:

Optional COP files:

Unified CM 10.5(x), 12.5(x) Direct Refresh upgrade; no COP file required.

Unified CM 12.0(1) 12.5(x) PCD Migrations require a COP file:

Unified CM 12.5(x) 12.5(y) Direct Standard upgrade; no COP file required.

IM and Presence Service Upgrades

CUP 8.5(4) through 12.5(x) Required COP files:

9.1(x) 12.5(x) Requires following COP File:

10.5(x), 11.x, 12.x 12.5(x) No COP files required

For this Release... The Following Versions are Supported...

12.5(1) • Cisco Unified Communications Manager 12.5.1.10000-22

12.5(1)SU1 • Cisco Unified Communications Manager 12.5.1.11900-146

12.5(1)SU2 • Cisco Unified Communications Manager 12.5.1.12900-115

12.5(1)SU3 • Cisco Unified Communications Manager 12.5.1.13900-152

12.5(1)SU4 • Cisco Unified Communications Manager 12.5.1.14900-63

12.5(1)SU5 • Cisco Unified Communications Manager 12.5.1.15900-66

Version Compatibility Between Unified CM and the IM and Presence Service

Deployment Type Release Mismatch Description

Unified Communications Manager Compatibility Information

Note This compatibility information isn't applicable for Cisco Webex.

Table 4: Recommended Release Requirements for Android Push Notifications Support

Unified Communications Expressway Version Unified Communications On-Premises Deployments

IM and Presence Stream Features/Services Advertisement Compatibility Recommendations

Mixed Versions IM and Presence Expected Status of FCM Flag on Comment

Any 11.5(1)SU with OFF Android Push (FCM) NOT supported.

11.5(1)SU9 (and higher) or 12.5(1)SU4 ON Android push (FCM) supported on version

Cisco Endpoint Support

Supported Cisco Endpoints

Table 6: Supported Cisco Endpoints

Device Series Device Model