Cisco Cisco Customer Voice Portal 8.0(1) Design Guide

In Unified ICM, a Network VRU is a configuration database entity. It is accessed using the Network 
VRU Explorer. A Network VRU entry contains the following pieces of information:

Type — A number from 2 to 10, which corresponds to one of the types described previously.

Labels — A list of labels that Unified ICM can use to transfer a call to the particular Network VRU 
being configured. These labels are relevant only for Network VRUs of Type 3, 7, or 10 (that is, those 
VRU types that use the Correlation ID mechanism to transfer calls), and they are required but never 
used in the case of Type 5. Each label consists of two parts:

A digit string, which becomes a DNIS that can be understood by the gatekeeper (when H.323 is 
used), by a SIP Proxy Server or a static route table (when SIP is used), or by gateway dial peers.

A routing client, or switch leg peripheral. In other words, each peripheral device that can act as 
a Switch leg must have its own label, even though the digit strings will likely be the same in all 
cases.

Network VRU configuration entries themselves have no value until they are associated with active calls. 
There are three places in Unified ICM where this association is made:

Under the Advanced tab for a given peripheral in the PG Explorer tool

In the Customer Instance configuration in the Unified ICM Instance Explorer tool

In every VRU Script configuration in the VRU Script List tool

Depending on the protocol-level call flow, Unified ICM Enterprise looks at either the peripheral or the 
Customer Instance to determine how to transfer a call to a VRU. Generally speaking, Unified ICM 
Enterprise examines the Network VRU that is associated with the Switch leg peripheral when the call 
first arrives on a Switch leg, and the Network VRU that is associated with the VRU leg peripheral when 
the call is being transferred to the VRU using the Translation Route mechanism. It examines the Network 
VRU that is associated with the Customer Instance when the call is being transferred to the VRU using 
the Correlation ID mechanism.

Unified ICM Enterprise also examines the Network VRU that is associated with the VRU Script every 
time it encounters a RunExternalScript node in its routing script. If Unified ICM does not believe the 
call is currently connected to the designated Network VRU, it will not execute the VRU Script.

Unified ICM Enterprise Release 7.1 introduced Network VRU Type 10, which simplifies the 
configuration of Network VRUs for Unified CVP. For most call flow models, a single Type 10 Network 
VRU can take the place of the Type 2, 3, 7, or 8 Network VRUs that were associated with the Customer 
Instance and/or the switch and VRU leg peripherals. The only major call flow model that still requires 
Type 7 or 8 is VRU Only (Model #4a, described below).

Note that the previously recommended VRU types still work as before, even in Unified ICM 
Enterprise 7.1. New installations should use Type 10 if possible, and existing installations may 
optionally switch to Type 10.

The Standalone Self-Service model typically does not interface with Unified ICM VRU scripts, so a 
Network VRU setting is not relevant. The Standalone Self-Service model with Unified ICM Label 
Lookup does not use the VRU scripts in Unified ICM; it simply issues a Route Request to the VRU PG 
Routing Client, therefore a Network VRU is not needed.