Cisco Systems VC-289 manual VC-295

Page 7

Configuring H.323 Gatekeepers and Proxies

H.323 Gatekeeper Features

To enable the gatekeeper to select the appropriate hop-off gateway, use the gw-type-prefixcommand to configure technology or gateway-type prefixes. Select technology prefixes to denote different types or classes of gateways. The gateways are then configured to register with their gatekeepers using these technology prefixes.

For example, voice gateways might register with technology prefix 1#, and H.320 gateways might register with technology prefix 2#. If there are several gateways of the same type, configure them to register with the same prefix type. By having them register with the same prefix type, the gatekeeper treats the gateways as a pool out of which a random selection is made whenever a call for that prefix type arrives. If a gateway can serve more than one type of hop-off technology, it can register more than one prefix type with the gatekeeper.

Callers will need to know the technology prefixes that are defined. The callers will need to know the type of device they are trying to reach and will need to prepend the appropriate technology prefix to the destination address to indicate the type of gateway needed to reach the destination.

For example, callers might request 1#2125551111 if they know that address 2125551111 is for a telephone and that the technology prefix for voice gateways is 1#. The voice gateway is configured with a dial peer (using the dial-peercommand) so that when the gateway receives the call for 1#2125551111, it strips off the technology prefix 1# and bridges the next leg of the call to the telephone at 2125551111.

In cases in which the call scenario is as shown in Figure 57, voice-gw1 can be configured to prepend the voice technology prefix 1# so that the use of technology prefixes is completely transparent to the caller.

Figure 57

Call Scenario

 

 

PSTN

 

 

H.323 network

 

PSTN

 

 

Telephone

voice-gw1

voice-gw2

Telephone

13098

Additionally, in using the gw-type-prefixcommand, a particular gateway-type prefix can be defined as the default gateway type to be used for addresses that cannot be resolved. It also forces a technology prefix to always hop off in a particular zone.

If the majority of calls hop off on a particular type of gateway, the gatekeeper can be configured to use that type of gateway as the default type so that callers no longer have to prepend a technology prefix on the address. For example, if voice gateways are mostly used in a network, and all voice gateways have been configured to register with technology prefix 1#, the gatekeeper can be configured to use 1# gateways as the default technology if the following command is entered:

my-gatekeeper(config-gk)#gw-type-prefix 1# default-technology

Now a caller no longer needs to prepend 1# to use a voice gateway. Any address that does not contain an explicit technology prefix will be routed to one of the voice gateways that registered with 1#.

With this default technology definition, a caller could ask the gatekeeper for admission to 2125551111. If the local gatekeeper does not recognize the zone prefix as belonging to any remote zone, it will route the call to one of its local (1#) voice gateways so that the call hops off locally. However, if it knows that gk-ny handles the 212 area code, it can send a location request for 2125551111 to gk-ny. This requires that gk-ny also be configured with some default gateway type prefix and that its voice gateways be registered with that prefix type.

Cisco IOS Voice, Video, and Fax Configuration Guide

VC-295

Image 7
Contents VC-289 Configuring H.323 Gatekeepers and ProxiesVC-290 Principal Multimedia Conference Manager FunctionsGateway Support for Alternate Gatekeepers Zone and Subnet ConfigurationRedundant H.323 Zone Support Gatekeeper Multiple Zone SupportVC-292 Technology PrefixesTerminal Name Registration Interzone CommunicationRadius and TACACS+ Accounting via Radius and TACACS+VC-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 Subnet-address /bits-in-mask Zone subnet commandMask-addressenable Subnet local-gatekeeper-nameVC-307 Configuring Intergatekeeper CommunicationServer-address2...server-address6 -Optional Ras gk-id@host port priorityOther-gatekeeper-ip-address-Specifies the IP Configuring Redundant H.323 Zone SupportVC-308 VC-309 Configuring Local and Remote GatekeepersOther-gatekeeper-ip-address -IP address Configuring Redundant Gatekeepers for a Zone PrefixVerifying Zone Prefix Redundancy Other-gatekeeper-name -Name of the remoteZone 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 VC-337 Configuring a Proxy with ASRTunnel Vg-anylanVC-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 ExampleVC-347 Redundant Gatekeepers for a Zone Prefix ExampleRedundant Gatekeepers for a Technology Prefix Example Interzone Routing ExampleVC-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.