beautypg.com

Cisco H.323 VC-289 User Manual

Page 60

background image

Configuring H.323 Gatekeepers and Proxies

H.323 Gatekeeper Configuration Examples

VC-348

Cisco IOS Voice, Video, and Fax Configuration Guide

Similarly, in ny (New York in the 212 area code), gateways are configured to register with gk-ny as
follows:

gw-ny2 configured to register with technology prefix 2#

gw-ny3 configured to register with technology prefix 3#

gw-ny4 configured to register with technology prefix 4#

For the gatekeeper for San Jose, the configuration commands are as follows:

gatekeeper

zone local gk-sj cisco.com

zone remote gk-ny cisco.com 172.21.127.27

use-proxy gk-sj default direct

zone prefix gk-sj 408.......

zone prefix gk-ny 212.......

gw-type-prefix 3# hopoff gk-sj

gw-type-prefix 4# default-technology

For the gatekeeper for New York, the configuration commands are as follows:

gatekeeper

zone local gk-ny cisco.com

zone remote gk-sj cisco.com 172.21.1.48

use-proxy gk-ny default direct

zone prefix gk-sj 408.......

zone prefix gk-ny 212.......

gw-type-prefix 3# hopoff gk-ny

gw-type-prefix 4# default-technology

When a call is presented to gatekeeper gk-sj with the following target address in San Jose:

2#2125551212

Gatekeeper gk-sj recognizes that 2# is a technology prefix. It was not configured as such, but because
gw-sj2 registered with it, the gatekeeper now treats 2# as a technology prefix. It strips the prefix, which
leaves the telephone number 2125551212. This is matched against the zone prefixes that have been
configured. It is a match for 212......., so gk-sj knows that gk-ny handles this call. Gatekeeper gk-sj
forwards the entire address 2#2125551212 over to Gatekeeper gk-ny, which also looks at the technology
prefix 2# and routes it to gw-ny2.

When a call is presented to gatekeeper gk-sj with the following target address in San Jose:

2125551212

Gatekeeper gk-sj checks it against known technology prefixes but finds no match. It then checks it
against zone prefixes and matches on 212....... for gk-ny, and therefore routes this call to gk-ny.
Gatekeeper gk-ny does not have any local registrations for this address, and there is no technology prefix
on the address, but the default prefix is 4#, and gw-ny4 is registered with 4#, so the call gets routed to
gw-ny4.

Another call is presented to gatekeeper gk-sj with the following target address in San Jose:

3#2125551212

The call has technology prefix 3#, which is defined as a local hopoff prefix, so gk-sj routes this call to
gw-sj3, despite the fact that it has a New York zone prefix.

In this last example, a call is presented to gatekeeper gk-sj with the following target address in San Jose:

6505551212