Cisco Systems VC-289 manual Configuring Static Nodes, VC-313

Page 25

Configuring H.323 Gatekeepers and Proxies

H.323 Gatekeeper Configuration Task List

Configuring Static Nodes

In some cases, the registration information is not accessible for a terminal or endpoint from any gatekeeper. This inaccessible registration information may be because the endpoint does not use RAS, is in an area where no gatekeeper exists, or is in a zone where the gatekeeper addressing is unavailable either through DNS or through configuration.

These endpoints can still be accessed via a gatekeeper by entering them as static nodes. To enter the endpoints as static nodes, obtain the address of the endpoint and then use the following commands beginning in global configuration mode:

 

Command

Purpose

Step 1

 

 

Router(config)# gatekeeper

Enters gatekeeper configuration mode.

Step 2

 

 

Router(config-gk)# zone local gatekeeper-name

Specifies a zone controlled by a gatekeeper.

 

domain-name [ras-IP-address]

For an explanation of the arguments, see Step 2 of the

 

 

 

 

configuration task table in the “Starting a

 

 

Gatekeeper” section on page 304.

Step 3

 

 

Router(config-gk)# alias static ip-signalling-addr

Creates a static entry in the local alias table for each

 

[port] gkid gatekeeper-name [ras ip-ras-addr port]

E.164 address. Repeat this step for each E.164

 

[terminal mcu gateway {h320 h323-proxy voip}]

address you want to add for the endpoint.

 

[e164 e164-address] [h323id h323-id]

 

 

 

 

The keywords and arguments are as follows:

 

 

• ip-signalling-addr—Specifies the IP address of

 

 

the H.323 node, used as the address to signal

 

 

when establishing a call.

 

 

• port—(Optional) Specifies the port number other

 

 

than the endpoint call-signaling well-known port

 

 

number (1720).

 

 

• gkid gatekeeper-name—Specifies the name of

 

 

the local gatekeeper of whose zone this node is a

 

 

member.

 

 

• ras ip-ras-addr—(Optional) Specifies the node

 

 

remote access server (RAS) signaling address. If

 

 

omitted, the ip-signalling-addrparameter is used

 

 

in conjunction with the RAS well-known port.

 

 

• port—(Optional) Specifies a port number other

 

 

than the RAS well-known port number (1719).

 

 

• terminal—(Optional) Indicates that the alias

 

 

refers to a terminal.

 

 

• mcu—(Optional) Indicates that the alias refers to

 

 

a multiple control unit (MCU).

 

 

• gateway—(Optional) Indicates that the alias

 

 

refers to a gateway.

 

 

• h320—(Optional) Indicates that the alias refers

 

 

to an H.320 node.h320—(Optional) Indicates

 

 

that the alias refers to an H.320 node.

 

 

 

Cisco IOS Voice, Video, and Fax Configuration Guide

VC-313

Page 24 Page 26
Image 25
Page 24 Page 26
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.
Top Page Image Contents