Cisco Cisco Unified Customer Voice Portal 11.0(1)

You can accomplish call routing using the tech-prefix method, the zone prefix method, or a
combination of both. The sections that follow describe the tech-prefix and zone-prefix methods.

Note: There are variations to the routing methods described below, for example, the branch
office model.

Call Routing (tech-prefix method)

One method for performing call routing with Unified CVP is the tech-prefix method. With this
method, a specific class of H.323 devices registers with a unique tech-prefix. For example,
Unified CVP endpoints could register to the gatekeeper with a tech-prefix of 2#, VoiceXML
gateways could register with 3#, and Cisco Unified Communications Manager endpoints could
register with 1#. Additionally, with certain geographical distributions of devices, it might be
desirable to further subdivide the classification. For example, assuming there are two data
centers, you might want to register the Unified CVP devices in Data Center 1 with 98# and
Unified CVP devices in Data Center 2 with 99#. This is strictly a matter of customer preference
and topological deployment needs.

With the tech-prefix method, a RAS Admission Request to the gatekeeper contains a DNIS
prefixed with the tech-prefix (for example, 2#8005551212). When the gatekeeper receives such
a request, it will first look to see which endpoints are registered with that tech-prefix and then
perform an approximate round-robin selection among those endpoints. It will return the selected
IP address and port to the requesting endpoint in the RAS Admission Confirm message. The
requesting endpoint will then route the call to the selected server. Each type of endpoint has a
mechanism for stripping the tech-prefix, if desired, the details of which are described below.

Note: The gatekeeper command show gatekeeper gw-type-prefix can be very useful in
determining how the gatekeeper will route calls based on tech-prefix.

In this first example, we will assume that:

•

Unified CVP registers with 2#.

•

Ingress gateway registers with 3#.

•

VoiceXML gateway registers with 4# (assume ingress and VoiceXML gateways are separate).

•

Egress gateway registers with 5#. In this case, the Egress gateway is front-ending a legacy
ACD or IVR.

•

Cisco Unified Communications Manager registers with 1# (note that Cisco Unified
Communications Manager is registering with the default tech-prefix).

•

Default technology prefix in the gatekeeper is 1#.

Gatekeeper Configuration for Call Routing (tech-prefix method)

The gatekeeper configuration only requires that you specify a default technology prefix; it is
not necessary to explictly define zone prefixes.

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