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-6
Cisco Internet Service Node (ISN) Configuration and Administration Guide
OL-1251-03
Chapter 8 VoIP Configuration
Inbound Call Routing
Inbound Call Routing—With Gatekeeper
When a Gatekeeper is present, Inbound call routing to the ISN is controlled by information kept at one
or more H.323 Gatekeepers. H.323 enforces the concept of zones, where a single logical Gatekeeper
(which may be one or more actual Gatekeepers) is responsible for routing control within its zone.
or more H.323 Gatekeepers. H.323 enforces the concept of zones, where a single logical Gatekeeper
(which may be one or more actual Gatekeepers) is responsible for routing control within its zone.
For ease of illustration, we will initially assume that all the ISN nodes reside within the same H.323
zone, the “ISN Zone.”
zone, the “ISN Zone.”
Gatekeeper Configuration Example
shows the ISN nodes and Gateways separated into three different H.323 zones:
•
ISN_1 and GW Huey are assigned to Zone 1, which is controlled by GK_1.
•
ISN_2 and GW Dewey are assigned to Zone 2, which is controlled by GK_2.
•
ISN_3 and GW Louie are assigned to Zone 3, which is controlled by GK_3.
section, it is assumed that each of the Voice Browsers have registered with its Gatekeeper,
and that the Gateways are configured—for details, see
—to
perform RAS lookups in their Gatekeeper for incoming calls.
Figure 8-2
Inbound Call Routing, With Gatekeepers
Each Gatekeeper is configured with the complete list of supported numbers, which only point to Voice
Browsers at the ISN node in its zone. Each Gatekeeper is also configured with alternate endpoint
information for each Voice Browser, with each Voice Browser indicating two alternate endpoints from
its own ISN node, as shown in
Browsers at the ISN node in its zone. Each Gatekeeper is also configured with alternate endpoint
information for each Voice Browser, with each Voice Browser indicating two alternate endpoints from
its own ISN node, as shown in
Example 8-3
Inbound Call Routing GK_1 Configuration
zone local gk_1 cisco.com 10.10.10.00
*\ Must include GK IP address \*
gw-type-prefix 1#* default-technology
*\ Default for calls rec’d with no tech-prefix\*
zone prefix gk_1 8005550010 gw-pri 10 isn_1vb1@cisco.com isn_1vb2@cisco.com
endpoint alt-ep h323id isn_1vb1 10.10.10.12
endpoint alt-ep h323id isn_1vb1 10.10.10.12