To enable proxy communications for calls between local and remote zones or the H.225 Annex G border element, use the use -proxy command in gatekeeper configuration mode. To remove either a proxy configuration entry for a remote zone or the H.225 Annex
G border element, to disable proxy communications between local and remote zones or H.225 Annex G border element, use the
no form of this command.
use-proxy local-zone-name {default | h323-annexg | remote-zone remote-zone-name} {inbound-to | outbound-from} {gateway | terminal}
no use-proxy local-zone-name {default | h323-annexg | remote-zone remote-zone-name} [ {inbound-to | outbound-from} {gateway | terminal}]
Syntax Description
|
local
-zone -name
|
Name or zone name of the gatekeeper, which is usually the fully domain-qualified host name of the gatekeeper.
|
|
default
|
Default proxy policy for all calls that are not defined by a use -proxy command with the remote -zone keyword or h323-annexg keyword.
|
|
h323-annexg
|
Proxy policy for calls to or from the H.225 Annex G border element co-located with the gatekeeper.
|
|
remote
-zone remote -zone -name
|
Proxy policy for calls to or from a specific remote gatekeeper or zone.
|
|
inbound
-to
|
Proxy policy as it applies to calls that are inbound to the local zone from a remote zone. Each use -proxy command defines the policy for only one direction.
|
|
outbound
-from
|
Proxy policy as it applies to calls that are outbound from the local zone to a remote zone. Each use -proxy command defines the policy for only one direction.
|
|
gateway
|
Type of local device to which the policy applies. The gateway option applies the policy only to local gateways.
|
|
terminal
|
Type of local device to which the policy applies. The terminal option applies the policy only to local terminals.
|
Command Default
The local zone uses proxy for both inbound and outbound calls to and from the local H.323 terminals only. Proxy is not used
for both inbound and outbound calls to and from local gateways. For releases prior to Cisco IOS Release 12.3(7)T, both inbound
and outbound calls using the H.225 Annex G border element do not use the proxy.
Command Modes
Gatekeeper configuration
Command History
|
Release
|
Modification
|
|
12.0(5)T
|
This command was introduced on the Cisco AS5300.
|
|
12.1(5)XM2
|
The command was implemented on the Cisco AS5350 and Cisco AS5400.
|
|
12.2(4)T
|
This command was integrated into Cisco IOS Release 12.2(4)T. Support for the Cisco AS5300, Cisco AS5350, and Cisco AS5400
is not included in this release.
|
|
12.2(2)XB1
|
This command was implemented on the Cisco AS5850.
|
|
12.2(11)T
|
This command was integrated into Cisco IOS Release 12.2(11)T.
|
|
12.3(7)T
|
The h323-annexg keyword was added.
|
Usage Guidelines
This command replaces the zone access command used in previous versions of the gatekeeper. When a previous version of a gatekeeper is upgraded, any zone access commands are translated to use -proxy commands. You can use the show gatekeeper zone status command to see the gatekeeper proxy configuration.
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.
Examples
In the following example, the local zone sj.xyz.com is configured to use a proxy for inbound calls from remote zones tokyo.xyz.com
and milan.xyz.com to gateways in its local zone. The sj.xyz.com zone is also configured to use a proxy for outbound calls
from gateways in its local zone to remote zones tokyo.xyz.com and milan.xyz.com.
use-proxy sj.xyz.com remote-zone tokyo.xyz.com inbound-to gateway
use-proxy sj.xyz.com remote-zone tokyo.xyz.com outbound-from gateway
use-proxy sj.xyz.com remote-zone milan.xyz.com inbound-to gateway
use-proxy sj.xyz.com remote-zone milan.xyz.com outbound-from gateway
Because the default mode disables proxy communications for all gateway calls, only the gateway calls listed above can use
the proxy.
In the following example, the local zone sj.xyz.com uses a proxy for only those calls that are outbound from H.323 terminals
in its local zone to the specified remote zone germany.xyz.com:
no use-proxy sj.xyz.com default outbound-from terminal
use-proxy sj.xyz.com remote-zone germany.xyz.com outbound-from terminal
Note
|
Any calls inbound to H.323 terminals in the local zone sj.xyz.com from the remote zone germany.xyz.com use the proxy because
the default applies.
|
The following example removes one or more proxy statements for the remote zone germany.xyz.com from the proxy configuration
list:
no use-proxy sj.xyz.com remote-zone germany.xyz.com
This command removes all special proxy configurations for the remote zone germany.xyz.com. After you enter a command like
this, all calls between the local zone (sj.xyz.com) and germany.xyz.com are processed according to the defaults defined by
any use -proxy commands that use the default option.
To prohibit proxy use for inbound calls to H.323 terminals in a local zone from a specified remote zone, enter a command similar
to the following:
no use-proxy sj.xyz.com remote-zone germany.xyz.com inbound-to terminal
This command overrides the default and disables proxy use for inbound calls from remote zone germany.xyz.com to all H.323
terminals in the local zone sj.xyz.com.
In the following example, the local zone sj.xyz.com is configured to use a proxy for inbound calls and outbound calls that
use the H.225 Annex G border element co-located with the gatekeeper:
use-proxy sj.xyz.com h323-annexg inbound-to gateway
use-proxy sj.xyz.com h323-annexg outbound-from gateway
In the following example, the local zone sj.xyz.com is configured not to use a proxy for inbound calls and outbound calls
that use the H.225 Annex G border element co-located with the gatekeeper:
no use-proxy sj.xyz.com h323-annexg inbound-to terminal
no use-proxy sj.xyz.com h323-annexg outbound-from terminal
The following example removes one or more proxy statements for the H.225 Annex G border element from the proxy configuration
list:
no use-proxy sj.xyz.com h323-annexg
Feedback