About this Document


This document provides installation instructions for Unified CCE 11.5(1) ES30. 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)


Unified CCE Compatibility and Support Specifications


Unified CCE Version Support

11.5(1)

Unified CCE Component Support

Supported Unified CCE Components

You can install Unified CCE 11.5(1) ES30 on these Unified CCE components:

Unsupported Unified CCE Components

Do not install this engineering special on the following components:

 

Unified CCE Engineering Special Installation Planning


Installing Unified CCE 11.5(1) ES30


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 ICM 11.5(1) ES 30 and follow the instructions on the screen.
  3. Using the ICM Service Control, start all ICM services again.

Uninstall Directions for Unified CCE 11.5(1) ES30


  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.5(1) ES30

This section lists caveats specifically resolved by Unified CCE 11.5(1) ES30.

Index of Resolved Caveats

Identifier

Severity 

   Componet

Headline

CSCve75922

3

  pg.cucm

Agents not sent to wrapup after device failure with LOAD 1

CSCvf67430

3

   pg.cucm

Logout non-activity timer is not reset when Not Ready reason code is changed



Detailed list of Resolved Caveats in This Engineering Special.

Defect Number: CSCve75922

Component: pg.cucm

Severity: 3

Headline: Agents not sent to wrapup after device failure with LOAD 1



Symptom: Configure /LOAD 1 under PG Explorer. After a Device failure, agents will not go to Wrap-up. Once the issue begins for an agent, the issue affects all future calls. 



Conditions: Steps to reproduce (taken from CCE 10.5.x example): Configure /LOAD 1 under PG Explorer. PG Cycle is required if there was a change in /LOAD parameter. 1. Customer call disconnected, agent moved to WORK_READY state 2. Administrator removed agent device from CUCM Application user 3. Agent closing CTIOS/Finesse desktop 4. Administrator added agent device to the Application user 5. Agent logged in and taking calls 6. Disconnect customer call 7. Agent won't go to WORK_READY, instead moved to READY 8. Receives 2nd customer call 9. Customer call disconnected 10. Agent won't go to WORK_READY, instead moved to READY Once issue started for an agent, the issue affects all the future calls. 



Workaround: None 



Further Problem Description:



Defect Number: CSCvf67430

Component: pg.cucm

Severity: 3

Headline: Logout non-activity timer is not reset when Not Ready reason code is changed



Symptom: The agent is logged out anyway when the logout non-activity timer expires even the agent has changed the Not Ready reason code. 



Conditions: Before the timer expires, the agent has changed the Not Ready reason codes. 



Workaround: None 



Further Problem Description:



Caveats resolved earlier ESs and included as part of ICM11.5(1) ES30:

ES#

Identifier

Severity

Component

Headline

Comments


26


CSCvf78757


2

pg.cucm

 

CUCM PG (EAPIM) crash during Network Blind Transfer call flow


None

 

 

 


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/

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