About this Document
This document provides installation instructions for Unified CCE 12.5(1) ES28. 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.
Unified CCE Version Support
12.5(1)
Unified CCE Component Support
This section lists the Unified CCE components on which you can and cannot install this engineering special.
Supported Unified CCE Components
You can install Unified CCE 12.5(1) ES28 on these Unified CCE components:
Unsupported Unified CCE Components
Do not install this engineering special on other than the following components:
Installation of this patch requires 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.
- Using the ICM Service Control, stop all the ICM services running on the system.
- Launch the Installer provided for ES28 and follow the instructions on the screen.
-
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
- Step 1:
In <ICM HOME>\tomcat\config\server.xml make sure the entry for <Connector> entry for APJ protocol is as below
< Connector port="8009" protocol="AJP/1.3" redirectPort="8443" address="127.0.0.1" maxPostSize="5242880"
secretRequired="false" allowedRequestAttributesPattern=".*" />
If the highlighted entry is missing, then add the entry in server.xml
- Step 2:
- Download the 32 bit tomcat installer zip from http://archive.apache.org/dist/tomcat/tomcat-9/ . Download the same version that is displayed when version.bat was run.
- Unzip the installer to a temp folder.
- Copy tomcat-util-scan.jar from the <temp>\apache-tomcat-9.0.xx\lib location to <ICM HOME>\tomcat\lib .
- Using the ICM/CCE Service Control, start Apache Tomcat 9 service.
- Using the ICM Service Control, start all ICM services again.
- To uninstall this patch, go to Control Panel.
- Select "Add or Remove Programs".
- Find the installed patch in the list and select "Remove".
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:
- Resolved Caveats in Unified CCE 12.5(1) ES28
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) ES28
This section lists caveats specifically resolved by Unified CCE 12.5(1) ES28.
Index of Resolved Caveats
Identifier |
Severity |
Component |
Headline |
CSCvu91995 |
3 |
web.config.api |
PeripheralNumber error when editing the name of existing Precision Queues |
Detailed list of Resolved Caveats in This Engineering Special
Defect Number: CSCvu91995
Component: web.config.api
Severity: 3
Headline: PeripheralNumber error when editing the name of existing Precision Queues
Symptom:
Unable to change the name of some PQs on the system.
Getting the following error: "Unexpected database error. Try again later or contact your administrator"
In the Tomcat (CCBU) logs found the following::
%CCBU_334908-PRECISIONQUEUE-UPDATE-5397-6-REST_API_INFO: commit error: true errorMessage: The field value is either empty or not within the range of acceptable values.
Values must be between 0 and 16777215.
[ Table: 'Skill_Group' Field: 'PeripheralNumber' ]
%CCBU_http-bio-127.0.0.1-8080-exec-9-3-REST_API_EXCEPTION: %[exception=com.cisco.ccbu.api.jaxb.error.ApiException: Error committing transaction: RestCdbError[ count: 0 dataVal: errorCaption: errorCode: 41502 errorMsg: The field value is either empty or not within the range of acceptable values.
Values must be between 0 and 16777215.
[ Table: 'Skill_Group' Field: 'PeripheralNumber' ] errorMsgDetail: errorPrefix: errorSuffix: fieldName: PeripheralNumber fieldNum: 5 fieldType: 0 loggerErrorCode: 0 tableName: Skill_Group ]][message_string=uncaught exception thrown by the api]: The REST API has caught an exception
%CCBU_http-bio-127.0.0.1-8080-exec-9-3-EXCEPTION_INFO: %[build_date=Oct 13, 2017 1:01 AM][build_type=rel][exception=com.cisco.ccbu.api.jaxb.error.ApiException: Error committing transaction: RestCdbError[ count: 0 dataVal: errorCaption: errorCode: 41502 errorMsg: The field value is either empty or not within the range of acceptable values.
Values must be between 0 and 16777215.
Conditions:
This happens when PeripheralNumbers assigned to the Precision Queue in the Skill_Group table is greater than 16777215
Workaround:
None
Further Problem Description:
Issue presents itself when PQs were created in UCCE/ICM version 9.x and then later upgraded.
The following defect was present in 9.x: CSCud37151 PeripheralNumber error when creating PR Queues
This defect was fixed in 10.x and above; however the PQ created while on 9.x will still have the higher PeripheralNumber in the Skill_Group table.
The fix for CSCud37151 did not correct the bad PeripheralNumbers that were created due to the defect, it only prevented new PQs from being assigned PeripheralNumbers greater than 16777215.
You can access current Cisco documentation on the Support pages at the following sites:
- https://www.cisco.com
- https://www-china.cisco.com
- https://www-europe.cisco.com
Documentation Feedback
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
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:
- P3--Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
- P4--You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
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:
- P1--Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available./li>
- P2--Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.