Cisco Packaged Contact Center Enterprise Installation and Upgrade Guide, Release 10.0(x)
Downloads: This chapterpdf (PDF - 1.24 MB) The complete bookPDF (PDF - 4.0 MB) | The complete bookePub (ePub - 806.0 KB) | Feedback



Change History

Date Link Change



Initial publication

February, 2014

Hardware Requirements for C Series

Added C240 M3S TRC#1 Server.

February, 2014

Create a Virtual Machine from the OVA

Added RAID configuration for C240 M3S TRC#1.

March, 2014

Run RAID Config Validator Utility

Procedure change for RAID utility.

March, 2014

Create VM for Cisco Unified Intelligence Center Subscriber

Changed OVA file for direct install of Unified Intelligence Center Subscriber.

March, 2014

Base Configuration Updates

Update to base config parameters for user.microappToExtVXML and FromExtVXML.

March, 2014

Run Automation Script for Import and Run Automation Script for Export

Update to Golden Template Automation Script Import and Export topics. Developer change resulted from customer issue.

April, 2014

Run Windows Updates

Specified that user must select x64 platform when running the Windows hotfix.

July, 2014

Data Center Switch Configuration for UCS C-Series Server Ethernet Uplinks

Updated UCS C-Series Virtual Switch VLAN Tagging example.

July, 2014

Third-Party Software

Update the Java Runtime Environment (Optional)

Added Java version and upgrade information.

July, 2014

Set Deployment Type

Validate System and Build System Inventory

Added that when setting deployment to Packaged CCE PCCE-PAC-M1, the credentials entered for the Cisco Unified CCE Data Server Diagnostic Framework must be for a domain user account.

July, 2014

Configure Domain Manager

Added that the Cisco Root OU must be created in the same domain to which the Unified CCE servers belong.

July, 2014

Add Datastores to the Host Server

Specified that the user must add datastores to the host server after installing VMware vSphere ESXi.

About This Guide

This guide explains how to install, configure, and upgrade Packaged CCE.

Cisco Packaged Contact Center Enterprise (Packaged CCE) is a solution deployment for delivering Cisco Unified Contact Center Enterprise in a virtualized environment. Packaged CCE requires strict adherence to capacity limits that are detailed in the Cisco Packaged Contact Center Enterprise Design Guide, available at this location http:/​/​​en/​US/​products/​ps12586/​prod_​technical_​reference_​list.html. It is mandatory to follow all rules and requirements stated in the Design Guide.


This guide is prepared for partners and service providers who will be implementing Packaged CCE, who are familiar with Cisco contact center applications, and are experienced regarding the deployment and management of virtual machines using VMware technology.

Organization of This Guide

Section Content
Part I: Preparation

System requirements

Solution components

Prepare the customer site

Network design considerations

Part II: Installation: Golden Templates and Direct Installation
Procedures for the two installation options:
  • How to create Golden Templates and process them for export.
  • How to create Virtual Machines Directly.
Part III: Configuration Procedures for configuration of the Cisco contact-center products at the customer site.
Part IV: Version Upgrade Upgrade requirements and procedures
Appendix: Reference

External AW-HDS-DDS


Simple Network Management Protocol

UCS Network Configuration and QoS

Network Requirements and Fault Tolerance Considerations

Virtualization for Packaged CCE

Field Alerts and Field Notices

Note that Cisco products may be modified or key processes may be determined important. These are announced through use of the Cisco Field Alert and Cisco Field Notice mechanisms. You can register to receive Field Alerts and Field Notices through the Product Alert Tool on This tool enables you to create a profile to receive announcements by selecting all products of interest. Log into; then access the tool at:


Documentation Feedback

To provide comments about this document, send an email message to the following address:


We appreciate your comments.


This document uses the following conventions:



boldface font

Boldface font is used to indicate commands, such as user entries, keys, buttons, and folder and submenu names. For example:

  • Choose Edit > Find.
  • Click Finish.

italic font

Italic font is used to indicate the following:

  • To introduce a new term. Example: A skill group is a collection of agents who share similar skills.
  • For emphasis. Example: Do not use the numerical naming convention.
  • A syntax value that the user must replace. Example: IF (condition, true-value, false-value)
  • A book title. Example: See the Cisco Unified Contact Center Enterprise Installation and Upgrade Guide.

window font

Window font, such as Courier, is used for the following:

  • Text as it appears in code or that the window displays. Example: <html><title>Cisco Systems,Inc. </title></html>

< >

Angle brackets are used to indicate the following:

  • For arguments where the context does not allow italic, such as ASCII output.
  • A character string that the user enters but that does not appear on the window such as a password.