![]() |
SIP Configuration Guide, Cisco IOS Release 15M&T
|
||||||||||||
Support for Resource Availability Indication Over SIP Trunks
![]() |
|||||||||||||
|
Contents
Support for Resource Availability Indication Over SIP TrunksLast Updated: December 30, 2012
The Support for Monitoring Utilization of Critical Resources on Gateway Router, Cisco UBE and Cisco UCME and Reporting Over SIP Trunks feature implements monitoring of resource utilization and reporting functionality over the Session Initiation Protocol (SIP) trunk on the Cisco IOS gateway, Cisco Unified Border Element (Cisco UBE) and Cisco Unified Communications Manager Express (Cisco UCME). This feature supports monitoring of CPU, memory, Digital Signaling Processor (DSP) and the DS0 port on the Cisco IOS gateway and reporting the status to external devices using SIP OPTION mechanism.
Finding Feature InformationYour software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and 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 module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Restrictions for the Support for Resource Availability Indication Over SIP Trunks Feature
Information About the Support for Resource Availability Indication Over SIP Trunks Feature
Overview of the Support for Resource Availablity Indication Over SIP TrunksThe Support for Resource Available Indication Over SIP Trunks feature enables monitoring of CPU, memory, DSP, and DS0 resources on the Cisco IOS gateway and reporting of the status to external device using the gateway resources. The reporting from the gateway takes place either based on a configured time interval or on the configured threshold crossover. The gateway also supports extracting the gateway resource information from the external entity either on periodic or nonperiodic basis. The monitoring and reporting of resources is achieved by SIP OPTIONS using x-cisco-rai headers. The highlights of monitoring and reporting of resources are as follows:
Benefits of the Support for Resource Availablity Indication Over SIP Trunks
Overview on Monitoring and Reporting of Gateway ResourcesThe gateway uses the x-cisco-rai header in the OPTIONS message to report the resource utilization to the routing or monitoring entities. ABNF Format for ReportingThe Augmented Backus-Naur Form (ABNF) format of reporting is used to report the status of the report utilization to the monitoring entity. The Cisco IOS gateway may not use all the fields. Provision is also made for adding new resource types and new parameters for the resources. The following is the format of the header used for reporting:
x-cisco-rai = ("x-cisco-rai") HCOLON resource-param *(COMMA resource-param)
resource-param = resource-name-param SEMI resource-params *(SEMI resource-params)
resource-name-param = "SYSTEM" / "CPU" / "MEM" / "DS0" / "DSP" / token
resource-params = resource-status-param/resource-total-param/resource-available-param/resource-used-param/resource-extension
resource-status-param = "almost-out-of-resource" EQUAL ("true" / "false")
resource-total-param="total" EQUAL 1*(DIGIT) ["%" / "MB" / token]
resource-available-param = "available" EQUAL 1*(DIGIT) ["%" / "MB" / token]
resource-used-param = "used" EQUAL 1*3DIGIT "%"
resource-extension=generic-param
Semantics of the HeaderThe rules for constructing the header are as follows:
Following are the examples of the reporting format in the SIP OPTIONS message: Example 1: Cisco IOS Gateway Sending Resource Header when the Resources are Availablex-cisco-rai : SYSTEM; almost-out-of-resource=false x-cisco-rai : CPU; almost-out-of-resource=false;total=100%;available=60% x-cisco-rai : MEM; almost-out-of-resource=false;total=100%;available=40% x-cisco-rai : DSO; almost-out-of-resource=false;total=64;available=20 x-cisco-rai : DSP; almost-out-of-resource=false;total=64;available=20 Example 2: Cisco IOS Gateway Sending Resource Header when CPU Resources are Not Availablex-cisco-rai : SYSTEM; almost-out-of-resource=true x-cisco-rai : CPU; almost-out-of-resource=true;total=100%;available=20% x-cisco-rai : MEM; almost-out-of-resource=false;total=100%;available=40% x-cisco-rai : DSO; almost-out-of-resource=false;total=64;available=20 x-cisco-rai : DSP; almost-out-of-resource=false;total=64;available=20 Modes of ReportingThere are two modes of reporting:
Gateway Triggered Reporting to Routing Monitoring EntityIn gateway triggered reporting, the gateway sends the resource utilization information in an OPTION message to the external entity. The gateway includes a supported header with the option tag x-cisco-rai to indicate that this OPTION message carries the resource availability information. The trigger to send the OPTION message can be either periodic, or threshold based, or both. Periodic ReportingIn the periodic reporting mode, reporting is triggered based on a preconfigured timer value. This type of reporting is used to collect information on a resource usage. Threshold Triggered ReportingIn the threshold triggered reporting mode, reporting is triggered depending on the threshold levels configured for the resources that are being monitored. This mode of reporting is used to inform the external entity of the availability or nonavailability of the gateway to service further call requests from the external entity. Threshold triggered reporting is disabled by default. Routing Monitoring Entity Triggered ReportingIn routing or monitor triggered reporting, the external entity can extract the resource information from the gateway using the SIP OPTIONS message. The gateway expects the x-cisco-rai tag in either the require: or supported: header fields for an incoming OPTIONS message. The presence of the x-cisco-rai tag in any one of the header fields informs the gateway that this option is to retrieve the gateway resource information. Reporting Mechanism over SIP TrunkThe monitoring and reporting of gateway resources to an external entity is achieved by SIP OPTIONS using x-cisco-rai headers. The sample OPTIONS message format is as provided below. Inbound OPTIONS MessageThe following is a sample format of the incoming OPTIONS message and the corresponding response from the Cisco IOS gateway for resource statistics request: Received:OPTIONS sip:9.13.38.162:5060 SIP/2.0Via: SIP/2.0/UDP 9.13.40.83:5060;branch=z9hG4bK-21983-1-0From: <sip:9.13.40.83:5060>;tag=1To: sut <sip:service@9.13.38.162:5060>Call-ID: 1-21983@9.13.40.83CSeq: 1 OPTIONSContact: sip:sipp@9.13.40.83:5060Max-Forwards: 70Subject: Performance TestSupported: sec-agree, precondition Require: x-cisco-rai Content-Type: application/sdpContent-Length: 0 Outbound OPTIONS MessageThe following is a sample format of the OPTIONS message that is sent out from the Cisco IOS gateway to the external entity with resource statistics information in it: Sent:OPTIONS sip:9.13.38.163:5060 SIP/2.0 Via: SIP/2.0/UDP 9.13.38.162:5060;branch=z9hG4bKE211D From: <sip:9.13.38.162>;tag=1005B0-1CB To: <sip:9.13.38.163> Date: Wed, 16 Dec 2009 05:53:35 GMT Call-ID: 2EE072F6-E93E11DE-801BBA85-BFCDE3D6@9.13.38.162 User-Agent: Cisco-SIPGateway/IOS-12.x Max-Forwards: 70 CSeq: 101 OPTIONS Contact: <sip:9.13.38.162:5060> X-cisco-rai: SYSTEM ; almost-out-of-resource=true X-cisco-rai: CPU ; almost-out-of-resource=false;available=99%;total=100%;used=1% X-cisco-rai: DS0 ; almost-out-of-resource=false;available=23;total=23;used=0% X-cisco-rai: DSP ; almost-out-of-resource=false;available=96;total=96;used=0% X-cisco-rai: MEM ; almost-out-of-resource=true;available=51%;total=100%;used=49% Supported: x-cisco-rai Content-Length: 0 How to Configure the Support for Resource Availability Indication Over SIP Trunks FeatureConfiguring Resource Groups and Resource Monitoring ParametersSUMMARY STEPS
DETAILED STEPS Configuring SIP RAI MechanismThis task enables the router to extract the details of the SIP along with the index of the resource group that needs to be monitored. DETAILED STEPS Configuration Examples for the Support for Resource Availability Indication Over SIP Trunks Feature
Example Configuring Resource Groups and Resource Monitoring ParametersThe following example shows how to configure the resource group 1 to monitor CPU, DS0, DSP, and memory resources: voice class resource-group 1 resource cpu 1-min-avg threshold high 50 low 30 resource ds0 threshold high 50 low 30 resource dsp threshold high 50 low 30 resource memory total-mem threshold high 50 low 30 periodic-report interval 30 Example Configuring SIP RAI Mechanismsip-ua rai target ipv4:9.13.40.83 resource-group 1 transport udp rai target dns:whitesmoke resource-group 2 transport tcp rai target ipv6:[2217:10:10:10:10:10:10:2] resource-group 3 transport tcp rai target dns:butterfly resource-group 4 transport tcp tls scheme sips rai target ipv4:10.13.40.84 resource-group 5 transport tcp rai target ipv4:10.13.40.83 resource-group 1 Additional ReferencesRelated DocumentsMIBsTechnical Assistance
Feature Information for the Support for Resource Availability Indication Over SIP TrunksThe 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 www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R) 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. © 2012 Cisco Systems, Inc. All rights reserved.
|
||||||||||||
|
|