Cisco Cisco Unified Customer Voice Portal 10.5(1)
4-3
Cisco Customer Voice Portal (CVP) Release 3.0(0) Product Description
Chapter 4 VoIP Routing
Inbound Routing
Inbound Call Routing with No Gatekeeper Present
When no Gatekeeper is present, inbound call routing to the CVP is controlled by dial plan information
configured at each H.323 originating endpoint, a Cisco Voice Gateway.
configured at each H.323 originating endpoint, a Cisco Voice Gateway.
Cisco Gateways provide several capabilities:
•
Dial-Peers. A Gateway dial-peer associates a dialed number (or range of numbers, defined by wild
cards) with a Session Target. The Session Target can be either an IP address (such as 10.10.10.1) or
a Domain Name (such as CVP_1@cisco.com). If the Session Target is a Domain Name, the Gateway
resolves it through the Domain Name Server (DNS).
cards) with a Session Target. The Session Target can be either an IP address (such as 10.10.10.1) or
a Domain Name (such as CVP_1@cisco.com). If the Session Target is a Domain Name, the Gateway
resolves it through the Domain Name Server (DNS).
•
Domain Name Server. A Domain Name Server (DNS), such as Cisco Network Registrar, can map
a Domain Name to one or more IP addresses. If a Gateway DNS query on a dialed number returns
multiple IP addresses, the Gateway routes the call to each successive IP address until it obtains a
successful connection.
a Domain Name to one or more IP addresses. If a Gateway DNS query on a dialed number returns
multiple IP addresses, the Gateway routes the call to each successive IP address until it obtains a
successful connection.
•
Multiple Dial-Peers. Multiple dial-peers can be specified for the same dialed number, or range of
numbers. In this case, each dial-peer associates the dialed number with a different IP address or
Domain Name. The Gateway resolves multiple dial-peers according to well-defined rules, including
the number of digits matched, target preference, and round robin.
numbers. In this case, each dial-peer associates the dialed number with a different IP address or
Domain Name. The Gateway resolves multiple dial-peers according to well-defined rules, including
the number of digits matched, target preference, and round robin.
•
Default Route. Gateways can be configured with a default target that will be used to route any
Inbound call not defined in dial-peers.
Inbound call not defined in dial-peers.
•
Nearest Voice Browser Option. If multiple CVP nodes exist in a solution, it might be desirable to
have Gateways route inbound calls requiring CVP treatment to Voice Browsers at the nearest CVP
node. This is done by configuring each of the Gateways with dial-peers that point to the preferred
Voice Browsers.
have Gateways route inbound calls requiring CVP treatment to Voice Browsers at the nearest CVP
node. This is done by configuring each of the Gateways with dial-peers that point to the preferred
Voice Browsers.
•
Codecs. CVP currently supports only two voice codecs for inbound calls: g711 u-law or g711 a-law.
(G.729 is supported during IP transfers, only.) CVP codec selection is specified through VB Admin
(the Voice Browser command line interface). However, Gateway dial-peers must also be configured
to indicate which of the codecs need to be supported. (Dial-peers can be set up to process one or
both of the codecs for CVP communications.)
(G.729 is supported during IP transfers, only.) CVP codec selection is specified through VB Admin
(the Voice Browser command line interface). However, Gateway dial-peers must also be configured
to indicate which of the codecs need to be supported. (Dial-peers can be set up to process one or
both of the codecs for CVP communications.)
Note
For detailed instructions on how to configure Gateways for use with the CVP, see the Cisco Customer
Voice Portal (CVP) Configuration and Administration Guide.
Voice Portal (CVP) Configuration and Administration Guide.