Cisco Cisco Customer Voice Portal 8.0(1) Design Guide
6-5
Cisco Unified Customer Voice Portal (CVP) 8.x Solution Reference Network Design (SRND)
OL-15989-06
Chapter 6 Calls Originated by Cisco Unified Communications Manager
Protocol Call Flows
Now consider what happens if the target device issues another route request to Unified ICM. This part
of the call flow would not be possible without the initial TranslationRouteToVRU mentioned step
of the call flow would not be possible without the initial TranslationRouteToVRU mentioned step
12.
Unified ICM invokes a new routing script.
13.
The routing script encounters a Select or Label node, and it selects a target label.
14.
Unified ICM returns the target label to the Unified CVP Call Server (not to the device that issued
the route request).
the route request).
15.
The Unified CVP Call Server consults the gatekeeper, DNS SRV, or SIP Proxy to locate the
destination device.
destination device.
16.
The Unified CVP Call Server communicates via H.323 or SIP with the target device and instructs
Unified CM to establish a media stream to the device.
Unified CM to establish a media stream to the device.
Model #3a: Comprehensive Using ICM Micro-Apps
Model #3a involves both call switching and VRU activity. It differs from Model #2, therefore, in that
calls must be transferred to the Unified CVP VoiceXML gateway after they are transferred to the Unified
CVP Switch leg. Queuing is possible in this model, as is basic prompt-and-collect activity.
calls must be transferred to the Unified CVP VoiceXML gateway after they are transferred to the Unified
CVP Switch leg. Queuing is possible in this model, as is basic prompt-and-collect activity.
This model requires that the following items be configured:
•
Unified CM CTI route point that invokes a Unified ICM script
•
Unified CVP configured as a Type 10 NetworkVRU
•
The CTI route point configured in Unified ICM as a DN with a Type 10 NetworkVRU
•
The NetworkVRU must have labels for the Unified CVP Switch leg routing client
•
The NetworkVRU labels must be configured in a gatekeeper or SIP Proxy to point to VoiceXML
gateways
gateways
•
Unified CM configured with an H.323 trunk or SIP trunk
The call flow for this model is as follows:
1.
A caller dials a route point.
2.
Unified ICM invokes a routing script.
3.
The routing script encounters a SendToVRU node to transfer the call to Unified CVP. (Unified CVP
is configured as a Type 10 NetworkVRU.)
is configured as a Type 10 NetworkVRU.)
4.
Unified ICM returns the VRU label with Correlation ID to Unified CM.
5.
Unified CM consults the gatekeeper, DNS SRV, or SIP Proxy to locate the Unified CVP Call Server.
6.
The call is connected to the Unified CVP Call Server.
7.
Unified CM briefly establishes a G.711 media connection between the caller and the Unified CVP
H.323 Service (for H.323 only).
H.323 Service (for H.323 only).
8.
Unified ICM sends a VRU transfer label with Correlation ID to the Unified CVP Call Server.
9.
The Unified CVP Call Server consults the gatekeeper, DNS SRV, or SIP Proxy to locate the
VoiceXML gateway.
VoiceXML gateway.
10.
The Unified CVP Call Server communicates via H.323 or SIP with the VoiceXML gateway and
instructs Unified CM to establish a media stream to it.
instructs Unified CM to establish a media stream to it.
11.
The routing script executes one or more Unified CVP Microapplications via RunExternalScript
nodes, plays media files, requests DTMF input, and so forth.
nodes, plays media files, requests DTMF input, and so forth.