Cisco H.323 VC-289 - Manual (Page 42)

Configuring H.323 Gatekeepers and Proxies
H.323 Gatekeeper Configuration Task List
VC-330
Cisco IOS Voice, Video, and Fax Configuration Guide
Note To remove a trigger, enter the no server trigger command. To temporarily suspend a trigger, enter
the trigger configuration mode, as described in Step 2, and enter the shutdown subcommand.
Configuring Inbound or Outbound Gatekeeper Proxied Access
By default, a gatekeeper will offer the IP address of the local proxy when queried by a remote gatekeeper
(synonymous with remote zone). This is considered proxied access. Before Cisco IOS Release 12.0(5)T,
the local gatekeeper was configured using the zone access command to offer the address of the local
endpoint instead of the address of the local proxy (considered direct access).
Note The use-proxy command replaces the zone access command. The use-proxy command, configured
on a local gatekeeper, affects only the use of proxies for incoming calls (that is, it does not affect the
use of local proxies for outbound calls). When originating a call, a gatekeeper will use a proxy only
if the remote gatekeeper offers a proxy at the remote end. A call between two endpoints in the same
zone will always be a direct (nonproxied) call.
To configure a proxy for inbound calls from remote zones to gateways in its local zone and to configure
a proxy for outbound calls from gateways in its local zone to remote zones, use the following commands
beginning in global configuration mode:
Command Purpose
Step 1 Router(config)# gatekeeper Enters gatekeeper configuration mode.
Step 2 Router(config-gk)# use-proxy local-zone-name
{default | remote-zone remote-zone-name} {inbound-to
| outbound-from} {gateway | terminal}
Enables proxy communications for calls between
local and remote zones.
The keywords and arguments are as follows:
• local-zone-name—Specifies the name or zone
name of the gatekeeper, which is usually the fully
domain-qualified host name of the gatekeeper.
For example, if the domain name is cisco.com,
the gatekeeper name might be gk1.cisco.com.
However, if the gatekeeper is controlling
multiple zones, the name of the gatekeeper for
each zone should be a unique string that has a
mnemonic value.
• default—Defines the default proxy policy for all
calls that are not defined by a use-proxy
command that includes the remote-zone
keyword.
• remote-zone remote-zone-name—Defines a
proxy policy for calls to or from a specific remote
gatekeeper or zone.