The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document lists new features, changes, and caveats for the release of Cisco Packaged CCE 9.0(x) software. Details of these features are available in the relevant end-user documentation, which you can find on the Cisco.com Web page for Packaged CCE: http://www.cisco.com/en/US/products/ps12586/tsd_products_support_series_home.html. You can also open Release Notes for prior versions of Packaged CCE from that page.
To install this maintenance release:
Step 1 | Plan and schedule the maintenance period. |
Step 2 | Review all applicable documentation. |
Step 3 | Download the maintenance release from this location: http://software.cisco.com/download/release.html?mdfid=268439622&flowid=5210&softwareid=280840583&release=9.0(3)&relind=AVAILABLE&rellifecycle=&reltype=latest. Download the same maintenance installer for both Unified CCE and Packaged CCE. |
Step 4 | Stop all ICM services. |
Step 5 | Uninstall any ES that are installed on the servers. |
Step 6 | Double-click the maintenance release file to begin the installation. |
The Packaged CCE deployment now supports both the Unified Computing System (UCS) C260 M2 TRC#1 and C240 M3S TRC#1 servers for existing deployments.
Note | Only the UCS C240 M3S TRC#1 server will be available for new Packaged CCE orders. |
To ensure that your server firmware is current, go to http://www.cisco.com/cisco/software/type.html?mdfid=283862072&catid=282558030.
For more information about the UCS C240 M3S TRC#1 server specifications, refer to the Packaged CCE Specifications Guide.
The Packaged CCE deployment now supports both ESXi 5.0 and ESXi Server 5.1 with VM Version 8.
You may use either version. Side A and Side B must be on the same version.
When you created the Data Servers for Side A and Side B, you installed Microsoft SQL Server and enabled autogrowth for the tembdb. For this release, your autogrowth settings for the logger are updated automatically. However, you must manually enable autogrowth for:
After completing the upgrade installation procedure, perform the following steps to update your autogrowth settings.
Packaged CCE now supports Microsoft SQL Server 2008 R2 Standard Edition SP2. Two licenses are required: 1 for the Side A Data Server and 1 for the Side B Data Server.
For more information on the platform specifications for Packaged CCE, see Cisco Packaged CCE Products Specifications Guide.
Defects listed in the following sections are Severity 1 and Severity 2 defects identified by any means, and Severity 3 defects identified by customer-use. These include defects specific to Packaged CCE as well as Unified CCE defects that have an impact on Packaged CCE.
Identifier | Severity | Component | Headline |
---|---|---|---|
3 | pg.opc |
Incorrect call disposition value observed during Multiline call flow |
|
3 | install |
The HDS, AW and Outbound databases do not have the proper autogrowth settings. |
Identifier | Severity | Component | Headline |
---|---|---|---|
2 |
ctios.client |
Memory leak in COM Cil using all calls monitor mode |
|
2 |
install |
ICM Install on non-English OS does not add Firewall exceptions |
|
2 |
router |
DBAgent restarts when AW takes too long to send transaction |
|
2 |
db.logger |
No recovery from Logger A to B for historical tables after B was down/up |
|
2 |
outbound |
Campaign Manager crash observed in 450 campaign |
|
2 |
pg.opc |
Access entire bug record in CDETS |
|
3 |
serviceability.snmp |
BA_SIP notification incorrect cccaEventState |
|
3 |
pg.cucm |
Agent gets stuck in Talking state |
|
3 |
pg.cucm |
Mobile Agent - logout reason code is wrong if call dropped while wrap up |
|
3 |
pg.cucm |
Receive control failure when completing conference to PSTN |
|
3 |
pg.cucm.jtapi |
Conf Controller wrong when PG fails when consult call in alerting 60s |
|
3 |
scripteditor |
Access to Script Editor becomes blocked when making API config changes |
|
3 |
serviceability.snmp |
BA_SIP notification has incorrect cccaEventState |
|
3 |
router |
Incorrect correlation ID range results in reporting problems |
|
3 |
tools |
PG setup asserts with error message while editing pim |
|
3 |
pg.opc |
Unexpected CallType for single step transfer call after PG failover |
|
3 |
db.logger |
Transaction log for database is full in 10mins during longevity |
|
3 |
pg.cucm.jtapi |
Call state not correctly reset when request to barge a conf call fails |
|
3 |
web.setup |
Unable to remove Administration clients in Administration Client setup |
|
3 |
router |
PQ gadget returns 0 agent counts while running agent bulk operation |
|
3 |
pg.opc |
OnHold field is not updating correctly in Agent_Real_Time |
|
3 |
outbound |
Date time in dialer detail table updating 1 hr lesser than the system time |
|
3 |
pg.cucm |
Eagtpim crash producing Mini dump during longetivity load |
|
3 |
reporting.webview |
Showing incorrect value for expanded call variables in admin page |
|
3 |
pg.cucm.jtapi |
conf. receiver CTIOS desktop grays out upon conference call flwd by trnf |
|
3 |
pg.acmi |
Extension field is not updating in Agent Logout table at parent side |
|
3 |
pg.cucm.jtapi |
Call failures during load with CD-1 |
|
3 |
outbound |
Callback records with same DialingListID are considered as duplicate |
|
3 |
pg.acmi |
Auto config is not working properly in Parent-Child deployment under cer |
|
3 |
pg.opc |
TCD.TalkTime incorrect |
|
3 |
router |
db agent periodically stops responding under heavy call load |
|
3 |
pg.cucm.jtapi |
Starting a conference after an consult call alternation fails |
|
3 |
scripteditor |
Script Ed crashes for PQ configuration when reload config button clicked |
|
3 |
user_interface |
CCEADMIN PCCE administration webpage fails to finish loading |
|
3 |
pg.opc |
Calls in progress not matching actual calls |
|
3 |
pg.cucm.jtapi |
Silent Monitoring gives only one way, when CLID is " " (empty) |
|
3 |
cg.ctiserver |
AGENT_TEAM_CONFIG_EVENT is not getting the correct AgentID |
|
3 |
outbound |
Dialer shows DIAL_ERROR for SIP resp 404 with cause20(SUBSCRIBER_ABSENT) |
|
3 |
outbound |
Dialer transfer fails if UPDATE arrives after SIP REFER |
|
3 |
outbound |
Callback Records with same DialingListID are considered as duplicate |
|
3 |
router |
Calls handled in CT not incremented when activity queued for long time |
|
3 |
web.config.ui |
Webconfig timeout error making config changes when AD is slow |
|
3 |
tools |
Data access error pop up found on icmdba tool |
|
3 |
outbound |
Dialer not setting the correct call result |
|
3 |
outbound |
CampaignManager stops pushing records to dialer after network failure |
|
3 |
outbound |
Dialer_Detail table CustomerTimeZone field is one hour off for 787 340 |
|
3 |
outbound |
CampaignManager asserts in 300 campaign load with ACCESS_VIOLATION error |
|
3 |
aw.tools |
Re-skilling webpage not working after apply MR patch |
|
3 |
router |
Router is asserting on executing get_config command through RTTEST |
|
3 |
ctios.client |
CTIOS 8.5(4) ctiosphone.exe won't run on Win7 |
|
3 |
ctios.client |
CTIOS 9.0 Toolkit missing debug libraries |
|
3 |
reporting |
Agent queue Interval shows incorrect calls handled and PctActive |
|
3 |
reporting |
CUIC transition reports do not address precision queue |
|
3 |
web.config.ui |
UCCE web login is allowed to supervisors |
|
3 |
reporting |
Agent queue interval report incorrect data |
|
3 |
reporting |
Agent skill group historical all fields does not report precision queues |
For Cisco Packaged CCE troubleshooting tips, go to Cisco Documentation Wiki at http://docwiki-dev.cisco.com/wiki/Category:Unified_Contact_Center_Enterprise.
You can provide comments about this document by sending email to the following address:
mailto: ccbu_docfeedback@cisco.com
We appreciate your comments.
If you have an account with Cisco.com, you can use Cisco's Bug Search tool to find detailed information about defects.
To use the Bug Search tool, visit https://www.cisco.com/cisco/psn/bssprt/bss.