CVP solution has several types of call control traffic. Call control functions
are to set up, maintain, tear down, or redirect calls.
works in Call Control mode or Signaling mode with three types of VoIP
endpoints: Cisco IOS Voice Gateways, Cisco Unified Communications Manager, and
Peripheral Gateway. Call Control traffic flows between the following endpoints:
and the Call Server
Gateway can be a Peripheral Gateway, Unified Communication Manager, a Cisco IOS
Voice Gateway, or another SIP device. The connection can be over a WAN or a
Call Server and
Gateway can be Unified Communication Manager or a Cisco IOS Voice Gateway. The
Egress Gateway is either a VoiceXML Gateway that is used to provide
prompt-and-collect treatment to the caller, or it is the target of a transfer
to an agent (Unified CCE or TDM) or a legacy TDM IVR. The connection can be
over a WAN or LAN.
designs do not support SIP for interoperability between the Peripheral Gateway
and Unified CVP. If your design requires this functionality, contact the Cisco
Assessment to Quality (A2Q) team.
Server and the Unified ICM VRU Peripheral Gateway communicates using the
GED-125 protocol. The GED-125 protocol includes the following features:
messages, that control the caller experience when a call arrives.
to transfer or disconnect the caller.
that control the IVR treatment the caller experiences.
Peripheral Gateway connects to Unified CVP over a LAN connection. However, in
deployments that use clustering over the WAN, Unified CVP can connect to the
redundant VRU Peripheral Gateway across the WAN.
time, no tool exists that specifically addresses communications between the
VRU Peripheral Gateway and Unified CVP. However, the bandwidth that is consumed
between the Unified ICM Central Controller and VRU Peripheral Gateway is
similar to the bandwidth that is consumed between the VRU Peripheral Gateway
and Unified CVP.
Peripheral Gateway to ICM Central Controller Bandwidth Calculator tool,
which is accessible through your credentials, is available through the Cisco
Steps to Success Portal at
also access the Bandwidth Calculator directly (with proper login
VRU Peripheral Gateway are split across the WAN, the total bandwidth that is
required is double of what the calculator tool reports: one for Unified ICM
Central Controller to VRU Peripheral Gateway and other for VRU Peripheral
Gateway to Unified CVP.
VoiceXML Gateway communicates with ASR/TTS Servers using Media Resource Control
Protocol (MRCP) v1.0 and v2
only with IOS Voice
Gateway. This protocol
connections to the ASR/TTS Server, such as Nuance. The connection can be over
LAN or WAN.
not test or qualify speech applications in WAN environment. For guidelines on
design, support over WAN and associated caveats, see the vendor-specific
documentation. TAC will provide limited support (as in the case of any
third-party interoperability certified products) on issues related to speech
Controller to Unified CVP VRU Peripheral Gateway
exists that specifically addresses communications between the Unified ICM
Central Controller and the Unified CVP VRU Peripheral Gateway. However, testing
shows that the tool for calculating bandwidth that is needed between the
Unified ICM Central Controller and the IP IVR Peripheral Gateway also produces
accurate measurements for Unified CVP, if you perform the following
substitution in one field.
number of RUN VRU SCRIPT nodes field, substitute the number of
Unified ICM script nodes that interact with Unified CVP. Nodes that can
interact with Unified CVP are Run External Script, Label, Divert Label, Queue
to Skill Group, Queue to Agent, Agent, Release, Send to VRU, and Translation
Route to VRU.
calculator tool is available (with proper login authentication) at:
connection can be over a WAN or a LAN.