draft-ietf-sip-mib-00.txt   draft-ietf-sip-mib-01.txt 
Internet Engineering Task Force K. Lingle, SIP Working Group K. Lingle,
Cisco Systems, Inc., Internet Draft Cisco Systems, Inc.,
J. Maeng, draft-ietf-sip-mib-01.txt J. Maeng,
VTEL Corp., July 2000 VTEL Corp.,
D. Walker Expires: January 2001 D. Walker,
SS8 Networks, Inc. SS8 Networks, Inc.
Internet Draft
Document: draft-ietf-sip-mib-00.txt March 6, 2000
Expires: September, 2000
Management Information Base Management Information Base
for Session Invitation Protocol for Session Initiation Protocol
draft-ietf-sip-mib-00.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are all provisions of Section 10 of RFC 2026.
working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are working documents of the Internet Engineering
months and may be updated, replaced, or obsoleted by other documents Task Force (IETF), its areas, and its working groups. Note that
at any time. It is inappropriate to use Internet- Drafts as other groups may also distribute working documents as Internet-
Drafts. Internet-Drafts are draft documents valid for a maximum of
six months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-
Draft Shadow Directories can be accessed at
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This particular draft is being developed in the Session Initiation This particular draft is being developed in the Session Initiation
Protocol Working Group. Discussion of it therefore belongs on that Protocol Working Group. Discussion of it therefore belongs on that
list. The charter for Session Initiation Protocol may be found at list. The charter for Session Initiation Protocol may be found at
http://www.ietf.org/html.charters/sip-charter.html http://www.ietf.org/html.charters/sip-charter.html
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that are used In particular, it describes a set of managed objects that are used
to manage Session Initiation Protocol(SIP) [17] devices, which to manage Session Initiation Protocol(SIP) [17] devices, which
include User Agent, Proxy server, Redirect server and Registrar. include User Agents, Proxy servers, Redirect servers and Registrars.
Table of Contents
1.Introduction .......................................................2
2.The SNMP Management Framework ......................................2
3.Overview ...........................................................3
4.Structure of SIP MIB ...............................................3
4.1 Textual Conventions ..............................................3
4.2 Relationship to Other MIB ........................................4
5.Definitions ........................................................4
6.Security Considerations ...........................................67
7.Intellectual Property .............................................67
8.Full Copyright Statement ..........................................68
9.References ........................................................68
10. Authors' Addresses ..............................................69
1. 1. Introduction
Introduction
This memo defines a portion of the Management Information Base This memo defines a portion of the Management Information Base
(MIB)for use with network management protocols in the Internet (MIB)for use with network management protocols in the Internet
community. In particular, it describes a set of managed objects that community. In particular, it describes a set of managed objects that
are used to schedule management operations periodically or at are used to schedule management operations periodically or at
specified dates and times. specified dates and times.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [16]. document are to be interpreted as described in RFC 2119 [16].
2. Lingle/Maeng/Walker 1
The SNMP Management Framework
2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2271 [1]. - An overall architecture, described in RFC 2271 [1].
o Mechanisms for describing and naming objects and events for - Mechanisms for describing and naming objects and events for the
the purpose of management. The first version of this purpose of management. The first version of this Structure of
Structure of Management Information (SMI) is called SMIv1 and Management Information (SMI) is called SMIv1 and described in
described in STD16, RFC 1155 [2], STD 16, RFC 1212 [3] and STD16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
RFC 1215 [4]. The second version, called SMIv2, is described second version, called SMIv2, is described in STD 58, RFC 2578
in STD 58, RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. [5], RFC 2579 [6] and RFC 2580 [7].
o Message protocols for transferring management information. - Message protocols for transferring management information. The
The first version of the SNMP message protocol is called first version of the SNMP message protocol is called SNMPv1 and
SNMPv1 and described in RFC 1157 [8]. A second version of the described in RFC 1157 [8]. A second version of the SNMP message
SNMP message protocol, which is not an Internet standards protocol, which is not an Internet standards track protocol, is
track protocol, is called SNMPv2c and described in RFC 1901 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
[9] and RFC 1906 [10]. The third version of the message The third version of the message protocol is called SNMPv3 and
protocol is called SNMPv3 and described in RFC 2272 [11] and described in RFC 2272 [11] and RFC 2274 [12].
RFC 2274 [12].
o Protocol operations for accessing management information. The - Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats first set of protocol operations and associated PDU formats is
is described in STD 15, RFC 1157 [8]. A second set of described in STD 15, RFC 1157 [8]. A second set of protocol
protocol operations and associated PDU formats is described operations and associated PDU formats is described in RFC 1905
in RFC 1905 13]. 13].
o A set of fundamental applications described in RFC 2273 [14] - A set of fundamental applications described in RFC 2273 [14] and
and the view-based access control mechanism described in RFC the view-based access control mechanism described in RFC 2275
2275 [15]. [15].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
skipping to change at page 3, line 4 skipping to change at line 99
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of SMIv1 during the translation process. However, this loss of
machinereadable information is not considered to change the machinereadable information is not considered to change the
semantics of the MIB. semantics of the MIB.
3. 3. Overview
Overview
The Session Initiation Protocol (SIP) [17] is an application-layer The Session Initiation Protocol (SIP) [17] is an application-layer
control protocol that can establish, modify and terminate multimedia control protocol that can establish, modify and terminate multimedia
sessions or calls. This mib provides some managed objects for SIP sessions or calls. This MIB provides some managed objects for SIP
devices defined in RFC 2543 - User Agent, Proxy server, Redirect devices defined in RFC 2543 - User Agent, Proxy server, Redirect
Lingle/Maeng/Walker 2
server and Registrar. It is provided as a base for the work within server and Registrar. It is provided as a base for the work within
the working group to define a mib. the working group to define a MIB.
This MIB is intended to provide management of the basic devices in This MIB is intended to provide management of the basic devices in
SIP. It provides for monitoring of status and protocol statistics, SIP. It provides for monitoring of status and protocol statistics,
as well as for configuration of basic SIP devices. as well as for configuration of SIP devices.
4. 4. Structure of SIP MIB
Structure of SIP MIB
Objects in this MIB are arranged into groups. Each group is This memo specifies six MIB modules. They are SIP-MIB-SMI, SIP-
organized as a set of related objects. The overall structure is COMMON-MIB, SIP-REGISTRAR-MIB, SIP-SERVER-MIB, SIP-UA-MIB and SIP-
described below. TC. SIP-MIB-SMI indicates the root OID of SIP MIB modules. SIP-
COMMON-MIB contains common objects used in all the SIP entities such
as Registrars, Proxy Servers, Redirect Servers and User Agents. SIP-
SIP-REGISTRAR-MIB, SIP-SERVER-MIB and SIP-UA-MIB includes objects
defined for Registrars, Proxy and Redirect servers, and User Agents,
respectively. SIP-TC defines the textual conventions used through
out MIB modules.
-- Common to all the SIP devices The MIB modules contain the following groups of objects:
-- SIP-COMMON-MIB: Common to all the SIP devices
sipCommonConfigGroup sipCommonConfigGroup
sipCommonStatsGroup sipCommonStatsGroup
sipCommonNotifGroup
-- Groups of objects for User Agent -- SIP-REGISTRAR-MIB: Groups of objects for Registrars
sipUAConfigGroup sipRegistrarConfigGroup
sipUAStatsGroup sipRegistrarStatsGroup
-- Groups of objects for Proxy/Redirect server configuration
sipNetServerConfigGroup
-- Groups of objects for Proxy server -- SIP-SERVER-MIB: Groups of objects for proxy and Redirect Servers
sipServerConfigGroup
sipServerStatsGroup
sipProxyConfigGroup sipProxyConfigGroup
sipProxyStatsGroup sipProxyStatsGroup
-- Groups of objects for Registrar -- SIP-UA-MIB: Groups of objects for User Agents
sipRegistrarConfigGroup sipUAConfigGroup
sipRegistrarStatsGroup sipUAStatsGroup
-- Groups of objects for Redirect server (A place holder - not
defined at this time)
-- sipRedirectConfigGroup
-- sipRedirectStatsGroup
-- Notification Groups of objects for UA, Proxy, Redirect and It is required to implement SIP-COMMON-MIB together with its own MIB
Registrar (A place holder - not defined at this time) module in Registrars, Proxy Servers, Redirect Servers and User
-- sipUANotificationGroup Agents. For instance, a SIP Registrar will need four MIB modules,
-- sipProxyNotificationGroup SIP-MIB-SMI, SIP-COMMON-MIB, SIP-REGISTRAR-MIB, and SIP-TC in order
-- sipRedirectNotificationGroup to provide a complete set of objects . If a device has more than one
-- sipRegistrarNotificationGroup sip entity or multiple instances of the same entity, it may
implement multiple SIP modules. Section 4.2 describes handling of
multiple instances in detail.
4.1 Textual Conventions 4.1 Textual Conventions
The datatypes SipServerActions is used as textual conventions in The data type SipServerActions is used as textual conventions in
this document. These textual conventions have NO effect on either this document. These textual conventions have NO effect on either
the syntax nor the semantics of any managed object. Objects defined the syntax nor the semantics of any managed object. Objects defined
Lingle/Maeng/Walker 3
using these conventions are always encoded by means of the rules using these conventions are always encoded by means of the rules
that define their primitive type. Hence, no changes to the SMI or that define their primitive type. Hence, no changes to the SMI or
the SNMP are necessary to accommodate these textual conventions the SNMP are necessary to accommodate these textual conventions
which are adopted merely for the convenience of readers. which are adopted merely for the convenience of readers.
4.2 Relationship to Other MIB 4.2 Relationship to Other MIB
If there is a need for using a single agent which supports multiple There is a requirement to be able to support multiple instances of
instances of sipMIB, one may use the Entity MIB [19]. It in no way SIP MIB modules in the context of a single system having a single
alters the information required in the sipMib. SNMP agent. For example, a device acting as a SIP Proxy Server may
also contain a Registrar function. It is also possible to have
multiple instances of a particular type of SIP entity running on the
same system. For example, there may be Registrars for different
domains with completely different behaviors.
The Entity MIB introduces a standardized way of presenting the While there are separate MIB modules defined for SIP Redirect &
components of complex systems that may contain multiple racks, Proxy Servers, for Registrars, and for User Agents, there is also a
shelves,line cards, and/or ports. The Entity MIB's main goal is to "common" MIB module expected to be supported by every SIP entity.
present these system components, their containment relationship, and So a SIP Proxy Server must support the SIP-SERVER-MIB and SIP-
mapping information with other MIBs. COMMON-MIB modules. Likewise, the Registrar must support the SIP-
REGISTRAR and SIP-COMMON-MIB modules. Here we have the requirement
for supporting multiple instances of a particular MIB module in one
system.
5. This problem is solved by using the framework provided by RFC 2788
Definitions [19]. The Network Services Monitoring MIB applTable will be
populated with entries corresponding to each SIP entity in the
system. Each entity will then have an applIndex associated with it.
That applIndex is used throughout the SIP MIB modules' tables so
that each SIP entity can have its own set (instances) of managed
objects defined in those MIBs.
SIP-MIB DEFINITIONS ::= BEGIN A quick example will illustrate how it would conceptually appear in
a running system. Take the example above of a Proxy Server co-
located with a Registrar.
NETWORK-SERVICES-MIB applTable would be populated something like the
following:
applIndex | applName | applDescription
----------+-----------------+------------------------------
1 | "sip_proxy" | "ACME Inc. SIP Proxy Ver 1.0"
----------+-----------------+------------------------------
2 | "registrar" | "ACME Inc. Registrar Ver 1.3"
----------+-----------------+------------------------------
Note: There are a number of other objects in the applTable. They
are not included for the sake of brevity and for the fact that they
do not enhance the concept being presented.
The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for
the proxy (applIndex=1) and one for the registrar (applIndex=2).
The SIP-SERVER-MIB and SIP-REGISTRAR-MIB tables would, however,
Lingle/Maeng/Walker 4
only be populated with one row indexed by applIndex=1 and
applIndex=2 respectively.
SIP-COMMON-MIB sipCommonCfgTable might be populated as:
applIndex | sipProtocolVersion | sipServiceOperStatus | ...
----------+--------------------+----------------------+----
1 | "SIP/2.0" | up(1) |
----------+--------------------+----------------------+----
2 | "SIP/2.0" | restarting(6) |
----------+--------------------+----------------------+----
while the SIP-SERVER-MIB sipProxyCfgTable is populated as:
applIndex | sipRequestMaxExpires | sipProxyStateful | ...
----------+----------------------+------------------+----
1 | 3600 | false |
----------+----------------------+------------------+----
and the SIP-REGISTRAR-MIB sipRegUserTable is populated as:
applIndex | sipUserIndex | sipUserUri | ...
----------+--------------+--------------------------+----
2 | 1 | drwalker@ss8networks.com |
----------+--------------+--------------------------+----
2 | 2 | joon_maeng@vtel.com |
----------+--------------+--------------------------+----
2 | 3 | klingle@cisco.com |
----------+--------------+--------------------------+----
The NETWORK-SERVICES-MIB assocTable is not considered a requirement
for SIP systems. It is not a mandatory group for NETWORK-SERVICES-
MIB compliance.
5. Definitions
5.1. SIP Structure Management Information
SIP-MIB-SMI DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
mib-2
FROM SNMPv2-SMI;
sipMIB MODULE-IDENTITY
LAST-UPDATED "200007080000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO
"SIP MIB Team email: sip-mib@egroups.com
Co-editor Kevin Lingle
Cisco Systems, Inc.
postal: 7025 Kit Creek Road
Lingle/Maeng/Walker 5
P.O. Box 14987
Research Triangle Park, NC 27709
USA
email: klingle@cisco.com
phone: +1-919-392-2029
Co-editor Joon Maeng
VTEL Corporation
postal: 108 Wild Basin Rd.
Austin, TX 78746
USA
email: joon_maeng@vtel.com
phone: +1-512-437-4567
Co-editor Dave Walker
SS8 Networks, Inc.
postal: 80 Hines Road
Kanata, ON K2K 2T8
Canada
email: drwalker@ss8networks.com
phone: +1 613 592 2100"
DESCRIPTION
"Initial version of Session Initiation Protocol (SIP)
MIB module that defines base OID for all other
SIP-related MIB Modules."
::= { mib-2 9998 } -- to be assigned by IANA
END
5.2. SIP Textual Conventions
SIP-TC DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC
sipMIB
FROM SIP-MIB-SMI;
sipTC MODULE-IDENTITY
LAST-UPDATED "200007080000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO
"SIP MIB Team email: sip-mib@egroups.com
Co-editor Kevin Lingle
Cisco Systems, Inc.
postal: 7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709
Lingle/Maeng/Walker 6
USA
email: klingle@cisco.com
phone: +1-919-392-2029
Co-editor Joon Maeng
VTEL Corporation
postal: 108 Wild Basin Rd.
Austin, TX 78746
USA
email: joon_maeng@vtel.com
phone: +1-512-437-4567
Co-editor Dave Walker
SS8 Networks, Inc.
postal: 80 Hines Road
Kanata, ON K2K 2T8
Canada
email: drwalker@ss8networks.com
phone: +1 613 592 2100"
DESCRIPTION
"Initial version of Session Initiation Protocol (SIP)
MIB Textual Conventions module used by other
SIP-related MIB Modules."
::= { sipMIB 1 }
--
-- Textual Conventions
--
SipServerActions ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Lists the possible actions of a SIP network server.
A specific action may be requested by a user agent
as a Contact parameter in a REGISTER."
SYNTAX INTEGER {
redirect(1),
proxy(2)
}
END
5.3. SIP Common
SIP-COMMON-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE,
Counter32, Counter32,
Integer32, Integer32,
Gauge32, Gauge32,
mib-2,
TimeTicks, TimeTicks,
Unsigned32 Unsigned32
Lingle/Maeng/Walker 7
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION,
DateAndTime, DateAndTime,
RowStatus, RowStatus,
TimeStamp,
TruthValue TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB; FROM SNMP-FRAMEWORK-MIB
sipMIB MODULE-IDENTITY sipMIB
LAST-UPDATED "200003020000Z" FROM SIP-MIB-SMI
applIndex
FROM NETWORK-SERVICES-MIB;
sipCommonMIB MODULE-IDENTITY
LAST-UPDATED "200004120000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO CONTACT-INFO
"SIP MIB Team email: sip-mib@egroups.com "SIP MIB Team email: sip-mib@egroups.com
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
skipping to change at page 5, line 14 skipping to change at line 437
Co-editor Joon Maeng Co-editor Joon Maeng
VTEL Corporation VTEL Corporation
postal: 108 Wild Basin Rd. postal: 108 Wild Basin Rd.
Austin, TX 78746 Austin, TX 78746
USA USA
email: joon_maeng@vtel.com email: joon_maeng@vtel.com
phone: +1-512-437-4567 phone: +1-512-437-4567
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
postal: 135 Michael Cowpland Drive, Suite 200 postal: 80 Hines Road
Kanata, ON K2M 2E9 Kanata, ON K2K 2T8
Canada Canada
email: drwalker@ss8networks.com email: drwalker@ss8networks.com
phone: +1 613 592 2459" phone: +1 613 592 2100"
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Initial version of Session Initiation Protocol (SIP)
MIB module. SIP is an application-layer signalling
protocol for creating, modifying and terminating
multimedia sessions with one or more participants.
These sessions include Internet multimedia conferences
and Internet telephone calls. SIP is defined in
RFC 2543 (March 1999).
This MIB is defined for the management of SIP User Lingle/Maeng/Walker 8
Agents (UAs), Proxy and Redirect Servers, and Common MIB module. This module defines objects which
registrars. may be common to all SIP entities.
SIP is an application-layer signalling protocol for
creating, modifying and terminating multimedia
sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 2543 (March
1999).
This MIB is defined for the managing objects which are
common to SIP User Agents (UAs), Proxy and Redirect
Servers, and Registrars. Objects specific to each of
these entities may be managed using entity specific
MIBs defined in other modules.
A User Agent is an application that contains both a A User Agent is an application that contains both a
User Agent Client (UAC) and a User Agent Server (UAS). User Agent Client (UAC) and a User Agent Server (UAS).
A UAC is an application that initiates a SIP request. A UAC is an application that initiates a SIP request.
A UAS is an application that contacts the user when a A UAS is an application that contacts the user when a
SIP request is received and that returns a response on SIP request is received and that returns a response on
behalf of the user. The response accepts, rejects, or behalf of the user. The response accepts, rejects, or
redirects the request. redirects the request.
A Proxy Server acts as both a client and a server. A Proxy Server acts as both a client and a server.
skipping to change at page 5, line 52 skipping to change at line 482
responding to them or passing them on to other responding to them or passing them on to other
servers, possibly after modification. servers, possibly after modification.
A Redirect Server accepts requests from clients and A Redirect Server accepts requests from clients and
returns zero or more addresses to that client. Unlike returns zero or more addresses to that client. Unlike
a Proxy server it does not initiate requests. Unlike a Proxy server it does not initiate requests. Unlike
a User Agent Server it does not accept calls. a User Agent Server it does not accept calls.
A Registrar is a server that accepts REGISTER A Registrar is a server that accepts REGISTER
requests. A Registrar is typically co-located with a requests. A Registrar is typically co-located with a
Proxy or Redirect Server. Proxy or Redirect Server."
::= { sipMIB 2 }
A SIP transaction occurs between a client and a server
and comprises all messages from the first request sent
from the client to the server up to a final (non-1xx)
response sent from the server to the client."
::= { mib-2 9998 } -- to be assigned by IANA
--
-- High Level Structure of MIB Object Definitions
--
sipMIBObjects OBJECT IDENTIFIER ::= { sipMIB 1 }
sipCommon OBJECT IDENTIFIER ::= { sipMIBObjects 1 }
sipUA OBJECT IDENTIFIER ::= { sipMIBObjects 2 }
sipServer OBJECT IDENTIFIER ::= { sipMIBObjects 3 }
sipProxy OBJECT IDENTIFIER ::= { sipMIBObjects 4 }
sipRedir OBJECT IDENTIFIER ::= { sipMIBObjects 5 }
sipReg OBJECT IDENTIFIER ::= { sipMIBObjects 6 }
--
-- Textual Conventions
--
SipServerActions ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Lists the possible actions of a SIP network server.
A specific action may be requested by a user agent
as a Contact parameter in a REGISTER."
SYNTAX INTEGER {
redirect(1),
proxy(2)
}
-- --
-- sipCommon Group -- sipCommon Group
-- This group contains MIB objects that are common to all SIP -- This group contains MIB objects that are common to all SIP
-- entities. -- entities.
-- --
sipCommonCfg OBJECT IDENTIFIER ::= { sipCommon 1 } sipCommonCfg OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
sipCommonStats OBJECT IDENTIFIER ::= { sipCommon 2 } sipCommonStats OBJECT IDENTIFIER ::= { sipCommonMIB 2 }
sipCommonStatsSummary OBJECT IDENTIFIER ::= { sipCommonStats 1 } sipCommonStatsSummary OBJECT IDENTIFIER ::= { sipCommonStats 1 }
sipCommonStatsMethod OBJECT IDENTIFIER ::= { sipCommonStats 2 } sipCommonStatsMethod OBJECT IDENTIFIER ::= { sipCommonStats 2 }
sipCommonStatsInfo OBJECT IDENTIFIER ::= { sipCommonStats 3 } sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonStats 3 }
sipCommonStatsSuccess OBJECT IDENTIFIER ::= { sipCommonStats 4 } sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonStats 4 }
sipCommonStatsRedirect OBJECT IDENTIFIER ::= { sipCommonStats 5 }
sipCommonStatsErrClient OBJECT IDENTIFIER ::= { sipCommonStats 6 }
sipCommonStatsErrServer OBJECT IDENTIFIER ::= { sipCommonStats 7 }
sipCommonStatsGlobalFail OBJECT IDENTIFIER ::= { sipCommonStats 8 }
sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonStats 9 }
Lingle/Maeng/Walker 9
-- --
-- Common Configuration Objects -- Common Configuration Objects
-- --
sipCommonCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the common configuration objects
applicable to all SIP entities. Each row represents
those objects for a particular SIP entity present in
this system. The instances of SIP entities are
uniquely identified by applIndex."
::= { sipCommonCfg 1 }
sipCommonCfgEntry OBJECT-TYPE
SYNTAX SipCommonCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of common configuration."
INDEX { applIndex }
::= { sipCommonCfgTable 1 }
SipCommonCfgEntry ::=
SEQUENCE {
sipProtocolVersion SnmpAdminString,
sipServiceOperStatus INTEGER,
sipServiceAdminStatus INTEGER,
sipServiceStartTime TimeTicks,
sipServiceLastChange TimeTicks,
sipOrganization SnmpAdminString,
sipMaxTransactions Unsigned32,
sipInviteTimeout Unsigned32,
sipHideOperation INTEGER,
sipUserLocationServerAddr SnmpAdminString,
sipCanUseCompact TruthValue,
sipRequestUriHostMatching TruthValue
}
sipProtocolVersion OBJECT-TYPE sipProtocolVersion OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will reflect the version of SIP supported by "This object will reflect the version of SIP supported by
this user agent. It will follow the same format as SIP this SIP entity. It will follow the same format as SIP
version information contained in the SIP messages version information contained in the SIP messages
generated by this SIP entity. For example, entities generated by this SIP entity. For example, entities
supporting SIP version 2 will return 'SIP/2.0' as dictated supporting SIP version 2 will return 'SIP/2.0' as dictated
by RFC 2543." by RFC 2543."
::= { sipCommonCfg 1 } ::= { sipCommonCfgEntry 1 }
Lingle/Maeng/Walker 10
sipServiceOperStatus OBJECT-TYPE sipServiceOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), up(1),
down(2), down(2),
testing(3), testing(3),
unknown(4), unknown(4),
halted(5), halted(5),
restarting(6) restarting(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 7, line 23 skipping to change at line 573
DESCRIPTION DESCRIPTION
"This object contains the current operational state of the "This object contains the current operational state of the
SIP application. SIP application.
up(1) : The application is operating normally, and up(1) : The application is operating normally, and
is processing (receiving and possibly is processing (receiving and possibly
issuing) SIP requests and responses. issuing) SIP requests and responses.
down(2) : The application is currently unable to down(2) : The application is currently unable to
process SIP messages. process SIP messages.
testing(3) : The application is currently in test mode testing(3) : The application is currently in test mode
and unable to process SIP messages. and may not be able to process SIP
messages.
unknown(4) : The operational status of the application unknown(4) : The operational status of the application
cannot be determined for some reason. cannot be determined for some reason.
halted(5) : The application has been manually halted(5) : The application has been manually
prevented from processing SIP messages. prevented from processing SIP messages.
restarting(6) : The application is booting and will soon restarting(6) : The application is booting and will soon
be able to process SIP messages." be able to process SIP messages."
::= { sipCommonCfg 2 } ::= { sipCommonCfgEntry 2 }
sipServiceAdminStatus OBJECT-TYPE sipServiceAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
shutdown(1), shutdown(1),
reset(2), reset(2),
restart(3), restart(3),
stop(4), stop(4),
rts(5) rts(5)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 7, line 54 skipping to change at line 605
state of the SIP server application. state of the SIP server application.
shutdown(1) : Immediately kill the application, don't shutdown(1) : Immediately kill the application, don't
restart. restart.
reset(2) : Restart application, reinitialize data, reset(2) : Restart application, reinitialize data,
requires rts. requires rts.
restart(3) : Restart application, no data loss, requires restart(3) : Restart application, no data loss, requires
rts. rts.
stop(4) : Stop processing new requests, requires rts. stop(4) : Stop processing new requests, requires rts.
rts(5) : Return to service." rts(5) : Return to service."
::= { sipCommonCfg 3 }
Lingle/Maeng/Walker 11
::= { sipCommonCfgEntry 3 }
sipServiceStartTime OBJECT-TYPE sipServiceStartTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the SIP entity was last "The value of sysUpTime at the time the SIP entity was last
started. If the current state was entered prior to the started. If the current state was entered prior to the
last re-initialization of the local network management last re-initialization of the local network management
subsystem, then this object contains a zero value." subsystem, then this object contains a zero value."
::= { sipCommonCfg 4 } ::= { sipCommonCfgEntry 4 }
sipServiceLastChange OBJECT-TYPE sipServiceLastChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the SIP entity entered "The value of sysUpTime at the time the SIP entity entered
its current operational state. If the current state was its current operational state. If the current state was
entered prior to the last re-initialization of the local entered prior to the last re-initialization of the local
network management subsystem, then this object contains a network management subsystem, then this object contains a
zero value." zero value."
::= { sipCommonCfg 5 } ::= { sipCommonCfgEntry 5 }
sipOrganization OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object contains the name of the organization issuing
the request or response. It may also be inserted by a
proxy at a boundary of an organization. If the object
exists, it is inserted into requests and responses."
REFERENCE
"RFC 2543, Section 6.24"
::= { sipCommonCfgEntry 6 }
sipMaxTransactions OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the maximum number of simultaneous
transactions that the SIP entity can manage."
::= { sipCommonCfgEntry 7 }
sipInviteTimeout OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
Lingle/Maeng/Walker 12
"This object specifies the default duration that a SIP
client will wait for a response to an INVITE request.
For proxy servers, if a received request contained an
Expires header, then the value in the header takes
precedence. The server returns a 408 Request Timeout if
no response is received before
expiration of the request timer.
For user agent clients, this value is inserted into the
Expires header."
::= { sipCommonCfgEntry 8 }
sipHideOperation OBJECT-TYPE
SYNTAX INTEGER {
none(1),
hop(2),
route(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies which type of Hide header the server
adds to requests. These headers are normally added by a
User Agent, but may be added by a proxy. The value of
this object does not affect processing of Hide headers in
received requests.
The value of this object only applies to requests that do
not contain a Hide:route header.
none(1) : The server doesn't insert a Hide header.
hop(2) : The server inserts a Hide:hop header.
route(3) : The server inserts a Hide:route header."
REFERENCE
"RFC 2543, Section 6.22"
DEFVAL { none }
::= { sipCommonCfgEntry 9 }
sipUserLocationServerAddr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object will specify the address of the User Location
Server (ULS) being used to resolve the location of end
points.
This could be a Domain Name Server (DNS) or a SIP
proxy/redirect server in the case where this entity is a
user agent. This could be some sort of database server if
this entity is a proxy/redirect server.
The format of the address follows the IETF service
Lingle/Maeng/Walker 13
location protocol. The syntax is as follows:
mapping-type:type-specific-syntax
The mapping-type specifies a scheme for mapping the
matching dial string to a target server. The type-
specific-syntax is exactly that, something that the
particular mapping scheme can understand.
For example,
Session target Meaning
ipv4:171.68.13.55:1006 The session target is the IP
version 4 address of
171.68.13.55 and port 1006.
dns:pots.cisco.com The session target is the IP
host with dns name
pots.cisco.com.
The valid Mapping type definitions for the peer are as
follows:
ipv4 - Syntax: ipv4:w.x.y.z:port or ipv4:w.x.y.z
dns - Syntax: dns:host.domain."
::= { sipCommonCfgEntry 10 }
sipCanUseCompact OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies whether or not the client is able
to use the compact encoding form in the requests it sends.
If the value of this object is TRUE, the client is able to
encode outgoing messages using the compact encoding form.
If the value is FALSE, the client is unable to encode
outgoing messages using the compact form."
REFERENCE
"RFC 2543, Section 9"
::= { sipCommonCfgEntry 11 }
sipRequestUriHostMatching OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies whether or not the host in
RequestURI must match server's host name.
If the value of this object is TRUE, then the server
requires a match, and if the RequestURI doesn't match the
server's host name, a 404 Not Found status code is
returned by the server.
If the value is FALSE, then no match is required."
REFERENCE
"RFC 2543, Section 4.3"
Lingle/Maeng/Walker 14
::= { sipCommonCfgEntry 12 }
-- --
-- Support for multiple ports -- Support for multiple ports
-- --
sipPortTable OBJECT-TYPE sipPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipPortEntry SYNTAX SEQUENCE OF SipPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the list of ports that this SIP entity "This table contains the list of ports that each SIP entity
is allowed to use. These ports can be advertised using in this system is allowed to use. These ports can be
the Contact header in a REGISTER request or response. advertised using the Contact header in a REGISTER request
Port 5060 (the default SIP port registered with IANA) must or response. The instances of SIP entities are uniquely
always be present in this table." identified by applIndex."
::= { sipCommonCfg 6 } ::= { sipCommonCfg 2 }
sipPortEntry OBJECT-TYPE sipPortEntry OBJECT-TYPE
SYNTAX SipPortEntry SYNTAX SipPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specification of a particular port." "Specification of a particular port."
INDEX { sipPort } INDEX { applIndex, sipPort }
::= { sipPortTable 1 } ::= { sipPortTable 1 }
SipPortEntry ::= SipPortEntry ::=
SEQUENCE { SEQUENCE {
sipPort INTEGER, sipPort INTEGER,
sipTransport INTEGER, sipTransport INTEGER,
sipPortStatus RowStatus sipPortStatus RowStatus
} }
sipPort OBJECT-TYPE sipPort OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (1..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects a particular port that can be used by "This object reflects a particular port that can be used by
the SIP application." the SIP application."
::= { sipPortEntry 1 } ::= { sipPortEntry 1 }
sipTransport OBJECT-TYPE sipTransport OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
udp(1), udp(1),
tcp(2), tcp(2),
udpAndTcp(3) udpAndTcp(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the transport protocol the SIP "This object will specify the transport protocol the SIP
application will use to receive SIP messages. application will use to receive SIP messages.
Lingle/Maeng/Walker 15
udp(1) : Use User Datagram Protocol. udp(1) : Use User Datagram Protocol.
tcp(2) : Use Transmission Control Protocol. tcp(2) : Use Transmission Control Protocol.
udpAndTcp(3) : Use both UDP and TCP." udpAndTcp(3) : Use both UDP and TCP."
::= { sipPortEntry 2 } ::= { sipPortEntry 2 }
sipPortStatus OBJECT-TYPE sipPortStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 9, line 33 skipping to change at line 853
::= { sipPortEntry 3 } ::= { sipPortEntry 3 }
-- --
-- Support for multiple non-SIP URIs -- Support for multiple non-SIP URIs
-- --
sipUriSupportedTable OBJECT-TYPE sipUriSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUriSupportedEntry SYNTAX SEQUENCE OF SipUriSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of URIs supported by the SIP "This table contains a list of URIs supported by each SIP
entity. These are in addition to the SIP URL which must entity in this system. These are in addition to the SIP
necessarily be supported. Normally the list of URIs URL which must necessarily be supported. Normally the
supported by an entity is static (i.e. will not change list of URIs supported by an entity is static (i.e. will
over time). not change over time).
A URI is a Uniform Resource Identifier (as defined in RFC A URI is a Uniform Resource Identifier (as defined in RFC
2396). 2396).
URIs could, for example, contain URLs for phones, fax, or URIs could, for example, contain URLs for phones, fax, or
irc if they were defined) or a mailto: (RFC 2368) URL." irc if they were defined) or a mailto: (RFC 2368) URL.
The instances of SIP entities are uniquely identified
by applIndex."
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
::= { sipCommonCfg 7 } ::= { sipCommonCfg 3 }
sipUriSupportedEntry OBJECT-TYPE sipUriSupportedEntry OBJECT-TYPE
SYNTAX SipUriSupportedEntry SYNTAX SipUriSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular non-SIP URI supported by the SIP entity." "A particular non-SIP URI supported by the SIP entity."
INDEX { sipUriSupportedIndex } INDEX { applIndex, sipUriSupportedIndex }
::= { sipUriSupportedTable 1 } ::= { sipUriSupportedTable 1 }
SipUriSupportedEntry ::= SipUriSupportedEntry ::=
SEQUENCE { SEQUENCE {
Lingle/Maeng/Walker 16
sipUriSupportedIndex Unsigned32, sipUriSupportedIndex Unsigned32,
sipUriSupported SnmpAdminString sipUriSupported SnmpAdminString
} }
sipUriSupportedIndex OBJECT-TYPE sipUriSupportedIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row "This object uniquely identifies a conceptual row
skipping to change at page 10, line 36 skipping to change at line 921
-- --
-- Support for features which may be requested in Proxy-Require -- Support for features which may be requested in Proxy-Require
-- and Require headers -- and Require headers
-- --
sipFtrSupportedTable OBJECT-TYPE sipFtrSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipFtrSupportedEntry SYNTAX SEQUENCE OF SipFtrSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of the non-standard features "This table contains a list of the non-standard features
supported by the SIP entity, and which may be required by supported by each SIP entity in this system, and which
a peer. Definition of such features is outside the scope may be required by a peer. Definition of such features is
of SIP, which only provides mechanisms whereby support for outside the scope of SIP, which only provides mechanisms
specific features may be signalled or requested. whereby support for specific features may be signalled or
requested.
For example, a user agent client may require that a server For example, a user agent client may require that a server
support the 'com.example.billing' feature, which it would support the 'com.example.billing' feature, which it would
indicate in a Require header. Such a client would have indicate in a Require header. Such a client would have
a row in its sipFtrSupportedTable containing the string a row in its sipFtrSupportedTable containing the string
'com.example.billing'. Similarly, a server which is 'com.example.billing'. Similarly, a server which is
capable of handling requests for such features would list capable of handling requests for such features would list
the string in its sipFtrSupportedTable. the string in its sipFtrSupportedTable.
If a server does not support the required feature If a server does not support the required feature
(indicated in a Require header to a UAS, or in a Proxy- (indicated in a Require header to a UAS, or in a Proxy-
Require to a proxy server), the server returns a 420 Bad Require to a proxy server), the server returns a 420 Bad
Lingle/Maeng/Walker 17
Extension listing the feature in an Unsupported header. Extension listing the feature in an Unsupported header.
Normally the list of such features supported by an entity Normally the list of such features supported by an entity
is static (i.e. will not change over time)." is static (i.e. will not change over time).
The instances of SIP entities are uniquely identified
by applIndex."
REFERENCE REFERENCE
"RFC 2543, Sections 6.28, 6.30, and 6.38" "RFC 2543, Sections 6.28, 6.30, and 6.38"
::= { sipCommonCfg 8 } ::= { sipCommonCfg 4 }
sipFtrSupportedEntry OBJECT-TYPE sipFtrSupportedEntry OBJECT-TYPE
SYNTAX SipFtrSupportedEntry SYNTAX SipFtrSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular non-standard feature supported by the SIP "A particular non-standard feature supported by the SIP
entity, and which may be required by a peer." entity, and which may be required by a peer."
INDEX { sipFtrSupportedIndex } INDEX { applIndex, sipFtrSupportedIndex }
::= { sipFtrSupportedTable 1 } ::= { sipFtrSupportedTable 1 }
SipFtrSupportedEntry ::= SipFtrSupportedEntry ::=
SEQUENCE { SEQUENCE {
sipFtrSupportedIndex Unsigned32, sipFtrSupportedIndex Unsigned32,
sipFtrSupported SnmpAdminString sipFtrSupported SnmpAdminString
} }
sipFtrSupportedIndex OBJECT-TYPE sipFtrSupportedIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
skipping to change at page 11, line 34 skipping to change at line 986
sipFtrSupported OBJECT-TYPE sipFtrSupported OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a particular non-standard feature "This object indicates a particular non-standard feature
which is supported by the SIP entity." which is supported by the SIP entity."
::= { sipFtrSupportedEntry 2 } ::= { sipFtrSupportedEntry 2 }
-- --
-- Additional Common Configuration Objects -- Common Statistics Objects
-- --
sipOrganization OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object contains the name of the organization issuing
the request or response. It may also be inserted by a
proxy at a boundary of an organization. If the object
exists, it is inserted into requests and responses."
REFERENCE
"RFC 2543, Section 6.24"
::= { sipCommonCfg 9 }
sipMaxTransactions OBJECT-TYPE --
SYNTAX Unsigned32 (1..4294967295) -- Summary Statistics
MAX-ACCESS read-only --
STATUS current
DESCRIPTION
"This object indicates the maximum number of simultaneous
transactions that the SIP entity can manage."
::= { sipCommonCfg 10 }
sipRequestDfltExpires OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the default duration that a SIP
client will wait for a response to an INVITE request.
For proxy servers, if a received request contained an
Expires header, then the value in the header takes
precedence. The server returns a 408 Request Timeout if
no response is received before
expiration of the request timer.
For user agent clients, this value is inserted into the
Expires header."
::= { sipCommonCfg 11 }
sipHideOperation OBJECT-TYPE Lingle/Maeng/Walker 18
SYNTAX INTEGER { sipSummaryStatsTable OBJECT-TYPE
none(1), SYNTAX SEQUENCE OF SipSummaryStatsEntry
hop(2), MAX-ACCESS not-accessible
route(3)
}
MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies which type of Hide header the server "This table contains the summary statistics objects
adds to requests. These headers are normally added by a applicable to all SIP entities. Each row represents
User Agent, but may be added by a proxy. The value of those objects for a particular SIP entity present in
this object does not affect processing of Hide headers in this system. The instances of SIP entities are uniquely
received requests. identified by applIndex."
::= { sipCommonStatsSummary 1 }
The value of this object only applies to requests that do
not contain a Hide:route header.
none(1) : The server doesn't insert a Hide header.
hop(2) : The server inserts a Hide:hop header.
route(3) : The server inserts a Hide:route header."
REFERENCE
"RFC 2543, Section 6.22"
DEFVAL { none }
::= { sipCommonCfg 12 }
sipUserLocationServerAddr OBJECT-TYPE sipSummaryStatsEntry OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SipSummaryStatsEntry
MAX-ACCESS read-write MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the address of the User Location "A row of summary statistics."
Server (ULS) being used to resolve the location of end INDEX { applIndex }
points. ::= { sipSummaryStatsTable 1 }
This could be a Domain Name Server (DNS) or a SIP
proxy/redirect server in the case where this entity is a
user agent. This could be some sort of database server if
this entity is a proxy/redirect server.
The format of the address follows the IETF service
location protocol. The syntax is as follows:
mapping-type:type-specific-syntax
The mapping-type specifies a scheme for mapping the
matching dial string to a target server. The type-
specific-syntax is exactly that, something that the
particular mapping scheme can understand.
For example,
Session target Meaning
ipv4:171.68.13.55:1006 The session target is the IP
version 4 address of
171.68.13.55 and port 1006.
dns:pots.cisco.com The session target is the IP
host with dns name
pots.cisco.com.
The valid Mapping type definitions for the peer are as
follows:
ipv4 - Syntax: ipv4:w.x.y.z:port or ipv4:w.x.y.z
dns - Syntax: dns:host.domain."
::= { sipCommonCfg 13 }
-- SipSummaryStatsEntry ::=
-- Common Statistics Objects SEQUENCE {
-- sipSummaryInRequests Counter32,
sipSummaryOutRequests Counter32,
sipSummaryInResponses Counter32,
sipSummaryOutResponses Counter32,
sipSummaryTotalTransactions Counter32
}
--
-- Summary Statistics
--
sipSummaryInRequests OBJECT-TYPE sipSummaryInRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the total number of SIP request "This object indicates the total number of SIP request
messages received by the SIP entity." messages received by the SIP entity including
::= { sipCommonStatsSummary 1 } retransmissions."
::= { sipSummaryStatsEntry 1 }
sipSummaryOutRequests OBJECT-TYPE sipSummaryOutRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the total number of SIP request "This object contains the total number of SIP request
messages sent out (originated and relayed) by the SIP messages sent out (originated and relayed) by the SIP
entity. Where a particular message is sent more than entity. Where a particular message is sent more than
once, for example as a retransmission, or as a result of once, for example as a retransmission, or as a result of
forking, each transmission is counted separately." forking, each transmission is counted separately."
::= { sipCommonStatsSummary 2 } ::= { sipSummaryStatsEntry 2 }
sipSummaryInResponses OBJECT-TYPE sipSummaryInResponses OBJECT-TYPE
Lingle/Maeng/Walker 19
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the total number of SIP response "This object contains the total number of SIP response
messages received by the SIP entity." messages received by the SIP entity including
::= { sipCommonStatsSummary 3 } retransmissions."
::= { sipSummaryStatsEntry 3 }
sipSummaryOutResponses OBJECT-TYPE sipSummaryOutResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the total number of SIP response "This object contains the total number of SIP response
messages sent (originated and relayed) by the SIP entity." messages sent (originated and relayed) by the SIP entity
::= { sipCommonStatsSummary 4 } including retransmissions."
::= { sipSummaryStatsEntry 4 }
sipSummaryTotalTransactions OBJECT-TYPE sipSummaryTotalTransactions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of transactions "This object contains a count of the number of transactions
completed or in progress. completed or in progress.
A SIP transaction occurs between a client and a server and A SIP transaction occurs between a client and a server and
skipping to change at page 14, line 28 skipping to change at line 1088
the client to the server up to a final (non-1xx) response the client to the server up to a final (non-1xx) response
sent from the server to the client. sent from the server to the client.
A transaction is identified by the CSeq sequence number A transaction is identified by the CSeq sequence number
within a single call leg. The ACK request has the same within a single call leg. The ACK request has the same
CSeq number as the corresponding INVITE request, but CSeq number as the corresponding INVITE request, but
comprises a transaction of its own. comprises a transaction of its own.
In the case of a forked request, all branches count as a In the case of a forked request, all branches count as a
single transaction." single transaction."
::= { sipCommonStatsSummary 5 } ::= { sipSummaryStatsEntry 5 }
-- --
-- SIP Method Statistics -- SIP Method Statistics
-- Total counts for each SIP method. -- Total counts for each SIP method.
-- --
sipMethodStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipMethodStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the per method statistics objects
applicable to all SIP entities. Each row represents
those objects for a particular SIP entity present in
Lingle/Maeng/Walker 20
this system. The instances of SIP entities are uniquely
identified by applIndex."
::= { sipCommonStatsMethod 1 }
sipMethodStatsEntry OBJECT-TYPE
SYNTAX SipMethodStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of per method statistics."
INDEX { applIndex }
::= { sipMethodStatsTable 1 }
SipMethodStatsEntry ::=
SEQUENCE {
sipStatsInviteIns Counter32,
sipStatsInviteOuts Counter32,
sipStatsAckIns Counter32,
sipStatsAckOuts Counter32,
sipStatsByeIns Counter32,
sipStatsByeOuts Counter32,
sipStatsCancelIns Counter32,
sipStatsCancelOuts Counter32,
sipStatsOptionsIns Counter32,
sipStatsOptionsOuts Counter32,
sipStatsRegisterIns Counter32,
sipStatsRegisterOuts Counter32
}
sipStatsInviteIns OBJECT-TYPE sipStatsInviteIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE requests "This object reflects the total number of INVITE requests
received by the SIP entity." received by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.1" "RFC 2543, Section 4.2.1"
::= { sipCommonStatsMethod 1 } ::= { sipMethodStatsEntry 1 }
sipStatsInviteOuts OBJECT-TYPE sipStatsInviteOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE requests "This object reflects the total number of INVITE requests
sent by the SIP entity." sent by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.1" "RFC 2543, Section 4.2.1"
::= { sipCommonStatsMethod 2 } ::= { sipMethodStatsEntry 2 }
sipStatsAckIns OBJECT-TYPE sipStatsAckIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
Lingle/Maeng/Walker 21
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of ACK requests "This object reflects the total number of ACK requests
received by the SIP entity." received by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.2" "RFC 2543, Section 4.2.2"
::= { sipCommonStatsMethod 3 } ::= { sipMethodStatsEntry 3 }
sipStatsAckOuts OBJECT-TYPE sipStatsAckOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of ACK requests sent "This object reflects the total number of ACK requests sent
by the SIP entity." by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.2" "RFC 2543, Section 4.2.2"
::= { sipCommonStatsMethod 4 } ::= { sipMethodStatsEntry 4 }
sipStatsByeIns OBJECT-TYPE sipStatsByeIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of BYE requests "This object reflects the total number of BYE requests
received by the SIP entity." received by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.4" "RFC 2543, Section 4.2.4"
::= { sipCommonStatsMethod 5 } ::= { sipMethodStatsEntry 5 }
sipStatsByeOuts OBJECT-TYPE sipStatsByeOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of BYE requests sent "This object reflects the total number of BYE requests sent
by the SIP entity." by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.4" "RFC 2543, Section 4.2.4"
::= { sipCommonStatsMethod 6 } ::= { sipMethodStatsEntry 6 }
sipStatsCancelIns OBJECT-TYPE sipStatsCancelIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of CANCEL requests "This object reflects the total number of CANCEL requests
received by the SIP entity." received by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.5" "RFC 2543, Section 4.2.5"
::= { sipCommonStatsMethod 7 } ::= { sipMethodStatsEntry 7 }
sipStatsCancelOuts OBJECT-TYPE sipStatsCancelOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
Lingle/Maeng/Walker 22
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of CANCEL requests "This object reflects the total number of CANCEL requests
sent by the SIP entity." sent by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.5" "RFC 2543, Section 4.2.5"
::= { sipCommonStatsMethod 8 } ::= { sipMethodStatsEntry 8 }
sipStatsOptionsIns OBJECT-TYPE sipStatsOptionsIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of OPTIONS requests "This object reflects the total number of OPTIONS requests
received by the SIP entity." received by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.3" "RFC 2543, Section 4.2.3"
::= { sipCommonStatsMethod 9 } ::= { sipMethodStatsEntry 9 }
sipStatsOptionsOuts OBJECT-TYPE sipStatsOptionsOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of OPTIONS requests "This object reflects the total number of OPTIONS requests
sent by the SIP entity." sent by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.3" "RFC 2543, Section 4.2.3"
::= { sipCommonStatsMethod 10 } ::= { sipMethodStatsEntry 10 }
sipStatsRegisterIns OBJECT-TYPE sipStatsRegisterIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of REGISTER requests "This object reflects the total number of REGISTER requests
received by the SIP entity." received by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.6" "RFC 2543, Section 4.2.6"
::= { sipCommonStatsMethod 11 } ::= { sipMethodStatsEntry 11 }
sipStatsRegisterOuts OBJECT-TYPE sipStatsRegisterOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of REGISTER requests "This object reflects the total number of REGISTER requests
sent by the SIP entity." sent by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.6" "RFC 2543, Section 4.2.6"
::= { sipCommonStatsMethod 12 } ::= { sipMethodStatsEntry 12 }
sipStatsInfoIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of INFO requests
received by the SIP entity."
REFERENCE
"draft-ietf-sip-info-method-02.txt"
::= { sipCommonStatsMethod 13 }
sipStatsInfoOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of INFO requests
sent by the SIP entity."
REFERENCE
"draft-ietf-sip-info-method-02.txt"
::= { sipCommonStatsMethod 14 }
--
-- SIP Informational Response Statistics
--
-- These counters reflect the number of SIP messages sent and
-- received by this system that relate to providing some
-- informational response to the progress of processing a SIP
-- request.
--
sipStatsInfoTryingIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Trying
(100) responses received by the SIP entity.
Trying responses indicate that some unspecified
action is being taken on behalf of this call, but
the user has not yet been located. Inbound Trying
responses indicate that outbound INVITE requests
sent out by this system have been received and
are processed."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.1.1"
::= { sipCommonStatsInfo 1 }
sipStatsInfoTryingOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Trying
(100) responses sent by the SIP entity.
Trying responses indicate that some unspecified
action is being taken on behalf of this call, but
the user has not yet been located. Outbound Trying
responses indicate that this system is successfully
receiving INVITE requests and processing them on
behalf of the system initiating the INVITE."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.1.1"
::= { sipCommonStatsInfo 2 }
sipStatsInfoRingingIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Ringing
(180) responses received by the SIP entity.
A inbound Ringing response indicates that the UAS that is
processing an INVITE initiated by this system has
found a possible location where the desired end user
has registered recently and is trying to alert the user."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.1.2"
::= { sipCommonStatsInfo 3 }
sipStatsInfoRingingOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Ringing
(180) responses sent by the SIP entity.
A outbound Ringing response indicates that this
system has processed an INVITE for a particular
end user and found a possible location where that
user has registered recently. The system is trying
to alert the end user and is conveying that status
to the system that originated the INVITE."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.1.2"
::= { sipCommonStatsInfo 4 }
sipStatsInfoForwardedIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Call Is Being
Forwarded (181) responses received by the SIP entity.
A proxy server might use a Forwarded status code to
indicate that the call is being forwarded to a different
set of destinations. Inbound Forwarded responses indicate
to this system that forwarding actions are taking place
with regard to calls initiated by this system."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.1.3"
::= { sipCommonStatsInfo 5 }
sipStatsInfoForwardedOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Call Is Being
Forwarded (181) responses sent by the SIP entity.
A proxy server might use a Forwarded status code to
indicate that the call is being forwarded to a different
set of destinations. Outbound Forwarded responses
indicate this system is taking some forwarding action
for calls and conveying that status to the system that
initiated the calls."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.1.3"
::= { sipCommonStatsInfo 6 }
sipStatsInfoQueuedIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Queued
(182) responses received by the SIP entity.
Inbound Queued responses indicate that the users that
this system is attempting to call are temporarily
unavailable but the SIP agents operating on behalf
of those users wish to queue the calls rather than
reject them. When the called parties become available,
this system can expect to receive the appropriate
final status response. The Reason-Phrase from the
Queued response messages Status-Line can give further
details about the status of the call. Multiple
Queued responses to update this system about the status
of the queued call might be received."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.1.4"
::= { sipCommonStatsInfo 7 }
sipStatsInfoQueuedOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Queued
(182) responses sent by the SIP entity.
Outbound Queued responses indicate that this system
has determined that the called party is temporarily
unavailable but the call is not rejected. Instead,
the call is queued until the called party becomes
available. Queued responses messages are sent to
the system originating the call request to convey
the current status of a queued call."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.1.4"
::= { sipCommonStatsInfo 8 }
sipStatsInfoSessionProgIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Session
Progress (183) responses received by the SIP entity."
::= { sipCommonStatsInfo 9 }
sipStatsInfoSessionProgOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Session
Progress (183) responses sent by the SIP entity."
::= { sipCommonStatsInfo 10 }
-- --
-- SIP Success Response Statistics
--
-- These counters reflect the number of SIP messages sent and
-- received by this system that relate to successful completion of a
-- SIP request.
--
sipStatsSuccessOkIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Ok
(200) responses received by the SIP entity.
The meaning of inbound Ok responses depends
on the method used in the associated request.
BYE : The Ok response means the call has Lingle/Maeng/Walker 23
been terminated. -- support for extension methods
CANCEL : The Ok response means the search for
the end user has been cancelled.
INVITE : The Ok response means the called party
has agreed to participate in the call.
OPTIONS : The Ok response means the called party
has agreed to share its capabilities.
REGISTER : The Ok response means the registration
has succeeded.
INFO : The Ok response means the INFO request
was received and processed correctly."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.2.1"
::= { sipCommonStatsSuccess 1 }
sipStatsSuccessOkOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Ok
(200) responses sent by the SIP entity.
The meaning of outbound Ok responses depends
on the method used in the associated request.
BYE : The Ok response means the call has
been terminated.
CANCEL : The Ok response means the search for
the end user has been cancelled.
INVITE : The Ok response means the called party
has agreed to participate in the call.
OPTIONS : The Ok response means the called party
has agreed to share its capabilities.
REGISTER : The Ok response means the registration
has succeeded.
INFO : The Ok response means the INFO request
was received and processed correctly."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.2.1"
::= { sipCommonStatsSuccess 2 }
--
-- SIP Redirection Response Statistics
--
-- These counters reflect the number of SIP messages sent and
-- received by this system that relate to call redirection actions
-- taken by a Redirect Server.
-- --
sipStatsRedirMultipleChoiceIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Multiple
Choices (300) responses received by the SIP entity.
Multiple Choices responses indicate that the called
party can be reached at several different locations
and the server cannot or prefers not to proxy the
request."
REFERENCE
"RFC 2543, Section 5.1.1 & 7.3.1"
::= { sipCommonStatsRedirect 1 }
sipStatsRedirMultipleChoiceOuts OBJECT-TYPE sipStatsExtMethodTable OBJECT-TYPE
SYNTAX Counter32 SYNTAX SEQUENCE OF SipStatsExtMethodEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Multiple "This table contains the list of extension methods which
Choices (300) responses sent by the SIP entity. each SIP entity in this system has been requested to
Multiple Choices responses indicate that the called monitor. The instances of SIP entities are uniquely
party can be reached at several different locations identified by applIndex."
and the server cannot or prefers not to proxy the ::= { sipCommonStatsMethod 2 }
request."
REFERENCE
"RFC 2543, Section 5.1.1 & 7.3.1"
::= { sipCommonStatsRedirect 2 }
sipStatsRedirMovedPermIns OBJECT-TYPE sipStatsExtMethodEntry OBJECT-TYPE
SYNTAX Counter32 SYNTAX SipStatsExtMethodEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Moved "This row contains information on a particular extension
Permanently (301) responses received by the SIP entity. method that the SIP entity has been requested to monitor."
Moved Permanently responses indicate that the called party INDEX { applIndex, sipStatsExtMethodIndex }
can no longer be found at the address offered in the ::= { sipStatsExtMethodTable 1 }
request and the requesting UAC should retry at the new
address given by the Contact header field of the
response."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.3.2"
::= { sipCommonStatsRedirect 3 }
sipStatsRedirMovedPermOuts OBJECT-TYPE SipStatsExtMethodEntry ::=
SYNTAX Counter32 SEQUENCE {
MAX-ACCESS read-only sipStatsExtMethodIndex Unsigned32,
STATUS current sipStatsExtMethodName SnmpAdminString,
DESCRIPTION sipStatsExtMethodIns Counter32,
"This object reflects the total number of Moved sipStatsExtMethodOuts Counter32,
Permanently (301) responses sent by the SIP entity. sipStatsExtMethodStatus RowStatus
Moved Permanently responses indicate that the called party }
can no longer be found at the address offered in the
request and the requesting UAC should retry at the new
address given by the Contact header field of the
response."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.3.2"
::= { sipCommonStatsRedirect 4 }
sipStatsRedirMovedTempIns OBJECT-TYPE sipStatsExtMethodIndex OBJECT-TYPE
SYNTAX Counter32 SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Moved "This object uniquely identifies a conceptual row in the
Temporarily (302) responses received by the SIP entity. table."
Moved Temporarily responses indicate the UAC should ::= { sipStatsExtMethodEntry 1 }
retry the request directed at the new address(es)
given by the Contact header field of the response.
The duration of this redirection can be indicated
through the Expires header. If no explicit expiration
time is given, the new address(es) are only valid
for this call."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.3.3"
::= { sipCommonStatsRedirect 5 }
sipStatsRedirMovedTempOuts OBJECT-TYPE sipStatsExtMethodName OBJECT-TYPE
SYNTAX Counter32 SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Moved "This object contains the name of the particular extension
Temporarily (302) responses sent by the SIP entity. method that the SIP entity has been requested to monitor.
Moved Temporarily responses indicate the UAC should For example, it may contain the string 'INFO' if the
retry the request directed at the new address(es) network management station has requested that the SIP
given by the Contact header field of the response. entity count the number of messages sent an received
The duration of this redirection can be indicated which containing an INFO method. It is an error for any
through the Expires header. If no explicit expiration of the methods contained in RFC 2543 to be requested."
time is given, the new address(es) are only valid
for this call."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.3.3"
::= { sipCommonStatsRedirect 6 }
sipStatsRedirSeeOtherIns OBJECT-TYPE Lingle/Maeng/Walker 24
SYNTAX Counter32 ::= { sipStatsExtMethodEntry 2 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of See Other
(303) responses received by the SIP entity."
REFERENCE
"RFC 2543, Sections 5.1.1"
::= { sipCommonStatsRedirect 7 }
sipStatsRedirSeeOtherOuts OBJECT-TYPE sipStatsExtMethodIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of See Other
(303) responses sent by the SIP entity."
REFERENCE
"RFC 2543, Sections 5.1.1"
::= { sipCommonStatsRedirect 8 }
sipStatsRedirUseProxyIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Use Proxy "This object reflects the total number of requests received
(305) responses received by the SIP entity. by the SIP entity which requested the method contained in
Use Proxy responses indicate that requested resources the sipStatsExtMethodName column."
must be accessed through the proxy given by the ::= { sipStatsExtMethodEntry 3 }
Contact header field of the response. The recipient
of this response is expected to repeat this single
request via the proxy."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.3.4"
::= { sipCommonStatsRedirect 9 }
sipStatsRedirUseProxyOuts OBJECT-TYPE sipStatsExtMethodOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Use Proxy "This object reflects the total number of requests sent
(305) responses sent by the SIP entity. by the SIP entity which requested the method contained in
See Other responses indicate that requested resources the sipStatsExtMethodName column."
must be accessed through the proxy given by the ::= { sipStatsExtMethodEntry 4 }
Contact header field of the response. The recipient
of this response is expected to repeat this single
request via the proxy."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.3.4"
::= { sipCommonStatsRedirect 10 }
sipStatsRedirAltServiceIns OBJECT-TYPE sipStatsExtMethodStatus OBJECT-TYPE
SYNTAX Counter32 SYNTAX RowStatus
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Alternative "The row status of the entry. This object is required
Service (380) responses received by the SIP entity. to create or delete rows remotely by a manager."
Alternative Service responses indicate that the call ::= { sipStatsExtMethodEntry 5 }
was not successful, but alternative services are
possible. Those alternative services are described
in the message body of the response."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.3.5"
::= { sipCommonStatsRedirect 11 }
sipStatsRedirAltServiceOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Alternative
Service (380) responses sent by the SIP entity.
Alternative Service responses indicate that the call
was not successful, but alternative services are
possible. Those alternative services are described
in the message body of the response."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.3.5"
::= { sipCommonStatsRedirect 12 }
--
-- SIP Client Error Responses Statistics
--
-- The following Inbound counters reflect failure responses received
-- by a SIP entity providing a client function.
--
-- The following Outbound counters reflect failure responses sent by
-- a SIP entity providing a server function.
-- --
-- Servers generally send these responses to Clients. -- SIP Response Status Codes
-- --
sipStatsClientBadRequestIns OBJECT-TYPE sipStatusCodesTable OBJECT-TYPE
SYNTAX Counter32 SYNTAX SEQUENCE OF SipStatusCodesEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object reflects the total number of Bad Request (400)
responses received by the SIP entity. Inbound Bad Request
responses indicate that requests issued by this system
could not be understood due to malformed syntax."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.1"
::= { sipCommonStatsErrClient 1 }
sipStatsClientBadRequestOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Bad Request (400)
responses sent by the SIP entity. Outbound Bad Request
responses indicate that requests received by this system
could not be understood due to malformed syntax."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.1"
::= { sipCommonStatsErrClient 2 }
sipStatsClientUnauthorizedIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Unauthorized
(401) responses received by the SIP entity. Inbound
Unauthorized responses indicate that requests issued by
this system require user authentication."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.2"
::= { sipCommonStatsErrClient 3 }
sipStatsClientUnauthorizedOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Unathorized (401) "This table contains statistics on response status code
responses sent by the SIP entity. classes for each SIP entity in this system. The instances
Outbound Unauthorized responses indicate that requests of SIP entities are uniquely identified by applIndex."
received by this system require user authentication." ::= { sipCommonStatusCode 1 }
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.2"
::= { sipCommonStatsErrClient 4 }
sipStatsClientPaymentReqdIns OBJECT-TYPE sipStatusCodesEntry OBJECT-TYPE
SYNTAX Counter32 SYNTAX SipStatusCodesEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Payment Required "This row contains statistics on response status codes."
(402) responses received by the SIP entity." INDEX { applIndex }
REFERENCE ::= { sipStatusCodesTable 1 }
"RFC 2543, Sections 5.1.1 & 7.4.3"
::= { sipCommonStatsErrClient 5 }
sipStatsClientPaymentReqdOuts OBJECT-TYPE Lingle/Maeng/Walker 25
SYNTAX Counter32 SipStatusCodesEntry ::=
MAX-ACCESS read-only SEQUENCE {
STATUS current sipStatsInfoClassIns Counter32,
DESCRIPTION sipStatsInfoClassOuts Counter32,
"This object reflects the total number of Payment Required sipStatsSuccessClassIns Counter32,
(402) responses sent by the SIP entity." sipStatsSuccessClassOuts Counter32,
REFERENCE sipStatsRedirClassIns Counter32,
"RFC 2543, Sections 5.1.1 & 7.4.3" sipStatsRedirClassOuts Counter32,
::= { sipCommonStatsErrClient 6 } sipStatsReqFailClassIns Counter32,
sipStatsReqFailClassOuts Counter32,
sipStatsServerFailClassIns Counter32,
sipStatsServerFailClassOuts Counter32,
sipStatsGlobalFailClassIns Counter32,
sipStatsGlobalFailClassOuts Counter32
}
sipStatsClientForbiddenIns OBJECT-TYPE sipStatsInfoClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Forbidden (403) "This object reflects the number of 1xx class
responses received by the SIP entity. Inbound Forbidden SIP responses received by the SIP entity.
responses indicate that requests issued by this system are This class of responses relates to providing some
understood by the server but the server refuses to fulfill information concerning the progress of processing
the request. Authorization will not help and the requests a SIP request."
should not be repeated."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.4" "RFC 2543, Sections 5.1.1 & 7.1"
::= { sipCommonStatsErrClient 7 } ::= { sipStatusCodesEntry 1 }
sipStatsClientForbiddenOuts OBJECT-TYPE sipStatsInfoClassOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Forbidden (403) "This object reflects the number of 1xx class
responses sent by the SIP entity. Outbound Forbidden SIP responses sent by the SIP entity.
responses indicate that requests received by this system This class of responses relates to providing some
are understood but this system is refusing to information concerning the progress of processing
fulfill the requests." a SIP request."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.4" "RFC 2543, Sections 5.1.1 & 7.1"
::= { sipCommonStatsErrClient 8 } ::= { sipStatusCodesEntry 2 }
sipStatsClientNotFoundIns OBJECT-TYPE sipStatsSuccessClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Not Found (404) "This object reflects the number of 2xx class SIP
responses received by the SIP entity. responses received by the SIP entity. This class of
Inbound Not Found responses indicate that the called party responses relate to successful completion of a SIP
does not exist at the domain specified in the Request-URI
or the domain is not handled by the recipient of the
request." request."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.5"
::= { sipCommonStatsErrClient 9 }
sipStatsClientNotFoundOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Not Found (404)
responses sent by the SIP entity.
Outbound Not Found responses indicate that this system
knows that the called party does not exist at the domain
specified in the Request-URI or the domain is not handled
by this system."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.5"
::= { sipCommonStatsErrClient 10 }
sipStatsClientMethNotAllowedIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Method Not
Allowed (405) responses received by the SIP entity.
Inbound Method Not Allowed responses indicate that
requests issued by this system have specified a SIP method
in the Request-Line that is not allowed for the address
identified by the Request-URI."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.6"
::= { sipCommonStatsErrClient 11 }
sipStatsClientMethNotAllowedOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Method Not
Allowed (405) responses sent by the SIP entity.
Outbound Method Not Allowed responses indicate that
requests received by this system have SIP methods
specified in the Request-Line that are not allowed for the
address identified by the Request-URI."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.6"
::= { sipCommonStatsErrClient 12 }
sipStatsClientNotAcceptableIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Not Acceptable
(406) responses received by the SIP entity.
Inbound Not Acceptable responses indicate that the
resources identified by requests issued by this system
cannot generate responses with content characteristics
acceptable to this system according to the accept headers
sent in the requests."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.7"
::= { sipCommonStatsErrClient 13 }
sipStatsClientNotAcceptableOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Not Acceptable
(406) responses sent by the SIP entity.
Outbound Not Acceptable responses indicate that the
resources identified by requests received by this system
cannot generate responses with content characteristics
acceptable to the system sending the requests."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.7"
::= { sipCommonStatsErrClient 14 }
sipStatsClientProxyAuthReqdIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Proxy
Authentication Required (407) responses received by the
SIP entity.
Inbound Proxy Authentication Required responses indicate
that this system must authenticate itself with the proxy
before gaining access to the requested resource."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.8"
::= { sipCommonStatsErrClient 15 }
sipStatsClientProxyAuthReqdOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Proxy
Authenticaion Required (407) responses sent by the SIP
entity.
Outbound Proxy Authentication Required responses indicate
that the systems issuing requests being processed by this
system must authenticate themselves with this system
before gaining access to requested resources."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.8"
::= { sipCommonStatsErrClient 16 }
sipStatsClientReqTimeoutIns OBJECT-TYPE Lingle/Maeng/Walker 26
SYNTAX Counter32 "RFC 2543, Sections 5.1.1 & 7.2"
MAX-ACCESS read-only ::= { sipStatusCodesEntry 3 }
STATUS current
DESCRIPTION
"This object reflects the total number of Request Timeout
(408) responses received by the SIP entity.
Inbound Request Timeout responses indicate that requests
issued by this system are not being processed by the
server within the time indicated in the Expires header of
the request."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.9"
::= { sipCommonStatsErrClient 17 }
sipStatsClientReqTimeoutOuts OBJECT-TYPE sipStatsSuccessClassOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Request Timeout "This object reflects the number of 2xx class SIP
(408) responses sent by the SIP entity. responses sent by the SIP entity. This class of
Outbound Request Timeout responses indicate that this responses relate to successful completion of a SIP
system is not able to produce an appropriate response
within the time indicated in the Expires header of the
request." request."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.9" "RFC 2543, Sections 5.1.1 & 7.2"
::= { sipCommonStatsErrClient 18 } ::= { sipStatusCodesEntry 4 }
sipStatsClientConflictIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Conflict (409)
responses received by the SIP entity.
Inbound Conflict responses indicate that requests issued
by this system could not be completed due to a conflict
with the current state of a requested resource."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.10"
::= { sipCommonStatsErrClient 19 }
sipStatsClientConflictOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Conflict (409)
responses sent by the SIP entity.
Outbound Conflict responses indicate that requests
received by this system could not be completed due to a
conflict with the current state of a requested resource."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.10"
::= { sipCommonStatsErrClient 20 }
sipStatsClientGoneIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Gone (410)
responses received by the SIP entity.
Inbound Gone responses indicate that resources requested
by this system are no longer available at the recipient
server and no forwarding address is known."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.11"
::= { sipCommonStatsErrClient 21 }
sipStatsClientGoneOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Gone (410)
responses sent by the SIP entity.
Outbound Gone responses indicate that the requested
resources are no longer available at this system and
no forwarding address is known."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.11"
::= { sipCommonStatsErrClient 22 }
sipStatsClientLengthRequiredIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Length Required
(411) responses received by the SIP entity.
Inbound Length Required responses indicate that requests
issued by this system are being refused by servers because
of no defined Content-Length header field."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.12"
::= { sipCommonStatsErrClient 23 }
sipStatsClientLengthRequiredOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Length Required
(411) responses sent by the SIP entity.
Outbound Length Required responses indicate that requests
received by this system are being refused because of no
defined Content-Length header field."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.12"
::= { sipCommonStatsErrClient 24 }
sipStatsClientReqEntTooLargeIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Request Entity
Too Large 413) responses received by the SIP entity.
Inbound Request Entity Too Large responses indicate that
requests issued by this system are being refused because
the request is larger than the server is willing or able
to process."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.13"
::= { sipCommonStatsErrClient 25 }
sipStatsClientReqEntTooLargeOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Request Entity
Too Large (413) responses sent by the SIP entity.
Outbound Request Entity Too Large responses indicate that
requests received by this system are larger than this
system is willing or able to process."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.13"
::= { sipCommonStatsErrClient 26 }
sipStatsClientReqURITooLargeIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Request-URI Too
Large (414) responses received by the SIP entity.
Inbound Request-URI Too Large responses indicate that
requests issued by this system are being refused because
the Request-URI is longer than the server is willing or
able to interpret."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.14"
::= { sipCommonStatsErrClient 27 }
sipStatsClientReqURITooLargeOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Request-URI Too
Large (414) responses sent by the SIP entity.
Outbound Request-URI Too Large responses indicate that
Request-URIs received by this system are longer than this
system is willing or able to interpret."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.14"
::= { sipCommonStatsErrClient 28 }
sipStatsClientNoSupMediaTypeIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Unsupported Media
Type (415) responses received by the SIP entity.
Inbound Unsupported Media Type responses indicate that
requests issued by this system are being refused because
the message body of the request is in a format not
supported by the requested resource for the requested
method."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.15"
::= { sipCommonStatsErrClient 29 }
sipStatsClientNoSupMediaTypeOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Unsupported Media
Type (415) responses sent by the SIP entity.
Outbound Unsupported Media Type responses indicate that
the body of requests received by this system are in a
format not supported by the requested resource for the
requested method."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.15"
::= { sipCommonStatsErrClient 30 }
sipStatsClientBadExtensionIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Bad Extension
(420) responses received by the SIP entity.
Inbound Bad Extension responses indicate that the
recipient did not understand the protocol extension
specified in a Require header field."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5.16"
::= { sipCommonStatsErrClient 31 }
sipStatsClientBadExtensionOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Bad Extension
(420) responses sent by the SIP entity.
Outbound Bad Extension responses indicate that this system
did not understand the protocol extension specified in a
Require header field of requests."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.16"
::= { sipCommonStatsErrClient 32 }
sipStatsClientTempNotAvailIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Temporarily Not
Available 480) responses received by the SIP entity.
Inbound Temporarily Not Available responses indicate that
the called party is currently unavailable."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.17"
::= { sipCommonStatsErrClient 33 }
sipStatsClientTempNotAvailOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Temporarily Not
Available (480) responses sent by the SIP entity.
Outbound Temporarily Not Available responses indicate that
the called party's end system was contacted successfully
but the called party is currently unavailable."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.17"
::= { sipCommonStatsErrClient 34 }
sipStatsClientCallLegNoExistIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Call
Leg/Transaction Does Not Exist (481) responses received by
the SIP entity.
Inbound Call Leg/Transaction Does Not Exist responses
indicate that either BYE or CANCEL requests issued by this
system were received by a server and no matching call leg
or transaction existed."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.18"
::= { sipCommonStatsErrClient 35 }
sipStatsClientCallLegNoExistOuts OBJECT-TYPE sipStatsRedirClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Call "This object reflects the number of 3xx class SIP
Leg/Transaction Does Not Exist (481) responses sent by the responses received by the SIP entity. This class of
SIP entity. responses relate to call redirection actions taken
Outbound Call Leg/Transaction Does Not Exist responses by a Redirect Server."
indicate that BYE or CANCEL requests have been received by
this system and no call leg or transaction matching that
request exists."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.18" "RFC 2543, Sections 5.1.1 & 7.3"
::= { sipCommonStatsErrClient 36 } ::= { sipStatusCodesEntry 5 }
sipStatsClientLoopDetectedIns OBJECT-TYPE sipStatsRedirClassOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Loop Detected "This object reflects the number of 3xx class SIP
(482) responses received by the SIP entity. responses sent by the SIP entity. This class of
Inbound Loop Detected responses indicate that requests responses relate to call redirection actions taken
issued by this system were received at servers and the by a Redirect Server."
server found itself in the Via path more than once."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.19" "RFC 2543, Sections 5.1.1 & 7.3"
::= { sipCommonStatsErrClient 37 } ::= { sipStatusCodesEntry 6 }
sipStatsClientLoopDetectedOuts OBJECT-TYPE sipStatsReqFailClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Loop Detected "This object reflects the number of 4xx class SIP
(482) responses sent by the SIP entity. responses received by the SIP entity. This class of
Outbound Loop Detected responses indicate that requests responses reflect request failure by a SIP entity
received by this system contain a Via path with this providing a client function."
system appearing more than once."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.19" "RFC 2543, Sections 5.1.1 & 7.4"
::= { sipCommonStatsErrClient 38 } ::= { sipStatusCodesEntry 7 }
sipStatsClientTooManyHopsIns OBJECT-TYPE Lingle/Maeng/Walker 27
sipStatsReqFailClassOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Too Many Hops "This object reflects the number of 4xx class SIP
(483) responses received by the SIP entity. responses sent by the SIP entity. This class of
Inbound Too Many Hops responses indicate that requests responses reflect request failure by a SIP entity
issued by this system contain more Via entries (hops) than providing a server function."
allowed by the Max-Forwards header field of the requests."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.20" "RFC 2543, Sections 5.1.1 & 7.4"
::= { sipCommonStatsErrClient 39 } ::= { sipStatusCodesEntry 8 }
sipStatsClientTooManyHopsOuts OBJECT-TYPE sipStatsServerFailClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Too Many Hops "This object reflects the number of 5xx class SIP
(483) responses sent by the SIP entity. responses received by the SIP entity. This class of
Outbound Too Many Hops responses indicate that requests responses reflect failure responses received by a
received by this system contain more Via entries (hops) SIP entity providing a client function. These
than are allowed by the Max-Forwards header field of the responses are not definite failures and must not
requests." terminate a search if other possible locations remain
untried."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.20" "RFC 2543, Sections 5.1.1 & 7.5"
::= { sipCommonStatsErrClient 40 } ::= { sipStatusCodesEntry 9 }
sipStatsClientAddrIncompleteIns OBJECT-TYPE sipStatsServerFailClassOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Address "This object reflects the number of 5xx class SIP
Incomplete (484) responses received by the SIP entity. responses sent by the SIP entity. This class of
Inbound Address Incomplete responses indicate that responses reflect failure responses sent by a SIP
requests issued by this system had To addresses or entity providing a server function. These
Request-URIs that were incomplete." responses are not definite failures and must not
terminate a search if other possible locations remain
untried."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.21" "RFC 2543, Sections 5.1.1 & 7.5"
::= { sipCommonStatsErrClient 41 } ::= { sipStatusCodesEntry 10 }
sipStatsClientAddrIncompleteOuts OBJECT-TYPE sipStatsGlobalFailClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Address "This object reflects the number of 6xx class SIP
Incomplete (484) responses sent by the SIP entity. responses received by the SIP entity. This class of
responses reflect failure responses received by a
Outbound Address Incomplete responses indicate that
requests received by this system had To addresses or
Request-URIs that were incomplete."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.21"
::= { sipCommonStatsErrClient 42 }
sipStatsClientAmbiguousIns OBJECT-TYPE Lingle/Maeng/Walker 28
SYNTAX Counter32 SIP entity providing a client function.
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Ambiguous (485)
responses received by the SIP entity.
Inbound Ambiguous responses indicate that requests issued
by this system provided ambiguous address information."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.22"
::= { sipCommonStatsErrClient 43 }
sipStatsClientAmbiguousOuts OBJECT-TYPE The responses generally indicate that a server has
SYNTAX Counter32 definitive information about a particular called party,
MAX-ACCESS read-only not just the particular instance indicated in the
STATUS current Request-URI. All further searches for this user are
DESCRIPTION doomed to failure and pending searches should be
"This object reflects the total number of Ambiguous (485) terminated."
responses sent by the SIP entity.
Outbound Ambiguous responses indicate that requests
received by this system contained ambiguous address
information."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.22" "RFC 2543, Sections 5.1.1 & 7.6"
::= { sipCommonStatsErrClient 44 } ::= { sipStatusCodesEntry 11 }
sipStatsClientBusyHereIns OBJECT-TYPE sipStatsGlobalFailClassOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Busy Here (486) "This object reflects the number of 6xx class SIP
responses received by the SIP entity. responses sent by the SIP entity. This class of
Inbound Busy Here responses indicate that the responses reflect failure responses sent by a SIP
called party is currently not willing or not able to entity providing a server function.
take additional calls."
REFERENCE
"RFC 2543, Section 5.1.1 & 7.4.23"
::= { sipCommonStatsErrClient 45 }
sipStatsClientBusyHereOuts OBJECT-TYPE The responses generally indicate that a server has
SYNTAX Counter32 definitive information about a particular called party,
MAX-ACCESS read-only not just the particular instance indicated in the
STATUS current Request-URI. All further searches for this user are
DESCRIPTION doomed to failure and pending searches should be
"This object reflects the total number of Busy Here (486) terminated."
responses sent by the SIP entity.
Outbound Busy Here responses indicate that the
called party's end system was contacted successfully but
the called party is currently not willing or able to take
additional calls."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4.23" "RFC 2543, Sections 5.1.1 & 7.6"
::= { sipCommonStatsErrClient 46 } ::= { sipStatusCodesEntry 12 }
-- --
-- SIP Server Error Responses Statistics -- support for specific status codes
--
-- The following Inbound counters reflect failure responses received
-- by a SIP entity providing a client function.
--
-- The following Outbound counters reflect failure responses sent by
-- a SIP entity providing a server function.
--
-- Servers generally send these responses to Clients. They are not
-- definite failures and must not terminate a search if other
-- possible locations remain untried.
-- --
sipStatsServerIntErrorIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Internal Server
Error (500) responses received by the SIP entity.
Inbound Internal Server Error responses indicate that
servers to which this system is sending requests have
encountered unexpected conditions that prevent them from
fulfilling the requests."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5.1"
::= { sipCommonStatsErrServer 1 }
sipStatsServerIntErrorOuts OBJECT-TYPE sipCommonStatusCodeTable OBJECT-TYPE
SYNTAX Counter32 SYNTAX SEQUENCE OF SipCommonStatusCodeEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object reflects the total number of Internal Server
Error (500) responses sent by the SIP entity.
Outbound Internal Server Error responses indicate that
this system has encountered unexpected conditions that
prevent it from fulfilling received requests."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5.1"
::= { sipCommonStatsErrServer 2 }
sipStatsServerNotImplementedIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Not Implemented "This table contains the list of SIP status codes which
(501) responses received by the SIP entity. each SIP entity in this system has been requested to
Inbound Not Implemented responses indicate that servers to monitor. The instances of SIP entities are uniquely
which this system is sending requests do not support the identified by applIndex."
functionality required to fulfill the requests." ::= { sipCommonStatusCode 2 }
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5.2"
::= { sipCommonStatsErrServer 3 }
sipStatsServerNotImplementedOuts OBJECT-TYPE sipCommonStatusCodeEntry OBJECT-TYPE
SYNTAX Counter32 SYNTAX SipCommonStatusCodeEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Not Implemented "This row contains information on a particular SIP status
(501) responses sent by the SIP entity. code that the SIP entity has been requested to monitor."
Outbound Not Implemented responses indicate that this
system does not support the functionality required to
fulfill the requests."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5.2"
::= { sipCommonStatsErrServer 4 }
sipStatsServerBadGatewayIns OBJECT-TYPE Lingle/Maeng/Walker 29
SYNTAX Counter32 INDEX { applIndex, sipCommonStatusCodeValue }
MAX-ACCESS read-only ::= { sipCommonStatusCodeTable 1 }
STATUS current
DESCRIPTION
"This object reflects the total number of Bad Gateway (502)
responses received by the SIP entity."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5.3"
::= { sipCommonStatsErrServer 5 }
sipStatsServerBadGatewayOuts OBJECT-TYPE SipCommonStatusCodeEntry ::=
SYNTAX Counter32 SEQUENCE {
MAX-ACCESS read-only sipCommonStatusCodeValue INTEGER,
STATUS current sipCommonStatusCodeIns Counter32,
DESCRIPTION sipCommonStatusCodeOuts Counter32,
"This object reflects the total number of Bad Gateway (502) sipCommonStatusCodeSendNotif TruthValue,
responses sent by the SIP entity." sipCommonStatusCodeStatus RowStatus
REFERENCE }
"RFC 2543, Sections 5.1.1 & 7.5.3"
::= { sipCommonStatsErrServer 6 }
sipStatsServerServiceUnavailIns OBJECT-TYPE sipCommonStatusCodeValue OBJECT-TYPE
SYNTAX Counter32 SYNTAX INTEGER (100..999)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Service "This object contains a SIP status code value that the SIP
Unavailable (503) responses received by the SIP entity. entity has been requested to monitor. All of the other
Inbound Service Unavailable responses indicate that the information in the row is related to this value."
server servicing this system's request is temporarily ::= { sipCommonStatusCodeEntry 1 }
unavailable to handle the request."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5.4"
::= { sipCommonStatsErrServer 7 }
sipStatsServerServiceUnavailOuts OBJECT-TYPE sipCommonStatusCodeIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Service
Unavailable (503) responses sent by the SIP entity.
Outbound Service Unavailable responses indicate that this
system is temporarily unable to handle received requests."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5.4"
::= { sipCommonStatsErrServer 8 }
sipStatsServerGatewayTimeoutIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Gateway Time-out "This object reflects the total number of response messages
(504) responses received by the SIP entity. received by the SIP entity with the status code value
Inbound Gateway Time-out responses indicate that the contained in the sipCommonStatusCodeValue column."
server attempting to complete this system's request did ::= { sipCommonStatusCodeEntry 2 }
not receive a timely response from yet another system it
was accessing to complete the request."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5.5"
::= { sipCommonStatsErrServer 9 }
sipStatsServerGatewayTimeoutOuts OBJECT-TYPE sipCommonStatusCodeOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Gateway Time-out "This object reflects the total number of response messages
(504) responses sent by the SIP entity. sent by the SIP entity with the status code value
Outbound Gateway Time-out responses indicate that this contained in the sipCommonStatusCodeValue column."
system did not receive a timely response from the system ::= { sipCommonStatusCodeEntry 3 }
it had accessed to assist in completing a received
request."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5.5"
::= { sipCommonStatsErrServer 10 }
sipStatsServerBadSipVersionIns OBJECT-TYPE sipCommonStatusCodeSendNotif OBJECT-TYPE
SYNTAX Counter32 SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of SIP Version Not "This object controls whether a notification is sent when
Supported (505) responses received by the SIP entity. the status code value specified in the
Inbound SIP Version Not Supported responses indicate that sipCommonStatusCodeValue column is sent or received.
the server does not support, or refuses to support, the If the value of this object is TRUE, then a notification
SIP protocol version that was used in the request is sent. If it is FALSE, no notification is sent."
message." DEFVAL { false }
REFERENCE ::= { sipCommonStatusCodeEntry 4 }
"RFC 2543, Sections 5.1.1 & 7.5.6"
::= { sipCommonStatsErrServer 11 }
sipStatsServerBadSipVersionOuts OBJECT-TYPE Lingle/Maeng/Walker 30
SYNTAX Counter32 sipCommonStatusCodeStatus OBJECT-TYPE
MAX-ACCESS read-only SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of SIP Version Not "The row status of the entry. This object is required
Supported (505) responses sent by the SIP entity. to create or delete rows remotely by a manager."
Outbound SIP Version Not Supported responses indicate that ::= { sipCommonStatusCodeEntry 5 }
this system does not support, or refuses to support, the
SIP protocol version used in received requests."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5.6"
::= { sipCommonStatsErrServer 12 }
-- --
-- SIP Global Failure Response Statistics -- Transaction Statistics
--
-- The following Inbound counters reflect failure responses received
_- by a SIP entity providing a client function.
--
-- The following Outbound counters reflect failure responses sent by
-- a SIP entity providing a server function.
--
-- Servers generally send these responses to Clients. The responses
-- generally indicate that a server has definitive information about
-- a particular called party, not just the particular instance
-- indicated in the Request-URI. All further searches for this user
-- are doomed to failure and pending searches should be terminated.
-- --
sipStatsGlobalBusyEverywhereIns OBJECT-TYPE sipCurrentTransTable OBJECT-TYPE
SYNTAX Counter32 SYNTAX SEQUENCE OF SipCurrentTransEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object reflects the total number of Busy
Everywhere (600) responses received by the SIP entity.
Inbound Busy Everywhere responses indicate that the
called party's end system was contacted successfully
but the called party is busy and does not want to take
the call at this time."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.6.1"
::= { sipCommonStatsGlobalFail 1 }
sipStatsGlobalBusyEverywhereOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Busy
Everywhere (600) responses sent by the SIP entity.
Outbound Busy Everywhere responses indicate that
this system has successfully contacted a called party's
end system and the called party does not want to take
the call at this time."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.6.1"
::= { sipCommonStatsGlobalFail 2 }
sipStatsGlobalDeclineIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Decline
(603) responses received by the SIP entity.
Decline responses indicate that the called party's end
system was contacted successfully but the called party
explicitly does not want to, or cannot, participate."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.6.2"
::= { sipCommonStatsGlobalFail 3 }
sipStatsGlobalDeclineOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Decline
(603) responses sent by the SIP entity.
Outbound Decline responses indicate that this system
has successfully contacted a called party's end system
and the called party explicitly does not want to, or
cannot, participate."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.6.2"
::= { sipCommonStatsGlobalFail 4 }
sipStatsGlobalNotAnywhereIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of Does Not
Exist Anywhere (604) responses received by the SIP entity.
Inbound Does Not Exist Anywhere responses indicate that
the server handling this system's request has
authoritative information that the called party indicated
in the To request field does not exist anywhere."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.6.3"
::= { sipCommonStatsGlobalFail 5 }
sipStatsGlobalNotAnywhereOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Does Not "This table contains information on the transactions
Exist Anywhere (604) responses sent by the SIP entity. currently awaiting definitive responses by each SIP
Outbound Does Not Exist Anywhere responses indicate that entity in this system. The instances of SIP entities
this system has authoritative information that the called are uniquely identified by applIndex."
party in the To field of received requests does not exist ::= { sipCommonStatsTrans 1 }
anywhere."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.6.3"
::= { sipCommonStatsGlobalFail 6 }
sipStatsGlobalNotAcceptableIns OBJECT-TYPE sipCurrentTransEntry OBJECT-TYPE
SYNTAX Counter32 SYNTAX SipCurrentTransEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Not Acceptable "Information on a particular SIP entities' current
(606) responses received by the SIP entity. transactions."
Inbound Not Acceptable responses indicate that the called INDEX { applIndex }
party's end system was contacted successfully but some ::= { sipCurrentTransTable 1 }
aspect of the session description is not acceptable."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.6.4"
::= { sipCommonStatsGlobalFail 7 }
sipStatsGlobalNotAcceptableOuts OBJECT-TYPE SipCurrentTransEntry ::=
SYNTAX Counter32 SEQUENCE {
MAX-ACCESS read-only sipCurrentTransactions Gauge32
STATUS current }
DESCRIPTION
"This object reflects the total number of Not Acceptable
(606) responses sent by the SIP entity.
Outbound Not Acceptable responses indicate that the called
party wishes to communicate, but cannot adequately support
the session described in the request."
REFERENCE
"RFC 2543, Sections 5.1.1 & 7.6.4"
::= { sipCommonStatsGlobalFail 8 }
--
-- Transaction Statistics
--
sipCurrentTransactions OBJECT-TYPE sipCurrentTransactions OBJECT-TYPE
SYNTAX Gauge32 (0..4294967295) SYNTAX Gauge32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the number of transactions awaiting "This object contains the number of transactions awaiting
definitive (non-1xx) response. In the case of a forked definitive (non-1xx) response. In the case of a forked
request, all branches count as a single transaction. The request, all branches count as a single transaction. The
value of this object will reflect the number of rows in value of this object will reflect the number of rows in
sipTransactionTable." sipTransactionTable."
::= { sipCommonStatsTrans 1 } ::= { sipCurrentTransEntry 1 }
sipTransactionTable OBJECT-TYPE sipTransactionTable OBJECT-TYPE
Lingle/Maeng/Walker 31
SYNTAX SEQUENCE OF SipTransactionEntry SYNTAX SEQUENCE OF SipTransactionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on all of the transactions "This table contains information on all of the transactions
currently being processed (the count of such transactions currently being processed (the count of such transactions
is maintained in the sipCurrentTransactions object)." is maintained in the sipCurrentTransactions object) by a
particular SIP entity in this system. The instances of SIP
entities are uniquely identified by applIndex."
::= { sipCommonStatsTrans 2 } ::= { sipCommonStatsTrans 2 }
sipTransactionEntry OBJECT-TYPE sipTransactionEntry OBJECT-TYPE
SYNTAX SipTransactionEntry SYNTAX SipTransactionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular current transaction." "Information on a particular current transaction."
INDEX { sipTransIndex } INDEX { applIndex, sipTransIndex }
::= { sipTransactionTable 1 } ::= { sipTransactionTable 1 }
SipTransactionEntry ::= SipTransactionEntry ::=
SEQUENCE { SEQUENCE {
sipTransIndex Unsigned32, sipTransIndex Unsigned32,
sipTransTo SnmpAdminString, sipTransTo SnmpAdminString,
sipTransFrom SnmpAdminString, sipTransFrom SnmpAdminString,
sipTransCallId SnmpAdminString, sipTransCallId SnmpAdminString,
sipTransCSeq Unsigned32, sipTransCSeq Unsigned32,
sipTransState INTEGER, sipTransState INTEGER,
sipTransOutstandingBranches Integer32, sipTransNumOutstandingBranches Integer32,
sipTransExpiry DateAndTime, sipTransExpiry DateAndTime,
sipTransCallingPartyContentType SnmpAdminString, sipTransCallingPartyContentType SnmpAdminString,
sipTransCalledPartyContentType SnmpAdminString sipTransCalledPartyContentType SnmpAdminString
} }
sipTransIndex OBJECT-TYPE sipTransIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 41, line 21 skipping to change at line 1768
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the To header in request "This object contains the value of the To header in request
message." message."
::= { sipTransactionEntry 2 } ::= { sipTransactionEntry 2 }
sipTransFrom OBJECT-TYPE sipTransFrom OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
Lingle/Maeng/Walker 32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the From header in the "This object contains the value of the From header in the
request message." request message."
::= { sipTransactionEntry 3 } ::= { sipTransactionEntry 3 }
sipTransCallId OBJECT-TYPE sipTransCallId OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 42, line 15 skipping to change at line 1824
initial(2) : Prior to sending or receiving any initial(2) : Prior to sending or receiving any
request. request.
calling(3) : After sending the request and prior to calling(3) : After sending the request and prior to
receiving any response. receiving any response.
ringing(4) : After receiving one or more ringing(4) : After receiving one or more
informational (1xx) responses. informational (1xx) responses.
completed(5) : After ACK has been sent following completed(5) : After ACK has been sent following
reception of definitive response. reception of definitive response.
callProceeding(6) : Entered on reception of an INVITE. callProceeding(6) : Entered on reception of an INVITE.
failure(7) : Entered when call fails(send status failure(7) : Entered when call fails(send status
Lingle/Maeng/Walker 33
code>=300). code>=300).
success(8) : Entered when user answers(send status success(8) : Entered when user answers(send status
code=200). code=200).
confirmed(9) : Entered on reception of an ACK in confirmed(9) : Entered on reception of an ACK in
failure or success states." failure or success states."
REFERENCE REFERENCE
"RFC 2543, Figures 12 and 13" "RFC 2543, Figures 12 and 13"
::= { sipTransactionEntry 6 } ::= { sipTransactionEntry 6 }
sipTransOutstandingBranches OBJECT-TYPE sipTransNumOutstandingBranches OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of branches "This object contains a count of the number of branches
awaiting a final response. Only a forking proxy will have awaiting a final response. Only a forking proxy will have
a value greater than one." a value greater than one."
::= { sipTransactionEntry 7 } ::= { sipTransactionEntry 7 }
sipTransExpiry OBJECT-TYPE sipTransExpiry OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an indication of when the transaction "This object contains an indication of when the transaction
will be considered to have timed out. This value is based will be considered to have timed out. This value is based
on the value in the Expires header, or the value of the on the value in the Expires header, or the value of the
sipRequestDfltExpires object if no Expires value was sipInviteTimeout object if no Expires value was
specified in the original request." specified in the original request."
::= { sipTransactionEntry 8 } ::= { sipTransactionEntry 8 }
sipTransCallingPartyContentType OBJECT-TYPE sipTransCallingPartyContentType OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the content type of the transaction, "This object contains the content type of the transaction,
including parameters, as indicated by the session including parameters, as indicated by the session
skipping to change at page 43, line 7 skipping to change at line 1880
::= { sipTransactionEntry 9 } ::= { sipTransactionEntry 9 }
sipTransCalledPartyContentType OBJECT-TYPE sipTransCalledPartyContentType OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the content type of the transaction, "This object contains the content type of the transaction,
including parameters, as indicated by the session including parameters, as indicated by the session
respondant. All optional white space is removed from respondant. All optional white space is removed from
Lingle/Maeng/Walker 34
subfields in the media-type specification. It may subfields in the media-type specification. It may
indicate mime multipart, in which case the multiple indicate mime multipart, in which case the multiple
entries are separated by spaces." entries are separated by spaces."
REFERENCE REFERENCE
"RFC 2543, Section 6.16 and RFC 2068, Section 3.7" "RFC 2543, Section 6.16 and RFC 2068, Section 3.7"
::= { sipTransactionEntry 10 } ::= { sipTransactionEntry 10 }
-- --
-- Other Common Statistics -- Other Common Statistics
-- --
sipOtherStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipOtherStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains other common statistics supported by
each SIP entity in this system. The instances of SIP
entities are uniquely identified by applIndex."
::= { sipCommonStats 5 }
sipOtherStatsEntry OBJECT-TYPE
SYNTAX SipOtherStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information on a particular SIP entities' other common
statistics."
INDEX { applIndex }
::= { sipOtherStatsTable 1 }
SipOtherStatsEntry ::=
SEQUENCE {
sipNumUnsupportedUris Counter32
}
sipNumUnsupportedUris OBJECT-TYPE sipNumUnsupportedUris OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of RequestURIs received with unsupported scheme. "Number of RequestURIs received with unsupported scheme.
A server normally responds to such requests with a 400 Bad A server normally responds to such requests with a 400 Bad
Request status code." Request status code."
::= { sipCommonStats 10 } ::= { sipOtherStatsEntry 5 }
--
-- Notifications
--
sipCommonMIBNotifPrefix OBJECT IDENTIFIER ::= { sipCommonMIB 7 }
sipCommonMIBNotif OBJECT IDENTIFIER ::= {
sipCommonMIBNotifPrefix 0 }
Lingle/Maeng/Walker 35
sipStatusCodeNotif NOTIFICATION-TYPE
OBJECTS {
sipStatusCodeNotifValue,
sipStatusCodeNotifTo,
sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId,
sipStatusCodeNotifCSeq
}
STATUS current
DESCRIPTION
"Signifies that a specific status code has been used."
::= { sipCommonMIBNotif 1 }
sipStatusCodeNotifValue OBJECT-TYPE
SYNTAX INTEGER (100..999)
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This object contains the status code that caused the
notification."
::= { sipCommonMIBNotif 2 }
sipStatusCodeNotifTo OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This object contains the value of the To header in the
message containing the status code that caused the
notification."
::= { sipCommonMIBNotif 3 }
sipStatusCodeNotifFrom OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This object contains the value of the From header in the
message containing the status code that caused the
notification."
::= { sipCommonMIBNotif 4 }
sipStatusCodeNotifCallId OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This object contains the value of the CallId in the
message containing the status code that caused the
notification."
::= { sipCommonMIBNotif 5 }
sipStatusCodeNotifCSeq OBJECT-TYPE
SYNTAX Unsigned32
Lingle/Maeng/Walker 36
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This object contains the CSeq value in the message
containing the status code that caused the notification."
::= { sipCommonMIBNotif 6 }
--
-- Conformance
--
sipCommonMIBConformance
OBJECT IDENTIFIER ::= { sipCommonMIB 6 }
sipCommonMIBCompliances
OBJECT IDENTIFIER ::= { sipCommonMIBConformance 1 }
sipCommonMIBGroups
OBJECT IDENTIFIER ::= { sipCommonMIBConformance 2 }
--
-- Compliance Statements
--
sipCommonCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SIP entities."
MODULE -- this module
MANDATORY-GROUPS { sipCommonConfigGroup,
sipCommonStatsGroup,
sipCommonNotifGroup }
::= { sipCommonMIBCompliances 1 }
--
-- Units of Conformance
--
sipCommonConfigGroup OBJECT-GROUP
OBJECTS {
sipProtocolVersion,
sipServiceOperStatus,
sipServiceAdminStatus,
sipServiceStartTime,
sipServiceLastChange,
sipTransport,
sipPortStatus,
sipUriSupported,
sipFtrSupported,
sipOrganization,
sipMaxTransactions,
sipInviteTimeout,
sipHideOperation,
sipUserLocationServerAddr,
Lingle/Maeng/Walker 37
sipCanUseCompact,
sipRequestUriHostMatching,
sipStatusCodeNotifValue,
sipStatusCodeNotifTo,
sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId,
sipStatusCodeNotifCSeq
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration common
to all SIP enities."
::= { sipCommonMIBGroups 1 }
sipCommonStatsGroup OBJECT-GROUP
OBJECTS {
sipSummaryInRequests,
sipSummaryOutRequests,
sipSummaryInResponses,
sipSummaryOutResponses,
sipSummaryTotalTransactions,
sipStatsInviteIns,
sipStatsInviteOuts,
sipStatsAckIns,
sipStatsAckOuts,
sipStatsByeIns,
sipStatsByeOuts,
sipStatsCancelIns,
sipStatsCancelOuts,
sipStatsOptionsIns,
sipStatsOptionsOuts,
sipStatsRegisterIns,
sipStatsRegisterOuts,
sipStatsExtMethodName,
sipStatsExtMethodIns,
sipStatsExtMethodOuts,
sipStatsExtMethodStatus,
sipStatsInfoClassIns,
sipStatsInfoClassOuts,
sipStatsSuccessClassIns,
sipStatsSuccessClassOuts,
sipStatsRedirClassIns,
sipStatsRedirClassOuts,
sipStatsReqFailClassIns,
sipStatsReqFailClassOuts,
sipStatsServerFailClassIns,
sipStatsServerFailClassOuts,
sipStatsGlobalFailClassIns,
sipStatsGlobalFailClassOuts,
sipCommonStatusCodeIns,
sipCommonStatusCodeOuts,
sipCommonStatusCodeSendNotif,
sipCommonStatusCodeStatus,
sipCurrentTransactions,
Lingle/Maeng/Walker 38
sipTransTo,
sipTransFrom,
sipTransCallId,
sipTransCSeq,
sipTransState,
sipTransNumOutstandingBranches,
sipTransExpiry,
sipTransCallingPartyContentType,
sipTransCalledPartyContentType,
sipNumUnsupportedUris
}
STATUS current
DESCRIPTION
"A collection of objects providing statistics common
toall SIP entities."
::= { sipCommonMIBGroups 2 }
sipCommonNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS {
sipStatusCodeNotif
}
STATUS current
DESCRIPTION
"A collection of notifications common to all SIP entities."
::= { sipCommonMIBGroups 3 }
END
5.4. SIP User Agent
SIP-UA-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Counter32,
Integer32
FROM SNMPv2-SMI
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF
sipMIB
FROM SIP-MIB-SMI
applIndex
FROM NETWORK-SERVICES-MIB;
sipUAMIB MODULE-IDENTITY
LAST-UPDATED "200007080000Z"
Lingle/Maeng/Walker 39
ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO
"SIP MIB Team email: sip-mib@egroups.com
Co-editor Kevin Lingle
Cisco Systems, Inc.
postal: 7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709
USA
email: klingle@cisco.com
phone: +1-919-392-2029
Co-editor Joon Maeng
VTEL Corporation
postal: 108 Wild Basin Rd.
Austin, TX 78746
USA
email: joon_maeng@vtel.com
phone: +1-512-437-4567
Co-editor Dave Walker
SS8 Networks, Inc.
postal: 80 Hines Road
Kanata, ON K2K 2T8
Canada
email: drwalker@ss8networks.com
phone: +1 613 592 2100"
DESCRIPTION
"Initial version of Session Initiation Protocol (SIP)
User Agent (UA) MIB module.
SIP is an application-layer signalling protocol for
creating, modifying and terminating multimedia
sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 2543 (March
1999).
A User Agent is an application that contains both a
User Agent Client (UAC) and a User Agent Server (UAS).
A UAC is an application that initiates a SIP request.
A UAS is an application that contacts the user when a
SIP request is received and that returns a response on
behalf of the user. The response accepts, rejects, or
redirects the request."
::= { sipMIB 3 }
-- --
-- sipUA group -- sipUA group
-- This group contains MIB objects related to SIP User Agents. -- This group contains MIB objects related to SIP User Agents.
-- --
sipUACfg OBJECT IDENTIFIER ::= { sipUA 1 } sipUACfg OBJECT IDENTIFIER ::= { sipUAMIB 1 }
Lingle/Maeng/Walker 40
sipUACfgTimer OBJECT IDENTIFIER ::= { sipUACfg 1 } sipUACfgTimer OBJECT IDENTIFIER ::= { sipUACfg 1 }
sipUACfgRetry OBJECT IDENTIFIER ::= { sipUACfg 2 } sipUACfgRetry OBJECT IDENTIFIER ::= { sipUACfg 2 }
sipUAStats OBJECT IDENTIFIER ::= { sipUA 2 } sipUAStats OBJECT IDENTIFIER ::= { sipUAMIB 2 }
sipUAStatsRetry OBJECT IDENTIFIER ::= { sipUAStats 1 } sipUAStatsRetry OBJECT IDENTIFIER ::= { sipUAStats 1 }
-- --
-- User Agent Configuration -- User Agent Configuration
-- --
-- --
-- SIP Timer Configuration -- SIP Timer Configuration
-- --
sipUACfgTimerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUACfgTimerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains timer configuration objects applicable
to each SIP user agent in this system. The instances of
SIP entities are uniquely identified by applIndex."
::= { sipUACfgTimer 1 }
sipUACfgTimerEntry OBJECT-TYPE
SYNTAX SipUACfgTimerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of timer configuration."
INDEX { applIndex }
::= { sipUACfgTimerTable 1 }
SipUACfgTimerEntry ::=
SEQUENCE {
sipUACfgTimerTrying Integer32,
sipUACfgTimerProv Integer32,
sipUACfgTimerAck Integer32,
sipUACfgTimerDisconnect Integer32,
sipUACfgTimerReRegister Integer32
}
sipUACfgTimerTrying OBJECT-TYPE sipUACfgTimerTrying OBJECT-TYPE
SYNTAX Integer32 (100..1000) SYNTAX Integer32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the time a user agent will wait to "This object specifies the time a user agent will wait to
receive a provisional response to an INVITE before receive a provisional response to an INVITE before
resending the INVITE." resending the INVITE."
::= { sipUACfgTimer 1 } ::= { sipUACfgTimerEntry 1 }
sipUACfgTimerExpires OBJECT-TYPE sipUACfgTimerProv OBJECT-TYPE
SYNTAX Integer32 (60000..300000) SYNTAX Integer32 (60000..300000)
Lingle/Maeng/Walker 41
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the time a user agent will wait to "This object specifies the time a user agent will wait to
receive a final response to an INVITE before canceling the receive a final response to an INVITE before canceling the
transaction." transaction."
::= { sipUACfgTimer 2 } ::= { sipUACfgTimerEntry 2 }
sipUACfgTimerConnect OBJECT-TYPE sipUACfgTimerAck OBJECT-TYPE
SYNTAX Integer32 (100..1000) SYNTAX Integer32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the time a user agent will wait to "This object specifies the time a user agent will wait to
receive an ACK confirmation indicating that a session is receive an ACK confirmation indicating that a session is
established." established."
::= { sipUACfgTimer 3 } ::= { sipUACfgTimerEntry 3 }
sipUACfgTimerDisconnect OBJECT-TYPE sipUACfgTimerDisconnect OBJECT-TYPE
SYNTAX Integer32 (100..1000) SYNTAX Integer32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the time a user agent will wait to "This object specifies the time a user agent will wait to
receive a BYE confirmation indicating that a session is receive a BYE confirmation indicating that a session is
disconnected." disconnected."
::= { sipUACfgTimer 4 } ::= { sipUACfgTimerEntry 4 }
sipUACfgTimerReRegister OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies how long the user agent wishes its
registrations to be valid."
::= { sipUACfgTimerEntry 5 }
-- --
-- SIP Retry Configuration -- SIP Retry Configuration
-- --
sipUACfgRetryTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUACfgRetryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains retry configuration objects applicable
to each SIP user agent in this system. The instances of
SIP entities are uniquely identified by applIndex."
::= { sipUACfgRetry 1 }
Lingle/Maeng/Walker 42
sipUACfgRetryEntry OBJECT-TYPE
SYNTAX SipUACfgRetryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of retry configuration."
INDEX { applIndex }
::= { sipUACfgRetryTable 1 }
SipUACfgRetryEntry ::=
SEQUENCE {
sipUACfgRetryInvite Integer32,
sipUACfgRetryBye Integer32,
sipUACfgRetryCancel Integer32,
sipUACfgRetryRegister Integer32,
sipUACfgRetryResponse Integer32
}
sipUACfgRetryInvite OBJECT-TYPE sipUACfgRetryInvite OBJECT-TYPE
SYNTAX Integer32 (1..10) SYNTAX Integer32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a user agent "This object will specify the number of times a user agent
will retry sending an INVITE request." will retry sending an INVITE request."
::= { sipUACfgRetry 1 } ::= { sipUACfgRetryEntry 1 }
sipUACfgRetryBye OBJECT-TYPE sipUACfgRetryBye OBJECT-TYPE
SYNTAX Integer32 (1..10) SYNTAX Integer32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a user agent "This object will specify the number of times a user agent
will retry sending a BYE request." will retry sending a BYE request."
::= { sipUACfgRetry 2 } ::= { sipUACfgRetryEntry 2 }
sipUACfgRetryCancel OBJECT-TYPE sipUACfgRetryCancel OBJECT-TYPE
SYNTAX Integer32 (1..10) SYNTAX Integer32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a user agent "This object will specify the number of times a user agent
will retry sending a CANCEL request." will retry sending a CANCEL request."
::= { sipUACfgRetry 3 } ::= { sipUACfgRetryEntry 3 }
sipUACfgRetryRegister OBJECT-TYPE sipUACfgRetryRegister OBJECT-TYPE
SYNTAX Integer32 (1..10) SYNTAX Integer32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a user agent "This object will specify the number of times a user agent
will retry sending a REGISTER request." will retry sending a REGISTER request."
::= { sipUACfgRetry 4 } ::= { sipUACfgRetryEntry 4 }
Lingle/Maeng/Walker 43
sipUACfgRetryResponse OBJECT-TYPE sipUACfgRetryResponse OBJECT-TYPE
SYNTAX Integer32 (1..10) SYNTAX Integer32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a user agent "This object will specify the number of times a user agent
will retry sending a Response and expecting an ACK." will retry sending a Response and expecting an ACK."
::= { sipUACfgRetry 5 } ::= { sipUACfgRetryEntry 5 }
-- --
-- User Agent Statistics -- User Agent Statistics
-- --
-- --
-- SIP Retry Statistics -- SIP Retry Statistics
-- --
-- The counter objects in this group correspond directly to the -- The counter objects in this group correspond directly to the
-- retry timers supported in sipCfgRetry group. -- retry timers supported in sipCfgRetry group. applIndex can
-- be used to correlate the two groups.
--
-- --
sipUAStatsRetryTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUAStatsRetryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains retry statistics objects applicable
to each SIP user agent in this system. The instances of
SIP entities are uniquely identified by applIndex."
::= { sipUAStatsRetry 1 }
sipUAStatsRetryEntry OBJECT-TYPE
SYNTAX SipUAStatsRetryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of retry statistics."
INDEX { applIndex }
::= { sipUAStatsRetryTable 1 }
SipUAStatsRetryEntry ::=
SEQUENCE {
sipStatsRetryInvites Counter32,
sipStatsRetryByes Counter32,
sipStatsRetryCancels Counter32,
sipStatsRetryRegisters Counter32,
sipStatsRetryResponses Counter32
}
sipStatsRetryInvites OBJECT-TYPE sipStatsRetryInvites OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
Lingle/Maeng/Walker 44
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE retries "This object reflects the total number of INVITE retries
that have been sent by the user agent. If the number of that have been sent by the user agent. If the number of
'first attempt' INVITES is of interest, subtract the value 'first attempt' INVITES is of interest, subtract the value
of this object from sipStatsTrafficInviteOut." of this object from sipStatsTrafficInviteOut."
::= { sipUAStatsRetry 1 } ::= { sipUAStatsRetryEntry 1 }
sipStatsRetryByes OBJECT-TYPE sipStatsRetryByes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of BYE retries that "This object reflects the total number of BYE retries that
have been sent by the user agent." have been sent by the user agent."
::= { sipUAStatsRetry 2 } ::= { sipUAStatsRetryEntry 2 }
sipStatsRetryCancels OBJECT-TYPE sipStatsRetryCancels OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of CANCEL retries "This object reflects the total number of CANCEL retries
that have been sent by the user agent." that have been sent by the user agent."
::= { sipUAStatsRetry 3 } ::= { sipUAStatsRetryEntry 3 }
sipStatsRetryRegisters OBJECT-TYPE sipStatsRetryRegisters OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of REGISTER retries "This object reflects the total number of REGISTER retries
that have been sent by the user agent." that have been sent by the user agent."
::= { sipUAStatsRetry 4 } ::= { sipUAStatsRetryEntry 4 }
sipStatsRetryResponses OBJECT-TYPE sipStatsRetryResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Response (while "This object reflects the total number of Response (while
expecting an ACK) retries that have been sent by the user expecting an ACK) retries that have been sent by the user
agent." agent."
::= { sipUAStatsRetry 5 } ::= { sipUAStatsRetryEntry 5 }
--
-- Notifications
--
sipUAMIBNotif OBJECT IDENTIFIER ::= { sipUAMIB 3 }
-- none at this time
Lingle/Maeng/Walker 45
--
-- Conformance
--
sipUAMIBConformance
OBJECT IDENTIFIER ::= { sipUAMIB 4 }
sipUAMIBCompliances
OBJECT IDENTIFIER ::= { sipUAMIBConformance 1 }
sipUAMIBGroups
OBJECT IDENTIFIER ::= { sipUAMIBConformance 2 }
--
-- Compliance Statements
--
sipUACompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SIP entities."
MODULE -- this module
MANDATORY-GROUPS { sipUAConfigGroup,
sipUAStatsGroup }
-- sipUANotifGroup }
::= { sipUAMIBCompliances 1 }
--
-- Units of Conformance
--
sipUAConfigGroup OBJECT-GROUP
OBJECTS {
sipUACfgTimerTrying,
sipUACfgTimerProv,
sipUACfgTimerAck,
sipUACfgTimerDisconnect,
sipUACfgTimerReRegister,
sipUACfgRetryInvite,
sipUACfgRetryBye,
sipUACfgRetryCancel,
sipUACfgRetryRegister,
sipUACfgRetryResponse
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration for
SIP User Agents."
::= { sipUAMIBGroups 1 }
sipUAStatsGroup OBJECT-GROUP
OBJECTS {
sipStatsRetryInvites,
sipStatsRetryByes,
sipStatsRetryCancels,
Lingle/Maeng/Walker 46
sipStatsRetryRegisters,
sipStatsRetryResponses
}
STATUS current
DESCRIPTION
"A collection of objects providing statistics for
SIP User Agents."
::= { sipUAMIBGroups 2 }
--sipUANotifGroup NOTIFICATION-GROUP
-- OBJECTS {
-- none at this time
-- }
-- STATUS current
-- DESCRIPTION
-- "A collection of notifications defined for SIP User
-- Agents."
-- ::= { sipMIBGroups 3 }
END
5.5. SIP Redirect & Proxy Server
SIP-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Counter32,
Integer32,
Unsigned32
FROM SNMPv2-SMI
RowStatus,
TruthValue
FROM SNMPv2-TC
MODULE-COMPLIANCE,
OBJECT-GROUP
FROM SNMPv2-CONF
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
SipServerActions
FROM SIP-TC
sipMIB
FROM SIP-MIB-SMI
applIndex
FROM NETWORK-SERVICES-MIB;
Lingle/Maeng/Walker 47
sipServerMIB MODULE-IDENTITY
LAST-UPDATED "200007080000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO
"SIP MIB Team email: sip-mib@egroups.com
Co-editor Kevin Lingle
Cisco Systems, Inc.
postal: 7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709
USA
email: klingle@cisco.com
phone: +1-919-392-2029
Co-editor Joon Maeng
VTEL Corporation
postal: 108 Wild Basin Rd.
Austin, TX 78746
USA
email: joon_maeng@vtel.com
phone: +1-512-437-4567
Co-editor Dave Walker
SS8 Networks, Inc.
postal: 80 Hines Road
Kanata, ON K2K 2T8
Canada
email: drwalker@ss8networks.com
phone: +1 613 592 2100"
DESCRIPTION
"Initial version of Session Initiation Protocol (SIP)
Server MIB module.
SIP is an application-layer signalling protocol for
creating, modifying and terminating multimedia
sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 2543 (March
1999).
This MIB is defined for the management of SIP Proxy
and Redirect Servers.
A Proxy Server acts as both a client and a server.
It accepts requests from other clients, either
responding to them or passing them on to other
servers, possibly after modification.
A Redirect Server accepts requests from clients and
returns zero or more addresses to that client. Unlike
a Proxy server it does not initiate requests. Unlike
a User Agent Server it does not accept calls."
Lingle/Maeng/Walker 48
::= { sipMIB 4 }
-- --
-- sipServer group -- sipServer group
-- This group contains MIB objects common to Proxy and Redirect -- This group contains MIB objects common to Proxy and Redirect
-- Servers. -- Servers.
-- --
sipServerCfg OBJECT IDENTIFIER ::= { sipServer 1 } sipServerCfg OBJECT IDENTIFIER ::= { sipServerMIB 1 }
sipServerStats OBJECT IDENTIFIER ::= { sipServer 2 } sipServerStats OBJECT IDENTIFIER ::= { sipServerMIB 2 }
-- --
-- Common Server Configuration Objects -- Common Server Configuration Objects
-- --
sipServerCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains configuration objects applicable
to SIP redirect and proxy servers. Each row represents
those objects for a particular SIP server present in
this system. The instances of SIP servers are uniquely
identified by applIndex."
::= { sipServerCfg 1 }
sipServerCfgEntry OBJECT-TYPE
SYNTAX SipServerCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of common configuration."
INDEX { applIndex }
::= { sipServerCfgTable 1 }
SipServerCfgEntry ::=
SEQUENCE {
sipServerHost SnmpAdminString,
sipInformationAlwaysSendTrying TruthValue,
sipInformationTryingInterval Integer32,
sipPgpVersion SnmpAdminString,
sipServerDfltAction SipServerActions,
sipServerRespectUAAction TruthValue
}
sipServerHost OBJECT-TYPE sipServerHost OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the host portion of a SIP URL that is assigned "This is the host portion of a SIP URL that is assigned
to the SIP server. It may contain a fully qualified to the SIP server. It may contain a fully qualified
domain name, or an IP address (v4 only for now)." domain name, or an IP address (v4 only for now)."
REFERENCE REFERENCE
Lingle/Maeng/Walker 49
"RFC 2543, Section 2" "RFC 2543, Section 2"
::= { sipServerCfg 1 } ::= { sipServerCfgEntry 1 }
-- --
-- Support for 1xx Status Codes -- Support for 1xx Status Codes
-- --
sipInformationTryingInitial OBJECT-TYPE sipInformationAlwaysSendTrying OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true, the server sends 100 Trying when a "If this object is true, the server sends 100 Trying when a
request is processed." request is processed."
::= { sipServerCfg 2 } ::= { sipServerCfgEntry 2 }
sipInformationTryingInterval OBJECT-TYPE sipInformationTryingInterval OBJECT-TYPE
SYNTAX Integer32 (0..60000) SYNTAX Integer32 (0..60000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Server sends a 100 Trying at intervals of this duration "Server sends a 100 Trying at intervals of this duration
as counted from when the request was processed. If the as counted from when the request was processed. If the
value is zero, no such retransmission is performed." value is zero, no such retransmission is performed."
::= { sipServerCfg 3 } ::= { sipServerCfgEntry 3 }
-- --
-- Security -- Security
-- --
sipPgpVersion OBJECT-TYPE sipPgpVersion OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the version of PGP (Pretty Good "This object indicates the version of PGP (Pretty Good
Privacy) supported by this server. Common values are Privacy) supported by this server. Common values are
2.6.2 and 5.0." 2.6.2 and 5.0."
::= { sipServerCfg 4 } ::= { sipServerCfgEntry 4 }
-- --
-- Additional Server Configuration -- Additional Server Configuration
-- --
sipServerDfltAction OBJECT-TYPE sipServerDfltAction OBJECT-TYPE
SYNTAX SipServerActions SYNTAX SipServerActions
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether the default action of the "This object specifies whether the default action of the
server is to be a proxy server or a redirect server. A server is to be a proxy server or a redirect server. A
User Agent may indicate a preference upon registration of User Agent may indicate a preference upon registration of
Contact information. The value of this object is used in Contact information. The value of this object is used in
the absence of such an indication." the absence of such an indication."
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
::= { sipServerCfg 5 }
Lingle/Maeng/Walker 50
::= { sipServerCfgEntry 5 }
sipServerRespectUAAction OBJECT-TYPE sipServerRespectUAAction OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether the server should respect "This object specifies whether the server should respect
the wishes of a User Agent when the UA specifies a server the wishes of a User Agent when the UA specifies a server
action (proxy or redirect) for certain Contact action (proxy or redirect) for certain Contact
information. If the value of this object is false, then information. If the value of this object is false, then
the value contained in the sipServerDfltAction is used." the value contained in the sipServerDfltAction is used."
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
::= { sipServerCfg 6 } ::= { sipServerCfgEntry 6 }
sipRequestUriHostMatching OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies whether or not the host in
RequestURI must match server's host name.
If the value of this object is TRUE, then the server
requires a match, and if the RequestURI doesn't match the
server's host name, a 404 Not Found status code is
returned by the server.
If the value is FALSE, then no match is required."
REFERENCE
"RFC 2543, Section 4.3"
::= { sipServerCfg 7 }
-- --
-- Common Server Statistics -- Common Server Statistics
-- --
-- none at this time -- none at this time
-- sipProxy group -- sipProxy group
-- This group contains MIB objects related to SIP Proxy Servers. -- This group contains MIB objects related to SIP Proxy Servers.
-- --
sipProxy OBJECT IDENTIFIER ::= { sipServerMIB 3 }
sipProxyCfg OBJECT IDENTIFIER ::= { sipProxy 1 } sipProxyCfg OBJECT IDENTIFIER ::= { sipProxy 1 }
sipProxyStats OBJECT IDENTIFIER ::= { sipProxy 2 } sipProxyStats OBJECT IDENTIFIER ::= { sipProxy 2 }
-- --
-- Proxy Server Configration -- Proxy Server Configuration
-- --
sipProxyCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipProxyCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains configuration objects applicable
to SIP proxy servers. Each row represents those objects
for a particular SIP proxy server present in this system.
The instances of SIP proxy servers are uniquely identified
by applIndex."
::= { sipProxyCfg 1 }
sipProxyCfgEntry OBJECT-TYPE
SYNTAX SipProxyCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of common configuration."
INDEX { applIndex }
Lingle/Maeng/Walker 51
::= { sipProxyCfgTable 1 }
SipProxyCfgEntry ::=
SEQUENCE {
sipRequestMaxExpires Unsigned32,
sipProxyStateful TruthValue,
sipProxySendsCancel TruthValue,
sipProxyForwardAll1xx TruthValue,
sipProxyRecursion TruthValue,
sipProxyProvideAlternatives TruthValue,
sipProxyRecordRoute TruthValue,
sipProxyStateTimeout Integer32,
sipProxyAuthMethod INTEGER,
sipProxyAuthPgpAlgorithm INTEGER,
sipProxyAuthRealm SnmpAdminString,
sipProxyNonceLifeTime Integer32,
sipPgpPrivateKey OCTET
STRING(SIZE(0..255)),
sipHideRespect TruthValue
}
sipRequestMaxExpires OBJECT-TYPE sipRequestMaxExpires OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum duration that a SIP "This object specifies the maximum duration that a SIP
proxy server will accept from a client in the Expires proxy server will accept from a client in the Expires
header. header.
If a longer duration is contained in the request, the If a longer duration is contained in the request, the
server returns a 400 Bad Request response." server returns a 400 Bad Request response."
::= { sipProxyCfg 1 } ::= { sipProxyCfgEntry 1 }
sipProxyStateful OBJECT-TYPE sipProxyStateful OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the proxy server "This object specifies whether or not the default for
operates in stateful mode. When stateful, a proxy the the proxy server is to operate in stateful mode.
remembers the incoming request which generated outgoing
requests, and the outgoing requests. A stateless proxy
forgets all information once an outgoing request is
generated.
If the value of this object is TRUE, the proxy is When stateful, a proxy remembers the incoming request
stateful. If FALSE, the proxy is stateless." which generated outgoing requests, and the outgoing
requests. A stateless proxy forgets all information
once an outgoing request is generated.
If the value of this object is TRUE, the proxy defaults
to stateful. If FALSE, the proxy defaults to stateless."
REFERENCE REFERENCE
"RFC 2543, Section 12.3" "RFC 2543, Section 12.3"
::= { sipProxyCfg 2 } ::= { sipProxyCfgEntry 2 }
Lingle/Maeng/Walker 52
sipProxySendsCancel OBJECT-TYPE sipProxySendsCancel OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not a forking proxy sends "This object specifies whether or not a forking proxy sends
CANCEL on outstanding branch requests after receiving a CANCEL on outstanding branch requests after receiving a
2xx or 6xx, or after the request times-out. 2xx or 6xx, or after the request times-out.
If the value of this object is TRUE, the server sends a If the value of this object is TRUE, the server sends a
CANCELs on branches where no definitive response has been CANCELs on branches where no definitive response has been
received. If FALSE, the proxy does not send CANCELs." received. If FALSE, the proxy does not send CANCELs."
REFERENCE REFERENCE
"RFC 2543, Section 12.4" "RFC 2543, Section 12.4"
::= { sipProxyCfg 3 } ::= { sipProxyCfgEntry 3 }
sipProxyForwardAll1xx OBJECT-TYPE sipProxyForwardAll1xx OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the proxy forwards "This object specifies whether or not the proxy forwards
all 1xx responses upstream towards the source of the all 1xx responses, except the 100 Trying response,
request. upstream towards the source of the request.
If the value of this object is TRUE, all 1xx response are If the value of this object is TRUE, the 1xx responses are
sent. If the value is FALSE, duplicate 1xx responses are sent. If the value is FALSE, duplicate 1xx responses are
not sent upstream." not sent upstream."
::= { sipProxyCfg 4 } ::= { sipProxyCfgEntry 4 }
sipProxyRecursion OBJECT-TYPE sipProxyRecursion OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Proxy performs "This object specifies whether or not the Proxy performs
recursive search on the Contacts provided in 3xx recursive search on the Contacts provided in 3xx
redirects. redirects.
If the value of this object is TRUE, a recursive search is If the value of this object is TRUE, a recursive search is
performed. If the value is FALSE, no search is performed, performed. If the value is FALSE, no search is performed,
the 3xx response is sent upstream towards the source of the 3xx response is sent upstream towards the source of
the request." the request."
::= { sipProxyCfg 5 } ::= { sipProxyCfgEntry 5 }
sipProxyProvideAlternatives OBJECT-TYPE sipProxyProvideAlternatives OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object specifies whether or not the Server provides "The object specifies whether or not the Server provides
alternative Contacts in 3xx and 485 responses. alternative Contacts in 3xx and 485 responses.
If the value of this object is TRUE, the server inserts a If the value of this object is TRUE, the server inserts a
Lingle/Maeng/Walker 53
list of alternative URLs into a Contact header where the list of alternative URLs into a Contact header where the
request Originator may possibly find the desired called request Originator may possibly find the desired called
party. If the value is FALSE, the server doesn't add party. If the value is FALSE, the server doesn't add
Contact information to 3xx and 485 responses. Contact information to 3xx and 485 responses.
Note that the policies of a server may limit the Note that the policies of a server may limit the
particular alternatives that are returned when this object particular alternatives that are returned when this object
is TRUE." is TRUE."
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
DEFVAL { false } DEFVAL { false }
::= { sipProxyCfg 6 } ::= { sipProxyCfgEntry 6 }
sipProxyRecordRoute OBJECT-TYPE sipProxyRecordRoute OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the proxy adds itself "This object specifies whether or not the proxy adds itself
to the Record-Route header. This header is used to list to the Record-Route header as a default action. This
the proxies that insist on being in the signalling path header is used to list the proxies that insist on being in
for subsequent requests related to the call-leg. the signalling path for subsequent requests related to the
call-leg.
If the value of this object is TRUE, the proxy adds itself If the value of this object is TRUE, the proxy adds itself
to the end of the Record-Route header, creating the header to the end of the Record-Route header, creating the header
if required. if required. If the value is FALSE, the proxy doesn't add
If the value is FALSE, the proxy doesn't add itself to the itself to the Record-Route header."
Record-Route header."
REFERENCE REFERENCE
"RFC 2543, Section 6.29" "RFC 2543, Section 6.29"
::= { sipProxyCfg 7 } ::= { sipProxyCfgEntry 7 }
sipProxyUseCompact OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies whether or not the proxy should use
the compact encoding form in the requests it sends.
If the value of this object is TRUE, the proxy encodes all
outgoing messages using the compact encoding form. If the
value is FALSE, the encoding form used on the
corresponding incoming message is used, and if no incoming
message existed, full encoding is used."
REFERENCE
"RFC 2543, Section 9"
::= { sipProxyCfg 8 }
sipProxyRetransmissionBuffer OBJECT-TYPE sipProxyStateTimeout OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the duration after reception of the "This object specifies the duration after reception of the
first definitive non-200 response that a stateful proxy first definitive non-200 response that a stateful proxy
retains state in order to handle possible retransmissions retains state in order to handle possible retransmissions
of the response." of the response."
REFERENCE REFERENCE
"RFC 2543, Section 12.3.6" "RFC 2543, Section 12.3.6"
::= { sipProxyCfg 9 } ::= { sipProxyCfgEntry 8 }
-- --
-- Security -- Security
-- --
sipProxyAuthMethod OBJECT-TYPE sipProxyAuthMethod OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(1), none(1),
basic(2), basic(2),
digest(3), digest(3),
Lingle/Maeng/Walker 54
pgp(4) pgp(4)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the authentication method that is "This object specifies the authentication method that is
used to authenticate request originators. If the value is used to authenticate request originators. If the value is
none(1), no authentication is performed." none(1), no authentication is performed."
::= { sipProxyCfg 10 } ::= { sipProxyCfgEntry 9 }
sipProxyAuthPgpAlgorithm OBJECT-TYPE sipProxyAuthPgpAlgorithm OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
md5(2), md5(2),
sha1(3) sha1(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the PGP algorithm the proxy uses." "This object specifies the PGP algorithm the proxy uses."
::= { sipProxyCfg 11 } ::= { sipProxyCfgEntry 10 }
sipProxyAuthRealm OBJECT-TYPE sipProxyAuthRealm OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the realm used in Proxy-Authenticate "This object specifies the realm used in Proxy-Authenticate
headers. Note that this may need to be stored per user." headers. Note that this may need to be stored per user."
::= { sipProxyCfg 12 } ::= { sipProxyCfgEntry 11 }
sipProxyNonceLifeTime OBJECT-TYPE sipProxyNonceLifeTime OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the life-time of a given nonce. A "This object specifies the life-time of a given nonce. A
nonce is a server specified value whose contents are nonce is a server specified value whose contents are
opaque to the entity being authenticated and which is used opaque to the entity being authenticated and which is used
in calculating authentication data. If this object has a in calculating authentication data. If this object has a
value of zero, then value of zero, then
nonces are not reused." nonces are not reused."
::= { sipProxyCfg 13 } ::= { sipProxyCfgEntry 12 }
-- --
-- Proxy-Authenticate received by this server -- Proxy-Authenticate received by this server
-- (i.e. this server is being authenticated by a peer) -- (i.e. this server is being authenticated by a peer)
-- --
sipPgpPrivateKey OBJECT-TYPE sipPgpPrivateKey OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..255)) SYNTAX OCTET STRING(SIZE(0..255))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
Lingle/Maeng/Walker 55
DESCRIPTION DESCRIPTION
"The value of this object is the server's private PGP key, "The value of this object is the server's private PGP key,
used for both PGP authentication of this server and for used for both PGP authentication of this server and for
PGP-based PGP-based
encryption." encryption."
::= { sipProxyCfg 14 } ::= { sipProxyCfgEntry 13 }
sipHideRespect OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies whether the server encrypts Via
headers as requested by received Hide headers."
::= { sipProxyCfgEntry 14 }
sipRxProxyAuthTable OBJECT-TYPE sipRxProxyAuthTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRxProxyAuthEntry SYNTAX SEQUENCE OF SipRxProxyAuthEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains authentication data for peers of the "This table contains authentication data for peers of each
server." proxy server in this system. The instances of proxy
::= { sipProxyCfg 15 } server are uniquely identified by the applIndex."
::= { sipProxyCfg 2 }
sipRxProxyAuthEntry OBJECT-TYPE sipRxProxyAuthEntry OBJECT-TYPE
SYNTAX SipRxProxyAuthEntry SYNTAX SipRxProxyAuthEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains authentication data for a single "This object contains authentication data for a single
peer." peer."
INDEX { sipRxProxyAuthIndex } INDEX { applIndex, sipRxProxyAuthIndex }
::= { sipRxProxyAuthTable 1 } ::= { sipRxProxyAuthTable 1 }
SipRxProxyAuthEntry ::= SipRxProxyAuthEntry ::=
SEQUENCE { SEQUENCE {
sipRxProxyAuthIndex Unsigned32, sipRxProxyAuthIndex Unsigned32,
sipRxProxyAuthRealm SnmpAdminString, sipRxProxyAuthRealm SnmpAdminString,
sipRxProxyAuthPassword OCTET STRING, sipRxProxyAuthPassword OCTET STRING,
sipRxProxyAuthStatus RowStatus sipRxProxyAuthStatus RowStatus
} }
sipRxProxyAuthIndex OBJECT-TYPE sipRxProxyAuthIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in the "This object uniquely identifies a conceptual row in the
table." table."
::= { sipRxProxyAuthEntry 1 } ::= { sipRxProxyAuthEntry 1 }
Lingle/Maeng/Walker 56
sipRxProxyAuthRealm OBJECT-TYPE sipRxProxyAuthRealm OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the realm that is specified by "This object contains the realm that is specified by
another server when it is authenticating this server." another server when it is authenticating this server."
::= { sipRxProxyAuthEntry 2 } ::= { sipRxProxyAuthEntry 2 }
sipRxProxyAuthPassword OBJECT-TYPE sipRxProxyAuthPassword OBJECT-TYPE
skipping to change at page 53, line 4 skipping to change at line 3113
::= { sipRxProxyAuthEntry 3 } ::= { sipRxProxyAuthEntry 3 }
sipRxProxyAuthStatus OBJECT-TYPE sipRxProxyAuthStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row status of the entry. This object is required "The row status of the entry. This object is required
to create or delete rows remotely by a manager." to create or delete rows remotely by a manager."
::= { sipRxProxyAuthEntry 4 } ::= { sipRxProxyAuthEntry 4 }
sipHideRespect OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies whether the server encrypts Via
headers as requested by received Hide headers."
::= { sipProxyCfg 16 }
-- --
-- Proxy Server Statistics -- Proxy Server Statistics
-- --
sipProxyStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipProxyStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the statistics objects applicable
to all SIP Proxy Servers in this system.
Each row represents those objects for a particular
SIP Proxy Server. The instances of SIP Proxy Server
are uniquely identified by applIndex."
::= { sipProxyStats 1 }
sipProxyStatsEntry OBJECT-TYPE
SYNTAX SipProxyStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of summary statistics."
INDEX { applIndex }
::= { sipProxyStatsTable 1 }
Lingle/Maeng/Walker 57
SipProxyStatsEntry ::=
SEQUENCE {
sipNumProxyRequireFailures Counter32
}
sipNumProxyRequireFailures OBJECT-TYPE sipNumProxyRequireFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the number of occurrences of "This object contains the number of occurrences of
unsupported options being specified in received Proxy- unsupported options being specified in received Proxy-
Require headers. Such occurrences result in a 420 Bad Require headers. Such occurrences result in a 420 Bad
Extension status code being Extension status code being
returned." returned."
::= { sipProxyStats 1 } ::= { sipProxyStatsEntry 1 }
-- --
-- sipRedir group -- sipRedir group
-- This group contains MIB objects related to SIP Redirect Servers. -- This group contains MIB objects related to SIP Redirect Servers.
-- --
sipRedir OBJECT IDENTIFIER ::= { sipServerMIB 4 }
sipRedirCfg OBJECT IDENTIFIER ::= { sipRedir 1 } sipRedirCfg OBJECT IDENTIFIER ::= { sipRedir 1 }
sipRedirStats OBJECT IDENTIFIER ::= { sipRedir 2 } sipRedirStats OBJECT IDENTIFIER ::= { sipRedir 2 }
-- none at this time -- none at this time
-- --
-- Notifications
--
sipServerMIBNotif OBJECT IDENTIFIER ::= { sipServerMIB 5 }
sipProxyNotif OBJECT IDENTIFIER ::= { sipServerMIBNotif 1 }
sipRedirNotif OBJECT IDENTIFIER ::= { sipServerMIBNotif 2 }
-- none at this time
--
-- Conformance
--
sipServerMIBConformance
OBJECT IDENTIFIER ::= { sipServerMIB 6 }
sipServerMIBCompliances
OBJECT IDENTIFIER ::= { sipServerMIBConformance 1 }
sipServerMIBGroups
OBJECT IDENTIFIER ::= { sipServerMIBConformance 2 }
--
-- Compliance Statements
--
Lingle/Maeng/Walker 58
sipCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SIP entities."
MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup }
-- sipServerStatsGroup,
-- sipServerNotifGroup }
GROUP sipProxyConfigGroup
DESCRIPTION
"This group is mandatory for SIP Proxy servers."
GROUP sipProxyStatsGroup
DESCRIPTION
"This group is mandatory for SIP Proxy servers."
-- GROUP sipProxyNotifGroup
-- DESCRIPTION
-- "This group is mandatory for SIP Proxy servers."
-- GROUP sipRedirectConfigGroup
-- DESCRIPTION
-- "This group is mandatory for SIP Redirect servers."
-- GROUP sipRedirectStatsGroup
-- DESCRIPTION
-- "This group is mandatory for SIP Redirect servers."
-- GROUP sipRedirectNotifGroup
-- DESCRIPTION
-- "This group is mandatory for SIP Redirect servers."
::= { sipServerMIBCompliances 1 }
--
-- Units of Conformance
--
sipServerConfigGroup OBJECT-GROUP
OBJECTS {
sipServerHost,
sipInformationAlwaysSendTrying,
sipInformationTryingInterval,
sipPgpVersion,
sipServerDfltAction,
sipServerRespectUAAction
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration common
to SIP Proxy and Redirect servers."
Lingle/Maeng/Walker 59
::= { sipServerMIBGroups 1 }
--sipServerStatsGroup OBJECT-GROUP
-- OBJECTS {
-- none at this time
-- }
-- STATUS current
-- DESCRIPTION
-- "A collection of objects providing common statistics for
-- SIP Proxy and Redirect servers."
-- ::= { sipServerMIBGroups 2 }
sipProxyConfigGroup OBJECT-GROUP
OBJECTS {
sipRequestMaxExpires,
sipProxyStateful,
sipProxySendsCancel,
sipProxyForwardAll1xx,
sipProxyRecursion,
sipProxyProvideAlternatives,
sipProxyRecordRoute,
sipProxyStateTimeout,
sipProxyAuthMethod,
sipProxyAuthPgpAlgorithm,
sipProxyAuthRealm,
sipProxyNonceLifeTime,
sipPgpPrivateKey,
sipRxProxyAuthRealm,
sipRxProxyAuthPassword,
sipRxProxyAuthStatus,
sipHideRespect
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration for
SIP Proxy servers."
::= { sipServerMIBGroups 3 }
sipProxyStatsGroup OBJECT-GROUP
OBJECTS {
sipNumProxyRequireFailures
}
STATUS current
DESCRIPTION
"A collection of objects providing statistics for
SIP Proxy servers."
::= { sipServerMIBGroups 4 }
--sipProxyNotifGroup NOTIFICATION-GROUP
-- OBJECTS {
-- none at this time
-- }
-- STATUS current
-- DESCRIPTION
Lingle/Maeng/Walker 60
-- "A collection of notifications defined for SIP
-- Proxy servers."
-- ::= { sipServerMIBGroups 5 }
--sipRedirectConfigGroup OBJECT-GROUP
-- OBJECTS {
-- none at this time
-- }
-- STATUS current
-- DESCRIPTION
-- "A collection of objects providing configuration for
-- SIP Redirect servers."
-- ::= { sipServerMIBGroups 6 }
--sipRedirectStatsGroup OBJECT-GROUP
-- OBJECTS {
-- none at this time
-- }
-- STATUS current
-- DESCRIPTION
-- "A collection of objects providing statistics for
-- SIP Redirect servers."
-- ::= { sipServerMIBGroups 7 }
--sipRedirectNotifGroup NOTIFICATION-GROUP
-- OBJECTS {
-- none at this time
-- }
-- STATUS current
-- DESCRIPTION
-- "A collection of notifications defined for SIP
-- Redirect servers."
-- ::= { sipServerMIBGroups 8 }
END
5.6. SIP Registrar
SIP-REGISTRAR-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Counter32,
Gauge32,
Unsigned32
FROM SNMPv2-SMI
DateAndTime,
RowStatus,
TimeStamp,
TruthValue
FROM SNMPv2-TC
Lingle/Maeng/Walker 61
MODULE-COMPLIANCE,
OBJECT-GROUP
FROM SNMPv2-CONF
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
SipServerActions
FROM SIP-TC
sipMIB
FROM SIP-MIB-SMI
applIndex
FROM NETWORK-SERVICES-MIB;
sipRegistrarMIB MODULE-IDENTITY
LAST-UPDATED "200007080000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO
"SIP MIB Team email: sip-mib@egroups.com
Co-editor Kevin Lingle
Cisco Systems, Inc.
postal: 7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709
USA
email: klingle@cisco.com
phone: +1-919-392-2029
Co-editor Joon Maeng
VTEL Corporation
postal: 108 Wild Basin Rd.
Austin, TX 78746
USA
email: joon_maeng@vtel.com
phone: +1-512-437-4567
Co-editor Dave Walker
SS8 Networks, Inc.
postal: 80 Hines Road
Kanata, ON K2K 2T8
Canada
email: drwalker@ss8networks.com
phone: +1 613 592 2100"
DESCRIPTION
"Initial version of Session Initiation Protocol (SIP)
Registrar MIB module.
SIP is an application-layer signalling protocol for
creating, modifying and terminating multimedia
sessions with one or more participants. These sessions
Lingle/Maeng/Walker 62
include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 2543 (March
1999).
A Registrar is a server that accepts REGISTER
requests. A Registrar is typically co-located with a
Proxy or Redirect Server."
::= { sipMIB 5 }
--
-- sipReg group -- sipReg group
-- This group contains MIB objects related to SIP Registrars. -- This group contains MIB objects related to SIP Registrars.
-- --
sipRegCfg OBJECT IDENTIFIER ::= { sipReg 1 } sipRegCfg OBJECT IDENTIFIER ::= { sipRegistrarMIB 1 }
sipRegStats OBJECT IDENTIFIER ::= { sipReg 2 } sipRegStats OBJECT IDENTIFIER ::= { sipRegistrarMIB 2 }
-- --
-- Registrar Configuration -- Registrar Configuration
-- --
sipRegCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains configuration objects applicable
SIP registrars. Each row represents those objects
for a particular SIP registrar present in this system.
The instances of SIP registrars are uniquely identified
by applIndex."
::= { sipRegCfg 1 }
sipRegCfgEntry OBJECT-TYPE
SYNTAX SipRegCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of common configuration."
INDEX { applIndex }
::= { sipRegCfgTable 1 }
SipRegCfgEntry ::=
SEQUENCE {
sipRegAllowThirdParty TruthValue,
sipRegContactDfltExpiryDuration Unsigned32,
sipRegContactDfltExpiryDate DateAndTime,
sipRegMaxContactExpiryDate Unsigned32,
sipRegRespHasContacts TruthValue,
sipRegMaxUsers Unsigned32,
sipRegCurrentUsers Gauge32
}
sipRegAllowThirdParty OBJECT-TYPE sipRegAllowThirdParty OBJECT-TYPE
Lingle/Maeng/Walker 63
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Registrar should "This object specifies whether or not the Registrar should
allows third party registrations. In third-party allows third party registrations. In third-party
registration, the entity issuing the request (in the From registration, the entity issuing the request (in the From
header) is different from the entity being registered (in header) is different from the entity being registered (in
the To header) to whom the the To header) to whom the
provided Contact information applies. provided Contact information applies.
If the value of this object is TRUE, the Registrar allows If the value of this object is TRUE, the Registrar allows
third party registrations. If the value is FALSE, third third party registrations. If the value is FALSE, third
party registrations are rejected: a 403 Forbidden status party registrations are rejected: a 403 Forbidden status
code is returned to the requestor." code is returned to the requestor."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.6" "RFC 2543, Section 4.2.6"
::= { sipRegCfg 1 } ::= { sipRegCfgEntry 1 }
sipRegContactDfltExpiryDuration OBJECT-TYPE sipRegContactDfltExpiryDuration OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default expiration (time-to- "This object specifies the default expiration (time-to-
live) of Contact information that is provided by User live) of Contact information that is provided by User
Agents when registering with this Registrar. This value Agents when registering with this Registrar. This value
skipping to change at page 54, line 38 skipping to change at line 3510
value to the registered User Agent. value to the registered User Agent.
The value contained in this object only applies if the