Cisco Cisco Customer Voice Portal 8.0(1) Design Guide

ICM Customers are now supported, one cannot initiate a two-step transfer from the Unified CVP VRU 
switch leg to a completely separate Unified CVP (for example, a two-steps CVP-to-CVP transfer using 
SendToVRU). A translation route would have to be used in order for such a two-step transfers to work.

Type 10 Network VRU has the following behavior:

There is a Handoff of routing client responsibilities to the Unified CVP switch leg.

There is an automatic transfer to the Unified CVP VRU leg, resulting in a second transfer in the case 
of calls originated by the VRU, ACD, or Cisco Unified Communications Manager (Unified CM).

For calls originated by Unified CM, the Correlation ID transfer mechanism is used. The Correlation 
ID is automatically added to the end of the transfer label defined in the Type 10 Network VRU 
configuration.

The final transfer to the Unified CVP VRU leg is similar to a Type 7 transfer, in that a RELEASE 
message is sent to the VRU prior to any transfer.

In Unified CVP implementations without the ICM Customers feature (that is, in Unified CVP 
implementations with a single Network VRU), a single Type 10 Network VRU should be defined, and 
all Unified ICM VRU scripts should be associated with it. It requires one label for the Unified CVP 
Switch leg routing client, which will transfer the call to the Unified CVP VRU leg. If calls will be 
transferred to Unified CVP from Unified CM, it also needs another label for the Unified CM routing 
client, and this label should be different from the label used for the CVP Routing Client. This label will 
transfer the call to the Unified CVP Switch leg. The Unified ICM Router will send this label to 
Unified CM with a Correlation ID concatenated to it. Unified CM must be configured to handle these 
arbitrary extra digits.

The Unified CVP Switch leg peripheral should be configured to point to the same Type 10 Network 
VRU. Also, all incoming dialed numbers for calls that are to be transferred to Unified CVP should be 
associated with a Customer Instance that points to the same Type 10 Network VRU.

For calls that originate at a Call Routing Interface VRU or at a TDM ACD, a TranslationRouteToVRU 
node should be used to transfer the call to Unified CVP’s Switch leg peripheral. For all other calls, use 
either a SendToVRU node, a node that contains automatic SendToVRU behavior (such as the queuing 
nodes), or a RunExternalScript.

Cisco Unified ICM 7.1 introduces the Type10 Network VRU. This VRU must be used for all new 
implementations of Unified CVP using Unified ICM 7.1 or greater. The Type5 VRU must be used for 
existing customer deployments that have upgraded or for deployments that are not running Unified ICM 
7.1 or later.

Type 5 and Type 6 are similar in the sense that the VRU entity functions both as a switch (call control) 
and as the VRU (IVR). However, they differ on how to connect to the VRU.

In Type 6, the Switch and the VRU are the same device, therefore the call is already at the VRU. No 
Connect and Request Instructions message sequence is needed from the point of view of Unified ICM.

On the other hand, in Type 5, the Switch and the VRU are different devices even though they are in the 
same service node from the viewpoint of Unified ICM (that is, they both interact with Unified ICM 
through the same PG interface). Therefore, Unified ICM uses a Connect and Request Instructions 
sequence to complete the IVR call.