Table Of Contents

Configuring the Cisco IOS Gatekeeper for the Cisco MXE Video Interoperability Solution

Configuring the Cisco IOS Gatekeeper for the Cisco MXE Video Interoperability Solution

---

Revised: June 3, 2011

This chapter describes how to configure Cisco IOS for the Cisco MXE Video Interoperability Solution. For more information about configuring a gatekeeper, see the "Configuring H.323 Gatekeepers and Proxy" chapter in the Cisco IOS H.323 Configuration Guide for your release on Cisco.com.

This configuration is required only for H.323 endpoints.

Before You Begin

Open a Telnet/SSH session with a Cisco IOS gateway that is to be configured as an H.323 gatekeeper.

Procedure

---

Step 1 To enter gatekeeper configuration mode, enter the following command in global configuration mode:

Router(config)# gatekeeper

Step 2 To specify a zone controlled by the gatekeeper, enter the following command:

Router(config)# zone local gatekeeper-name domain-name ras-ip-address

where gatekeeper-name is the name for this gatekeeper; domain-name is the domain name that this gatekeeper serves; and ras-IP-address is the IP address of this gatekeeper.

This command specifies the zone for which the gatekeeper is responsible. A gatekeeper zone is a collection of H.323 nodes, and in this zone configuration, Cisco Unified Communications Manager (CUCM) functions as a node for the gatekeeper.

Step 3 If you are configuring only a single zone, continue to Step 4. A single zone deployment does not require remote zones.

or

To statically specify a remote zone, enter the following command for each remote zone that you want to configure:

Router(config)# zone remote other-gatekeeper-name other-domain-name other-gatekeeper-ip-address

where other-gatekeeper-name is the name for this remote gatekeeper; other-domain-name is the domain name that this gatekeeper serves; and other-ip-address is the IP address of this remote gatekeeper.

This command creates remote gatekeeper zones for which other gatekeepers are responsible.

Step 4 (Optional) To configure a technology prefix for this gatekeeper, enter the following command:

Router(config)# gw-type-prefix type-prefix default-technology

This command sets up a default technology prefix for the local zone. CUCM can then be configured to register to receive calls using this same technology prefix. Alternatively, you can configure CUCM as a remote zone and configure specific zone prefixes for it.

Step 5 (Optional) To create prefixes for each zone, enter the following command for each prefix that you want to configure:

Router(config)# zone prefix gatekeeper-name prefix

where gatekeeper-name is the name for the local or remote gatekeeper, and prefix is the prefix to assign to this zone.

Step 6 To disable proxy communications between local and remote zones for inbound calls, enter the following command:

Router(config)# no use-proxy gatekeeper-name default inbound-to terminal

where gatekeeper-name is the name of this gatekeeper.

This command configures the gatekeeper so that it does not act as a media proxy for inbound calls to terminals that are registered with it.

Step 7 To disable proxy communications between local and remote zones for outbound calls, enter the following command:

Router(config)# no use-proxy gatekeeper-name default outbound-from terminal

where gatekeeper-name is the name of this gatekeeper.

This command configures the gatekeeper so that it does not act as a media proxy for outbound calls from terminals registered that are registered with it.

Step 8 (Optional) To forward of calls between zones, enable forwarding of LRQ queries by entering the following command:

Router(config-gk)# lrq forward-queries

Step 9 (Optional) To enable bandwidth management on the gatekeeper, enter the following commands:

Router(config-gk)# bandwidth ?

•check-destination—Destination zone bandwidth check before responding ARQ

•interzone—Configure max bandwidth allowed from zone to all other zones

•remote—Configure max bandwidth allowed to all remote zones

•session—Configure max bandwidth allowed for a session in a zone

•total—Configure max bandwidth allowed for all calls in a zone

By default, all values are set to unlimited. If you modify the default configuration, ensure that the session bandwidth is at least twice the region bandwidth that is configured in CUCM. The total bandwidth should be at least the session bandwidth multiplied by the maximum number of desired concurrent calls.

---

Example 8-1 Configuration for Two-Zone Deployment with Default Technology Prefix

gatekeeper

 zone local h323_gatekeeper domain.com 209.165.200.225

 zone remote c2600GK domain.com 209.165.201.1 1719

 zone prefix c2600GK 845657..

 zone prefix c2600GK 8456580.

 gw-type-prefix 1#* default-technology

 no use-proxy h323_gatekeeper default inbound-to terminal

 no use-proxy h323_gatekeeper default outbound-from terminal