Cisco Cisco Unified Customer Voice Portal 10.0(1)

ForUnified ICME Release 7.1 and later, do the following:

1. Configure a single Type 10 Network VRU and associate it with all Unified CVP peripherals

in the PG Explorer configuration tool, and also define it as the default system Network
VRU in the System Information tool.

2. In order to support the initial call transfer to Unified CVP from the pre-route routing client,

configure Translation Route labels to target the Unified CVP peripherals.

3. In order to support the transfer to VRU leg, configure the Type 10 Network VRU that you

defined above in Step 1 with Network Routing Number labels for each Unified CVP
peripheral routing client.

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

the routing script transfers the call into Unified CVP, it must use a TranslationRouteToVRU
node. No subsequent node is necessary in order to perform the transfer to Unified CVP's
VRU leg; this will take place automatically.

Note: Non-prerouted calls can also share the same Network VRU and the same Unified
CVP Call Servers.

ForUnified 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 all 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 transfers the call into Unified CVP, it must use two nodes in

succession: first, a TranslationRouteToVRU, and then an explicit SendToVRU node. 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 leg. (The VRU leg will usually end up running through the same
Unified CVP Call Server as the Switch leg.)

Note: Non-prerouted calls can also share the same Type 2 Call Servers and Type 2 and
Type 7 Network VRUs; however, note that the scripts which handle non-prerouted calls
must also use an explicit SendToVRU node before they can execute any micro-applications.

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