Release Notes for Cisco Unified Communications Manager and the IM and Presence Service, Release 12.0(1)

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Release Notes for Cisco Unified Communications Manager and the IM and Presence Service, Release 12.0(1)

Chapter Title

About this Release

Results

Updated:
August 17, 2017

Chapter: About this Release

About this Release

Revision History

Date

Revision

August 17, 2017

Initial publish

September 28, 2017

Added Revision History table to keep track of updates.

October 03, 2017

Edited language in Supported Versions.

October 06, 2017

Updated information related to documentation defect CSCvg10775.

October 24, 2017

Added important note on bandwidth allocations for 88xx phones.

November 2, 2017

Added important note on route filters and associated route patterns.

November 10, 2017

Added Enhanced CTL and ITL Trust feature.

December 06, 2017

Added Release 12.0(1)SU1 info with Extension Mobility Roaming Across Clusters feature.

December 13, 2017

Added topics on missing ENUM values for CSCvd71818 and CSCvg70867. Also added Important Note on DRS backups with PLM selected.

December 15, 2017

In Branding section, utils branding CLI commands are lower case.

April 11, 2018

Updated terminology around MRA Access Policy.

July 17, 2018

Updated list of caveats to include CSCvg04920.

January 13, 2020

Updated Supported Versions and Documentation for this release to call out SU release support.

January 16, 2020

Added Video Endpoint Migration Requirements to Important Notes

January 30, 2020

Added Important Note on gateway support.

February 12, 2020

Added important note on blue screen appearing during certain refresh upgrades.

October 19, 2020

Added updates on removal of Java Development Kit (JDK) from Cisco IP Manager Assistant.

April 28, 2021

Corrected SAST Roles in Tokenless CTL File for Release 12.0(1).

May 12, 2021

Updated Supported versions for Release 12.0(1)SU5.

Supported Versions

The following versions are supported for Release 12.0(1) and 12.0(1) SU releases:

Releases

Supported Versions

Release 12.0(1)

  • Cisco Unified Communications Manager 12.0.1.10000-10

  • IM and Presence Service 12.0.1.10000-12

Release 12.0(1)SU1

  • Cisco Unified Communications Manager 12.0.1.21900-7

Release 12.0(1)SU2

  • Cisco Unified Communications Manager 12.0.1.22900-11

Release 12.0(1)SU3

  • Cisco Unfiied Communications Manager 12.0.1.23900-9

Release 12.0(1)SU4

  • Cisco Unfiied Communications Manager 12.0.1.24900-18

Release 12.0(1)SU5

  • Cisco Unfiied Communications Manager 12.0.1.25900-7

Note
There are no 12.0(1) SU releases for the IM and Presence Service. The IM and Presence Service 12.0(1) version of 12.0.1.10000-12 is supported with any Unified Communications Manager 12.0(1) SU version.

Version Compatibility Between Unified CM and IM and Presence Service

Version compatibility between Unified Communications Manager and the IM and Presence Service depends on the IM and Presence deployment type:

  • Standard Deployments of IM and Presence—Both Unified Communications Manager and the IM and Presence Service must be running one of the 12.0(1) versions from the above table for the deployment to be supported. Note that if you are running a 12.0(1) SU version of Unified Communications Manager, you must connect to the 12.0(1) version of the IM and Presence Service.

  • Centralized Deployments of IM and Presence—There is no requirement that both the telephony cluster and IM and Presence clusters run 12.0(1) versions. If you have a centralized 12.0(1) IM and Presence cluster, you can connect to a telephony cluster that is running a different release, such as 12.5(1) or 11.5(1). However, note that the IM and Presence central cluster also includes a standalone, non-telephony Unified CM publisher node. This node, which exists for database and user provisioning, must be running the same release as the IM and Presence Service.

Upgrades

For information on upgrading to Release 12.0(1) or subsequent 12.0(1) SU releases, see the Upgrade and Migration Guide for Cisco Unified Communications Manager and IM and Presence Service, Release 12.0(1).

RTMT Installation Updates

From Release 12.0(1) and later versions, you are prompted to select the installed JRE on your machine when you launch the RTMT installation screen.

The RTMT will not recognize the latest version, if the JRE is upgraded automatically to newer version, as the older JRE version is uninstalled from your machine.

For example, while RTMT installation, if you have selected the version JRE 1.8.0.131 which is installed in the following directory: C:\Program Files (x86)\Java\jre1.8.0_131.

Then, when JRE is upgraded it deletes the older directory jre1.8.131 and new directory gets created which is not recognized by RTMT, that is C:\Program Files (x86)\Java\jre1.8.0_144.

When you try to launch RTMT from the desktop shortcut (Cisco Unified Real-Time Monitoring Tool 12.0.exe), it prompts the launch error message as Windows error 2 occurred while loading the Java VM. You can resolve this issue, by re-installing the RTMT or use the run.bat in the RTMT installed directory.

Cisco Jabber During Upgrade

It is not an essential requirement that all users must log out from Cisco Jabber, when upgrading IM and Presence Service. However, it is always a best practice that users log out from Cisco Jabber during the upgrade.

OpenJDK Migration

For this release, Cisco has migrated to the Open Java Development Kit (OpenJDK) platform from Oracle JDK for Cisco Unified Communications Manager programming and application development.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco