Following are the configuration steps for registering a gateway on a gatekeeper:
Step 1. Enable the gateway process on the router.
Step 2. Configure interface commands for H.323 registration at the gatekeeper.
Step 3. Configure the dial peers that are pointing to the gatekeeper.
Step 4. If necessary, prevent ephone-dn and dial-peer registration at the gatekeeper.
Example 8-15 and Figure 8-36 show the configuration for a gateway registering with a
gatekeeper.
Example 8-15 H.323 Gateway Configuration
SanJose#show running-config
gateway
!
interface Loopback 0
ip address 192.168.1.3 255.255.255.0
h323-gateway voip interface
h323-gateway voip bind srcaddr 192.168.1.3
h323-gateway voip id GK1 ipaddr 192.168.1.15 1719 priority 1
h323-gateway voip h323-id Houston
h323-gateway voip tech-prefix 1#
Figure 8-36 Configuring Gateways to Use H.323 Gatekeepers
You can use the following steps to configure gateways to use H.323 gatekeepers.
Step 1. Enable the H.323 VoIP gateway to register with a gatekeeper.
Router(config)#gateway
Sometimes it is helpful to enable the gateway process at the end of your gateway
configuration to avoid automatic gateway registration at the gatekeeper.
For example, this is useful if you have multiple gatekeepers and want to make
sure you are unicasting to a specific gatekeeper or using a specific H.323 ID.
This allows all interface commands to be entered before the gateway attempts
registration with the gatekeeper.
Step 2. Enter interface configuration mode for the interface you intend to use for
communication with the H.323 gatekeeper.
Router(config)#interface loopback 0
Step 3. Give the interface an IP address.
Router(config-if)#ip-address 192.168.1.3 255.255.255.0
Step 4. Configure the interface as an H.323 gateway interface.
Router(config-if)#h323-gateway voip interface
Step 5. Define the IP address on the gateway to be used for H.323 communication.
Router(config-if)#h323-gateway voip bind srcaddr 192.168.1.3
Step 6. Define the name and location of the gatekeeper.
Router(config-if)#h323-gateway voip id Houston ipaddr 192.168.1.15 1719
priority 1
498 Authorized Self-Study Guide: Cisco Voice over IP (CVOICE)
San Jose
Gatekeeper
192.168.1.15
Houston
(H.323)
192.168.1.3
Fa0/1
SanJose
(H.323)
Houston
Phone2-1
3001
Phone2-2
3002
Phone1-1
2001
Phone1-2
2002
WAN
GK1
This command is acclimated to specify the IP abode of the attendant and the
zone the aperture should annals with, in this case Houston. Without the voip
id parameter, the aperture will use multicast for attendant discovery. When
using multicast, the aperture will annals with the aboriginal accessible area on the
gatekeeper. The attendant ID is the area the aperture should annals with.
Step 7. Specify the H.323 aperture name to analyze it to its associated gatekeeper.
Router(config-if)#h323-gateway voip h323-id Houston
This is an alternative command acclimated to analyze a aperture to its associated gatekeeper.
In this case, the aperture will annals with the name Houston at the
gatekeeper.
Step 8. Specify the technology prefix the aperture registers with the gatekeeper.
Router(config-if)#h323-gateway voip tech-prefix 1#
The aperture will acquaint the attendant it wants to annals with a technology
prefix of 1#. Each technology prefix can accommodate as abounding as 11 characters.
Although not carefully necessary, a batter assurance (#) is frequently acclimated as the last
digit in a technology prefix.
Table 8-3 provides a table of aperture interface agreement commands and explains
their purpose.
Table 8-3 Aperture Interface Agreement Commands
Command Purpose
h323-gateway voip interface Identifies an interface as a VoIP aperture interface.
h323-gateway voip id (Optional) Defines the name and area of the gatekeeper
gatekeeper-id {ipaddr for this gateway.
ip-address [port]| multicast} Following are the keywords and arguments:
[priority priority] ■ gatekeeper-id: H.323 identification of the gatekeeper,
which should bout a area configured on a gatekeeper. If
no bout is found, the attendant will annals the gateway
with the aboriginal configured bounded zone.
■ ipaddr ip-address: IP abode acclimated to analyze the
gatekeeper.
■ port: UDP anchorage cardinal acclimated for communicating with a
gatekeeper.
■ multicast: Acclimated by the aperture to locate a gatekeeper.
■ antecedence priority: This is the antecedence of this gatekeeper.
The adequate ambit is 1–127, and the absence is 127.
continues
Table 8-3 Gateway Interface Configuration Commands (continued)
Command Purpose
h323-gateway voip (Optional) Defines the H.323 name of the gateway that
h323-id interface-id identifies this gateway to its associated gatekeeper.
Usually this ID is the name of the gateway, with the gatekeeper
domain name appended to the end: name@domainname.
h323-gateway voip (Optional) Defines the numbers used as the technology prefix
tech-prefix prefix that the gateway uses to register with a gatekeeper.
This command can contain up to 11 characters. Although it is
not strictly necessary, a pound symbol (#) is frequently used
as the last digit in a prefix. Valid characters are 0–9, #, and *.