Cisco Cisco Unified Customer Voice Portal 10.0(1)

For Unified ICME Release 7.1 and later, do the following:

1. Configure a single Type 10 Network VRU and defined as the default system Network

VRU in the System Information tool.

2. Configure the Type 10 Network VRU with two sets of labels. Associate the first set with

the Unified CM routing client, which contains a label that Unified CM uses to transfer the
call to Unified CVP. Configure Unified CM with a series of route patterns, which include
that label followed by one to five arbitrary digits. For example, if the selected label is
1111, then the following route patterns are needed: 1111X, 1111XX, 1111XXX,
1111XXXX, and 1111XXXXX. The second set of Network VRU labels must contain the
usual Comprehensive Model "Network Routing Number," which must be associated with
each Unified CVP Call Server routing client.

3. Associate all micro-application VRU scripts with that same Type 10 Network VRU.

4. When the routing script transfers the call into Unified CVP, it should use a single

SendToVRU node. No subsequent node is necessary in order to perform the transfer to
Unified CVP's VRU leg; this will take place automatically. (The SendToVRU node can
be omitted since any micro-application script node will invoke the same functionality
automatically; however, you can include this node explicitly in the script for troubleshooting
purposes.)

Note: Non-prerouted calls can also share the same Network VRU and the same Unified
CVP Call Servers as those calls which are transferred from Unified CM; however, note
that the scripts which handle non-prerouted calls must also use an explicit SendToVRU
node before they can execute any micro-applications.

For Unified ICME Release 7.0, do the following:

1. Configure two Network VRUs: one Type 2 and one Type 7.

2. In the PG Explorer tool, assign the Unified CVP Call Servers to the Type 2 Network VRU.

3. Configure one set of Translation Route labels to target the Type 2 Call Servers; these will

be used to transfer the call from the original routing client to the Unified CVP Switch leg.

4. Assign a label to the Type 7 Network VRU for each Unified CVP Call Server routing

client, whose label string is set to the Network Routing Number.

5. Configure the Type 7 Network VRU as the system default Network VRU in the System

Information configuration tool.

6. Associate all micro-application VRU scripts with the Type 7 Network VRU.

7. When the routing script to transfers the call into Unified CVP, it should use two nodes in

succession: first, a TranslationRouteToVRU, and then an explicit SendToVRU node (which
contrary to the Unified ICME 7.1 case, is not optional). The first node transfers the call
from the initial routing client to one of the Type 2 Call Servers (Unified CVP Switch leg);
the second one transfers the call from the Type 2 Call Server to the Unified CVP VRU

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