Cisco Cisco Unified Customer Voice Portal 11.0(1)

X

VoiceXML Server

X

VoiceXML Studio

X

Ingress Gateway

X

VXML Gateway

X

SIP Proxy Server

X

Gatekeeper

X

Operations Console

X

Reporting Server

X

ASR/TTS

X

Media Server

X

DNS Server

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 the Gatekeeper are
used. The H.323 Service communicates with the IVR Service rather than directly with Unified
ICME. 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.

Standalone VoiceXML Scenario

This scenario involves calls arriving through a gateway, and interacting directly with a VoiceXML
Server to execute VoiceXML applications. The gateway performs both ingress and VXML
functions. This is designed for customers who require a sophisticated VoiceXML-based VRU,
for applications which in many cases will not need to interact with Unified ICME at all.

However, some Standalone customers do require the ability to make back-end requests to Unified
ICME, without relinquishing control of the call. To fill that need, Unified CVP has a Request
ICM Label capability. The application generally acts on its own, but includes a special step to
send a query to Unified ICME and receive a response. The query can contain full call context
information, as can the response.

Planning Guide for Cisco Unified Customer Voice Portal 4.0(1)