This document provides
installation instructions for Unified CCE 12.0(1) ES26. It also contains a list
of Unified CCE issues resolved by this engineering special. Review all
installation information before installing the product. Failure to install this
engineering special as described can result in inconsistent Unified CCE
behavior.
This document contains
these sections:
In the Product Alert
Tool, you can set up profiles to receive email notification of new Field
Notices, Product Alerts, or End of Sale information for your selected products.
The Product
Alert Tool is available at https://www.cisco.com/cisco/support/notifications.html.
Along with fixes for the defects specified
below, this Engineering Special also includes support for the following features
to PCCE 12.0(1):
·
Platform support
This engineering
special is supported on 12.0(1) running on either Windows Server 2012 R2 or
Windows Server 2016. However, if you are on a CCE 12.0 server that was in-line
upgraded to Windows Server 2016, ensure you install the ES18 patch before
installing the ES26 patch.
Note: You can down the ES18 patch from https://software.cisco.com/download/specialrelease/60cc617f633ae3bfe2dcf418474b4f45
·
Avaya ACD support for PCCE 4K and PCCE 12K deployments
This feature
provides support for Avaya integration. For more information about the feature,
see the Cisco Packaged Contact Center Enterprise Features Guide at https://www.cisco.com/c/en/us/support/customer-collaboration/packaged-contact-center-enterprise/products-maintenance-guides-list.html
Note: CVP12.0(1) ES4 needs to be installed on the CVP call servers
to be able to configure DNIS configurations on the CVP servers.
·
ICM-to-ICM Gateway support for PCCE 4K and PCCE 12K deployments
This feature
provides support for ICM-to-ICM Gateway configuration. For more information
about the feature, see the Cisco Packaged Contact Center Enterprise Features
Guide at https://www.cisco.com/c/en/us/support/customer-collaboration/packaged-contact-center-enterprise/products-maintenance-guides-list.html
·
Third Party Integrations
Use the
third-party integration feature to add third-party user interfaces the Contact
Center employs into Unified CCE Administration. You can host custom gadgets
such as a custom agent reskilling gadget or a third-party pages
such as a browser-based email client. Use the pages or gadgets to manage
multiple third-party components from the single panel of Unified CCE Administration.
For information
on how to integrate a third-party gadget or page to Unified CCE Administration,
see the Cisco Packaged Contact Center Enterprise Administration and
Configuration Guide, Release 12.0 (1) at https://www.cisco.com/c/en/us/support/customer-collaboration/packaged-contact-center-enterprise/products-maintenance-guides-list.html
·
CVP Statistics for PCCE 2K, PCCE 4K and PCCE 12K deployments
This feature
enables the administrator to view statistics for CVP Call Server, VXML Server,
and Reporting Server in the Inventory page of Unified CCE Administration.
Note: CVP12.0(1) ES4 needs to be installed on the CVP call servers
for the CVP Statistics feature to work as expected.
· Call Progress Analysis (CPA) Parameters for Outbound
Campaign configuration. These parameters can be configured under ‘Advanced’
tab of the Campaign configuration.
This section lists the
Unified CCE components on which you can and cannot install this engineering
special.
You can install Unified CCE
12.0(1) ES26 on these Unified CCE components:
· AW
· Router / Rogger
Do not install this engineering special on the components
which are other than:
· AW
· Router / Rogger
If you are having a Fresh Install/Tech
Refresh of P/CCE 12.0(1) on Windows Server 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).
Installation
of this patch requires all CCE services to be shut down during the entire period
of 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 following the instructions on the screen
3.
Using
the CCE Service Control, start all CCE services again.
Note: Remove patches in the reverse order
of their installation. For example, if you installed patches 3, then 5, then 10
for a product, you must uninstall patches 10, 5, and 3, in that order, to
remove the patches from that product.
This section provides a
list of significant Unified CCE defects resolved by this engineering special.
It contains these subsections:
Note: You can view more information on
and track individual Unified CCE defects using the Cisco Bug Search tool,
located at: https://bst.cloudapps.cisco.com/bugsearch/search?null.
This section lists caveats
specifically resolved by Unified CCE 12.0(1) ES26.
Caveats in this section are
ordered by UNIFIED CCE component, severity, and then identifier.
|
Identifier |
Severity |
Component |
Headline |
|
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 |
|
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 |
|
CSCvq12348 |
2 |
dbconfig |
Departmental Administrator not allowed to create agent or enable Email & Chat support |
|
CSCvq88066 |
2 |
dbconfig |
PCCE v12 Supervisor re-skilling agent/skills page blank after installing ES21 |
|
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 |
|
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 |
|
CSCvp86341 |
3 |
dbconfig |
ECE Differential sync fails under certain condition |
|
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 |
Agent State after RONA to READY, updates RNA Timer to 120 in PCCE and System validation rule alert |
|
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 |
|
CSCvp19303 |
3 |
template |
DataCenter based sorting is not working in DialNumber page |
|
CSCvq07040 |
2 |
web.config.api |
CUIC Out-of-Sync post failover operation in the PCCE2k-SPOG inventory |
|
CSCvq27248 |
3 |
web.config.api |
ECC Payload API deficient in UCCE deployments, without ECC API support |
|
CSCvp34995 |
3 |
web.config.ui |
Unable to Add 20 Custom Gateways if Remote ICM is Configured |
|
CSCvo71587 |
3 |
Install |
Websetup doesn't come up after installing ICM12.0(1) ES6 |
|
CSCvp92559 |
2 |
web.setup |
websetup router API throws java.lang.NumberFormatException while creating router |
Caveats are ordered by
severity then defect number.
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.
<hr size=3
width="100%" align=center>
Defect Number: CSCvo46854
Component: dbconfig
Severity: 2
Headline: ECE goes OOS when the department is
getting created
Symptom: Create
same department in CCEadmin similar
to the one present in ECE
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.
<hr size=3
width="100%" align=center>
Defect Number: CSCvo78127
Component: dbconfig
Severity: 2
Headline: SipServerGroup
issues
Symptom: SipServerGroup will not clear the selected members when
site is changed.
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.
<hr size=3
width="100%" align=center>
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.
<hr size=3
width="100%" align=center>
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.
<hr size=3
width="100%" align=center>
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.
<hr size=3 width="100%"
align=center>
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.
<hr size=3
width="100%" align=center>
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: 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: 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: 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.
<hr size=3
width="100%" align=center>
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.
<hr size=3
width="100%" align=center>
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.
<hr size=3
width="100%" align=center>
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.
<hr size=3
width="100%" align=center>
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.
<hr size=3
width="100%" align=center>
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.
<hr size=3
width="100%" align=center>
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.
<hr size=3
width="100%" align=center>
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.
<hr size=3
width="100%" align=center>
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.
<hr size=3
width="100%" align=center>
Defect Number: CSCvo59157
Component: dbconfig
Severity: 3
Headline: PCCC 12.0 SIP Header Passing to ICM
should not require parameter
$$IGNORE
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: 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.
<hr size=3
width="100%" align=center>
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: 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.
<hr size=3
width="100%" align=center>
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.
<hr size=3 width="100%"
align=center>
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: 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: 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.
<hr size=3
width="100%" align=center>
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: CSCvq27248
Component: web.config.api
Severity: 3
Headline: ECC Payload API deficient in UCCE
deployments, without ECC API support
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: 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: Agent State after RONA to READY,
updates RNA Timer to 120 in PCCE and System validation rule 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: 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) In IIS MAnager --> Default Web Site --> ISAPI filters, there
are 2 configured entries. One named "tomcat" and the other named
"jakarta".
Conditions: None
Workaround: 1. Open IIS Manager and traverse to "Default Web
Site".
2. Open
"ISAPI Filters".
3. Remove
the ISAPI filter named "jakarta".
4. Restart
IIS service.
Further Problem Description:
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:
To provide comments about
this document, send an email message to the following address:
contactcenterproducts_docfeedback@cisco.com
We appreciate your
comments.
Cisco.com is a starting
point for all technical assistance. Customers and partners can obtain documentation,
troubleshooting tips, and sample configurations from online tools. For
Cisco.com registered users, additional troubleshooting tools are available from
the TAC site.
Cisco.com provides a broad
range of features and services to help customers and partners streamline
business processes and improve productivity. Through Cisco.com, you can find
information about Cisco and our networking solutions, services, and programs.
You can also resolve technical issues with online technical support and
download software packages. Valuable online skill assessment, training, and
certification programs are also available.
Customers and partners can
self-register on Cisco.com to obtain additional personalized information and
services. Registered users can order products, check on the status of an order,
access technical support, and view benefits specific to their relationships
with Cisco.
The Cisco TAC site is
available to all customers who need technical assistance with a Cisco product
or technology that is under warranty or covered by a maintenance contract.
If you have a priority
level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to https://www.cisco.com/c/en/us/support/index.html.
P3 and P4 level problems
are defined as follows:
In each of the above cases,
use the Cisco TAC site to quickly find answers to your questions.
If you cannot resolve your
technical issue by using the TAC online resources, Cisco.com registered users
can open a case online by using the TAC Case Open tool at the following site: https://mycase.cloudapps.cisco.com/create/start/
If you have a priority
level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and
immediately open a case. To obtain a directory of toll-free numbers for your
country, go to the following sites:
P1 and P2 level problems
are defined as follows: