Cisco Systems VC-289 manual Configuring the Proxy, Configuring a Forced Disconnect on a Gatekeeper

Page 44

Configuring H.323 Gatekeepers and Proxies

H.323 Gatekeeper Configuration Task List

Configuring a Forced Disconnect on a Gatekeeper

To force a disconnect on a gatekeeper, use the following command in privileged EXEC mode:

Command

Purpose

 

 

Router# clear h323 gatekeeper call

Forces a disconnect on a specific call or on all calls currently

{all local-callID local-callID}

active on this gatekeeper.

 

The keywords and arguments are as follows:

 

all—Forces all active calls currently associated with this

 

gatekeeper to be disconnected.

 

local-callID—Forces a single active call associated with this

 

gatekeeper to be disconnected.

 

local-callID—Specifies the local call identification number

 

(CallID) that identifies the call to be disconnected.

 

 

To force a particular call to be disconnected (as opposed to all active calls on the H.323 gateway), use the local call identification number (CallID) to identify that specific call. Find the local CallID number for a specific call by using the show gatekeeper calls command; the ID number is displayed in the LocalCallID column.

Verifying a Forced Disconnect

To show the status of each ongoing call that a gatekeeper is aware of, use the show gatekeeper calls command. If you have forced a disconnect either for a particular call or for all calls associated with a particular H.323 gatekeeper, the system will not display information about those calls.

The following is sample output from the show gatekeeper calls command:

router# show gatekeeper calls

Total

number of active calls =1

 

 

 

 

 

 

Gatekeeper Call Info

 

 

 

 

 

====================

 

 

 

LocalCallID

 

Age (secs)

BW

 

 

12-3339

 

94

768 (Kbps)

 

Endpt(s): Alias

E.164Addr

CallSignalAddr

Port

RASSignalAddr

Port

src

EP: epA

 

10.0.0.11

1720

10.0.0.11

1700

dst

EP: epB2zoneB.com

 

 

 

 

src

PX: pxA

 

10.0.0.1

1720

10.0.0.11

24999

dst

PX: pxB

 

172.21.139.90

1720

172.21.139.90

24999

Configuring the Proxy

This section describes the following configuration tasks for configuring the proxy. Depending on your specific network design, either the first task or the second task is required.

Configuring a Proxy Without ASR, page 333

Configuring a Proxy with ASR, page 337

Cisco IOS Voice, Video, and Fax Configuration Guide

VC-332

Image 44
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-299VC-300 Proxy Outside the FirewallProxies and NAT VC-301 Quality of ServiceApplication-Specific Routing Prerequisite Tasks and Restrictions VC-302Configuring the Gatekeeper VC-303Starting a Gatekeeper VC-304VC-305 H323-gateway voip h.323-id commandGw-prioritypriority gw-alias-Optional Use 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-307VC-308 Configuring Redundant H.323 Zone SupportOther-gatekeeper-ip-address-Specifies the IP 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 addressVC-311 Configuring Redundant Gatekeepers for a Technology PrefixZone local or zone remote command. You can 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-320VC-321 Configuring E.164 Interzone RoutingOther-gatekeeper-ip-address -Specifies the IP 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 VC-330 Configuring Inbound or Outbound Gatekeeper Proxied AccessRemote-zone remote-zone-name -Defines a VC-331 Verifying Gatekeeper Proxied Access ConfigurationRouter# show gatekeeper zone status VC-332 Configuring the ProxyConfiguring a Forced Disconnect on a Gatekeeper VC-333 Configuring a Proxy Without ASRShow interfaces command 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-350VC-351 Enabling the Proxy to Forward H.323 PacketsIsolating the Multimedia Network PX1 Configuration VC-352R1 Configuration VC-353Co-Edge Proxy with Subnetting Example VC-354VC-355 VC-356 PX2 ConfigurationR2 Configuration Configuring a QoS-Enforced Open Proxy Using Rsvp Example VC-357VC-358 Configuring a Closed Co-Edge Proxy with ASR VC-359VC-360 Defining Multiple Zones ExampleDefining One Zone for Multiple Gateways Example VC-361 Configuring a Proxy for Inbound Calls ExampleConfiguring a Proxy for Outbound Calls Example Removing a Proxy Example Security Example VC-362VC-363 Gktmp and RAS Messages ExampleProhibiting Proxy Use for Inbound Calls Example 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.