This document provides installation instructions for Unified CCE 11.5(1)
ES31. 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.
·
Unified CCE 11.5(1)
This section lists the Unified CCE components on which you can and cannot install this engineering special.
You can install Unified CCE 11.5(1) ES31 on these Unified CCE components:
Do not install this engineering special on any components other than the
following components:
Installation
of this patch requires the all Unified CCE services to
be shutdown during the entire period of installation. It is always
recommended to install this ES during a scheduled downtime.
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.5(1)
ES31.
Caveats in this section are ordered by UNIFIED CCE component, severity, and
then identifier.
|
Identifier |
Severity |
Component |
Headline |
|
CSCva07327 |
3 |
pg.cucm.jtapi |
Finesse agents frozen for 60 seconds waiting on response |
|
CSCvf59905 |
3 |
pg.cucm.jtapi |
Finesse agents get frozen for 60 seconds while waiting for response to Clear Connection request |
Caveats are ordered by severity then defect number.
Defect Number: CSCva07327
Component: pg.cucm.jtapi
Severity: 3
Headline: Finesse agents frozen for 60 seconds waiting on response
Symptom: One or more Finesse agents are not able to control calls from their
desktop for up to a minute. This occurs while an agent attempted to transfer a
call just as the call ended. This could impact more than one agent if the
calling number is the same for active calls in progress, say if the calling
number is masked, or multiple callers have blocked their calling number.
Conditions: Finesse with UCCE. Attempting to control a call while as it is
ending.
Workaround: Agent returns to normal, usually less than 60 seconds. In the
meantime, Agent can attempt controlling the call through the phone.
Further Problem Description: Can occur with any call control request from
Finesse that times out on the PG.
Defect Number: CSCvf59905
Component: pg.cucm.jtapi
Severity: 3
Headline: Finesse agents get frozen for 60 seconds while waiting for response to Clear Connection request
Symptom: Finesse server not publishing XMPP to agent for WRAPup when agent and client disconnect at same time.
Causing agent desktop to fail.
Conditions: 1. Agent is on a conference call. 2. Agent disconnects the call
from the finesse client desktop. The disconnect() request from JGW to UnifiedCM fails with an exception. But, JGW does not send
any confirmation back PIM. PIMs sends the FailureConf
back to CTI after the default 60secs timeout. 3. Before this 60secs timeout
happens in PIM, customer also disconnects the call and that moved the Agent to WrapUp state. But, Finesse did not process these events for
the Agent because, there was an outstanding ClearConnectionRequest
with CTIServer for that Agent.
Workaround: Restart the agent desktop.
Further Problem Description: The expectation from the fix is that, if JGW
sends the failure confirmation immediately as soon it encounters an exception
in the UnifiedCM disconnect() API (this can go upto 15secs, because the default timeout for any UnifiedCM API requests is 15secs), finesse server wont be blocked to process the events that happens when the
customer disconnected the call.
Caveats resolved earlier
ESs and included as part of ICM11.5(1) ES31:
|
ES# |
Identifier |
Severity |
Component |
Headline |
|
26 |
CSCvf78757 |
2 |
pg.cucm |
CUCM PG (EAPIM) crash during Network Blind Transfer call flow |
|
30 |
CSCve75922 |
3 |
pg.cucm |
Agents not sent to wrapup after device failure with LOAD 1 |
|
30 |
CSCvf67430 |
3 |
pg.cucm |
Logout
non-activity timer is not reset when Not Ready reason code is changed. |
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: