Cisco Cisco Customer Voice Portal Downloads

Gatekeeper Configuration for Call Routing (zone-prefix method)

Do the following:

1. Configure the default tech-prefix:

2. Define the zone prefix(es) for all DNIS values that should be routed to Unified CVP.

–

The H323-id is what must be specified in the zone-prefix command. Although by
default the H323-id is the IP address of the Unified CVP machine, it can be changed
using the setH323ID VBAdmin command so care must be taken to make sure this
matches. This is a very common mistake when configuring the gatekeeper.

–

If multiple Unified CVP devices are specified, the gatekeeper will perform an
approximate round-robin selection algorithm when selecting a Unified CVP endpoint
to which to route the call.

–

It is best to use the wildcard (*) syntax for all zone prefixes. Mixing the dot syntax
with * syntax can have unpredictable routing results

3. Define the zone prefix for the Network VRU label. This is how Unified CVP will locate

a VoiceXML gateway to process the IVR leg of the call.

4. Define the zone prefix(es) for agent phone device target ids. Typically, the H.323-ids of

all subscribers in the Cisco Unified Communications Manager cluster are listed here

5. Define alternate endpoints for all egress gateways (both VoiceXML gateways and ACD

egress gateways, if present). In the event Unified CVP sends a call setup to an egress
gateway which fails, Unified CVP will then try the all the alternate endpoints in turn, until
it receives a successful response.

Configuration and Administration Guide for Cisco Unified Customer Voice Portal Release 4.1(1)