About this Document

This document provides installation instructions for Unified CCE 12.5(1) ES25. It also contains a list of Unified CCE issues resolved by this engineering special. Review all installation information before installing the product. Failure to install this engineering special as described can result in inconsistent Unified CCE behavior.

This document contains these sections:

Sign Up for Email Notification of New Field Notices

In the Product Alert Tool, you can set up profiles to receive email notification of new Field Notices, Product Alerts, or End of Sale information for your selected products.

The Product Alert Tool is available at https://www.cisco.com/cisco/support/notifications.html.

About Cisco Unified CCE (and Unified CCE Engineering Specials)

Along with fixes for the defects specified below, this Engineering Special also includes support for the following features to UCCE / PCCE 12.5(1):

Non-Production System(NPS)

Non-Production System (NPS) usage mode is introduced to give you more control on license usage. With NPS, you can switch from production deployment to other deployment types such as lab, testing, and staging. For more information, refer to the section Smart Licensing in Administration Guide for Cisco Unified Contact Center Enterprise

Unified CCE Compatibility and Support Specifications

Unified CCE Version Support

Unified CCE Component Support

Supported Unified CCE Components

You can install Unified CCE 12.5(1) ES25 on these Unified CCE components:

Unsupported Unified CCE Components

Do not install this engineering special on any components other than:

Unified CCE Engineering Special Installation Planning

Installing Unified CCE 12.5(1) ES25

Installation of this patch requires the all ICM services to be shut down during the entire period of installation. It is always recommended to install this ES during a scheduled downtime.
  1. Open CCE Web Administration, Navigate to the License Management Page.
  2. De-register the Product Instance.
  3. Using the ICM Service Control, stop all the ICM services running on the system.
  4. Launch the Installer provided for ES25 and follow the instructions on the screen.
  5. Check the version of tomcat installed by running <ICM HOME>\tomcat\bin\version.bat . If its 9.0.37 or higher, then do the following steps


  6. Using the ICM Service Control, start all ICM services again.
  7. In the rare event where the CCE Web Administration UI isn't working as expected, clear the browser cache and re-open CCE Web Administration.

Uninstall Directions for Unified CCE 12.5(1) ES25

  1. To uninstall this patch, go to Control Panel.
  2. Select "Add or Remove Programs".
  3. Find the installed patch in the list and select "Remove".
  4. In the rare event where the CCE Web Administration UI isn't working as expected, clear the browser cache and re-open CCE Web Administration.

Note: Remove patches in the reverse order of their installation. For example, if you installed patches 3, then 5, then 10 for a product, you must uninstall patches 10, 5, and 3, in that order, to remove the patches from that product.

Resolved Caveats in this Engineering Special

This section provides a list of significant Unified CCE defects resolved by this engineering special. It contains these subsections:

Note: You can view more information on and track individual Unified CCE defects using the Cisco Bug Search tool, located at: https://bst.cloudapps.cisco.com/bugsearch/search?null.

Resolved Caveats in Unified CCE 12.5(1) ES25

This section lists caveats specifically resolved by Unified CCE 12.5(1) ES25.

Index of Resolved Caveats

Caveats in this section are ordered by UNIFIED CCE component, severity, and then identifier.

Identifier Severity Component Headline
CSCvu54806 2 dbconfig Not able to update credentials of Remote Site CUCM PUB
CSCvu85367 2 dbconfig Symmetric Key exception observed intermittently
CSCvu20611 3 smart-license Correct CCE Server License tag
CSCvv74905 3 smart-license ICM 12.5(1) setting "Next_Available_Number" to 5000 for "Smart_License_Entitlements" table.

Detailed list of Resolved Caveats in This Engineering Special

Caveats are ordered by severity then defect number.

Defect Number: CSCvu54806

Component: dbconfig

Severity: 2

Headline: Not able to update credentials of Remote Site CUCM PUB


Symptom: Not able to update credentials of Remote Site CUCM PUB

Conditions: 2k Remote site with new CUCM publisher

Workaround: None

Further Problem Description: Getting the Patch: The following links take you to an emergency patch, called an Engineering Special or ES. These emergency patches are meant for deployments that are actively encountering a specific problem and cannot wait for a formal release to include a fix. An ES receives limited testing compared to a formal release. Installing an ES on a production system poses a risk of instability due to that limited testing. If you are not directly experiencing this problem, wait to install a major, minor, or maintenance release that includes the fix for this issue. If you experience this problem and cannot wait for a later formal release, select the ES that matches the base release of your deployment. The base release is the front part of the ES name. Only install an ES that matches the release that your deployment runs. Always read the release notes or Readme file before running the patch installer.

Defect Number: CSCvu85367

Component: dbconfig

Severity: 2

Headline: Symmetric Key exception observed intermittently


Symptom: Symmetric Key exception observed intermittently

Conditions: No Specific Condition

Workaround: Restart Tomcat

Further Problem Description: Getting the Patch: The following links take you to an emergency patch, called an Engineering Special or ES. These emergency patches are meant for deployments that are actively encountering a specific problem and cannot wait for a formal release to include a fix. An ES receives limited testing compared to a formal release. Installing an ES on a production system poses a risk of instability due to that limited testing. If you are not directly experiencing this problem, wait to install a major, minor, or maintenance release that includes the fix for this issue. If you experience this problem and cannot wait for a later formal release, select the ES that matches the base release of your deployment. The base release is the front part of the ES name. Only install an ES that matches the release that your deployment runs. Always read the release notes or Readme file before running the patch installer.

Defect Number: CSCvu20611

Component: smart-license

Severity: 3

Headline: Correct CCE Server License tag


Symptom: Correct CCE Server License tag.

Conditions: This issue occurs in UCCE deployments only

Workaround: No workaround, but it does not have any side effects on functionality.

Further Problem Description: This issue will be corrected in 12.6(1) release Getting the Patch: The following links take you to an emergency patch, called an Engineering Special or ES. These emergency patches are meant for deployments that are actively encountering a specific problem and cannot wait for a formal release to include a fix. An ES receives limited testing compared to a formal release. Installing an ES on a production system poses a risk of instability due to that limited testing. If you are not directly experiencing this problem, wait to install a major, minor, or maintenance release that includes the fix for this issue. If you experience this problem and cannot wait for a later formal release, select the ES that matches the base release of your deployment. The base release is the front part of the ES name. Only install an ES that matches the release that your deployment runs. Always read the release notes or Readme file before running the patch installer.

Defect Number: CSCvv74905

Component: smart-license

Severity: 3

Headline: ICM 12.5(1) setting "Next_Available_Number" to 5000 for "Smart_License_Entitlements" table.


Symptom: Distributor keep on sending "Add" request to router for Smart_License_Entitlements table with tag id 5000 and logger rejects it. ES15 installation is triggering those request to initiate. Clgr logs: 19:50:52:712 la-clgr Trace: Add for table Smart_License_Entitlements: 19:50:52:712 la-clgr Trace: SmartLicenseEntitlementsTagID = 5000 19:50:52:712 la-clgr Trace: Error code is: 70001 19:50:52:712 la-clgr Trace: Message action is: Add (1) 19:50:52:712 la-clgr Trace: Message type is: t_Smart_License_Entitlements (660) 19:50:52:712 la-clgr Trace: Id field 1 is: 5000 19:50:52:712 la-clgr Trace: Id field 2 is: -1 19:50:52:712 la-clgr Trace: Field number is: 1 19:50:52:712 la-clgr Trace: Thread[2912]: InsertConfig failed 19:50:52:712 la-clgr Trace: Thread[2912]: ConfigMsg Type 660, Action 1, Count 1, Version 1, Flags 0 19:50:52:712 la-clgr Trace: Thread[2912]: Config Transaction for Source 1, TransactionID 380, SequenceNumber 3 has been aborted. 19:50:52:712 la-clgr Trace: Thread[2912]: Config Error: Attempt to insert a new record with a unique ID that is already in use. This is happening because ICM 12.5(1) setting "Next_Available_Number" to 5000 for "Smart_License_Entitlements" table after installation.

Conditions: ICM 12.5 ES15 installation.

Workaround: None

Further Problem Description: Distributor keep on sending "Add" request to router for Smart_License_Entitlements table with tag id 5000 and logger rejects it. ES15 installation is triggering those request. Clgr logs: 19:50:52:712 la-clgr Trace: Add for table Smart_License_Entitlements: 19:50:52:712 la-clgr Trace: SmartLicenseEntitlementsTagID = 5000 19:50:52:712 la-clgr Trace: Error code is: 70001 19:50:52:712 la-clgr Trace: Message action is: Add (1) 19:50:52:712 la-clgr Trace: Message type is: t_Smart_License_Entitlements (660) 19:50:52:712 la-clgr Trace: Id field 1 is: 5000 19:50:52:712 la-clgr Trace: Id field 2 is: -1 19:50:52:712 la-clgr Trace: Field number is: 1 19:50:52:712 la-clgr Trace: Thread[2912]: InsertConfig failed 19:50:52:712 la-clgr Trace: Thread[2912]: ConfigMsg Type 660, Action 1, Count 1, Version 1, Flags 0 19:50:52:712 la-clgr Trace: Thread[2912]: Config Transaction for Source 1, TransactionID 380, SequenceNumber 3 has been aborted. 19:50:52:712 la-clgr Trace: Thread[2912]: Config Error: Attempt to insert a new record with a unique ID that is already in use. This is happening because ICM 12.5(1) setting "Next_Available_Number" to 5000 for "Smart_License_Entitlements" table after installation. This is because, ICM 12.5(1) setting "Next_Available_Number" to 5000 for "Smart_License_Entitlements" table after installation.

Obtaining Documentation

You can access current Cisco documentation on the Support pages at the following sites:

Documentation Feedback

To provide comments about this document, send an email message to the following address:

contactcenterproducts_docfeedback@cisco.com

We appreciate your comments.

Obtaining Technical Assistance

Cisco.com is a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC site.

Cisco.com

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. You can also resolve technical issues with online technical support and download software packages. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

Technical Assistance Center

The Cisco TAC site is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Site

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to https://www.cisco.com/c/en/us/support/index.html.

P3 and P4 level problems are defined as follows:

In each of the above cases, use the Cisco TAC site to quickly find answers to your questions.

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following site: https://mycase.cloudapps.cisco.com/create/start/

CContacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following sites:

P1 and P2 level problems are defined as follows: