Cisco Systems VC-289 manual Configuring a Proxy for Inbound Calls Example, VC-361

Page 73

Configuring H.323 Gatekeepers and Proxies

H.323 Gatekeeper Configuration Examples

A priority 0 is assigned to gateway gw1 to exclude it from the gateway pool for prefix 650........ When

gateway gw2 registers with gatekeeper localgk, it is added to the gateway pool for each prefix as follows:

For gateway pool for 415......., gateway gw2 is set to priority 10.

For gateway pool for 650......., gateway gw2 is set to priority 5.

To change gateway gw2 from priority 10 for zone 415

to the default priority 5, enter the following

command:

 

 

 

 

no zone prefix localgk 415

gw-pri 10 gw2

 

 

To change both gateways gw1 and gw2 from priority 10 for zone 415

to the default priority 5, enter

the following command:

 

 

 

 

no zone prefix localgk 415

gw-pri 10 gw1 gw2

 

 

In the preceding example, the prefix 415

remains assigned to gatekeeper localgk. All gateways that

do not specify a priority level for this prefix are assigned a default priority of 5. To remove the prefix and all associated gateways and priorities from this gatekeeper, enter the following command:

no zone prefix localgk 415.......

Configuring a Proxy for Inbound Calls Example

In the following example, the local zone sj.xyz.com is configured to use a proxy for inbound calls from remote zones tokyo.xyz.com and milan.xyz.com to gateways in its local zone. The sj.xyz.com zone is also configured to use a proxy for outbound calls from gateways in its local zone to remote zones tokyo.xyz.com and milan.xyz.com.

gatekeeper

use-proxy sj.xyz.com remote-zone tokyo.xyz.com inbound-to gateway use-proxy sj.xyz.com remote-zone tokyo.xyz.com outbound-from gateway use-proxy sj.xyz.com remote-zone milan.xyz.com inbound-to gateway use-proxy sj.xyz.com remote-zone milan.xyz.com outbound-from gateway

Because the default mode disables proxy communications for all gateway calls, only the gateway call scenarios listed can use the proxy.

Configuring a Proxy for Outbound Calls Example

In the following example, the local zone sj.xyz.com uses a proxy for only those calls that are outbound from H.323 terminals in its local zone to the specified remote zone germany.xyz.com:

gatekeeper

no use-proxy sj.xyz.com default outbound-from terminal use-proxy sj.xyz.com remote-zone germany.xyz.com outbound-from

terminal

Note that any calls inbound to H.323 terminals in the local zone sj.xyz.com from the remote zone germany.xyz.com use the proxy because the default applies.

Cisco IOS Voice, Video, and Fax Configuration Guide

VC-361

Image 73
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 ModeProxies and NAT Proxy Outside the FirewallVC-300 Application-Specific Routing Quality of ServiceVC-301 VC-302 Prerequisite Tasks and RestrictionsVC-303 Configuring the GatekeeperVC-304 Starting a GatekeeperGw-prioritypriority gw-alias-Optional Use H323-gateway voip h.323-id commandVC-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-307Other-gatekeeper-ip-address-Specifies the IP Configuring Redundant H.323 Zone SupportVC-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 addressZone local or zone remote command. You can Configuring Redundant Gatekeepers for a Technology PrefixVC-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 RadiusOther-gatekeeper-ip-address -Specifies the IP Configuring E.164 Interzone RoutingVC-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 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 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 ExampleIsolating the Multimedia Network Enabling the Proxy to Forward H.323 PacketsVC-351 VC-352 PX1 ConfigurationVC-353 R1 ConfigurationVC-354 Co-Edge Proxy with Subnetting ExampleVC-355 R2 Configuration PX2 ConfigurationVC-356 VC-357 Configuring a QoS-Enforced Open Proxy Using Rsvp ExampleVC-358 VC-359 Configuring a Closed Co-Edge Proxy with ASRDefining 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 VC-362 Removing a Proxy Example Security ExampleProhibiting 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.