Cisco Cisco Unified Contact Center Enterprise 10.0(1) Leaflet

This deployment provides the following benefits:

It is simplified because multiple CTI OS Servers can be configured to use the same CTI Server.

This deployment model allows many small sites to use a single PG with multiple PIMs rather than 
each requiring its own PG.

This solution can reduce box count because all of the PG processes, including the PIM and CTI OS 
Server processes, are running on the same box.

This solution also allows the use of multiple PIMs under a single PG to connect to different 
Unified CM clusters to increase the scaling of a single Unified CCE PG. This is not applicable to 
the Unified System CCE PG.

Because the motivation for this new deployment model is to reduce box count, CTI OS Servers are 
required to reside on the same server with the rest of the PG processes.

This deployment has the following restrictions:

Each PG can be configured for only one peripheral type.

ARS and ERS peripheral types are supported in this deployment model.

Multi-instance deployments cannot add more than one CTI OS Server per instance.

This deployment model cannot be used with Unified System CCE peripherals, but it may be used 
with Unified CCE peripherals.

PGs are typically co-located with a peripheral. Allowing multiple peripherals per PG could result in 
some peripherals being situated remotely from the PG. This is not supported for some peripherals and 
remains unsupported in this case. For example, the Unified CM (Enterprise and System deployments) 
would not be aggregated in a single PG unless all the ACD and Unified CM peripherals were co-located 
on a local LAN with the PG. In general, the deployment rules associated with ACD integrations on a PG 
still apply. For those deployments supporting remote PGs, all network requirements (including 
bandwidth, latency, and availability requirements) must be met.

Scaling is reduced when this deployment model is implemented to 75% of the scaling capacity for a 
single CTI OS. For example, if a given configuration supports 1000 agents with a single CTI OS server, 
it will support 750 agents using multiple CTI OS servers. This is due to the extra overhead of extra 
CTI OS processes and to the extra processing load incurred by the CTI Server due to the extra clients. 
The exception to this is when this feature is used for supporting over 2000 agents (the CTI Manager 
limit) on Unified CCE. (See 

 for an example.) Note that this deployment is supported only 

when using the Unified CCE PG, and it does not support a VRU under the same PG (no Generic type 
supported).