About this Document


This document provides installation instructions for Unified CCE 11.6(2) ES78. 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:

Sign Up for Email Notification of New Field Notices


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.

About Cisco Unified CCE (and Unified CCE Engineering Specials)


This 11.6(2) engineering special is meant to be installed on duplexed sides of an Agent PG (CUCM PG).

Known / Open caveat of this Engineering Special

The Logger and Historical DB may have the event captured in the Event and Application_Event table with the MessageString column data populated as the below:

“EMS Error. FormatMessage for message id a108c02d failed. GetLastError() returned 317”

This is because the Router and Logger services are unaware of this new event originating from PG. This error / warning may be safely ignored.

Unified CCE Compatibility and Support Specifications


Unified CCE Version Support

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 11.6(2) ES78 on these Unified CCE components:

Note: The engineering special needs to be applied on both sides of the Agent PG (CUCM PG), preferably in a maintenance window.

Unsupported Unified CCE Components

Do not install this engineering special on any component other than the duplexed Agent PG’s.

Unified CCE Engineering Special Installation Planning


Installing Unified CCE 11.6(2) ES78


Installation of this patch requires that all Unified CCE services be shut down during the entire period of installation.

  1. It is always recommended to install this ES during a scheduled downtime.
  2. Using the Unified CCE Service Control, stop all the Unified CCE Services running on the system.
  3. Launch the installer provided and follow the instructions on the screen.

If the Unified CCE Services are set to manual, using the Unified CCE Service Control, start all the Unified CCE Services.

Uninstall Directions for Unified CCE 11.6(2) ES78


  1. To uninstall this patch, go to Control Panel.
  2. Select "Add or Remove Programs".
  3. 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:


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 11.6(2) ES78

This section lists caveats specifically resolved by Unified CCE 11.6(2) ES78.

Index of Resolved Caveats

Caveats in this section are ordered by UNIFIED CCE component, severity, and then identifier.
Identifier Severity Component Headline
CSCvq11852 2 pg.opc Chat and emails don't get assigned to agents even though they are available

Detailed list of Resolved Caveats in This Engineering Special

Caveats are ordered by severity, and then by the defect number.


Defect Number: CSCvq11852

Component: pg.opc

Severity: 2

Headline: Chat and emails don't get assigned to agents even though they are available


Symptom:
After Public network disconnection, one side Router loses connectivity with its PGs. This triggers other router side to bring the Application path down and thereby all associated agents are moved to status 'D'. Router sees Media Routing Domain as unavailable as reported by Application path. 1. Router marks those agent statuses to 'D'. It should not show as ICMAvailable in RTTEST agent_status and in Script editor as well. This is misleading. 2. Since Router A is ACTIVE and processing calls, need to handle the same when only Router B disconnects.

Conditions:
Public network flapping, disconnecting connecting between Router & PGs 10:15:46:635 rb-ccag Device: PG02, disconnected. 10:23:42:562 rb-ccag Device: PG02, disconnected. 10:23:46:561 rb-ccag Device: PG01, disconnected. 10:26:57:996 rb-ccag Device: PG01, disconnected. Other side router moved the Agent state in chat and email to D 19:52:30:979 ra-rtr Trace: Agent XXXX from PG domain XXXX. [na-0:1,RD**] to [na-0:1,D*] 19:52:30:979 ra-rtr Trace: Agent XXXX from PG domain XXXX . [na-0:1,D*] to [nr-0:1,D*] 19:52:30:979 ra-rtr Trace: Agent XXXX ended temp-unavail in domain XXXX . State changed from [nr-0:1,D*] to [nr-0:1,D] 19:52:31:979 ra-rtr Trace: Agent XXXX from PG domain XXXX. [nr-0:1,D] to [nr-0:1,RD] 19:52:31:979 ra-rtr Trace: Agent XXXX from PG domain XXXX. [nr-0:1,RD] to [na-0:1,RD]

Workaround:
Either perform exit_opc on Agent PG or restart egain services

Further Problem Description:
Need to set "watch skillgroup" in the router to get the agent state under by router

Caveats resolved in earlier ESs and included as part of Unified CCE 11.6(2) ES78

Identifier Severity Component Headline
CSCvh66113 2 pg.opc Interval Reporting Failures During Load: SGI, ASGI, AI
CSCvr34208 3 pg.opc Finesse non-voice agent's state is stuck in "Active" after all tasks are closed
CSCvp66976 3 pg.opc Mismatch in the Call_Type_Interval and TCD tables with calls marked as Short instead of Abandoned
CSCvp83424 3 pg.opc PG OPC crash during state transfer
CSCvu76997 3 pg.opc START_TASK_EVENT not generated for a Start_Application_Task_Req
CSCvj64880 3 pg.opc NotReady Reason code is lost for Non-Voice MRD's once Agent answers a Voice Call
CSCvx86254 3 pg.opc Dialer detail entry missing if agent conferences external numbers on dialer calls
CSCvq16162 3 router Cisco Unified Contact Center Enterprise Denial of Service Vulnerability

Obtaining Documentation


You can access current Cisco documentation on the Support pages at the following sites:

Documentation Feedback

To provide comments about this document, send an email message to the following address:

contactcenterproducts_docfeedback@cisco.com

We appreciate your comments.

Obtaining Technical Assistance


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:

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/

Contacting 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: