Cisco Cisco Customer Voice Portal 8.0(1)
The Ingress Gateway may be deployed separately from the VoiceXML Gateway, but in most
implementations they are one and the same: one gateway performs both functions. Gateways
are often deployed in farms, for centralized deployment models. In Branch deployment models,
one combined gateway is usually located at each branch office.
implementations they are one and the same: one gateway performs both functions. Gateways
are often deployed in farms, for centralized deployment models. In Branch deployment models,
one combined gateway is usually located at each branch office.
The VoiceXML Gateway hosts the IOS voice browser, the component which interprets
VoiceXML pages from either the Unified CVP IVR service or the VXML Server, plays .wav
files and Text-to-Speech (TTS), inputs voice and DTMF, and sends results back to the VoiceXML
requestor. It also mediates between Media Servers, VXML Servers, ASR and TTS Servers, and
the IVR service.
VoiceXML pages from either the Unified CVP IVR service or the VXML Server, plays .wav
files and Text-to-Speech (TTS), inputs voice and DTMF, and sends results back to the VoiceXML
requestor. It also mediates between Media Servers, VXML Servers, ASR and TTS Servers, and
the IVR service.
Unless it is combined with the Ingress Gateway, the VoiceXML Gateway does not require any
TDM hardware. All its interfaces are VoIP on one side and HTTP (carrying VXML or
TDM hardware. All its interfaces are VoIP on one side and HTTP (carrying VXML or
.wav
files) and MRCP (carrying ASR and TTS traffic) on the other side. As with Ingress Gateways,
VXML Gateways are often deployed in farms for centralized deployment models, or one per
office in Branch deployments.
VXML Gateways are often deployed in farms for centralized deployment models, or one per
office in Branch deployments.
Voice Codec class configuration should be symmetrical on the Ingress gateway and the Egress
gateway. Use the voice class codec command to define the list of codecs available and the order
in which they should be tried.
gateway. Use the voice class codec command to define the list of codecs available and the order
in which they should be tried.
For example, if G.729 is the preferred codec, the codec class should be configured to prefer
G.729 and then G.711 on both gateways as shown in the example below. Codec class 2 is used
for Codec negotiation.
G.729 and then G.711 on both gateways as shown in the example below. Codec class 2 is used
for Codec negotiation.
voice class codec 1
codec preference 1 g729r8
codec preference 2 g711ulaw
voice class codec 2
codec preference 1 g729r8
codec preference 2 g711ulaw
Refer to the Operations Console online help topics under Managing Devices > Configuring a
Gateway to perform the following tasks:
Gateway to perform the following tasks:
•
Adding a Gateway
•
Editing a Gateway
•
Deleting a Gateway
•
Gateway Configuration Settings
•
Executing Gateway Commands
•
Getting Gateway Statistics
•
Transferring a File to a Gateway
•
Finding a Gateway
Configuration and Administration Guide for Cisco Unified Customer Voice Portal Release 8.0(1)
473
Chapter 13: Configuring the H.323 Devices and VoIP
Configuring a Gateway