Configuring H.323 Gatekeepers and Proxies

H.323 Gatekeeper Configuration Task List

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-proxycommand replaces the zone access command. The use-proxycommand, 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-proxylocal-zone-name

Enables proxy communications for calls between

 

{default remote-zone remote-zone-name}{inbound-to

local and remote zones.

 

outbound-from} {gateway terminal}

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-zoneremote-zone-name—Defines a

 

 

proxy policy for calls to or from a specific remote

 

 

gatekeeper or zone.

 

 

 

Cisco IOS Voice, Video, and Fax Configuration Guide

VC-330

Page 41 Page 43
Page 42
Image 42
Cisco Systems VC-289 Configuring Inbound or Outbound Gatekeeper Proxied Access, Remote-zone remote-zone-name -Defines a
Page 41 Page 43

VC-289 specifications

Cisco Systems has long been a leader in networking technology, and among its diverse range of products is the VC-289. Designed specifically for enhanced performance in high-demand environments, the VC-289 serves a critical role in supporting the modern networking infrastructure.

One of the standout features of the VC-289 is its scalability. The device is engineered to easily accommodate expanded workloads, ensuring that organizations can grow without the need for frequent upgrades. This scalability is complemented by Cisco's commitment to backward compatibility, allowing businesses to integrate new systems with existing setups seamlessly.

In terms of performance, the VC-289 boasts impressive processing power. With advanced multi-core architecture, it is capable of handling multiple data streams simultaneously, making it ideal for environments that require consistent data flow, such as cloud computing and IoT applications. The device’s high throughput ensures that users experience minimal latency, facilitating quick data transfers even during peak usage times.

Security is another key characteristic of the VC-289. Cisco has integrated robust security protocols that protect against various cyber threats. Through features such as advanced encryption standards and intrusion prevention systems, organizations can ensure that sensitive data remains secure and is not compromised during transmission.

Another notable technology within the VC-289 is its support for software-defined networking (SDN) capabilities. This allows for more flexible network management, enabling IT teams to adapt the network according to evolving business needs. The ability to programmatically control the network also means that businesses can implement changes more rapidly, reducing downtime and improving overall productivity.

The VC-289 is designed with energy efficiency in mind, featuring power-saving modes that help reduce operational costs. This focus on sustainability not only benefits the environment but also appeals to organizations striving to meet corporate social responsibility objectives.

In conclusion, the Cisco Systems VC-289 stands as an exemplary solution for modern networking challenges. With its scalability, performance capabilities, enhanced security features, SDN support, and energy efficiency, it meets the demands of today's fast-paced and ever-evolving technological landscape. Organizations looking to invest in a robust networking solution would do well to consider the VC-289 as a cornerstone of their infrastructure.
Top Page Image Contents