Cisco Systems VC-289 manual Security, VC-297

Page 9

Configuring H.323 Gatekeepers and Proxies

H.323 Proxy Features

Note Gatekeeper failover will not be completely transparent to endpoints and gatekeepers. When the standby gatekeeper takes over, it does not have the state of the failed gatekeeper. If an endpoint that had registered with the failed gatekeeper now makes a request to the new gatekeeper, the gatekeeper responds with a reject, indicating that it does not recognize the endpoint. The endpoint must reregister with the new gatekeeper before it can continue H.323 operations.

For an example of configuring gatekeeper HSRP support, see the “H.323 Gatekeeper and Proxy Configuration Examples” section.

H.323 Proxy Features

Each of the following sections describes how the proxy feature can be used in an H.323 network:

Security, page 297

Quality of Service, page 301

Application-Specific Routing, page 301

Security

When terminals signal each other directly, they must have direct access to each other’s addresses. This exposes an attacker to key information about a network. When a proxy is used, the only addressing information that is exposed to the network is the address of the proxy; all other terminal and gateway addresses are hidden.

There are several ways to use a proxy with a firewall to enhance network security. The configuration to be used depends on how capable the firewall is of handling the complex H.323 protocol suite. Each of the following sections describes a common configuration for using a proxy with a firewall:

Proxy Inside the Firewall, page 298

Proxy in Co-Edge Mode, page 299

Proxy Outside the Firewall, page 300

Proxies and NAT, page 300

Cisco IOS Voice, Video, and Fax Configuration Guide

VC-297

Image 9
Contents VC-289 Configuring H.323 Gatekeepers and ProxiesVC-290 Principal Multimedia Conference Manager FunctionsRedundant H.323 Zone Support Zone and Subnet ConfigurationGatekeeper Multiple Zone Support Gateway Support for Alternate GatekeepersVC-292 Technology PrefixesRadius and TACACS+ Interzone CommunicationAccounting via Radius and TACACS+ Terminal Name RegistrationVC-294 Interzone Routing Using E.164 AddressesVC-295 VC-296 Hsrp SupportVC-297 SecurityVC-298 Proxy Inside the FirewallVC-299 Proxy in Co-Edge ModeProxy Outside the Firewall Proxies and NATVC-300 Quality of Service Application-Specific RoutingVC-301 VC-302 Prerequisite Tasks and RestrictionsVC-303 Configuring the GatekeeperVC-304 Starting a GatekeeperH323-gateway voip h.323-id command Gw-prioritypriority gw-alias-Optional UseVC-305 Mask-addressenable Zone subnet commandSubnet local-gatekeeper-name Subnet-address /bits-in-maskServer-address2...server-address6 -Optional Configuring Intergatekeeper CommunicationRas gk-id@host port priority VC-307Configuring Redundant H.323 Zone Support Other-gatekeeper-ip-address-Specifies the IPVC-308 VC-309 Configuring Local and Remote GatekeepersVerifying Zone Prefix Redundancy Configuring Redundant Gatekeepers for a Zone PrefixOther-gatekeeper-name -Name of the remote Other-gatekeeper-ip-address -IP addressConfiguring Redundant Gatekeepers for a Technology Prefix Zone local or zone remote command. You canVC-311 VC-312 Verifying Technology Prefix RedundancyVC-313 Configuring Static NodesVC-314 Configuring H.323 Users via RadiusVC-315 Server radius or aaa group server tacacs+VC-316 VC-317 Password default password-SpecifiesVC-318 Configuring a RADIUS/AAA ServerVC-319 Users via Radius section onVC-320 Configuring User Accounting Activity for RadiusConfiguring E.164 Interzone Routing Other-gatekeeper-ip-address -Specifies the IPVC-321 VC-322 Configuring H.323 Version 2 FeaturesVC-323 Configuring a Dialing Prefix for Each GatewayVC-324 Gateway with the h323-gateway voip h.323-id commandVC-325 Following is an example of a registration messageVC-326 Configuring a Prefix to a Gatekeeper Zone ListVC-327 Arq, lcf, lrj, lrq, rrq, urq -Specifies RegistrationVC-328 VC-329 Configuring Inbound or Outbound Gatekeeper Proxied Access Remote-zone remote-zone-name -Defines aVC-330 Verifying Gatekeeper Proxied Access Configuration Router# show gatekeeper zone statusVC-331 Configuring the Proxy Configuring a Forced Disconnect on a GatekeeperVC-332 Configuring a Proxy Without ASR Show interfaces commandVC-333 VC-334 VC-335 VC-336 Tunnel Configuring a Proxy with ASRVg-anylan VC-337VC-338 Without ASR section onVC-339 VC-340 Cisco IOS Dial Technologies CommandVC-341 VC-342 VC-343 VC-344 VC-345 Configuring a Proxy with ASR section onVC-346 Configuring a Gatekeeper ExampleRedundant Gatekeepers for a Technology Prefix Example Redundant Gatekeepers for a Zone Prefix ExampleInterzone Routing Example VC-347VC-348 VC-349 Configuring Hsrp on the Gatekeeper ExampleVC-350 Using ASR for a Separate Multimedia Backbone ExampleEnabling the Proxy to Forward H.323 Packets Isolating the Multimedia NetworkVC-351 VC-352 PX1 ConfigurationVC-353 R1 ConfigurationVC-354 Co-Edge Proxy with Subnetting ExampleVC-355 PX2 Configuration R2 ConfigurationVC-356 VC-357 Configuring a QoS-Enforced Open Proxy Using Rsvp ExampleVC-358 VC-359 Configuring a Closed Co-Edge Proxy with ASRDefining Multiple Zones Example Defining One Zone for Multiple Gateways ExampleVC-360 Configuring a Proxy for Inbound Calls Example Configuring a Proxy for Outbound Calls ExampleVC-361 VC-362 Removing a Proxy Example Security ExampleGktmp and RAS Messages Example Prohibiting Proxy Use for Inbound Calls ExampleVC-363 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.