This document provides
installation instructions for Unified CCE 12.5(1) ES91. 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.
.
This section lists the Unified
CCE components on which you can and cannot install this engineering special.
You can install Unified CCE
12.5(1) ES91 on these Unified CCE components:
Do not install this engineering
special on any component other than:
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 12.5(1) ES91.
Caveats in this section are
ordered by Unified CCE component, severity, and then identifier.
|
|
Severity |
Component |
Headline |
||
|
CSCvz26111 |
2 |
web.config.ui |
Configuration in Call Settings - Miscellaneous cannot be saved in SPOG for PCCE |
||
|
CSCvy91067 |
3 |
web.config.api |
Tomcat OutOfMemoryError due to SQL Delay |
||
|
CSCvz10953 |
3 |
web.config.ui |
Cannot edit status or schedule on multiple Outbound campaigns in SPOG if some have AMD disabled |
||
|
CSCvz21484 |
3 |
web.config.api |
Import API requests at the same millisecond results in “Session was already closed” failure |
||
Caveats
are ordered by severity then defect number.
Defect Number: CSCvz26111
Severity: 2
Headline: Configuration in Call Settings>Miscellaneous
cannot be saved in SPOG for PCCE
Symptom: When the
user goes to the Call Settings>Miscellaneous and they do any change (in any
of the two tabs, Global or Main Site), if they click on Save, they get the
message "Successfully Saved". However, the configuration is not saved
and can be seen that it is still unchanged in the tab.
Conditions: Call Settings>Miscellaneous
update any field is not saving.
Workaround: No
workaround available.
Further Problem Description: None
Defect Number: CSCvy91067
Severity: 3
Headline: Tomcat OutOfMemoryError due to SQL Delay
Symptom: Tomcat goes out of memory due to SQL
insertion delay.
0003170320: 10.17.46.12: Jun 24
2021 23:19:11.727 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-2-3-REST_API_EXCEPTION:
%[exception=java.lang.OutOfMemoryError:
Java heap space][message_string=uncaught exception
thrown by the api]: The REST API has caught an
exception
Conditions: SQL delay in inserting the records
to DB.
Example: 1925
secs (~30mins)
for contacts to be inserted into DL.
0003170346:
10.17.46.12: Jun 24 2021 23:30:24.462 +0530:
%CCBU_ajp-nio-127.0.0.1-8009-exec-3-6-REST_API_INFO: Time to take to write into the database
for 1000 records is
1925225
Workaround: Restart
the Tomcat.
Further Problem Description: None
Defect Number: CSCvz10953
Severity: 3
Headline: Cannot edit status or schedule on multiple Outbound campaigns in SPOG if some have AMD disabled
Symptom: Multiple
campaigns cannot be edited at the same time in SPOG (regarding the Status and
the schedule) if at least one of the campaigns has AMD disabled.
The user will get the error:
"Campaign(s) cannot be
updated due to one or more errors.
: AMDTreatmentMode:
Unexpected input."
Conditions: Steps to reproduce:
Go to
SPOG>Organization>Campaigns.
Select more than
one campaigns(at least one of them needs to have AMD
disabled) and then Edit>Status and Schedule.
Configure any
change and click on Save.
Workaround: Edit the
campaigns one by one.
or
Enable AMD on all
the campaigns.
Further Problem Description: None
Defect Number: CSCvz21484
Severity: 3
Headline: Import API requests at the same millisecond results in “Session was already closed” failure
Symptom: Import API requests at the same
millisecond results in “Session was already closed” failure.
Conditions: When two or more Import API requests
are sent at the same millisecond
Workaround: The API
request tool can slow down and add 50ms delay between sending API requests as a
workaround
Further Problem Description: None
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: