This document provides installation instructions for Unified CCE 11.6(2) ES24. 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.
ICM 11.6(2)
This section lists the Unified CCE components on which you can and cannot install this engineering special.
You can install Unified CCE 11.6(2) ES24 on these Unified CCE components:
Do not install this engineering special on any other component other than,
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 11.6(2) ES24.
Caveats in this section are ordered by UNIFIED CCE component, severity, and then identifier.
|
Identifier |
Severity |
Component |
Headline |
|
CSCvp66976 |
3 |
pg.opc |
Mismatch
in the Call_Type_Interval and TCD tables with calls
marked as Short instead of Abandoned |
|
CSCvr50880 |
3 |
pg.opc |
OPC
considers the call as Short while RTR marks it as Abandoned causing a
mismatch in CTI and TCD |
Caveats are ordered by severity then defect number.
Defect Number: CSCvp66976
Component: pg.opc
Severity: 3
Headline: Mismatch in the Call_Type_Interval and TCD tables with calls marked as Short instead of Abandoned
Symptom: OPC
considers the call as Short while RTR marks it as Abandoned. OPC duration is
wrongly calculated with the RNACallHandler for these
calls with incorrect QueuedTime resulted Call to be
marked as Short instead of Abandoned.
Conditions:
Workaround: Use the Call_Type_Interval table to
generate the reports which has the correct data.
Further Problem Description: The issue is with OPC when processing the RNACallHandler while clearing the call with the requery abort we are using a method which does not use the NetworkQTime/NetQTime. This
caused the QueueTime to be less adding the duration
to be very less resulting the call to be handled as Short call though the TimetoAband/Duration is more.
Defect Number: CSCvr50880
Component: pg.opc
Severity: 3
Headline: OPC considers the call as Short while RTR marks it as Abandoned causing a mismatch in CTI and TCD
Symptom:
Mismatch in the Call_Type_Interval and TCD tables
with calls marked as Short instead of Abandoned. OPC considers the call as
Short while RTR marks it as Abandoned.
Conditions: TimeToAband=5 where OPC TCD has call
with Abandoned (CDF-2) and Router marks the call as short (CTI).
Workaround: Use the Call_Type_Interval table to
generate the reports which has the correct data.
Further Problem Description:
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: