About this Document
This document provides installation instructions for Unified CCE 12.0(1) ES49. 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 behavior of Unified CCE.
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.
Install ES49 after installing ES37 in all Packaged CCE deployments. ES37 patch can be downloaded from :
https://software.cisco.com/download/specialrelease/7779234b1cb167ee442b383bc6caf4ed
Along
with fixes for the defects specified below, this Engineering Special also
includes support for the following features of PCCE 12.0(1):
- Desktop Layout Editors
The following Desktop Layout editors are available in the Teams and Resources pages of the Unified CCE Administration.
Text Editor : Allows you to view and edit code in text format. It is the default editor.
XML Editor : Allows you to view and edit code in XML format. However, you cannot add or edit comments () in this editor.
- Support for hostname or IP address change of 12.0(1) PG in PCCE Technology Refresh upgrade.
Note: PCCE Technology Refresh upgrade support is available from future releases.
Unified CCE Version Support
UCCE 12.0(1)
Unified CCE Component Support
This section lists the Unified CCE components on which you can and cannot install this engineering special.
Supported Unified CCE Components
You can install Unified CCE 12.0(1) ES49 on these Unified CCE components:
- AW
- PG(For hostname or IP address change of 12.0(1) PG in PCCE Technology Refresh upgrade)
This engineering special (ES49) is not supported on other components
Shut down all CCE services during the installation. It is always recommended to
install this ES during a scheduled downtime.
1.
Using the CCE Service Control, stop all the CCE
services running on the system
2.
Launch the Installer provided for this ES and
follow the instructions on the screen
3.
Using the CCE Service Control, start all CCE
services again.
If you are having a Fresh Install/Tech Refresh of P/CCE 12.0(1)
2016, before applying any ES, run the mandatory update. You can
download CCE Mandatory Update for 12.0 Fresh Install/Tech Refresh
from:
https://software.cisco.com/download/home/268439622/type/280840583/release/12.0(1)
- To uninstall this patch, go to Control Panel.
- Select "Add or Remove Programs".
- Find the installed patch in the list and select "Remove".
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.
Resolved Caveats in this Engineering Special
This section provides a list of significant Unified CCE defects resolved by this engineering special. It contains these subsections:
- Resolved Caveats in Unified CCE 12.0(1) ES49
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.
Resolved Caveats in Unified CCE 12.0(1) ES49
This section lists caveats specifically resolved by Unified CCE 12.0(1) ES49.
Index of Resolved Caveats
Caveats in this section are ordered by UNIFIED CCE component, severity, and then identifier.
Identifier |
Severity |
Component |
Headline |
CSCvs41895 |
1 |
dbconfig |
PCCE4k: CUCM subscribers are auto discovered while performing inventory update on CM publisher |
CSCvn99825 |
2 |
dbconfig |
CVP server deploy fails while creating remote site when CVP hostname is given |
CSCvo46854 |
2 |
dbconfig |
ECE goes OOS when the department is getting created |
CSCvo78127 |
2 |
dbconfig |
SipServerGroup issues |
CSCvp03348 |
2 |
dbconfig |
unable to create main site in PCCE 12k. |
CSCvp11040 |
2 |
dbconfig |
Dialed Number Bulk DELETE does not work in PCCE 4K/12K |
CSCvp18469 |
2 |
dbconfig |
Internal server error seen when trying to open SPOG miscellaneous page |
CSCvp20817 |
2 |
dbconfig |
Remote Network Routing in Router gets disabled while creating new peripheral set |
CSCvp28792 |
2 |
dbconfig |
Fresh Install wizard throws error for ESXi C240 M4 servers for PCCE 2K |
CSCvp30895 |
2 |
dbconfig |
In PCCE 4K/12K, Capacity Info is Wrongly calculated for SkillGroups and other Config items |
CSCvp32924 |
2 |
dbconfig |
checkIfPeripheralConfigurationChanged & getECEHosts tasks fails with NullPointer exception |
CSCvp37092 |
2 |
dbconfig |
Gateway IPaddress to Hostname mapping creates problem while adding gateway in device configuration |
CSCvp47032 |
2 |
dbconfig |
More validations needs to be added during peripheral set deletion in PCCE 4k/12k deployment |
CSCvp47242 |
2 |
dbconfig |
Router Public Interfaces are getting changed during Peripheral Set creation/deletion |
CSCvp57531 |
2 |
dbconfig |
Enable Database Routing in Router gets disabled while creating/deleting Peripheral set |
CSCvp58853 |
2 |
dbconfig |
ECE goes OUT_OF_SYNC when agent password does not comply with the password policy |
CSCvp59306 |
2 |
dbconfig |
Can not create Dial Number when we have same peripheral set name across sites |
CSCvp60962 |
2 |
dbconfig |
Principal AW health status stays as ERROR when diag portal service starts after Tomcat service |
CSCvp64750 |
2 |
dbconfig |
Tomcat crash observed while handling config transactions |
CSCvp76696 |
2 |
dbconfig |
Default Config Creation in Social Miner fails while adding SM to cce inventory |
CSCvp89228 |
2 |
dbconfig |
PCCE SPOG missing default route configuration on CVP |
CSCvp96392 |
2 |
dbconfig |
CVP goes out of sync while adding gateway to locations |
CSCvq12348 |
2 |
dbconfig |
Departmental Administrator not allowed to create agent or enable Email & Chat support |
CSCvq67966 |
2 |
dbconfig |
ECE goes out of sync when we perform Agent Update operation |
CSCvq88066 |
2 |
dbconfig |
PCCE v12 Supervisor re-skilling agent/skills page blank after installing ES21 |
CSCvr51613 |
2 |
dbconfig |
PCCE 4K/12K CVVB Inventory Import Fails |
CSCvr90903 |
2 |
dbconfig |
HDS disk size needs to updated for PCCE deployment |
CSCvs12341 |
2 |
dbconfig |
SSO component registration is failing for CUIC subscribers in PCCE 4K deployment |
CSCvs23301 |
2 |
dbconfig |
PCCE 12k Agent bulk creation aborted due to congestion |
CSCvs25265 |
2 |
dbconfig |
Peripheral set capacity rules creation is not working |
CSCvs42013 |
2 |
dbconfig |
Media Server orchestration failing |
CSCvn77418 |
3 |
dbconfig |
Incorrect error thrown on deleting gateways associated with location |
CSCvn77421 |
3 |
dbconfig |
IdS is reporting incorrect status in SPOG UI |
CSCvn78159 |
3 |
dbconfig |
In SPEC based deployment, status rules do not run. |
CSCvn78163 |
3 |
dbconfig |
Campaign Skill group Search Pop-over is not working as expected |
CSCvn79565 |
3 |
dbconfig |
Campaign Multi-edit popup and contacts template issues |
CSCvn82112 |
3 |
dbconfig |
DeploymentSettings and SignOut Ui issues in Fresh Install |
CSCvn92277 |
3 |
dbconfig |
enforce wrapup code missing for PCCE 12.0 |
CSCvo15059 |
3 |
dbconfig |
Inconsistent behavior for 'Cancel' button click in Device Configuration UI |
CSCvo28848 |
3 |
dbconfig |
Run time status rules task is failing-for PCCE spec based harware |
CSCvo45192 |
3 |
dbconfig |
PG explorer marks entries as modified during normal traversal |
CSCvo59157 |
3 |
dbconfig |
PCCC 12.0 SIP Header Passing to ICM should not require parameter |
CSCvo61931 |
3 |
dbconfig |
Updating an ECE Agent with same screenName, ECE goes to out-of-sync |
CSCvo66492 |
3 |
dbconfig |
SPOG ECE Agent Screen Name does not allow spaces |
CSCvo85717 |
3 |
dbconfig |
Post Call Survey DN limit needs to be updated in PCCE 2k deployment |
CSCvo98128 |
3 |
dbconfig |
Disable Routing Client names in PG Explorer (UCM , VRU , MR PG) for PCCE deployment |
CSCvp11036 |
3 |
dbconfig |
Unable to create Agents and AgentTeam using bulk job in PCCE 4K/12K |
CSCvp20793 |
3 |
dbconfig |
Not able to delete Peripheral set under certain conditions |
CSCvp21111 |
3 |
dbconfig |
Device Hostname is truncated with an Error message in CVP Stats dialog |
CSCvp28803 |
3 |
dbconfig |
PCCE Fresh Install wizard is displaying PCCE 4K and 12K deployment types |
CSCvp36895 |
3 |
dbconfig |
Roles are not loading in Administrator gadget |
CSCvp38942 |
3 |
dbconfig |
PCCE disk size validation should be relaxed to include sizing consideration for Outbound Database |
CSCvp47136 |
3 |
dbconfig |
Transferable Files File Upload API endpont has to be changed |
CSCvp66880 |
3 |
dbconfig |
Custom Role user gets all Navigation menu's in cceadmin |
CSCvp68561 |
3 |
dbconfig |
Gateway deletion from inventory should not happen when it is mapped in CVP device configuration |
CSCvp83276 |
3 |
dbconfig |
PCCE Machine Limits need correction |
CSCvp86341 |
3 |
dbconfig |
ECE Differential sync fails under certain condition |
CSCvp86346 |
3 |
dbconfig |
populateExternalPageFeaturesFromCodes message filling up Tomcat logs |
CSCvp93416 |
3 |
dbconfig |
Registration of Context Service shows undefined |
CSCvp98507 |
3 |
dbconfig |
ECE Agent created using Bulk job do not get propagated to ECE. |
CSCvq00400 |
3 |
dbconfig |
Failed to retrieve placement of external page when card with no menu's exists in between |
CSCvq03314 |
3 |
dbconfig |
Not able to create agents belonging to departments in PCCE4k / 12k deployments |
CSCvq06932 |
3 |
dbconfig |
Providing wrong credentials while selecting Principal AW from CCEAdmin does not throw error |
CSCvq12588 |
3 |
dbconfig |
In PCCE 4K,In IE browser, Sync Staus layout is broken in Inventory |
CSCvq27469 |
3 |
dbconfig |
Inventory and Features page not loading post Contact Director deployment set |
CSCvq32445 |
3 |
dbconfig |
SPOG UI: Inventory alerts rules messages are truncated in the middle and not understandable. |
CSCvq33205 |
3 |
dbconfig |
If External machine name contains a long string, name is coming out of the delete popover in IE |
CSCvq35784 |
3 |
dbconfig |
Help icon is missing in New Site dialog in IE browser |
CSCvq46558 |
3 |
dbconfig |
'Select All' option is deselected in Departments summary view |
CSCvq54170 |
3 |
dbconfig |
PS deletion should check for machines membership in Sip server group |
CSCvq62990 |
3 |
dbconfig |
CVP DNIS API accepts more than 32 characters in each DNIS |
CSCvq64857 |
3 |
dbconfig |
Deletion of single DN using Bulk Job Deletion works however failed message is thrown. |
CSCvq99289 |
3 |
dbconfig |
PCCE alert: MR PIM and node manager trace level warning |
CSCvr17986 |
3 |
dbconfig |
PCS dialnumbers are not considered in Capacityrule when "PCS EnabledDialedNumberPatterns" configured |
CSCvr51586 |
3 |
dbconfig |
PCCE 4K/12K PG 1, 2 and 3 are not deleted via the Inventory Import Revert Tasks |
CSCvr72278 |
3 |
dbconfig |
Agent Teams deleted in PCCE 12.0 are not deleting the corresponding teams in CUIC |
CSCvr99898 |
3 |
dbconfig |
PCCE 12K inventory does not show more than 45 vm |
CSCvs08501 |
3 |
dbconfig |
Regular Hours table data is missing in Business Hours in IE browser |
CSCvs13583 |
3 |
dbconfig |
Unable to add Administrator in System Default role using Role Gadget. |
CSCvs17596 |
3 |
dbconfig |
CCEAdmin does not show peripheral value of Agent in UCCE 4k deployment |
CSCvs21511 |
3 |
dbconfig |
PCCE 12K: HDS fails to register to SSO mode |
CSCvs24355 |
3 |
dbconfig |
PCCE 4K/12K deployment does not list System Options under Outbound option menu |
CSCvs31166 |
3 |
dbconfig |
In IE browser, Sync dialog is not opened on clicking Sync icon |
CSCvs32861 |
3 |
dbconfig |
Only first AW credentials are used to setup PCCE4k/12k deployment |
CSCvs33853 |
3 |
dbconfig |
SPOG Campaign Download all Contacts option not working |
CSCvs36134 |
3 |
dbconfig |
Bulk Update or Create of an Agent is failing with error "team name is required and cannot be empty" |
CSCvs41738 |
3 |
dbconfig |
Unable to create Dialed Number for Remote site in PCCE 4k Bulk Job |
CSCvs60065 |
3 |
dbconfig |
PCCE cuic sync sets OutOfSyncTimestamp to 1970 |
CSCvs64183 |
3 |
dbconfig |
CCE Administration Registration Failure |
CSCvs77949 |
3 |
dbconfig |
Agents with TraceON enabled for 12k is 400 in Doc vs 100 in System Capacity (pcce webadmin) |
CSCvs96235 |
3 |
dbconfig |
PCCE exeeded configuration limit should not trigger Service Busy state |
CSCvt09634 |
3 |
dbconfig |
PCCE 4K/12K day 1 validations are not exercised for both Main Site and Remote Sites |
CSCvt60373 |
3 |
dbconfig |
Alerts status is showing as greyed out in PCCE2K |
CSCvt65656 |
3 |
dbconfig |
Database API Exceptions are not handled during PCCE 4K/12K fresh install |
CSCvt65662 |
3 |
dbconfig |
NullPointerException during PCCE 4K/12K fresh install when Rogger is simplexed in the CSV |
CSCvt73896 |
3 |
dbconfig |
Overview page is blank in non PCCE deployment (like UCCE and HCS) in 12.0 ES37 |
CSCvt75129 |
3 |
dbconfig |
MR PG Peripheral,Routing Client name inconsistency for Core and Remote site causes validation errors |
CSCvt98567 |
3 |
dbconfig |
Need to update System Validations in PCCE 2K. Only one of Type 2 and Type 10 Network VRUs allowed |
CSCvt98590 |
3 |
dbconfig |
Unable to create more than one Application Instance in PCCE 2K |
CSCvu12137 |
3 |
dbconfig |
Error alert is observed for MR PG in PCCE CCEAdmin Inventory page |
CSCvn71946 |
4 |
dbconfig |
Advanced search for IP Address in inventory throws an internal server error |
CSCvn78580 |
4 |
dbconfig |
Minor alignment issues in IE |
CSCvo35666 |
4 |
dbconfig |
PCCE: domain admin can still see removed tools from config manager |
CSCvo61941 |
4 |
dbconfig |
ECE Database Server is referred as services server in edit page of the inventory |
CSCvo94307 |
4 |
dbconfig |
Filter DN to Label Mapping option in PG Explorer for CUCM PG ( PCCE 4k/12k ) |
CSCvp28327 |
4 |
dbconfig |
Choosing "Agent State after RONA" to "Ready" in PCCE Desk Settings trigger System validation alert. |
CSCvp48558 |
4 |
dbconfig |
No scrolling for sites in IVR Filetransfer screen if there are more sites |
CSCvq13988 |
4 |
dbconfig |
database transaction failed error shown to user if we use same value(case sensitive) in Username |
CSCvs45079 |
4 |
dbconfig |
FTP password is visible in the logs |
CSCvu09271 |
4 |
dbconfig |
PG VM shows incorrect alarm related to Dialer process even when it is active |
CSCvt07963 |
5 |
dbconfig |
[VPAT Observation] Keyboard visual focus is not visible on some elements |
CSCvq14472 |
6 |
dbconfig |
ECCPayload API does not work in Packaged CCE deployments despite the API guide claiming support |
CSCvp12852 |
3 |
doc |
Edit Attributes for Multiple Agents Option missing in PCCE 11.6 GUI |
CSCvp36907 |
4 |
doc |
Application gateway gadget OLH incorrect about support for IP address change |
CSCvo71587 |
3 |
install |
Websetup doesn't come up after installing ICM12.0(1)_ES6 |
CSCvr21614 |
2 |
template |
Orchestration doesn't happen when we do agent multi delete from non-principal AW |
CSCvs64057 |
2 |
template |
Reason Codes doesn't show in Teams gadget for the first time |
CSCvo91661 |
3 |
template |
Courtesy Callback page issues |
CSCvp19303 |
3 |
template |
DataCenter based sorting is not working in DialNumber page |
CSCvp23552 |
3 |
template |
Accessibility issues in cceadmin |
CSCvp98528 |
3 |
template |
Edit button should be disable when we select agents from different Peripheral Sets |
CSCvq47995 |
3 |
template |
Stats icon missing for external CVP Reporting server |
CSCvq78029 |
3 |
template |
Search doesn't work in Sip server group Site selection |
CSCvq95029 |
3 |
template |
API exceptions observed while redirecting to RouteSettings page in cceadmin |
CSCvr09420 |
3 |
template |
Able to remove Principal check for AW in cceadmin |
CSCvr55052 |
3 |
template |
PCS DN Routing Type changes to External Voice after edit |
CSCvr84124 |
3 |
template |
After fresh install of PCCE 4k, not able to update inventory without restarting Tomcat |
CSCvs16800 |
3 |
template |
Help File for PCCE 4k deployment is showing detail for non-packaged deployment type |
CSCvs23235 |
3 |
template |
Resize columns not working in PCCE 4k inventory page |
CSCvs26988 |
3 |
template |
PCCE4k: Inventory Machine credentials are not editable |
CSCvs39941 |
3 |
template |
Not able to update credentials for HDS machine in PCCE 4K/12K |
CSCvs48546 |
3 |
template |
SSO supervisor : cceadmin fails to load due to bundle mismatch |
CSCvs56462 |
3 |
template |
Miscellaneous page fails to load with InternalServerError when there are no NetworkVRU's in system |
CSCvt05248 |
3 |
template |
In 4k, While deleting a peripheral set, the validation errors are not getting listed in UI |
CSCvp37039 |
4 |
template |
Not able to add users to ScriptAdmin role |
CSCvq95394 |
4 |
template |
Missing details in Keyboard Shortcuts popover |
CSCvq03677 |
2 |
web.config.api |
PCCE2k: LD remains in UNAVAILABLE as login failed for user 'livedatauser' created by PCCE |
CSCvq07040 |
2 |
web.config.api |
CUIC Out-of-Sync post failover operation in the PCCE2k-SPOG inventory |
CSCvs04669 |
2 |
web.config.api |
Bulk Agent edit using PCCE for enabling ECE option for agent fails |
CSCvs40373 |
2 |
web.config.api |
Existing Agents Unable to be Enabled for ECE After Application of PCCE ES34 |
CSCvq01988 |
3 |
web.config.api |
Personal callback DELETE API always returns a 404 |
CSCvq27248 |
3 |
web.config.api |
Supporting ECC API deficient in UCCE deployments |
CSCvq33281 |
3 |
web.config.api |
PCCE2K-SPOG: Miscalculation/Representation of Total Alerts in the Inventory (Build #288) |
CSCvq63352 |
3 |
web.config.api |
Alert on the Router Configuration for enabling the Application Gateway using WebSetup in Inventory |
CSCvs77189 |
2 |
web.config.ui |
Cannot Switch to HCS 4K Deployment if Total Dialed Numbers on All CVP Route Clients Exceeds 4000 |
CSCvp34995 |
3 |
web.config.ui |
Unable to Add 20 Custom Gateways if Remote ICM is Configured |
CSCvp36973 |
3 |
web.config.ui |
PCCE SPOG Specific Navigation Menu's made available for UCCE |
CSCvq44602 |
3 |
web.config.ui |
CCEadmin always uses credentials of first CUCM in case of main site and remote site deployment |
CSCvq45077 |
3 |
web.config.ui |
MR PG's not available under the configuration in UCCE Admin for SocialMiner (HCS 2K) |
CSCvq85125 |
3 |
web.config.ui |
Switching to NAM(Deprecated) stuck at loading for long and after Inventory not displayed |
CSCvr05766 |
3 |
web.config.ui |
Online help missing on SingleSignon(SSO) Page of Webadmin |
CSCvr33101 |
3 |
web.config.ui |
Unable to set trace levels from secondary AW for Log Collection in PCCE 2K Deployment |
CSCvr49943 |
3 |
web.config.ui |
Unable to save CUIC/IDS/Livedata config / incorrect error message |
CSCvr72636 |
3 |
web.config.ui |
SSO supervisors gets blank screen when SPOG page is refreshed |
CSCvr81939 |
3 |
web.config.ui |
In Dialed Number gadget, incorrect Routing Types are shown for MR Peripherals |
CSCvp48927 |
4 |
web.config.ui |
ALL-LANG: UCCE/PCCE WebAdmin: Calendar and time are not localized in Business Hours menu |
CSCvp92559 |
2 |
web.setup |
websetup router API throws java.lang.NumberFormatException while creating router |
Detailed list of Resolved Caveats in This Engineering Special
Caveats are ordered by severity then defect number.
Defect Number: CSCvs41895
Component: dbconfig
Severity: 1
Headline: PCCE4k: CUCM subscribers are auto discovered while performing inventory update on CM publisher
Symptom:
PCCE4k: CUCM subscribers are auto discovered while performing inventory update on CM publisher
Conditions:
while performing inventory update on CM publisher
Workaround:
None
Further Problem Description:
Defect Number: CSCvn99825
Component: dbconfig
Severity: 2
Headline: CVP server deploy fails while creating remote site when CVP hostname is given
Symptom:
Remote site creation fails
Conditions:
CVP server hostname provided while creating remote site
Workaround:
none
Further Problem Description:
CVP server deploy fails while creating remote site when CVP hostname is given.
NULL pointer exception seen as Primary CVP Host comes as NULL:
initialization task: DataCenterCVPServerDeploymentTask_sideA
0000006421: 10.10.10.21: Jan 08 2019 06:15:41.240 -0500: %CCBU_539-DATACENTERCONFIGASYNCTASK-6-REST_API_INFO: DataCenterCVPServerDeploymentTask :: Invoking Task
0000006422: 10.10.10.21: Jan 08 2019 06:15:41.245 -0500: %CCBU_539-DATACENTERCONFIGASYNCTASK-6-REST_API_INFO: DataCenterCVPServerDeploymentTask :: Got Primary CVP Host null
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES6 at https://software.cisco.com/download/specialrelease/69571a20478917ff4e4f5045fd73679b
Defect Number: CSCvo46854
Component: dbconfig
Severity: 2
Headline: ECE goes OOS when the department is getting created
Symptom:
ECE goes OOS
Conditions:
Create same department in CCEadmin similar to the one present in ECE
Workaround:
Create with different department name
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES6 at https://software.cisco.com/download/specialrelease/69571a20478917ff4e4f5045fd73679b
Defect Number: CSCvo78127
Component: dbconfig
Severity: 2
Headline: SipServerGroup issues
Symptom:
SipServerGroup will not clear the selected members when site is changed.
Conditions:
Sip Server group creation or modification
Workaround:
NA
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES15 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvp03348
Component: dbconfig
Severity: 2
Headline: unable to create main site in PCCE 12k.
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES15 at https://software.cisco.com/download/specialrelease/db85925c5ae14f035a43ff799c6f6b66
Symptom:
Creation of Main site in 12K deployment fails
Conditions:
12k deployment - Site creation
Workaround:
NA
Further Problem Description:
Defect Number: CSCvp11040
Component: dbconfig
Severity: 2
Headline: Dialed Number Bulk DELETE does not work in PCCE 4K/12K
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES15 at https://software.cisco.com/download/specialrelease/
Symptom:
Deletion of dialed number fails
Conditions:
PCCE 4K and above deployments
Workaround:
NA
Further Problem Description:
Defect Number: CSCvp18469
Component: dbconfig
Severity: 2
Headline: Internal server error seen when trying to open SPOG miscellaneous page
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES15 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvp20817
Component: dbconfig
Severity: 2
Headline: Remote Network Routing in Router gets disabled while creating new peripheral set
Symptom:
Remote Network Routing in Router gets disabled while creating new peripheral set
Conditions:
While creating new peripheral set in PCCE 4k
Workaround:
Edit router setup in websetup and enable Remote Network Routing. Cycle the router afterwards.
Further Problem Description:
Remote Network Routing in Router gets disabled while creating new peripheral set
Defect Number: CSCvp28792
Component: dbconfig
Severity: 2
Headline: Fresh Install wizard throws error for ESXi C240 M4 servers for PCCE 2K
Symptom:
During Fresh Install of PCCE 2K deployment, initialise task is popping up with following below error:
%[error_string=validateInventory:errors after processing inventory = [ApiError[errorType=inventory.MissingMachine, errorData=CVP, errorMessage=CVP not found on vmhost sideA]]][url=]: The REST API has encountered an error
Due to this Fresh Install is completely blocked.
CUCM is in 12.5 version and installed off box.
Conditions:
CUCM is in 12.5 version and installed off box.
ESXI Server C240 M4 with cucm installed off box.
Workaround:
friendly patch has been given.
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES15 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvp30895
Component: dbconfig
Severity: 2
Headline: In PCCE 4K/12K, Capacity Info is Wrongly calculated for SkillGroups and other Config items
Symptom:
Capacity rules are broken for PCCE 4K and PCCE 12K deployments.
Conditions:
PCCE 4K / 12K deployment
Workaround:
None.
Further Problem Description:
Defect Number: CSCvp32924
Component: dbconfig
Severity: 2
Headline: checkIfPeripheralConfigurationChanged & getECEHosts tasks fails with NullPointer exception
Symptom:
checkIfPeripheralConfigurationChanged & getECEHosts tasks fails with NullPointerexception in PCCE4k system
Conditions:
In PCCE 4k system with multiple sites
Workaround:
None
Further Problem Description:
Defect Number: CSCvp37092
Component: dbconfig
Severity: 2
Headline: Gateway IPaddress to Hostname mapping creates problem while adding gateway in device configuration
Will change the RNE Type based on analysis
Symptom:
CVP Orchestration fails
Conditions:
Use Gateway hostname while saving to inventory
Workaround:
Delete and readd Gateway with ip address
Further Problem Description:
Defect Number: CSCvp47032
Component: dbconfig
Severity: 2
Headline: More validations needs to be added during peripheral set deletion in PCCE 4k/12k deployment
Symptom:
peripheral set deletion is allowed from SPOG even When we have ATR or label for any peripherals in PS
Conditions:
When we have ATR or label for any peripherals in PS
Workaround:
Delete the configuration from tools and try out deletion.
Further Problem Description:
Defect Number: CSCvp47242
Component: dbconfig
Severity: 2
Headline: Router Public Interfaces are getting changed during Peripheral Set creation/deletion
Symptom:
Router Public Interfaces are getting changed during Peripheral Set creation/deletion
Conditions:
Peripheral Set creation/deletion
Workaround:
Edit Router and change the ip addresses to original
Further Problem Description:
Defect Number: CSCvp57531
Component: dbconfig
Severity: 2
Headline: Enable Database Routing in Router gets disabled while creating/deleting Peripheral set
Symptom:
Enable Database Routing in Router gets disabled
Conditions:
while creating/deleting Peripheral set
Workaround:
Edit Router and enable it back
Further Problem Description:
Defect Number: CSCvp58853
Component: dbconfig
Severity: 2
Headline: ECE goes OUT_OF_SYNC when agent password does not comply with the password policy
Symptom:
ECE goes OUT_OF_SYNC
Conditions:
When agent password does not comply with ECE's password policy
Workaround:
Sync ECE by performing differential sync . either manually or automatically it gets triggered every 10 mins
Further Problem Description:
Defect Number: CSCvp59306
Component: dbconfig
Severity: 2
Headline: Can not create Dial Number when we have same peripheral set name across sites
Symptom:
Can not create Dial Number when we have same peripheral set name across sites
Conditions:
when we have same peripheral set name across sites
Workaround:
Need to re-create peripheral set with different name.
Further Problem Description:
Defect Number: CSCvp60962
Component: dbconfig
Severity: 2
Headline: Principal AW health status stays as ERROR when diag portal service starts after Tomcat service
Symptom:
Principal AW health status stays as ERROR
Conditions:
when diag portal service starts after Tomcat service
Workaround:
Restart Tomcat service
Further Problem Description:
Defect Number: CSCvp64750
Component: dbconfig
Severity: 2
Headline: Tomcat crash observed while handling config transactions
Symptom:
Tomcat crash occurred with an unrecoverable stack overflow error.
Conditions:
Perform update in Application Instance or Application Path or Application Member
Workaround:
None
Further Problem Description:
Defect Number: CSCvp76696
Component: dbconfig
Severity: 2
Headline: Default Config Creation in Social Miner fails while adding SM to cce inventory
Symptom:
Default Config Creation in Social Miner fails
Conditions:
while adding SM to cce inventory
Workaround:
None
Further Problem Description:
Defect Number: CSCvp89228
Component: dbconfig
Severity: 2
Headline: PCCE SPOG missing default route configuration on CVP
Symptom:
PCCE SPOG missing default route configuration on CVP
Conditions:
Wont be able to configure default route for CVP through SPOG
Workaround:
Not available
Further Problem Description:
The code must allow only ">" or ".*" for default route to work
Defect Number: CSCvp92559
Component: web.setup
Severity: 2
Headline: websetup router API throws java.lang.NumberFormatException while creating router
Symptom:
websetup router API throws java.lang.NumberFormatException while creating router
Conditions:
While using websetup router API directly
Workaround:
None
Further Problem Description:
Defect Number: CSCvp96392
Component: dbconfig
Severity: 2
Headline: CVP goes out of sync while adding gateway to locations
Symptom:
CVP Goes out of sync
Conditions:
Use Hostname for gateway while saving inventory
Workaround:
Delete Gateway from inventory and add it with ip address
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvq03677
Component: web.config.api
Severity: 2
Headline: PCCE2k: LD remains in UNAVAILABLE as login failed for user 'livedatauser' created by PCCE
PCCE2k: LD remains in UNAVAILABLE as login failed for user 'livedatauser' created by PCCE
Symptom:
PCCE2k: LD remains in UNAVAILABLE as login failed for user 'livedatauser' created by PCCE
Conditions:
Post reboot
Workaround:
You also have to reploy live data topology after tomcat restart.
Workaround Steps-
1) Reset AW access on LD publisher . unset live-data aw-access primary
2) Restart AW access on LD publisher . unset live-data aw-access secondary
3) Restart Tomcat services on AW.
4) Restart Nimbus Service ron both publisher and subscriber after ~5 mins of tomcat restart.
Further Problem Description:
Defect Number: CSCvq07040
Component: web.config.api
Severity: 2
Headline: CUIC Out-of-Sync post failover operation in the PCCE2k-SPOG inventory
Symptom:
SPOG was not updating CUIC when supervisor is moved from SSO to Non SSO and/or vice versa.
Conditions:
Observed during the SPOG-CUIC Sync operation
Workaround:
NA
Further Problem Description:
Defect Number: CSCvq12348
Component: dbconfig
Severity: 2
Headline: Departmental Administrator not allowed to create agent or enable Email & Chat support
Symptom:
Departmental administrators are unable to enable support for email and chat by clicking "Support Email & Chat" because the "Screen Name" and "Email Address" fields remain disabled.
Conditions:
When creating a new agent or modifying an existing agent to enable support for Email & Chat login
Workaround:
None
Further Problem Description:
Defect Number: CSCvq67966
Component: dbconfig
Severity: 2
Headline: ECE goes out of sync when we perform Agent Update operation
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Defect Number: CSCvq88066
Component: dbconfig
Severity: 2
Headline: PCCE v12 Supervisor re-skilling agent/skills page blank after installing ES21
Symptom:
PCCE Supervisor unable to re-skill the agents
Conditions:
PCCE 12.0 with ES21
Workaround:
none
Further Problem Description:
Defect Number: CSCvr21614
Component: template
Severity: 2
Headline: Orchestration doesn't happen when we do agent multi delete from non-principal AW
Symptom:
Orchestration doesn't happen when we do agent multi delete from non-principal AW
Conditions:
Perform operations from non-principal AW
Workaround:
Remove agents from ECE manually
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr51613
Component: dbconfig
Severity: 2
Headline: PCCE 4K/12K CVVB Inventory Import Fails
Symptom:
Inventory Import fails at
"Create Default Virtualized Voice Browser configurations"
Conditions:
PCCE 4K and 12K Inventory Import via core_inventory.csv file.
Workaround:
1) Remove the CVVB servers from the inventory CSV file.
2) Perform the workaround for the following defect: CSCvr51586 - PCCE 4K/12K PG 1, 2, and 3 are not deleted via the Inventory Import Revert Tasks
3) Add Virtualized Voice Browser(s) as an external machine after the Inventory Import completes successfully.
Further Problem Description:
Signature in ICM Tomcat CCBU logs:
[exception=com.cisco.ccbu.api.jaxb.error.ApiException: Main: DataCenter Not Found][message_string=Exception in VVBDefaultConfigurationTask ]: The REST API has caught an exception
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr90903
Component: dbconfig
Severity: 2
Headline: HDS disk size needs to updated for PCCE deployment
Symptom:
HDS Disk size is wrongly configured
Conditions:
PCCE deployment
Workaround:
None
Further Problem Description:
Defect Number: CSCvs04669
Component: web.config.api
Severity: 2
Headline: Bulk Agent edit using PCCE for enabling ECE option for agent fails
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs12341
Component: dbconfig
Severity: 2
Headline: SSO component registration is failing for CUIC subscribers in PCCE 4K deployment
Symptom:
SSO component registration is failing for CUIC subscribers in PCCE 4K deployment
Conditions:
When more than one subscriber is added.
Workaround:
NA
Further Problem Description:
Defect Number: CSCvs23301
Component: dbconfig
Severity: 2
Headline: PCCE 12k Agent bulk creation aborted due to congestion
Symptom:
Bulk job for agent creation aborts due to congestion in PCCE 12K after around 34mins
Conditions:
In PCCE 12K agent creation bulk job with a csv containing 12000 agent config for 1st PG.
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs25265
Component: dbconfig
Severity: 2
Headline: Peripheral set capacity rules creation is not working
Symptom:
Peripheral set capacity rules creation is not working
Conditions:
Create a Peripheral Set in PCCE 4k system
Workaround:
None
Further Problem Description:
Defect Number: CSCvs40373
Component: web.config.api
Severity: 2
Headline: Existing Agents Unable to be Enabled for ECE After Application of PCCE ES34
Symptom:
After Enabling 'support Email & Chat' toggle, ECE agents are not being synced.
Conditions:
Enabling Chat and Email for an existing agents in PCCE.
PCCE 12.0(1) ES 34
Workaround:
Agent enabled for ECE at initial creation.
Further Problem Description:
After enabling 'support Email & Chat' checkbox, The ECE users are not syncing with ECE, as a result, they don't show up on the PCCE-ECE gadget.
Also, this seems to be working in PCCE 12 base and is broken in one of the ES's (ES36)
Below is the exception that is seen on AWDB tomcat logs -
Dec 02 2019 10:10:50.165 -0500: %CCBU_pool-1761-thread-1-3-REST_API_EXCEPTION: %[exception=com.cisco.ccbu.api.jaxb.error.ApiException: 404-100
The following IDs supplied in the URI path were not found: '5003'.][message_string=Error 404 occurred while trying to GET to https://10.1.1.2:443]: The REST API has caught an exception
0003844719: 10.65.53.85: Dec 02 2019 10:10:50.165 -0500: %CCBU_pool-1761-thread-1-3-EXCEPTION_INFO: %[build_date=Nov 13, 2019 4:24 AM][build_type=rel][exception=com.cisco.ccbu.api.jaxb.error.ApiException: 404-100
The following IDs supplied in the URI path were not found: '5003'.
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.processErrorResponse(RESTClient.java:158)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.analyzeClientResponse(RESTClient.java:108)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.makeRequest(RESTClient.java:255)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.get(RESTClient.java:298)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ProcessingWorker.sendRestRequestToMachine(ProcessingWorker.java:153)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ECEProcessingWorker.prepareRequestDataAndInvokeOrchestration(ECEProcessingWorker.java:174)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ECEProcessingWorker.handleAgentUpdate(ECEProcessingWorker.java:121)
at com.cisco.ccbu.cce.unifiedconfig.orchestration.worker.ECEProcessingWorker.updateWorkflow(ECEProcessingWorker.java:92)
Defect Number: CSCvs42013
Component: dbconfig
Severity: 2
Headline: Media Server orchestration failing
$$PREFCS
Symptom:
In CVP, media server details are not getting updated
Conditions:
Enable FTP for CVP
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs64057
Component: template
Severity: 2
Headline: Reason Codes doesn't show in Teams gadget for the first time
Symptom:
Reason Codes doesn't show in Teams gadget
Conditions:
first time when logged into cceadmin
Workaround:
Go to Overview and come back to Teams gadget. This time all the make request goes with Finesse hostname
Further Problem Description:
Defect Number: CSCvs77189
Component: web.config.ui
Severity: 2
Headline: Cannot Switch to HCS 4K Deployment if Total Dialed Numbers on All CVP Route Clients Exceeds 4000
Symptom:
When attempting to switch to HCS-4K deployment model, the user receives the following error:
You have reached capacity for MAXIMUM_DIALED_NUMBERS_EXTERNAL. The limit is 4000 [name=MAXIMUM_DIALED_NUMBERS_EXTERNAL, max=4000, actual=####]
When checking the number of Dialed Numbers configured, the number will be under 4000 per CVP peripheral.
Conditions:
When the total number of Dialed Numbers on all CVP routing clients exceeds 4000.
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.5(1)_ES7 at https://software.cisco.com/download/specialrelease/37fde0aa7635fb3bfb5fd0217dac919d
Defect Number: CSCvn77418
Component: dbconfig
Severity: 3
Headline: Incorrect error thrown on deleting gateways associated with location
$$PREFCS
Symptom:
Database transaction error is seen in SPOG UI
Conditions:
When trying to delete a gateway associated with location
Workaround:
NA -
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES6 at https://software.cisco.com/download/specialrelease/69571a20478917ff4e4f5045fd73679b
Defect Number: CSCvn77421
Component: dbconfig
Severity: 3
Headline: IdS is reporting incorrect status in SPOG UI
$$PREFCS
Symptom:
IdS is reporting incorrect status in SPOG UI
Conditions:
When checking from SSO under device configuration
Workaround:
NA
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES6 at https://software.cisco.com/download/specialrelease/69571a20478917ff4e4f5045fd73679b
Defect Number: CSCvn78159
Component: dbconfig
Severity: 3
Headline: In SPEC based deployment, status rules do not run.
Symptom:
This issue will cause exceptions in VMHostDatastoreStatusDataProcessor in the tomcat logs.
Conditions:
SPEC based PCCE deployment
Workaround:
None
Further Problem Description:
Defect Number: CSCvn78163
Component: dbconfig
Severity: 3
Headline: Campaign Skill group Search Pop-over is not working as expected
$$IGNORE
Symptom:
Org Settings ? Campaign.
Click new and go to Skill group tab
Add New. Click on Skill Group search adder. First its coming as empty, and try type something and remove it.It will display all skill groups.
Conditions:
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES6 at https://software.cisco.com/download/specialrelease/69571a20478917ff4e4f5045fd73679b
Defect Number: CSCvn79565
Component: dbconfig
Severity: 3
Headline: Campaign Multi-edit popup and contacts template issues
Symptom:
1. Status and schedule checkbox is not enabled in multi -edit popup when trying to edit status and schedule
2. Save button is not enabled when status or schedule is modified.
3. Extension of contacts template file is .txt, the extension should be .csv
Conditions:
When editing multiple campaigns or when downloading contacts template.
Workaround:
1. Use single edit instead of multi edit
2. Rename the contacts template from .txt to .csv
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES6 at https://software.cisco.com/download/specialrelease/69571a20478917ff4e4f5045fd73679b
Defect Number: CSCvn82112
Component: dbconfig
Severity: 3
Headline: DeploymentSettings and SignOut Ui issues in Fresh Install
$$IGNORE
Symptom:
Conditions:
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES6 at https://software.cisco.com/download/specialrelease/69571a20478917ff4e4f5045fd73679b
Defect Number: CSCvn92277
Component: dbconfig
Severity: 3
Headline: enforce wrapup code missing for PCCE 12.0
Symptom:
Force Wrap Up feature is only available in UCCE but not PCCE 12.0.
Conditions:
This is an enhancement CSCuo73536 already added in Finesse 12.0 but PCCE interface didn't reflect the change so the option is not shown in agent desk setting.
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES6 at https://software.cisco.com/download/specialrelease/69571a20478917ff4e4f5045fd73679b
Defect Number: CSCvo15059
Component: dbconfig
Severity: 3
Headline: Inconsistent behavior for 'Cancel' button click in Device Configuration UI
Symptom:
Inconsistent behavior for 'Cancel' button click in Device Configuration UI
Conditions:
Device Configuration UI
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES15 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvo28848
Component: dbconfig
Severity: 3
Headline: Run time status rules task is failing-for PCCE spec based harware
Symptom:
Would see the error in CCE admin page and below exception in tomcat logs
0001560931: 10.252.96.13: Jan 30 2019 23:57:26.377 -0700: %CCBU_pool-1-thread-45-Infrastructure-2057694-6-REST_API_INFO: updateRunTimeValidationStatus: running dataCollector: MetricStatusCollector
0001560932: 10.252.96.13: Jan 30 2019 23:57:27.008 -0700: %CCBU_pool-1-thread-45-Infrastructure-2057694-3-REST_API_EXCEPTION: %[exception=java.lang.ClassCastException: com.vmware.vim25.NasDatastoreInfo cannot be cast to com.vmware.vim25.VmfsDatastoreInfo][message_string=Error executing task RuntimeStatusRulesTask]: The REST API has caught an exception
0001560933: 10.252.96.13: Jan 30 2019 23:57:27.009 -0700: %CCBU_pool-1-thread-45-Infrastructure-2057694-3-EXCEPTION_INFO: %[build_date=Jul 06, 2018 7:15 AM][build_type=rel][exception=java.lang.ClassCastException: com.vmware.vim25.NasDatastoreInfo cannot be cast to com.vmware.vim25.VmfsDatastoreInfo
at com.cisco.ccbu.cce.unifiedconfig.api.status.datacollection.perf.PerfHelpers.getDiskInfoByDiskName(PerfHelpers.java:136)
at com.cisco.ccbu.cce.unifiedconfig.api.status.datacollection.MetricStatusCollector.updateDiskMetrics(MetricStatusCollector.java:219)
at com.cisco.ccbu.cce.unifiedconfig.api.status.datacollection.MetricStatusCollector.getMetrics(MetricStatusCollector.java:201)
at com.cisco.ccbu.cce.unifiedconfig.api.status.datacollection.MetricStatusCollector.getMetricsForVms(MetricStatusCollector.java:118)
at com.cisco.ccbu.cce.unifiedconfig.api.status.datacollection.MetricStatusCollector.updateMetrics(MetricStatusCollector.java:85)
at com.cisco.ccbu.cce.unifiedconfig.api.status.datacollection.MetricStatusCollector.collectStatusData(MetricStatusCollector.java:70)
at com.cisco.ccbu.cce.unifiedconfig.api.status.StatusTask.updateRunTimeValidationStatus(StatusTask.java:139)
at com.cisco.ccbu.cce.unifiedconfig.api.status.StatusTask.performActions(StatusTask.java:103)
at com.cisco.ccbu.cce.unifiedconfig.tasks.SingleSideTask.execute(SingleSideTask.java:69)
at com.cisco.ccbu.cce.unifiedconfig.api.status.RuntimeStatusRulesTask.execute(RuntimeStatusRulesTask.java:151)
at com.cisco.ccbu.cce.unifiedconfig.tasks.TaskBase.call(TaskBase.java:36)
at com.cisco.ccbu.cce.unifiedconfig.tasks.TaskBase.call(TaskBase.java:26)
at com.cisco.ccbu.cce.unifiedconfig.tasks.TaskExecutor.execute(TaskExecutor.java:62)
at com.cisco.ccbu.cce.unifiedconfig.tasks.TaskExecutor.run(TaskExecutor.java:49)
at com.cisco.ccbu.infra.threads.ThreadPoolManager$FixedDelayRunnable.run(ThreadPoolManager.java:793)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at com.cisco.ccbu.infra.threads.InstrumentedRunnable.run(InstrumentedRunnable.java:92)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at com.cisco.ccbu.infra.threads.ThreadPoolThread.run(ThreadPoolThread.java:164)
][product_name=UCCE WebConfiguration][subsystem_exception_info=][tid=pool-1-thread-45-Infrastructure-2057694][version_number=UCCE WebConfiguration_11_6_1_0_1_0_17]: Information associated with the following logged exception
0001560934: 10.252.96.13: Jan 30 2019 23:57:27.010 -0700: %CCBU_pool-1-thread-45-Infrastructure-2057694-6-REST_API_INFO: Task : RuntimeStatusRulesTask has executed 25731 times
Conditions:
PCCE 11.6 with ES 9 and on spec based hardware with NFS datastore type
Workaround:
None
Further Problem Description:
Error is seeing on MetricStatusCollector API as part of RuntimeStatusRulesTask.Since customer applied ES09 already, which supports spec based hardware, you won't see this issue during initial deployment wizard.But somehow, it's not been updated in getDiskInfoByDiskName class which will get executed as part of MetricStatusCollector API.
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES15 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvo45192
Component: dbconfig
Severity: 3
Headline: PG explorer marks entries as modified during normal traversal
Symptom:
PG explorer marks entries as modified during traversal
Conditions:
PCCE 4k & 12k deployments
Workaround:
Update all the fields having value -1 in tools UI and then save the configuration.
Here are the fields which invalid value.
These fields are below.
In Logical_Interface_Controller table :- Interval field.
Routing Client:- Timeout threshold, Timeout limit, LateThreshold.
Peripheral :- Multiline Agent Control, MultilineAgentStateBehavior.
Correcting values for these fields, fix the problem.
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES15 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvo59157
Component: dbconfig
Severity: 3
Headline: PCCC 12.0 SIP Header Passing to ICM should not require parameter
PCCE SPOG should not require configuration of Parameter for the SIP Header under CVP CS SIP Subsystem
Symptom:
When creating SIP Header from SPOG, if you don't provide a parameter name you get an error
Conditions:
Everytime you try to add a new SIP Header
Workaround:
Add the parameter from SPOG, and modify the sip.properties file
Further Problem Description:
Defect Number: CSCvo61931
Component: dbconfig
Severity: 3
Headline: Updating an ECE Agent with same screenName, ECE goes to out-of-sync
Symptom:
In a post upgrade scenario of ECE, ECE can go out of sync in the conditions specified.
Conditions:
In a post upgrade scenario of ECE where agents were already imported to ECE from PCCE using ECE administration and the "Support for Email and Chat" option is not enabled in PCCE SPOG and if Admin makes the option true and give a new screenName or existing screenName,
Workaround:
Use Bulk Upload with same/different screenname of an ECE agent
Further Problem Description:
Defect Number: CSCvo66492
Component: dbconfig
Severity: 3
Headline: SPOG ECE Agent Screen Name does not allow spaces
Symptom:
SPOG ECE Agent Screen Name field does not allow spaces.
Conditions:
Observed on the Chat interaction Screen Name shown to customers
Workaround:
None
Further Problem Description:
Defect Number: CSCvo71587
Component: install
Severity: 3
Headline: Websetup doesn't come up after installing ICM12.0(1)_ES6
Symptom:
1) All web apps like Web Setup, CCE Admin will stop working after installing 12.0(1) ES6.
2) Websetup login throws error to run sslutil tool.
Conditions:
After installation of certain Engineering Specials that contain a fix for the file ccbu-common-shindig-server.war . For instance, ES6 and ES15.
Workaround:
1. Launch sslutil from "Administration Tools" desktop folder
2. Select ALL INSTANCES and run the tool.
3. Relaunch websetup and login
Further Problem Description:
Defect Number: CSCvo85717
Component: dbconfig
Severity: 3
Headline: Post Call Survey DN limit needs to be updated in PCCE 2k deployment
Symptom:
Post Call Survey DN limit needs to be updated in PCCE 2k deployment
Conditions:
in PCCE 2k deployment
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES15 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvo91661
Component: template
Severity: 3
Headline: Courtesy Callback page issues
Symptom:
Dial Number Configuration doesn't load in page automatically
Conditions:
when we change the site
Workaround:
reselect the reporting server
Further Problem Description:
Defect Number: CSCvo98128
Component: dbconfig
Severity: 3
Headline: Disable Routing Client names in PG Explorer (UCM , VRU , MR PG) for PCCE deployment
Symptom:
Issue while applying the config changes to configuration associated with Routing Client on SPOG.
Conditions:
Changed the auto-generated Routing Client name format using PG Explorer in PCCE environment.
Workaround:
None
Further Problem Description:
None.
PSIRT Evaluation:
The Cisco PSIRT has evaluated this issue and does not meet the criteria for PSIRT ownership or involvement. This issue will be addressed via normal resolution channels.
If you believe that there is new information that would cause a change in the severity of this issue, please contact psirt@cisco.com for another evaluation.
Additional information on Cisco''s security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES15 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvp11036
Component: dbconfig
Severity: 3
Headline: Unable to create Agents and AgentTeam using bulk job in PCCE 4K/12K
Symptom:
Error about missing Agent Team refererence when performing Agent Bulk Create.
Conditions:
In PCCE 4K/12K deployment. When CSV file for Agent Bulk Create contains a reference to Agent Team that does not exist in the database.
Workaround:
Create the Agent Team manually before attempting to perform Bulk Agent Config.
Further Problem Description:
Defect Number: CSCvp12852
Component: doc
Severity: 3
Headline: Edit Attributes for Multiple Agents Option missing in PCCE 11.6 GUI
Symptom:
Per PCCE 11.6 Administration and Configuration Guide:
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/pcce/pcce_11_6_1/maintenance/Guide/pcce_b_admin-config-11_6/pcce_b_admin-config-11_6_chapter_010.html#PCCE_TK_MA67B7C4_00
Step 1
Navigate to Unified CCE Administration > Manage > Agents.
Step 2
Check the check box for each agent whose attribute assignments and values you want to edit.
To select all agents in a list, check the select/deselect all check box in the list header. (The check box is enabled for select all only when the number of agents in the list is less than or equal to 50.)
The total number of selected agents appears above the agent list. To clear all agents, check the select/deselect all check box. (The check box is enabled for deselect all when you check one or more agents in the list, regardless of the number of agents in the list.)
Step 3
Click Edit > Attributes.
The Edit Attributes pop-up window opens with a list of attributes. The # of Selected Agents column indicates how many of the selected agents already are assigned each attribute.
For step 3 In Edit option we do not have a option for Attributes in drop down list and thereby no Attributes pop-up window opens up.
Conditions:
PCCE 11.6, 12.0 Multi-edit attribute feature was deprecated. The relevant steps needs to be removed from PCCE guide.
Workaround:
None
Further Problem Description:
Not sure if this is a doc defect or actual feature is missing from PCCE.
Defect Number: CSCvp19303
Component: template
Severity: 3
Headline: DataCenter based sorting is not working in DialNumber page
Symptom:
DataCenter based sorting is not working in DialNumber page
Conditions:
When viewing the dialed numbers configured in the system, using "Call Settings" -> "Route Settings" menu, in CCE web administration tool.
Workaround:
None
Further Problem Description:
Defect Number: CSCvp20793
Component: dbconfig
Severity: 3
Headline: Not able to delete Peripheral set under certain conditions
Symptom:
Not able to delete Peripheral set under certain conditions
Conditions:
Multiple sites having same peripheral set names
Workaround:
None
Further Problem Description:
Defect Number: CSCvp21111
Component: dbconfig
Severity: 3
Headline: Device Hostname is truncated with an Error message in CVP Stats dialog
Symptom:
Device Hostname is truncated with an Error message in CVP Stats dialog
Conditions:
None
Workaround:
None
Further Problem Description:
Defect Number: CSCvp23552
Component: template
Severity: 3
Headline: Accessibility issues in cceadmin
Symptom:
Accessibility issues in cceadmin
Conditions:
Not able to access some of the cceadmin options using Keystrokes
Workaround:
use mouse control
Further Problem Description:
Defect Number: CSCvp28803
Component: dbconfig
Severity: 3
Headline: PCCE Fresh Install wizard is displaying PCCE 4K and 12K deployment types
Symptom:
CCE Web Administrator UI of Fresh Install machines displays all PCCE deployments (lab mode, 2K, 4K and 12K ) while setting deployment Type.
As expected, only 2K and Lab mode PCCE deployment type should get displayed. As PCCE 4K and 12K deployment type depends on the Router, Logger and Aw components creation in websetup.
Conditions:
Workaround:
Further Problem Description:
Defect Number: CSCvp34995
Component: web.config.ui
Severity: 3
Headline: Unable to Add 20 Custom Gateways if Remote ICM is Configured
Symptom:
Unable to Add 20 Custom Gateways in cceadmin
Conditions:
Observed only when remote ICM is Configured
Workaround:
None
Further Problem Description:
Defect Number: CSCvp36895
Component: dbconfig
Severity: 3
Headline: Roles are not loading in Administrator gadget
$$PREFCS
Symptom:
Conditions:
Workaround:
Search for role based on key word
Further Problem Description:
Defect Number: CSCvp36973
Component: web.config.ui
Severity: 3
Headline: PCCE SPOG Specific Navigation Menu's made available for UCCE
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Defect Number: CSCvp38942
Component: dbconfig
Severity: 3
Headline: PCCE disk size validation should be relaxed to include sizing consideration for Outbound Database
Symptom:
PCCE Install and Upgrade Guide should include sizing consideration for Outbound Database.
Conditions:
PCCE Install and Upgrade Guide, using Outbound option
Workaround:
N/A
Further Problem Description:
Defect Number: CSCvp47136
Component: dbconfig
Severity: 3
Headline: Transferable Files File Upload API endpont has to be changed
$$PREFCS
The endpoint is not as per convention
Symptom:
The API endpoint does not reflect the resource.
Conditions:
Normal working condition
Workaround:
No workaround
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES15 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvp66880
Component: dbconfig
Severity: 3
Headline: Custom Role user gets all Navigation menu's in cceadmin
Symptom:
Custom Role user gets all Navigation menu's in cceadmin
Conditions:
Custom Role user gets all Navigation menu's in cceadmin
Workaround:
No admin operations are allowed to perform. It's a UI visibility issue.
Further Problem Description:
Defect Number: CSCvp68561
Component: dbconfig
Severity: 3
Headline: Gateway deletion from inventory should not happen when it is mapped in CVP device configuration
Symptom:
Gateway deletion from inventory should not happen
Conditions:
Gateway deletion from inventory should not happen
Workaround:
None
Further Problem Description:
Defect Number: CSCvp83276
Component: dbconfig
Severity: 3
Headline: PCCE Machine Limits need correction
Symptom:
When adding a new 3rd Party Multichannel machine to the Inventory page in PCCE 11.6, then an error is seen stating, "The maximum number of 3rd Party Multichannel machines has been reached. The limit is 1."
Conditions:
Occurs if customer already has one 3rd Party Multichannel machine in the inventory.
Workaround:
None, documentation needs to be updated to list the limits.
Further Problem Description:
Defect Number: CSCvp86341
Component: dbconfig
Severity: 3
Headline: ECE Differential sync fails under certain condition
Symptom:
ECE Differential sync fails
Conditions:
When we create and delete agent when ece is down / out of sync
Workaround:
Remove agent from Deleted Objects and try differential sync
Further Problem Description:
Defect Number: CSCvp86346
Component: dbconfig
Severity: 3
Headline: populateExternalPageFeaturesFromCodes message filling up Tomcat logs
$$PREFCS
Symptom:
populateExternalPageFeaturesFromCodes message filling up Tomcat logs
Conditions:
Workaround:
Further Problem Description:
Defect Number: CSCvp93416
Component: dbconfig
Severity: 3
Headline: Registration of Context Service shows undefined
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Defect Number: CSCvp98507
Component: dbconfig
Severity: 3
Headline: ECE Agent created using Bulk job do not get propagated to ECE.
Symptom:
ECE users do not get created on the ECE side.
Conditions:
Only with ECE Agents
Workaround:
1. Edit the ECE agent that was not synced, in the Agent gadget.
2. Un-check the "Support Email & chat" checkbox. Click Save.
3. Check the "Support Email & chat" checkbox. Click Save.
Further Problem Description:
Defect Number: CSCvp98528
Component: template
Severity: 3
Headline: Edit button should be disable when we select agents from different Peripheral Sets
Symptom:
Edit button should be disable
Conditions:
when we select agents from different Peripheral Sets
Workaround:
None
Further Problem Description:
Defect Number: CSCvq00400
Component: dbconfig
Severity: 3
Headline: Failed to retrieve placement of external page when card with no menu's exists in between
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Defect Number: CSCvq01988
Component: web.config.api
Severity: 3
Headline: Personal callback DELETE API always returns a 404
Symptom:
Issuing a delete on the personal callback API with a valid ID will return an HTTP 404 result, which is incorrect.
The following example will return an HTTP 404 error:
https:///unifiedconfig/config/personalcallback/
Conditions:
Using the personal callback API and issuing an individual record delete will fail with an HTTP 404.
Workaround:
none
Further Problem Description:
Defect Number: CSCvq03314
Component: dbconfig
Severity: 3
Headline: Not able to create agents belonging to departments in PCCE4k / 12k deployments
Symptom:
Cannot create agents through CCE web administration tool in PCCE 4k / 12k agent deployments, because the mandatory field "Peripheral Set" to which the agent should get tagged, is not enlisting any existing ones
Conditions:
When trying to add new Agents or supervisors that belong to a certain department
Workaround:
First create the agent with the "Department" field left empty, i.e. set to Global, and then assign the agent to the respective department through the CCE web administration tool.
In case if the logged-in admin is department admin, department becomes mandatory while creating agent. so follow below workaround, first choose PS and then choose department.
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvq06932
Component: dbconfig
Severity: 3
Headline: Providing wrong credentials while selecting Principal AW from CCEAdmin does not throw error
Symptom:
Modifying principal AW with incorrect credentials and showing wrong credential saved successfully in UI. It will make user to assume wrong credential is saved successfully. But it will not save incorrect credential.
Conditions:
PCCE UI refresh in every 30 seconds. If you modify the principal AW credentials with incorrect value and try to save, it will give you error saying invalid credentials. But if you keep hitting the save button and UI refreshes in 30 seconds then in the backend because of UI refresh the incorrect credentials will be replaced with existing valid credentials and after hitting save button it will show successfully saved in UI.
Workaround:
None
Further Problem Description:
Defect Number: CSCvq12588
Component: dbconfig
Severity: 3
Headline: In PCCE 4K,In IE browser, Sync Staus layout is broken in Inventory
Symptom:
Sync Staus layout is not proper in Inventory in IE browser in PCCE4K
(Differential Sync is displayed out of the Sync Status border)
Conditions:
None
Workaround:
None
Further Problem Description:
Defect Number: CSCvq27248
Component: web.config.api
Severity: 3
Headline: Supporting ECC API deficient in UCCE deployments
Symptom:
Although ECC Payload REST API is available for use while integrating with CCE, the supporting ECC API (Expanded Call Context) isn't available or allowed, thereby hampering access to the individual ECC variables that form the payload body of the ECC Payload API.
Basically, the refURL's and the ECC variable names are not available to be retrieved to be used in the ECC Payload API, while creating or updating ECC payloads using the POST and PUT methods respectively.
Conditions:
When trying to integrate with UCCE via REST API with the deployment type set to UCCE 2k / 4k / 12k / 24k deployments.
Workaround:
None
Further Problem Description:
Although there is a way to retrieve the refURL's of the ECC variables that are part of the "Default" Payload of the system that contains all the ECC variables that pre-existed before upgrade to ver 12.0, any new ECC variables created post upgrade, are still not accessible.
Defect Number: CSCvq27469
Component: dbconfig
Severity: 3
Headline: Inventory and Features page not loading post Contact Director deployment set
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Defect Number: CSCvq32445
Component: dbconfig
Severity: 3
Headline: SPOG UI: Inventory alerts rules messages are truncated in the middle and not understandable.
Symptom:
we observed in Invetory of SPOG UI alerts rule messages are truncated in the middle and not making meaning statement and not able to understand. This is happening for message having long length.
Conditions:
lengthier rule messages are impacted.
Workaround:
Further Problem Description:
Defect Number: CSCvq33205
Component: dbconfig
Severity: 3
Headline: If External machine name contains a long string, name is coming out of the delete popover in IE
$$PREFCS
Symptom:
In IE browser, If External machine name contains a long string, name is coming out of the delete popover
Conditions:
only in IE browser
Workaround:
None
Further Problem Description:
Defect Number: CSCvq33281
Component: web.config.api
Severity: 3
Headline: PCCE2K-SPOG: Miscalculation/Representation of Total Alerts in the Inventory (Build #288)
$$PREFCS
PCCE2K-SPOG: Miscalculation/Representation of Total Alerts in the Inventory
Symptom:
PCCE2K-SPOG: Miscalculation/Representation of Total Alerts in the Inventory
Conditions:
Workaround:
Further Problem Description:
Defect Number: CSCvq35784
Component: dbconfig
Severity: 3
Headline: Help icon is missing in New Site dialog in IE browser
$$PREFCS
Symptom:
Help icon is missing in New site dialog in IE browser
Conditions:
None
Workaround:
None
Further Problem Description:
Defect Number: CSCvq44602
Component: web.config.ui
Severity: 3
Headline: CCEadmin always uses credentials of first CUCM in case of main site and remote site deployment
Symptom:
CUCM account gets locked in PCCE environment
Conditions:
password is diff in main and remote site for axl user.
Main Site . Remote Site . Test Result
CUCM PUB CUCM PUB
UserName1\Password1 UserName1\Password1 pass
UserName1\Password1 UserName1\Password1 Fail(cucm account gets locked)
Workaround:
Set the same username/password
Further Problem Description:
Defect Number: CSCvq45077
Component: web.config.ui
Severity: 3
Headline: MR PG's not available under the configuration in UCCE Admin for SocialMiner (HCS 2K)
Symptom:
MR PG's are not available under the configuration in UCCE Admin
When customer clicks on SocialMiner > Select Media Routing PG, no PGs available
Conditions:
HCS 2000 deployment.
HCS 2000 deployment model (deployment type 11) trying to use machine type CCE_ROGGER(29) to fetch the PG machine details and is the reason for failure. Here, the PG machines are having machineType 23(CCE_PG).
Workaround:
Contact TAC
Further Problem Description:
Defect Number: CSCvq46558
Component: dbconfig
Severity: 3
Headline: 'Select All' option is deselected in Departments summary view
Symptom:
Steps:
1)Login to cceadmin and create 2 departments.
2)Select all the departments(click on Select All the option)
3)Click on Delete button
4)While in Delete popover, Click on Overview and click on Departments in Organization Setup card view
check 'Select All' option is deselected and 2 departments are deslected but still delete popover is displayed
Conditions:
Reproducible in all the browsers(Chrome, FF and IE)
Workaround:
None
Further Problem Description:
Defect Number: CSCvq47995
Component: template
Severity: 3
Headline: Stats icon missing for external CVP Reporting server
Symptom:
Stats icon missing for CVP Reporting server
Conditions:
Add CVP Reporting server as external machine
Workaround:
None
Further Problem Description:
Defect Number: CSCvq54170
Component: dbconfig
Severity: 3
Headline: PS deletion should check for machines membership in Sip server group
Symptom:
Ps deletion fails
Conditions:
When PS member is part of Sip server group
Workaround:
Remove sip server group membership and try to delete PS
Further Problem Description:
Defect Number: CSCvq62990
Component: dbconfig
Severity: 3
Headline: CVP DNIS API accepts more than 32 characters in each DNIS
Symptom:
CVP DNIS API accepts more than 32 characters in each DNIS
Conditions:
CVP DNIS API
Workaround:
None
Further Problem Description:
Defect Number: CSCvq63352
Component: web.config.api
Severity: 3
Headline: Alert on the Router Configuration for enabling the Application Gateway using WebSetup in Inventory
Symptom:
Alert on the Router Configuration for enabling the Application Gateway using WebSetup in Inventory
Conditions:
Workaround:
Further Problem Description:
Defect Number: CSCvq64857
Component: dbconfig
Severity: 3
Headline: Deletion of single DN using Bulk Job Deletion works however failed message is thrown.
Symptom:
Job to delete single Dialed Number using Bulk Job from 'Manage Bulk Job' fails.
Conditions:
When we try to delete single Dialed Number using Bulk Job from 'Manage Bulk Job'.
Workaround:
None.
Further Problem Description:
Defect Number: CSCvq78029
Component: template
Severity: 3
Headline: Search doesn't work in Sip server group Site selection
Symptom:
Search doesn't work in Sip server group Site selection
Conditions:
Sip server group creation
Workaround:
Select site by going through the list
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvq85125
Component: web.config.ui
Severity: 3
Headline: Switching to NAM(Deprecated) stuck at loading for long and after Inventory not displayed
Symptom:
Switching to NAM(Deprecated) stuck at loading for long and after Inventory not displayed
Conditions:
In case of NAM(Deprecated) and NamRogger(Deprecated)
When the user switches to this deployment , Webadmin gets stuck at Loading for long time .
After some 15 mins , Page recovers and post that all looks good except Inventory page which says the below error:
"The requested page cannot be displayed.Contact the System Administrator if the problem persists"
If NAm is out of support then we can remove these deployments from the list else this have to be fixed .
Workaround:
None
Further Problem Description:
Defect Number: CSCvq95029
Component: template
Severity: 3
Headline: API exceptions observed while redirecting to RouteSettings page in cceadmin
Symptom:
API exceptions observed while redirecting to RouteSettings page in cceadmin
Conditions:
While redirecting to RouteSettings page in cceadmin
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvq99289
Component: dbconfig
Severity: 3
Headline: PCCE alert: MR PIM and node manager trace level warning
Symptom:
PCCE alert: Trace Level rule warning on Unified CCE PG server
Conditions:
NA
Workaround:
NA
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr05766
Component: web.config.ui
Severity: 3
Headline: Online help missing on SingleSignon(SSO) Page of Webadmin
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr09420
Component: template
Severity: 3
Headline: Able to remove Principal check for AW in cceadmin
Symptom:
Able to remove Principal check for AW
Conditions:
When you hit any error while saving AW after edit. Principal AW checkbox becomes editable
Workaround:
Mark Aw as principal again
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr17986
Component: dbconfig
Severity: 3
Headline: PCS dialnumbers are not considered in Capacityrule when "PCS EnabledDialedNumberPatterns" configured
Symptom:
PCS dialnumbers are considered in Capacity rule
Conditions:
when "PCS Enabled Dialed Number Patterns" field is configured
Workaround:
configure "PCS Enabled Dialed Number Patterns" with prefix of PCS@
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr33101
Component: web.config.ui
Severity: 3
Headline: Unable to set trace levels from secondary AW for Log Collection in PCCE 2K Deployment
$$PREFCS
Symptom:
Unable to set trace levels from secondary AW for Log Collection in PCCE 2K Deployment
Conditions:
When you try to set trace level for log collection from cceadmin on secondary AW server
Workaround:
Perform the operation from Primary/Principle AW
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr49943
Component: web.config.ui
Severity: 3
Headline: Unable to save CUIC/IDS/Livedata config / incorrect error message
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr51586
Component: dbconfig
Severity: 3
Headline: PCCE 4K/12K PG 1, 2 and 3 are not deleted via the Inventory Import Revert Tasks
Symptom:
If PCCE Inventory import fails, PGs 1, 2, and 3 are not deleted when the successful imports are reverted. The next time the Inventory Import is triggered by uploading a corrected core_inventory.csv, the process will fail at the Peripheral Set 1 import.
Failure occurs at the "Peripheral Gateway creation on PG Side A of Peripheral Set ps1"
Conditions:
PCCE 12.0 4K and 12K Deployment Configuration via the cceadmin page
Workaround:
Navigate to each PG, open up PGSetup, and manually delete each PG. The PG id numbers will continue to increment.
Further Problem Description:
ICM Tomcat CCBU log signature:
"com.cisco.ccbu.api.jaxb.error.ApiException: There are already 3 PGs configured on this VM."
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr55052
Component: template
Severity: 3
Headline: PCS DN Routing Type changes to External Voice after edit
Symptom:
PCS DN Routing Type changes to External Voice after edit
Conditions:
When we don't have any value for "PCS Enabled Dialed Number Patterns" while editing
Workaround:
Delete the DN which changed to External Voice.
Create a new DN with routingType PCS and specify appropriate dialed number pattern.
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr72278
Component: dbconfig
Severity: 3
Headline: Agent Teams deleted in PCCE 12.0 are not deleting the corresponding teams in CUIC
Symptom:
Agent Teams deleted in PCCE are not getting deleted in CUIC
Conditions:
PCCE 12.0(1) auto team sync to CUIC
Workaround:
None
Further Problem Description:
This is tested in lab as well and there were no 500 error codes returned by CUIC for the PUT/POST calls on valuelists/collections.
From CUIC localhost access logs, it is observed that no DELETE REST calls are received from PCCE
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr72636
Component: web.config.ui
Severity: 3
Headline: SSO supervisors gets blank screen when SPOG page is refreshed
Symptom:
The SSO supervisor logs into the spog console. They gets a blank page on the browser when the SPOG console is refreshed
Conditions:
Supervisor login with SSO
Workaround:
Clear the cache and re-login to CCEAdmin
Further Problem Description:
Defect Number: CSCvr81939
Component: web.config.ui
Severity: 3
Headline: In Dialed Number gadget, incorrect Routing Types are shown for MR Peripherals
Symptom:
In Dialed Number gadget, incorrect Routing Types are shown for MR peripherals
Conditions:
In PCCE, when a Peripheral Set or Remote Site is configured with MR peripherals.
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr84124
Component: template
Severity: 3
Headline: After fresh install of PCCE 4k, not able to update inventory without restarting Tomcat
Symptom:
Inventory update fails after PCCE 4k deployment setup. Reason codes are not getting created on setting up PCCE 4k deployment
Conditions:
Setup PCCE 4k deployment
Workaround:
Restart Tomcat
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvr99898
Component: dbconfig
Severity: 3
Headline: PCCE 12K inventory does not show more than 45 vm
Symptom:
inventory in 12k shows only 45 items
Conditions:
12k pcce inventory list with more than 45 vm list
Workaround:
filter the vm to see
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs08501
Component: dbconfig
Severity: 3
Headline: Regular Hours table data is missing in Business Hours in IE browser
$$PREFCS
Symptom:
Steps:
1)Launch CCEADMIN in IE browser
2)Go to Business Hours
3)Click on Regular Hours tab
4)Click on either Type or Custom and check table data is missing
Conditions:
None
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs13583
Component: dbconfig
Severity: 3
Headline: Unable to add Administrator in System Default role using Role Gadget.
Symptom:
Unable to add Administrator in System Default role using Role Gadget.
Conditions:
If we have one or more third party gadget registered, we are unable to add administrator in System Default role using role gadget after restarting Tomcat.
Workaround:
Use Administrator Gadget to assign role to Administrator
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs16800
Component: template
Severity: 3
Headline: Help File for PCCE 4k deployment is showing detail for non-packaged deployment type
Symptom:
Help File for PCCE 4k deployment is showing detail for non-packaged deployment type
Conditions:
When OLH file is opened
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs17596
Component: dbconfig
Severity: 3
Headline: CCEAdmin does not show peripheral value of Agent in UCCE 4k deployment
Symptom:
Peripheral Column in Agent Summary Page is empty.
Conditions:
This is only applicable to UCCE deployment
Workaround:
NA
Further Problem Description:
NA
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs21511
Component: dbconfig
Severity: 3
Headline: PCCE 12K: HDS fails to register to SSO mode
Due to this unable to set SSO mode on the PCCE 12K deployment.
Symptom:
This happens during setting SSO mode on PCCE 12K deployment.
Conditions:
PCCE 12K deployment SSO configure.
Workaround:
Remove HDS from the inventory and click Register for proceeding to SSO registration.
Further Problem Description:
Defect Number: CSCvs23235
Component: template
Severity: 3
Headline: Resize columns not working in PCCE 4k inventory page
$$PREFCS
Symptom:
Resize columns not working in PCCE 4k inventory page
Conditions:
Resize columns not working in PCCE 4k inventory page
Workaround:
NA
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs24355
Component: dbconfig
Severity: 3
Headline: PCCE 4K/12K deployment does not list System Options under Outbound option menu
Symptom:
PCCE deployment does not list System Options under Outbound option menu
Conditions:
PCCE 4K/12K Deployment
Workaround:
NA
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs26988
Component: template
Severity: 3
Headline: PCCE4k: Inventory Machine credentials are not editable
Symptom:
Editable Field details, PS creation details are wrongly mentioned
Conditions:
Admin and Config guide
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs31166
Component: dbconfig
Severity: 3
Headline: In IE browser, Sync dialog is not opened on clicking Sync icon
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs32861
Component: dbconfig
Severity: 3
Headline: Only first AW credentials are used to setup PCCE4k/12k deployment
Symptom:
Only first AW credentials are used to setup PCCE4k/12k deployment
Conditions:
PCCE 4k /12k deployment
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs33853
Component: dbconfig
Severity: 3
Headline: SPOG Campaign Download all Contacts option not working
Symptom:
SPOG Campaign download all contacts option not working
Conditions:
SPOG Campaign
Workaround:
NA
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs36134
Component: dbconfig
Severity: 3
Headline: Bulk Update or Create of an Agent is failing with error "team name is required and cannot be empty"
Symptom:
Bulk Update or Create fails
Conditions:
Agent creation using Bulk import
Workaround:
Use regular agent gadget to create/update Agent
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs39941
Component: template
Severity: 3
Headline: Not able to update credentials for HDS machine in PCCE 4K/12K
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs41738
Component: dbconfig
Severity: 3
Headline: Unable to create Dialed Number for Remote site in PCCE 4k Bulk Job
Symptom:
On Create Dialed number with remote site in PCCE 4k/12k bulk job, job is failing with error message: "Peripheral Set does not belongs to DataCenter mentioned in ref url".
Conditions:
Remote site should have PS with name which is already existing
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs48546
Component: template
Severity: 3
Headline: SSO supervisor : cceadmin fails to load due to bundle mismatch
Symptom:
cceadmin fails to load due to bundle mismatch
Conditions:
Login SSO enabled supervisor agent to finesse desktop first and launch cceadmin in new tab
Workaround:
Open cceadmin in another browser or private session
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.5(1)_ES7 at https://software.cisco.com/download/specialrelease/37fde0aa7635fb3bfb5fd0217dac919d
Defect Number: CSCvs56462
Component: template
Severity: 3
Headline: Miscellaneous page fails to load with InternalServerError when there are no NetworkVRU's in system
$$PREFCS
This problem can only if user has only Avaya integration with PCCE 4k and creates network/peripheral target labels for Avaya Peripherals. If user uses CVP then this problem would not come as in that case user needs to create network vru labels . Moreover, In case user run into this problem, A dummy network VRU entry would resolve the problem . Though this is an overhead but it can be used as workaround for this problem
Symptom:
Miscellaneous page fails to load
Conditions:
Avaya integration with PCCE 4k
Workaround:
A dummy network VRU entry to be added
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.5(1)_ES7 at https://software.cisco.com/download/specialrelease/37fde0aa7635fb3bfb5fd0217dac919d
Defect Number: CSCvs60065
Component: dbconfig
Severity: 3
Headline: PCCE cuic sync sets OutOfSyncTimestamp to 1970
$$PREFCS
OutOfSyncTimestamp should not be modified to 1970 if the system already was in sync earlier.
Symptom:
CUIC OutOfSyncTimestamp is set to 1970-01-01 05:30:00.000 and Pairing
status becomes- DEFERRED_SYNC_IN_PROGRESS
Conditions:
during cuic sync
Workaround:
none
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs64183
Component: dbconfig
Severity: 3
Headline: CCE Administration Registration Failure
Symptom:
On PCCE SPOG registration of CUIC, PCCE and Finesse fails.
This happens even after click on Retry.
There is no much information provided in PCCE tomcat logs for this issue
Conditions:
This was tested in a PCCE lab only with all CCE components in one VM.
Tested in 12.5 Drop5 and Golden drop.
Workaround:
The issue seems to be related to ids2_url is blank which causes API request fail. Even though, there is no ids node 2 in these deployment.
This is the work-around:
Edit idsclientlib.conf on:
cuic - /opt/cisco/cuic/cuicsrvr/lib/idsclientlib.conf ( requires root access )
finesse - /opt/cisco/desktop/finesse/lib/idsclientlib.conf ( requires root access )
pcceadmin - conf/idsclientlib.conf
In the file make sure of ids2 has the url, same as ids1:
ids1_url=https\://cuic.cc.lab\:8553/ids/v1/
ids2_url=https\://cuic.cc.lab\:8553/ids/v1/
Safe the file.
After this registration worked for PCCE and CUIC but not for Finesse.
Further Problem Description:
After adding ids2_url on /opt/cisco/desktop/finesse/lib/idsclientlib.conf
Finesse registration in PCCE SPOG still fails
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.5(1)_ES7 at https://software.cisco.com/download/specialrelease/37fde0aa7635fb3bfb5fd0217dac919d
Defect Number: CSCvs77949
Component: dbconfig
Severity: 3
Headline: Agents with TraceON enabled for 12k is 400 in Doc vs 100 in System Capacity (pcce webadmin)
$$IGNORE
Symptom:
Agents with TraceON enabled for 12k is 400 in Doc vs 100 in System Capacity (pcce webadmin)
Conditions:
Agents with TraceON enabled for 12k
Workaround:
NA
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.5(1)_ES7 at https://software.cisco.com/download/specialrelease/37fde0aa7635fb3bfb5fd0217dac919d
Defect Number: CSCvs96235
Component: dbconfig
Severity: 3
Headline: PCCE exeeded configuration limit should not trigger Service Busy state
Symptom:
When a Skill Groups/Precision Queues limit is exceeded, you will no long be able to do any configuration change.
If you try to make any change to the user who is blocked, due to reaching a threshold, you will get "Server busy" error. And this also stops any reskilling from all agents for the next 15 minutes.
Conditions:
Upgrade of PCCE to 12.0
Workaround:
N/A
Further Problem Description:
Not reproducible in 12.5
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.5(1)_ES7 at https://software.cisco.com/download/specialrelease/37fde0aa7635fb3bfb5fd0217dac919d
Defect Number: CSCvt05248
Component: template
Severity: 3
Headline: In 4k, While deleting a peripheral set, the validation errors are not getting listed in UI
$$IGNORE
In 4k, While deleting a peripheral set, the validation errors are not getting listed in UI
Symptom:
In 4k, While deleting a peripheral set, the validation errors are not getting listed in UI
It just shows a generic message "Internal server error. Contact system admin...."
This happens only in 12.5.2 code base. Checked in master. It works fine there.
Conditions:
Happens when we delete a peripheral set
Workaround:
no work around
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.5(1)_ES7 at https://software.cisco.com/download/specialrelease/37fde0aa7635fb3bfb5fd0217dac919d
Defect Number: CSCvt09634
Component: dbconfig
Severity: 3
Headline: PCCE 4K/12K day 1 validations are not exercised for both Main Site and Remote Sites
Symptom:
PS specified validations are not run both during fresh install and when adding a Remote Site or Peripheral Set
Conditions:
When performing PCCE 4K/12K fresh install, Remote Site addition.
Workaround:
N/A
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.5(1)_ES7 at https://software.cisco.com/download/specialrelease/37fde0aa7635fb3bfb5fd0217dac919d
Defect Number: CSCvt60373
Component: dbconfig
Severity: 3
Headline: Alerts status is showing as greyed out in PCCE2K
Symptom:
After adding Gateway to remote site, Alert status is showing as greyed out
Conditions:
While validating all alarms
Workaround:
NA
Further Problem Description:
Defect Number: CSCvt65656
Component: dbconfig
Severity: 3
Headline: Database API Exceptions are not handled during PCCE 4K/12K fresh install
Symptom:
Seeing the following exception in the tomcat logs
exception=com.cisco.ccbu.api.jaxb.error.ApiException: The user name or password for the web service https://10.10.10.21:443 was not correct.
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.processErrorResponse(RESTClient.java:134)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.analyzeClientResponse(RESTClient.java:108)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.makeRequest(RESTClient.java:258)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.makeRequest(RESTClient.java:262)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.makeRequest(RESTClient.java:192)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.get(RESTClient.java:288)
at com.cisco.ccbu.cce.unifiedconfig.util.RESTClient.get(RESTClient.java:277)
at com.cisco.ccbu.cce.unifiedconfig.api.inventory12k.validators.InventoryImportFreshInstallValidator.validateDatabases(InventoryImportFreshInstallValidator.java:132)
at com.cisco.ccbu.cce.unifiedconfig.api.inventory12k.validators.InventoryImportFreshInstallValidator.validateFreshInstall(InventoryImportFreshInstallValidator.java:91)
Conditions:
During PCCE 4K/12K fresh install, when the unifiedconfied API is not able to retrieve the list of MS SQL databases configured on one of the AW, RGR machines.
Workaround:
N/A
Further Problem Description:
Defect Number: CSCvt65662
Component: dbconfig
Severity: 3
Headline: NullPointerException during PCCE 4K/12K fresh install when Rogger is simplexed in the CSV
Symptom:
Observing the following exception in tomcat logs
java.lang.NullPointerException
at com.cisco.ccbu.cce.unifiedconfig.api.inventory.InventoryUtilities.getMachineAddressObjOrNull(InventoryUtilities.java:1982)
at com.cisco.ccbu.cce.unifiedconfig.api.inventory.InventoryUtilities.getMachineAddress(InventoryUtilities.java:1921)
at com.cisco.ccbu.cce.unifiedconfig.api.inventory.InventoryUtilities.getMachineAddressOrThrow(InventoryUtilities.java:1906)
at com.cisco.ccbu.cce.unifiedconfig.api.inventory.InventoryUtilities.getDiagnosticPortalRestClient(InventoryUtilities.java:2067)
at com.cisco.ccbu.cce.unifiedconfig.api.inventory12k.validators.InventoryImportBaseValidator.getDMPNumbersOnRouter(InventoryImportBaseValidator.java:184)
at com.cisco.ccbu.cce.unifiedconfig.api.inventory12k.validators.InventoryImportBaseValidator.validateRouterDMPNumber(InventoryImportBaseValidator.java:158)
Conditions:
When performing PCCE 4K/12K fresh install, provide the information for only one side Rogger or Router machine. (i.e. Simplexed Rogger / Router in the CSV data)
Workaround:
When performing PCCE 4K/12K fresh install, provide the information for both sides of Rogger or Router machines.
Further Problem Description:
Defect Number: CSCvt73896
Component: dbconfig
Severity: 3
Headline: Overview page is blank in non PCCE deployment (like UCCE and HCS) in 12.0 ES37
Symptom:
Overview page is blank in UCCE and HCS deployment in 12.0 ES37
Conditions:
Pre-Condition:
Install 12.0 ES37 on top of 12.0 FCS
Steps:
1)Login to CCEADMIN
2)Switch Deployment to any UCCE and HCS type
3)Check the Overview page, Overview page is blank. No Gadgets are visible
Gadgets are opened through left side navigation
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvt75129
Component: dbconfig
Severity: 3
Headline: MR PG Peripheral,Routing Client name inconsistency for Core and Remote site causes validation errors
Symptom:
Peripheral name and Routing Client name auto-created when adding remote Data Centers MR PG's, have inconsistent naming convention to that of the core site, which may in turn cause System and Capacity validation errors / alerts. There may also be errors thrown when accessing Dialed Number configuration page in CCE Administration tool, while trying to add Multichannel routing type DN's as well.
For Core Site, MR PG peripheral and routing client name has the following suffix:-
Outbound
Multichannel
Multichannel2
Multichannel3
For remote Data Center site, MR PG peripheral and routing client name has the following suffix:-
Outbound
MultiChannel
MultiChannel2
MultiChannel3
Notice the upper case 'C' for MR PG peripheral and routing client name associated with the remote data center site, in the Peripheral and Routing_Client table of the CCE database.
Conditions:
When configuring Multimedia enabled remote Data Center in Packaged CCE 2000 Agents deployment
Workaround:
None
Further Problem Description:
Defect Number: CSCvt98567
Component: dbconfig
Severity: 3
Headline: Need to update System Validations in PCCE 2K. Only one of Type 2 and Type 10 Network VRUs allowed
Symptom:
On the PCCE 2K deployments impacted by this bug, we will observer more than one Type 2 Network_Vru records in the AWDB.
In a valid PCCE 2K deployment, there must be only one Type 2 Network_Vru record.
Conditions:
In PCCE 2K deployment when Remote Sites are configured.
Workaround:
N/A
Further Problem Description:
Defect Number: CSCvt98590
Component: dbconfig
Severity: 3
Headline: Unable to create more than one Application Instance in PCCE 2K
Symptom:
PCCE 2K deployment limits the number of Application Instances that can be configured to 1. Creating more than one Application Instance will cause system validation errors in CCE Admin UI.
Conditions:
Only in PCCE 2K deployment
Workaround:
N/A
Further Problem Description:
Defect Number: CSCvu12137
Component: dbconfig
Severity: 3
Headline: Error alert is observed for MR PG in PCCE CCEAdmin Inventory page
Symptom:
Error alert is observed for MR PG (Side A and B) in CCEAdmin Inventory page. The alert states that ?Each MR_PIM process (mr_pim.exe) must be active on one side and idle on the other side?. Customer has 2 PIM?s (PIM2 and PIM3) in MRG PG. PIM2 is for outbound and PIM3 is for Social Miner. Both PIM?s are active on Side A and Idle on Side. Also, the DFP API?s are returning correct status to AW.
PCCE Version - 11.6.1 ES62
Conditions:
None
Workaround:
Checked the status of MR PG using DFP
To fix the alert : Rename PIM for Social Miner from "Social MIner" to "SocialMiner" using Peripheral Gateway Setup tool.
RCA: Process name is expected to be single word by PCCE Status processing logic.
Further Problem Description:
Defect Number: CSCvn71946
Component: dbconfig
Severity: 4
Headline: Advanced search for IP Address in inventory throws an internal server error
Symptom:
Internal server error seen when IP address advanced search in done in PCCE 4k/12k inventory page
Conditions:
PCCE 4k/12k inventory page IP address advanced search
Workaround:
Further Problem Description:
Defect Number: CSCvn78580
Component: dbconfig
Severity: 4
Headline: Minor alignment issues in IE
Symptom:
Minor alignment issues observed in SPOG with no functional impact
Conditions:
Observed with Internet Explorer and in some specific pages like InfraStructure?Device Config->IVR, Infrastructure ? Peripheral gateway, Org Setup? Business Hour
Workaround:
None
Further Problem Description:
Defect Number: CSCvo35666
Component: dbconfig
Severity: 4
Headline: PCCE: domain admin can still see removed tools from config manager
Symptom:
Config Manager shows some tools which are removed
Conditions:
Observed with Region Editor Tool
Workaround:
Further Problem Description:
The "Region Editor" tool should not be accessible from config manager since it has been removed from the tools list starting 11.x. ICM-Config/Setup admin can still view the tool if they are NOT a PCCE CCEAdmin. In PCCE, Tools > Miscellaneous Tools > Deleted Objects. ? is the only tool which is officially supported using Config manager in PCCE. Everything else needs to be configured from the PCCE CCEAdmin page and should not be visible in config manager.
Defect Number: CSCvo61941
Component: dbconfig
Severity: 4
Headline: ECE Database Server is referred as services server in edit page of the inventory
Symptom:
ECE Database Server is referred as services server in edit page of the inventory
Conditions:
None
Workaround:
None
Further Problem Description:
Defect Number: CSCvo94307
Component: dbconfig
Severity: 4
Headline: Filter DN to Label Mapping option in PG Explorer for CUCM PG ( PCCE 4k/12k )
Symptom:
The PG Explorer tool under Configuration Manager allows the "Dialed Number/Label map" configuration to be enabled for the routing clients, even though they are not supported in PCCE deployments.
Conditions:
When accessing the Routing Client tab in PG Explorer, while the deployment type is set to Packaged CCE 2k / 4k / 12k deployment types.
Workaround:
Do not configure anything other than "Do not use DN/Label map" option under the "Routing Client" tab in PG Explorer.
Further Problem Description:
Defect Number: CSCvp28327
Component: dbconfig
Severity: 4
Headline: Choosing "Agent State after RONA" to "Ready" in PCCE Desk Settings trigger System validation alert.
Validation Alert Presented to Customer
Symptom:
PCCE Validation Alert: Agent Desk Settings: Ring No Answer Times must not be set
Conditions:
If you select "Agent State after RONA" to READY, it updates RingNoAnswerTime to 120 in PCCE and System validation rule have alert.
Workaround:
System Validation Alert can be ignored.
Further Problem Description:
Agent State post RONA to READY, updates RNA Timer to 120 in PCCE and System validation rule alert
Defect Number: CSCvp36907
Component: doc
Severity: 4
Headline: Application gateway gadget OLH incorrect about support for IP address change
Symptom:
Support for IP address change in Application gateway gadget is incorrectly documentation in the OLH
Conditions:
Observed only in the OLH of the Application gateway gadget
Workaround:
None
Further Problem Description:
Defect Number: CSCvp37039
Component: template
Severity: 4
Headline: Not able to add users to ScriptAdmin role
Symptom:
cceadmin -> roles -> scriptadmin
Conditions:
Refresh Default roles
Workaround:
Refreshing the default roles in DB for script admin
Further Problem Description:
Defect Number: CSCvp48558
Component: dbconfig
Severity: 4
Headline: No scrolling for sites in IVR Filetransfer screen if there are more sites
Symptom:
No scrolling for sites in IVR Filetransfer screen if there are more sites
Conditions:
If there are more number of sites in the system
Workaround:
None
Further Problem Description:
Defect Number: CSCvp48927
Component: web.config.ui
Severity: 4
Headline: ALL-LANG: UCCE/PCCE WebAdmin: Calendar and time are not localized in Business Hours menu
$$PREFCS
Symptom:
Conditions:
Unified CCE Version : 12.5.1.0.0.164, LanguagePack12_5_1.exe dated 25.04.2019 + localized OS
Workaround:
n/a
Further Problem Description:
Defect Number: CSCvq13988
Component: dbconfig
Severity: 4
Headline: database transaction failed error shown to user if we use same value(case sensitive) in Username
Symptom:
database transaction failed error shown to user
Conditions:
when we use same username in case sensitive
Workaround:
None
Further Problem Description:
Defect Number: CSCvq95394
Component: template
Severity: 4
Headline: Missing details in Keyboard Shortcuts popover
Symptom:
Missing details in Keyboard Shortcuts popover
Conditions:
Keyboard shorts cuts pop-over
Workaround:
None
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvs45079
Component: dbconfig
Severity: 4
Headline: FTP password is visible in the logs
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.0(1)_ES44 at https://software.cisco.com/download/specialrelease/
Defect Number: CSCvu09271
Component: dbconfig
Severity: 4
Headline: PG VM shows incorrect alarm related to Dialer process even when it is active
$$PREFCS
Symptom:
PG VM shows incorrect alarm related to Dialer process even when it is active
Conditions:
PG VM shows incorrect alarm related to Dialer process even when it is active. This was seen post upgrade of ICM to 12.5.2 build (SSP 263)
It gives an incorrect information even when dialer component is up.
Workaround:
NA
Further Problem Description:
Defect Number: CSCvt07963
Component: dbconfig
Severity: 5
Headline: [VPAT Observation] Keyboard visual focus is not visible on some elements
Symptom:
Keyboard visual focus is not visible on some elements
Conditions:
? Select a high contrast scheme (High Contrast #1) from Windows Setting. Open Windows Settings > Easy of Access > High Contrast > Turn on high contrast and select High contrast #1
? Visually inspect the pages[Overview page]
Please refer attached doc for more details[ADR 1.4.3 T2 High-Contrast Schemes].
Workaround:
Do not select high contrast scheme
Further Problem Description:
Getting the Patch:
The following links take you to an emergency patch, called an Engineering Special or ES.
These emergency patches are meant for deployments that are actively encountering a
specific problem and cannot wait for a formal release to include a fix.
An ES receives limited testing compared to a formal release.
Installing an ES on a production system poses a risk of instability due to that limited testing.
If you are not directly experiencing this problem, wait to install a major, minor, or maintenance
release that includes the fix for this issue.
If you experience this problem and cannot wait for a later formal release, select the ES that matches
the base release of your deployment. The base release is the front part of the ES name.
Only install an ES that matches the release that your deployment runs.
Always read the release notes or Readme file before running the patch installer.
- ICM12.5(1)_ES7 at https://software.cisco.com/download/specialrelease/37fde0aa7635fb3bfb5fd0217dac919d
Defect Number: CSCvq14472
Component: dbconfig
Severity: 6
Headline: ECCPayload API does not work in Packaged CCE deployments despite the API guide claiming support
Symptom:
ECCPayload API as documented in the Cisco Packaged Contact Center Enterprise Developer Reference
guide, does not work.
An HTTP Status / Error code of 403 (Forbidden) gets returned as a response, to the API request.
Conditions:
When deployment type is set to PCCE 2000/ 4000 / 12000 agents or Lab mode deployment type using the CCE web administration tool
Workaround:
None
Further Problem Description:
You can access current Cisco documentation on the Support pages at the following sites:
- https://www.cisco.com
- https://www-china.cisco.com
- https://www-europe.cisco.com
Documentation Feedback
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
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.
Technical Assistance Center
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.
Contacting TAC by Using the Cisco TAC Site
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:
- P3--Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
- P4--You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
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/
CContacting TAC by Telephone
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:
- P1--Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available./li>
- P2--Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.