Cisco Systems VC-289 manual Without ASR section on, VC-338

Page 50

Configuring H.323 Gatekeepers and Proxies

H.323 Gatekeeper Configuration Task List

 

Command

Purpose

Step 3

 

 

Router(config-if)# ip address ip-address mask

Sets a primary or secondary IP address for an

 

[secondary]

interface.

 

 

The keywords and arguments are as follows:

 

 

ip-address—Specifies the IP address.

 

 

mask—Specifies the mask for the associated IP

 

 

subnet.

 

 

secondary—(Optional) Specifies that the

 

 

configured address is a secondary IP address. If

 

 

this keyword is omitted, the configured address is

 

 

the primary IP address.

Step 4

 

 

Router(config-if)# h323 interface [port-number]

Signals the proxy that this interface IP address is the

 

 

one to use.

 

 

For an explanation of the arguments, see Step 3 in the

 

 

configuration task table in the “Configuring a Proxy

 

 

Without ASR” section on page 333.

Step 5

 

 

Router(config-if)# h323 h323-idh323-id

Configures the proxy name. (More than one name can

 

 

be configured if necessary.)

 

 

The h323-idargument specifies the name of the

 

 

proxy. It is recommended that this be a fully qualified

 

 

e-mail identification (ID), with the domain name

 

 

being the same as that of its gatekeeper.

Step 6

 

 

Router(config-if)# h323 gatekeeper [id

Specifies the gatekeeper associated with a proxy and

 

gatekeeper-id] {ipaddr ipaddr [port] multicast}

controls how the gatekeeper is discovered.

 

 

For an explanation of the keywords and arguments,

 

 

see Step 5 in the configuration task table in the

 

 

“Configuring a Proxy Without ASR” section on

 

 

page 333.

Step 7

 

 

Router(config-if)# h323 qos {ip-precedence value

Enables quality of service (QoS) on the proxy.

 

rsvp {controlled-load guaranteed-qos}}

For an explanation of the keywords and arguments,

 

 

 

 

see Step 6 in the configuration task table in the

 

 

“Configuring a Proxy Without ASR” section on

 

 

page 333.

Step 8

 

 

Router(config-if)# interface type number [name-tag]

If ASR is to be used, enters the interface through

 

 

which outbound H.323 traffic should be routed.

 

 

For an explanation of the keywords and arguments,

 

 

see Step 2 in the configuration task table in the

 

 

“Configuring a Proxy Without ASR” section on

 

 

page 333.

 

 

 

Cisco IOS Voice, Video, and Fax Configuration Guide

VC-338

Image 50
Contents Configuring H.323 Gatekeepers and Proxies VC-289Principal Multimedia Conference Manager Functions VC-290Gatekeeper Multiple Zone Support Zone and Subnet ConfigurationRedundant H.323 Zone Support Gateway Support for Alternate GatekeepersTechnology Prefixes VC-292Accounting via Radius and TACACS+ Interzone CommunicationRadius and TACACS+ Terminal Name RegistrationInterzone Routing Using E.164 Addresses VC-294VC-295 Hsrp Support VC-296Security VC-297Proxy Inside the Firewall VC-298Proxy in Co-Edge Mode VC-299VC-300 Proxy Outside the FirewallProxies and NAT VC-301 Quality of ServiceApplication-Specific Routing Prerequisite Tasks and Restrictions VC-302Configuring the Gatekeeper VC-303Starting a Gatekeeper VC-304VC-305 H323-gateway voip h.323-id commandGw-prioritypriority gw-alias-Optional Use Subnet local-gatekeeper-name Zone subnet commandMask-addressenable Subnet-address /bits-in-maskRas gk-id@host port priority Configuring Intergatekeeper CommunicationServer-address2...server-address6 -Optional VC-307VC-308 Configuring Redundant H.323 Zone SupportOther-gatekeeper-ip-address-Specifies the IP Configuring Local and Remote Gatekeepers VC-309Other-gatekeeper-name -Name of the remote Configuring Redundant Gatekeepers for a Zone PrefixVerifying Zone Prefix Redundancy Other-gatekeeper-ip-address -IP addressVC-311 Configuring Redundant Gatekeepers for a Technology PrefixZone local or zone remote command. You can Verifying Technology Prefix Redundancy VC-312Configuring Static Nodes VC-313Configuring H.323 Users via Radius VC-314Server radius or aaa group server tacacs+ VC-315VC-316 Password default password-Specifies VC-317Configuring a RADIUS/AAA Server VC-318Users via Radius section on VC-319Configuring User Accounting Activity for Radius VC-320VC-321 Configuring E.164 Interzone RoutingOther-gatekeeper-ip-address -Specifies the IP Configuring H.323 Version 2 Features VC-322Configuring a Dialing Prefix for Each Gateway VC-323Gateway with the h323-gateway voip h.323-id command VC-324Following is an example of a registration message VC-325Configuring a Prefix to a Gatekeeper Zone List VC-326Arq, lcf, lrj, lrq, rrq, urq -Specifies Registration VC-327VC-328 VC-329 VC-330 Configuring Inbound or Outbound Gatekeeper Proxied AccessRemote-zone remote-zone-name -Defines a VC-331 Verifying Gatekeeper Proxied Access ConfigurationRouter# show gatekeeper zone status VC-332 Configuring the ProxyConfiguring a Forced Disconnect on a Gatekeeper VC-333 Configuring a Proxy Without ASRShow interfaces command VC-334 VC-335 VC-336 Vg-anylan Configuring a Proxy with ASRTunnel VC-337Without ASR section on VC-338VC-339 Cisco IOS Dial Technologies Command VC-340VC-341 VC-342 VC-343 VC-344 Configuring a Proxy with ASR section on VC-345Configuring a Gatekeeper Example VC-346Interzone Routing Example Redundant Gatekeepers for a Zone Prefix ExampleRedundant Gatekeepers for a Technology Prefix Example VC-347VC-348 Configuring Hsrp on the Gatekeeper Example VC-349Using ASR for a Separate Multimedia Backbone Example VC-350VC-351 Enabling the Proxy to Forward H.323 PacketsIsolating the Multimedia Network PX1 Configuration VC-352R1 Configuration VC-353Co-Edge Proxy with Subnetting Example VC-354VC-355 VC-356 PX2 ConfigurationR2 Configuration Configuring a QoS-Enforced Open Proxy Using Rsvp Example VC-357VC-358 Configuring a Closed Co-Edge Proxy with ASR VC-359VC-360 Defining Multiple Zones ExampleDefining One Zone for Multiple Gateways Example VC-361 Configuring a Proxy for Inbound Calls ExampleConfiguring a Proxy for Outbound Calls Example Removing a Proxy Example Security Example VC-362VC-363 Gktmp and RAS Messages ExampleProhibiting Proxy Use for Inbound Calls Example VC-364

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.