This document provides installation instructions for Unified CCE 11.6(2) ES71. 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 11.6(2) ES71 on these Unified CCE components:
Do not install this engineering special on any component other than:
1. Launch the installer provided for ES71 and follow the instructions
provided by the installer to complete the installation.
2. Once the installation is complete, restart the machine.
3. Using the ICM Service Control, start the UCCE services if they are
not started already.
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) ES71.
Caveats in this section are ordered by UNIFIED CCE component, severity, and
then identifier.
Identifier |
Severity |
Component |
Headline |
CSCvu76997 |
3 |
pg.opc |
START_TASK_EVENT
not generated for a Start_Application_Task_Req |
Caveats are ordered by severity then defect number.
Defect Number: CSCvu76997
Component: pg.opc
Severity: 3
Headline: START_TASK_EVENT not generated for a Start_Application_Task_Req
Symptom:
Custom / 3rd party applications integrating with Agent PG over the ARM /
GED-188 protocol interface monitoring non-voice task events do not receive
notification about task actively being worked upon by Agents via
START_TASK_EVENT
Conditions: Only impacts those tasks that are initialized or routed by
multimedia applications internally, and notified to Agent PG for task
initialization, via the START_APPLICATION_TASK_REQ / START_APPLICATION_TASK_RESP
mechanism.
Workaround: None
Further Problem Description: The Agent PG generates a TaskID that it
conveys back to the custom application (via the START_APPLICATION_TASK_RESP
message), that initially notified PG about the non-routed task having been worked
upon by an Agent. However all other CTI clients monitoring tasks, fail to get
notified via the START_TASK_EVENT which can lead to those applications not
being able to track / process further events for such tasks. As these are
essentially non-routed tasks, there wouldn't be the usual event sequence of
receiving an AGENT_LEGACY_PRE_CALL_EVENT message prior to the START_TASK_EVENT.
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.
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: