Cisco Cisco Customer Response Solution Downloads Design Guide

This Chapter discusses the design implications of where IPCC Express is located in your network with 
respect to call processing resources. On a systems level, how IPCC Express is deployed can affect its 
performance, possibly even compromising functionality. This section addresses the importance of the 
IPCC Express location within a Cisco CallManager deployment.

The IPCC Express design considerations in this section focus on the following main IP Telephony 
deployment models:

This section assumes that you are already familiar with the Cisco Architecture for Voice, Video, and 
Integrated Data (AVVID) network infrastructure and the Cisco CallManager cluster design 
considerations for each deployment model. For more information on the infrastructure and design 
models, refer to the Cisco IP Telephony Solution Reference Network Design documentation, available 
online at 

The IPCC Express reference architecture shown in Figure 2-1 represents a single IPCC Express contact 
center as it can be maximally deployed in Release 3.5

1

. The deployment consists of one central site and 

four remote sites. At the central site, an IPCC Express primary server, its (optional) cold standby server, 
and four IPCC Express Expansion Servers are deployed. The deployment as shown consists of the 
maximum number of servers supported for IPCC Express at its primary server site. Each remote site, in 

1. 

Release 3.1 supports the same reference architecture; however, Release 3.0 does not. Specifically, Re-

lease 3.0 does not support either a historical reporting server nor any local or remote monitoring and re-
cording servers