This document provides installation instructions for Unified CCE 12.5(1)
ES126. 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 behaviour.
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.
ICM12.5(1)
You can install Unified CCE 12.5(1) ES126 on these Unified CCE components:
Do not install this engineering special on any components other than:
1. Download the patch and copy
the patch local to the server where patch is going to be installed.
2. Stop all ICM services and
application running on the server
3. Run the patch installer exe
and follow the instructions.
4. Reboot the server on
successful completion of patch install.
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
oStep 1:
In <ICM
HOME>\tomcat\conf\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
oStep 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.
6. Start the ICM 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)
ES126.
Caveats in this section are ordered by UNIFIED CCE component, severity, and
then identifier.
Identifier |
Severity |
Component |
Headline |
CSCwc04257 |
3 |
aw.tools |
UCCE 12.5 - AW - Webadmin - Unable to Login to CCEAdmin, receiving Service Temporarily Unavailable |
Caveats are ordered by severity then defect number.
Defect Number: CSCwc04257
Component: aw.tools
Severity: 3
Headline: UCCE 12.5 - AW - Webadmin - Unable to Login to CCEAdmin, receiving Service Temporarily Unavailable
Symptom: UCCE - AW server v12.5 When ever user
tries to login CCEadmin, Tomcat crashes leading to
the following error. Service Temporarily Unavailable! The server is temporarily
unable to service your request due to maintenance downtime or capacity
problems. Please try again later. Tomcat/ISAPI/isapi_redirector/1.2.41.1
Conditions: None
Workaround: None
Further Problem Description: NA
Defect Number: CSCvs59785
Component: aw.tools
Severity: 4
Headline: AgentExplorer crash with supervisor creation when User is created with different sam and upn name.
Symptom: This issue is observed only in below condition:
1) User's sam and upn name should be different.
2) User should exist in more than 1 domain which has trust relationship with UCCE domain.
Reproducible in trusted domains and parent child domain.
Steps to reproduce:
1) Have 1 trusted domain with CCE domain and 1 child domain for CCE domain.
2) Create a below user in all domain .(sam and upn name should be different as below).
example:
User name - user1
user sam name - user1sam
user upn name - user1upn
3) Create a agent by providing sam name in login name select default domain with trusted or child domain.
4) select Supervisor check box.
Expected Result :
Supervisor should save.
Actual Result :
Agent explorer is crashing
Conditions: Occurs only if same user exist in multiple domains (3 or more)
with different upn and sam
name.
Workaround: Keep both upn and sam
as same name.
Further Problem Description: NA
Defect Number: CSCvr51665
Component: aw.tools
Severity: 3
Headline: Unable to promote agents to supervisor - User object Not reachable
Symptom: Unable to promote agents to supervisor's. When attempting to
promote an agent to a supervisor the system generates the following error:
"The specified agent's Active Directory user account is not valid for a supervisor. See your domain administrator.
[User object Not reachable"
Customer upgraded from UCCE 11.6 to UCCE 12.0. After the upgrade they are no longer able to promote agents to supervisor's. They get the generic error:
"The specified agent's Active Directory user account is not valid for a supervisor. See your domain administrator.
[User object Not reachable"
Supervisors that we demote to agents and then make agents again get the same error.
As part of troubleshooting we noticed, serviceability is
lacking in this area. Please add some serviceability traces as well while
fixing the defect.
Conditions: Complex forest that has multiple domains.
The issue seems to occur when ICM is unable to navigate the global catalog.
Workaround: None
Further Problem Description: NA
Defect Number: CSCvs59403
Component: tools
Severity: 3
Headline: Websetup and CCEAdmin login delay ~30 mins
Symptom: After upgrading ICM from 11.6(1) to 11.6(2), there's considerable
amount of delay observed after login. It takes more than 30 mins and eventually
gets in to undesirable results such as failed/timed out, etc...
Conditions: Large AD environment with 20-30 externally trusted domains
Workaround: Downgraded to 11.6.1, no delays were observed OR
Replaced sadlib.pdb & sadlib.dll from 11.6.1 to 11.6.2 version files and the delay was fixed but faced some other issues as follows.
1) Tried to login into web setup using child domain credential it works.
2) Tried to login into web setup using parent domain user credential it don't work. (Error validating the Active directory
environment. Unable to load current domain information.)
3) Domain manger don't open (after
reverting the changes it works)
Further Problem Description: NA
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: