![]() |
IP SLAs Configuration Guide, Cisco IOS Release 12.4T
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Configuring Gatekeeper Registration Delay Operations for VoIP
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Contents
Configuring VoIP Gatekeeper Registration Delay OperationsLast Updated: March 22, 2011
This document describes how to configure an Cisco IOS IP Service Level Agreements (SLAs) Voice over IP (VoIP) gatekeeper registration delay operation to determine the average, median, or aggregated response time (delay) of registration attempts from a VoIP gateway to a VoIP gatekeeper device. To measure VoIP gatekeeper registration response time, the gatekeeper registration delay operation functions by sending a lightweight Registration Request (RRQ) from an H.323 gateway (GW) to an H.323 gatekeeper (GK), and recording the amount of time taken to receive the Registration Confirmation (RCF) back from the gatekeeper.
Finding Feature InformationYour software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required. Restrictions for IP SLAs VoIP Gatekeeper Registration Delay OperationsYou cannot configure the IP SLAs VoIP gatekeeper registration delay operation if the gatekeeper has already been registered with the gateway. Information About IP SLAs VoIP Gatekeeper Registration Delay OperationsH.323 Gatekeepers and GatewaysH.232 is the ITU-T protocol standard used for managing and facilitating packetized voice and video over local-area networks (LANs, particularly intranets) and over the Internet. H.323 consists of several component standards; see the âGlossaryâ section of this chapter for details on these standardized protocols. H.323 is considered an âumbrella protocolâ because it defines all aspects of call transmission, from call establishment to capabilities exchange to network resource availability. H.323 defines Registration, Admission, and Status (RAS) protocols for call routing, H.225 protocols for call setup, and H.245 protocols for capabilities exchange. The IP SLAs VoIP Gatekeeper Registration Delay Monitoring feature focuses on the function of the call control H.323 stack. For an in-depth discussion of H.323, including gatekeeper and gateway functionality, see the âH.323 Applicationsâ chapter of the Cisco IOS Voice, Video, and Fax Configuration Guide. Gateway-to-Gatekeeper Registration Delay Time MonitoringThe IP SLAs VoIP gatekeeper registration delay operation provides statistical data on the amount of time taken to register a gateway to a gatekeeper. IP SLAs was designed to gather information over time, at intervals you specify, so that statistics can be provided on key metrics often used in Service Level Agreements (SLAs). Aggregated totals, median, or average data can be viewed using the Cisco IOS command-line interface (CLI) on the device running IP SLAs, or retrieved from the device by external applications using SNMP. Cisco IOS IP SLAs also provides notification options based on performance thresholds and reaction triggering. These notification options allow for proactive monitoring in an environment where IT departments can be alerted to potential network problems, rather than having to manually examine data. This operation will measure time from when the RRQ message is sent and when RCF message is received. A timeout may be required if a response is not received in a certain timeframe. How to Configure IP SLAs VoIP Gatekeeper Registration Delay Operations
Configuring the VoIP H.323 GatewaySUMMARY STEPS
DETAILED STEPS ExampleThe following example shows sample output from the show gateway command if the gateway (named GW3) is registered to a gatekeeper (named slagk):
Router# show gateway
H.323 ITU-T Version: 4.0 H323 Stack Version: 0.1
H.323 service is up
Gateway GW3 is registered to Gatekeeper slagk
Alias list (CLI configured)
E164-ID 2073418
E164-ID 5251212
H323-ID GW3
Alias list (last RCF)
E164-ID 2073418
E164-ID 5251212
H323-ID GW3
H323 resource thresholding is Disabled
The following example shows sample output for the show gateway command if the gateway is not registered to a gatekeeper:
Router# show gateway
Gateway gw3 is not registered to any gatekeeper
Alias list (CLI configured)
E164-ID 2073418
E164-ID 5251212
H323-ID gw3/ww
Alias list (last RCF)
H323 resource thresholding is Disabled
Use theshow gatekeeper endpoint command to verify the endpointâs registration status to the gatekeeper. The following example shows the common output of this command if an endpoint is registered:
Router# show gatekeeper endpoint
GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags
-------------- ----- ------------- ---- --------- ---- -----
172.16.13.35 1720 172.16.13.35 50890 gk VOIP-GW
E164-ID: 2073418
E164-ID: 5251212
H323-ID: gw3
Total number of active registrations = 1
The following example shows the common output of the show gatekeeper endpoint command if an endpoint is not registered:
Router# show gatekeeper endpoint
GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags
-------------- ----- ------------- ---- --------- ---- -----
Total number of active registrations = 0
The following configuration example shows a properly configured gateway: gateway interface Ethernet1/1 ip address 172.29.129.123 255.255.255.0 h323-gateway voip interface h323-gateway voip id zone1 ipaddr 172.29.129.124 1719 h323-gateway voip id saagk ipaddr 172.29.129.28 1719 h323-gateway voip h323-id GWZ Troubleshooting TipsTo troubleshoot registration issues, see the Troubleshooting Gatekeeper Registration Issues technical assistance document. Configuring and Scheduling a VoIP Gatekeeper Registration Delay Operation
SUMMARY STEPS
DETAILED STEPS
Troubleshooting Tips
What to Do NextTo add proactive threshold conditions and reactive triggering for generating traps, or for starting another operation, to an IP SLAs operation, see the "Configuring Proactive Threshold Monitoring" section. To view and interpret the results of an IP SLAs operation use the show ip sla statistics command. Checking the output for fields that correspond to criteria in your service level agreement will help you determine whether the service metrics are acceptable. Configuration Examples for IP SLAs VoIP Gatekeeper Registration Delay OperationsExample Configuring the IP SLAs VoIP gatekeeper registration delay operationIn the following example, a VoIP gatekeeper registration delay operation is configured and scheduled to start immediately. This example assumes the gateway to gatekeeper relationship has already been configured. Router# configure terminal Router(config)# ip sla 1 Router(config-ip-sla)# voip delay gatekeeper-registration Router(config-ip-sla-voip)# exit Router(config)# ip sla schedule 1 start-time now life forever Additional ReferencesRelated DocumentsMIBsTechnical Assistance
Feature Information for the IP SLAs VoIP Gatekeeper Registration Delay OperationThe following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
GlossaryGatekeepers --Network devices that help to facilitate and control H.323-based voice and video communications across networks. Gatekeepers are responsible for providing address translation between LAN aliases and IP addresses, call control and routing services to H.323 endpoints, system management, and security policies. These services provided by the gatekeeper in communicating between H.323 endpoints are defined in RAS. Gateways --Network devices that provide translation between circuit-switched networks (particularly, H.320 ISDN) and packet-based networks (for example, H.323 LANs), allowing endpoints in networks with different transmission formats, codecs, and protocols to communicate. H.225.0 --Protocol standard that defines the establishment and disconnection of H.323 calls. H.225.0 RAS --H.225.0 Registration/Admission/Status. Standard that facilitates communication between H.323 gateways (endpoints) and H.323 gatekeepers. H.235 --Protocol standard that defines security solutions for H.323 protocols (Q.931, H.245, RAS, Streams). H.235 was formerly called H.SECURE. H.245 --Protocol standard that defines connection management and negotiation capabilities between H.323 devices on the network once the call is established by Q.931. H.323 --An ITU protocol standard for the transmission of real-time audio (Voice/VoIP), video (for example, videoconferencing), and data information over packet switching-based networks. Such networks include IP-based (including the Internet) networks, Internet packet exchange-based local-area networks (LANs), enterprise networks and metropolitan and wide-area networks (WANs). H.323 can also be applied to multipoint multimedia communications. H.323 defines a distributed architecture for IP telephony applications, including multimedia, video conferencing, video over the Internet, and VoIP. Q.931 --Protocol standard that defines the establishment and disconnection of H.323 calls. RTP/RTCP --Real-time Protocol/Real-Time Control Protocol serves as the standardized means for transmitting and receiving audio and video streams across the network once the call is established. VoIP --Voice or Video over Internet Protocol. Sometimes used to refer to all IP telephony applications. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|