Cisco Cisco Customer Voice Portal 8.0(1) Design Guide

Observe the following design considerations when implementing Server Groups:

When you are using the Local SRV configuration, that configuration does not work with the DNS 
SRV configuration. However, elements may be declared as A record hostnames instead of IP 
addresses, and resolved through a DNS server lookup or in the OS etc host file.

If you are using the CUP proxy, typically the SRV cluster name (such as proxy-servers.cisco.com) 
will need to be defined in the service parameters section of the proxy configuration. Otherwise a 404 
not found rejection may result. The CUSP proxy has a similar configuration in the CLI.

The CVP log file has traces which show endpoint status events. Refer to the Unified CVP System CLI 
instructions in the Configuration and Administration Guide for Cisco Unified Customer Voice Portal, 
available at: 

An H.323 gatekeeper is used when using H.323 in any of the ICM-integrated deployment models except 
Model #4 (VRU Only with NIC Controlled Routing), which does not use Unified CVP for call control 
at all. Additionally, if SIP is used as the call control protocol, the gatekeeper is not required. An 
originating gateway can perform all of its H.323 call routing by using VoIP dial-peers that contain static 
IP addresses, whereas the Unified  CVP H.323 Service must always perform a gatekeeper Remote Access 
Service (RAS) lookup to route calls.

In one particular situation, when using the VBAdmin SetTransferLabel option, the H.323 Service 
ignores the IP address returned from the gatekeeper and instead routes the IVR call leg back to the 
originating gateway from which the call arrived. This feature ensures that no WAN bandwidth is used 
during IVR treatment or queuing. A gatekeeper is still required in this situation because the H.323 
Service has to perform the gatekeeper lookup function to obtain possible alternate endpoints in the event 
that the attempt to transfer the call to the originating gateway fails.

Unified CVP can use one of the following types of gatekeeper high-availability mechanisms:

Only HSRP and alternate gatekeeper are supported by Unified CVP. Alternate gatekeeper support was 
introduced in Unified CVP 3.1 SR1.

HSRP is a Cisco proprietary router redundancy protocol that allows two or more gatekeepers to share 
the same IP address in an active/standby fashion. Using HSRP, two gatekeepers work together to present 
the appearance of a single virtual IP address on the LAN.