Cisco Systems VC-289 manual Configuring a Gatekeeper Example, VC-346

Page 58

Configuring H.323 Gatekeepers and Proxies

H.323 Gatekeeper Configuration Examples

Configuring a Co-Edge Proxy with ASR Without Subnetting Example, page 352

Co-Edge Proxy with Subnetting Example, page 354

Configuring an Inside-Edge Proxy with ASR Without Subnetting Example, page 356

Configuring a QoS-Enforced Open Proxy Using RSVP Example, page 357

Configuring a Closed Co-Edge Proxy with ASR Without Subnetting Example, page 359

Defining Multiple Zones Example, page 360

Defining One Zone for Multiple Gateways Example, page 360

Configuring a Proxy for Inbound Calls Example, page 361

Configuring a Proxy for Outbound Calls Example, page 361

Removing a Proxy Example, page 362

H.235 Security Example, page 362

GKTMP and RAS Messages Example, page 363

Prohibiting Proxy Use for Inbound Calls Example, page 363

Disconnecting a Single Call Associated with an H.323 Gateway Example, page 363

Disconnecting All Calls Associated with an H.323 Gateway Example, page 363

Configuring a Gatekeeper Example

The following is an annotated example of how to configure a gatekeeper:

hostname gk-eng.xyz.com

!This router serves as the gatekeeper for the engineering community.

!at xyz.com.

ip domain-name xyz.com

!Domain name of this company. interface Ethernet0

ip address 172.21.127.27 255.255.255.0

!This gatekeeper can be found at address 172.21.127.27. gatekeeper

!Enter gatekeeper config mode.

zone local gk-eng.xyz.com xyz.com

!Because a zone is, by definition, the area of control of a gatekeeper,

!we tend to use the terms “zone name” and “gatekeeper name” synonymously.

!Here we use the host name as the name of the gatekeeper and zone.

!This is not necessary, but it does simplify administration.

zone remote gk-mfg.xyz.com xyz.com 172.12.10.14 1719 zone remote gk-corp.xyz.com xyz.com 172.12.32.80 1719

!A couple of other zones within xyz.com. We make lots of calls

!between these departments, so we just configure these so we save

!a little time bypassing DNS lookup to find their gatekeepers. use-proxy gk-eng.xyz.com remote-zone gk-mfg.xyz.com direct use-proxy gk-eng.xyz.com remote-zone gk-corp.xyz.com direct use-proxy gk-eng.xyz.com default proxied

!We have good QoS on our local network, so we don't need proxies when

!calling between the xyz.com zones. But for all other zones, we want

!to use proxies.

zone subnet gk-eng.xyz.com 172.21.127.0/24 enable no zone subnet gk-eng.xyz.com default enable

!We will accept registrations from our local subnet as long as they

!do not specify some other gatekeeper name. We will not accept any

!registrations from any other subnet.

zone bw gk-eng.xyz.com 2000

Cisco IOS Voice, Video, and Fax Configuration Guide

VC-346

Image 58
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-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 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-307Other-gatekeeper-ip-address-Specifies the IP Configuring Redundant H.323 Zone SupportVC-308 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 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 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-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.