Configuring H.323 Gatekeepers and Proxies
H.323 Gatekeeper Configuration Examples
–Configuring a
–Co-Edge Proxy with Subnetting Example, page 354
–Configuring an
–Configuring a
–Configuring a Closed
•Defining Multiple Zones Example, page 360
•Defining One Zone for Multiple Gateways Example, page 360
•Configuring a Proxy for Inbound Calls Example, page 361
•Configuring a Proxy for Outbound Calls Example, page 361
•Removing a Proxy Example, page 362
•H.235 Security Example, page 362
•GKTMP and RAS Messages Example, page 363
•Prohibiting Proxy Use for Inbound Calls Example, page 363
•Disconnecting a Single Call Associated with an H.323 Gateway Example, page 363
•Disconnecting All Calls Associated with an H.323 Gateway Example, page 363
Configuring a Gatekeeper Example
The following is an annotated example of how to configure a gatekeeper:
hostname
!This router serves as the gatekeeper for the engineering community.
!at xyz.com.
ip
!Domain name of this company. interface Ethernet0
ip address 172.21.127.27 255.255.255.0
!This gatekeeper can be found at address 172.21.127.27. gatekeeper
!Enter gatekeeper config mode.
zone local
!Because a zone is, by definition, the area of control of a gatekeeper,
!we tend to use the terms “zone name” and “gatekeeper name” synonymously.
!Here we use the host name as the name of the gatekeeper and zone.
!This is not necessary, but it does simplify administration.
zone remote
!A couple of other zones within xyz.com. We make lots of calls
!between these departments, so we just configure these so we save
!a little time bypassing DNS lookup to find their gatekeepers.
!We have good QoS on our local network, so we don't need proxies when
!calling between the xyz.com zones. But for all other zones, we want
!to use proxies.
zone subnet
!We will accept registrations from our local subnet as long as they
!do not specify some other gatekeeper name. We will not accept any
!registrations from any other subnet.
zone bw
Cisco IOS Voice, Video, and Fax Configuration Guide