Cisco Systems VC-289 manual PX1 Configuration, VC-352

Page 64

Configuring H.323 Gatekeepers and Proxies

H.323 Gatekeeper Configuration Examples

Assuming these requirements are met, configure the network illustrated in Figure 62 as follows:

Configure each of the four networks as a separate routing autonomous system and do not redistribute routes between the multimedia backbone and any other autonomous system.

Create a loopback interface on the proxy and configure it to be the proxy interface. That way no subnets of the multimedia backbone will be exposed to the edge network, or the other way around.

To ensure that the address of the loopback interface does not travel outside the edge network, configure the appropriate distribution list on the edge router that connects the edge network to the data backbone. Configuring the appropriate distribution list guarantees that any ongoing H.323 call will be interrupted if the multimedia backbone fails. Otherwise, H.323 packets that originate from one proxy and that are destined to another proxy might discover an alternate route using the edge networks and the data backbone.

In some topologies, the two edge networks and the data backbone may be configured as a single autonomous system, but it is preferable to separate them as previously described because they are different networks with different characteristics.

The following examples illustrate the router configuration that is relevant to the closed proxy operation.

Configuring a Co-Edge Proxy with ASR Without Subnetting Example

See Figure 63 and the following configuration examples to see how to configure RIP on the two edge networks and how to configure IGRP on the two backbone networks.

Figure 63

Sample Configuration Without Subnetting

 

 

E1: 172.22.0.1

E1: 172.22.0.2

 

L0: 10.0.0.0

 

L0: 10.0.0.1

 

PX1

Multimedia

E0: 172.23.0.1

 

backbone

 

E0: 172.20.0.1

 

 

 

 

 

 

PX2

EP1

Edge net 1

 

Edge net 2

 

 

 

R2

E0: 172.20.0.2

Data backbone

172.23.0.2

 

R1

 

 

 

E2: 172.21.0.2

 

E1: 172.21.0.1

 

EP2

11027

PX1 Configuration

The following output is for the PX1 configuration:

!

proxy h323

!

interface Loopback0

ip address 10.0.0.0 255.0.0.0

!Assume PX1 is in Zone 1, and the gatekeeper resides in the same routers as PX1: h323 interface

h323 h323-id PX1@zone1.com

h323 gatekeeper ipaddr 10.0.0.0

!

Cisco IOS Voice, Video, and Fax Configuration Guide

VC-352

Image 64
Contents Configuring H.323 Gatekeepers and Proxies VC-289Principal Multimedia Conference Manager Functions VC-290Zone and Subnet Configuration Redundant H.323 Zone SupportGatekeeper Multiple Zone Support Gateway Support for Alternate GatekeepersTechnology Prefixes VC-292Interzone Communication Radius and TACACS+Accounting via Radius 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-299Proxies and NAT Proxy Outside the FirewallVC-300 Application-Specific Routing Quality of ServiceVC-301 Prerequisite Tasks and Restrictions VC-302Configuring the Gatekeeper VC-303Starting a Gatekeeper VC-304Gw-prioritypriority gw-alias-Optional Use H323-gateway voip h.323-id commandVC-305 Zone subnet command Mask-addressenableSubnet local-gatekeeper-name Subnet-address /bits-in-maskConfiguring Intergatekeeper Communication Server-address2...server-address6 -OptionalRas gk-id@host port priority VC-307Other-gatekeeper-ip-address-Specifies the IP Configuring Redundant H.323 Zone SupportVC-308 Configuring Local and Remote Gatekeepers VC-309Configuring Redundant Gatekeepers for a Zone Prefix Verifying Zone Prefix RedundancyOther-gatekeeper-name -Name of the remote Other-gatekeeper-ip-address -IP addressZone local or zone remote command. You can Configuring Redundant Gatekeepers for a Technology PrefixVC-311 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-320Other-gatekeeper-ip-address -Specifies the IP Configuring E.164 Interzone RoutingVC-321 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 Remote-zone remote-zone-name -Defines a Configuring Inbound or Outbound Gatekeeper Proxied AccessVC-330 Router# show gatekeeper zone status Verifying Gatekeeper Proxied Access ConfigurationVC-331 Configuring a Forced Disconnect on a Gatekeeper Configuring the ProxyVC-332 Show interfaces command Configuring a Proxy Without ASRVC-333 VC-334 VC-335 VC-336 Configuring a Proxy with ASR TunnelVg-anylan 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-346Redundant Gatekeepers for a Zone Prefix Example Redundant Gatekeepers for a Technology Prefix ExampleInterzone Routing Example VC-347VC-348 Configuring Hsrp on the Gatekeeper Example VC-349Using ASR for a Separate Multimedia Backbone Example VC-350Isolating the Multimedia Network Enabling the Proxy to Forward H.323 PacketsVC-351 PX1 Configuration VC-352R1 Configuration VC-353Co-Edge Proxy with Subnetting Example VC-354VC-355 R2 Configuration PX2 ConfigurationVC-356 Configuring a QoS-Enforced Open Proxy Using Rsvp Example VC-357VC-358 Configuring a Closed Co-Edge Proxy with ASR VC-359Defining One Zone for Multiple Gateways Example Defining Multiple Zones ExampleVC-360 Configuring a Proxy for Outbound Calls Example Configuring a Proxy for Inbound Calls ExampleVC-361 Removing a Proxy Example Security Example VC-362Prohibiting Proxy Use for Inbound Calls Example Gktmp and RAS Messages 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.