Cisco Cisco IP Contact Center Release 4.6.1 Installation Guide

economies over having two separate Unified CCE setups for each Unified ICME parent, in that
the Unified CCE CallRouter and Logger and Admin Workstation (AW)/WebView/HDS can
be shared between them.

Note: Although Unified IP IVR or Unified CVP can be used as the IVR, in the following figure,
in the child, IVR refers to Unified IP IVR. For a graphic showing the use of Unified CVP, see
the section 

.

Figure 3: Multiple Unified ICME parents with a single Unified CCE child

Note: Call types on the Unified CCE child must not span peripherals. That is, a separate set of
Call Types is required for each peripheral on the child. This is to keep the correlation between
the Call Type on the child to a single peripheral on the parent. Failure to do this results in the
Unified ICME parent (Services) seeing only a subset of the calls corresponding to the Call Type
on the child. See 

 for more details.

Single Unified ICME Parent with Multiple Unified CCE Children

This deployment shows a Unified ICME parent with two IPCC Enterprise Gateway PGs
connected to two Unified CCE children with IPCC System PGs. Each Gateway PG can connect
to only one IPCC System PG.

Note: The Unified CCE child systems could be branch offices or service bureaus.

This deployment allows calls to be translation-routed from the Unified ICME parent, which is
the Customer shown in 

 to either of the two Unified CCE children (Provider

Site 1 and Provider Site 2 in 

), each of which is treated as a separate ACD

by the parent Unified ICME. In the figure, Unified CVP, which is being used at the Customer
site, is shown here doing network queuing from the Unified ICME parent. This deployment
also provides the ability for each child Unified CCE to route incoming calls to those sites through

Cisco Contact Center Gateway Deployment Guide for Cisco Unified ICME/CCE/SCCE/CCX Enterprise Releases 7.5(1) and Express Release 7.0(1)