Cisco Cisco IPCC Web Option Leaflet

Component location and administration are centralized.

Calls are treated and queued locally, eliminating the need for queuing across a WAN connection.

There is less load on Unified CM because Unified CVP is the primary routing point.   This allows 
higher scalability per cluster compared to Unified IP IVR implementations. See 

, for more information.

WAN connections to agent sites must be provisioned with bandwidth for voice as well as control 
and CTI. See 

more information.

A local voice gateway might be needed at remote sites for local out-calling and 911.

Load balancing of calls across Unified CVP Call Servers is managed by SIP and Cisco Unified Presence 
Proxy Services. The load balancing does not take into account the site where the call came in, but calls 
are distributed based on simple load balancing rules define in Cisco Unified Presence (for example, 
alternate call distributions across configured Unified CVP Call Servers and preferential weighting of 
Call Servers).

Currently, if the system is designed to do so, Unified CVP can queue the call at the ingress gateway. This 
requires that Unified CVP be configured with settransferlabel for H.323 or Send To Originator for 
SIP, to match the NetworkVRU label. This will cause Unified CVP to send the call back to the ingress 
gateway for queuing when a label matching this NetworkVRU label is returned from Unified ICM. 
Currently Unified ICM is unaware of the location of the initial gateway, therefore it cannot make a label 
selection based on the original ingress location of the call.