This document provides installation instructions for Unified CCE 11.6(1) ES27. 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.
Support for Tested Reference Configuration as M3/M4 Tested Reference Configuration and M5 Tested Reference Configuration / Specification Based Configuration"
11.6
You can install Unified CCE 11.6(1) ES27 on these Unified CCE components:
Do not install this engineering special on the following components:
Installation of this patch requires that all ICM services are shut down during the entire installation process. It is always recommended to install this ES during a scheduled downtime.
·
Using the ICM Service Control, stop all the ICM services running on the
system
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.
Specification Based Hardware Support
Instruction in this
Engineering Special
Select
and Initialize the Packaged CCE Deployment
The steps for
selecting and initializing your deployment type depend on which deployment type
you are using.
Initialize
the Packaged CCE Deployment Type
When you sign
into Unified CCE Administration for the first time, you are prompted to enter
information and credentials for the components in your deployment. Packaged CCE
uses this information to configure the components and build the System
Inventory.
Procedure
Step
1:
On the Deployment page, select the instance from the Instance drop-down list. You must be a member of the
Setup security group for the instance you select. Click Next.
Note
The system does not support IP address change. Use the hostname if
you foresee a change in IP address. This is applicable for all the Hostname/ IP Address fields.
Step
2:
On the VM Host page, enter the IP address, Username, and
Password for the VMware hosts for Side A and Side B. Select the hardware layout
type as M3/M4 Tested Reference Configuration or
M5 Tested Reference Configuration / Specification Based Configuration.
Click Next.
The VMware hosts are the two servers on which ESXi is installed. The username and password fields are the
host login names and passwords configured in ESXi.
Packaged CCE
validates the hosts in your deployment.
•
If you select M3/M4 Tested
Reference Configuration and click Next,
the system checks if the hardware is supported UCS hardware and verifies if the
VMs are configured as per the reference design. If the validation is
successful, the Credentials page
opens.
•
If you select M5 Tested Reference Configuration / Specification
Based Configuration and click Next,
the system validates the hardware specifications of the VMware host and
verifies if the VMs are configured as per the reference design. If the
validation is successful, click Next to
open the Credentials page. See the Virtualization
for Cisco Packaged CCE at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/uc_system/virtualization/pcce_virt_index.html
for hardware specifications.
•
If the validation fails, click Update Hosts to go back to the VM Hosts page and edit the values. Click Retry to run the validation with existing values.
Note
• Datastores
used by Cisco VMs should not be shared or used by other third-party VMs.
• Packaged CCE core components include:
• Unified CCE Rogger
• Unified CCE AW/HDS/DDS
• Unified CCE PG
• Unified CVP Server
• Unified CVP OAMP Server
• UnifiedIntelligence
Center Publisher
• Finesse
VM
annotations are used to identify Packaged CCE core component VMs. Do not change
the default annotations of any of the core component VMs. The following terms
are reserved for core component annotations: Cisco, Finesse, CUIC, and CVP. Do
not use these reserved terms in the annotations of any of the non-core
component VMs.
Step
3
On the Credentials page, enter the specified information for each
component in your deployment. After entering information for a component, click
Next.
The system validates the credentials you entered
before prompting you for the next component's information.
|
Component |
Information Required |
|
Unified CM |
Either: •
The Unified CM Publisher for an on-box Unified
Communications Manager deployment.
•
The Unified CM Publisher Name and IP address
for an external Unified Communications Manager deployment.
Note Only a single Unified CM cluster can be
integrated to a single Packaged CCE
deployment. AXL username and password. |
|
Unified CVP |
Unified CVP
Server (Side A) username and password. Unified CVP Server (Side B) username
and password. |
|
Unified CCE
AW-HDS-DDS |
Unified CCE
Diagnostic Framework Service domain, username, and password. These
credentials must be for a domain user who is a member of the Config security group for the instance, and valid on all
Unified CCE components in your deployment (the Side A and Side B Unified CCE Roggers, PGs, and AW-HDS-DDSs). |
|
Unified
Intelligence Center |
Unified
Intelligence Center Administration application username and password.
Identity Service Administration username and password. |
|
Finesse |
Finesse
Administration username and password. |
Step
4
On the Settings page, select the following:
•
Select the codec used for Mobile Agent calls
from the Mobile Agent Codec drop-down
menu. The
codec
you select must match the codec specified on the voice gateways.
•
If you have an external Unified Communications
Manager, select the Unified CM Subscribers to which the Side A and Side B
Unified CCE PGs connect from the Side
A Connection and Side
B Connection drop-down menus.
•
For the Automatically
create service accounts check box, either:
◦Leave
the check box checked if you want automated initialization to create the
service accounts
in
Active Directory.
These
accounts will be created and added to the Service group.
◦Uncheck
the check box if you want to use an existing Active Directory account. Enter
the username and password for an existing Active Directory user in the same
domain as the Packaged CCE servers.
This
account will be added to the Service group.
Click Next.
◦The deployment is
initialized. The Details dialog
box displays the status of the automated initialization tasks.
Step 5
After the
automated initialization tasks complete, click Done. The System
Inventory opens. If one of the automated initialization
tasks fails, correct the errors and then click Retry.
If the retry is
successful, the automated initialization continues.
For some task
failures, all completed tasks must be reverted before the task can be retried.
You see a message informing you that the system needs to be reverted to a clean
state.
Click OK, and then after the system is in a clean state,
click Start Over.
Note
: For complete documentation pleases refer to the Package CCE
Specification Based Hardware_01
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 11.6(1) ES27.
Caveats in this section are ordered by UNIFIED CCE component, severity, and then identifier.
| Identifier | Severity | Component | Headline |
|---|---|---|---|
| CSCvk03510 | 3 | dbconfig | PCCE support for BE7KH M5 hardware. |
Caveats are ordered by severity then defect number.
Defect Number: CSCvk03510
Component: dbconfig
Severity: 3
Headline: PCCE support for BE7KH M5 hardware.
$$IGNOREYou 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: