Cisco Cisco Customer Voice Portal 8.0(1) Design Guide

Page of 223
 
4-24
Cisco Unified Customer Voice Portal (CVP) 8.x Solution Reference Network Design (SRND)
OL-15989-06
Chapter 4      Designing Unified CVP for High Availability
VoiceXML Gateway
Centralized VoiceXML Gateways
In this configuration, the VoiceXML gateways reside in the same data center as the Unified CVP Call 
Server.
H.323 VoiceXML Gateways
On the gatekeeper, configure a zone prefix list that contains the H.323 IDs of all VoiceXML gateways at 
the data center. For example, assume that there are three VoiceXML gateways in the data center with 
H.323 IDs of VoiceXMLgw1, VoiceXMLgw2, and VoiceXMLgw3, and that the ICM label for the 
Network VRU is 5551000. In this example, the gatekeeper distributes calls in essentially a round-robin 
scheme among all three VoiceXML gateways, provided they are all in service:
zone prefix gkzone-name 5551000* gw-priority 10 VoiceXMLgw1 VoiceXMLgw2 VoiceXMLgw3
SIP VoiceXML Gateways
If you are using Cisco Unified Presence Server: On the SIP proxy server, configure a static route for the 
Network VRU label for each gateway. If the VRU label is 5551000, the static route pattern would be 
5551000* in order to allow for the correlation-id to be appended and routed to the VoiceXML gateway. 
If you are using SIP static routes on the Unified CVP Call Server: Under the SIP Service configuration 
for the Call Server, configure a static route for each Network VRU label and gateway. If the VRU label 
is 5551000, the static route pattern would be 5551000>. The > is a wildcard representing one or more 
digits, and it is needed so that the correlation-id appended to the DNIS number can be passed to the 
VoiceXML gateway correctly.
Note
Other wildcard characters can be used. Refer to the topic Valid Formats for Dialed Numbers in the 
Operations Console online help for complete wildcard format and precedence information.
In the case of both SIP proxy or Unified CVP static routes, the next-hop address of the route can be either 
the IP address of the gateway or a DNS SRV record. If you are using an IP address, you must create 
multiple static routes, one for each VoiceXML gateway. In the case of DNS SRV, only one route per 
Network VRU label is needed, and the SRV record will provide for load-balancing and redundancy.
Distributed VoiceXML Gateways (Co-Resident Ingress Gateway and VoiceXML)
In this configuration, the gateway that processes the incoming call from the PSTN is separated from the 
Unified CVP servers by a low-bandwidth connection such as a WAN, and the VoiceXML gateway that 
is used is the same as the ingress gateway. The purpose of this configuration is to keep the media stream 
at the edge to avoid consuming bandwidth on the WAN.
H.323 VoiceXML Gateways
Use the SetTransferLabel in VBAdmin (not gatekeeper zone prefixes) to control the selection of the 
VoiceXML gateway. The SetTransferLabel command is specified per Network VRU label. When the 
Unified CVP Call Server receives a label from ICM that matches what is configured in the 
SetTransferLabel, the Call Server performs a gatekeeper lookup but ignores the destination gateway 
returned by the gatekeeper and sends the call back to the gateway that originated the call. The H.323 
Service determines the originating gateway by looking at the source IP address of the H.323 signaling.