This document provides installation instructions for Unified CCE 12.5(1) ES12. 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.
Along with fixes for the defects specified below, this Engineering
Special also includes support for the following features to PCCE 12.5(1):
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) ES12 on these Unified CCE components:
Do not install this engineering special on any components other than:
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. Using
the ICM Service Control, stop all the ICM services running on the system.
2. Launch
the Installer provided for ES12 and follow the instructions on
the screen.
3. 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
4. Using
the ICM Service Control, start all ICM services again.
All CVPs are no longer media servers by default.
After installation do the following to make CVP act as media server.
1.
Login to CCE web administration.
2.
Go to inventory gadget.
3.
Edit the CVP machine, you intent to mark as media
server.
4.
Check “Enable Media Server” option.
5.
Save.
Note: The FTP credentials will be lost after patch uninstallation, and this needs to be configured again after uninstallation.
Pre
Uninstallation
1.
Login into CCE Web Administration.
2.
Go to inventory.
3.
Disable all the CVP which are marked as
media server.
Uninstall
Patch
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.
Post
uninstallation
1.
Restart ICM box post uninstallation.
2.
Login to CCE Web Administration.
3.
Go to inventory.
4.
Edit one of the CVP machine.
5.
Trigger full sync.
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 individual Unified CCE defects and track 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) ES12.
Caveats in this section are ordered by UNIFIED CCE component, severity, and then identifier.
|
Identifier |
Severity |
Component |
Headline |
|
CSCvs21511 |
3 |
dbconfig |
PCCE
12K: HDS fails to register to SSO mode |
|
CSCvs49920 |
3 |
dbconfig |
Not
able to switch PrincipalAW when DF Service is down
on the existing PrincipalAW |
|
CSCvs79502 |
3 |
dbconfig |
PCCE4k:
Able to add Machines to inventory with Same MachineName |
|
CSCvt65662 |
3 |
dbconfig |
NullPointerException during PCCE 4K/12K fresh install when Rogger
is simplexed in the CSV |
|
CSCvs64057 |
2 |
template |
Reason
Codes doesn't show in Teams gadget for the first time |
Caveats are ordered by severity then defect number.
Defect Number: CSCvs64057
Component: template
Severity: 2
Headline: Reason Codes doesn't show in Teams gadget for the first time
Symptom:
Reason Codes doesn't show in Teams gadget
Conditions: first time when logged into cceadmin
Workaround: Go to Overview and come back to Teams gadget. This time all the
make request goes with Finesse hostname
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.
<hr size=0 width="100%" align=center>
Defect Number: CSCvs21511
Component: dbconfig
Severity: 3
Headline: PCCE 12K: HDS fails to register to SSO mode
Due to this unable to set SSO
mode on the PCCE 12K deployment.
Symptom: This happens during setting SSO mode on PCCE 12K deployment.
Conditions: PCCE 12K deployment SSO configure.
Workaround: Remove HDS from the inventory and click Register for proceeding
to SSO registration.
Further Problem Description:
Defect Number: CSCvs49920
Component: dbconfig
Severity: 3
Headline: Not able to switch PrincipalAW when DF Service is down on the existing PrincipalAW
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Defect Number: CSCvs79502
Component: dbconfig
Severity: 3
Headline: PCCE4k: Able to add Machines to inventory with Same MachineName
Symptom:
Able to add Machines to inventory with Same MachineName
Conditions: PCCE4k
Workaround: None
Further Problem Description:
Defect Number: CSCvt65662
Component: dbconfig
Severity: 3
Headline: NullPointerException during PCCE 4K/12K fresh install when Rogger is simplexed in the CSV
Symptom:
Observing the following exception in tomcat logs java.lang.NullPointerException
at
com.cisco.ccbu.cce.unifiedconfig.api.inventory.InventoryUtilities.getMachineAddressObjOrNull(InventoryUtilities.java:1982)
at com.cisco.ccbu.cce.unifiedconfig.api.inventory.InventoryUtilities.getMachineAddress(InventoryUtilities.java:1921)
at
com.cisco.ccbu.cce.unifiedconfig.api.inventory.InventoryUtilities.getMachineAddressOrThrow(InventoryUtilities.java:1906)
at com.cisco.ccbu.cce.unifiedconfig.api.inventory.InventoryUtilities.getDiagnosticPortalRestClient(InventoryUtilities.java:2067)
at
com.cisco.ccbu.cce.unifiedconfig.api.inventory12k.validators.InventoryImportBaseValidator.getDMPNumbersOnRouter(InventoryImportBaseValidator.java:184)
at com.cisco.ccbu.cce.unifiedconfig.api.inventory12k.validators.InventoryImportBaseValidator.validateRouterDMPNumber(InventoryImportBaseValidator.java:158)
Conditions: When performing PCCE 4K/12K fresh install, provide the
information for only one side Rogger or Router machine.
(i.e. Simplexed Rogger /
Router in the CSV data)
Workaround: When performing PCCE 4K/12K fresh install, provide the
information for both sides of Rogger or Router
machines.
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. ICM12.0(1)_ES49 at
https://software.cisco.com/download/specialrelease/f0536d930a4e7319b84bac021536e896
|
ES# |
Identifier |
Severity |
Component |
Headline |
|
ES5 |
3 |
aw.tools |
ECC CTI variable size check enforcement to be relaxed and a
warning be displayed if size is exceeded |
|
|
ES7 |
CSCvs85018 |
2 |
dbconfig |
Finesse
gadget is not loading in CCEAMDIN in PCCE labonly
mode |
|
ES7 |
CSCvs64183 |
3 |
dbconfig |
PCCE
registration of SSO clients fail in SPOG |
|
ES7 |
CSCvs77949 |
3 |
dbconfig |
Agents
with TraceON enabled for 12k is 400 in Doc vs 100
in System Capacity (pcce webadmin) |
|
ES7 |
CSCvs96235 |
3 |
dbconfig |
PCCE
exeeded configuration limit should not trigger
Service Busy state |
|
ES7 |
CSCvt09634 |
3 |
dbconfig |
PCCE
4K/12K day 1 validations are not exercised for both Main Site and Remote
Sites |
|
ES7 |
CSCvu00949 |
3 |
dbconfig |
SPOG:
Cloud Connect Integration page not working in Lab Only mode |
|
ES7 |
CSCvt07963 |
5 |
dbconfig |
[VPAT
Observation] Keyboard visual focus is not visible on some elements |
|
ES7 |
CSCvs48546 |
3 |
template |
SSO
supervisor : cceadmin fails to load due to bundle
mismatch |
|
ES7 |
CSCvs56462 |
3 |
template |
Miscellaneous
page fails to load with InternalServerError when
there are no NetworkVRU's in system |
|
ES7 |
CSCvt05248 |
3 |
template |
In
4k, While deleting a peripheral set, the validation errors are not getting
listed in UI |
|
ES7 |
CSCvs77189 |
2 |
web.config.ui |
Cannot
Switch to HCS 4K Deployment if Total Dialed Numbers
on All CVP Route Clients Exceeds 4000 |
|
ES7 |
CSCvt01048 |
3 |
web.config.ui |
CVP
shows OUT_OF_SYNC every 10 mins after CloudConnectInventoryScanner |
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: