Cisco Cisco Unified Customer Voice Portal 11.0(1)
The benefits of using a SIP Proxy Server include:
•
Priority and weight routing can be used with the routes for load balancing and failover
•
If a SIP Proxy Server is already used in your SIP network, Unified CVP can be an additional
SIP endpoint—it fits incrementally into the existing SIP network
SIP endpoint—it fits incrementally into the existing SIP network
•
If the Cisco Unified Presence Server is being used as the SIP Proxy Server, dial plan
management is available in the web administration of the static routes
management is available in the web administration of the static routes
•
If the Cisco Unified Presence Server is being used as the SIP Proxy Server, you are better
positioned to also take advantage of Presence and Cisco Unified Client, as a compliment to
Unified CVP
positioned to also take advantage of Presence and Cisco Unified Client, as a compliment to
Unified CVP
If a SIP Proxy Server is not used, then Ingress Gateways and Unified CallManagers need to
point directly to Unified CVP. In such a deployment:
point directly to Unified CVP. In such a deployment:
•
Load balancing is done via DNS SRV lookups from Gateway to DNS Server—SIP calls can
be balanced using this mechanism
be balanced using this mechanism
•
Load balancing of calls outbound from Unified CVP (outbound call leg) can be done in
similar fashion
similar fashion
•
Failover of SIP rejections can also be performed if SRV records are configured with ordered
priorities
priorities
Ingress Gateway
The Ingress Gateway is the point at which an incoming call enters the Unified CVP solution.
It terminates TDM phone lines on one side and implements VoIP on the other side. It also
provides for sophisticated call switching capabilities at the command of other Unified CVP
solution components. It works with either SIP or H.323 protocols, and also supports Media
Gateway Control Protocol (MGCP) for use with Unified CallManager.
It terminates TDM phone lines on one side and implements VoIP on the other side. It also
provides for sophisticated call switching capabilities at the command of other Unified CVP
solution components. It works with either SIP or H.323 protocols, and also supports Media
Gateway Control Protocol (MGCP) for use with Unified CallManager.
The Ingress Gateway can be deployed separately from the VXML 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.
VXML Gateway
The VXML Gateway hosts the IOS Voice Browser, the component which interprets VXML
pages from either the IVR Service or the VoiceXML Server, plays .wav files and TTS, inputs
voice and DTMF, and sends results back to the VXML requestor. It also mediates between
Media Servers, VoiceXML Servers, ASR and TTS Servers, and IVR Services.
pages from either the IVR Service or the VoiceXML Server, plays .wav files and TTS, inputs
voice and DTMF, and sends results back to the VXML requestor. It also mediates between
Media Servers, VoiceXML Servers, ASR and TTS Servers, and IVR Services.
Unless it is combined with the Ingress Gateway (see above), the VXML Gateway does not
require any 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
require any 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
Planning Guide for Cisco Unified Customer Voice Portal 4.0(1)
21
Chapter 1: Product Overview
Unified CVP Solution Components