Cisco Cisco Unified Contact Center Enterprise 9.0(1) Guia Do Desenho

These are the only possible deployments of System Unified CCE. It is installed and configured using a 
specific set of tools, and those tools cannot handle any other options. For example:

System Unified CCE does not support installing the Outbound Controller on the same server as a 
PG; it must be installed on its own server.

System Unified CCE does not support adding a second Unified CCE System PG peripheral. One 
peripheral is the only model that is supported.

System Unified CCE does not allow configuration of a VRU PG and connection to Unified CVP. 
Unified CVP is not supported by System Unified CCE.

However, if the deployment that is being installed falls within the parameters required by System Unified 
CCE, there are several benefits:

Streamlined installation — You can install and configure System Unified CCE as a single unit rather 
than having to install and configure each component separately.

Web-based administration for both registry and database configuration — All configuration is done 
through the web interface, so it is no longer necessary to run local setup to change registry 
configuration.

Certified configurations that have been tested to work together

For a large number of Unified CCE customers, System Unified CCE will meet their requirements and 
provide benefits of simpler installation and administration. For customers with more complex 
requirements, traditional Unified CCE is supported with manual installation and administration using 
Unified ICM Setup and Unified ICM Configuration Manager. For those configurations that System 
Unified CCE does fit, the reduced deployment time and ease of administration provide significant 
benefits.

Unified CCE Gateway PG allows Unified CCE or Unified CCX to appear as a traditional ACD connected 
to the Unified ICM system. Unified CCE Gateway PG does this by providing a PG to the Unified ICM 
system that communicates to the CTI interface of Unified CCE System PG or Unified CCX.

When Unified CCE Gateway PG is used in a deployment, its relationship of Unified ICM is termed a 
parent and Unified CCE is called the child:

Parent

The Unified ICM system that serves as the network or enterprise routing point. The child looks like 
an ACD to the parent, which uses the appropriate Unified CCE Gateway PG (Enterprise or Express) 
to communicate to the CTI interface on the child Unified CCE. The parent can perform all functions 
that a Unified ICM can usually perform, including pre- and post-routing and end-to-end call tracking 
using translation routes.

Child

The Unified CCE System PG or Unified CCX system that is set up to function as an ACD. The child 
can receive calls that are translation-routed from the parent, but it is not aware of any other 
peripherals attached to the parent. The child can also post-route calls from the Unified CCE to the 
parent, where the call can be handled like any other Unified ICM call. For example, the call could 
be translation-routed to any (TDM or IP) ACD controlled by the Unified ICM or queued in the 
Unified ICM network queue point with Unified CVP.

In the parent/child model, the child Unified CCE is configured to function completely on its own and 
does not need the connection to the parent to route calls to agents. This independence provides complete 
local survivability for mission-critical contact centers if the network between the child and parent goes