How To Cloud Register Dx80

Supported Upgrade and Migration Paths with COP Files

The post-obit tabular array highlights supported upgrade paths to upgrade to Release xiv of Cisco Unified Communications Manager and the IM and Presence Service. Information technology as well lists the upgrade paths that crave COP files. You must install COP files on each node before you begin an upgrade using the Cisco Unified Bone Admin interface, or before you begin an upgrade or migration using the Prime Collaboration Deployment (PCD) tool. If you lot are using PCD, you can perform a bulk installation of the COP files before yous begin the upgrade.

Note

Unless indicated otherwise, each release category includes the SU releases inside that category.

You can download COP files for Cisco Unified Communications Manager and the IM and Presence Service at https://software.cisco.com/download/domicile/268439621. After y'all select the destination version for the upgrade, cull Unified Communications Manager Utilities to see the list of COP files.

Note

Although information technology is not mandatory, we strongly recommend that you run the Upgrade Readiness COP file prior to the upgrade in club to maximize upgrade success. Cisco TAC may require that you run this COP file to provide effective technical support.

Table 1. Supported Upgrade Paths and COP Files for Cisco Unified Communications Manager and the IM and Presence Service
Source	Destination	Mechanism		Pre-requisites	Version Switching* (Source to Destination and Vice Versa)
10.0	14	PCD 14 Migration Chore (V2V)		No COP file required.	Not supported
10.5	fourteen	PCD 14 Migration Task (V2V)		Run pre-upgrade-check COP file.	Not supported
10.5	fourteen	Fresh Install with Data Import (V2V)		Run pre-upgrade-bank check COP file. ciscocm.DataExport_v1.0.cop.sgn	Not supported
11.0	14	PCD fourteen Migration Chore (V2V)		Run pre-upgrade-check COP file.	Not supported
11.0	14	Fresh Install with Data Import (V2V)		Run pre-upgrade-cheque COP file. ciscocm.DataExport_v1.0.cop.sgn	Not supported
11.5	xiv	Straight Refresh Upgrade	Via Os Admin or CLI	Run pre-upgrade-cheque COP file. For Unified CM, required COP file is: cop ciscocm.enable-sha512sum-2021-signing-central-v1.0.cop.sgn if source is older than 11.v.1.22900-28. For IM and Presence Service, required COP file is: ciscocm.enable-sha512sum-2021-signing-key-v1.0.cop.sgn if source is older than 11.5.one.22900-6. Use the following COP file to upgrade IM and Presence Service from release xi.v.1.18900-fifteen to 14: ciscocm.V11.five.1_CSCvv25961_add_diffie_C0085-1.cop.sgn.	Supported
		Direct Refresh Upgrade	Via PCD Upgrade Task	Run pre-upgrade-check COP file. For Unified CM, required COP file is: cop ciscocm.enable-sha512sum-2021-signing-key-v1.0.cop.sgn if source is older than 11.v.1.22900-28. For IM and Presence Service, required COP file is: ciscocm.enable-sha512sum-2021-signing-key-v1.0.cop.sgn if source is older than 11.5.1.22900-half-dozen. Utilize the following COP file to upgrade IM and Presence Service from release 11.five.i.18900-15 to 14: ciscocm.V11.five.1_CSCvv25961_add_diffie_C0085-1.cop.sgn.	Supported
		PCD 14 Migration Task (V2V)		Run pre-upgrade-bank check COP file.	Non supported
		Fresh Install with Data Import (V2V)		Run pre-upgrade-check COP file. ciscocm.DataExport_v1.0.cop.sgn	Non supported
12.0	14	Directly Refresh Upgrade	Via Os Admin or CLI	Run pre-upgrade-bank check COP file. For Unified CM, required COP file is: ciscocm.enable-sha512sum-2021-signing-key-v1.0.cop.sgn if source is older than 12.0.1.24900-xix. For IM and Presence Service, required COP file is: ciscocm.enable-sha512sum-2021-signing-primal-v1.0.cop.sgn if source is older than 12.0.ane.21000-34.	Supported
		Direct Refresh Upgrade	Via PCD Upgrade Task	Run pre-upgrade-check COP file. For Unified CM, required COP file is: ciscocm.enable-sha512sum-2021-signing-key-v1.0.cop.sgn if source is older than 12.0.1.24900-19. For IM and Presence Service, required COP file is: ciscocm.enable-sha512sum-2021-signing-key-v1.0.cop.sgn if source is older than 12.0.1.21000-34.	Supported
		PCD 14 Migration Task (V2V)		Run pre-upgrade-check COP file.	Not supported
		Fresh Install with Information Import (V2V)		Run pre-upgrade-check COP file. ciscocm.DataExport_v1.0.cop.sgn	Not supported
12.5	14	Direct Standard Upgrade (simple upgrades)	Via Os Admin or CLI	Run pre-upgrade-bank check COP file. For Unified CM, required COP file is: ciscocm.enable-sha512sum-2021-signing-primal-v1.0.cop.sgn if source is older than 12.v.1.14900-63. For IM and Presence Service, required COP file is: ciscocm.enable-sha512sum-2021-signing-primal-v1.0.cop.sgn if source is older than 12.five.1.14900-four.	Supported
		Direct Standard Upgrade	Via PCD Upgrade Chore	Run pre-upgrade-check COP file. For Unified CM, required COP file is: ciscocm.enable-sha512sum-2021-signing-cardinal-v1.0.cop.sgn if source is older than 12.5.1.14900-63. For IM and Presence Service, required COP file is: ciscocm.enable-sha512sum-2021-signing-key-v1.0.cop.sgn if source is older than 12.five.1.14900-4.	Supported
		PCD 14 Migration Task (V2V)		Run pre-upgrade-check COP file.	Not supported
		Fresh Install with Data Import (V2V)		Run pre-upgrade-check COP file. ciscocm.DataExport_v1.0.cop.sgn	Not supported

* 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 directly upgrades, merely not with migrations.

Annotation

PCD Upgrades and Migrations—Use Cisco Prime Collaboration Deployment Release 14 for all PCD tasks.

Unified Communications Manager Compatibility Information

Cisco Collaboration Organisation Applications

This release of Cisco Unified Communications Manager and the IM and Presence Service is a role of the Cisco Collaboration Systems Release 14 and is compatible with the other Cisco Collaboration applications and versions in Cisco Collaboration Systems Release 14.

For a full listing of Cisco Collaboration applications that are a part of Cisco Collaboration Systems Release xiv, and the supported versions for each, run across 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 button Notification characteristic is supported only on the post-obit software versions:

Unified Communications Manager 12.5(ane)SU3
IM and Presence Service 12.5(1)SU3
Cisco Jabber 12.9.1
Cisco Expressway X12.half-dozen.2

Note

This compatibility information isn't applicable for Cisco Webex.

Table iii. Recommended Release Requirements for Android Push Notifications Support
Unified Communications Manager and IM and Presence Service Version	Freeway Version	Unified Communications Mobile and Remote Admission	On-Premises Deployments
All clusters on: 11.5(ane)SU8 or earlier 12.v(ane)SU2 or before	X12.6.2	Android Push Notification is not supported	Android Push Notification is non supported
All clusters on: 12.5(1)SU3	X12.6.2	Enable Android Push Notification using the CLI xConfiguration XCP Config FcmService: On on Expressway for messaging merely	Android Push Notification is supported
Cluster with mixed versions (11.5(1)SU8 or earlier, OR 12.v(1)SU2 or earlier, AND 12.5(1)SU3)	X12.6.2	Android Push button Notification for Messaging is non supported VOIP is supported on Release 12.5(1)SU3	Android Push button Notification is supported with Release 12.v(1)SU3

IM and Presence Stream Features/Services Advertisement Compatibility Recommendations

IM and Presence Service supports the advertizing of XMPP stream features/services to the clients connecting over Cisco Expressway's Mobile and Remote Access.

Depending on your electric current IM and Presence Service version mix, you may demand 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 button Notification Service (APNS) is not affected past the FCM service flag status.

Table four. Solution Matrix from the Perspective of Superhighway CLI Enable/Disable Command for Android Push Notifications (FCM)
Mixed Versions IM and Presence Clusters	Expected Status of FCM Flag on Expressway X12.7	Comment
Whatsoever eleven.v(ane)SU with 12.five(i)SU2 and lower	OFF	Android Push (FCM) Non supported.
xi.5(1)SU8 (and lower) or 12.5(i)SU2 (and lower) with 12.five(1)SU3	OFF	Android push button (FCM) NOT supported
xi.5(1)SU8 (and lower) or 12.5(one)SU2 (and lower) with 12.v(1)SU4 (and higher)	OFF	Android button (FCM) supported on 12.five(one)SU4 (or newer) versions
11.5(one)SU9 (and college) or 12.5(ane)SU4 (and higher) with 12.5(one)SU3	ON	Android push (FCM) supported on version 12.5(one)SU3 and higher
eleven.5(one)SU9 (and higher) with 12.5(1)SU4 (and college)	Flag non required (Motorway 12.7 relies fully on the new discovery machinery)	Android push (FCM) supported on 12.5(1)SU4 (or newer) versions

Cisco Endpoint Support

All end of Life and Stop 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 Auction (EOS), or Finish of Software Maintenance, click the EOS link to view support details.

Annotation

Unless they are specified in the "Deprecated Phone Models" list, telephone models that are Finish of Software Maintenance will go on to be supported on the latest Unified Communications Manager releases. However, they will non have advantage of whatever new Unified Communications Manager or firmware features associated with that release.

Table 5. Supported Cisco Endpoints
Device Serial	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 Telephone 7800 Series	Cisco IP Phone 7811 Cisco IP Phone 7821 Cisco IP Phone 7841 Cisco IP Phone 7861 Cisco IP Conference Telephone 7832
Cisco Unified IP Telephone 7900 Series	Cisco Unified IP Phone Expansion Module 7915—EOS Notice Cisco Unified IP Telephone Expansion Module 7916—EOS Notice Cisco Unified IP Phone 7942G—EOS Notice Cisco Unified IP Phone 7945G—EOS Detect Cisco Unified IP Phone 7962G—EOS Notice Cisco Unified IP Phone 7965G—EOS Notice Cisco Unified IP Phone 7975G—EOS Detect
Cisco IP Phone 8800 Serial	Cisco IP Phone 8811, 8831, 8841, 8845, 8851, 8851NR, 8861, 8865, 8865NR Cisco Wireless IP Telephone 8821, 8821-EX Cisco Unified IP Conference Telephone 8831—EOS Notice Cisco IP Conference Telephone 8832
Cisco Unified IP Telephone 8900 Series	Cisco Unified IP Phone 8945—EOS Observe Cisco Unified IP Telephone 8961—EOS Observe
Cisco Unified IP Phone 9900 Series	Cisco Unified IP Phone 9951—EOS Notice Cisco Unified IP Telephone 9971—EOS Discover
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
Webex	Webex App Webex Room Phone Webex Desk Camera Webex Desk Webex Desk-bound Pro Webex Desk Limited Edition Webex Share—EOS Notice Webex Board 55, 55s, 70, 70s, 85, 85s Webex Room Panorama Webex Room seventy Panorama Webex Room lxx Panorama Upgrade Webex Room seventy Webex Room 70 G2 Webex Room 55 Webex Room 55 Dual Webex Room Kit Pro Webex Room Kit Plus Webex Room Kit Webex Room Kit Mini Webex Room USB
Webex Meetings	Webex Meetings for iPad and iPhone Webex Meetings for Android
Cisco Analog Telephony Adapters	Cisco ATA 190 Series Analog Telephone Adapters—EOS/EOL Observe Cisco ATA 191 Series Analog Phone Adapters
Cisco DX Serial	Cisco Webex DX70—EOS Discover Cisco Webex DX80—EOS Observe Cisco DX650—EOS Notice
Cisco TelePresence IX5000	Cisco TelePresence IX5000
Cisco TelePresence EX Serial	Cisco TelePresence System EX90—EOS Observe
Cisco TelePresence MX Series	Cisco TelePresence MX200 G2—EOS Discover 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 Observe Cisco TelePresence SX80—EOS Discover

For a list of firmware versions that are used for each Cisco endpoint, run across the Cisco Collaboration Systems Release Compatibility Matrix at http://www.cisco.com/c/en/usa/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 tabular array lists Cisco endpoints that take reached the End of Support date, but which are not withal deprecated. Different deprecated endpoints, you can still deploy these endpoints in the latest release, but they are not supported actively, are not tested, and may non work.

Click the links to view support announcements for each endpoint.

For data on all of the End of Back up and End-of-Life products, see https://www.cisco.com/c/en_ca/products/eos-eol-listing.html.

Table 6. 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 Telephone Expansion Module 7925G, 7925G-EX, 7926G Cisco Unified IP Conference Station 7935, 7936, 7937G Cisco TelePresence EX60 Cisco TelePresence MX200-G1, MX200-G2, MX300-G1, MX300-G2 Cisco TelePresence 500-32, 500-37, m MXP, 1100, 1300-65, 1300-47, 3000 Series

Deprecated Telephone Models

The following tabular array lists all the telephone 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 telephone model that was first deprecated in Release 11.5(1) is deprecated for all later releases, including all 12.x releases.

If y'all are upgrading to the current release of Unified Communications Managing director and you have any of these phone models deployed, the phone will not work after the upgrade.

Table 7. Deprecated Phone Models for this Release
Deprecated Telephone Models for this Release	First Deprecated as of Unified CM...
Cisco Unified Wireless IP Phone 7921 Cisco Unified IP Telephone 7970 Cisco Unified IP Phone 7971	12.0(ane) and later on releases
Cisco IP Phone 12 S Cisco IP Phone 12 SP Cisco IP Phone 12 SP+ Cisco IP Phone 30 SP+ Cisco IP Phone thirty VIP Cisco Unified IP Phone 7902G Cisco Unified IP Phone 7905G Cisco Unified IP Phone 7910 Cisco Unified IP Phone 7910G Cisco Unified IP Telephone 7910+SW Cisco Unified IP Phone 7910G+SW Cisco Unified IP Phone 7912G Cisco Unified Wireless IP Phone 7920 Cisco Unified IP Conference Station 7935	xi.v(one) and later releases

For boosted information refer to the Field Observe: Cisco Unified Communications Manager Release xiv does not support some deprecated phone models at https://world wide web.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/trouble/14_0_1/fieldNotices/cucm_b_deprecated-phones-14.html.

Upgrades that Involve Deprecated Phones

If yous are using whatsoever of these phones on an earlier release and you desire to upgrade to this release, do the following:

Confirm whether the phones in your network will exist supported in this release.
Identify any not-supported phones.
For whatsoever non-supported phones, ability downwardly the phone and disconnect the phone from the network.
Provision a supported phone for the phone user. You can use the post-obit methods to migrate from older model to newer model phones:
- Native Telephone Migration using IVR and Telephone Services
- Migration FX tool
Once all the phones in your network are supported by this release, upgrade your system.

Note

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

Licensing

You do non demand to buy 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 Managing director 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. Come across the following table for virtualization requirements.

Tabular array 8. Virtualization Requirements
Virtualization Requirements for...	For information, become to...
Unified Communications Manager	For information well-nigh Unified Communications Manager virtualization requirements, go to https://world wide web.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-cisco-unified-communications-director.html.
IM and Presence Service	For data about the IM and Presence Service virtualization requirements, get to https://www.cisco.com/c/dam/en/u.s./td/docs/voice_ip_comm/uc_system/virtualization/virtualization-cisco-ucm-im-presence.html.
Cisco Business Edition Deployments	For information on the virtualization requirements for Unified Communications Manager in a collaboration solution deployment such every bit 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

The post-obit LDAP directories are supported:

Microsoft Active Directory 2012 R1/ R2
Microsoft Active Directory 2016
Microsoft Active Directory 2019—Supported for 11.5(ane)SU7, 12.v(ane)SU2, and later releases
Microsoft Lightweight Directory Services 2012 R1/ R2
Microsoft Lightweight Directory Services 2019—Supported for 11.5(1)SU7, 12.v(ane)SU2, and later releases
Oracle Directory Services Enterprise Edition 11gR1 (11.1.ane.7.x or newer)
Oracle Unified Directory 12cPS3 (12.2.1.3.0)
Open LDAP 2.4.44 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 exist used with DirSync. (The supportedcontrol aspect may return the pagecontrolsupport and persistentcontrolsupport sub attributes, if configured.)

Supported Web Browsers

The post-obit web browsers are supported:

Firefox with Windows 10 (64 chip)
Chrome with Windows ten (64 bit)
Internet Explorer 11 with Windows ten (64 bit)
Internet Explorer 11 with Windows seven (64 bit)
Microsoft Edge browser with Windows 10 (32 bit/64 bit)
Safari with MacOS (ten.ten)

Note

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

SFTP Server Back up

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 9. SFTP Server Support

SFTP Server

Support Clarification

SFTP Server on Cisco Prime Collaboration Deployment

This server is the but SFTP server that is provided and tested past Cisco, and fully supported by Cisco TAC.

Version compatibility depends on your version of Emergency Responder and Cisco Prime Collaboration Deployment. See the Cisco Prime number Collaboration Deployment Administration Guide before you upgrade its version (SFTP) or Emergency Responder to ensure that the versions are compatible.

SFTP Server from a Engineering science Partner

These servers are third political party provided and tertiary political party tested. Version compatibility depends on the third-political party test. See the Technology Partner page if you lot upgrade their SFTP production and/or upgrade Unified Communications Manager for which versions are uniform:

https://market place.cisco.com

SFTP Server from another Tertiary Party

These servers are third party provided and are not officially supported by Cisco TAC.

Version compatibility is on a all-time effort footing 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, utilize 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^® Agile Directory^® Federation Services two.0
Microsoft Azure Advertizing
OpenAM
PingFederate^®
F5 Big-IP
Okta

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

API and Secure Connectedness Packages

The following table provides information on the API Evolution and secure connection packages that are supported with this release.

Table ten. Supported Packages
Package Type	Details
API Development	Cisco Unified Communications Managing director and the IM and Presence Service support OpenJDK for awarding development. Release 14 use OpenJDK version 1.viii.0.262. Release 14SU1 use OpenJDK version 1.8.0.262.b10-0.
SSL Connections	For Secure Sockets Layer (SSL) connections, these releases support either OpenSSL or Cisco SSL. You tin utilize either of the following for your corresponding versions: Release 14 uses OpenSSL 1.0.2u.six.ii.374 and CiscoSSL 1.0.2u.6.2.374. Release 14SU1 uses OpenSSL one.0.2y.half-dozen.2.403 and CiscoSSL 1.0.2y.6.2.403.
SSH Clients	Release 14 supports OpenSSH client version 7.five.14i.1.v.xviii for SSH connections. Release 14SU1 supports OpenSSH client version 7.five.14i.one.5.eighteen for SSH connections.

Note

For boosted information on the packages that are installed on your system, run the show packages active CLI command. Run into the Command Line Interface Reference Guide for Cisco Unified Communications Solutions for more data about this command and its options.

TLS 1.2 Support

Unified Communications Manager and the IM and Presence Service back up the use of TLS 1.2. For detailed information on TLS one.ii support, see TLS one.ii Compatibility Matrix for Cisco Collaboration Products at:

https://world wide web.cisco.com/c/en/us/td/docs/voice_ip_comm/uc_system/unified/communications/arrangement/Compatibility/TLS/TLS1-two-Compatibility-Matrix.html.

Supported Ciphers for Unified Communications Director

The following ciphers are supported by Unified Communications Manager:

Table xi. Unified Communications Manager Cipher Support for TLS Ciphers
Application / Process	Protocol	Port	Supported Ciphers
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: ECDHE-RSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: AES128-GCM-SHA256: AES128-SHA256:AES128-SHA: CAMELLIA128-SHA`
DRS	TCP / TLS	4040	`ECDHE-RSA-AES256-GCM-SHA384: ECDHE-RSA-AES256-SHA384: ECDHE-RSA-AES256-SHA: DHE-RSA-CAMELLIA256-SHA: AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: ECDHE-RSA-AES128-GCM-SHA256: ECDHE-RSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: DHE-RSA-CAMELLIA128-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA`
Cisco Tomcat	TCP / TLS	8443 / 443	ECDHE-RSA-AES256-GCM-SHA384: ECDHE-RSA-AES256-SHA384: ECDHE-RSA-AES256-SHA: DHE-RSA-AES256-GCM-SHA384: DHE-RSA-AES256-SHA256: DHE-RSA-AES256-SHA: DHE-RSA-CAMELLIA256-SHA: AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: ECDHE-RSA-AES128-GCM-SHA256: ECDHE-RSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: DHE-RSA-AES128-GCM-SHA256: DHE-RSA-AES128-SHA256: DHE-RSA-AES128-SHA: DHE-RSA-CAMELLIA128-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-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-AES128-GCM-SHA256: ECDHE-ECDSA-AES128-SHA256: ECDHE-ECDSA-AES128-SHA: ECDHE-ECDSA-DES-CBC3-SHA
Cisco CallManager	TCP / TLS	5061	`ECDHE-RSA-AES256-GCM-SHA384: ECDHE-ECDSA-AES256-GCM-SHA384 ECDHE-RSA-AES256-SHA384: ECDHE-ECDSA-AES256-SHA384: ECDHE-RSA-AES256-SHA ECDHE-ECDSA-AES256-SHA: AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA ECDHE-ECDSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-GCM-SHA256: ECDHE-RSA-AES128-SHA256 ECDHE-ECDSA-AES128-SHA256: ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA: ECDHE-ECDSA-DES-CBC3-SHA`
Cisco CTL Provider	TCP / TLS	2444	`AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA:`
Cisco Certificate Authority Proxy Function	TCP / TLS	3804	`AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA:`
CTIManager	TCP / TLS	2749	`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: ECDHE-RSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA`
Cisco Trust Verification Service	TCP / TLS	2445	`AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA`
Cisco Intercluster Lookup Service	TCP / TLS	7501	`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: ECDHE-RSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA:`
Secure Configuration download (HAPROXY)	TCP / TLS	6971, 6972	`ECDHE-RSA-AES256-GCM-SHA384: ECDHE-RSA-AES256-SHA384: ECDHE-RSA-AES256-SHA: DHE-RSA-CAMELLIA256-SHA: AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: ECDHE-RSA-AES128-GCM-SHA256: ECDHE-RSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: DHE-RSA-CAMELLIA128-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA: ECDHE-ECDSA-AES256-GCM-SHA384: ECDHE-ECDSA-AES256-SHA384: ECDHE-ECDSA-AES256-SHA: ECDHE-ECDSA-AES128-SHA256: ECDHE-ECDSA-AES128-SHA: ECDHE-ECDSA-DES-CBC3-SHA:`
Authenticated Contact Search	TCP / TLS	9443	`ECDHE-RSA-AES256-GCM-SHA384: ECDHE-RSA-AES256-SHA384: ECDHE-RSA-AES256-SHA: DHE-RSA-CAMELLIA256-SHA: AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: ECDHE-RSA-AES128-GCM-SHA256: ECDHE-RSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: DHE-RSA-CAMELLIA128-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA: ECDHE-ECDSA-AES256-GCM-SHA384: ECDHE-ECDSA-AES256-SHA384: ECDHE-ECDSA-AES256-SHA: ECDHE-ECDSA-AES128-SHA256: ECDHE-ECDSA-AES128-SHA: ECDHE-ECDSA-DES-CBC3-SHA:`

Supported Ciphers for SSH

The following ciphers are supported past SSH:

Tabular array 12. Zip Back up for SSH Ciphers
Service	Ciphers/Algorithms
SSH Server	Ciphers `aes128-ctr aes192-ctr aes256-ctr aes128-gcm@openssh.com aes256-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-group1-sha1 diffie-hellman-group-commutation-sha256 diffie-hellman-group-exchange-sha1`
SSH Client	Ciphers: `aes128-ctr aes192-ctr aes256-ctr aes128-gcm@openssh.com aes256-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-group1-sha1 diffie-hellman-grouping-exchange-sha256 diffie-hellman-group-exchange-sha1`
DRS Customer	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 diffie-hellman-group14-sha1 diffie-hellman-grouping-exchange-sha256 diffie-hellman-group-exchange-sha1 diffie-hellman-group1-sha1`
SFTP customer	Ciphers: `aes128-ctr aes192-ctr aes256-ctr` MAC algorithms: `hmac-sha2-256 hmac-sha1` Kex algorithms: `ecdh-sha2-nistp521 ecdh-sha2-nistp384 diffie-hellman-group14-sha1 diffie-hellman-group1-sha1 diffie-hellman-group-exchange-sha256 diffie-hellman-group-exchange-sha1`
End Users (Linux OS)	`SHA-512 – Hashing (salted)`
DRS Backups / RTMT SFTPs	`AES-128 – Encryption`
Application Users	`AES-256 – Encryption`

IM and Presence Service Compatibility Information

Platform Compatibility

The IM and Presence Service shares a platform with Unified Communications Managing director. 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 data on the post-obit items:

Secure Connections
Virtualization Requirements
Supported Web Browsers

External Database Support

Many IM and Presence Service features such as Persistent Conversation, High Availability for Persistent Chat, Message Archiver, and Managed File Transfer require that y'all deploy an external database. For information on database back up, meet the Database Setup Guide for the IM and Presence Service.

Supported LDAP Directories

The following LDAP directories are supported:

Microsoft Active Directory 2012 R1/ R2
Microsoft Active Directory 2016
Microsoft Active Directory 2019—Supported for 11.5(1)SU7, 12.five(1)SU2, and later releases
Microsoft Lightweight Directory Services 2012 R1/ R2
Microsoft Lightweight Directory Services 2019—Supported for 11.five(1)SU7, 12.5(1)SU2, and later releases
Oracle Directory Services Enterprise Edition 11gR1 (11.1.1.seven.ten or newer)
Oracle Unified Directory 12cPS3 (12.two.1.three.0)
Open up LDAP 2.4.44 or later
Other LDAPv3 Compliant Directories—Unified Communications Manager uses standard LDAPv3 for accessing the user'southward data. Ensure that the supportedcontrol attribute is configured in the LDAPv3 compliant directory servers to exist used with DirSync. (The supportedcontrol attribute may return the pagecontrolsupport and persistentcontrolsupport 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 tabular array lists supported SIP Controlled and SIP Open up Federation integrations:

Tabular array 13. Supported SIP Controlled and Open Federations
Third-Party Organization	Single Enterprise Network* (Intradomain or Interdomain Federation)		Business to Business (Interdomain Federation)
Third-Party Organization	Direct Federation	via Motorway	via Pike
Skype for Business 2015 (on-premise)	Y	Non supported	Y (Traffic Nomenclature)
Office 365 (uses a deject-hosted Skype for Business)	Not applicative	Not applicative	Y (Traffic Classification)

* The Unmarried Enterprise Network tin be partitioned intradomain federation or interdomain federation as the support values are the aforementioned 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:

IBM Sametime
Cisco Webex Messenger
IM and Presence Service Release 9.x and upwardly
Any other XMPP-compliant system

Intercluster Peering Back up

This release of the IM and Presence Service supports intercluster peering with the following IM and Presence Service releases:

Release 10.x
Release eleven.x
Release 12.x

Agenda 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. Come across the table below for support information:

Table 14. Support Information for Calendar Integration

Component

Install Compatible Version

Windows Server

Windows Server 2016
Windows Server 2019—With 11.10 releases, the minimum IM and Presence Service Release is xi.5(1)SU7. With 12.ten releases, the minimum IM and Presence Service Release is 12.v(1)SU2.

Microsoft Exchange Server 2016

Microsoft Exchange 2016

Microsoft Substitution Server 2019

Microsoft Exchange 2019

Microsoft Office 365

See your Microsoft documentation for details on deploying a hosted Office 365 server.

Notation

Every bit of October 2020, Microsoft is changing the authentication machinery that is supported by Commutation Online to utilise OAuth-based hallmark only. After the change, if yous desire to deploy calendar integration betwixt 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 alter volition not affect integration with an on-premises Substitution server.

Active Directory

Active Directory 2012 with Windows Server 2012
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.

A 3rd-Political party Certificate OR Certificate Server

One or the other of these is required to generate the certificates.

Note

Microsoft Exchange integration with IM and Presence Service supports certificates using RSA 1024 or 2048 flake keys and SHA1 and SHA256 signature algorithms.

Supported Ciphers for the IM and Presence Service

IM and Presence Service supports the post-obit ciphers:

Table fifteen. Unified Communications Manager IM & Presence Cipher Support for TLS Ciphers
Application / Process	Protocol	Port	Supported Ciphers
Cisco SIP Proxy	TCP / TLS	5061	ECDHE-RSA-AES256-GCM-SHA384: ECDHE-ECDSA-AES256-GCM-SHA384: ECDHE-RSA-AES256-SHA384: ECDHE-ECDSA-AES256-SHA384: ECDHE-RSA-AES256-SHA: ECDHE-ECDSA-AES256-SHA: AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: ECDHE-RSA-AES128-GCM-SHA256: ECDHE-ECDSA-AES128-GCM-SHA256: ECDHE-RSA-AES128-SHA256: ECDHE-ECDSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: ECDHE-ECDSA-AES128-SHA: AES128-GCM-SHA256: AES128-SHA256: AES128-SHA:CAMELLIA128-SHA: ECDHE-RSA-DES-CBC3-SHA: ECDHE-ECDSA-DES-CBC3-SHA: DES-CBC3-SHA
Cisco SIP Proxy	TCP / TLS	5062	ECDHE-RSA-AES256-GCM-SHA384: ECDHE-ECDSA-AES256-GCM-SHA384: ECDHE-RSA-AES256-SHA384: ECDHE-ECDSA-AES256-SHA384: ECDHE-RSA-AES256-SHA: ECDHE-ECDSA-AES256-SHA: AES256-GCM-SHA384: AES256-SHA256:AES256-SHA: CAMELLIA256-SHA: ECDHE-RSA-AES128-GCM-SHA256: ECDHE-ECDSA-AES128-GCM-SHA256: ECDHE-RSA-AES128-SHA256: ECDHE-ECDSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: ECDHE-ECDSA-AES128-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA: ECDHE-RSA-DES-CBC3-SHA: ECDHE-ECDSA-DES-CBC3-SHA: DES-CBC3-SHA
Cisco SIP Proxy	TCP / TLS	8083	`ECDHE-RSA-AES256-GCM-SHA384: ECDHE-ECDSA-AES256-GCM-SHA384: ECDHE-RSA-AES256-SHA384: ECDHE-ECDSA-AES256-SHA384: ECDHE-RSA-AES256-SHA: ECDHE-ECDSA-AES256-SHA: AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: ECDHE-RSA-AES128-GCM-SHA256: ECDHE-ECDSA-AES128-GCM-SHA256: ECDHE-RSA-AES128-SHA256: ECDHE-ECDSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: ECDHE-ECDSA-AES128-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA: ECDHE-RSA-DES-CBC3-SHA: ECDHE-ECDSA-DES-CBC3-SHA: DES-CBC3-SHA`
Cisco Tomcat	TCP / TLS	8443, 443	ECDHE-RSA-AES256-GCM-SHA384: ECDHE-RSA-AES256-SHA384: ECDHE-RSA-AES256-SHA: DHE-RSA-AES256-GCM-SHA384: DHE-RSA-AES256-SHA256: DHE-RSA-AES256-SHA: DHE-RSA-CAMELLIA256-SHA: AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: ECDHE-RSA-AES128-GCM-SHA256: ECDHE-RSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: DHE-RSA-AES128-GCM-SHA256: DHE-RSA-AES128-SHA256: DHE-RSA-AES128-SHA: DHE-RSA-CAMELLIA128-SHA: AES128-GCM-SHA256: AES128-SHA256:AES128-SHA: CAMELLIA128-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-AES128-GCM-SHA256: ECDHE-ECDSA-AES128-SHA256: ECDHE-ECDSA-AES128-SHA: ECDHE-ECDSA-DES-CBC3-SHA
Cisco XCP XMPP Federation Connection Managing director	TCP /TLS	5269	`ECDHE-RSA-AES256-GCM-SHA384: ECDHE-ECDSA-AES256-GCM-SHA384: ECDHE-RSA-AES256-SHA384: ECDHE-ECDSA-AES256-SHA384: ECDHE-RSA-AES256-SHA: ECDHE-ECDSA-AES256-SHA: AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: ECDHE-RSA-AES128-GCM-SHA256: ECDHE-ECDSA-AES128-GCM-SHA256: ECDHE-RSA-AES128-SHA256: ECDHE-ECDSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: ECDHE-ECDSA-AES128-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA: ECDHE-RSA-DES-CBC3-SHA: ECDHE-ECDSA-DES-CBC3-SHA: DES-CBC3-SHA`
Cisco XCP Client Connection Director	TCP / TLS	5222	`ECDHE-RSA-AES256-GCM-SHA384: ECDHE-ECDSA-AES256-GCM-SHA384: ECDHE-RSA-AES256-SHA384: ECDHE-ECDSA-AES256-SHA384: ECDHE-RSA-AES256-SHA: ECDHE-ECDSA-AES256-SHA: AES256-GCM-SHA384:AES256-SHA256: AES256-SHA:CAMELLIA256-SHA: ECDHE-RSA-AES128-GCM-SHA256: ECDHE-ECDSA-AES128-GCM-SHA256: ECDHE-RSA-AES128-SHA256: ECDHE-ECDSA-AES128-SHA256: ECDHE-RSA-AES128-SHA: ECDHE-ECDSA-AES128-SHA: AES128-GCM-SHA256:AES128-SHA256: AES128-SHA:CAMELLIA128-SHA: ECDHE-RSA-DES-CBC3-SHA: ECDHE-ECDSA-DES-CBC3-SHA: 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) awarding. 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 fix, tear down and maintain calling features based on a user's action at the Lync client.

Notation

SIP federation and Remote Telephone call Command (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, only for RCC a user must exist licensed for Cisco IM and Presence Service and Microsoft Lync/OCS at the aforementioned 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, electric current release
Microsoft Lync Server 2010 or 2013 Release 4.10, Standard Edition or Enterprise Edition
- Lync Server Command Panel
- Lync Server Deployment Sorcerer
- Lync Server Logging Tool
- Lync Server Management Beat out
- Lync Server Topology Builder
Microsoft 2010 Lync Client, or, Microsoft 2013 Lync Client

(Optional) Upgraded Skype for Business concern 2015 Client

Note

The Skype for Concern 2015 customer must have been upgraded from a Lync 2013 customer and must exist 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 Phone call Control with Microsoft Lync Server for the IM and Presence Service at https://world wide web.cisco.com/c/en/us/support/unified-communications/unified-presence/products-installation-and-configuration-guides-list.html.