Cisco Cisco Customer Voice Portal 8.0(1)
8-8
Cisco Customer Voice Portal (CVP) Release 3.1(0) Configuration and Administration Guide
Chapter 8 VoIP Configuration
Inbound Call Routing
•
Technology Prefix. Each Customer Voice Portal Voice Browser is automatically registered with its
Gatekeeper with the Tech Prefix 2#. The Voice Browser’s software is shipped with the tech-prefix
2# pre configured. If necessary, this number may be changed using the VB Admin’s SetTechPrefix
command.
Gatekeeper with the Tech Prefix 2#. The Voice Browser’s software is shipped with the tech-prefix
2# pre configured. If necessary, this number may be changed using the VB Admin’s SetTechPrefix
command.
Gateway Configuration
Since a Gatekeeper is present in the configuration, the Gateway’s role can be minimized. It is
recommended that the Gateways be configured to always query the Gatekeeper for routing information.
This can be done using a wildcard dial-peer, as shown in
recommended that the Gateways be configured to always query the Gatekeeper for routing information.
This can be done using a wildcard dial-peer, as shown in
. To provide maximum protection
in the event of gatekeeper problems (even when using HSRP), it is strongly advisable to statistically
configure at least one of the Customer Voice Portal Voice Browsers in the gateway configuration. Note
that these dial-peers have a “lower” preference than the ras dial-peer.
configure at least one of the Customer Voice Portal Voice Browsers in the gateway configuration. Note
that these dial-peers have a “lower” preference than the ras dial-peer.
Example 8-4
Inbound Call Routing Gateway Configuration
Note
In all occurrences of “voice-class codec 1” the actual values are adjustable to your needs.
dial-peer voice 1 voip
voice-class codec 1
destination-pattern 888800... *\ The wildcard pattern\*
session target ras
dtmf-relay rtp-nte h245-signal h245-alphanumeric
preference 0
no vad (comprehensive IVR mode only)
tech-prefix 2#
dial-peer voice 2 voip
voice-class codec 1
destination-pattern 888800....
session target ipv4:10.10.10.11
dtmf-relay rtp-nte h245-signal h245-alphanumeric
preference 1
no vad (Comprehensive Mode only)
tech-prefix 2#
dial-peer voice 3 voip
voice-class codec 1
destination-pattern 888800....
session target ipv4:10.10.10.12
dtmf-relay rtp-nte h245-signal h245-alphanumeric
preference 1
no vad (Comprehensive Mode only)
tech-prefix 2#
Gateways not in the Customer Voice Portal zone must be configured to query their own zone Gatekeeper
for routing information. The originating Gatekeeper will discover the Customer Voice Portal Zone
Gatekeeper through the H.323 Location Request (LRQ) message. The Customer Voice Portal Zone
Gatekeeper will determine proper routing, which will be returned to the originating Gateway (via the
originating Gatekeeper).
for routing information. The originating Gatekeeper will discover the Customer Voice Portal Zone
Gatekeeper through the H.323 Location Request (LRQ) message. The Customer Voice Portal Zone
Gatekeeper will determine proper routing, which will be returned to the originating Gateway (via the
originating Gatekeeper).