This document provides installation instructions for Unified CCE 11.6(1) ES44. 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.6(1)
This section lists the Unified CCE components on which you can and cannot install this engineering special.
You can install Unified CCE 11.6(1) ES44 on these Unified CCE components:
Do not install this engineering special on the components other than the following components:
Installation of this patch requires that all Unified CCE services
be shut down during the entire period of installation. It is always
recommended to install this ES during a scheduled downtime.
If the Unified CCE Services are set to manual, using the Unified
CCE Service Control, start all the Unified CCE Services.
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(1) ES44.
Caveats in this section are ordered by UNIFIED CCE component, severity, and then identifier.
|
Identifier |
Severity |
Component |
Headline |
|
CSCvf48226 |
2 |
outbound |
Dialer
does not dial out any calls when registered with Standby Campaign Manager
during CM failover |
|
CSCvi10693 |
2 |
outbound |
Outbound
Campaign Manager restarts with minidump when
Campaign is disabled using REST API |
|
CSCvk06453 |
2 |
outbound |
Outbound
Dialer dials out to Customer Phone Numbers contained in Do Not Call List |
|
CSCvj59379 |
3 |
outbound |
Personal
Callback is scheduled with incorrect time if 2nd PCB scheduled when DST is
Active |
|
CSCvk69877 |
3 |
outbound |
Campaign
Manager Standby Side keeps Accumulating Memory (process private bytes) |
Caveats are ordered by severity then defect number.
Defect Number: CSCvf48226
Component: outbound
Severity: 2
Headline: Dialer does not dial out any calls when registered with Standby Campaign Manager during CM failover
Symptom:
Active Dialer does not dial out to any customer phone numbers.
Conditions: The issue is known to occur when the active side Campaign
Manager is cycled and failover is done to the other side, such that the Dialer
becomes active with the Standby Campaign Manager.
Workaround: Stop and Start both sides of Campaign Manager(s).
Further Problem Description:
Defect Number: CSCvi10693
Component: outbound
Severity: 2
Headline: Outbound Campaign Manager restarts with minidump when Campaign is disabled using REST API
Symptom:
Outbound Campaign Manager restarts, producing a minidump.
The failure typically occurs only intermittently.
Conditions: Disable the Campaign using the REST API (the Campaign was
originally created also using the REST API).
Workaround: N/A
Further Problem Description: This is known to be a timing issue and occurs
intermittently when the Dialer requests the customer records for the Campaign
at the same time the Campaign is being disabled using the REST API. Note:
Campaigns created using the REST API can be edited/updated/disabled/deleted
using only the REST APIs.
Defect Number: CSCvk06453
Component: outbound
Severity: 2
Headline: Outbound Dialer dials out to Customer Phone Numbers contained in Do Not Call List
Symptom:
Outbound Dialer is dialing out to customer phone numbers included in the Do Not
Call List.
Conditions: The issue is known to occur when Do Not Call phone numbers are
imported using the Do Not Call Import file, and one or both of the following
conditions exist: 1. The entries in the Do Not Call import file are separated
by comma (','). Example: 1234567890, 0123456789, 2. There are entries in the Do
Not Call Import file that contain both Phone number and extension, and each is
separated by a comma (','). Example: 1234567890,1234 0123456789,0123.
Workaround: 1. If the Do Not Call entries in the
Do Not Call Import File contain only Phone Numbers, remove all commas (',')
from the Do Not Call Import file. 2. If the Do Not
Call entries in the Do Not Call Import File contain Phone Numbers and
Extensions, use Pipe Delimited or Fixed format instead of Comma Delimited.
Further Problem Description: When the Do Not Call
list entries are imported with the comma (','), the Do_Not_Call
table in the Outbound database is updated with right phone numbers and
extensions. Querying the Do Not Call list in Campaign Manager using procmon, however, responds that the number is not in the
list. Note that "donotcall" is the procmon command used to check the Do Not Call list from
Campaign Manager's memory.
Defect Number: CSCvj59379
Component: outbound
Severity: 3
Headline: Personal Callback is scheduled with incorrect time if 2nd PCB scheduled when DST is Active
Symptom: The
"Current Time" and "Callback Time" is incorrect in the
Callback scheduling UI if the Agent schedules a follow-on Personal Callback
call while talking to the customer on the original Personal Callback call. If
the Agent fails to notice the resulting incorrect Callback Time in the UI and
schedules the next Personal Callback call by adding minutes to the currently
shown Callback Time, the Dialer may schedule the Personal Callback in the past.
Conditions: 1. An additional Personal Callback call is scheduled while
talking to a customer on a Personal Callback call. 2. Daylight Savings Time is
active in the Customer Time Zone.
Workaround: Agent could correct the Callback time in the UI and schedule
the PCB in the correct (customer normalized) time.
Further Problem Description:
Defect Number: CSCvk69877
Component: outbound
Severity: 3
Headline: Campaign Manager Standby Side keeps Accumulating Memory (process private bytes)
Symptom:
Campaign Manager Standby side keeps accumulating memory (process private
bytes), as shown in Resource Monitor. The issue does not occur on the Active
side.
Conditions: Outbound Option High Availability is enabled.
Workaround: None.
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: