After you complete the configuration of the contact center applications , you must import and apply Packaged CCE base configuration data. If you do not apply the base configuration, you cannot change deployment type, your system cannot validate correctly, and you will need to configure each element manually. This pre-configured database, contained in a zip file that you download from Cisco, performs the following functions on the system:
Creates core system objects to support call routing and dial plan for Packaged CCE.
Creates two Peripheral Gateways:
One Generic PG with 1 CUCM PIM and 4 CVP PIMs
One MR PG with 2 PIMs - one for Outbound and one for Multichannel
Configures the system Correlation ID to be 1001-9999
Sets intelligent application defaults for the Packaged CCE deployment model:
Default Agent Desk Settings record
Enables ECC Variables
Create configuration objects to support CVP:
A type 10 Network VRU for CVP along with Network VRU Labels to send calls to CVP
CVP ECC Variables
VXML_Server Network VRU Script - GS,V microapp
Creates configuration objects to support Multichannel Configuration:
A Network VRU for the MR PG
Application Instance for Multichannel
Media Classes for Multichannel
Apply Base Configuration for Fresh Installs Only
The Base Configuration is run once on a fresh installation of Packaged CCE. If you have already applied the base configuration to Packaged CCE and are upgrading to a later release of Packaged CCE, do not download the base configuration a second time—in this instance, apply configuration changes manually.
Download the Domain_Update_Tool.zip file from the same location in Step 1. Save it locally and unzip it.
Unzip and copy the configuration folder to the local drive of CCE Data Server on Side A.
Open the ICMDBA Tool on the CCE Data Server on Side A.
Select the CCE Data Server and expand the tree to <instance name>_sideA.
Select Data on the menu bar and click Import.
Browse to locate the configuration folder and click Open.
Click OK and then click Import.
Click Start and then click OK on all messages.
Before you run PowerShell in Step 11 below, enter the command get-executionpolicy to determine whether the Restricted Execution policy is in effect or is restricted.
If the policy is restricted, enter set-executionpolicy. At the Supply Values prompt, enter "Unrestricted." Then enter 'Y". This changes the execution policy.
Navigate to the folder Domain_Update_Tool and right-click UpdateDomain.PS1. and Run with PowerShell. Respond as follows:
For Server name, enter the computer name of the CCE Data Server Side A.
For Database name, enter <instance_sideA (Logger database)>.
For Domain Name, enter the customer's domain name.
Return to the ICMDBA tool.
Click the logger database (for example, pcce_side A).
Open Data on the menu bar and click Synchronize.
Enter the hostname for the CCE Data Server on Side A.
Enter the database name as <instance name>_sideA for the source side.
Enter the hostname for the CCE Data Server on Side B.
Enter the database name as <instance name>_sideB for the target side.
Initialize the AW on Side B.
To do this, select Start > All Programs > Cisco Unified CCE Tools > Administration Tools > Initialize Local Database.
Click Start and then click OK on all messages.
What to Do Next
After running base configuration and before changing deployment type to Packaged CCE, you must perform prevalidation configuration.
Set Deployment Type and Run System Validation
Sign in and select deployment type
After you have completed installation and configuration, sign in to Packaged CCE to select the Packaged CCE deployment type.
To sign in and select the deployment type:
Point to https://<IP Address>/cceadmin/Container.jsp, where <IP Address> is the address of either CCE data server (the one on Side A or the one on Side B).
At the sign in page, enter the Active Directory username and password. This opens the Configure Deployment page, showing the default deployment type of Not Specified.
Select Packaged CCE: CCE-PAC-M1 from the drop-down. This launches the VM Validation process to ensure that the deployment is in conformance with the required virtual machine specifications, capacity limits, and system validation rules.
Enter fields for the Host (or IP address), Username, and Password for the two core servers (Side A and Side B).
After a successful validation, you see a Congratulations message.
If the Host (or IP address), Username, or Password entries were invalid, you see a Could Not Connect message.
If either the server or any of the VMs do not meet requirements, you see a message indicating connection problems. This message has a link to a log file. Open this file to see whether the servers are valid and whether all VMs match the deployment profiles.
Sample log file showing summary of invalid results
VM Validation Results: Wed Jun 20 08:05:36 EDT 2012
Valid Systems: 0 of 1
ESX Server: sideB
ESX Server Properties Valid: true
VM Layout Valid: false.
The information at the top of the log is a summary of the results. This log shows that the server is valid but the VM layout is not.
Sample log showing invalid server
This shows that the server does not have the required number of CPU Cores.
Required Version: 5.0.0
Required Min CPU Cores: 20
Required Min Memory (MB): 95000
Required HD(s) (GB): [1392, 1949, 273]
Required Bios <Major version>: C260
Required Vendor: Cisco Systems Inc
Found Version: 5.0.0
Found CPU Cores: 10
Found Memory (MB): 98185
Found HD(s) (GB): [1392, 273, 1949]
Found Bios: C222.214.171.124b.0.102620111637
Found Vendor: Cisco Systems Inc
Sample log showing valid VM
Virtual Machines Matching Defined Profiles:
Profile: Unified CCE Data Server
OS: Microsoft Windows Server 2008 R2 (64-bit)
CPU Cores: 4
RAM (MB): 8192
HD(s) (GB): [80, 750]
VMWare Tools Version: 8384
There are three log entries for invalid VMs:
Required Profiles without Matching Virtual Machines This means system does not have VMs present that match our requirements.
Optional Profiles without Matching Virtual Machines This means that the CVP Reporting profile, which is defined as optional, does not exist on the system. This does not block validation.
Virtual Machines without Matching Profiles This means the system has VMs that do not match requirements. They might be extra VMs or incorrectly-configured VMs.
Capacity and validation rules pages in the user interface
Two screens in the user interface, both accessed by tabs on the Home menu, show additional system information, with indicator for what you must address:
Capacity Info shows the maximum capacity that Packaged CCE supports, whether your system is within those limits, and what percentage of the maximum is currently used. For example, if the maximum capacity is 100 reason codes and your system has 300, the capacity indicator will be red.
System Validation shows the software specifications for which Packaged CCE has been qualified and whether your system conforms to those rules. For example, if exactly 9 ECC Variables are required for CVP and your system has 8 or 10, the Is Valid indicator will be red.
Validation for other system types
For Packaged CCE: CCE-PAC-M1 Lab Only, the same Capacity Info and System Validation checks apply. There is no VM Validation for these lab systems.
For all other deployment types, no VM validation, Capacity Info, or System Validation takes place.
The Deployment Type drop-down menu on the Packaged CCE Configure Deployment screen offers 14 options.
The two options appropriate for Packaged CCE are Packaged CCE: CCE-PAC-M1 and Packaged CCE: CCE-PAC-M1 Lab Only.
Packaged CCE: CCE-PAC-M1
Capacity check for full call capacity (8 cps / 1000 agents)
Validation of all VMs (CCE, CVP, CUIC, UCM, Finesse)
The production option enables full call capacity (8 cps / 1000 agents) and checks hardware and all VMs footprint (CCE, CVP, CUIC, UCM, Finesse).
Requires duplexed C260 servers.
Select this option if you want a system that runs at production-level call capacity.
Packaged CCE: CCE-PAC-M1 Lab Only
No VM Validation
Allows installation on any hardware.
Select this option for demo systems.
The lab only option reduces the call capacity of the system to 1 CPS and allows a maximum of 50 agents.
All other types
Configuration Manager Changes for Unified CCE
After you run the base configuration using ICMDBA and have changed the deployment type, you must perform the tasks listed here in Cisco Unified CCE Configuration Manager.
If you are using an Administration Server and Real-time Data Server system or an Administration Client system, double-click the Unified CCE Tools icon on the desktop, and then choose Administration Tools.
Create Agent Targeting Rule
Configure Dialed Numbers.
Configure routing in Script Editor and schedule for the Call Type.
Configure routing and administrative scripts.
Make a Call
This section explains to make a call:
Start up all Unified CCE services if they are not set to Auto Start.
#Configure VXML leg where the incoming called-number matches the Network
dial-peer voice 9999 voip
description Used for VRU leg
incoming called-number 777T
dtmf-relay rtp-nte dtmf-relay rtp-nte
voice-class codec 1
The value configured in Unified CM Administration Clusterwide Domain Configuration must match the Server Group name in Unified CVP Server Groups
Packaged CCE 9.0(x) has been localized for 14 languages.
If a customer requires one of these languages instead of the default (English), you can download the Packaged CCE Language Pack executable from the Download Software page.
Install Language Pack
Install the Language Pack on both CCE Data Servers (Side A and Side B) and on any external HDS systems. Once the Language Pack is installed, the Unified Web Administration Sign-In page is populated with a language drop-down menu that lists all languages. Select a language to display the user interface and the online help in that language. The system retains that language selection until you change it again.
Important: Install at off-peak hours. The CCE Data Servers and external HDS systems are not usable during the installation of the Language Pack.
UnInstall Language Pack
The customer can uninstall the Language Pack from Windows Control Panel > Programs and Features > Uninstall or change a program.
Microsoft SQL Server Collation Settings for Languages
This table shows the languages supported by Packaged CCE 9.0(x) and the SQL Server Collation setting for each. You must select a collation when you install Microsoft SQL Server 2008 R2, and it must be the collation that maps to the customer's language display.
If your initial collation selection is incorrect, the customer will need to uninstall Microsoft SQL Server and reinstall it with the correct collation configuration.
SQL Server Collation Setting
Windows System Locale
If the Windows system locale differs from the display language, some characters will appear incorrectly in the user interface and will be saved incorrectly to the database. For example, if the system locale is English and users are working in Spanish, characters such as the acute a will not appear correctly.
To change the system locale, perform this procedure at both CCE Call Servers, both CCE Data Servers, and any external HDS systems.
Open Control Panel > Region and Language.
Click the Administrative tab.
Under Language for non-Unicode programs, click Change System Locale.
Select the language and click OK.
Click the Format tab.
Under Format, match the language you selected in Step 4.