Cisco Cisco Unified Customer Voice Portal 11.0(1)

Page of 561
Figure 21: Unified CVP with Type 3 or 7 VRU-Only, Unified ICMH
Note: The numbers in the figure indicate call flow progression.
Configuration overview for this call flow model:
Set the Network VRU Type to 3 or 7. There is no difference between these two types except
that Type 7 causes Unified ICME to explicitly inform Unified CVP when it is about to transfer
the call away from Unified CVP. (Most customers use Type 7.)
The Network VRU names (where applicable), correlation IDs, and the ECC variable
configurations must be identical on the NAM and CICM. All Labels must also be duplicated,
but their routing clients will be different.
Use the CICM Script Editor’s SendToVRU node to connect the call to the Network VRU.
The following table contains the configuration instructions for this call flow model.
Table 13: Configuration Checklist, Type 3 or 7, Unified CVP VRU-Only Call Flow Model Network VRU, Unified ICMH 
Settings Specific to This Call Flow Model
Where to Go/What to Do
Check
off
when
done
Do the following:
Configure the VoiceXML Gateway used for the VRU
leg:
[ ]
For Step 1, in the Operations Console select Device
Management > Gateway > File Transfer > Scripts
,
1. Transfer the following Unified CVP gateway
scripts using the Unified CVP Operations
Console:
then browse to the <cvp
root>\Cisco\CVP\OpsConsoleServer
\GWDownloads
 folder.
bootstrap.tcl
Refer to the Operations Console online help for
detailed instructions.
handoff.tcl
survivabilty.tcl
For Steps 2 and 3, see the "
"
section.
bootstrap.vxml
recovery.vxml
For Step 4, see the "
ringtone.tcl
Configuration and Administration Guide for Cisco Unified Customer Voice Portal Release 4.1(1)
131
Chapter 2: Configuration Overview
Unified CVP VRU Call Flow Models with NIC Routing