draft-ietf-sip-mib-02.txt   draft-ietf-sip-mib-03.txt 
Internet Engineering Task Force K. Lingle Internet Engineering Task Force K. Lingle
Internet Draft Cisco Systems Internet Draft Cisco Systems
Document: draft-ietf-sip-mib-02.txt J. Maeng Document: draft-ietf-sip-mib-03.txt J. Maeng
March 2001 VTEL Corp. June 2001 ipDialog, Inc.
Expires: September 2001 J-F. Mule Expires: December 2001 J-F. Mule
Clarent Corp. Clarent Corp.
D. Walker D. Walker
SS8 Networks, Inc. SS8 Networks, Inc.
Management Information Base Management Information Base
for Session Initiation Protocol for Session Initiation Protocol
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
skipping to change at line 47 skipping to change at page 2, line 5
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) entities, which include to manage Session Initiation Protocol (SIP) entities, which include
User Agents, Proxy servers, Redirect servers and Registrars. User Agents, Proxy servers, Redirect servers and Registrars.
Lingle/Maeng/Walker/Mule 1
Table of Contents Table of Contents
Abstract..........................................................1 Abstract..........................................................1
1. Introduction...................................................2 1. Introduction...................................................2
2. The SNMP Management Framework..................................2 2. The SNMP Management Framework..................................2
3. Overview.......................................................3 3. Overview.......................................................3
4. Structure of SIP MIB...........................................3 4. Structure of SIP MIB...........................................3
4.1. Textual Conventions..........................................4 4.1. Textual Conventions..........................................4
4.2. Relationship to Other MIB....................................5 4.2. Relationship to Other MIB....................................5
5. Definitions....................................................8 5. Definitions....................................................8
5.1. SIP Structure Management Information.........................8 5.1. SIP Textual Conventions......................................8
5.2. SIP Textual Conventions......................................9 5.2. SIP Common...................................................9
5.3. SIP Common..................................................10 5.3. SIP User Agent..............................................57
5.4. SIP User Agent..............................................56 5.4. SIP Server (Registrar, Redirect & Proxy Server).............61
5.5. SIP Server (Registrar, Redirect & Proxy Server).............61 6. Changes from previous drafts..................................80
6. Security Considerations.......................................83 7. Security Considerations.......................................81
7. Intellectual Property.........................................84 8. Intellectual Property.........................................81
8. Full Copyright Statement......................................84 9. Full Copyright Statement......................................82
9. References....................................................86 10. References..................................................83
10. Author's Addresses..........................................87 11. Author's Addresses..........................................84
1. Introduction 1. Introduction
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 schedule management operations periodically or at specified dates to schedule management operations periodically or at specified dates
and times. 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. 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:
. An overall architecture, described in RFC 2271 [1]. o An overall architecture, described in RFC 2571 [1].
. Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
STD16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The STD16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
second version, called SMIv2, is described in STD 58, RFC 2578 second version, called SMIv2, is described in STD 58, RFC 2578
[5], RFC 2579 [6] and RFC 2580 [7]. [5], RFC 2579 [6] and RFC 2580 [7].
. Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
Lingle/Maeng/Mule/Walker 2
described in RFC 1157 [8]. A second version of the SNMP message described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3 and The third version of the message protocol is called SNMPv3 and
described in RFC 2272 [11] and RFC 2274 [12]. described in RFC 2572 [11] and RFC 2574 [12].
. Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [8]. A second set of protocol described in STD 15, RFC 1157 [8]. A second set of protocol
operations and associated PDU formats is described in RFC 1905 operations and associated PDU formats is described in RFC 1905
[13]. [13].
. A set of fundamental applications described in RFC 2273 [14] and the o A set of fundamental applications described in RFC 2573 [14] and
view-based access control mechanism described in RFC 2275 [15]. the view-based access control mechanism described in RFC 2575
[15].
A more detailed introduction to the current SNMP Management
Framework can be found in RFC 2570 [20].
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 line 140 skipping to change at page 3, line 49
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
entities defined in RFC 2543 - User Agent, Proxy server, Redirect entities defined in RFC 2543 - User Agent, Proxy server, Redirect
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 SIP This MIB is intended to provide management of the basic SIP
entities. It provides for monitoring of status and protocol entities. It provides for monitoring of status and protocol
statistics, as well as for configuration of SIP entities. It also statistics, as well as for configuration of SIP entities. It also
includes objects for the SIP INFO method [20]. includes objects for the SIP INFO method [19].
4. Structure of SIP MIB 4. Structure of SIP MIB
This memo specifies five MIB modules. They are SIP-MIB-SMI, SIP- This memo specifies five MIB modules. They are SIP-MIB-SMI, SIP-
COMMON-MIB, SIP-SERVER-MIB, SIP-UA-MIB and SIP-TC. SIP-MIB-SMI COMMON-MIB, SIP-SERVER-MIB, SIP-UA-MIB and SIP-TC. SIP-MIB-SMI
indicates the root OID of SIP MIB modules. SIP-COMMON-MIB contains indicates the root OID of SIP MIB modules. SIP-COMMON-MIB contains
common objects used in all the SIP entities such as Registrars, common objects used in all the SIP entities such as Registrars,
Proxy Servers, Redirect Servers and User Agents. SIP-SERVER-MIB and Proxy Servers, Redirect Servers and User Agents. SIP-SERVER-MIB and
SIP-UA-MIB includes objects defined for Registrars, Proxy Redirect SIP-UA-MIB includes objects defined for Registrars, Proxy Redirect
Lingle/Maeng/Mule/Walker 3
servers and User Agents, respectively. SIP-TC defines the textual servers and User Agents, respectively. SIP-TC defines the textual
conventions used throughout MIB modules. conventions used throughout MIB modules.
Each MIB Module contains following groups of objects: Each MIB Module contains following groups of objects:
-- SIP-COMMON-MIB: Common to all the SIP entities -- SIP-COMMON-MIB: Common to all the SIP entities
sipCommonConfigGroup, sipCommonConfigGroup,
sipCommonStatsGroup, sipCommonStatsGroup,
sipCommonConfigTimerGroup, sipCommonConfigTimerGroup,
sipCommonConfigTimerExtMethodGroup, sipCommonConfigTimerExtMethodGroup,
skipping to change at line 173 skipping to change at page 4, line 29
sipCommonConfigRetryExtMethodGroup, sipCommonConfigRetryExtMethodGroup,
sipCommonStatsRetryGroup, sipCommonStatsRetryGroup,
sipCommonStatsRetryExtMethodsGroup, sipCommonStatsRetryExtMethodsGroup,
sipCommonNotifGroup, sipCommonNotifGroup,
sipCommonStatusCodeNotifGroup. sipCommonStatusCodeNotifGroup.
-- SIP-SERVER-MIB: Groups of objects for Registrars, Proxy and -- SIP-SERVER-MIB: Groups of objects for Registrars, Proxy and
-- Redirect Servers -- Redirect Servers
sipServerConfigGroup, sipServerConfigGroup,
sipProxyConfigGroup, sipProxyConfigGroup,
sipProxyStatsGroup sipProxyStatsGroup,
sipServerConfigGroup,
sipRegistrarConfigGroup, sipRegistrarConfigGroup,
sipRegistrarStatsGroup, sipRegistrarStatsGroup.
-- SIP-UA-MIB: Groups of objects for User Agents -- SIP-UA-MIB: Groups of objects for User Agents
sipUAConfigGroup sipUAConfigGroup
It is required to implement SIP-COMMON-MIB together with its own MIB It is required to implement SIP-COMMON-MIB together with its own MIB
module in Registrars, Proxy Servers, Redirect Servers and User module in Registrars, Proxy Servers, Redirect Servers and User
Agents. For instance, a SIP Registrar will need four MIB modules, Agents. For instance, a SIP Registrar will need four MIB modules,
SIP-MIB-SMI, SIP-COMMON-MIB, SIP-SERVER-MIB, and SIP-TC in order to SIP-MIB-SMI, SIP-COMMON-MIB, SIP-SERVER-MIB, and SIP-TC in order to
provide a complete set of objects. If a device has more than one sip provide a complete set of objects. If a device has more than one sip
entity or multiple instances of the same entity, it should implement entity or multiple instances of the same entity, it should implement
skipping to change at line 200 skipping to change at page 5, line 5
4.1. Textual Conventions 4.1. Textual Conventions
The data type SipTransportProtocol is used as textual conventions in The data type SipTransportProtocol 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 or the semantics of any managed object. Objects defined the syntax or the semantics of any managed object. Objects defined
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.
Lingle/Maeng/Mule/Walker 4
4.2. Relationship to Other MIB 4.2. Relationship to Other MIB
There is a requirement to be able to support multiple instances of There is a requirement to be able to support multiple instances of
SIP MIB modules in the context of a single system having a single SIP MIB modules in the context of a single system having a single
SNMP agent. SNMP agent.
It is also possible to have multiple instances of a particular type 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 of SIP entity running on the same system. For example, there may be
Registrars for different domains with completely different Registrars for different domains with completely different
behaviors. behaviors.
While there are separate MIB modules defined for SIP User Agents and While there are separate MIB modules defined for SIP User Agents and
SIP servers, there is also a "common" MIB module expected to be SIP servers, there is also a "common" MIB module expected to be
supported by every SIP entity. Further, all SIP entities are either supported by every SIP entity. Further, all SIP entities are either
acting as a UAC, UAS or perhaps both. So a SIP Proxy Server must acting as a UAC, UAS or perhaps both. So a SIP Proxy Server must
support the SIP-SERVER-MIB and SIP-COMMON-MIB modules. Likewise, support the SIP-SERVER-MIB and SIP-COMMON-MIB modules. Likewise,
the Registrar must support the SIP-SERVER-MIB and SIP-COMMON-MIB the Registrar must support the SIP-SERVER-MIB and SIP-COMMON-MIB
modules. Here we have the requirement for supporting multiple modules. Here we have the requirement for supporting multiple
instances of a particular MIB module in one system. instances of a particular MIB module in one system.
This requirement is solved by using the framework provided by the This requirement is solved by using the framework provided by the
NETWORK-SERVICES-MIB, RFC 2788 [19]. A device implementing the SIP NETWORK-SERVICES-MIB, RFC 2788 [18]. A device implementing the SIP
MIB MUST support the NETWORK-SERVICES-MIB and, at a minimum, it MUST MIB MUST support the NETWORK-SERVICES-MIB and, at a minimum, it MUST
support the applIndex and applName objects in applTable. The support the applIndex and applName objects in applTable. The
following applName conventions will be adopted: following applName conventions will be adopted:
o for a SIP Proxy entity, applName must be equal to "sip_proxy" o for a SIP Proxy entity, applName must be equal to "sip_proxy"
o for a SIP Redirect entity, applName must be equal to o for a SIP Redirect entity, applName must be equal to
"sip_redirect" "sip_redirect"
o for a SIP Registrar entity, applName must be equal to o for a SIP Registrar entity, applName must be equal to
"sip_registrar" "sip_registrar"
o for a SIP User Agent entity, applName must be equal to o for a SIP User Agent entity, applName must be equal to
skipping to change at line 254 skipping to change at page 6, line 5
protocol version is used, the value MUST be as defined in SIP protocol version is used, the value MUST be as defined in SIP
[17], section 4.3.1. [17], section 4.3.1.
o applUptime: value must be identical to sipServiceStartTime o applUptime: value must be identical to sipServiceStartTime
defined in the SIP-COMMON module, defined in the SIP-COMMON module,
o applOperStatus: value should reflect the operational status o applOperStatus: value should reflect the operational status
defined in sipServiceOperStatus, at least by means of a defined in sipServiceOperStatus, at least by means of a
mapping, mapping,
o applLastChange: value must be identical to o applLastChange: value must be identical to
sipServiceLastChange defined in the SIP-COMMON module. sipServiceLastChange defined in the SIP-COMMON module.
Lingle/Maeng/Mule/Walker 5
Note: There are a number of other objects in the applTable. They 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 are not included for the sake of brevity and for the fact that they
do not enhance the concept being presented. do not enhance the concept being presented.
Example 1: The table below illustrates how it would conceptually Example 1: The table below illustrates how it would conceptually
appear in a system acting as both, a Proxy and Registrar server and appear in a system acting as both, a Proxy and Registrar server and
wishing to maintain separate SIP-COMMON-MIB instances. wishing to maintain separate SIP-COMMON-MIB instances.
The NETWORK-SERVICES-MIB applTable would be populated as follows: The NETWORK-SERVICES-MIB applTable would be populated as follows:
skipping to change at line 300 skipping to change at page 6, line 50
----------+----------------------+------------------+---- ----------+----------------------+------------------+----
1 | 3600 | false | 1 | 3600 | false |
----------+----------------------+------------------+---- ----------+----------------------+------------------+----
and sipRegUserTable in SIP-SERVER-MIB is populated as: and sipRegUserTable in SIP-SERVER-MIB is populated as:
applIndex | sipUserIndex | sipUserUri | ... applIndex | sipUserIndex | sipUserUri | ...
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 1 | drwalker@ss8.com | 2 | 1 | drwalker@ss8.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 2 | jmaeng@vtel.com | 2 | 2 | jmaeng@ipdialog.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 3 | klingle@cisco.com | 2 | 3 | klingle@cisco.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 4 | jfm@clarent.com | 2 | 4 | jfm@clarent.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
Lingle/Maeng/Mule/Walker 6
Example 2: The next table illustrates how it would conceptually Example 2: The next table illustrates how it would conceptually
appear in a system acting as both, a Proxy and Registrar server and appear in a system acting as both, a Proxy and Registrar server and
wishing to share a single instance of SIP-COMMON-MIB. wishing to share a single instance of SIP-COMMON-MIB.
The NETWORK-SERVICES-MIB applTable would be populated as follows: The NETWORK-SERVICES-MIB applTable would be populated as follows:
applIndex | applName | applDescription applIndex | applName | applDescription
----------+----------------------+--------------------------- ----------+----------------------+---------------------------
1 | "sip_proxy_registrar"| "ACME SIP Proxy&Registrar" 1 | "sip_proxy_registrar"| "ACME SIP Proxy&Registrar"
----------+----------------------+--------------------------- ----------+----------------------+---------------------------
skipping to change at line 342 skipping to change at page 7, line 38
----------+----------------------+------------------+---- ----------+----------------------+------------------+----
1 | 3600 | false | 1 | 3600 | false |
----------+----------------------+------------------+---- ----------+----------------------+------------------+----
and sipRegUserTable in SIP-SERVER-MIB is populated as: and sipRegUserTable in SIP-SERVER-MIB is populated as:
applIndex | sipUserIndex | sipUserUri | ... applIndex | sipUserIndex | sipUserUri | ...
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
1 | 1 | drwalker@ss8networks.com | 1 | 1 | drwalker@ss8networks.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
1 | 2 | jmaeng@vtel.com | 1 | 2 | jmaeng@ipdialog.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
1 | 3 | klingle@cisco.com | 1 | 3 | klingle@cisco.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
1 | 4 | jfm@clarent.com | 1 | 4 | jfm@clarent.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
The NETWORK-SERVICES-MIB assocTable is not considered a requirement The NETWORK-SERVICES-MIB assocTable is not considered a requirement
for SIP systems. It is not a mandatory group for NETWORK-SERVICES- for SIP systems. It is not a mandatory group for NETWORK-SERVICES-
MIB compliance. MIB compliance.
Lingle/Maeng/Mule/Walker 7
5. Definitions 5. Definitions
5.1. SIP Structure Management Information 5.1. SIP Textual Conventions
SIP-MIB-SMI DEFINITIONS ::= BEGIN SIP-TC DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
mib-2 mib-2
FROM SNMPv2-SMI;
sipMIB MODULE-IDENTITY
LAST-UPDATED "200102230000Z"
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: 495 March Road
Kanata, ON K2K 3G1
Canada
email: drwalker@ss8.com
phone: +1 613 592 2100
Co-editor Jean-Francois Mule
Clarent Corporation
700 Chesapeake Drive
Redwood City, CA 94063
email: jfm@clarent.com
phone: +1 650 481 2835"
DESCRIPTION
"Initial version of Session Initiation Protocol (SIP)
MIB module that defines base OID for all other
SIP-related MIB Modules."
Lingle/Maeng/Mule/Walker 8
::= { mib-2 9998 } -- to be assigned by IANA
END
5.2. SIP Textual Conventions
SIP-TC DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC;
sipMIB
FROM SIP-MIB-SMI;
sipTC MODULE-IDENTITY sipTC MODULE-IDENTITY
LAST-UPDATED "200102280000Z" LAST-UPDATED "200106060000Z"
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@yahoogroups.com "SIP MIB Team email: sip-mib@yahoogroups.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
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
Co-editor Joon Maeng Co-editor Joon Maeng
VTEL Corporation ipDialog, Inc.
postal: 108 Wild Basin Rd. postal: 7701 N. Lamar Blvd., Suite 304
Austin, TX 78746 Austin, TX 78752-1023
USA USA
email: joon_maeng@vtel.com email: jmaeng@ipdialog.com
phone: +1 512 437 4567 phone: +1 512 371 1770
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
postal: 495 March Road postal: 495 March Road
Kanata, ON K2K 3G1 Kanata, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: drwalker@ss8.com
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
Clarent Corporation Clarent Corporation
700 Chesapeake Drive 700 Chesapeake Drive
Redwood City, CA 94063 Redwood City, CA 94063
USA
email: jfm@clarent.com email: jfm@clarent.com
phone: +1 650 481 2835" phone: +1 650 481 2835"
Lingle/Maeng/Mule/Walker 9
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Initial version of Session Initiation Protocol (SIP)
MIB Textual Conventions module used by other MIB Textual Conventions module used by other
SIP-related MIB Modules." SIP-related MIB Modules."
::= { sipMIB 1 } ::= { mib-2 9992 } -- to be assigned by IANA
-- --
-- Textual Conventions -- Textual Conventions
-- --
SipTransportProtocol ::= TEXTUAL-CONVENTION SipTransportProtocol ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention is a bit map. Each bit represents a "This convention is a bit map. Each bit represents a
transport protocol. If a bit has value 1, then that transport protocol. If a bit has value 1, then that
skipping to change at line 503 skipping to change at page 9, line 40
SYNTAX BITS { SYNTAX BITS {
other(0), -- none of the following other(0), -- none of the following
udp(1), udp(1),
tcp(2), tcp(2),
sctp(3), sctp(3),
tls(4) tls(4)
} }
END END
5.3. SIP Common 5.2. SIP Common
SIP-COMMON-MIB DEFINITIONS ::= BEGIN SIP-COMMON-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
Counter32, Counter32,
Integer32, Integer32,
Gauge32, Gauge32,
TimeTicks, TimeTicks,
Unsigned32 Unsigned32,
mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
DateAndTime, DateAndTime,
RowStatus, RowStatus,
TruthValue TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
Lingle/Maeng/Mule/Walker 10
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
FROM SIP-MIB-SMI
SipTransportProtocol SipTransportProtocol
FROM SIP-TC FROM SIP-TC
applIndex applIndex
FROM NETWORK-SERVICES-MIB; FROM NETWORK-SERVICES-MIB;
sipCommonMIB MODULE-IDENTITY sipCommonMIB MODULE-IDENTITY
LAST-UPDATED "200102230000Z" LAST-UPDATED "200106060000Z"
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@yahoogroups.com "SIP MIB Team email: sip-mib@yahoogroups.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
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
Co-editor Joon Maeng Co-editor Joon Maeng
VTEL Corporation ipDialog, Inc.
postal: 108 Wild Basin Rd. postal: 7701 N. Lamar Blvd., Suite 304
Austin, TX 78746 Austin, TX 78752-1023
USA USA
email: joon_maeng@vtel.com email: jmaeng@ipdialog.com
phone: +1 512 437 4567 phone: +1 512 371 1770
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
postal: 495 March Road postal: 495 March Road
Kanata, ON K2K 3G1 Kanata, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: drwalker@ss8.com
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
Clarent Corporation Clarent Corporation
700 Chesapeake Drive 700 Chesapeake Drive
Redwood City, CA 94063 Redwood City, CA 94063
USA
email: jfm@clarent.com email: jfm@clarent.com
phone: +1 650 481 2835" phone: +1 650 481 2835"
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Initial version of Session Initiation Protocol (SIP)
Common MIB module. This module defines objects which Common MIB module. This module defines objects which
Lingle/Maeng/Mule/Walker 11
may be common to all SIP entities. may be common to all SIP entities.
SIP is an application-layer signalling protocol for SIP is an application-layer signalling protocol for
creating, modifying and terminating multimedia creating, modifying and terminating multimedia
sessions with one or more participants. These sessions sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 2543 (March telephone calls. SIP is defined in RFC 2543 (March
1999). 1999).
This MIB is defined for the managing objects which are This MIB is defined for the managing objects which are
skipping to change at line 619 skipping to change at page 11, line 40
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 } ::= { mib-2 9990 } -- to be assigned by IANA
-- Top-Level Components of this MIB.
sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 }
sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
sipCommonMIBConform OBJECT IDENTIFIER ::= { sipCommonMIB 2 }
-- --
-- sipCommon Group -- This MIB contains objects that are common to all SIP entities.
-- This group contains MIB objects that are common to all SIP
-- entities.
-- --
sipCommonCfg OBJECT IDENTIFIER ::= { sipCommonMIB 1 } sipCommonCfgBase OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 }
sipCommonCfgBase OBJECT IDENTIFIER ::= { sipCommonCfg 1 } sipCommonCfgTimer OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 }
sipCommonCfgTimer OBJECT IDENTIFIER ::= { sipCommonCfg 2 } sipCommonCfgRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 }
sipCommonCfgRetry OBJECT IDENTIFIER ::= { sipCommonCfg 3 } sipCommonStatsSummary OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 }
sipCommonStats OBJECT IDENTIFIER ::= { sipCommonMIB 2 } sipCommonStatsMethod OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 }
sipCommonStatsSummary OBJECT IDENTIFIER ::= { sipCommonStats 1 } sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 }
sipCommonStatsMethod OBJECT IDENTIFIER ::= { sipCommonStats 2 } sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 }
sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonStats 3 } sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 }
sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonStats 4 } sipCommonStatsOther OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 }
sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonStats 5 }
Lingle/Maeng/Mule/Walker 12
-- --
-- Common Configuration Objects -- Common Configuration Objects
-- --
sipCommonCfgTable OBJECT-TYPE sipCommonCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgEntry SYNTAX SEQUENCE OF SipCommonCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the common configuration objects "This table contains the common configuration objects
applicable to all SIP entities. Each row represents applicable to all SIP entities."
those objects for a particular SIP entity present in
this system. The instances of SIP entities are
uniquely identified by applIndex."
::= { sipCommonCfgBase 1 } ::= { sipCommonCfgBase 1 }
sipCommonCfgEntry OBJECT-TYPE sipCommonCfgEntry OBJECT-TYPE
SYNTAX SipCommonCfgEntry SYNTAX SipCommonCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common configuration." "A row of common configuration.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipCommonCfgTable 1 } ::= { sipCommonCfgTable 1 }
SipCommonCfgEntry ::= SipCommonCfgEntry ::=
SEQUENCE { SEQUENCE {
sipProtocolVersion SnmpAdminString, sipProtocolVersion SnmpAdminString,
sipServiceOperStatus INTEGER, sipServiceOperStatus INTEGER,
sipServiceAdminStatus INTEGER, sipServiceAdminStatus INTEGER,
sipServiceStartTime TimeTicks, sipServiceStartTime TimeTicks,
sipServiceLastChange TimeTicks, sipServiceLastChange TimeTicks,
skipping to change at line 694 skipping to change at page 13, line 7
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."
::= { sipCommonCfgEntry 1 } ::= { sipCommonCfgEntry 1 }
sipServiceOperStatus OBJECT-TYPE sipServiceOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), up(1),
down(2), down(2),
testing(3), testing(3),
Lingle/Maeng/Mule/Walker 13
unknown(4), unknown(4),
halted(5), halted(5),
restarting(6) restarting(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the current operational state of the "This object contains the current operational state of the
SIP application. SIP application.
skipping to change at line 753 skipping to change at page 14, line 8
::= { sipCommonCfgEntry 3 } ::= { 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
Lingle/Maeng/Mule/Walker 14
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."
::= { sipCommonCfgEntry 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
skipping to change at line 806 skipping to change at page 15, line 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For user agent clients, this value is inserted into the "For user agent clients, this value is inserted into the
Expires header. Expires header.
For proxy servers, if a received request contained an For proxy servers, if a received request contained an
Expires header, then the value in the header takes Expires header, then the value in the header takes
precedence. The server returns a 408 Request Timeout if precedence. The server returns a 408 Request Timeout if
no response is received before no response is received before
expiration of the request timer." expiration of the request timer."
::= { sipCommonCfgEntry 8 } ::= { sipCommonCfgEntry 8 }
sipRequestUriHostMatching OBJECT-TYPE sipRequestUriHostMatching OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
Lingle/Maeng/Mule/Walker 15
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the host in "This object specifies whether or not the host in
RequestURI must match server's host name. RequestURI must match server's host name.
If the value of this object is TRUE, then the server If the value of this object is TRUE, then the server
requires a match, and if the RequestURI doesn't match the requires a match, and if the RequestURI doesn't match the
server's host name, a 404 Not Found status code is server's host name, a 404 Not Found status code is
returned by the server. returned by the server.
If the value is FALSE, then no match is required." If the value is FALSE, then no match is required."
skipping to change at line 837 skipping to change at page 15, line 33
-- 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 each SIP entity "This table contains the list of ports that each SIP entity
in this system is allowed to use. These ports can be in this system is allowed to use. These ports can be
advertised using the Contact header in a REGISTER request advertised using the Contact header in a REGISTER request
or response. The instances of SIP entities are uniquely or response."
identified by applIndex."
::= { sipCommonCfgBase 2 } ::= { sipCommonCfgBase 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.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipPort } INDEX { applIndex, sipPort }
::= { sipPortTable 1 } ::= { sipPortTable 1 }
SipPortEntry ::= SipPortEntry ::=
SEQUENCE { SEQUENCE {
sipPort INTEGER, sipPort INTEGER,
sipTransportRcv SipTransportProtocol, sipTransportRcv SipTransportProtocol,
sipTransportSnd SipTransportProtocol, sipTransportSnd SipTransportProtocol,
sipPortStatus RowStatus sipPortStatus RowStatus
} }
skipping to change at line 869 skipping to change at page 16, line 15
SYNTAX INTEGER (1..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 }
sipTransportRcv OBJECT-TYPE sipTransportRcv OBJECT-TYPE
Lingle/Maeng/Mule/Walker 16
SYNTAX SipTransportProtocol SYNTAX SipTransportProtocol
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
entity will use to receive SIP messages. entity will use to receive SIP messages.
This object is a bit map. Each bit represents a transport This object is a bit map. Each bit represents a transport
protocol. If a bit has value 1, then that transport protocol protocol. If a bit has value 1, then that transport protocol
is currently being used. If a bit has value 0, then that is currently being used. If a bit has value 0, then that
skipping to change at line 926 skipping to change at page 17, line 14
"This table contains a list of URI schemes supported by each "This table contains a list of URI schemes supported by each
SIP entity in this system. These are in addition to the SIP SIP entity in this system. These are in addition to the SIP
URL which must necessarily be supported. Normally the URL which must necessarily be supported. Normally the
list of URI schemes supported by an entity is static list of URI schemes supported by an entity is static
(i.e. will not change over time). (i.e. will 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).
URI schemes could, for example, contain URLs for phones, fax, URI schemes could, for example, contain URLs for phones, fax,
or irc if they were defined) or a mailto: (RFC 2368) URL. or irc if they were defined) or a mailto: (RFC 2368) URL."
Lingle/Maeng/Mule/Walker 17
The instances of SIP entities are uniquely identified
by applIndex."
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
::= { sipCommonCfgBase 3 } ::= { sipCommonCfgBase 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.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipUriSupportedIndex } INDEX { applIndex, sipUriSupportedIndex }
::= { sipUriSupportedTable 1 } ::= { sipUriSupportedTable 1 }
SipUriSupportedEntry ::= SipUriSupportedEntry ::=
SEQUENCE { SEQUENCE {
sipUriSupportedIndex Unsigned32, sipUriSupportedIndex Unsigned32,
sipUriSupported SnmpAdminString sipUriSupported SnmpAdminString
} }
sipUriSupportedIndex OBJECT-TYPE sipUriSupportedIndex OBJECT-TYPE
skipping to change at line 986 skipping to change at page 18, line 19
-- --
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 each SIP entity in this system, and which supported by each SIP entity in this system, and which
may be required by a peer. Definition of such features is may be required by a peer. Definition of such features is
Lingle/Maeng/Mule/Walker 18
outside the scope of SIP, which only provides mechanisms outside the scope of SIP, which only provides mechanisms
whereby support for specific features may be signalled or whereby support for specific features may be signalled or
requested. 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
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"
::= { sipCommonCfgBase 4 } ::= { sipCommonCfgBase 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.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, 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
skipping to change at line 1043 skipping to change at page 19, line 21
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in the "This object uniquely identifies a conceptual row in the
table." table."
::= { sipFtrSupportedEntry 1 } ::= { sipFtrSupportedEntry 1 }
sipFtrSupported OBJECT-TYPE sipFtrSupported OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
Lingle/Maeng/Mule/Walker 19
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 }
-- --
-- SIP Timer Configuration -- SIP Timer Configuration
-- --
sipCommonCfgTimerTable OBJECT-TYPE sipCommonCfgTimerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgTimerEntry SYNTAX SEQUENCE OF SipCommonCfgTimerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains timer configuration objects applicable "This table contains timer configuration objects applicable
to SIP user agent and SIP stateful proxy entities. to SIP user agent and SIP stateful proxy entities."
The instances of SIP entities are uniquely identified by
applIndex."
::= { sipCommonCfgTimer 1 } ::= { sipCommonCfgTimer 1 }
sipCommonCfgTimerEntry OBJECT-TYPE sipCommonCfgTimerEntry OBJECT-TYPE
SYNTAX SipCommonCfgTimerEntry SYNTAX SipCommonCfgTimerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of timer configuration." "A row of timer configuration.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipCommonCfgTimerTable 1 } ::= { sipCommonCfgTimerTable 1 }
SipCommonCfgTimerEntry ::= SipCommonCfgTimerEntry ::=
SEQUENCE { SEQUENCE {
sipCfgInitialTimerInvite Unsigned32, sipCfgInitialTimerInvite Unsigned32,
sipCfgTimerProv Unsigned32, sipCfgTimerProv Unsigned32,
sipCfgInitialTimerAck Unsigned32,
sipCfgInitialTimerBye Unsigned32, sipCfgInitialTimerBye Unsigned32,
sipCfgInitialTimerRegister Unsigned32, sipCfgInitialTimerRegister Unsigned32,
sipCfgInitialTimerOptions Unsigned32, sipCfgInitialTimerOptions Unsigned32,
sipCfgInitialTimerInfo Unsigned32, sipCfgInitialTimerInfo Unsigned32,
sipCfgInitialTimerRsp Unsigned32, sipCfgInitialTimerRsp Unsigned32,
sipCfgTimerT2 Unsigned32 sipCfgTimerT2 Unsigned32
} }
sipCfgInitialTimerInvite OBJECT-TYPE sipCfgInitialTimerInvite OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
skipping to change at line 1100 skipping to change at page 20, line 26
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the initial value for the retransmit
timer for the INVITE method. The retransmit timer doubles timer for the INVITE method. The retransmit timer doubles
after each retransmission, ensuring an exponential backoff after each retransmission, ensuring an exponential backoff
in network traffic. This object represents the initial time in network traffic. This object represents the initial time
a SIP entity will wait to receive a provisional response to a SIP entity will wait to receive a provisional response to
an INVITE before resending the INVITE request." an INVITE before resending the INVITE request."
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 1 } ::= { sipCommonCfgTimerEntry 1 }
Lingle/Maeng/Mule/Walker 20
sipCfgTimerProv OBJECT-TYPE sipCfgTimerProv OBJECT-TYPE
SYNTAX Unsigned32 (60000..300000) SYNTAX Unsigned32 (60000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum time a SIP entity will wait "This object specifies the maximum time a SIP entity will wait
to receive a final response to an INVITE. The timer is started to receive a final response to an INVITE. The timer is started
upon receipt of a provisional response." upon receipt of a provisional response."
DEFVAL { 60000 } DEFVAL { 60000 }
::= { sipCommonCfgTimerEntry 2 } ::= { sipCommonCfgTimerEntry 2 }
sipCfgInitialTimerAck OBJECT-TYPE
SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the initial value for the retransmit
timer for the ACK method. The retransmit timer doubles
after each retransmission, ensuring an exponential backoff
in network traffic. This object represents the initial time
a SIP entity will wait to receive a response to an ACK."
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 3 }
sipCfgInitialTimerBye OBJECT-TYPE sipCfgInitialTimerBye OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the initial value for the retransmit
timer for the BYE method. The retransmit timer doubles timer for the BYE method. The retransmit timer doubles
after each retransmission, ensuring an exponential backoff after each retransmission, ensuring an exponential backoff
in network traffic. This object represents the initial time in network traffic. This object represents the initial time
a SIP entity will wait to receive a response to a BYE request." a SIP entity will wait to receive a response to a BYE request."
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 4 } ::= { sipCommonCfgTimerEntry 3 }
sipCfgInitialTimerRegister OBJECT-TYPE sipCfgInitialTimerRegister OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the initial value for the retransmit
timer for the REGISTER method. The retransmit timer doubles timer for the REGISTER method. The retransmit timer doubles
after each retransmission, ensuring an exponential backoff after each retransmission, ensuring an exponential backoff
in network traffic. This object represents the initial time in network traffic. This object represents the initial time
a SIP entity will wait to receive a response to a REGISTER a SIP entity will wait to receive a response to a REGISTER
request." request."
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 5 } ::= { sipCommonCfgTimerEntry 4 }
sipCfgInitialTimerOptions OBJECT-TYPE sipCfgInitialTimerOptions OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
Lingle/Maeng/Mule/Walker 21
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the initial value for the retransmit
timer for the OPTIONS method. The retransmit timer doubles timer for the OPTIONS method. The retransmit timer doubles
after each retransmission, ensuring an exponential backoff after each retransmission, ensuring an exponential backoff
in network traffic. This object represents the initial time in network traffic. This object represents the initial time
a SIP entity will wait to receive a response to an OPTIONS a SIP entity will wait to receive a response to an OPTIONS
request." request."
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 6 } ::= { sipCommonCfgTimerEntry 5 }
sipCfgInitialTimerInfo OBJECT-TYPE sipCfgInitialTimerInfo OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the initial value for the retransmit
timer for the INFO method. The retransmit timer doubles timer for the INFO method. The retransmit timer doubles
after each retransmission, ensuring an exponential backoff after each retransmission, ensuring an exponential backoff
in network traffic. This object represents the initial time in network traffic. This object represents the initial time
a SIP entity will wait to receive a response to a INFO request." a SIP entity will wait to receive a response to a INFO request."
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 7 } ::= { sipCommonCfgTimerEntry 6 }
sipCfgInitialTimerRsp OBJECT-TYPE sipCfgInitialTimerRsp OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the initial value for the retransmit
timer for final responses. The retransmit timer doubles timer for final responses. The retransmit timer doubles
after each retransmission, ensuring an exponential backoff after each retransmission, ensuring an exponential backoff
in network traffic. This object represents the initial time in network traffic. This object represents the initial time
a SIP entity will wait to retransmit a final response." a SIP entity will wait to retransmit a final response."
REFERENCE "Section 10.5.1 RFC2543" REFERENCE "Section 10.5.1 RFC2543"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 8 } ::= { sipCommonCfgTimerEntry 7 }
sipCfgTimerT2 OBJECT-TYPE sipCfgTimerT2 OBJECT-TYPE
SYNTAX Unsigned32 (200..10000) SYNTAX Unsigned32 (200..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the T2 timer for a SIP entity." "This object specifies the T2 timer for a SIP entity."
REFERENCE "Section 10.4 and 10.5 RFC2543" REFERENCE "Section 10.4 and 10.5 RFC2543"
DEFVAL { 4000 } DEFVAL { 4000 }
::= { sipCommonCfgTimerEntry 9 } ::= { sipCommonCfgTimerEntry 8 }
Lingle/Maeng/Mule/Walker 22
-- --
-- Initial Timers Extensions: support for extension methods -- Initial Timers Extensions: support for extension methods
-- --
sipCommonCfgTimerExtMethodTable OBJECT-TYPE sipCommonCfgTimerExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgTimerExtMethodEntry SYNTAX SEQUENCE OF SipCommonCfgTimerExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains retransmit timers for each SIP "This table contains retransmit timers for each SIP
extension method this entity supports. The instances extension method this entity supports.
of SIP entities are uniquely identified by applIndex.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788).
The applicable T2 timer value for timers configured The applicable T2 timer value for timers configured
in this table is that of the sipCfgTimerT2 object in this table is that of the sipCfgTimerT2 object
with the same applIndex value." with the same applIndex value."
::= { sipCommonCfgTimer 2 } ::= { sipCommonCfgTimer 2 }
sipCommonCfgTimerExtMethodEntry OBJECT-TYPE sipCommonCfgTimerExtMethodEntry OBJECT-TYPE
SYNTAX SipCommonCfgTimerExtMethodEntry SYNTAX SipCommonCfgTimerExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains timer value information for "This row contains timer value information for
a particular extension method." a particular extension method."
INDEX { applIndex, sipCommonCfgTimerExtMethodIndex } INDEX { applIndex, sipCfgTimerExtMethodIndex }
::= { sipCommonCfgTimerExtMethodTable 1 } ::= { sipCommonCfgTimerExtMethodTable 1 }
SipCommonCfgTimerExtMethodEntry ::= SipCommonCfgTimerExtMethodEntry ::=
SEQUENCE { SEQUENCE {
sipCfgTimerExtMethodIndex Unsigned32, sipCfgTimerExtMethodIndex Unsigned32,
sipCfgTimerExtMethodName SnmpAdminString, sipCfgTimerExtMethodName SnmpAdminString,
sipCfgTimerExtMethodTimer Unsigned32, sipCfgTimerExtMethodTimer Unsigned32,
sipCfgTimerExtMethodStatus RowStatus sipCfgTimerExtMethodStatus RowStatus
} }
skipping to change at line 1272 skipping to change at page 23, line 22
"This object contains the name of the particular extension "This object contains the name of the particular extension
method the SIP entity supports. For example, it may method the SIP entity supports. For example, it may
contain the string 'REFER' if the REFER method is supported. contain the string 'REFER' if the REFER method is supported.
It is an error for any of the methods contained in RFC 2543 It is an error for any of the methods contained in RFC 2543
to be requested." to be requested."
::= { sipCommonCfgTimerExtMethodEntry 2 } ::= { sipCommonCfgTimerExtMethodEntry 2 }
sipCfgTimerExtMethodTimer OBJECT-TYPE sipCfgTimerExtMethodTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
Lingle/Maeng/Mule/Walker 23
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the time a SIP entity will wait "This object specifies the time a SIP entity will wait
for a response to the extension method request before for a response to the extension method request before
retransmitting. The retransmit timer doubles after retransmitting. The retransmit timer doubles after
each retransmission, ensuring an exponential backoff each retransmission, ensuring an exponential backoff
in network traffic." in network traffic."
DEFVAL { 500 } DEFVAL { 500 }
skipping to change at line 1308 skipping to change at page 23, line 57
-- --
-- SIP Retry Configuration -- SIP Retry Configuration
-- --
sipCommonCfgRetryTable OBJECT-TYPE sipCommonCfgRetryTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgRetryEntry SYNTAX SEQUENCE OF SipCommonCfgRetryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains retry configuration objects applicable "This table contains retry configuration objects applicable
to SIP user agent and SIP proxies. The instances of to SIP user agent and SIP proxies."
SIP entities are uniquely identified by applIndex."
::= { sipCommonCfgRetry 1 } ::= { sipCommonCfgRetry 1 }
sipCommonCfgRetryEntry OBJECT-TYPE sipCommonCfgRetryEntry OBJECT-TYPE
SYNTAX SipCommonCfgRetryEntry SYNTAX SipCommonCfgRetryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of retry configuration." "A row of retry configuration.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipCommonCfgRetryTable 1 } ::= { sipCommonCfgRetryTable 1 }
SipCommonCfgRetryEntry ::= SipCommonCfgRetryEntry ::=
SEQUENCE { SEQUENCE {
sipCfgRetryInvite Unsigned32, sipCfgRetryInvite Unsigned32,
sipCfgRetryAck Unsigned32,
sipCfgRetryBye Unsigned32, sipCfgRetryBye Unsigned32,
sipCfgRetryCancel Unsigned32, sipCfgRetryCancel Unsigned32,
sipCfgRetryRegister Unsigned32, sipCfgRetryRegister Unsigned32,
sipCfgRetryOptions Unsigned32, sipCfgRetryOptions Unsigned32,
Lingle/Maeng/Mule/Walker 24
sipCfgRetryInfo Unsigned32, sipCfgRetryInfo Unsigned32,
sipCfgRetryFinalResponse Unsigned32, sipCfgRetryFinalResponse Unsigned32,
sipCfgRetryNonFinalResponse Unsigned32 sipCfgRetryNonFinalResponse Unsigned32
} }
sipCfgRetryInvite OBJECT-TYPE sipCfgRetryInvite OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (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 SIP entity "This object will specify the number of times a SIP entity
will retry sending an INVITE request." will retry sending an INVITE request."
REFERENCE "Section 10.5 RFC 2543" REFERENCE "Section 10.5 RFC 2543"
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 1 } ::= { sipCommonCfgRetryEntry 1 }
sipCfgRetryAck OBJECT-TYPE
SYNTAX Unsigned32(1..10)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object will specify the number of times a SIP entity
will retry sending an ACK request."
REFERENCE "Section 10.5 RFC 2543"
DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 2 }
sipCfgRetryBye OBJECT-TYPE sipCfgRetryBye OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (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 SIP entity "This object will specify the number of times a SIP entity
will retry sending a BYE request." will retry sending a BYE request."
REFERENCE "Section 10.4 RFC 2543" REFERENCE "Section 10.4 RFC 2543"
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 3 } ::= { sipCommonCfgRetryEntry 2 }
sipCfgRetryCancel OBJECT-TYPE sipCfgRetryCancel OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (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 SIP entity "This object will specify the number of times a SIP entity
will retry sending a CANCEL request." will retry sending a CANCEL request."
REFERENCE "Section 10.4 RFC 2543" REFERENCE "Section 10.4 RFC 2543"
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 4 } ::= { sipCommonCfgRetryEntry 3 }
sipCfgRetryRegister OBJECT-TYPE sipCfgRetryRegister OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (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 SIP entity "This object will specify the number of times a SIP entity
will retry sending a REGISTER request." will retry sending a REGISTER request."
REFERENCE "Section 10.4 RFC 2543" REFERENCE "Section 10.4 RFC 2543"
Lingle/Maeng/Mule/Walker 25
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 5 } ::= { sipCommonCfgRetryEntry 4 }
sipCfgRetryOptions OBJECT-TYPE sipCfgRetryOptions OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (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 SIP entity "This object will specify the number of times a SIP entity
will retry sending an OPTIONS request." will retry sending an OPTIONS request."
REFERENCE "Section 10.4 RFC2543" REFERENCE "Section 10.4 RFC2543"
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 6 } ::= { sipCommonCfgRetryEntry 5 }
sipCfgRetryInfo OBJECT-TYPE sipCfgRetryInfo OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (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 SIP entity "This object will specify the number of times a SIP entity
will retry sending an INFO request." will retry sending an INFO request."
REFERENCE "Section 2.4 RFC 2976" REFERENCE "Section 2.4 RFC 2976"
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 7 } ::= { sipCommonCfgRetryEntry 6 }
sipCfgRetryFinalResponse OBJECT-TYPE sipCfgRetryFinalResponse OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (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 SIP entity "This object will specify the number of times a SIP entity
will retry sending a final response and expecting an ACK." will retry sending a final response and expecting an ACK."
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 8 } ::= { sipCommonCfgRetryEntry 7 }
sipCfgRetryNonFinalResponse OBJECT-TYPE sipCfgRetryNonFinalResponse OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (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 SIP entity "This object will specify the number of times a SIP entity
will retry sending a non-final response." will retry sending a non-final response."
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 9 } ::= { sipCommonCfgRetryEntry 8 }
-- --
-- Retry Extensions: support for extension methods -- Retry Extensions: support for extension methods
-- --
sipCommonCfgRetryExtMethodTable OBJECT-TYPE sipCommonCfgRetryExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgRetryExtMethodEntry SYNTAX SEQUENCE OF SipCommonCfgRetryExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains retry configuration for each SIP "This table contains retry configuration for each SIP
extension method this entity supports. The instances extension method this entity supports."
Lingle/Maeng/Mule/Walker 26
of SIP entities are uniquely identified by applIndex."
::= { sipCommonCfgTimer 3 } ::= { sipCommonCfgTimer 3 }
sipCommonCfgRetryExtMethodEntry OBJECT-TYPE sipCommonCfgRetryExtMethodEntry OBJECT-TYPE
SYNTAX SipCommonCfgRetryExtMethodEntry SYNTAX SipCommonCfgRetryExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains retry configuration information for "This row contains retry configuration information for
a particular extension method." a particular extension method.
INDEX { applIndex, sipCommonCfgRetryExtMethodIndex }
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipCfgRetryExtMethodIndex }
::= { sipCommonCfgRetryExtMethodTable 1 } ::= { sipCommonCfgRetryExtMethodTable 1 }
SipCommonCfgRetryExtMethodEntry ::= SipCommonCfgRetryExtMethodEntry ::=
SEQUENCE { SEQUENCE {
sipCfgRetryExtMethodIndex Unsigned32, sipCfgRetryExtMethodIndex Unsigned32,
sipCfgRetryExtMethodName SnmpAdminString, sipCfgRetryExtMethodName SnmpAdminString,
sipCfgRetryExtMethodRetry Unsigned32, sipCfgRetryExtMethodRetry Unsigned32,
sipCfgRetryExtMethodStatus RowStatus sipCfgRetryExtMethodStatus RowStatus
} }
skipping to change at line 1505 skipping to change at page 27, line 22
will retry sending its request for this particular will retry sending its request for this particular
extension method." extension method."
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryExtMethodEntry 3 } ::= { sipCommonCfgRetryExtMethodEntry 3 }
sipCfgRetryExtMethodStatus OBJECT-TYPE sipCfgRetryExtMethodStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
Lingle/Maeng/Mule/Walker 27
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.
A value for sipCfgRetryExtMethodName must be set A value for sipCfgRetryExtMethodName must be set
for row creation to be successful. If that method for row creation to be successful. If that method
already exists for a particular applIndex, the row already exists for a particular applIndex, the row
create operation will fail." create operation will fail."
::= { sipCommonCfgRetryExtMethodEntry 4 } ::= { sipCommonCfgRetryExtMethodEntry 4 }
-- --
skipping to change at line 1530 skipping to change at page 27, line 46
-- Summary Statistics -- Summary Statistics
-- --
sipSummaryStatsTable OBJECT-TYPE sipSummaryStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipSummaryStatsEntry SYNTAX SEQUENCE OF SipSummaryStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the summary statistics objects "This table contains the summary statistics objects
applicable to all SIP entities. Each row represents applicable to all SIP entities. Each row represents
those objects for a particular SIP entity present in those objects for a particular SIP entity present in
this system. The instances of SIP entities are uniquely this system."
identified by applIndex."
::= { sipCommonStatsSummary 1 } ::= { sipCommonStatsSummary 1 }
sipSummaryStatsEntry OBJECT-TYPE sipSummaryStatsEntry OBJECT-TYPE
SYNTAX SipSummaryStatsEntry SYNTAX SipSummaryStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics." "A row of summary statistics.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipSummaryStatsTable 1 } ::= { sipSummaryStatsTable 1 }
SipSummaryStatsEntry ::= SipSummaryStatsEntry ::=
SEQUENCE { SEQUENCE {
sipSummaryInRequests Counter32, sipSummaryInRequests Counter32,
sipSummaryOutRequests Counter32, sipSummaryOutRequests Counter32,
sipSummaryInResponses Counter32, sipSummaryInResponses Counter32,
sipSummaryOutResponses Counter32, sipSummaryOutResponses Counter32,
sipSummaryTotalTransactions Counter32 sipSummaryTotalTransactions Counter32
skipping to change at line 1562 skipping to change at page 28, line 27
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 including messages received by the SIP entity including
retransmissions." retransmissions."
::= { sipSummaryStatsEntry 1 } ::= { sipSummaryStatsEntry 1 }
Lingle/Maeng/Mule/Walker 28
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."
skipping to change at line 1619 skipping to change at page 29, line 28
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."
::= { sipSummaryStatsEntry 5 } ::= { sipSummaryStatsEntry 5 }
-- --
Lingle/Maeng/Mule/Walker 29
-- SIP Method Statistics -- SIP Method Statistics
-- Total counts for each SIP method. -- Total counts for each SIP method.
-- --
sipMethodStatsTable OBJECT-TYPE sipMethodStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipMethodStatsEntry SYNTAX SEQUENCE OF SipMethodStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the per method statistics objects "This table contains the per method statistics objects
applicable to all SIP entities. Each row represents applicable to all SIP entities. Each row represents
those objects for a particular SIP entity present in those objects for a particular SIP entity present in
this system. The instances of SIP entities are uniquely this system."
identified by applIndex."
::= { sipCommonStatsMethod 1 } ::= { sipCommonStatsMethod 1 }
sipMethodStatsEntry OBJECT-TYPE sipMethodStatsEntry OBJECT-TYPE
SYNTAX SipMethodStatsEntry SYNTAX SipMethodStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of per method statistics." "A row of per method statistics.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipMethodStatsTable 1 } ::= { sipMethodStatsTable 1 }
SipMethodStatsEntry ::= SipMethodStatsEntry ::=
SEQUENCE { SEQUENCE {
sipStatsInviteIns Counter32, sipStatsInviteIns Counter32,
sipStatsInviteOuts Counter32, sipStatsInviteOuts Counter32,
sipStatsAckIns Counter32, sipStatsAckIns Counter32,
sipStatsAckOuts Counter32, sipStatsAckOuts Counter32,
sipStatsByeIns Counter32, sipStatsByeIns Counter32,
skipping to change at line 1668 skipping to change at page 30, line 25
sipStatsInfoIns Counter32, sipStatsInfoIns Counter32,
sipStatsInfoOuts Counter32 sipStatsInfoOuts 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 including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.1" "RFC 2543, Section 4.2.1"
::= { sipMethodStatsEntry 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
Lingle/Maeng/Mule/Walker 30
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 including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.1" "RFC 2543, Section 4.2.1"
::= { sipMethodStatsEntry 2 } ::= { sipMethodStatsEntry 2 }
sipStatsAckIns OBJECT-TYPE sipStatsAckIns 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 "This object reflects the total number of ACK requests
skipping to change at line 1714 skipping to change at page 31, line 13
REFERENCE REFERENCE
"RFC 2543, Section 4.2.2" "RFC 2543, Section 4.2.2"
::= { sipMethodStatsEntry 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 including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.4" "RFC 2543, Section 4.2.4"
::= { sipMethodStatsEntry 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 including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.4" "RFC 2543, Section 4.2.4"
::= { sipMethodStatsEntry 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 including retransmissions."
Lingle/Maeng/Mule/Walker 31
received by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.5" "RFC 2543, Section 4.2.5"
::= { sipMethodStatsEntry 7 } ::= { sipMethodStatsEntry 7 }
sipStatsCancelOuts OBJECT-TYPE sipStatsCancelOuts 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
sent by the SIP entity." sent by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.5" "RFC 2543, Section 4.2.5"
::= { sipMethodStatsEntry 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 including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.3" "RFC 2543, Section 4.2.3"
::= { sipMethodStatsEntry 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 including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.3" "RFC 2543, Section 4.2.3"
::= { sipMethodStatsEntry 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 including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.6" "RFC 2543, Section 4.2.6"
::= { sipMethodStatsEntry 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 including retransmissions."
REFERENCE REFERENCE
Lingle/Maeng/Mule/Walker 32
"RFC 2543, Section 4.2.6" "RFC 2543, Section 4.2.6"
::= { sipMethodStatsEntry 12 } ::= { sipMethodStatsEntry 12 }
sipStatsInfoIns OBJECT-TYPE sipStatsInfoIns 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 INFO requests "This object reflects the total number of INFO requests
received by the SIP entity." received by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2976" "RFC 2976"
::= { sipMethodStatsEntry 13 } ::= { sipMethodStatsEntry 13 }
sipStatsInfoOuts OBJECT-TYPE sipStatsInfoOuts 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 INFO requests "This object reflects the total number of INFO requests
sent by the SIP entity." sent by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2976" "RFC 2976"
::= { sipMethodStatsEntry 14 } ::= { sipMethodStatsEntry 14 }
-- --
-- support for extension methods -- support for extension methods
-- --
sipStatsExtMethodTable OBJECT-TYPE sipStatsExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatsExtMethodEntry SYNTAX SEQUENCE OF SipStatsExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the list of extension methods which "This table contains the list of extension methods which
skipping to change at line 1833 skipping to change at page 33, line 15
-- support for extension methods -- support for extension methods
-- --
sipStatsExtMethodTable OBJECT-TYPE sipStatsExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatsExtMethodEntry SYNTAX SEQUENCE OF SipStatsExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the list of extension methods which "This table contains the list of extension methods which
each SIP entity in this system has been requested to each SIP entity in this system has been requested to
monitor. The instances of SIP entities are uniquely monitor."
identified by applIndex."
::= { sipCommonStatsMethod 2 } ::= { sipCommonStatsMethod 2 }
sipStatsExtMethodEntry OBJECT-TYPE sipStatsExtMethodEntry OBJECT-TYPE
SYNTAX SipStatsExtMethodEntry SYNTAX SipStatsExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information on a particular extension "This row contains information on a particular extension
method that the SIP entity has been requested to monitor." method that the SIP entity has been requested to monitor.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipStatsExtMethodIndex } INDEX { applIndex, sipStatsExtMethodIndex }
::= { sipStatsExtMethodTable 1 } ::= { sipStatsExtMethodTable 1 }
SipStatsExtMethodEntry ::= SipStatsExtMethodEntry ::=
SEQUENCE { SEQUENCE {
sipStatsExtMethodIndex Unsigned32, sipStatsExtMethodIndex Unsigned32,
sipStatsExtMethodName SnmpAdminString, sipStatsExtMethodName SnmpAdminString,
sipStatsExtMethodIns Counter32, sipStatsExtMethodIns Counter32,
sipStatsExtMethodOuts Counter32, sipStatsExtMethodOuts Counter32,
sipStatsExtMethodStatus RowStatus sipStatsExtMethodStatus RowStatus
Lingle/Maeng/Mule/Walker 33
} }
sipStatsExtMethodIndex OBJECT-TYPE sipStatsExtMethodIndex 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."
::= { sipStatsExtMethodEntry 1 } ::= { sipStatsExtMethodEntry 1 }
skipping to change at line 1888 skipping to change at page 34, line 17
of the methods contained in RFC 2543 to be requested." of the methods contained in RFC 2543 to be requested."
::= { sipStatsExtMethodEntry 2 } ::= { sipStatsExtMethodEntry 2 }
sipStatsExtMethodIns OBJECT-TYPE sipStatsExtMethodIns 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 requests received "This object reflects the total number of requests received
by the SIP entity which requested the method contained in by the SIP entity which requested the method contained in
the sipStatsExtMethodName column." the sipStatsExtMethodName column including retransmissions
if appropriate for the method."
::= { sipStatsExtMethodEntry 3 } ::= { sipStatsExtMethodEntry 3 }
sipStatsExtMethodOuts 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 requests sent "This object reflects the total number of requests sent
by the SIP entity which requested the method contained in by the SIP entity which requested the method contained in
the sipStatsExtMethodName column." the sipStatsExtMethodName column including retransmissions
if appropriate for the method."
::= { sipStatsExtMethodEntry 4 } ::= { sipStatsExtMethodEntry 4 }
sipStatsExtMethodStatus OBJECT-TYPE sipStatsExtMethodStatus 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."
::= { sipStatsExtMethodEntry 5 } ::= { sipStatsExtMethodEntry 5 }
-- --
-- SIP Response Status Codes -- SIP Response Status Codes
Lingle/Maeng/Mule/Walker 34
-- --
sipStatusCodesTable OBJECT-TYPE sipStatusCodesTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatusCodesEntry SYNTAX SEQUENCE OF SipStatusCodesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains statistics on response status code "This table contains statistics on response status code
classes for each SIP entity in this system. The instances classes for each SIP entity in this system."
of SIP entities are uniquely identified by applIndex."
::= { sipCommonStatusCode 1 } ::= { sipCommonStatusCode 1 }
sipStatusCodesEntry OBJECT-TYPE sipStatusCodesEntry OBJECT-TYPE
SYNTAX SipStatusCodesEntry SYNTAX SipStatusCodesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains statistics on response status codes." "This row contains statistics on response status codes.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipStatusCodesTable 1 } ::= { sipStatusCodesTable 1 }
SipStatusCodesEntry ::= SipStatusCodesEntry ::=
SEQUENCE { SEQUENCE {
sipStatsInfoClassIns Counter32, sipStatsInfoClassIns Counter32,
sipStatsInfoClassOuts Counter32, sipStatsInfoClassOuts Counter32,
sipStatsSuccessClassIns Counter32, sipStatsSuccessClassIns Counter32,
sipStatsSuccessClassOuts Counter32, sipStatsSuccessClassOuts Counter32,
sipStatsRedirClassIns Counter32, sipStatsRedirClassIns Counter32,
skipping to change at line 1972 skipping to change at page 35, line 51
::= { sipStatusCodesEntry 1 } ::= { sipStatusCodesEntry 1 }
sipStatsInfoClassOuts 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 number of 1xx class "This object reflects the number of 1xx class
SIP responses sent by the SIP entity. SIP responses sent by the SIP entity.
Lingle/Maeng/Mule/Walker 35
This class of responses relates to providing some This class of responses relates to providing some
information concerning the progress of processing information concerning the progress of processing
a SIP request." a SIP request."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.1" "RFC 2543, Sections 5.1.1 & 7.1"
::= { sipStatusCodesEntry 2 } ::= { sipStatusCodesEntry 2 }
sipStatsSuccessClassIns OBJECT-TYPE sipStatsSuccessClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at line 2031 skipping to change at page 36, line 52
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of 3xx class SIP "This object reflects the number of 3xx class SIP
responses sent by the SIP entity. This class of responses sent by the SIP entity. This class of
responses relate to call redirection actions taken responses relate to call redirection actions taken
by a Redirect Server." by a Redirect Server."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.3" "RFC 2543, Sections 5.1.1 & 7.3"
Lingle/Maeng/Mule/Walker 36
::= { sipStatusCodesEntry 6 } ::= { sipStatusCodesEntry 6 }
sipStatsReqFailClassIns 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 number of 4xx class SIP "This object reflects the number of 4xx class SIP
responses received by the SIP entity. This class of responses received by the SIP entity. This class of
responses reflect request failure by a SIP entity responses reflect request failure by a SIP entity
skipping to change at line 2090 skipping to change at page 37, line 53
DESCRIPTION DESCRIPTION
"This object reflects the number of 5xx class SIP "This object reflects the number of 5xx class SIP
responses sent by the SIP entity. This class of responses sent by the SIP entity. This class of
responses reflect failure responses sent by a SIP responses reflect failure responses sent by a SIP
entity providing a server function. These entity providing a server function. These
responses are not definite failures and must not responses are not definite failures and must not
terminate a search if other possible locations remain terminate a search if other possible locations remain
untried." untried."
REFERENCE REFERENCE
Lingle/Maeng/Mule/Walker 37
"RFC 2543, Sections 5.1.1 & 7.5" "RFC 2543, Sections 5.1.1 & 7.5"
::= { sipStatusCodesEntry 10 } ::= { sipStatusCodesEntry 10 }
sipStatsGlobalFailClassIns 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 number of 6xx class SIP "This object reflects the number of 6xx class SIP
responses received by the SIP entity. This class of responses received by the SIP entity. This class of
skipping to change at line 2145 skipping to change at page 38, line 50
-- support for specific status codes -- support for specific status codes
-- --
sipCommonStatusCodeTable OBJECT-TYPE sipCommonStatusCodeTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonStatusCodeEntry SYNTAX SEQUENCE OF SipCommonStatusCodeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the list of SIP status codes which "This table contains the list of SIP status codes which
each SIP entity in this system has been requested to each SIP entity in this system has been requested to
monitor. It is the mechanism by which specific status monitor. It is the mechanism by which specific status
codes are monitored. The instances of SIP entities are codes are monitored."
uniquely identified by applIndex."
::= { sipCommonStatusCode 2 } ::= { sipCommonStatusCode 2 }
Lingle/Maeng/Mule/Walker 38
sipCommonStatusCodeEntry OBJECT-TYPE sipCommonStatusCodeEntry OBJECT-TYPE
SYNTAX SipCommonStatusCodeEntry SYNTAX SipCommonStatusCodeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information on a particular SIP status "This row contains information on a particular SIP status
code that the SIP entity has been requested to monitor." code that the SIP entity has been requested to monitor.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipCommonStatusCodeValue } INDEX { applIndex, sipCommonStatusCodeValue }
::= { sipCommonStatusCodeTable 1 } ::= { sipCommonStatusCodeTable 1 }
SipCommonStatusCodeEntry ::= SipCommonStatusCodeEntry ::=
SEQUENCE { SEQUENCE {
sipCommonStatusCodeValue INTEGER, sipCommonStatusCodeValue INTEGER,
sipCommonStatusCodeIns Counter32, sipCommonStatusCodeIns Counter32,
sipCommonStatusCodeOuts Counter32, sipCommonStatusCodeOuts Counter32,
sipCommonStatusCodeStatus RowStatus sipCommonStatusCodeStatus RowStatus
} }
skipping to change at line 2207 skipping to change at page 39, line 60
sipCommonStatusCodeStatus OBJECT-TYPE sipCommonStatusCodeStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row augmentation in sipCommonStatusCodeNotifTable "The row augmentation in sipCommonStatusCodeNotifTable
will be governed by the value of this RowStatus.This will be governed by the value of this RowStatus.This
object is required to create or delete rows remotely object is required to create or delete rows remotely
Lingle/Maeng/Mule/Walker 39
by a manager. by a manager.
If set to 'notInService', all counters values may be If set to 'notInService', all counters values may be
reset to zero and any associated notifications will be reset to zero and any associated notifications will be
disabled. Associated notifications are specified in the disabled. Associated notifications are specified in the
sipCommonStatusCodeNotifTable. sipCommonStatusCodeNotifTable.
The configuration specified by an entry will be made The configuration specified by an entry will be made
active when this object is set to 'active'." active when this object is set to 'active'."
::= { sipCommonStatusCodeEntry 4 } ::= { sipCommonStatusCodeEntry 4 }
skipping to change at line 2265 skipping to change at page 41, line 4
sipCommonStatusCodeNotifSend OBJECT-TYPE sipCommonStatusCodeNotifSend OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls whether a sipStatusCodeNotif "This object controls whether a sipStatusCodeNotif
is emitted when the status code value specified in is emitted when the status code value specified in
by sipCommonStatusCodeValue is sent or received. by sipCommonStatusCodeValue is sent or received.
If the value of this object is TRUE, then a notification If the value of this object is TRUE, then a notification
Lingle/Maeng/Mule/Walker 40
is sent. If it is FALSE, no notification is sent. is sent. If it is FALSE, no notification is sent.
Note well, that a notification may be emitted for Note well, that a notification may be emitted for
every msg sent or received that contains the particular every msg sent or received that contains the particular
status code. Depending on the status code involved, status code. Depending on the status code involved,
this can cause a significant number of notification this can cause a significant number of notification
emissions that could be detrimental to network performance. emissions that could be detrimental to network performance.
Managers are forewarned to be prudent in the use of Managers are forewarned to be prudent in the use of
this object to enable notifications. Look to this object to enable notifications. Look to
sipCommonStatusCodeNotifEmitMode for alternative sipCommonStatusCodeNotifEmitMode for alternative
controls for sipStatusCodeNotif emissions." controls for sipStatusCodeNotif emissions."
skipping to change at line 2324 skipping to change at page 42, line 4
set. It reflects when the 'oneShot' has set. It reflects when the 'oneShot' has
occurred and indicates the mode needs to occurred and indicates the mode needs to
be reset to get further notifications. be reset to get further notifications.
The mode is reset by setting this object The mode is reset by setting this object
to 'oneShot' or 'normal'." to 'oneShot' or 'normal'."
DEFVAL { normal } DEFVAL { normal }
::= { sipCommonStatusCodeNotifEntry 2 } ::= { sipCommonStatusCodeNotifEntry 2 }
sipCommonStatusCodeNotifThresh OBJECT-TYPE sipCommonStatusCodeNotifThresh OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
Lingle/Maeng/Mule/Walker 41
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the number of response messages "This object specifies the number of response messages
sent or received by this system that are considered sent or received by this system that are considered
excessive. Based on crossing that threshold, a excessive. Based on crossing that threshold, a
sipStatusCodeExceededNotif notification will be sent. sipStatusCodeExceededNotif notification will be sent.
The sipStatusCodeExceededNotif can be used as an The sipStatusCodeExceededNotif can be used as an
early warning mechanism in lieu of using sipStatusCodeNotif." early warning mechanism in lieu of using sipStatusCodeNotif."
DEFVAL { 500 } DEFVAL { 500 }
skipping to change at line 2381 skipping to change at page 43, line 4
sipStatusCodeNotifCallId OBJECT-TYPE sipStatusCodeNotifCallId OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the CallId in the "This object contains the value of the CallId in the
message containing the status code that caused the message containing the status code that caused the
notification." notification."
::= { sipCommonStatusCode 6 } ::= { sipCommonStatusCode 6 }
sipStatusCodeNotifCSeq OBJECT-TYPE sipStatusCodeNotifCSeq OBJECT-TYPE
Lingle/Maeng/Mule/Walker 42
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the CSeq value in the message "This object contains the CSeq value in the message
containing the status code that caused the notification." containing the status code that caused the notification."
::= { sipCommonStatusCode 7 } ::= { sipCommonStatusCode 7 }
-- --
-- Transaction Statistics -- Transaction Statistics
-- --
sipCurrentTransTable OBJECT-TYPE sipCurrentTransTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCurrentTransEntry SYNTAX SEQUENCE OF SipCurrentTransEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on the transactions "This table contains information on the transactions
currently awaiting definitive responses by each SIP currently awaiting definitive responses by each SIP
entity in this system. The instances of SIP entities entity in this system."
are uniquely identified by applIndex."
::= { sipCommonStatsTrans 1 } ::= { sipCommonStatsTrans 1 }
sipCurrentTransEntry OBJECT-TYPE sipCurrentTransEntry OBJECT-TYPE
SYNTAX SipCurrentTransEntry SYNTAX SipCurrentTransEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular SIP entities' current "Information on a particular SIP entities' current
transactions." transactions.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipCurrentTransTable 1 } ::= { sipCurrentTransTable 1 }
SipCurrentTransEntry ::= SipCurrentTransEntry ::=
SEQUENCE { SEQUENCE {
sipCurrentTransactions Gauge32 sipCurrentTransactions Gauge32
} }
sipCurrentTransactions OBJECT-TYPE sipCurrentTransactions OBJECT-TYPE
SYNTAX Gauge32 (0..4294967295) SYNTAX Gauge32 (0..4294967295)
skipping to change at line 2433 skipping to change at page 44, line 4
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."
::= { sipCurrentTransEntry 1 } ::= { sipCurrentTransEntry 1 }
sipTransactionTable OBJECT-TYPE sipTransactionTable OBJECT-TYPE
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
Lingle/Maeng/Mule/Walker 43
currently being processed (the count of such transactions currently being processed (the count of such transactions
is maintained in the sipCurrentTransactions object) by a is maintained in the sipCurrentTransactions object) by a
particular SIP entity in this system. The instances of SIP particular SIP entity in this system."
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.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, 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,
skipping to change at line 2500 skipping to change at page 45, line 18
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 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
Lingle/Maeng/Mule/Walker 44
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 CallId value in the "This object contains the value of the CallId value in the
request message." request message."
::= { sipTransactionEntry 4 } ::= { sipTransactionEntry 4 }
sipTransCSeq OBJECT-TYPE sipTransCSeq OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
skipping to change at line 2559 skipping to change at page 46, line 19
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 }
sipTransNumOutstandingBranches OBJECT-TYPE sipTransNumOutstandingBranches OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
Lingle/Maeng/Mule/Walker 45
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
skipping to change at line 2617 skipping to change at page 47, line 19
"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 }
-- --
-- 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 sipCommonCfgRetry group. applIndex can -- retry timers supported in sipCommonCfgRetry group. applIndex can
-- be used to correlate the two groups. -- be used to correlate the two groups.
Lingle/Maeng/Mule/Walker 46
-- --
-- --
sipCommonStatsRetryTable OBJECT-TYPE sipCommonStatsRetryTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonStatsRetryEntry SYNTAX SEQUENCE OF SipCommonStatsRetryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains retry statistics objects applicable "This table contains retry statistics objects applicable
to each SIP entity in this system. The instances of to each SIP entity in this system."
SIP entities are uniquely identified by applIndex."
::= { sipCommonStatsRetry 1 } ::= { sipCommonStatsRetry 1 }
sipCommonStatsRetryEntry OBJECT-TYPE sipCommonStatsRetryEntry OBJECT-TYPE
SYNTAX SipCommonStatsRetryEntry SYNTAX SipCommonStatsRetryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of retry statistics." "A row of retry statistics.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipCommonStatsRetryTable 1 } ::= { sipCommonStatsRetryTable 1 }
SipCommonStatsRetryEntry ::= SipCommonStatsRetryEntry ::=
SEQUENCE { SEQUENCE {
sipStatsRetryInvites Counter32, sipStatsRetryInvites Counter32,
sipStatsRetryAcks Counter32,
sipStatsRetryByes Counter32, sipStatsRetryByes Counter32,
sipStatsRetryCancels Counter32, sipStatsRetryCancels Counter32,
sipStatsRetryRegisters Counter32, sipStatsRetryRegisters Counter32,
sipStatsRetryOptions Counter32, sipStatsRetryOptions Counter32,
sipStatsRetryInfos Counter32, sipStatsRetryInfos Counter32,
sipStatsRetryFinalResponses Counter32, sipStatsRetryFinalResponses Counter32,
sipStatsRetryNonFinalResponses Counter32 sipStatsRetryNonFinalResponses Counter32
} }
sipStatsRetryInvites OBJECT-TYPE sipStatsRetryInvites 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 retries "This object reflects the total number of INVITE retries
that have been sent by the SIP entity. If the number of that have been sent by the SIP entity. 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 sipStatsInviteOuts." of this object from sipStatsInviteOuts."
::= { sipCommonStatsRetryEntry 1 } ::= { sipCommonStatsRetryEntry 1 }
sipStatsRetryAcks OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of ACK retries
that have been sent by the SIP entity. If the number of
'first attempt' ACKs is of interest, subtract the value
of this object from sipStatsAckOuts."
::= { sipCommonStatsRetryEntry 2 }
sipStatsRetryByes OBJECT-TYPE sipStatsRetryByes OBJECT-TYPE
Lingle/Maeng/Mule/Walker 47
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 SIP entity. If the number of have been sent by the SIP entity. If the number of
'first attempt' BYEs is of interest, subtract the value 'first attempt' BYEs is of interest, subtract the value
of this object from sipStatsByeOuts." of this object from sipStatsByeOuts."
::= { sipCommonStatsRetryEntry 3 } ::= { sipCommonStatsRetryEntry 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 SIP entity. If the number of that have been sent by the SIP entity. If the number of
'first attempt' CANCELs is of interest, subtract the value 'first attempt' CANCELs is of interest, subtract the value
of this object from sipStatsCancelOuts." of this object from sipStatsCancelOuts."
::= { sipCommonStatsRetryEntry 4 } ::= { sipCommonStatsRetryEntry 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 SIP entity. If the number of that have been sent by the SIP entity. If the number of
'first attempt' REGISTERSs is of interest, subtract the value 'first attempt' REGISTERSs is of interest, subtract the value
of this object from sipStatsRegisterOuts." of this object from sipStatsRegisterOuts."
::= { sipCommonStatsRetryEntry 5 } ::= { sipCommonStatsRetryEntry 4 }
sipStatsRetryOptions OBJECT-TYPE sipStatsRetryOptions 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 retries "This object reflects the total number of OPTIONS retries
that have been sent by the SIP entity. If the number of that have been sent by the SIP entity. If the number of
'first attempt' OPTIONS is of interest, subtract the value 'first attempt' OPTIONS is of interest, subtract the value
of this object from sipStatsOptionsOuts." of this object from sipStatsOptionsOuts."
::= { sipCommonStatsRetryEntry 6 } ::= { sipCommonStatsRetryEntry 5 }
sipStatsRetryInfos OBJECT-TYPE sipStatsRetryInfos 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 INFO retries that "This object reflects the total number of INFO retries that
have been sent by the SIP entity. If the number of have been sent by the SIP entity. If the number of
'first attempt' INFOS is of interest, subtract the value 'first attempt' INFOS is of interest, subtract the value
of this object from sipStatsInfoOuts." of this object from sipStatsInfoOuts."
::= { sipCommonStatsRetryEntry 7 } ::= { sipCommonStatsRetryEntry 6 }
sipStatsRetryFinalResponses OBJECT-TYPE sipStatsRetryFinalResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
Lingle/Maeng/Mule/Walker 48
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Final Response "This object reflects the total number of Final Response
retries that have been sent by the SIP entity." retries that have been sent by the SIP entity."
::= { sipCommonStatsRetryEntry 8 } ::= { sipCommonStatsRetryEntry 7 }
sipStatsRetryNonFinalResponses OBJECT-TYPE sipStatsRetryNonFinalResponses 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 non-Final Response "This object reflects the total number of non-Final Response
retries that have been sent by the SIP entity." retries that have been sent by the SIP entity."
::= { sipCommonStatsRetryEntry 9 } ::= { sipCommonStatsRetryEntry 8 }
-- --
-- Retry Extensions Stats: support for extension methods -- Retry Extensions Stats: support for extension methods
-- --
sipCommonStatsRetryExtMethodTable OBJECT-TYPE sipCommonStatsRetryExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonStatsRetryExtMethodEntry SYNTAX SEQUENCE OF SipCommonStatsRetryExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains retry statistics for each SIP "This table contains retry statistics for each SIP
extension method this entity supports. The instances extension method this entity supports."
of SIP entities are uniquely identified by applIndex."
::= { sipCommonStatsRetry 2 } ::= { sipCommonStatsRetry 2 }
sipCommonStatsRetryExtMethodEntry OBJECT-TYPE sipCommonStatsRetryExtMethodEntry OBJECT-TYPE
SYNTAX SipCommonStatsRetryExtMethodEntry SYNTAX SipCommonStatsRetryExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains retry statistics for "This row contains retry statistics for
a particular extension method." a particular extension method.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipStatsRetryExtMethodIndex }
::= { sipCommonStatsRetryExtMethodTable 1 } ::= { sipCommonStatsRetryExtMethodTable 1 }
SipCommonStatsRetryExtMethodEntry ::= SipCommonStatsRetryExtMethodEntry ::=
SEQUENCE { SEQUENCE {
sipStatsRetryExtMethodIndex Unsigned32, sipStatsRetryExtMethodIndex Unsigned32,
sipStatsRetryExtMethodName SnmpAdminString, sipStatsRetryExtMethodName SnmpAdminString,
sipStatsRetryExtMethodRetries Counter32, sipStatsRetryExtMethodRetries Counter32,
sipStatsRetryExtMethodStatus RowStatus sipStatsRetryExtMethodStatus RowStatus
} }
skipping to change at line 2793 skipping to change at page 50, line 21
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."
::= { sipCommonStatsRetryExtMethodEntry 1 } ::= { sipCommonStatsRetryExtMethodEntry 1 }
sipStatsRetryExtMethodName OBJECT-TYPE sipStatsRetryExtMethodName OBJECT-TYPE
Lingle/Maeng/Mule/Walker 49
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the name of the particular extension "This object contains the name of the particular extension
method the SIP entity supports. method the SIP entity supports.
For example, it may contain the string 'REFER' if the For example, it may contain the string 'REFER' if the
REFER method is supported. REFER method is supported.
It is an error for any of the methods contained It is an error for any of the methods contained
in RFC 2543 to be requested." in RFC 2543 to be requested."
skipping to change at line 2837 skipping to change at page 51, line 7
-- --
-- Other Common Statistics -- Other Common Statistics
-- --
sipOtherStatsTable OBJECT-TYPE sipOtherStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipOtherStatsEntry SYNTAX SEQUENCE OF SipOtherStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains other common statistics supported by "This table contains other common statistics supported by
each SIP entity in this system. The instances of SIP each SIP entity in this system."
entities are uniquely identified by applIndex." ::= { sipCommonStatsOther 1 }
::= { sipCommonStats 6 }
sipOtherStatsEntry OBJECT-TYPE sipOtherStatsEntry OBJECT-TYPE
SYNTAX SipOtherStatsEntry SYNTAX SipOtherStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular SIP entities' other common "Information on a particular SIP entities' other common
statistics." statistics.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipOtherStatsTable 1 } ::= { sipOtherStatsTable 1 }
Lingle/Maeng/Mule/Walker 50
SipOtherStatsEntry ::= SipOtherStatsEntry ::=
SEQUENCE { SEQUENCE {
sipNumUnsupportedUris Counter32 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."
::= { sipOtherStatsEntry 5 } ::= { sipOtherStatsEntry 1 }
-- --
-- Notifications -- Notifications
-- --
sipCommonMIBNotifPrefix OBJECT IDENTIFIER ::= { sipCommonMIB 7 }
sipCommonMIBNotif OBJECT IDENTIFIER ::= {
sipCommonMIBNotifPrefix 0 }
sipNotifApplIndex OBJECT-TYPE sipNotifApplIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX INTEGER (1..2147483647)
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the applIndex as described "This object contains the applIndex as described
in RFC 2788. It is used to bind this notification in RFC 2788. It is used to bind this notification
with a specific instance of SIP entity." with a specific instance of SIP entity."
::= { sipCommonMIBNotif 1 } ::= { sipCommonMIBNotifs 1 }
sipStatusCodeNotif NOTIFICATION-TYPE sipStatusCodeNotif NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifApplIndex, sipNotifApplIndex,
sipStatusCodeNotifTo, sipStatusCodeNotifTo,
sipStatusCodeNotifFrom, sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId, sipStatusCodeNotifCallId,
sipStatusCodeNotifCSeq sipStatusCodeNotifCSeq
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that a specific status code has been sent "Signifies that a specific status code has been sent
or received by the system." or received by the system."
::= { sipCommonMIBNotif 2 } ::= { sipCommonMIBNotifs 2 }
sipStatusCodeThreshExceededNotif NOTIFICATION-TYPE sipStatusCodeThreshExceededNotif NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifApplIndex, sipNotifApplIndex,
sipCommonStatusCodeIns, sipCommonStatusCodeIns,
sipCommonStatusCodeOuts sipCommonStatusCodeOuts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that a specific status code was found to "Signifies that a specific status code was found to
have been sent or received by the system enough to have been sent or received by the system enough to
exceed the configured threshold. This notification exceed the configured threshold. This notification
Lingle/Maeng/Mule/Walker 51
can be used as an early warning mechanism in lieu can be used as an early warning mechanism in lieu
of using sipStatusCodeNotif." of using sipStatusCodeNotif."
::= { sipCommonMIBNotif 3 } ::= { sipCommonMIBNotifs 3 }
-- --
-- Conformance -- Conformance
-- --
sipCommonMIBConformance
OBJECT IDENTIFIER ::= { sipCommonMIB 6 }
sipCommonMIBCompliances sipCommonMIBCompliances
OBJECT IDENTIFIER ::= { sipCommonMIBConformance 1 } OBJECT IDENTIFIER ::= { sipCommonMIBConform 1 }
sipCommonMIBGroups sipCommonMIBGroups
OBJECT IDENTIFIER ::= { sipCommonMIBConformance 2 } OBJECT IDENTIFIER ::= { sipCommonMIBConform 2 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
sipCommonCompliance MODULE-COMPLIANCE sipCommonCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities." "The compliance statement for SIP entities."
MODULE -- this module MODULE -- this module
skipping to change at line 2969 skipping to change at page 53, line 23
GROUP sipCommonStatsRetryGroup GROUP sipCommonStatsRetryGroup
DESCRIPTION DESCRIPTION
"This group is optional. A SIP entity can elect to "This group is optional. A SIP entity can elect to
not provide any retry statistics. If implemented, not provide any retry statistics. If implemented,
the sipCommonConfigRetryGroup must also be implemented." the sipCommonConfigRetryGroup must also be implemented."
GROUP sipCommonStatsRetryExtMethodsGroup GROUP sipCommonStatsRetryExtMethodsGroup
DESCRIPTION DESCRIPTION
"This group is optional. A SIP entity can elect to "This group is optional. A SIP entity can elect to
Lingle/Maeng/Mule/Walker 52
not provide any extension method retry statistics. not provide any extension method retry statistics.
If implemented, the sipCommonConfigRetryExtMethodGroup If implemented, the sipCommonConfigRetryExtMethodGroup
must also be implemented." must also be implemented."
GROUP sipCommonNotifGroup GROUP sipCommonNotifGroup
DESCRIPTION DESCRIPTION
"This group is optional. A SIP entity can elect to "This group is optional. A SIP entity can elect to
not provide any notifications. If implemented, the not provide any notifications. If implemented, the
sipCommonStatusCodeNotifGroup must also be implemented." sipCommonStatusCodeNotifGroup must also be implemented."
skipping to change at line 3018 skipping to change at page 54, line 14
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration common "A collection of objects providing configuration common
to all SIP enities." to all SIP enities."
::= { sipCommonMIBGroups 1 } ::= { sipCommonMIBGroups 1 }
sipCommonConfigTimerGroup OBJECT-GROUP sipCommonConfigTimerGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgInitialTimerInvite, sipCfgInitialTimerInvite,
sipCfgTimerProv, sipCfgTimerProv,
sipCfgInitialTimerAck,
sipCfgInitialTimerBye, sipCfgInitialTimerBye,
sipCfgInitialTimerRegister, sipCfgInitialTimerRegister,
sipCfgInitialTimerOptions, sipCfgInitialTimerOptions,
sipCfgInitialTimerInfo, sipCfgInitialTimerInfo,
sipCfgInitialTimerResp, sipCfgInitialTimerRsp,
sipCfgTimerT2 sipCfgTimerT2
} }
STATUS current STATUS current
Lingle/Maeng/Mule/Walker 53
DESCRIPTION DESCRIPTION
"A collection of objects providing timer configuration "A collection of objects providing timer configuration
common to all SIP enities." common to all SIP enities."
::= { sipCommonMIBGroups 2 } ::= { sipCommonMIBGroups 2 }
sipCommonConfigTimerExtMethodGroup OBJECT-GROUP sipCommonConfigTimerExtMethodGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgTimerExtMethodName, sipCfgTimerExtMethodName,
sipCfgTimerExtMethodTimer, sipCfgTimerExtMethodTimer,
sipCfgTimerExtMethodStatus sipCfgTimerExtMethodStatus
skipping to change at line 3052 skipping to change at page 54, line 46
"A collection of objects providing extension method timer "A collection of objects providing extension method timer
configuration." configuration."
::= { sipCommonMIBGroups 3 } ::= { sipCommonMIBGroups 3 }
sipCommonConfigRetryGroup OBJECT-GROUP sipCommonConfigRetryGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgRetryInvite, sipCfgRetryInvite,
sipCfgRetryBye, sipCfgRetryBye,
sipCfgRetryCancel, sipCfgRetryCancel,
sipCfgRetryRegister, sipCfgRetryRegister,
sipCfgRetryResponse,
sipCfgRetryOptions, sipCfgRetryOptions,
sipCfgRetryInfo sipCfgRetryInfo,
sipCfgRetryFinalResponse,
sipCfgRetryNonFinalResponse
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing retry configuration "A collection of objects providing retry configuration
common to all SIP enities." common to all SIP enities."
::= { sipCommonMIBGroups 4 } ::= { sipCommonMIBGroups 4 }
sipCommonConfigRetryExtMethodGroup OBJECT-GROUP sipCommonConfigRetryExtMethodGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgRetryExtMethodName, sipCfgRetryExtMethodName,
skipping to change at line 3086 skipping to change at page 55, line 24
sipSummaryInRequests, sipSummaryInRequests,
sipSummaryOutRequests, sipSummaryOutRequests,
sipSummaryInResponses, sipSummaryInResponses,
sipSummaryOutResponses, sipSummaryOutResponses,
sipSummaryTotalTransactions, sipSummaryTotalTransactions,
sipStatsInviteIns, sipStatsInviteIns,
sipStatsInviteOuts, sipStatsInviteOuts,
sipStatsAckIns, sipStatsAckIns,
sipStatsAckOuts, sipStatsAckOuts,
sipStatsByeIns, sipStatsByeIns,
Lingle/Maeng/Mule/Walker 54
sipStatsByeOuts, sipStatsByeOuts,
sipStatsCancelIns, sipStatsCancelIns,
sipStatsCancelOuts, sipStatsCancelOuts,
sipStatsOptionsIns, sipStatsOptionsIns,
sipStatsOptionsOuts, sipStatsOptionsOuts,
sipStatsRegisterIns, sipStatsRegisterIns,
sipStatsRegisterOuts, sipStatsRegisterOuts,
sipStatsInfoIns, sipStatsInfoIns,
sipStatsInfoOuts, sipStatsInfoOuts,
sipStatsExtMethodName, sipStatsExtMethodName,
skipping to change at line 3140 skipping to change at page 56, line 19
"A collection of objects providing statistics common "A collection of objects providing statistics common
toall SIP entities." toall SIP entities."
::= { sipCommonMIBGroups 6 } ::= { sipCommonMIBGroups 6 }
sipCommonStatsRetryGroup OBJECT-GROUP sipCommonStatsRetryGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatsRetryInvites, sipStatsRetryInvites,
sipStatsRetryByes, sipStatsRetryByes,
sipStatsRetryCancels, sipStatsRetryCancels,
sipStatsRetryRegisters, sipStatsRetryRegisters,
sipStatsRetryResponses,
sipStatsRetryOptions, sipStatsRetryOptions,
sipStatsRetryInfo sipStatsRetryInfos,
sipStatsRetryFinalResponses,
sipStatsRetryNonFinalResponses
} }
STATUS current STATUS current
Lingle/Maeng/Mule/Walker 55
DESCRIPTION DESCRIPTION
"A collection of objects providing retry statistics." "A collection of objects providing retry statistics."
::= { sipCommonMIBGroups 7 } ::= { sipCommonMIBGroups 7 }
sipCommonStatsRetryExtMethodsGroup OBJECT-GROUP sipCommonStatsRetryExtMethodsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatsRetryExtMethodName, sipStatsRetryExtMethodName,
sipStatsRetryExtMethodRetries, sipStatsRetryExtMethodRetries,
sipStatsRetryExtMethodStatus sipStatsRetryExtMethodStatus
} }
skipping to change at line 3182 skipping to change at page 57, line 4
sipCommonStatusCodeNotifGroup OBJECT-GROUP sipCommonStatusCodeNotifGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCommonStatusCodeNotifSend, sipCommonStatusCodeNotifSend,
sipCommonStatusCodeNotifEmitMode, sipCommonStatusCodeNotifEmitMode,
sipCommonStatusCodeNotifThresh, sipCommonStatusCodeNotifThresh,
sipCommonStatusCodeNotifInterval, sipCommonStatusCodeNotifInterval,
sipStatusCodeNotifTo, sipStatusCodeNotifTo,
sipStatusCodeNotifFrom, sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId, sipStatusCodeNotifCallId,
sipStatusCodeNotifCSeq sipStatusCodeNotifCSeq,
sipNotifApplIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects related to controlling and attribution "A collection of objects related to controlling and attribution
of notifications common to all SIP entities." of notifications common to all SIP entities."
::= { sipCommonMIBGroups 10 } ::= { sipCommonMIBGroups 10 }
END END
5.4. SIP User Agent 5.3. SIP User Agent
SIP-UA-MIB DEFINITIONS ::= BEGIN SIP-UA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Counter32, Unsigned32,
Integer32 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
Lingle/Maeng/Mule/Walker 56
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP
NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
RowStatus RowStatus
FROM SNMPv2-TC FROM SNMPv2-TC
sipMIB
FROM SIP-MIB-SMI
applIndex applIndex
FROM NETWORK-SERVICES-MIB FROM NETWORK-SERVICES-MIB
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
sipUAMIB MODULE-IDENTITY sipUAMIB MODULE-IDENTITY
LAST-UPDATED "200102230000Z" LAST-UPDATED "200106060000Z"
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@yahoogroups.com "SIP MIB Team email: sip-mib@yahoogroups.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
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
Co-editor Joon Maeng Co-editor Joon Maeng
VTEL Corporation ipDialog, Inc.
postal: 108 Wild Basin Rd. postal: 7701 N. Lamar Blvd., Suite 304
Austin, TX 78746 Austin, TX 78752-1023
USA USA
email: joon_maeng@vtel.com email: jmaeng@ipdialog.com
phone: +1 512 437 4567 phone: +1 512 371 1770
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
postal: 495 March Road postal: 495 March Road
Kanata, ON K2K 3G1 Kanata, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: drwalker@ss8.com
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
Clarent Corporation Clarent Corporation
700 Chesapeake Drive 700 Chesapeake Drive
Redwood City, CA 94063 Redwood City, CA 94063
USA
email: jfm@clarent.com email: jfm@clarent.com
phone: +1 650 481 2835" phone: +1 650 481 2835"
DESCRIPTION DESCRIPTION
Lingle/Maeng/Mule/Walker 57
"Initial version of Session Initiation Protocol (SIP) "Initial version of Session Initiation Protocol (SIP)
User Agent (UA) MIB module. User Agent (UA) MIB module.
SIP is an application-layer signalling protocol for SIP is an application-layer signalling protocol for
creating, modifying and terminating multimedia creating, modifying and terminating multimedia
sessions with one or more participants. These sessions sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 2543 (March telephone calls. SIP is defined in RFC 2543 (March
1999). 1999).
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."
::= { sipMIB 3 } ::= { mib-2 9992 } -- to be assigned by IANA
-- -- Top-Level Components of this MIB.
-- sipUA group sipUAMIBNotifs OBJECT IDENTIFIER ::= { sipUAMIB 0 }
-- This group contains MIB objects related to SIP User Agents. sipUAMIBObjects OBJECT IDENTIFIER ::= { sipUAMIB 1 }
-- sipUAMIBConform OBJECT IDENTIFIER ::= { sipUAMIB 2 }
sipUACfg OBJECT IDENTIFIER ::= { sipUAMIB 1 }
sipUACfgSipServer OBJECT IDENTIFIER ::= { sipUACfg 1 }
sipUAStats OBJECT IDENTIFIER ::= { sipUAMIB 2 }
-- --
-- User Agent Configuration -- This MIB contains objects related to SIP User Agents.
-- --
sipUACfgSipServer OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 }
sipUAStats OBJECT IDENTIFIER ::= { sipUAMIBObjects 2 }
-- --
-- SIP Server Configuration -- SIP Server Configuration
-- --
sipUACfgSipServerTable OBJECT-TYPE sipUACfgSipServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUACfgSipServerEntry SYNTAX SEQUENCE OF SipUACfgSipServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains SIP server configuration objects "This table contains SIP server configuration objects
applicable to each SIP user agent in this system. The applicable to each SIP user agent in this system."
instances of SIP entities are uniquely identified
by applIndex."
::= { sipUACfgSipServer 1 } ::= { sipUACfgSipServer 1 }
sipUACfgSipServerEntry OBJECT-TYPE sipUACfgSipServerEntry OBJECT-TYPE
SYNTAX SipUACfgSipServerEntry SYNTAX SipUACfgSipServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of server configuration." "A row of server configuration.
INDEX { applIndex, sipUACfgSipServerIndex }
Each row represents those objects for a particular SIP
user agent present in this system. applIndex is used to
uniquely identify these instances of SIP user agents and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipUACfgSipServerAddrIndex }
::= { sipUACfgSipServerTable 1 } ::= { sipUACfgSipServerTable 1 }
SipUACfgSipServerEntry ::= SipUACfgSipServerEntry ::=
Lingle/Maeng/Mule/Walker 58
SEQUENCE { SEQUENCE {
sipUACfgSipServerAddrIndex Unsigned32, sipUACfgSipServerAddrIndex Unsigned32,
sipUACfgSipServerAddrType InetAddressType, sipUACfgSipServerAddrType InetAddressType,
sipUACfgSipServerAddr InetAddress, sipUACfgSipServerAddr InetAddress,
sipUACfgSipServerAddrStatus RowStatus sipUACfgSipServerAddrStatus RowStatus
} }
sipUACfgSipServerAddrIndex OBJECT-TYPE sipUACfgSipServerAddrIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at line 3376 skipping to change at page 60, line 25
being used by the user agent. being used by the user agent.
'notInService' : the row's address is not being used 'notInService' : the row's address is not being used
by the user agent, but will remain in the table. by the user agent, but will remain in the table.
'notReady' : key information is missing thus, preventing 'notReady' : key information is missing thus, preventing
the row from being made 'active' (eg, no the row from being made 'active' (eg, no
address specified). address specified).
'createAndGo' : only allowed if the manager also provides 'createAndGo' : only allowed if the manager also provides
Lingle/Maeng/Mule/Walker 59
a varbind for sipUACfgSipServerAddr object a varbind for sipUACfgSipServerAddr object
in the same set operation. in the same set operation.
'createAndWait' : not applicable. 'createAndWait' : not applicable.
'destroy' : the row's address will no longer be used 'destroy' : the row's address will no longer be used
by the user agent and the row will be by the user agent and the row will be
removed from the table." removed from the table."
::= { sipUACfgSipServerEntry 4 } ::= { sipUACfgSipServerEntry 4 }
-- --
-- User Agent Statistics
--
-- none at this time
--
-- Notifications
--
sipUAMIBNotif OBJECT IDENTIFIER ::= { sipUAMIB 3 }
-- none at this time
--
-- Conformance -- Conformance
-- --
sipUAMIBConformance
OBJECT IDENTIFIER ::= { sipUAMIB 4 }
sipUAMIBCompliances sipUAMIBCompliances
OBJECT IDENTIFIER ::= { sipUAMIBConformance 1 } OBJECT IDENTIFIER ::= { sipUAMIBConform 1 }
sipUAMIBGroups sipUAMIBGroups
OBJECT IDENTIFIER ::= { sipUAMIBConformance 2 } OBJECT IDENTIFIER ::= { sipUAMIBConform 2 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
sipUACompliance MODULE-COMPLIANCE sipUACompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities." "The compliance statement for SIP entities."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipUAConfigGroup } MANDATORY-GROUPS { sipUAConfigGroup }
-- sipUANotifGroup }
::= { sipUAMIBCompliances 1 } ::= { sipUAMIBCompliances 1 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipUAConfigGroup OBJECT-GROUP sipUAConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipUACfgSipServerAddrIndex,
Lingle/Maeng/Mule/Walker 60
sipUACfgSipServerAddrType, sipUACfgSipServerAddrType,
sipUACfgSipServerAddr, sipUACfgSipServerAddr,
sipUACfgSipServerStatus sipUACfgSipServerAddrStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration for "A collection of objects providing configuration for
SIP User Agents." SIP User Agents."
::= { sipUAMIBGroups 1 } ::= { sipUAMIBGroups 1 }
--sipUANotifGroup NOTIFICATION-GROUP
-- OBJECTS {
-- none at this time
-- }
-- STATUS current
-- DESCRIPTION
-- "A collection of notifications defined for SIP User
-- Agents."
-- ::= { sipMIBGroups 2 }
END END
5.5. SIP Server (Registrar, Redirect & Proxy Server) 5.4. SIP Server (Registrar, Redirect & Proxy Server)
SIP-SERVER-MIB DEFINITIONS ::= BEGIN SIP-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Counter32, Counter32,
Integer32, Integer32,
Unsigned32 Unsigned32,
Gauge32,
mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
RowStatus, RowStatus,
TruthValue, TruthValue,
TimeStamp, DateAndTime TimeStamp, DateAndTime
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
sipMIB
FROM SIP-MIB-SMI
applIndex applIndex
FROM NETWORK-SERVICES-MIB; FROM NETWORK-SERVICES-MIB
InetAddressType,
InetAddress
FROM INET-ADDRESS-MIB;
sipServerMIB MODULE-IDENTITY sipServerMIB MODULE-IDENTITY
LAST-UPDATED "200102280000Z" LAST-UPDATED "200106060000Z"
Lingle/Maeng/Mule/Walker 61
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@yahoogroups.com "SIP MIB Team email: sip-mib@yahoogroups.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
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
Co-editor Joon Maeng Co-editor Joon Maeng
VTEL Corporation ipDialog, Inc.
postal: 108 Wild Basin Rd. postal: 7701 N. Lamar Blvd., Suite 304
Austin, TX 78746 Austin, TX 78752-1023
USA USA
email: joon_maeng@vtel.com email: jmaeng@ipdialog.com
phone: +1 512 437 4567 phone: +1 512 371 1770
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
postal: 495 March Road postal: 495 March Road
Kanata, ON K2K 3G1 Kanata, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: drwalker@ss8.com
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
Clarent Corporation Clarent Corporation
700 Chesapeake Drive 700 Chesapeake Drive
Redwood City, CA 94063 Redwood City, CA 94063
USA
email: jfm@clarent.com email: jfm@clarent.com
phone: +1 650 481 2835" phone: +1 650 481 2835"
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Initial version of Session Initiation Protocol (SIP)
Server MIB module. Server MIB module.
SIP is an application-layer signalling protocol for SIP is an application-layer signalling protocol for
creating, modifying and terminating multimedia creating, modifying and terminating multimedia
sessions with one or more participants. These sessions sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet include Internet multimedia conferences and Internet
skipping to change at line 3547 skipping to change at page 62, line 53
A Proxy Server acts as both a client and a server. A Proxy Server acts as both a client and a server.
It accepts requests from other clients, either It accepts requests from other clients, either
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
Lingle/Maeng/Mule/Walker 62
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 4 } ::= { mib-2 9991 } -- to be assigned by IANA
-- Top-Level Components of this MIB.
sipServerMIBNotifs OBJECT IDENTIFIER ::= { sipServerMIB 0 }
sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 }
sipServerMIBConform OBJECT IDENTIFIER ::= { sipServerMIB 2 }
-- --
-- sipServer group -- These groups contains objects common to all SIP servers.
-- This group contains MIB objects common to Proxy and Redirect
-- Servers.
-- --
sipServerCfg OBJECT IDENTIFIER ::= { sipServerMIB 1 } sipServerCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 1 }
sipServerStats OBJECT IDENTIFIER ::= { sipServerMIB 2 } sipServerStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 2 }
-- --
-- Common Server Configuration Objects -- Common Server Configuration Objects
-- --
sipServerCfgTable OBJECT-TYPE sipServerCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerCfgEntry SYNTAX SEQUENCE OF SipServerCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable "This table contains configuration objects applicable
to SIP redirect and proxy servers. Each row represents to SIP redirect and proxy servers."
those objects for a particular SIP server present in
this system. The instances of SIP servers are uniquely
identified by applIndex."
::= { sipServerCfg 1 } ::= { sipServerCfg 1 }
sipServerCfgEntry OBJECT-TYPE sipServerCfgEntry OBJECT-TYPE
SYNTAX SipServerCfgEntry SYNTAX SipServerCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common configuration." "A row of common configuration.
Each row represents those objects for a particular SIP
server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipServerCfgTable 1 } ::= { sipServerCfgTable 1 }
SipServerCfgEntry ::= SipServerCfgEntry ::=
SEQUENCE { SEQUENCE {
sipServerHost SnmpAdminString, sipServerHostAddrType InetAddressType,
sipInformationTryingInterval Integer32, sipServerHostAddr InetAddress,
sipPgpVersion SnmpAdminString, sipPgpVersion SnmpAdminString,
sipServerContactDfltAction INTEGER, sipServerContactDfltAction INTEGER,
sipServerRespectUAAction TruthValue sipServerRespectUAAction TruthValue
} }
sipServerHost OBJECT-TYPE sipServerHostAddrType OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX InetAddressType
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 "The type of Internet address by which the SIP server
to the SIP server. It may contain a fully qualified is reachable."
domain name, or an IP address (v4 only for now)."
Lingle/Maeng/Mule/Walker 63
REFERENCE REFERENCE
"RFC 2543, Section 2" "RFC 2543, Section 2"
::= { sipServerCfgEntry 1 } ::= { sipServerCfgEntry 1 }
sipServerHostAddr OBJECT-TYPE
-- SYNTAX InetAddress (SIZE(1..254))
-- Support for 1xx Status Codes
--
sipInformationTryingInterval OBJECT-TYPE
SYNTAX Integer32 (0..60000)
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 "This is the host portion of a SIP URL that is assigned
as counted from when the request was processed. If the to the SIP server. It may contain a fully qualified
value is zero, no such retransmission is performed." domain name, or an IP address. The length of the value
will depend on the type of address specified.
sipServerHostAddrType formalizes the type of address
given by this object. It is the users responsibility
to maintain consistency between this object and the
type specified by sipServerHostAddrType."
REFERENCE
"RFC 2543, Section 2"
::= { sipServerCfgEntry 2 } ::= { sipServerCfgEntry 2 }
-- --
-- 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
skipping to change at line 3663 skipping to change at page 65, line 4
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
::= { sipServerCfgEntry 4 } ::= { sipServerCfgEntry 4 }
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
Lingle/Maeng/Mule/Walker 64
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 sipServerContactDfltAction
is used."
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
::= { sipServerCfgEntry 5 } ::= { sipServerCfgEntry 5 }
-- --
-- Common Server Statistics
--
-- none at this time
-- 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 ::= { sipServerMIBObjects 3 }
sipProxyCfg OBJECT IDENTIFIER ::= { sipProxy 1 } sipProxyStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 4 }
sipProxyStats OBJECT IDENTIFIER ::= { sipProxy 2 }
-- --
-- Proxy Server Configuration -- Proxy Server Configuration
-- --
sipProxyCfgTable OBJECT-TYPE sipProxyCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipProxyCfgEntry SYNTAX SEQUENCE OF SipProxyCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable "This table contains configuration objects applicable
to SIP proxy servers. Each row represents those objects to SIP proxy servers."
for a particular SIP proxy server present in this system.
The instances of SIP proxy servers are uniquely identified
by applIndex."
::= { sipProxyCfg 1 } ::= { sipProxyCfg 1 }
sipProxyCfgEntry OBJECT-TYPE sipProxyCfgEntry OBJECT-TYPE
SYNTAX SipProxyCfgEntry SYNTAX SipProxyCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common configuration." "A row of common proxy configuration.
Each row represents those objects for a particular SIP
server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipProxyCfgTable 1 } ::= { sipProxyCfgTable 1 }
SipProxyCfgEntry ::= SipProxyCfgEntry ::=
SEQUENCE { SEQUENCE {
sipRequestMaxExpires Unsigned32, sipRequestMaxExpires Unsigned32,
sipProxyStateful TruthValue, sipProxyStatefulness INTEGER,
sipProxySendsCancel TruthValue, sipProxySendsCancel TruthValue,
sipProxyForwardAll1xx TruthValue, sipProxyForwardAll1xx TruthValue,
sipProxyRecursion TruthValue, sipProxyRecursion TruthValue,
sipProxyProvideAlternatives TruthValue, sipProxyProvideAlternatives TruthValue,
sipProxyRecordRoute TruthValue, sipProxyRecordRoute TruthValue,
Lingle/Maeng/Mule/Walker 65
sipProxyStateTimeout Integer32, sipProxyStateTimeout Integer32,
sipProxyAuthMethod BITS, sipProxyAuthMethod BITS,
sipProxyAuthPgpAlgorithm INTEGER, sipProxyAuthPgpAlgorithm INTEGER,
sipProxyAuthRealm SnmpAdminString, sipProxyAuthRealm SnmpAdminString,
sipProxyNonceLifeTime Integer32, sipProxyNonceLifeTime Integer32,
sipPgpPrivateKey OCTET STRING sipPgpPrivateKey OCTET STRING
} }
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
server returns a 400 Bad Request response."
::= { sipProxyCfgEntry 1 } ::= { sipProxyCfgEntry 1 }
sipProxyStateful OBJECT-TYPE sipProxyStatefulness OBJECT-TYPE
SYNTAX TruthValue SYNTAX INTEGER {
stateless(1),
transactionStateful(2),
callStateful(3)
}
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the default for "This object specifies the default mode of operation for
the the proxy server is to operate in stateful mode. the proxy server entity.
When stateful, a proxy remembers the incoming request A stateless proxy entity does not maintain state
which generated outgoing requests, and the outgoing for a SIP transaction. A stateless proxy forwards every
requests. A stateless proxy forgets all information request it receives downstream and every response it
once an outgoing request is generated. receives upstream. If the value of this object is
stateless(1), the proxy defaults to stateless operations.
If the value of this object is TRUE, the proxy defaults A transaction stateful proxy does maintain state
to stateful. If FALSE, the proxy defaults to stateless." information for the duration of a SIP transaction. Also
known as a stateful proxy. If the value if this object
is transactionStateful(2), the proxy is stateful on a
transaction basis.
A call stateful proxy does retain state that persists
for the duration of a call initiated through it. To
properly manage that state, the proxy will normally
need to receive the BYE requests that terminate the call.
If the value of this object is callStateful(3), the
proxy is call stateful."
REFERENCE REFERENCE
"RFC 2543, Section 12.3" "RFC 2543, Section 12.3"
::= { sipProxyCfgEntry 2 } ::= { sipProxyCfgEntry 2 }
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"
::= { sipProxyCfgEntry 3 } ::= { sipProxyCfgEntry 3 }
Lingle/Maeng/Mule/Walker 66
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, except the 100 Trying response, all 1xx responses, except the 100 Trying response,
upstream towards the source of the request. upstream towards the source of the request.
If the value of this object is TRUE, the 1xx responses are If the value of this object is TRUE, the 1xx responses are
skipping to change at line 3829 skipping to change at page 68, line 4
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 }
::= { sipProxyCfgEntry 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
Lingle/Maeng/Mule/Walker 67
to the Record-Route header as a default action. This to the Record-Route header as a default action. This
header is used to list the proxies that insist on being in header is used to list the proxies that insist on being in
the signalling path for subsequent requests related to the the signalling path for subsequent requests related to the
call-leg. 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 the value is FALSE, the proxy doesn't add if required. If the value is FALSE, the proxy doesn't add
itself to the Record-Route header." itself to the Record-Route header."
REFERENCE REFERENCE
"RFC 2543, Section 6.29" "RFC 2543, Section 6.29"
::= { sipProxyCfgEntry 7 } ::= { sipProxyCfgEntry 7 }
sipProxyStateTimeout 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 INVITE response that a stateful proxy retains state
retains state in order to handle possible retransmissions 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"
::= { sipProxyCfgEntry 8 } ::= { sipProxyCfgEntry 8 }
-- --
-- Security -- Security
-- --
sipProxyAuthMethod OBJECT-TYPE sipProxyAuthMethod OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
none(0), none(0),
skipping to change at line 3896 skipping to change at page 69, line 12
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
Lingle/Maeng/Mule/Walker 68
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the PGP algorithm the proxy uses." "This object specifies the PGP algorithm the proxy uses."
::= { sipProxyCfgEntry 10 } ::= { 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
skipping to change at line 3940 skipping to change at page 69, line 55
SYNTAX OCTET STRING(SIZE(0..255)) SYNTAX OCTET STRING(SIZE(0..255))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
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."
::= { sipProxyCfgEntry 13 } ::= { sipProxyCfgEntry 13 }
sipRxProxyAuthTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRxProxyAuthEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains authentication data for peers of each
proxy server in this system. The instances of proxy
server are uniquely identified by the applIndex."
::= { sipProxyCfg 2 }
sipRxProxyAuthEntry OBJECT-TYPE
SYNTAX SipRxProxyAuthEntry
MAX-ACCESS not-accessible
Lingle/Maeng/Mule/Walker 69
STATUS current
DESCRIPTION
"This object contains authentication data for a single
peer."
INDEX { applIndex, sipRxProxyAuthIndex }
::= { sipRxProxyAuthTable 1 }
SipRxProxyAuthEntry ::=
SEQUENCE {
sipRxProxyAuthIndex Unsigned32,
sipRxProxyAuthRealm SnmpAdminString,
sipRxProxyAuthPassword OCTET STRING,
sipRxProxyAuthStatus RowStatus
}
sipRxProxyAuthIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object uniquely identifies a conceptual row in the
table."
::= { sipRxProxyAuthEntry 1 }
sipRxProxyAuthRealm OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object contains the realm that is specified by
another server when it is authenticating this server."
::= { sipRxProxyAuthEntry 2 }
sipRxProxyAuthPassword OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(1..4095))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object contains the password that this server uses
when it is being authenticated by another server using the
realm specified by the sipRxProxyAuthRealm object in this
table row."
::= { sipRxProxyAuthEntry 3 }
sipRxProxyAuthStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The row status of the entry. This object is required
to create or delete rows remotely by a manager."
::= { sipRxProxyAuthEntry 4 }
-- --
-- Proxy Server Statistics -- Proxy Server Statistics
-- --
Lingle/Maeng/Mule/Walker 70
sipProxyStatsTable OBJECT-TYPE sipProxyStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipProxyStatsEntry SYNTAX SEQUENCE OF SipProxyStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the statistics objects applicable "This table contains the statistics objects applicable
to all SIP Proxy Servers in this system. 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 } ::= { sipProxyStats 1 }
sipProxyStatsEntry OBJECT-TYPE sipProxyStatsEntry OBJECT-TYPE
SYNTAX SipProxyStatsEntry SYNTAX SipProxyStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics." "A row of summary statistics.
Each row represents those objects for a particular SIP
server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipProxyStatsTable 1 } ::= { sipProxyStatsTable 1 }
SipProxyStatsEntry ::= SipProxyStatsEntry ::=
SEQUENCE { SEQUENCE {
sipNumProxyRequireFailures Counter32 sipNumProxyRequireFailures Counter32
} }
sipNumProxyRequireFailures OBJECT-TYPE sipNumProxyRequireFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at line 4053 skipping to change at page 70, line 43
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."
::= { sipProxyStatsEntry 1 } ::= { sipProxyStatsEntry 1 }
-- --
-- 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 ::= { sipServerMIBObjects 5 }
sipRedirCfg OBJECT IDENTIFIER ::= { sipRedir 1 } sipRedirStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 6 }
sipRedirStats OBJECT IDENTIFIER ::= { sipRedir 2 }
-- none at this time -- none at this time
-- --
-- sipReg group
-- This group contains MIB objects related to SIP Registrars. -- This group contains MIB objects related to SIP Registrars.
-- --
sipReg OBJECT IDENTIFIER ::= { sipServerMIB 5 } sipRegCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 7 }
sipRegCfg OBJECT IDENTIFIER ::= { sipReg 1 } sipRegStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 8 }
sipRegStats OBJECT IDENTIFIER ::= { sipReg 2 }
Lingle/Maeng/Mule/Walker 71
-- --
-- Registrar Configuration -- Registrar Configuration
-- --
sipRegCfgTable OBJECT-TYPE sipRegCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegCfgEntry SYNTAX SEQUENCE OF SipRegCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable "This table contains configuration objects applicable
SIP registrars. Each row represents those objects SIP registrars."
for a particular SIP registrar present in this system.
The instances of SIP registrars are uniquely identified
by applIndex."
::= { sipRegCfg 1 } ::= { sipRegCfg 1 }
sipRegCfgEntry OBJECT-TYPE sipRegCfgEntry OBJECT-TYPE
SYNTAX SipRegCfgEntry SYNTAX SipRegCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common configuration." "A row of common registrar configuration.
Each row represents those objects for a particular SIP
server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipRegCfgTable 1 } ::= { sipRegCfgTable 1 }
SipRegCfgEntry ::= SipRegCfgEntry ::=
SEQUENCE { SEQUENCE {
sipRegAllowThirdParty TruthValue, sipRegAllowThirdParty TruthValue,
sipRegContactDfltExpiryDuration Unsigned32,
sipRegContactDfltExpiryDate DateAndTime,
sipRegMaxContactExpiryDate Unsigned32, sipRegMaxContactExpiryDate Unsigned32,
sipRegRespHasContacts TruthValue,
sipRegMaxUsers Unsigned32, sipRegMaxUsers Unsigned32,
sipRegCurrentUsers Gauge32, sipRegCurrentUsers Gauge32,
sipRegDfltRegActiveInterval Unsigned32 sipRegDfltRegActiveInterval Unsigned32
} }
sipRegAllowThirdParty OBJECT-TYPE sipRegAllowThirdParty OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at line 4127 skipping to change at page 71, line 55
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"
::= { sipRegCfgEntry 1 } ::= { sipRegCfgEntry 1 }
Lingle/Maeng/Mule/Walker 72
sipRegContactDfltExpiryDuration OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the default expiration (time-to-
live) of Contact information that is provided by User
Agents when registering with this Registrar. This value
is only used when no expiration has been specified by the
user in the REGISTER
request.
If the value is applied to a registration and is different
from the default (one hour), the server must return the
value to the registered User Agent.
The value contained in this object only applies if the
value of the sipContactDfltExpiryDate object is NULL. If
the value of this object applies, and is zero, then no
default expiry is applied to registered contact
information."
REFERENCE
"RFC 2543, Section 4.2.6"
DEFVAL { 3600 }
::= { sipRegCfgEntry 2 }
sipRegContactDfltExpiryDate OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the default expiration date (time-
to-live) of Contact information that is provided by User
Agents when registering with this Registrar. This value
is only used when no expiration has been specified by the
user in the REGISTER request.
If this value is applied to a registration, the server
must return the value to the registered User Agent.
The value contained in this object only applies if the
value of the sipContactDfltExpiryDuration object is zero.
If the value of this object applies, and is NULL, then no
default expiry is applied to
registered contact information."
REFERENCE
"RFC 2543, Section 4.2.6"
::= { sipRegCfgEntry 3 }
sipRegMaxContactExpiryDate OBJECT-TYPE sipRegMaxContactExpiryDate 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 expiry that may be "This object specifies the maximum expiry that may be
Lingle/Maeng/Mule/Walker 73
requested by a User Agent for a particular Contact. User requested by a User Agent for a particular Contact. User
Agents can specify expiry using either an Expiry header in Agents can specify expiry using either an Expiry header in
a REGISTER request, or using an Expires parameter in a a REGISTER request, or using an Expires parameter in a
Contact header in a REGISTER request. If the value Contact header in a REGISTER request. If the value
requested by the User Agent is greater than the value of requested by the User Agent is greater than the value of
this object, then the contact information is given the this object, then the contact information is given the
duration specified by this object, and that duration duration specified by this object, and that duration
is indicated to the User Agent in the response." is indicated to the User Agent in the response."
DEFVAL { 4294967295 } DEFVAL { 4294967295 }
::= { sipRegCfgEntry 4 } ::= { sipRegCfgEntry 2 }
sipRegRespHasContacts OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies whether or not the Registrar should
return all currently reachable locations for a
successfully registering party in the REGISTER response
message.
If the value of this object is TRUE, the Registrar returns
the locations in the REGISTER response. If the value is
FALSE, no location information is provided."
::= { sipRegCfgEntry 5 }
sipRegMaxUsers OBJECT-TYPE sipRegMaxUsers OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum number of users that the "This object specifies the maximum number of users that the
registrar supports. The current number of users is registrar supports. The current number of users is
reflected by sipRegCurrentUsers." reflected by sipRegCurrentUsers."
::= { sipRegCfgEntry 6 } ::= { sipRegCfgEntry 3 }
sipRegCurrentUsers OBJECT-TYPE sipRegCurrentUsers 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 specifies the number of users currently "This object specifies the number of users currently
configured on the registrar." configured on the registrar."
::= { sipRegCfgEntry 7 } ::= { sipRegCfgEntry 4 }
sipRegDfltRegActiveInterval OBJECT-TYPE sipRegDfltRegActiveInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default time interval the "This object specifies the default time interval the
Registrar considers registrations to be active. The Registrar considers registrations to be active. The
value is used to compute the Expires header in the value is used to compute the Expires header in the
REGISTER response. If a user agent requests a time REGISTER response. If a user agent requests a time
interval shorter than specified by this object, the interval shorter than specified by this object, the
Registrar should honor that request." Registrar should honor that request. If a Contact
entry does not have an 'expires' parameter, this
Lingle/Maeng/Mule/Walker 74 object is used as the default value."
REFERENCE "Expires header, section 6.23 RFC2543" REFERENCE "Expires header, section 6.20 RFC2543"
::= { sipRegCfgEntry 8 } ::= { sipRegCfgEntry 5 }
-- --
-- Per User Information -- Per User Information
-- --
sipRegUserTable OBJECT-TYPE sipRegUserTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegUserEntry SYNTAX SEQUENCE OF SipRegUserEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on all users registered to "This table contains information on all users registered to
each Registrar in this system. The instances of SIP each Registrar in this system."
Registrar are uniquely identified by applIndex."
::= { sipRegCfg 2 } ::= { sipRegCfg 2 }
sipRegUserEntry OBJECT-TYPE sipRegUserEntry OBJECT-TYPE
SYNTAX SipRegUserEntry SYNTAX SipRegUserEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single user "This entry contains information for a single user
registered to this Registrar." registered to this Registrar.
Each row represents those objects for a particular SIP
server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipUserIndex } INDEX { applIndex, sipUserIndex }
::= { sipRegUserTable 1 } ::= { sipRegUserTable 1 }
SipRegUserEntry ::= SipRegUserEntry ::=
SEQUENCE { SEQUENCE {
sipUserIndex Unsigned32, sipUserIndex Unsigned32,
sipUserUri SnmpAdminString, sipUserUri SnmpAdminString,
sipUserPassword OCTET STRING,
sipUserAuthenticationFailures Counter32, sipUserAuthenticationFailures Counter32,
sipUserTableRowStatus RowStatus sipUserTableRowStatus RowStatus
} }
sipUserIndex OBJECT-TYPE sipUserIndex 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
skipping to change at line 4301 skipping to change at page 73, line 51
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the user's address-of-record. It is "This object contains the user's address-of-record. It is
the main form by which the registrar knows the user. The the main form by which the registrar knows the user. The
format is typically 'user@domain'. It is contained in the format is typically 'user@domain'. It is contained in the
To header for all REGISTER requests." To header for all REGISTER requests."
::= { sipRegUserEntry 2 } ::= { sipRegUserEntry 2 }
sipUserPassword OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..255))
Lingle/Maeng/Mule/Walker 75
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the password that the user must
enter when being authenticated."
::= { sipRegUserEntry 3 }
sipUserAuthenticationFailures OBJECT-TYPE sipUserAuthenticationFailures 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 times the "This object contains a count of the number of times the
user has failed authentication." user has failed authentication."
::= { sipRegUserEntry 4 } ::= { sipRegUserEntry 3 }
sipUserTableRowStatus OBJECT-TYPE sipUserTableRowStatus 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."
::= { sipRegUserEntry 5 } ::= { sipRegUserEntry 4 }
-- --
-- Per Contact Information -- Per Contact Information
-- --
sipContactTable OBJECT-TYPE sipContactTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipContactEntry SYNTAX SEQUENCE OF SipContactEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on every location where a "This table contains information on every location where a
registered user (specified by sipUserIndex) wishes to be registered user (specified by sipUserIndex) wishes to be
found (i.e. the user has provided Contact information to found (i.e. the user has provided Contact information to
each SIP Registrar in this system). each SIP Registrar in this system)."
The instances of SIP Registrar are uniquely identified by
applIndex."
::= { sipRegCfg 3 } ::= { sipRegCfg 3 }
sipContactEntry OBJECT-TYPE sipContactEntry OBJECT-TYPE
SYNTAX SipContactEntry SYNTAX SipContactEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single Contact. "This entry contains information for a single Contact.
Multiple contacts may exist for a single user." Multiple contacts may exist for a single user.
Each row represents those objects for a particular SIP
server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipUserIndex, sipContactIndex } INDEX { applIndex, sipUserIndex, sipContactIndex }
::= { sipContactTable 1 } ::= { sipContactTable 1 }
SipContactEntry ::= SipContactEntry ::=
SEQUENCE { SEQUENCE {
sipContactIndex Unsigned32, sipContactIndex Unsigned32,
sipContactDisplayName SnmpAdminString, sipContactDisplayName SnmpAdminString,
sipContactURI SnmpAdminString, sipContactURI SnmpAdminString,
Lingle/Maeng/Mule/Walker 76
sipContactLastUpdated TimeStamp, sipContactLastUpdated TimeStamp,
sipContactExpiry DateAndTime, sipContactExpiry DateAndTime,
sipContactPreference OCTET STRING, sipContactPreference OCTET STRING,
sipContactAction INTEGER, sipContactAction INTEGER,
sipContactRetryAfter DateAndTime sipContactRetryAfter DateAndTime
} }
sipContactIndex OBJECT-TYPE sipContactIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at line 4422 skipping to change at page 75, line 49
this object is also updated." this object is also updated."
::= { sipContactEntry 4 } ::= { sipContactEntry 4 }
sipContactExpiry OBJECT-TYPE sipContactExpiry OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the date and time when the contact "This object contains the date and time when the contact
Lingle/Maeng/Mule/Walker 77
information will no longer be valid. Such times may be information will no longer be valid. Such times may be
specified by the user at registration (Expires header or specified by the user at registration (Expires header or
expiry parameter in the Contact information), or a system expiry parameter in the Contact information), or a system
default can be applied." default can be applied."
::= { sipContactEntry 5 } ::= { sipContactEntry 5 }
sipContactPreference OBJECT-TYPE sipContactPreference OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..255)) SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at line 4480 skipping to change at page 76, line 49
After header." After header."
REFERENCE REFERENCE
"RFC 2543, Section 6.32" "RFC 2543, Section 6.32"
::= { sipContactEntry 8 } ::= { sipContactEntry 8 }
-- --
-- Registrar Statistics -- Registrar Statistics
-- --
sipRegStatsTable OBJECT-TYPE sipRegStatsTable OBJECT-TYPE
Lingle/Maeng/Mule/Walker 78
SYNTAX SEQUENCE OF SipRegStatsEntry SYNTAX SEQUENCE OF SipRegStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the summary statistics objects "This table contains the summary statistics objects
applicable to all SIP Registrars in this system. applicable to all SIP Registrars in this system."
Each row represents those objects for a particular
SIP Registrar. The instances of SIP Registrars are
uniquely identified by applIndex."
::= { sipRegStats 1 } ::= { sipRegStats 1 }
sipRegStatsEntry OBJECT-TYPE sipRegStatsEntry OBJECT-TYPE
SYNTAX SipRegStatsEntry SYNTAX SipRegStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics." "A row of summary statistics.
Each row represents those objects for a particular SIP
server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipRegStatsTable 1 } ::= { sipRegStatsTable 1 }
SipRegStatsEntry ::= SipRegStatsEntry ::=
SEQUENCE { SEQUENCE {
sipRegAcceptedRegistrations Counter32, sipRegAcceptedRegistrations Counter32,
sipRegRejectedRegistrations Counter32 sipRegRejectedRegistrations Counter32
} }
sipRegAcceptedRegistrations OBJECT-TYPE sipRegAcceptedRegistrations OBJECT-TYPE
skipping to change at line 4529 skipping to change at page 77, line 44
sipRegRejectedRegistrations OBJECT-TYPE sipRegRejectedRegistrations 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 REGISTER "This object contains a count of the number REGISTER
requests that have been rejected by the Registrar." requests that have been rejected by the Registrar."
::= { sipRegStatsEntry 2 } ::= { sipRegStatsEntry 2 }
-- --
-- Notifications
--
sipServerMIBNotif OBJECT IDENTIFIER ::= { sipServerMIB 5 }
sipProxyNotif OBJECT IDENTIFIER ::= { sipServerMIBNotif 1 }
sipRedirNotif OBJECT IDENTIFIER ::= { sipServerMIBNotif 2 }
-- none at this time
Lingle/Maeng/Mule/Walker 79
--
-- Conformance -- Conformance
-- --
sipServerMIBConformance
OBJECT IDENTIFIER ::= { sipServerMIB 6 }
sipServerMIBCompliances sipServerMIBCompliances
OBJECT IDENTIFIER ::= { sipServerMIBConformance 1 } OBJECT IDENTIFIER ::= { sipServerMIBConform 1 }
sipServerMIBGroups sipServerMIBGroups
OBJECT IDENTIFIER ::= { sipServerMIBConformance 2 } OBJECT IDENTIFIER ::= { sipServerMIBConform 2 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
sipProxyServerCompliance MODULE-COMPLIANCE sipProxyServerCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities acting "The compliance statement for SIP entities acting
as proxy servers." as proxy servers."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup, MANDATORY-GROUPS { sipServerConfigGroup,
sipProxyConfigGroup, sipProxyConfigGroup,
sipProxyStatsGroup } sipProxyStatsGroup }
-- sipProxyNotifGroup,
-- sipServerStatsGroup,
-- sipServerNotifGroup }
::= { sipServerMIBCompliances 1 } ::= { sipServerMIBCompliances 1 }
sipRedirectServerCompliance MODULE-COMPLIANCE sipRedirectServerCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities acting "The compliance statement for SIP entities acting
as redirect servers." as redirect servers."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup } MANDATORY-GROUPS { sipServerConfigGroup }
-- sipServerStatsGroup,
-- sipServerNotifGroup,
-- sipRedirectConfigGroup,
-- sipRedirectStatsGroup,
-- sipRedirectNotifGroup }
::= { sipServerMIBCompliances 2 } ::= { sipServerMIBCompliances 2 }
sipRegistrarServerCompliance MODULE-COMPLIANCE sipRegistrarServerCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities acting "The compliance statement for SIP entities acting
as registrars." as registrars."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup, MANDATORY-GROUPS { sipServerConfigGroup,
sipRegistrarConfigGroup, sipRegistrarConfigGroup,
sipRegistrarStatsGroup } sipRegistrarStatsGroup }
Lingle/Maeng/Mule/Walker 80
-- sipRegistrarNotifGroup,
-- sipServerStatsGroup,
-- sipServerNotifGroup,
::= { sipServerMIBCompliances 3 } ::= { sipServerMIBCompliances 3 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipServerConfigGroup OBJECT-GROUP sipServerConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipServerHost, sipServerHostAddrType,
sipInformationTryingInterval, sipServerHostAddr,
sipPgpVersion, sipPgpVersion,
sipServerDfltAction, sipServerContactDfltAction,
sipServerRespectUAAction sipServerRespectUAAction
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration common "A collection of objects providing configuration common
to SIP Proxy and Redirect servers." to SIP Proxy and Redirect servers."
::= { sipServerMIBGroups 1 } ::= { 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 sipProxyConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipRequestMaxExpires, sipRequestMaxExpires,
sipProxyStateful, sipProxyStatefulness,
sipProxySendsCancel, sipProxySendsCancel,
sipProxyForwardAll1xx, sipProxyForwardAll1xx,
sipProxyRecursion, sipProxyRecursion,
sipProxyProvideAlternatives, sipProxyProvideAlternatives,
sipProxyRecordRoute, sipProxyRecordRoute,
sipProxyStateTimeout, sipProxyStateTimeout,
sipProxyAuthMethod, sipProxyAuthMethod,
sipProxyAuthPgpAlgorithm, sipProxyAuthPgpAlgorithm,
sipProxyAuthRealm, sipProxyAuthRealm,
sipProxyNonceLifeTime, sipProxyNonceLifeTime,
sipPgpPrivateKey, sipPgpPrivateKey
sipRxProxyAuthRealm,
sipRxProxyAuthPassword,
sipRxProxyAuthStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration for "A collection of objects providing configuration for
Lingle/Maeng/Mule/Walker 81
SIP Proxy servers." SIP Proxy servers."
::= { sipServerMIBGroups 3 } ::= { sipServerMIBGroups 2 }
sipProxyStatsGroup OBJECT-GROUP sipProxyStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipNumProxyRequireFailures sipNumProxyRequireFailures
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics for "A collection of objects providing statistics for
SIP Proxy servers." SIP Proxy servers."
::= { sipServerMIBGroups 4 } ::= { sipServerMIBGroups 3 }
--sipProxyNotifGroup NOTIFICATION-GROUP
-- OBJECTS {
-- none at this time
-- }
-- STATUS current
-- DESCRIPTION
-- "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 }
sipRegistrarConfigGroup OBJECT-GROUP sipRegistrarConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipRegAllowThirdParty, sipRegAllowThirdParty,
sipRegContactDfltExpiryDuration,
Lingle/Maeng/Mule/Walker 82
sipRegContactDfltExpiryDate,
sipRegMaxContactExpiryDate, sipRegMaxContactExpiryDate,
sipRegRespHasContacts,
sipRegMaxUsers, sipRegMaxUsers,
sipRegCurrentUsers, sipRegCurrentUsers,
sipRegDfltRegActiveInterval, sipRegDfltRegActiveInterval,
sipUserUri, sipUserUri,
sipUserPassword,
sipUserAuthenticationFailures, sipUserAuthenticationFailures,
sipUserTableRowStatus, sipUserTableRowStatus,
sipContactDisplayName, sipContactDisplayName,
sipContactURI, sipContactURI,
sipContactLastUpdated, sipContactLastUpdated,
sipContactExpiry, sipContactExpiry,
sipContactPreference, sipContactPreference,
sipContactAction, sipContactAction,
sipContactRetryAfter sipContactRetryAfter
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration for "A collection of objects providing configuration for
SIP Registrars." SIP Registrars."
::= { sipServerMIBGroups 9 } ::= { sipServerMIBGroups 4 }
sipRegistrarStatsGroup OBJECT-GROUP sipRegistrarStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipRegAcceptedRegistrations, sipRegAcceptedRegistrations,
sipRegRejectedRegistrations sipRegRejectedRegistrations
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics for "A collection of objects providing statistics for
SIP Registrars." SIP Registrars."
::= { sipServerMIBGroups 10 } ::= { sipServerMIBGroups 5 }
--sipRegistrarNotifGroup NOTIFICATION-GROUP
-- OBJECTS {
-- none at this time
-- }
-- STATUS current
-- DESCRIPTION
-- "A collection of notifications defined for SIP
-- Registrars."
-- ::= { sipServerMIBGroups 11 }
END END
6. Security Considerations 6. Changes from previous drafts
o Changes from draft-ietf-sip-mib-02.txt
The following changes were made based on review comments to the
previous version of the draft.
In general
o Eliminated the SIP-MIB-SMI modules. Each MIB module will now
get it's own IANA OID.
o Top-level OID subtrees restructured in each MIB.
o General cleanup/removal of "placeholder" OID subtrees
for object groups and notifications that never materialized.
Regarding SIP-COMMON-MIB
o Removed sipCfgInitialTimerAck.
o Removed sipCfgRetryAck.
o Removed sipStatsRetryAcks.
o sipCommonStatsRetryExtMethodEntry was missing its INDEX
clause.
o sipNumUnsupportedUris OID was "5" when it was the
only object in the table. OID is now "1".
o High-level OID structure of the MIB is now sequential.
o Incorrect object descriptor for sipCfgInitialTimerRsp
inconsistent with reference in compliance section.
o Inconsistencies between sipCommonStatsRetryGroup definition
and SipCommonStatsRetryEntry OBJECT-TYPE corrected.
o sipNotifApplIndex was not in any object group in the
conformance section.
Regarding SIP-SERVER-MIB
o Removed sipInformationTryingInterval.
o Removed sipRxProxyAuthTable.
o Removed sipRegRespHasContacts.
o Removed sipRegContactDfltExpiryDate.
o Removed sipRegContactDfltExpiryDuration.
o Removed sipUserPassword.
o sipRequestMaxExpires DESCRIPTION changed to no
longer specifically mention 400 response.
o sipProxyStateful object descriptor changed to
sipProxyStatefullness and the SYNTAX changed
from TruthValue to an enumerated INTEGER.
o sipProxyStateTimeout DESCRIPTION changed to now reflect only
INVITE.
o Gauge32 was not being IMPORTed.
o sipServerContactDfltAction showed up in conformance
and other object descriptions in an older form.
o sipServerHost replaced with InetAddressType/InetAddress
object pair (sipServerHostAddrType & sipServerHostAddr).
Regarding SIP-UA-MIB
o IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex.
o sipUACfgSipServerEntry was referencing the wrong
auxilliary object and listing that object in the conformance
section.
o sipUACfgSipServerEntry listed sipUACfgSipServerStatus
when it should have been listing sipUACfgSipServerAddrStatus.
o SIP-UA-MIB IMPORTed Counter32, but never used it.
Removed the IMPORT of Counter32.
7. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
Lingle/Maeng/Mule/Walker 83
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
The managed objects in this MIB contain sensitive information since, The managed objects in this MIB contain sensitive information since,
collectively, they allow tracing and influencing of connections in collectively, they allow tracing and influencing of connections in
SIP entities and provide information of their connection SIP entities and provide information of their connection
characteristics. characteristics.
It is thus important to control even GET access to these objects and It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these objects when sending possibly to even encrypt the values of these objects when sending
them over the network via SNMP. Not all versions of SNMP provide them over the network via SNMP. Not all versions of SNMP provide
features for such a secure environment. features for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is itself is secure (for example by using IPSec), even then, there is
no control as to who on the secure network is allowed to access and no control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB. GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2574 [18] and the View-based of the User-based Security Model RFC 2574 [12] and the View-based
Access Control Model RFC 2575 [19] is recommended. Access Control Model RFC 2575 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
users) that have legitimate rights to indeed GET or SET users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
7. Intellectual Property 8. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances claims of rights made available for publication and any assurances
skipping to change at line 4816 skipping to change at page 82, line 16
to obtain a general license or permission for the use of such to obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification proprietary rights by implementors or users of this specification
can be obtained from the IETF Secretariat. can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
8. Full Copyright Statement 9. Full Copyright Statement
Lingle/Maeng/Mule/Walker 84
Copyright(C) The Internet Society (2001). All Rights Reserved. This Copyright(C) The Internet Society (2001). All Rights Reserved. This
document and translations of it may be copied and furnished to document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
skipping to change at line 4844 skipping to change at page 83, line 5
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Lingle/Maeng/Mule/Walker 85 10. References
9. References
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, January 1998. Describing SNMP Management Frameworks", RFC 2571, April 1999.
[2] Rose, M. and K. McCloghrie, "Structure and Identification of [2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990. 1155, May 1990.
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991. RFC 1212, March 1991.
[4] Rose, M., "A Convention for Defining Traps for use with the [4] Rose, M., "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991. SNMP", RFC 1215, March 1991.
skipping to change at line 4886 skipping to change at page 83, line 45
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January "Introduction to Community-based SNMPv2", RFC 1901, January
1996. 1996.
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network "Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996. Management Protocol (SNMPv2)", RFC 1906, January 1996.
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, January 1998. Protocol (SNMP)", RFC 2572, April 1999.
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2274, January 1998. (SNMPv3)", RFC 2574, April 1999.
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Operations for Version 2 of the Simple Network Management "Protocol Operations for Version 2 of the Simple Network
Protocol (SNMPv2)", January 1996. Management Protocol (SNMPv2)", RFC 1905, January 1996.
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
2273, January 1998 2573, April 1999.
Lingle/Maeng/Mule/Walker 86
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, January 1998. (SNMP)", RFC 2575, April 1999.
[16] Bradner, S., "Key words for use in RFCs to Indicate Requirement [16] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[17] M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg, [17] M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg,
"SIP: Session Initiation Protocol", RFC 2543, March 1999. "SIP: Session Initiation Protocol", RFC 2543, March 1999.
[18] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) [18] N. Freed, and S, Killle, ˘Network Services Monitor MIB÷, RFC
for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2574, April 1999.
[19] N. Freed, and S, Killle, ˘Network Services Monitor MIB÷,RFC
2788, March 2000 2788, March 2000
[20] S. Donavan, "The SIP INFO Method", RFC 2976, October 2000 [19] S. Donavan, "The SIP INFO Method", RFC 2976, October 2000
10. Author's Addresses [20] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999.
11. Author's Addresses
Kevin Lingle Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Road 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 USA Research Triangle Park, NC 27709
USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
Joon Maeng Joon Maeng
VTEL Corporation ipDialog, Inc.
108 Wild Basin Rd. 7701 N. Lamar Blvd., Suite 304
Austin, TX 78746 USA Austin, TX 78752-1023
email: joon_maeng@vtel.com USA
phone: +1 512 437 4567 email: jmaeng@ipdialog.com
phone: +1 512-371-1770
Jean-Francois MuleĂ Jean-Francois MuleĂ
Clarent Corporation Clarent Corporation
700 Chesapeake Drive, MS 101 700 Chesapeake Drive, MS 101
Redwood City, CA 94063 Redwood City, CA 94063
USA
email: jfm@clarent.com email: jfm@clarent.com
phone: +1 650 481 2835 phone: +1 650 481 2835
Dave Walker Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
495 March Road 495 March Road
Kanata, ON K2K 3G1 Kanata, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: drwalker@ss8.com
phone: +1 613 592 2100 phone: +1 613 592 2100
Lingle/Maeng/Mule/Walker 87
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/