Cisco Cisco Unified Customer Voice Portal 11.0(1)

 shows a Enterprise environment deployment.

In 

, the customer retains the ICM software and HTTP Media Servers, while the Gateways, 

CVPs, ASR/TTS servers, and NAM software are in the network. In this method, the end customer 
controls and manages all the business logic, while the Gateways, CVPs, and ASR/TTS servers provide 
the infrastructure.

HTTP Media Servers can be physically co-located with the Voice Browsers to reduce network bandwidth 
demands.

CVP’s Web-based architecture allows the use of Web methods to handle issues like fault-tolerance, 
scalability, etc. With the CVP:

Scaling, fault-tolerance, and file distribution are standard Web issues, with standard solutions.

By making Gateways, Voice Browsers, Application Servers, and Media Servers available in the IP 
network, the network itself enables IVR services and switching for carrier or customer Web 
applications.

The ability to place Gateways, Voice Browsers, and Media Servers at the edges of the IP network 
reduces the bandwidth demands on the central part of the network itself.

The CVP can accommodate internal fail-over in case a particular component is having difficulties or 
needs to be upgraded. For example, if an CVP Voice Browser or Gateway Voice Browser is looking for 
an Application Server and cannot connect with its normal Application Server, it can fail over to a 
different Application Server. 

When using the Gateway for IVR treatment, a content switch may be used to load balance and provide 
failover capabilities between the Gateway and Application server and between the Gateway and the 
media server (ASR/TTS/HTTP).