This document provides installation instructions for Unified CCE 12.5(1) ES111. 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:
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.
This section lists the Unified CCE components on which you can and cannot install this engineering special.
You can install Unified CCE 12.5(1) ES111 on these Unified CCE components:
Do not install this engineering special on any component other than the following:
Installation of this patch requires that all Unified CCE services be shut down during the entire period of installation.
If the Unified CCE Services are set to manual, using the Unified CCE Service Control, start all the Unified CCE Services.
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.
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.
This section lists caveats specifically resolved by Unified CCE 12.5(1) ES111.
Caveats in this section are ordered by Unified CCE component, severity, and then identifier.
| Identifier | Severity | Component | Headline |
|---|---|---|---|
| CSCwa41830 | 3 | web.config.api | Existing Departments are unable to Sync with ECE |
Caveats are ordered by severity, then by defect number.
Defect Number: CSCwa41830
Component: web.config.api
Severity: 3
Headline: Existing Departments are unable to Sync with ECE
0000348261: 10.84.252.71: Dec 01 2021 22:35:56.788 +0530: %CCBU_pool-11-thread-1-6-REST_API_INFO: Response Got is POST returned a response status of 204 No Content
0000348262: 10.84.252.71: Dec 01 2021 22:35:56.788 +0530: %CCBU_pool-11-thread-1-6-REST_API_INFO: sendRestRequestToMachine :: counterRetryAttempt= 1
0000348263: 10.84.252.71: Dec 01 2021 22:35:56.788 +0530: %CCBU_pool-11-thread-1-6-REST_API_INFO: Rest call: application/xml
0000348264: 10.84.252.71: Dec 01 2021 22:35:56.819 +0530: %CCBU_pool-11-thread-1-6-REST_API_INFO: Response Got Status is Not Found
0000348265: 10.84.252.71: Dec 01 2021 22:35:56.819 +0530: %CCBU_pool-11-thread-1-6-REST_API_INFO: Response Got is GET returned a response status of 404 Not Found
0000348266: 10.84.252.71: Dec 01 2021 22:35:56.819 +0530: %CCBU_pool-11-thread-1-3-REST_API_EXCEPTION: %[exception=com.cisco.ccbu.cce.unifiedconfig.api.error.CceDBDataNotFoundException: The specified URL does not exist.][message_string=Error 404 occurred while trying to GET to : The REST API has caught an exception
0000348267: 10.84.252.71: Dec 01 2021 22:35:56.819 +0530: %CCBU_pool-11-thread-1-3-EXCEPTION_INFO: %[build_date=Jan 07, 2020 3:17 PM][build_type=rel][exception=com.cisco.ccbu.cce.unifiedconfig.api.error.CceDBDataNotFoundException: The specified URL does not exist.
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.processErrorResponse(RESTClient.java:178)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.analyzeClientResponse(RESTClient.java:112)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.makeRequest(RESTClient.java:271)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.get(RESTClient.java:314)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ProcessingWorker.sendRestRequestToMachine(ProcessingWorker.java:153)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ECEProcessingWorker.getClientResponse(ECEProcessingWorker.java:276)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ECEProcessingWorker.getDepartmentFromECE(ECEProcessingWorker.java:233)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ECEProcessingWorker.bulkDepartmentSync(ECEProcessingWorker.java:360)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ECEProcessingWorker.eceDeferredSyncWorkFlow(ECEProcessingWorker.java:307)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ECEProcessingWorker.deferredSyncWorkflow(ECEProcessingWorker.java:103)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ProcessingWorker.call(ProcessingWorker.java:93)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ProcessingWorker.call(ProcessingWorker.java:37)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
| Identifier | Severity | Component | Headline |
|---|---|---|---|
| CSCvz50705 | 3 | web.config.api | Tomcat crashes when contacts for more than 200 campaigns are imported in a sequential manner |
| CSCwa30854 | 3 | ova | VM validation in cceadmin will fail when ICM in 12.5 and Finesse in 12.6 |
| CSCvw47719 | 3 | dbconfig | CUIC streaming datasource creation fails in PCCE lab deployment |
| CSCvx95438 | 3 | web.config.api | While setting deployment to PCCE 2k, issue while providing CVP cred |
| CSCvu80248 | 3 | web.config.api | [Smart Licensing] License management option is not available for NAM deployment |
| CSCvx98655 | 3 | web.config.ui | Licensing Management page is blank in CCEadmin when Contact director is chosen as deployment type |
| CSCvx94616 | 2 | web.config.api | B-Side Campaign Manager stays stuck in standby when frequent API requests are being sent |
| CSCvw53423 | 2 | dbconfig | Issue in Fresh Install of PCCE Simplex Lab mode |
You can access current Cisco documentation on the Support pages at the following sites:
To provide comments about this document, send an email message to the following address:
contactcenterproducts_docfeedback@cisco.com
We appreciate your comments.
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 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.
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.
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/
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: