Cisco Cisco Unified Customer Voice Portal 10.0(1)
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
8-7
Cisco Internet Service Node (ISN) Configuration and Administration Guide
OL-1251-03
Chapter 8 VoIP Configuration
Inbound Call Routing
endpoint alt-ep h323id isn_1vb1 10.10.10.13
endpoint alt-ep h323id isn_1vb2 10.10.10.11
endpoint alt-ep h323id isn_1vb2 10.10.10.13
endpoint alt-ep h323id isn_1vb2 10.10.10.11
endpoint alt-ep h323id isn_1vb2 10.10.10.13
The two Voice Browsers in the zone prefix command have equal priorities (pri 10), so under normal
circumstances the GK will route all calls randomly between vb1 and vb2. For the purpose of our
example, however, GK_1 knows that vb1 (at ISN_1) is completely Out-of-Service.
circumstances the GK will route all calls randomly between vb1 and vb2. For the purpose of our
example, however, GK_1 knows that vb1 (at ISN_1) is completely Out-of-Service.
Each of the Gateways queries its own Gatekeeper for Inbound calls, so if Gateway Huey receives a call
for 800-555-0010, it will query GK_1 for routing information, using the number 2#8005550010. Since
vb1 is Out-of-Service, GK_1 will return the IP Address of vb2 to Huey, as the target endpoint. In the
same response message (an H.323 ACF message) GK_1 will also pass the IP Addresses of vb2's
Alternate Endpoints (which in this example are vb1 and vb3 at ISN_1). Huey will first attempt to route
the call to vb2. If for some reason vb2 fails to respond to the call setup, Huey will try the alternate
endpoints in turn, until it receives a response. Huey will pass the number 2#8005550010 to the Voice
Browsers during call setup, which will in turn strip off the tech prefix 2#.
for 800-555-0010, it will query GK_1 for routing information, using the number 2#8005550010. Since
vb1 is Out-of-Service, GK_1 will return the IP Address of vb2 to Huey, as the target endpoint. In the
same response message (an H.323 ACF message) GK_1 will also pass the IP Addresses of vb2's
Alternate Endpoints (which in this example are vb1 and vb3 at ISN_1). Huey will first attempt to route
the call to vb2. If for some reason vb2 fails to respond to the call setup, Huey will try the alternate
endpoints in turn, until it receives a response. Huey will pass the number 2#8005550010 to the Voice
Browsers during call setup, which will in turn strip off the tech prefix 2#.
Caution
When defining a zone prefix, it strongly suggested that you use the “*” wildcard, rather than the “...”
wildcard pattern to avoid zone prefix conflicts within the Gatekeeper.
wildcard pattern to avoid zone prefix conflicts within the Gatekeeper.
ISN Voice Browser Configuration
The Gatekeeper processes Voice Browser registration as follows:
•
RRQ registration. ISN Voice Browsers register with the ISN Zone Gatekeeper through the H.323
Registration Request (RRQ) message. As part of RRQ registration, each Voice Browser sends its
name (for example, “isn_1vb1@cisco.com”) and IP address.
Registration Request (RRQ) message. As part of RRQ registration, each Voice Browser sends its
name (for example, “isn_1vb1@cisco.com”) and IP address.
•
IP Addresses for Alternate Endpoints. The Gatekeeper allows each registering endpoint to send a
list of IP Addresses for its alternate endpoints. This registration list is merged with any alternate
endpoint information statically configured on the Gatekeeper.
list of IP Addresses for its alternate endpoints. This registration list is merged with any alternate
endpoint information statically configured on the Gatekeeper.
Note
This feature is not supported by ISN Version 2.1.
•
Supported Numbers. The Gatekeeper allows each endpoint to register with a list of E.164 numbers
it supports, but it is recommended that the Voice Browsers don't do this. The reason for this is that
multiple Voice Browsers can support the dialed numbers, but the Gatekeeper does not permit
multiple endpoints to register with the same number.
it supports, but it is recommended that the Voice Browsers don't do this. The reason for this is that
multiple Voice Browsers can support the dialed numbers, but the Gatekeeper does not permit
multiple endpoints to register with the same number.
•
Technology Prefix. Each ISN 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.
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