Cisco Cisco Unified Customer Voice Portal 11.0(1)
Not Used
Installed (but
Inactive)
Inactive)
Optional
Required
Component
X
Content Services Switch
X
Unified ICME
The H.323-based call flow is much like the SIP-based call flow. However, the SIP Service and
the (optional) SIP Proxy Server are not used. Rather, the H.323 Service and (optionally) the
Gatekeeper are used. The H.323 Service communicates with the IVR Service rather than directly
with Unified ICME. If the Gatekeeper is used, the Ingress Gateway consults the Gatekeeper to
find the destination for messages, but does not pass messages through it. This is in contrast to
the SIP Proxy Server, where messages actually pass through the Proxy Server to the appropriate
destination.
the (optional) SIP Proxy Server are not used. Rather, the H.323 Service and (optionally) the
Gatekeeper are used. The H.323 Service communicates with the IVR Service rather than directly
with Unified ICME. If the Gatekeeper is used, the Ingress Gateway consults the Gatekeeper to
find the destination for messages, but does not pass messages through it. This is in contrast to
the SIP Proxy Server, where messages actually pass through the Proxy Server to the appropriate
destination.
VRU-Only Scenario
This scenario (called "Advanced Speech" in earlier versions of CVP) has Unified CVP providing
Unified ICME with VRU services for calls which are switched in some other manner, such as
by a carrier switched network via a Unified ICME Network Interface Controller (NIC) interface.
VRU services could be for initial prompt and collect, for integrated self-service applications,
for queuing, or for any combination thereof. This scenario does not use SIP or H.323, and
requires no Ingress Gateway. It does use VXML Gateways, but VXML Server is optional, as
are ASR and TTS Servers, and Media Servers.
Unified ICME with VRU services for calls which are switched in some other manner, such as
by a carrier switched network via a Unified ICME Network Interface Controller (NIC) interface.
VRU services could be for initial prompt and collect, for integrated self-service applications,
for queuing, or for any combination thereof. This scenario does not use SIP or H.323, and
requires no Ingress Gateway. It does use VXML Gateways, but VXML Server is optional, as
are ASR and TTS Servers, and Media Servers.
Depending on which kind of routing client is in charge of call switching, Unified ICME may
transfer the call to the VRU-Only Call Server either by a Translation Route to VRU node, or
by a Send To VRU node. In the first case, the ICM Service portion of the Call Server will
determine that the arriving call is a VRU leg call by matching the arriving DNIS with its
configured list of arriving DNISs. In the second case, it will determine that it is a VRU leg call
by the fact that the DNIS length is greater than its configured maximum DNIS length. Digits
beyond the maximum DNIS length are taken to be the Correlation ID.
transfer the call to the VRU-Only Call Server either by a Translation Route to VRU node, or
by a Send To VRU node. In the first case, the ICM Service portion of the Call Server will
determine that the arriving call is a VRU leg call by matching the arriving DNIS with its
configured list of arriving DNISs. In the second case, it will determine that it is a VRU leg call
by the fact that the DNIS length is greater than its configured maximum DNIS length. Digits
beyond the maximum DNIS length are taken to be the Correlation ID.
Table 5: Components Used for VRU-Only Scenario
Not Used
Installed (but
Inactive)
Inactive)
Optional
Required
Component
X
SIP Service (part of Call Server)
X
IVR Service (part of Call Server)
X
ICM Service (part of Call Server)
X
H.323 Service (part of Call
Server)
Server)
X
VXML Server
X
Call Studio
X
Ingress Gateway
X
VXML Gateway
X
SIP Proxy Server
Planning Guide for Cisco Unified Customer Voice Portal Cisco Unified Customer Voice Portal 4.1(1)
32
Chapter 3: - Choosing a Deployment Model
Call Flow Models