Cisco Cisco Unified Customer Voice Portal 11.0(1)

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 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 2 Network VRU.

7. When the routing script transfers the call into Unified CVP, it should 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.

Common Unified ICMH Configuration for Unified CVP Switch Leg

The steps in the following table describe Unified ICMH configuration instructions common to
Comprehensive Unified ICMH and VRU-Only with NIC routing, with Correlation ID call
routing call flow models for Unified CVP switch legs.

Specify the following:

On the NAM, ICM Configuration Manager,
Network VRU Explorer tool:

•

Type: 10.

1. Define a Network VRU for Unified CVP.

•

Name: cvpVRU.

2. Assign labels.

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