Cisco Cisco Customer Voice Portal 8.0(1) Design Guide

In 

, two switches provide the first level of network redundancy for the Unified CVP Servers:

If one switch fails, only a subset of the components becomes inaccessible. The components 
connected to the remaining switch can still be accessed for call processing.

If a Content Services Switch (CSS) is used, its redundant partner must reside on the same VLAN in 
order to send keep-alive messages to each other via Virtual Router Redundancy Protocol (VRRP), a 
protocol similar to Hot Standby Router Protocol (HSRP). If one of the switches fails, the other CSS 
is still functional.

Although 

 shows a CSS being used for redundancy, you may also use the Application 

Content Engine (ACE). Refer to 

.

For more information on data center network design, refer to the Data Center documentation available at 

NIC teaming is not currently supported in the Unified CVP solution.

Cisco recommends that the NIC card and ethernet switch be set to 100 MB full duplex for 10/100 links, 
or set to auto-negotiate for gigabit links.

The function of the originating gateway in a Unified CVP solution is to accept calls from the PSTN and 
direct them to Unified CVP for call routing and IVR treatment.

This section covers the following topics:

For the most current information on how to provide redundancy and reliability for originating gateways 
and T1/E1 lines, refer to the latest version of the Cisco Unified Contact Center Enterprise Solution 
Reference Network Design (SRND), available at 

In addition, consider the following issues when designing gateways for high availability in a Unified 
CVP solution:

When used in ICM-integrated models, the originating gateway communicates with Unified CVP 
using H.323 or SIP. Unlike MGCP, SIP and H.323 do not have redundancy features built into the 
protocol. Instead, SIP and H.323 rely on the gateways and call processing components for 
redundancy.

When configuring the gateway, it is best to bind the H.323 or SIP signaling to the virtual loopback 
interface, as illustrated in the following configuration examples:

H.323: