This document provides installation instructions for Unified CCE 11.6(2) ES85. 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 behaviour.
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 engineering special adds the ability to send DTMF tones
via the Avaya TSAPI Peripheral Gateway(PG) to exercise Take-Back and Transfer
feature provided by the carrier network. The DTMF tones may be invoked by the
transferring Agent directly using the CTI link interface or by placing a post
route call to ICM Router which then returns a label starting with a prefix of
“DTMF” followed by the DTMF sequence that needs to be out pulsed by
the Avaya Communication Manager (ACM).
With the use of the DTMF label, the following steps are performed when transferring calls inter-switch:
1. An
agent receives an inbound call.
2. The
agent then begins a consultative call or single step transfer by dialling
(#8XXX or speed dial #). A new call is initiated that send a Post-Route Request
to Unified ICM Router.
3. Unified
ICM response to the Post-Route request is a label of the form DTMF*8xxxxxxxx .
The DTMF prefix in the label informs the PIM that it must perform a Carrier
Call Transfer by instructing ACM to out-pulse DTMF tones.
·
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) ES85 on these Unified CCE components:
Do not install this engineering special on any other component other than the Avaya TSAPI PG
Installation
of this patch requires all Unified CCE services to be shut down on the PG
machine and should hence be carried out in a scheduled maintenance window.
·
Stop the Avaya TSAPI PG service using the
Unified CCE Service Control
· Launch the ICM 11.6(2) ES85 installer and follow the on-screen instructions
· Start the Avaya TSAPI PG service using the Unified CCE Service Control
Please
note: Apply this engineering special on both sides of the duplexed Avaya
TSAPI PG pair.
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) ES85.
Caveats in this section are ordered by UNIFIED CCE component, severity, and
then identifier.
Identifier |
Severity |
Component |
Headline |
CSCvr99349 |
3 |
pg.tdm |
VDN monitoring not being re-attempted if initial monitoring failed due to congestion error from AES |
CSCvz71475 |
6 |
pg.tdm |
Avaya
TSAPI PG could not process the DTMF request and impacting call failures |
Caveats are ordered by severity then defect number.
Defect Number: CSCvr99349
Component: pg.tdm
Severity: 3
Headline: VDN monitoring not being re-attempted if initial monitoring failed due to congestion error from AES
Symptom: Not all splits or VDN's on the Avaya Communication Manager
(ACM) get monitored by the Avaya (Definity) PG with the PIM component logs
having traces like the following: -
[TSAPILIB] Universal Failure
confirmation received as : Driver congestion for Request type: Unknown CSTA
Event Type(113)
Conditions: Unified ICM integration with
Avaya ACM using the Avaya (Definity) PG over the TSAPI interface and having
many resources (greater than 4000) to monitor on the switch.
Workaround:
None
Further Problem Description:
Defect Number: CSCvz71475
Component: pg.tdm
Severity: 6
Headline: Avaya TSAPI PG could not process the DTMF request and impacting call failures
Symptom:
Avaya TSAPI PG could not process the DTMF request and impacting call failures
Conditions: When trying to use "dtmf"
digits while agent is on the call.
Workaround: NA
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: