This document provides installation instructions for Unified CCE 12.0(1)
ES15. 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 adds support for the following features to PCCE 12.0(1):
· CVP Statistics in CCE Administration UI. Note: CVP12.0(1) ES3 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.
UCCE 12.0(1)
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) ES15 on these Unified CCE components:
Do not install this engineering special on the components which are other
than:
·
Using the ICM Service Control, stop all the ICM
services running on the system
·
Launch the Installer provided for ES15 and
following the instructions on the screen
·
Using the ICM Service Control, start all ICM
services again.
Note:
If Web Setup does not come up after
installing this ES, Run SSL Encryption Utility and follow the below steps
·
Run SSL Encryption Utility under Cisco Unified
CCE Tools
·
Select ALL INSTANCES
·
Select 'Enable Encryption' option in Web Setup
·
Select Apply
·
Restart Tomcat service
· 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.
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)
ES15.
Caveats in this section are ordered by UNIFIED CCE component, severity, and
then identifier.
|
Identifier |
Severity |
Component |
Headline |
|
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 |
|
CSCvp28792 |
2 |
dbconfig |
Fresh Install wizard throws error for ESXi C240 M4 servers for PCCE 2K |
|
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 |
|
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 |
|
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 |
|
CSCvp47136 |
3 |
dbconfig |
Transferable Files File Upload API endpont has to be changed |
|
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. |
|
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 |
|
CSCvn78163 |
3 |
dbconfig |
Campaign Skill group Search Pop-over is not working as expected |
|
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 |
|
CSCvn71946 |
4 |
dbconfig |
Advanced search for IP Address in inventory throws an internal server error |
|
CSCvn78580 |
4 |
dbconfig |
Minor alignment issues in IE |
Caveats are ordered by severity then defect number.
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:
Defect Number: CSCvp03348
Component: dbconfig
Severity: 2
Headline: unable to create main site in PCCE 12k.
Defect Number: CSCvp11040
Component: dbconfig
Severity: 2
Headline: Dialed Number Bulk DELETE does not work in PCCE 4K/12K
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:
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:
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:
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: None
Workaround: None
Further Problem Description:
Defect Number: CSCvo15059
Component: dbconfig
Severity: 3
Headline: Inconsistent behavior for 'Cancel' button click in Device Configuration UI
$$PREFCS
Symptom: Steps: 1)Login to cceadmin 2)Go to
Infrastructure Settings-->Device Configuration 3)Go to CVP Reporting
Server-->Click on Properties tab and Click on Database Configuration tab now
click on 'Cancel' and see Database Configuration fields are displayed in
Properties tab
Conditions: Database Configuration fields are displayed in Properties tab
in CVP Reporting Server
Workaround:
Further Problem Description:
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.
Defect Number: CSCvo45192
Component: dbconfig
Severity: 3
Headline: PG explorer marks entries as modified during normal traversal
$$PREFCS
Symptom:
Conditions:
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:
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:
Defect Number: CSCvo61931
Component: dbconfig
Severity: 3
Headline: Updating an ECE Agent with same screenName, ECE goes to out-of-sync
$$PREFCS
Symptom: 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, If Admin makes the
option true and give a new screenName or existing screenName, ECE goes to out of sync.
Conditions: None
Workaround: Using Bulk Upload with same/different screenname of an ECE
agent, ECE is not going Out of Sync
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:
Defect Number: CSCvo98128
Component: dbconfig
Severity: 3
Headline: Disable Routing Client names in PG Explorer (UCM , VRU , MR PG) for PCCE deployment
$$IGNORE
Symptom:
Conditions:
Workaround:
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
Defect Number: CSCvp11036
Component: dbconfig
Severity: 3
Headline: Unable to create Agents and AgentTeam using bulk job in PCCE 4K/12K
Defect Number: CSCvp47136
Component: dbconfig
Severity: 3
Headline: Transferable Files File Upload API endpont has to be changed
$$PREFCS
Symptom:
Conditions:
Workaround:
Further Problem Description:
Defect Number: CSCvn77418
Component: dbconfig
Severity: 3
Headline: Incorrect error thrown on deleting
gateways associated with location
Symptom: Database
transaction error is seen in SPOG UI
Conditions: When trying to delete a gateway associated with location
Workaround: NA
Further Problem Description:
Defect Number: CSCvn77421
Component: dbconfig
Severity: 3
Headline: IdS is
reporting incorrect status in SPOG UI
Symptom: IdS is reporting incorrect status in SPOG UI
Conditions: When checking from SSO under device configuration
Workaround: NA
Further Problem Description:
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: 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:
Defect Number: CSCvn82112
Component: dbconfig
Severity: 3
Headline: DeploymentSettings
and SignOut Ui issues in Fresh Install
Symptom: DeploymentSettings and SignOut Ui issues in
Fresh Install
Conditions: None
Workaround: NA
Further Problem Description:
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:
Defect Number: CSCvo35666
Component: dbconfig
Severity: 4
Headline: PCCE: domain admin can still see removed tools from config manager
Symptom: 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.
Conditions: ICM-Config/Setup admin is NOT a PCCE CCEAdmin
Workaround:
Further Problem Description:
Defect Number: CSCvo61941
Component: dbconfig
Severity: 4
Headline: ECE Database Server is referred as services server in edit page of the inventory
$$PREFCS
Symptom: ECE Database Server is referred as services server in edit page of
the inventory
Conditions: None
Workaround: None
Further Problem Description:
Defect Number: CSCvn71946
Component: dbconfig
Severity: 4
Headline: Advanced search for IP Address in
inventory throws an internal server error
Symptom: Advanced search for IP Address in inventory throws an
internal server error
Conditions: None
Workaround: NA
Further Problem Description:
Defect Number: CSCvn78580
Component: dbconfig
Severity: 4
Headline: Minor alignment issues in IE
Symptom: Minor alignment issues in IE
Conditions: None
Workaround: NA
Further Problem Description:
Defect Number: CSCvn78163
Component: dbconfig
Severity: 3
Headline: Campaign Skill group Search
Pop-over is not working as expected
Symptom: Org Settings → Campaign.
Click new and
go to Skill group tab
Add
New. Click on Skill Group search adder. First it’s
coming as empty, and try type something and remove it. It will display all
skill groups.
Conditions: None
Workaround: NA
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: