Cisco Systems VC-289 Configuring Redundant H.323 Zone Support, Manual Configuration, Command

Models: VC-289

1 76
Download 76 pages 30.7 Kb
Page 20
Image 20
Manual Configuration

Configuring H.323 Gatekeepers and Proxies

H.323 Gatekeeper Configuration Task List

zone3.comintxt“ras gk.3@gk.zone3.com:1725” zone4.comintxt“ras gk4@gk.zone4.com:1725 123” zone5.comintxt“ras gk5@101.0.0.1:1725”

Manual Configuration

If you choose not to use DNS or if DNS is not available, configure intergatekeeper communication manually. To configure intergatekeeper manual communication, use the following command in gatekeeper configuration mode for every other gatekeeper in the network:

Command

Purpose

 

 

Router(config-gk)#zone remote other-gatekeeper-name

Statically specifies a remote zone if Domain Name System

other-domain-name other-gatekeeper-ip-address

(DNS) is unavailable or undesirable. Enter this command

[port-number]

for each gatekeeper.

 

 

The arguments are as follows:

 

other-gatekeeper-name—Specifies the name of the

 

remote gatekeeper.

 

other-domain-name—Specifies the domain name of

 

the remote gatekeeper.

 

other-gatekeeper-ip-address—Specifies the IP

 

address of the remote gatekeeper.

 

port-number—(Optional) Specifies the RAS signaling

 

port number for the remote zone. Value ranges are

 

from 1 to 65,535. If this option is not set, the default is

 

the well-known RAS port number 1719.

 

 

Configuring Redundant H.323 Zone Support

Regardless of whether you specify sequential or blast, there is an order to how the LRQs are sent. With sequential, the LRQs are sent one at a time with a delay between each. With blast, the LRQs are sent back-to-back in a rapid sequence without any delay between them. The order in which zone and technology prefixes are configured determines the order in which the LRQs are sent to the remote gatekeepers. Using zone prefixes as an example, the local gatekeeper routes the call to the first zone that responds with an LCF. If the local gatekeeper is configured for a zone prefix that already has remote gatekeepers configured, the local gatekeeper will automatically put that zone prefix at the top of the list.

For example:

gatekeeper

zone local gnet-2503-2-gk cisco.com

zone remote gnet-2600-1-gk cisco.com 172.18.194.131 1719 zone remote gnet-2503-3-gk cisco.com 172.18.194.134 1719 zone prefix gnet-2600-1-gk 919.......

zone prefix gnet-2503-6-gk 919.......

With this configuration, LRQs are first sent to gnet-2600-1-gk (which is the first zone prefix because it has a remote gatekeeper configured for it) and then to gnet-2503-6-gk (which is the second zone prefix). If you add the local gatekeeper to that zone prefix, it automatically goes to the top of the list, as shown below:

gatekeeper

zone local gnet-2503-2-gk cisco.com

zone remote gnet-2600-1-gk cisco.com 172.18.194.131 1719

Cisco IOS Voice, Video, and Fax Configuration Guide

VC-308

Page 20
Image 20
Cisco Systems VC-289 manual Configuring Redundant H.323 Zone Support, Manual Configuration, Command, Purpose, VC-308