Cisco Systems VC-289 Configuring Intergatekeeper Communication, Via DNS, Command, Purpose, VC-307

Configuring H.323 Gatekeepers and Proxies

H.323 Gatekeeper Configuration Task List

Note To explicitly enable or disable a particular endpoint, specify its host address using a 32-bit subnet mask.

Configuring Intergatekeeper Communication

This section describes two ways to configure intergatekeeper communication:

•Via DNS, page 307

•Manual Configuration, page 308

Via DNS

To configure intergatekeeper communication using DNS, use the following commands in global configuration mode:

	Command	Purpose
Step 1
	Router(config)# ip name-serverdns-server-name	Specifies the DNS server address.
	[server-address2...server-address6]	The arguments are as follows:
		• dns-server-name— Specifies the IP address of
		the name server.
		• server-address2...server-address6—(Optional)
		IP addresses of additional name servers (a
		maximum of six name servers).
Step 2
	Router(config)# ip domain-namename	Defines a default domain name that the Cisco IOS
		software uses to complete unqualified host names
		(names without a dotted-decimal domain name). The
		name argument specifies the default domain name
		used to complete unqualified host names. Do not
		include the initial period that separates an unqualified
		name from the domain name.

For all gatekeepers in the system, enter a text record of the form into DNS:

ras [gk-id@]host [:port] [priority]

The gk-idargument is an optional gatekeeper ID. If the optional gatekeeper ID is not specified, host is used as the gatekeeper ID.

The host argument is either an IP address or the actual host name of the gatekeeper in the form host.some_domain.com.

The port argument, if specified, should be some port number other than RAS port 1719.

The priority argument specifies the order in which the listed gatekeepers should be searched for endpoints. Gatekeepers with lower priorities are searched before those with higher numbers.

How you enter the text record for a particular domain depends on the DNS implementation. The following examples are for the Berkeley Internet Name Domain (BIND). These records are typically entered into the “hosts” database:

zone1.comintxt“ras gk.zone1.com” zone2.comintxt“ras gk2@gk.zone2.com”

Cisco IOS Voice, Video, and Fax Configuration Guide

VC-307