draft-ietf-sip-mib-09.txt   draft-ietf-sip-mib-10.txt 
SIP Working Group K. Lingle SIP Working Group K. Lingle
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: August 1, 2005 J. Mule Expires: September 4, 2006 J. Mule
CableLabs CableLabs
J. Maeng J. Maeng
D. Walker D. Walker
January 28, 2005 March 3, 2006
Management Information Base for Session Initiation Protocol (SIP) Management Information Base for the Session Initiation Protocol (SIP)
draft-ietf-sip-mib-09.txt draft-ietf-sip-mib-10.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of Section 3 of RFC 3667. By submitting this Internet-Draft, each applicable patent or other IPR claims of which he or she is aware
author represents that any applicable patent or other IPR claims of have been or will be disclosed, and any of which he or she becomes
which he or she is aware have been or will be disclosed, and any of aware will be disclosed, in accordance with Section 6 of BCP 79.
which he or she become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 1, 2005. This Internet-Draft will expire on September 4, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
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 to In particular, it describes a set of managed objects that are used to
manage Session Initiation Protocol (SIP) entities, which include User manage Session Initiation Protocol (SIP) entities, which include User
Agents, Proxy, Redirect and Registrar servers. Agents, Proxy, Redirect and Registrar servers.
Table of Contents Table of Contents
1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . 3 3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Structure of SIP MIB . . . . . . . . . . . . . . . . . . . . 3 5. Structure of the SIP MIB . . . . . . . . . . . . . . . . . . . 4
5.1 Textual Conventions . . . . . . . . . . . . . . . . . . . 5 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6
5.2 Relationship to the Network Services MIB . . . . . . . . . 6 5.2. Relationship to the Network Services MIB . . . . . . . . . 6
6. Accommodating SIP Extension Methods . . . . . . . . . . . . 9 5.3. IMPORTed MIB Modules and REFERENCE Clauses . . . . . . . . 10
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . 10 6. Accommodating SIP Extension Methods . . . . . . . . . . . . . 10
7.1 SIP Textual Conventions . . . . . . . . . . . . . . . . . 10 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.2 SIP Common MIB Module . . . . . . . . . . . . . . . . . . 13 7.1. SIP Textual Conventions . . . . . . . . . . . . . . . . . 11
7.3 SIP User Agent MIB Module . . . . . . . . . . . . . . . . 52 7.2. SIP Common MIB Module . . . . . . . . . . . . . . . . . . 14
7.4 SIP Server MIB Module (Proxy, Redirect and Registrar 7.3. SIP User Agent MIB Module . . . . . . . . . . . . . . . . 53
Servers) . . . . . . . . . . . . . . . . . . . . . . . . . 56 7.4. SIP Server MIB Module (Proxy, Redirect and Registrar
8. Changes from Previous Draft Revisions . . . . . . . . . . . 74 Servers) . . . . . . . . . . . . . . . . . . . . . . . . . 57
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . 86 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 76
9.1 Registration of Numeric Identifiers for SIP methods . . . 86 9. Security Considerations . . . . . . . . . . . . . . . . . . . 76
9.2 IANA-assigned OBJECT IDENTIFIER values for the SIP MIB 10. Contributor Acknowledgments . . . . . . . . . . . . . . . . . 78
modules . . . . . . . . . . . . . . . . . . . . . . . . . 88 11. Changes from Previous Draft Revisions . . . . . . . . . . . . 78
10. Security Considerations . . . . . . . . . . . . . . . . . . 88 12. Normative References . . . . . . . . . . . . . . . . . . . . . 90
11. Contributor Acknowledgments . . . . . . . . . . . . . . . . 90 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 90
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 90 Intellectual Property and Copyright Statements . . . . . . . . . . 91
12.1 Normative References . . . . . . . . . . . . . . . . . . 90
12.2 Informational References . . . . . . . . . . . . . . . . 91
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 92
Intellectual Property and Copyright Statements . . . . . . . 93
1. Conventions 1. Conventions
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 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Introduction 2. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
skipping to change at page 3, line 39 skipping to change at page 3, line 39
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a set Structure of Management Information (SMI). This memo specifies a set
of MIB modules that are compliant to the SMIv2, which is described in of MIB modules that are compliant to the SMIv2, which is described in
STD 58, comprised of RFC 2578 [RFC2578], RFC 2579 [RFC2579], and RFC STD 58, comprised of RFC 2578 [RFC2578], RFC 2579 [RFC2579], and RFC
2580 [RFC2580]. 2580 [RFC2580].
4. Overview 4. Overview
The Session Initiation Protocol (SIP) RFC 3261 [RFC3261] is an SIP [RFC3261] is an application-layer control (signaling) protocol
application-layer control (signaling) protocol for creating, for creating, modifying, and terminating sessions with one or more
modifying, and terminating sessions with one or more participants. participants. These sessions include Internet telephone calls,
These sessions include Internet telephone calls, multimedia multimedia distribution, and multimedia conferences.
distribution, and multimedia conferences. This MIB provides some
managed objects for SIP entities defined in RFC 3261 [RFC3261] - User
Agents, and Proxy, Redirect and Registrar servers: it is intended to
provide management of the basic SIP entities. It provides for
monitoring of status and protocol statistics, as well as for
configuration of SIP entities.
5. Structure of SIP MIB This MIB provides some managed objects for SIP entities defined in
RFC 3261 [RFC3261] - User Agents, and Proxy, Redirect and Registrar
servers: it is intended to provide management of the basic SIP
entities. It provides for monitoring of status and protocol
statistics, as well as for configuration of SIP entities.
This memo specifies four MIB modules. They are SIP-COMMON-MIB, 5. Structure of the SIP MIB
SIP-SERVER-MIB, SIP-UA-MIB and SIP-TC. SIP-COMMON-MIB contains
common objects used in all the SIP entities. SIP-SERVER-MIB contains Four MIB modules are specified: SIP-COMMON-MIB, SIP-SERVER-MIB, SIP-
objects specific to Proxy, Redirect and Registrar servers, and UA-MIB and SIP-TC. SIP-COMMON-MIB contains common MIB objects used
SIP-UA-MIB includes objects specific to User Agents. SIP-TC defines in all the SIP entities. SIP-SERVER-MIB contains objects specific to
the textual conventions used throughout MIB modules. The MIB Modules Proxy, Redirect and Registrar servers, and SIP-UA-MIB includes
contain following groups of objects: objects specific to User Agents. SIP-TC defines the textual
conventions used throughout MIB modules.
The MIB modules contain following groups of objects:
SIP-COMMON-MIB: Management objects common to all the SIP entities SIP-COMMON-MIB: Management objects common to all the SIP entities
o sipCommonMIBObjects o sipCommonMIBObjects
* sipCommonCfgBase: This object group defines configuration * sipCommonCfgBase: This object group defines configuration
objects common to all SIP entities including the SIP protocol objects common to all SIP entities including the SIP protocol
version, the type of SIP entity (UA, proxy, redirect, registrar version, the type of SIP entity (UA, proxy, redirect, registrar
server), the operational and administrative status, the SIP server), the operational and administrative status, the SIP
organization name, the maximum number of SIP transactions an organization name, the maximum number of SIP transactions an
entity can manage, etc. entity can manage, etc.
* sipCommonCfgTimer: This object group defines timer * sipCommonCfgTimer: This object group defines timer
skipping to change at page 5, line 49 skipping to change at page 6, line 6
proxy or redirect calls. proxy or redirect calls.
To conform with this specification, an SNMP agent MUST implement the To conform with this specification, an SNMP agent MUST implement the
SIP-TC MIB module, plus the SIP-COMMON-MIB module and one of the SIP SIP-TC MIB module, plus the SIP-COMMON-MIB module and one of the SIP
entity-type- specific MIB modules (SIP-SERVER-MIB or SIP-UA-MIB) as entity-type- specific MIB modules (SIP-SERVER-MIB or SIP-UA-MIB) as
applicable for each instance of a SIP entity being managed. If a applicable for each instance of a SIP entity being managed. If a
device has more than one SIP entity or multiple instances of the same device has more than one SIP entity or multiple instances of the same
entity type, it MUST implement multiple SIP modules. Section 4.2 entity type, it MUST implement multiple SIP modules. Section 4.2
describes handling of multiple instances in detail. describes handling of multiple instances in detail.
5.1 Textual Conventions 5.1. Textual Conventions
The data types SipTransportProtocol, SipEntityRole, The data types SipTransportProtocol, SipEntityRole,
SipOptionTagHeaders, and SipMethodIdentifier are used as Textual SipOptionTagHeaders, and SipMethodName are defined in the SIP-TC MIB
Conventions in this document. They are defined in the SIP-TC MIB module and used as Textual Conventions in this document.
module.
5.2 Relationship to the Network Services MIB 5.2. Relationship to the Network Services MIB
In the design of the SIP MIB, the authors considered the following In the design of the SIP MIB, the authors considered the following
requirement: the SIP MIB must allow a single system with a single requirement: the SIP MIB must allow a single system with a single
SNMP agent to support multiple instances of various SIP MIB modules. SNMP agent to support multiple instances of various SIP MIB modules.
This requirement is met by using the framework provided by the This requirement is met by using the framework provided by the
Network Services Monitoring MIB, NETWORK-SERVICES-MIB, RFC 2788 Network Services Monitoring MIB, NETWORK-SERVICES-MIB, RFC 2788
[RFC2788]. [RFC2788].
A device implementing the SIP MIB MUST support the A device implementing the SIP MIB MUST support the NETWORK-SERVICES-
NETWORK-SERVICES-MIB and, at a minimum, it MUST support the index and MIB and, at a minimum, it MUST support the index and name objects
name objects (applIndex and applName) in the application table (applIndex and applName) in the application table (applTable). In
(applTable). In order to allow each instance of a SIP entity to be order to allow each instance of a SIP entity to be managed as a
managed as a separate network service application, a naming separate network service application, a naming convention SHOULD be
convention SHOULD be used to make the application name unique. For used to make the application name unique. For example, if a system
example, if a system is running 2 SIP UAs that need to be managed as is running 2 SIP UAs that need to be managed as 2 separate SIP
2 separate SIP entities, by convention, the application names used in entities, by convention, the application names used in the Network
the Network Services Monitoring MIB application table should be Services Monitoring MIB application table should be "sip_ua1" and
"sip_ua1" and "sip_ua2". This convention allows each instance to "sip_ua2". This convention allows each instance to have its own row
have its own row in the application table (applTable). in the application table (applTable).
It is therefore RECOMMENDED to adopt the following application name It is therefore RECOMMENDED to adopt the following application name
conventions: conventions:
o for a SIP Proxy entity, the applName value SHOULD be equal to a o for a SIP Proxy entity, the applName value SHOULD be equal to a
character string starting with "sip_proxy" followed by a unique character string starting with "sip_proxy" followed by a unique
application instance identifier, for example, "sip_proxy1", application instance identifier, for example, "sip_proxy1",
"sip_proxy17" "sip_proxy17"
o for a SIP Registrar entity, the applName value SHOULD be equal to o for a SIP Registrar entity, the applName value SHOULD be equal to
a character string starting with "sip_registrar" followed by a a character string starting with "sip_registrar" followed by a
unique application instance identifier, for example, unique application instance identifier, for example,
skipping to change at page 8, line 41 skipping to change at page 8, line 44
+-----------+--------------+-------------------+-----+ +-----------+--------------+-------------------+-----+
Example 2: Example 2:
This example illustrates how to represent a system acting as both This example illustrates how to represent a system acting as both
Proxy and Registrar server, where the two entities share a single Proxy and Registrar server, where the two entities share a single
instance of SIP-COMMON-MIB. instance of SIP-COMMON-MIB.
The NETWORK-SERVICES-MIB applTable might be populated as follows: The NETWORK-SERVICES-MIB applTable might be populated as follows:
+-----------+------------------------+--------------------------------+ +-----------+------------------------+------------------------------+
| applIndex | applName | applDescription | | applIndex | applName | applDescription |
+-----------+------------------------+--------------------------------+ +-----------+------------------------+------------------------------+
| 1 | "sip_proxy_registrar1" | "ACME SIP Proxy and Registrar" | | 1 | "sip_proxy_registrar1" | "ACME SIP Proxy and |
+-----------+------------------------+--------------------------------+ | | | Registrar" |
+-----------+------------------------+------------------------------+
The SIP-COMMON-MIB sipCommonCfgTable would have only one row to cover The SIP-COMMON-MIB sipCommonCfgTable would have only one row to cover
both the proxy and the registrar. both the proxy and the registrar.
SIP-COMMON-MIB sipCommonCfgTable might be populated as: SIP-COMMON-MIB sipCommonCfgTable might be populated as:
+-----------+--------------------+----------------------+ +-----------+--------------------+----------------------+
| applIndex | sipProtocolVersion | sipServiceOperStatus | | applIndex | sipProtocolVersion | sipServiceOperStatus |
+-----------+--------------------+----------------------+ +-----------+--------------------+----------------------+
| 1 | "SIP/2.0" | up(1) | | 1 | "SIP/2.0" | up(1) |
skipping to change at page 9, line 48 skipping to change at page 10, line 5
| quiescing | --> | quiescing | | quiescing | --> | quiescing |
| testing | --> | up | | testing | --> | up |
| unknown | --> | --indeterminate-- | | unknown | --> | --indeterminate-- |
+----------------------+-----------------------+-------------------+ +----------------------+-----------------------+-------------------+
If the sipOperStatus is 'unknown' there is no corresponding value of If the sipOperStatus is 'unknown' there is no corresponding value of
applOperStatus. Therefore, the last known value of applOperStatus applOperStatus. Therefore, the last known value of applOperStatus
SHOULD be maintained until the sipOperStatus transitions to a value SHOULD be maintained until the sipOperStatus transitions to a value
that can be mapped appropriately. that can be mapped appropriately.
5.3. IMPORTed MIB Modules and REFERENCE Clauses
The SIP MIB modules defined in this document IMPORT definitions
normatively from the following MIB modules, beyond [RFC2578],
[RFC2579] and [RFC2580]: INET-ADDRESS-MIB [RFC4001], NETWORK-
SERVICES-MIB [RFC2788], SNMP-FRAMEWORK-MIB [RFC3411].
This MIB module also includes REFERENCE clauses that normatively
refer to SIP [RFC3261], and INET-ADDRESS-MIB [RFC4001].
6. Accommodating SIP Extension Methods 6. Accommodating SIP Extension Methods
The core set of SIP methods is defined in RFC 3261 [RFC3261]. Other The core set of SIP methods is defined in RFC 3261 [RFC3261]. Other
IETF RFCs define additional methods. In the future, additional IETF RFCs define additional methods. In the future, additional
methods may be defined. In order to avoid having to update the methods may be defined. In order to avoid having to update the SIP-
SIP-COMMON-MIB module to accommodate these extension methods, we use COMMON-MIB module to accommodate these extension methods, we use a
a method identifier (SipMethodIdentifier textual-convention) to method identifier name (SipMethodName textual-convention) to
represent all SIP methods registered with IANA. See IANA represent all SIP methods registered with IANA. See IANA
Consideration section. Consideration section.
For example, the sipMethodSupportedTable is the main table for For example, the sipMethodSupportedTable is the main table for
listing all of the SIP methods supported by a system, including the listing all of the SIP methods supported by a system, including the
SIP methods defined in RFC 3261 [RFC3261] and other SIP methods SIP methods defined in RFC 3261 [RFC3261] and other SIP methods
registered with IANA. The table is informational in nature and registered with IANA. The table is informational in nature and
populated by the system. Entries cannot be added or deleted by a populated by the system. Entries cannot be added or deleted by a
SNMP manager. SNMP manager.
The SIP specification RFC 3261 [RFC3261] section 27.4 establishes the
sub-registries for SIP Methods and Response Codes under
http://www.iana.org/assignments/sip-parameters. This document uses
the existing sub-registry for the names of registered SIP method.
For example, in the sipSupportedMethodTable of SIP-COMMON-MIB, the
sipMethodName values can be represented as as follows:
+------------------------+
| sipMethodSupportedName |
+------------------------+
| "ACK" |
| "BYE" |
| "CANCEL" |
| "INVITE" |
| "OPTIONS" |
+------------------------+
7. Definitions 7. Definitions
7.1 SIP Textual Conventions 7.1. SIP Textual Conventions
SIP-TC DEFINITIONS ::= BEGIN SIP-TC DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
sipTC MODULE-IDENTITY sipTC MODULE-IDENTITY
LAST-UPDATED "200501281700Z" LAST-UPDATED "200603021700Z"
ORGANIZATION "IETF Session Initiation Protocol Working Group" ORGANIZATION "IETF Session Initiation Protocol Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
skipping to change at page 11, line 8 skipping to change at page 11, line 43
Co-editor Joon Maeng Co-editor Joon Maeng
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 858 Coal Creek Circle postal: 858 Coal Creek Circle
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 3708 phone: +1 303 661 9100
Co-editor Dave Walker Co-editor Dave Walker
email: drwalker@rogers.com" email: drwalker@rogers.com"
DESCRIPTION DESCRIPTION
"Session Initiation Protocol (SIP) MIB Textual "Session Initiation Protocol (SIP) MIB Textual
Conventions module used by other SIP-related Conventions module used by other SIP-related
MIB Modules. MIB Modules.
Copyright (C) The Internet Society (2005). This version Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
REVISION "200501281700Z" REVISION "200603021700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-TC module. "Initial version of the IETF SIP-TC module.
This version published as part of RFC XXXX." This version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX1 } ::= { mib-2 XXX1 }
-- RFC Ed: replace XXX1 with actual IANA assigned number for this -- RFC Ed: replace XXX1 with actual IANA assigned number for this
-- sipTC mib module and remove this note -- sipTC mib module and remove this note
-- --
-- Textual Conventions -- Textual Conventions
skipping to change at page 12, line 43 skipping to change at page 13, line 29
(Section 20.37) and Unsupported (Section 20.40) (Section 20.37) and Unsupported (Section 20.40)
header fields." header fields."
SYNTAX BITS { SYNTAX BITS {
require(0), -- Require header require(0), -- Require header
proxyRequire(1), -- Proxy-Require header proxyRequire(1), -- Proxy-Require header
supported(2), -- Supported header supported(2), -- Supported header
unsupported(3) -- Unsupported header unsupported(3) -- Unsupported header
} }
-- REFERENCE "RFC 3261, Section 19.2" -- REFERENCE "RFC 3261, Section 19.2"
SipMethodIdentifier ::= TEXTUAL-CONVENTION SipMethodName ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is an IETF Assigned Numbers Authority (IANA) "This textual convention is a string that uniquely
assigned number that uniquely identifies a SIP identifies a SIP method. The scope of uniqueness
method. The scope of uniqueness is the context is the context of all defined SIP methods.
of all defined SIP methods.
Experimental support of extension methods is Experimental support of extension methods is
acceptable and expected. Extention methods are acceptable and expected. Extention methods are
those defined in Internet-Draft documents but those defined in Internet-Draft documents but
not yet allocated an official number by IANA. not yet allocated an official sanctioned by IANA.
To support experimental extension methods, any To support experimental extension methods, any
object using this textual convention as syntax object using this textual convention as syntax
MAY return/accept a method identifier value other MAY return/accept a method identifier value other
than those defined by IANA. That system MUST than those sanctioned by IANA. That system MUST
ensure no collisions with officially assigned ensure no collisions with officially assigned
method identifier values and MUST provide a method names."
identifier to method name mapping via a mechanism SYNTAX OCTET STRING (SIZE (1..128))
like sipMethodSupportedTable."
SYNTAX Unsigned32 (1..4294967295)
END END
7.2 SIP Common MIB Module 7.2. SIP Common MIB Module
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,
Gauge32, Gauge32,
TimeTicks, TimeTicks,
Unsigned32, Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI -- RFC 2578
RowStatus, RowStatus,
TruthValue TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB -- RFC 3411
SipTransportProtocol, SipTransportProtocol,
SipMethodIdentifier, SipMethodName,
SipEntityRole, SipEntityRole,
SipOptionTagHeaders SipOptionTagHeaders
FROM SIP-TC FROM SIP-TC
applIndex applIndex
FROM NETWORK-SERVICES-MIB FROM NETWORK-SERVICES-MIB -- RFC 2788
InetPortNumber InetPortNumber
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB; -- RFC 4001
sipCommonMIB MODULE-IDENTITY sipCommonMIB MODULE-IDENTITY
LAST-UPDATED "200501281700Z" LAST-UPDATED "200603031700Z"
ORGANIZATION "IETF Session Initiation Protocol Working Group" ORGANIZATION "IETF Session Initiation Protocol Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
skipping to change at page 14, line 38 skipping to change at page 15, line 19
Co-editor Joon Maeng Co-editor Joon Maeng
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 858 Coal Creek Circle postal: 858 Coal Creek Circle
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 3708 phone: +1 303 661 9100
Co-editor Dave Walker Co-editor Dave Walker
email: drwalker@rogers.com" email: drwalker@rogers.com"
DESCRIPTION DESCRIPTION
"Session Initiation Protocol (SIP) Common MIB module. "Session Initiation Protocol (SIP) Common MIB module.
This module defines objects which MAY be common to all This module defines objects which MAY be common to all
SIP entities. 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
skipping to change at page 16, line 6 skipping to change at page 16, line 36
Redirect Server: A redirect server is a user agent Redirect Server: A redirect server is a user agent
server that generates 3xx responses to requests it server that generates 3xx responses to requests it
receives, directing the client to contact an alternate receives, directing the client to contact an alternate
set of URIs. set of URIs.
Registrar: A registrar is a server that accepts Registrar: A registrar is a server that accepts
REGISTER requests and places the information it REGISTER requests and places the information it
receives in those requests into the location service receives in those requests into the location service
for the domain it handles. for the domain it handles.
Copyright (C) The Internet Society (2005). This version Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed: replace XXXX with actual RFC number and -- RFC Ed: replace XXXX with actual RFC number and
-- remove this note -- remove this note
REVISION "200501281700Z" REVISION "200603031700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-COMMON-MIB module. "Initial version of the IETF SIP-COMMON-MIB module.
This version published as part of RFC XXXX." This version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX2 } ::= { mib-2 XXX2 }
-- RFC Ed: replace XXX2 with actual IANA assigned number and remove this note -- RFC Ed: replace XXX2 with actual IANA assigned number and
-- remove this note
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 } sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 }
sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 } sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
sipCommonMIBConform OBJECT IDENTIFIER ::= { sipCommonMIB 2 } sipCommonMIBConform OBJECT IDENTIFIER ::= { sipCommonMIB 2 }
-- --
-- This MIB contains objects that are common to all SIP entities. -- This MIB contains objects that are common to all SIP entities.
-- --
skipping to change at page 19, line 4 skipping to change at page 19, line 34
issuing) SIP requests and responses. issuing) SIP requests and responses.
down : The application is currently unable to down : The application is currently unable to
process SIP messages. process SIP messages.
congested : The application is operational but no congested : The application is operational but no
additional inbound transactions can be additional inbound transactions can be
accommodated at the moment. accommodated at the moment.
restarting : The application is currently unavailable restarting : The application is currently unavailable
but it is in the process of restarting and but it is in the process of restarting and
will, presumably, soon be able to process will, presumably, soon be able to process
SIP messages. SIP messages.
quiescing : The application is currently operational quiescing : The application is currently operational
but has been administratively put into but has been administratively put into
quiesce mode. Additional inbound quiesce mode. Additional inbound
transactions MAY be rejected. transactions MAY be rejected.
testing : The application is currently in test mode testing : The application is currently in test mode
and MAY not be able to process SIP messages. and MAY not be able to process SIP
messages.
The operational status values defined for this object are The operational status values defined for this object
not based on any specific information contained in the SIP are not based on any specific information contained in
standard." the SIP standard."
::= { sipCommonCfgEntry 2 } ::= { sipCommonCfgEntry 2 }
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
started. If started prior to the last re-initialization of last started. If started prior to the last
the local network management subsystem, then this object re-initialization of the local network management
contains a zero value." subsystem, then this object contains a zero value."
::= { sipCommonCfgEntry 3 } ::= { sipCommonCfgEntry 3 }
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
its current operational state. If the current state was entered its current operational state. If the current
entered prior to the last re-initialization of the local state was entered prior to the last re-initialization of
network management subsystem, then this object contains a the local network management subsystem, then this object
zero value." contains a zero value."
::= { sipCommonCfgEntry 4 } ::= { sipCommonCfgEntry 4 }
sipOrganization OBJECT-TYPE sipOrganization OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the organization name which the SIP "This object contains the organization name which the SIP
entity inserts into Organization headers of SIP messages entity inserts into Organization headers of SIP messages
processed by this system. If the string is empty, no processed by this system. If the string is empty, no
skipping to change at page 21, line 19 skipping to change at page 21, line 49
::= { sipCommonCfgEntry 8 } ::= { sipCommonCfgEntry 8 }
-- --
-- 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
in this system is allowed to use. These ports can be entity in this system is allowed to use. These ports
advertised using the Contact header in a REGISTER request can be advertised using the Contact header in a REGISTER
or response." request or response."
::= { 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 Each row represents those objects for a particular SIP
skipping to change at page 21, line 51 skipping to change at page 22, line 34
SEQUENCE { SEQUENCE {
sipPort InetPortNumber, sipPort InetPortNumber,
sipTransportRcv SipTransportProtocol sipTransportRcv SipTransportProtocol
} }
sipPort OBJECT-TYPE sipPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
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
the SIP application." by the SIP application."
::= { sipPortEntry 1 } ::= { sipPortEntry 1 }
sipTransportRcv OBJECT-TYPE sipTransportRcv OBJECT-TYPE
SYNTAX SipTransportProtocol SYNTAX SipTransportProtocol
MAX-ACCESS read-only MAX-ACCESS read-only
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
protocol. If a bit has value 1, then that transport protocol transport protocol. If a bit has value 1, then that
is currently being used. If a bit has value 0, then that transport protocol is currently being used. If a bit
transport protocol is currently not being used." has value 0, then that transport protocol is currently
not being used."
::= { sipPortEntry 2 } ::= { sipPortEntry 2 }
-- --
-- Support for SIP option tags (SIP extensions). -- Support for SIP option tags (SIP extensions).
-- SIP extensions MAY be supported or required by SIP entities. -- SIP extensions MAY be supported or required by SIP entities.
-- --
sipOptionTagTable OBJECT-TYPE sipOptionTagTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipOptionTagEntry SYNTAX SEQUENCE OF SipOptionTagEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 22, line 34 skipping to change at page 23, line 17
-- --
sipOptionTagTable OBJECT-TYPE sipOptionTagTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipOptionTagEntry SYNTAX SEQUENCE OF SipOptionTagEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of the SIP option tags "This table contains a list of the SIP option tags
(SIP extensions) that either required, supported, or (SIP extensions) that either required, supported, or
unsupported by the SIP entity. unsupported by the SIP entity.
These option tags are used in the Require, Proxy-Require, These option tags are used in the Require,
Supported and Unsupported header fields. Proxy-Require, Supported and Unsupported header fields.
Example: if a user agent client supports and requires the Example: if a user agent client supports and requires
server to support reliability of provisional the server to support reliability of provisional
responses, this table contains a row with the responses, this table contains a row with the string
string '100rel' in sipOptionTag and the value '100rel' in sipOptionTag and the value 0xA0 in
0xA0 in sipOptionTagHeaderField. sipOptionTagHeaderField.
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
Require to a Proxy Server), the server returns a 420 Bad Proxy-Require to a Proxy Server), the server returns a
Extension listing the feature in an Unsupported header. 420 Bad 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
is static (i.e. will not change over time)." entity is static (i.e. will not change over time)."
REFERENCE REFERENCE
"RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40" "RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40"
::= { sipCommonCfgBase 3 } ::= { sipCommonCfgBase 3 }
sipOptionTagEntry OBJECT-TYPE sipOptionTagEntry OBJECT-TYPE
SYNTAX SipOptionTagEntry SYNTAX SipOptionTagEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular SIP option tag (extension) supported or "A particular SIP option tag (extension) supported or
unsupported by the SIP entity, and which may be supported unsupported by the SIP entity, and which may be
or required by a peer. supported or required by a peer.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and uniquely identify these instances of SIP entities and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788). NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot." and their value SHOULD be kept at reboot."
INDEX { applIndex, sipOptionTagIndex } INDEX { applIndex, sipOptionTagIndex }
::= { sipOptionTagTable 1 } ::= { sipOptionTagTable 1 }
skipping to change at page 23, line 35 skipping to change at page 24, line 20
sipOptionTagIndex Unsigned32, sipOptionTagIndex Unsigned32,
sipOptionTag SnmpAdminString, sipOptionTag SnmpAdminString,
sipOptionTagHeaderField SipOptionTagHeaders sipOptionTagHeaderField SipOptionTagHeaders
} }
sipOptionTagIndex OBJECT-TYPE sipOptionTagIndex 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
table." the table."
::= { sipOptionTagEntry 1 } ::= { sipOptionTagEntry 1 }
sipOptionTag OBJECT-TYPE sipOptionTag OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the SIP option tag. "This object indicates the SIP option tag.
The option tag names are registered with The option tag names are registered with
IANA and available at http://www.iana.org." IANA and available at http://www.iana.org."
skipping to change at page 25, line 12 skipping to change at page 25, line 44
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788). NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot." and their value SHOULD be kept at reboot."
INDEX { applIndex, sipMethodSupportedIndex } INDEX { applIndex, sipMethodSupportedIndex }
::= { sipMethodSupportedTable 1 } ::= { sipMethodSupportedTable 1 }
SipMethodSupportedEntry ::= SipMethodSupportedEntry ::=
SEQUENCE { SEQUENCE {
sipMethodSupportedIndex SipMethodIdentifier, sipMethodSupportedIndex Unsigned32,
sipMethodName SnmpAdminString sipMethodName SnmpAdminString
} }
sipMethodSupportedIndex OBJECT-TYPE sipMethodSupportedIndex OBJECT-TYPE
SYNTAX SipMethodIdentifier SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row "This object uniquely identifies a conceptual row
in the table and reflects an assigned number used in the table and reflects an assigned number used
to identifier a specific SIP method. to identifier a specific SIP method.
This identifier is suitable for referenceing the This identifier is suitable for referencing the
associated method throughout this and other MIBs associated method throughout this and other MIBs
supported by this managed system." supported by this managed system."
::= { sipMethodSupportedEntry 1 } ::= { sipMethodSupportedEntry 1 }
sipMethodName OBJECT-TYPE sipMethodName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the supported method's name. "This object reflects the supported method's name.
skipping to change at page 25, line 47 skipping to change at page 26, line 31
::= { sipMethodSupportedEntry 2 } ::= { sipMethodSupportedEntry 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
to SIP user agent and SIP stateful Proxy Server entities." applicable to SIP user agent and SIP stateful Proxy
Server entities."
::= { 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 Each row represents those objects for a particular SIP
skipping to change at page 26, line 44 skipping to change at page 27, line 31
sipCfgTimerT2 Unsigned32, sipCfgTimerT2 Unsigned32,
sipCfgTimerT4 Unsigned32 sipCfgTimerT4 Unsigned32
} }
sipCfgTimerA OBJECT-TYPE sipCfgTimerA OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the initial value for the retransmit "This object reflects the initial value for the
timer for the INVITE method. The retransmit timer doubles retransmit timer for the INVITE method. The retransmit
after each retransmission, ensuring an exponential backoff timer doubles after each retransmission, ensuring an
in network traffic. This object represents the initial time exponential backoff in network traffic. This object
a SIP entity will wait to receive a provisional response to represents the initial time a SIP entity will wait to
an INVITE before resending the INVITE request." receive a provisional response to an INVITE before
resending the INVITE request."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.1.2" "RFC 3261, Section 17.1.1.2"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 1 } ::= { sipCommonCfgTimerEntry 1 }
sipCfgTimerB OBJECT-TYPE sipCfgTimerB OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 27, line 29 skipping to change at page 28, line 17
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 2 } ::= { sipCommonCfgTimerEntry 2 }
sipCfgTimerC OBJECT-TYPE sipCfgTimerC OBJECT-TYPE
SYNTAX Unsigned32 (180000..300000) SYNTAX Unsigned32 (180000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP Proxy Server "This object reflects the maximum time a SIP Proxy Server
will wait to receive a provisional response to an INVITE. will wait to receive a provisional response to an
INVITE.
The Timer C MUST be set for each client transaction when The Timer C MUST be set for each client transaction when
an INVITE request is proxied." an INVITE request is proxied."
REFERENCE REFERENCE
"RFC 3261, Section 16.6" "RFC 3261, Section 16.6"
DEFVAL { 180000 } DEFVAL { 180000 }
::= { sipCommonCfgTimerEntry 3 } ::= { sipCommonCfgTimerEntry 3 }
sipCfgTimerD OBJECT-TYPE sipCfgTimerD OBJECT-TYPE
SYNTAX Unsigned32 (0..300000) SYNTAX Unsigned32 (0..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the amount of time that the server "This object reflects the amount of time that the server
transaction can remain in the 'Completed' state when transaction can remain in the 'Completed' state when
unreliable transports are used. The default value MUST be unreliable transports are used. The default value MUST
greater than 32000 for UDP transport and its value MUST be greater than 32000 for UDP transport and its value
be 0 for TCP/SCTP transport." MUST be 0 for TCP/SCTP transport."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.1.2" "RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 4 } ::= { sipCommonCfgTimerEntry 4 }
sipCfgTimerE OBJECT-TYPE sipCfgTimerE OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the initial value for the retransmit "This object reflects the initial value for the retransmit
timer for a non-INVITE method while in 'Trying State'. timer for a non-INVITE method while in 'Trying State'.
The retransmit timer doubles after each retransmission The retransmit timer doubles after each retransmission
until it reaches T2 to ensure an exponential backoff until it reaches T2 to ensure an exponential backoff
skipping to change at page 28, line 14 skipping to change at page 29, line 4
sipCfgTimerE OBJECT-TYPE sipCfgTimerE OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the initial value for the retransmit "This object reflects the initial value for the retransmit
timer for a non-INVITE method while in 'Trying State'. timer for a non-INVITE method while in 'Trying State'.
The retransmit timer doubles after each retransmission The retransmit timer doubles after each retransmission
until it reaches T2 to ensure an exponential backoff until it reaches T2 to ensure an exponential backoff
in network traffic. This object represents the initial time in network traffic. This object represents the initial
a SIP entity will wait to receive a provisional response to time a SIP entity will wait to receive a provisional
the request before resending the non-INVITE request." response to the request before resending the non-INVITE
request."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.2.2" "RFC 3261, Section 17.1.2.2"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 5 } ::= { sipCommonCfgTimerEntry 5 }
sipCfgTimerF OBJECT-TYPE sipCfgTimerF OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 28, line 43 skipping to change at page 29, line 34
"RFC 3261, Section 17.1.2.2" "RFC 3261, Section 17.1.2.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 6 } ::= { sipCommonCfgTimerEntry 6 }
sipCfgTimerG OBJECT-TYPE sipCfgTimerG OBJECT-TYPE
SYNTAX Unsigned32 (0..1000) SYNTAX Unsigned32 (0..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the initial value for the retransmit "This object reflects the initial value for the
timer for final responses to INVITE requests. retransmit timer for final responses to INVITE requests.
If timer G fires, the response is passed to the transport If timer G fires, the response is passed to the
layer once more for retransmission, and timer G is set transport layer once more for retransmission, and
to fire in MIN(2*T1, T2) seconds. From then on, when timer G is set to fire in MIN(2*T1, T2) seconds. From
timer G fires, the response is passed to the transport then on, when timer G fires, the response is passed to
again for transmission, and timer G is reset with a value the transport again for transmission, and timer G is
that doubles, unless that value exceeds T2, in which case reset with a value that doubles, unless that value
it is reset with the value of T2. exceeds T2, in which case it is reset with the value of
T2. The default value MUST be T1 for UDP transport and
The default value MUST be T1 for UDP transport and its value its value MUST be 0 for reliable transport like
MUST be 0 for reliable transport like TCP/SCTP." TCP/SCTP."
REFERENCE REFERENCE
"RFC 3261, Section 17.2.1" "RFC 3261, Section 17.2.1"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 7 } ::= { sipCommonCfgTimerEntry 7 }
sipCfgTimerH OBJECT-TYPE sipCfgTimerH OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 29, line 36 skipping to change at page 30, line 27
sipCfgTimerI OBJECT-TYPE sipCfgTimerI OBJECT-TYPE
SYNTAX Unsigned32 (0..10000) SYNTAX Unsigned32 (0..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP entity will "This object reflects the maximum time a SIP entity will
wait to receive additional ACK message retransmissions. wait to receive additional ACK message retransmissions.
The timer is started upon entering the 'Confirmed' state. The timer is started upon entering the 'Confirmed' state.
The default value MUST be T4 for UDP transport and its value The default value MUST be T4 for UDP transport and its
MUST be 0 for reliable transport like TCP/SCTP." value MUST be 0 for reliable transport like TCP/SCTP."
REFERENCE REFERENCE
"RFC 3261, Section 17.2.1" "RFC 3261, Section 17.2.1"
DEFVAL { 5000 } DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 9 } ::= { sipCommonCfgTimerEntry 9 }
sipCfgTimerJ OBJECT-TYPE sipCfgTimerJ OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP server will "This object reflects the maximum time a SIP server will
wait to receive retransmissions of non-INVITE request. wait to receive retransmissions of non-INVITE request.
The timer is started upon entering the 'Completed' state The timer is started upon entering the 'Completed' state
for non-INVITE transactions. When timer J fires, the server for non-INVITE transactions. When timer J fires, the
MUST transition to the 'Terminated' state." server MUST transition to the 'Terminated' state."
REFERENCE "RFC 3261, Section 17.2.2" REFERENCE "RFC 3261, Section 17.2.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 10 } ::= { sipCommonCfgTimerEntry 10 }
sipCfgTimerK OBJECT-TYPE sipCfgTimerK OBJECT-TYPE
SYNTAX Unsigned32 (0..10000) SYNTAX Unsigned32 (0..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP client will "This object reflects the maximum time a SIP client will
wait to receive retransmissions of responses to non-INVITE wait to receive retransmissions of responses to
requests. non-INVITE requests.
The timer is started upon entering the 'Completed' state The timer is started upon entering the 'Completed' state
for non-INVITE transactions. When timer K fires, the server for non-INVITE transactions. When timer K fires, the
MUST transition to the 'Terminated' state. server MUST transition to the 'Terminated' state.
The default value MUST be T4 for UDP transport and its value The default value MUST be T4 for UDP transport and its
MUST be 0 for reliable transport like TCP/SCTP." value MUST be 0 for reliable transport like TCP/SCTP."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.2.2" "RFC 3261, Section 17.1.2.2"
DEFVAL { 5000 } DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 11 } ::= { sipCommonCfgTimerEntry 11 }
sipCfgTimerT1 OBJECT-TYPE sipCfgTimerT1 OBJECT-TYPE
SYNTAX Unsigned32 (200..10000) SYNTAX Unsigned32 (200..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 33, line 23 skipping to change at page 34, line 14
"This object contains the total number of SIP response "This object contains the total number of SIP response
messages sent (originated and relayed) by the SIP entity messages sent (originated and relayed) by the SIP entity
including retransmissions." including retransmissions."
::= { sipSummaryStatsEntry 4 } ::= { sipSummaryStatsEntry 4 }
sipSummaryTotalTransactions OBJECT-TYPE sipSummaryTotalTransactions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of transactions "This object contains a count of the number of
that are in progress and transactions that have reached the transactions that are in progress and transactions that
terminated state. It is not applicable to stateless have reached the terminated state. It is not applicable
SIP Proxy Servers. to stateless SIP Proxy Servers.
A SIP transaction occurs between a client and a server and A SIP transaction occurs between a client and a server
comprises all messages from the first request sent from and comprises all messages from the first request sent
the client to the server up to a final (non-1xx) response from the client to the server up to a final (non-1xx)
sent from the server to the client. response sent from the server to the client.
If the request is INVITE and the final response is a non-2xx, If the request is INVITE and the final response is a
the transaction also include an ACK to the response. The ACK non-2xx, the transaction also include an ACK to the
for a 2xx response to an INVITE request is a separate response. The ACK for a 2xx response to an INVITE
transaction. request is a separate transaction.
The branch ID parameter in the Via header field values The branch ID parameter in the Via header field values
serves as a transaction identifier. serves as a transaction identifier.
A transaction is identified by the CSeq sequence number A transaction is identified by the CSeq sequence number
within a single call leg. The ACK request has the same within a single call leg. The ACK request has the same
CSeq number as the corresponding INVITE request, but CSeq number as the corresponding INVITE request, but
comprises a transaction of its own. comprises a transaction of its own.
In the case of a forked request, each branch counts as a In the case of a forked request, each branch counts as a
skipping to change at page 34, line 37 skipping to change at page 35, line 28
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and uniquely identify these instances of SIP entities and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipStatsMethod } INDEX { applIndex, sipStatsMethod }
::= { sipMethodStatsTable 1 } ::= { sipMethodStatsTable 1 }
SipMethodStatsEntry ::= SipMethodStatsEntry ::=
SEQUENCE { SEQUENCE {
sipStatsMethod SipMethodIdentifier, sipStatsMethod SipMethodName,
sipStatsOutbounds Counter32, sipStatsOutbounds Counter32,
sipStatsInbounds Counter32 sipStatsInbounds Counter32
} }
sipStatsMethod OBJECT-TYPE sipStatsMethod OBJECT-TYPE
SYNTAX SipMethodIdentifier SYNTAX SipMethodName
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies the SIP method "This object uniquely identifies the SIP method
related to the objects in a particular row." related to the objects in a particular row."
::= { sipMethodStatsEntry 1 } ::= { sipMethodStatsEntry 1 }
sipStatsOutbounds OBJECT-TYPE sipStatsOutbounds 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 "This object reflects the total number of requests
sent by the SIP entity, excluding retransmissions. sent by the SIP entity, excluding retransmissions.
Retransmissions are counted separately and are not Retransmissions are counted separately and are not
reflected in this counter." reflected in this counter."
REFERENCE REFERENCE
skipping to change at page 36, line 13 skipping to change at page 37, line 4
"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 Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and uniquely identify these instances of SIP entities and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipStatusCodeMethod, sipStatusCodeValue } INDEX { applIndex, sipStatusCodeMethod, sipStatusCodeValue }
::= { sipStatusCodesTable 1 } ::= { sipStatusCodesTable 1 }
SipStatusCodesEntry ::= SipStatusCodesEntry ::=
SEQUENCE { SEQUENCE {
sipStatusCodeMethod SipMethodIdentifier, sipStatusCodeMethod SipMethodName,
sipStatusCodeValue Unsigned32, sipStatusCodeValue Unsigned32,
sipStatusCodeIns Counter32, sipStatusCodeIns Counter32,
sipStatusCodeOuts Counter32, sipStatusCodeOuts Counter32,
sipStatusCodeRowStatus RowStatus sipStatusCodeRowStatus RowStatus
} }
sipStatusCodeMethod OBJECT-TYPE sipStatusCodeMethod OBJECT-TYPE
SYNTAX SipMethodIdentifier SYNTAX SipMethodName
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row "This object uniquely identifies a conceptual row
in the table and reflects an assigned number used in the table and reflects an assigned number used
to identifier a specific SIP method." to identifier a specific SIP method."
::= { sipStatusCodesEntry 1 } ::= { sipStatusCodesEntry 1 }
sipStatusCodeValue OBJECT-TYPE sipStatusCodeValue OBJECT-TYPE
SYNTAX Unsigned32 (100..999) SYNTAX Unsigned32 (100..999)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a SIP status code value that the SIP "This object contains a SIP status code value that the
entity has been requested to monitor. All of the other SIP entity has been requested to monitor. All of the
information in the row is related to this value." other information in the row is related to this value."
::= { sipStatusCodesEntry 2 } ::= { sipStatusCodesEntry 2 }
sipStatusCodeIns OBJECT-TYPE sipStatusCodeIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of response messages "This object reflects the total number of response
received by the SIP entity with the status code value messages received by the SIP entity with the status code
contained in the sipStatusCodeValue column." value contained in the sipStatusCodeValue column."
::= { sipStatusCodesEntry 3 } ::= { sipStatusCodesEntry 3 }
sipStatusCodeOuts OBJECT-TYPE sipStatusCodeOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of response messages "This object reflects the total number of response
sent by the SIP entity with the status code value messages sent by the SIP entity with the status code
contained in the sipStatusCodeValue column." value contained in the sipStatusCodeValue column."
::= { sipStatusCodesEntry 4 } ::= { sipStatusCodesEntry 4 }
sipStatusCodeRowStatus OBJECT-TYPE sipStatusCodeRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row augmentation in sipStatusCodeNotifTable "The row augmentation in sipStatusCodeNotifTable
will be governed by the value of this RowStatus. will be governed by the value of this RowStatus.
This object is REQUIRED to create or delete rows This object is REQUIRED to create or delete rows
by a manager. by a manager.
skipping to change at page 38, line 34 skipping to change at page 39, line 24
} }
sipStatusCodeNotifSend OBJECT-TYPE sipStatusCodeNotifSend OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
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 sipStatusCodeValue is sent or received. by sipStatusCodeValue 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
is sent. If it is 'false', no notification is sent. notification 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 message sent or received that contains the particular every message sent or received that contains the
status code. Depending on the status code involved, particular status code. Depending on the status code
this can cause a significant number of notification involved, this can cause a significant number of
emissions that could be detrimental to network performance. notification 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
sipStatusCodeNotifEmitMode for alternative sipStatusCodeNotifEmitMode for alternative
controls for sipStatusCodeNotif emissions." controls for sipStatusCodeNotif emissions."
DEFVAL { false } DEFVAL { false }
::= { sipStatusCodeNotifEntry 1 } ::= { sipStatusCodeNotifEntry 1 }
sipStatusCodeNotifEmitMode OBJECT-TYPE sipStatusCodeNotifEmitMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
normal(1), normal(1),
skipping to change at page 42, line 25 skipping to change at page 43, line 17
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and uniquely identify these instances of SIP entities and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipStatsRetryMethod } INDEX { applIndex, sipStatsRetryMethod }
::= { sipCommonStatsRetryTable 1 } ::= { sipCommonStatsRetryTable 1 }
SipCommonStatsRetryEntry ::= SipCommonStatsRetryEntry ::=
SEQUENCE { SEQUENCE {
sipStatsRetryMethod SipMethodIdentifier, sipStatsRetryMethod SipMethodName,
sipStatsRetries Counter32, sipStatsRetries Counter32,
sipStatsRetryFinalResponses Counter32, sipStatsRetryFinalResponses Counter32,
sipStatsRetryNonFinalResponses Counter32 sipStatsRetryNonFinalResponses Counter32
} }
sipStatsRetryMethod OBJECT-TYPE sipStatsRetryMethod OBJECT-TYPE
SYNTAX SipMethodIdentifier SYNTAX SipMethodName
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies the SIP method "This object uniquely identifies the SIP method
related to the objects in a row." related to the objects in a row."
::= { sipCommonStatsRetryEntry 1 } ::= { sipCommonStatsRetryEntry 1 }
sipStatsRetries OBJECT-TYPE sipStatsRetries OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 43, line 19 skipping to change at page 44, line 11
retries that have been sent by the SIP entity. retries that have been sent by the SIP entity.
Note that there could be multiple retransmissions Note that there could be multiple retransmissions
per request." per request."
::= { sipCommonStatsRetryEntry 3 } ::= { sipCommonStatsRetryEntry 3 }
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
retries that have been sent by the SIP entity." Response retries that have been sent by the SIP entity."
::= { sipCommonStatsRetryEntry 4 } ::= { sipCommonStatsRetryEntry 4 }
-- --
-- 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
skipping to change at page 44, line 17 skipping to change at page 45, line 9
sipNumUnsupportedMethods Counter32, sipNumUnsupportedMethods Counter32,
sipOtherwiseDiscardedMsgs Counter32 sipOtherwiseDiscardedMsgs 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
Request status code." Bad Request status code."
::= { sipOtherStatsEntry 1 } ::= { sipOtherStatsEntry 1 }
sipNumUnsupportedMethods OBJECT-TYPE sipNumUnsupportedMethods OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of SIP requests received with unsupported methods. "Number of SIP requests received with unsupported
methods.
A server normally responds to such requests with a A server normally responds to such requests with a
501 (Not Implemented) or 405 (Method Not Allowed)." 501 (Not Implemented) or 405 (Method Not Allowed)."
::= { sipOtherStatsEntry 2 } ::= { sipOtherStatsEntry 2 }
sipOtherwiseDiscardedMsgs OBJECT-TYPE sipOtherwiseDiscardedMsgs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of SIP messages received that for any number "Number of SIP messages received that for any number
skipping to change at page 51, line 30 skipping to change at page 52, line 21
NOTIFICATIONS { NOTIFICATIONS {
sipStatusCodeNotif, sipStatusCodeNotif,
sipStatusCodeThreshExceededInNotif, sipStatusCodeThreshExceededInNotif,
sipStatusCodeThreshExceededOutNotif, sipStatusCodeThreshExceededOutNotif,
sipServiceColdStart, sipServiceColdStart,
sipServiceWarmStart, sipServiceWarmStart,
sipServiceStatusChanged sipServiceStatusChanged
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications common to all SIP entities." "A collection of notifications common to all SIP
entities."
::= { sipCommonMIBGroups 5 } ::= { sipCommonMIBGroups 5 }
sipCommonStatusCodeNotifGroup OBJECT-GROUP sipCommonStatusCodeNotifGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatusCodeNotifSend, sipStatusCodeNotifSend,
sipStatusCodeNotifEmitMode, sipStatusCodeNotifEmitMode,
sipStatusCodeNotifThresh, sipStatusCodeNotifThresh,
sipStatusCodeNotifInterval sipStatusCodeNotifInterval
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects related to controlling and attribution "A collection of objects related to controlling and
of notifications common to all SIP entities." attribution of notifications common to all SIP
entities."
::= { sipCommonMIBGroups 6 } ::= { sipCommonMIBGroups 6 }
sipCommonNotifObjectsGroup OBJECT-GROUP sipCommonNotifObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatusCodeNotifTo, sipStatusCodeNotifTo,
sipStatusCodeNotifFrom, sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId, sipStatusCodeNotifCallId,
sipStatusCodeNotifCSeq, sipStatusCodeNotifCSeq,
sipNotifApplIndex, sipNotifApplIndex,
sipNotifSequenceNumber sipNotifSequenceNumber
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of accessible-for-notify objects "A collection of accessible-for-notify objects
related to the notification defined in this related to the notification defined in this
MIB module." MIB module."
::= { sipCommonMIBGroups 7 } ::= { sipCommonMIBGroups 7 }
END END
7.3 SIP User Agent MIB Module 7.3. SIP User Agent MIB Module
SIP-UA-MIB DEFINITIONS ::= BEGIN SIP-UA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Unsigned32, Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI -- RFC 2578
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- RFC 2580
applIndex applIndex
FROM NETWORK-SERVICES-MIB FROM NETWORK-SERVICES-MIB -- RFC 2788
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB -- RFC 4001
SipEntityRole SipEntityRole
FROM SIP-TC; FROM SIP-TC;
sipUAMIB MODULE-IDENTITY sipUAMIB MODULE-IDENTITY
LAST-UPDATED "200501281700Z" LAST-UPDATED "200603021700Z"
ORGANIZATION "IETF Session Initiation Protocol Working Group" ORGANIZATION "IETF Session Initiation Protocol
Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
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
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
skipping to change at page 53, line 21 skipping to change at page 54, line 12
Co-editor Joon Maeng Co-editor Joon Maeng
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 858 Coal Creek Circle postal: 858 Coal Creek Circle
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 3708 phone: +1 303 661 9100
Co-editor Dave Walker Co-editor Dave Walker
email: drwalker@rogers.com" email: drwalker@rogers.com"
DESCRIPTION DESCRIPTION
"Session Initiation Protocol (SIP) User Agent (UA) "Session Initiation Protocol (SIP) User Agent (UA)
MIB module. 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 page 53, line 43 skipping to change at page 54, line 34
2002). 2002).
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.
Copyright (C) The Internet Society (2005). This version Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
REVISION "200501281700Z" REVISION "200603021700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-UA-MIB module. "Initial version of the IETF SIP-UA-MIB module.
This version published as part of RFC XXXX." This version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX3 } ::= { mib-2 XXX3 }
-- RFC Ed: replace XXX3 with actual IANA assigned number -- RFC Ed: replace XXX3 with actual IANA assigned number
-- RFC Ed: and remove these notes -- RFC Ed: and remove these notes
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipUAMIBObjects OBJECT IDENTIFIER ::= { sipUAMIB 1 } sipUAMIBObjects OBJECT IDENTIFIER ::= { sipUAMIB 1 }
sipUAMIBConform OBJECT IDENTIFIER ::= { sipUAMIB 2 } sipUAMIBConform OBJECT IDENTIFIER ::= { sipUAMIB 2 }
-- --
-- This MIB contains objects related to SIP User Agents. -- This MIB contains objects related to SIP User Agents.
-- --
sipUACfgServer OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 } sipUACfgServer OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 }
-- --
-- SIP Server Configuration -- SIP Server Configuration
-- --
sipUACfgServerTable OBJECT-TYPE sipUACfgServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUACfgServerEntry SYNTAX SEQUENCE OF SipUACfgServerEntry
skipping to change at page 55, line 25 skipping to change at page 56, line 18
be tried." be tried."
::= { sipUACfgServerEntry 1 } ::= { sipUACfgServerEntry 1 }
sipUACfgServerAddrType OBJECT-TYPE sipUACfgServerAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the type of address contained "This object reflects the type of address contained
in the associated instance of sipUACfgServerAddr." in the associated instance of sipUACfgServerAddr."
REFERENCE "INET-ADDRESS-MIB (RFC 3291)" REFERENCE "INET-ADDRESS-MIB (RFC 4001)"
::= { sipUACfgServerEntry 2 } ::= { sipUACfgServerEntry 2 }
sipUACfgServerAddr OBJECT-TYPE sipUACfgServerAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the address of a SIP server "This object reflects the address of a SIP server
this user agent will use to proxy/redirect calls." this user agent will use to proxy/redirect calls."
REFERENCE "INET-ADDRESS-MIB (RFC 3291)" REFERENCE "INET-ADDRESS-MIB (RFC 4001)"
::= { sipUACfgServerEntry 3 } ::= { sipUACfgServerEntry 3 }
sipUACfgServerFunction OBJECT-TYPE sipUACfgServerFunction OBJECT-TYPE
SYNTAX SipEntityRole SYNTAX SipEntityRole
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the function of the SIP server "This object reflects the function of the SIP server
this user agent should communicate with: registrar, proxy this user agent should communicate with: registrar,
(outbound proxy), etc." proxy (outbound proxy), etc."
::= { sipUACfgServerEntry 4 } ::= { sipUACfgServerEntry 4 }
-- --
-- Conformance -- Conformance
-- --
sipUAMIBCompliances sipUAMIBCompliances
OBJECT IDENTIFIER ::= { sipUAMIBConform 1 } OBJECT IDENTIFIER ::= { sipUAMIBConform 1 }
sipUAMIBGroups sipUAMIBGroups
OBJECT IDENTIFIER ::= { sipUAMIBConform 2 } OBJECT IDENTIFIER ::= { sipUAMIBConform 2 }
skipping to change at page 56, line 38 skipping to change at page 57, line 31
sipUACfgServerFunction sipUACfgServerFunction
} }
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 }
END END
7.4 SIP Server MIB Module (Proxy, Redirect and Registrar Servers) 7.4. SIP Server MIB Module (Proxy, Redirect and Registrar Servers)
SIP-SERVER-MIB DEFINITIONS ::= BEGIN SIP-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Counter32, Counter32,
Unsigned32, Unsigned32,
Gauge32, Gauge32,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI -- RFC 2578
TruthValue, TruthValue,
TimeStamp, DateAndTime TimeStamp, DateAndTime
FROM SNMPv2-TC FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB -- RFC 3411
applIndex applIndex
FROM NETWORK-SERVICES-MIB FROM NETWORK-SERVICES-MIB -- RFC 2788
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB; -- RFC 4001
sipServerMIB MODULE-IDENTITY sipServerMIB MODULE-IDENTITY
LAST-UPDATED "200501281700Z" LAST-UPDATED "200603021700Z"
ORGANIZATION "IETF Session Initiation Protocol Working Group" ORGANIZATION "IETF Session Initiation Protocol
Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
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
skipping to change at page 57, line 46 skipping to change at page 58, line 38
Co-editor Joon Maeng Co-editor Joon Maeng
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 858 Coal Creek Circle postal: 858 Coal Creek Circle
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 3708 phone: +1 303 661 9100
Co-editor Dave Walker Co-editor Dave Walker
email: drwalker@rogers.com" email: drwalker@rogers.com"
DESCRIPTION DESCRIPTION
"Session Initiation Protocol (SIP) Server MIB module. "Session Initiation Protocol (SIP) Server MIB module.
SIP is an application-layer signaling protocol for SIP is an application-layer signaling 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
include Internet multimedia conferences and Internet sessions include Internet multimedia conferences and
telephone calls. SIP is defined in RFC 3261 (June Internet telephone calls. SIP is defined in
2002). RFC 3261 (June 2002).
This MIB is defined for the management of SIP Proxy, This MIB is defined for the management of SIP Proxy,
Redirect and Registrar Servers. Redirect and Registrar Servers.
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. returns zero or more addresses to that client.
Unlike a User Agent Server it does not accept calls. Unlike 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
Proxy or Redirect Server. a Proxy or Redirect Server.
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
This version of this MIB module is part of RFC XXXX; This version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
REVISION "200501281700Z" REVISION "200603021700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-SERVER-MIB module. "Initial version of the IETF SIP-SERVER-MIB module.
This version published as part of RFC XXXX." This version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX4 } ::= { mib-2 XXX4 }
-- RFC Ed: replace XXX4 with actual IANA assigned number and remove this note -- RFC Ed: replace XXX4 with actual IANA assigned number
-- and remove this note
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 } sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 }
sipServerMIBConform OBJECT IDENTIFIER ::= { sipServerMIB 2 } sipServerMIBConform OBJECT IDENTIFIER ::= { sipServerMIB 2 }
-- --
-- These groups contain objects common to all SIP servers. -- These groups contain objects common to all SIP servers.
-- --
sipServerCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 1 } sipServerCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 1 }
skipping to change at page 59, line 11 skipping to change at page 60, line 4
-- 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." to SIP Redirect and Proxy Servers."
::= { 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 Each row represents those objects for a particular
server present in this system. applIndex is used to SIP server present in this system. applIndex is used
uniquely identify these instances of SIP servers and to uniquely identify these instances of SIP servers
correlate them through the common framework of the and correlate them through the common framework of
NETWORK-SERVICES-MIB (RFC 2788). The same value of the NETWORK-SERVICES-MIB (RFC 2788). The same value
applIndex used in the corresponding SIP-COMMON-MIB of applIndex used in the corresponding SIP-COMMON-MIB
is used here. is used here.
The objects in this table entry SHOULD be non-volatile The objects in this table entry SHOULD be
and their value SHOULD be kept at reboot." non-volatile and their value SHOULD be kept at
reboot."
INDEX { applIndex } INDEX { applIndex }
::= { sipServerCfgTable 1 } ::= { sipServerCfgTable 1 }
SipServerCfgEntry ::= SipServerCfgEntry ::=
SEQUENCE { SEQUENCE {
sipServerHostAddrType InetAddressType, sipServerHostAddrType InetAddressType,
sipServerHostAddr InetAddress sipServerHostAddr InetAddress
} }
sipServerHostAddrType OBJECT-TYPE sipServerHostAddrType OBJECT-TYPE
skipping to change at page 60, line 5 skipping to change at page 60, line 46
is reachable." is reachable."
REFERENCE REFERENCE
"RFC 3261, Section 19.1.1" "RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 1 } ::= { sipServerCfgEntry 1 }
sipServerHostAddr OBJECT-TYPE sipServerHostAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the host portion of a SIP URI that is assigned "This is the host portion of a SIP URI that is
to the SIP server. It MAY contain a fully qualified assigned to the SIP server. It MAY contain a fully
domain name, or an IP address. The length of the value qualified domain name, or an IP address. The length
will depend on the type of address specified. of the value will depend on the type of address
specified.
sipServerHostAddrType formalizes the type of address sipServerHostAddrType formalizes the type of address
given by this object. It is the users responsibility given by this object. It is the users responsibility
to maintain consistency between this object and the to maintain consistency between this object and the
type specified by sipServerHostAddrType." type specified by sipServerHostAddrType."
REFERENCE REFERENCE
"RFC 3261, Section 19.1.1" "RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 2 } ::= { sipServerCfgEntry 2 }
-- --
-- This group contains MIB objects related to SIP Proxy Servers. -- This group contains MIB objects
-- related to SIP Proxy Servers.
-- --
sipProxyCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 3 } sipProxyCfg OBJECT IDENTIFIER ::=
sipProxyStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 4 } { sipServerMIBObjects 3 }
sipProxyStats OBJECT IDENTIFIER ::=
{ sipServerMIBObjects 4 }
-- --
-- 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." to SIP Proxy Servers."
::= { 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 proxy configuration. "A row of common proxy configuration.
Each row represents those objects for a particular SIP Each row represents those objects for a particular
server present in this system. applIndex is used to SIP server present in this system. applIndex is used
uniquely identify these instances of SIP servers and to uniquely identify these instances of SIP servers
correlate them through the common framework of the and correlate them through the common framework of
NETWORK-SERVICES-MIB (RFC 2788). The same value of the NETWORK-SERVICES-MIB (RFC 2788). The same value
applIndex used in the corresponding SIP-COMMON-MIB of applIndex used in the corresponding SIP-COMMON-MIB
is used here. is used here.
The objects in this table entry SHOULD be non-volatile The objects in this table entry SHOULD be
and their value SHOULD be kept at reboot." non-volatile and their value SHOULD be kept at
reboot."
INDEX { applIndex } INDEX { applIndex }
::= { sipProxyCfgTable 1 } ::= { sipProxyCfgTable 1 }
SipProxyCfgEntry ::= SipProxyCfgEntry ::=
SEQUENCE { SEQUENCE {
sipProxyStatefulness INTEGER, sipProxyStatefulness INTEGER,
sipProxyRecursion TruthValue, sipProxyRecursion TruthValue,
sipProxyRecordRoute TruthValue, sipProxyRecordRoute TruthValue,
sipProxyAuthMethod BITS, sipProxyAuthMethod BITS,
sipProxyAuthRealm SnmpAdminString sipProxyAuthRealm SnmpAdminString
} }
sipProxyStatefulness OBJECT-TYPE sipProxyStatefulness OBJECT-TYPE
skipping to change at page 61, line 24 skipping to change at page 62, line 22
sipProxyStatefulness OBJECT-TYPE sipProxyStatefulness OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
stateless(1), stateless(1),
transactionStateful(2), transactionStateful(2),
callStateful(3) callStateful(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the default mode of operation for "This object reflects the default mode of operation
the Proxy Server entity. for the Proxy Server entity.
A stateless proxy is a logical entity that does not A stateless proxy is a logical entity that does not
maintain the client or server transaction state machines maintain the client or server transaction state
when it processes requests. A stateless proxy forwards machines when it processes requests. A stateless
every request it receives downstream and every response proxy forwards every request it receives downstream
it receives upstream. If the value of this object is and every response it receives upstream. If the value
stateless(1), the proxy defaults to stateless of this object is stateless(1), the proxy defaults to
operations. stateless operations.
A transaction stateful proxy, or simply a 'stateful A transaction stateful proxy, or simply a 'stateful
proxy', is a logical entity that maintains the client proxy', is a logical entity that maintains the client
and server transaction state machines during the and server transaction state machines during the
processing of a request. A (transaction) stateful proxy processing of a request. A (transaction) stateful
is not the same as a call stateful proxy. If the value proxy is not the same as a call stateful proxy. If
if this object is transactionStateful(2), the proxy is the value if this object is transactionStateful(2),
stateful on a transaction basis. the proxy is stateful on a transaction basis.
A call stateful proxy is a logical entity if it retains A call stateful proxy is a logical entity if it
state for a dialog from the initiating INVITE to the retains state for a dialog from the initiating INVITE
terminating BYE request. A call stateful proxy is to the terminating BYE request. A call stateful
always transaction stateful, but the converse is not proxy is always transaction stateful, but the
necessarily true. If the value of this object is converse is not necessarily true. If the value of
callStateful(3), the proxy is call stateful." this object is callStateful(3), the proxy is call
stateful."
REFERENCE REFERENCE
"RFC 3261, Section 16" "RFC 3261, Section 16"
::= { sipProxyCfgEntry 1 } ::= { sipProxyCfgEntry 1 }
sipProxyRecursion OBJECT-TYPE sipProxyRecursion OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects whether or not the Proxy performs "This object reflects whether or not the Proxy
recursive search on the Contacts provided in 3xx performs recursive search on the Contacts provided in
redirects. 3xx redirects.
If the value of this object is 'true', a recursive search If the value of this object is 'true', a recursive
is performed. If the value is 'false', no search is search is performed. If the value is 'false', no
performed, the 3xx response is sent upstream towards the search is performed, the 3xx response is sent
source of the request." upstream towards the source of the request."
REFERENCE REFERENCE
"RFC 3261 Sections 16.5 and 16.6" "RFC 3261 Sections 16.5 and 16.6"
::= { sipProxyCfgEntry 2 } ::= { sipProxyCfgEntry 2 }
sipProxyRecordRoute OBJECT-TYPE sipProxyRecordRoute OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects whether or not the proxy adds itself "This object reflects whether or not the proxy adds
to the Record-Route header as a default action. This itself to the Record-Route header as a default
header is used to list the proxies that insist on being in action.
the signaling path for subsequent requests related to the This header is used to list the proxies that insist
call-leg. on being in the signaling path for subsequent
requests related to the call-leg.
If the value of this object is 'true', the proxy adds itself If the value of this object is 'true', the proxy adds
to the end of the Record-Route header, creating the header itself to the end of the Record-Route header,
if required. If the value is 'false', the proxy does creating the header if required. If the value is
not add itself to the Record-Route header." 'false', the proxy does not add itself to the
Record-Route header."
REFERENCE REFERENCE
"RFC 3261, Section 20.30" "RFC 3261, Section 20.30"
::= { sipProxyCfgEntry 3 } ::= { sipProxyCfgEntry 3 }
-- --
-- Security -- Security
-- --
sipProxyAuthMethod OBJECT-TYPE sipProxyAuthMethod OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
none(0), none(0),
skipping to change at page 63, line 20 skipping to change at page 64, line 22
bit 2 HTTP Digest is used." bit 2 HTTP Digest is used."
REFERENCE REFERENCE
"RFC 3261 Sections 22, 23, 26, 26.2.3" "RFC 3261 Sections 22, 23, 26, 26.2.3"
::= { sipProxyCfgEntry 4 } ::= { sipProxyCfgEntry 4 }
sipProxyAuthRealm OBJECT-TYPE sipProxyAuthRealm OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the realm used in Proxy-Authenticate "This object reflects the realm used in
headers. Note that this MAY need to be stored per user." Proxy-Authenticate headers. Note that this MAY need
to be stored per user."
REFERENCE REFERENCE
"RFC 3261, Section 22.1" "RFC 3261, Section 22.1"
::= { sipProxyCfgEntry 5 } ::= { sipProxyCfgEntry 5 }
-- --
-- Proxy Server Statistics -- Proxy Server Statistics
-- --
sipProxyStatsTable OBJECT-TYPE sipProxyStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipProxyStatsEntry SYNTAX SEQUENCE OF SipProxyStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 63, line 45 skipping to change at page 64, line 48
to all SIP Proxy Servers in this system." to all SIP Proxy Servers in this system."
::= { 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 Each row represents those objects for a particular
server present in this system. applIndex is used to SIP server present in this system. applIndex is used
uniquely identify these instances of SIP servers and to uniquely identify these instances of SIP servers
correlate them through the common framework of the and correlate them through the common framework of
NETWORK-SERVICES-MIB (RFC 2788). The same value of the NETWORK-SERVICES-MIB (RFC 2788). The same value
applIndex used in the corresponding SIP-COMMON-MIB of applIndex used in the corresponding SIP-COMMON-MIB
is used here." is used here."
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
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the number of occurrences of "This object contains the number of occurrences of
unsupported options being specified in received Proxy- unsupported options being specified in received
Require headers. Such occurrences result in a 420 Bad Proxy- Require headers. Such occurrences result in a
Extension status code being 420 Bad Extension status code being returned."
returned."
::= { sipProxyStatsEntry 1 } ::= { sipProxyStatsEntry 1 }
-- --
-- This group contains MIB objects related to SIP Registrars. -- This group contains MIB objects related to SIP Registrars.
-- --
sipRegCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 5 } sipRegCfg OBJECT IDENTIFIER ::=
sipRegStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 6 } { sipServerMIBObjects 5 }
sipRegStats OBJECT IDENTIFIER ::=
{ sipServerMIBObjects 6 }
-- --
-- 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." SIP Registrars."
::= { 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 Registrar configuration. "A row of common Registrar configuration.
Each row represents those objects for a particular SIP Each row represents those objects for a particular
server present in this system. applIndex is used to SIP server present in this system. applIndex is used
uniquely identify these instances of SIP servers and to uniquely identify these instances of SIP servers
correlate them through the common framework of the and correlate them through the common framework of
NETWORK-SERVICES-MIB (RFC 2788). The same value of the NETWORK-SERVICES-MIB (RFC 2788). The same value
applIndex used in the corresponding SIP-COMMON-MIB of applIndex used in the corresponding SIP-COMMON-MIB
is used here." is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipRegCfgTable 1 } ::= { sipRegCfgTable 1 }
SipRegCfgEntry ::= SipRegCfgEntry ::=
SEQUENCE { SEQUENCE {
sipRegAllowThirdParty TruthValue, sipRegAllowThirdParty TruthValue,
sipRegMaxContactExpiryDuration Unsigned32, sipRegMaxContactExpiryDuration Unsigned32,
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-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects whether or not the Registrar SHOULD "This object reflects whether or not the Registrar
allow third party registrations. In third-party SHOULD allow third party registrations. In third-party
registration, the entity issuing the request (in the registration, the entity issuing the request (in the
From header) is different from the entity being registered From header) is different from the entity being
(in the To header) to whom the provided Contact information registered (in the To header) to whom the provided
applies. Contact information applies.
If the value of this object is 'true', If the value of this object is 'true', the Registrar
the Registrar allows third-party registrations. If the allows third-party registrations. If the value is
value is 'false', third-party registrations are rejected: 'false', third-party registrations are rejected: a
a 403 (Forbidden) status code is returned to the requester. 403 (Forbidden) status code is returned to the
This object SHOULD be non-volatile and its value SHOULD requester.
be kept at reboot." This object SHOULD be non-volatile and its value
SHOULD be kept at reboot."
REFERENCE REFERENCE
"RFC 3261, Section 10.2" "RFC 3261, Section 10.2"
::= { sipRegCfgEntry 1 } ::= { sipRegCfgEntry 1 }
sipRegMaxContactExpiryDuration OBJECT-TYPE sipRegMaxContactExpiryDuration OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 66, line 4 skipping to change at page 67, line 9
::= { sipRegCfgEntry 1 } ::= { sipRegCfgEntry 1 }
sipRegMaxContactExpiryDuration OBJECT-TYPE sipRegMaxContactExpiryDuration OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum expiry that may be "This object reflects the maximum expiry that may be
requested by a User Agent for a particular Contact. requested by a User Agent for a particular Contact.
User Agents can specify expiry using either an Expiry User Agents can specify expiry using either an Expiry
header in a REGISTER request, or using an Expires parameter header in a REGISTER request, or using an Expires
in a Contact header in a REGISTER request. If the value parameter in a Contact header in a REGISTER request.
requested by the User Agent is greater than the value If the value requested by the User Agent is greater
of this object, then the contact information is given the than the value of this object, then the contact
duration specified by this object, and that duration information is given the duration specified by this
is indicated to the User Agent in the response." object, and that duration is indicated to the User
Agent in the response."
::= { sipRegCfgEntry 2 } ::= { sipRegCfgEntry 2 }
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 reflects the maximum number of users that "This object reflects the maximum number of users that
the Registrar supports. The current number of users is the Registrar supports. The current number of users
reflected by sipRegCurrentUsers." is reflected by sipRegCurrentUsers."
::= { sipRegCfgEntry 3 } ::= { 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 reflects the number of users currently "This object reflects the number of users currently
registered with the Registrar." registered with the Registrar."
::= { sipRegCfgEntry 4 } ::= { sipRegCfgEntry 4 }
skipping to change at page 66, line 50 skipping to change at page 68, line 7
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. If a Contact Registrar SHOULD honor that request. If a Contact
entry does not have an 'expires' parameter, the value entry does not have an 'expires' parameter, the value
of the Expires header field is used instead. If a of the Expires header field is used instead. If a
Contact entry has no 'expires' parameter and no the Contact entry has no 'expires' parameter and no the
Expires header field is present, the value of this Expires header field is present, the value of this
object is used as the default value. object is used as the default value.
This object SHOULD be non-volatile and its value SHOULD This object SHOULD be non-volatile and its value
be kept at reboot." SHOULD be kept at reboot."
REFERENCE "RFC 3261, Section 10.2" REFERENCE "RFC 3261, Section 10.2"
::= { sipRegCfgEntry 5 } ::= { 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 "This table contains information on all users
to each Registrar in this system." registered to each Registrar in this system."
::= { 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 Each row represents those objects for a particular
server present in this system. applIndex is used to SIP server present in this system. applIndex is used
uniquely identify these instances of SIP servers and to uniquely identify these instances of SIP servers
correlate them through the common framework of the and correlate them through the common framework of
NETWORK-SERVICES-MIB (RFC 2788). The same value of the NETWORK-SERVICES-MIB (RFC 2788). The same value
applIndex used in the corresponding SIP-COMMON-MIB of applIndex used in the corresponding SIP-COMMON-MIB
is used here." is used here."
INDEX { applIndex, sipUserIndex } INDEX { applIndex, sipUserIndex }
::= { sipRegUserTable 1 } ::= { sipRegUserTable 1 }
SipRegUserEntry ::= SipRegUserEntry ::=
SEQUENCE { SEQUENCE {
sipUserIndex Unsigned32, sipUserIndex Unsigned32,
sipUserUri SnmpAdminString, sipUserUri SnmpAdminString,
sipUserAuthenticationFailures Counter32 sipUserAuthenticationFailures Counter32
} }
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
table." the table."
::= { sipRegUserEntry 1 } ::= { sipRegUserEntry 1 }
sipUserUri OBJECT-TYPE sipUserUri OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the user's address-of-record. It "This object contains the user's address-of-record.
is the main form by which the Registrar knows the user. It is the main form by which the Registrar knows the
The format is typically 'user@domain'. It is contained user. The format is typically 'user@domain'. It is
in the To header for all REGISTER requests." contained in the To header for all REGISTER
requests."
::= { sipRegUserEntry 2 } ::= { sipRegUserEntry 2 }
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
user has failed authentication." the user has failed authentication."
::= { sipRegUserEntry 3 } ::= { sipRegUserEntry 3 }
-- --
-- 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 "This table contains information on every location
a registered user (specified by sipUserIndex) wishes to where a registered user (specified by sipUserIndex)
be found (i.e. the user has provided Contact information wishes to be found (i.e. the user has provided Contact
to each SIP Registrar in this system)." information to each SIP Registrar in this system)."
::= { 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 Each row represents those objects for a particular
server present in this system. applIndex is used to SIP server present in this system. applIndex is used
uniquely identify these instances of SIP servers and to uniquely identify these instances of SIP servers
correlate them through the common framework of the and correlate them through the common framework of
NETWORK-SERVICES-MIB (RFC 2788). The same value of the NETWORK-SERVICES-MIB (RFC 2788). The same value
applIndex used in the corresponding SIP-COMMON-MIB of applIndex used in the corresponding SIP-COMMON-MIB
is used here." is used here."
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,
sipContactLastUpdated TimeStamp, sipContactLastUpdated TimeStamp,
skipping to change at page 69, line 33 skipping to change at page 70, line 41
DESCRIPTION DESCRIPTION
"Along with the sipUserIndex, this object uniquely "Along with the sipUserIndex, this object uniquely
identifies a conceptual row in the table." identifies a conceptual row in the table."
::= { sipContactEntry 1 } ::= { sipContactEntry 1 }
sipContactDisplayName OBJECT-TYPE sipContactDisplayName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the display name for the Contact. "This object contains the display name for the
Contact.
For example, 'Santa at Home', or 'Santa on his Sled', For example, 'Santa at Home', or 'Santa on his Sled',
corresponding to contact URIs of corresponding to contact URIs of
sip:BigGuy@sip.northpole.ca or sip:BigGuy@example.com or
sip:sclaus817@sip.mobile.com, respectively." sip:sclaus817@example.com, respectively."
::= { sipContactEntry 2 } ::= { sipContactEntry 2 }
sipContactURI OBJECT-TYPE sipContactURI OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains either a SIP URI where "This object contains either a SIP URI where
the user can be contacted. This URI is normally returned the user can be contacted. This URI is normally
to a client from a Redirect Server, or is used as the returned to a client from a Redirect Server, or is
RequestURI in a SIP request line for requests forwarded used as the RequestURI in a SIP request line for
by a proxy." requests forwarded by a proxy."
::= { sipContactEntry 3 } ::= { sipContactEntry 3 }
sipContactLastUpdated OBJECT-TYPE sipContactLastUpdated OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the time when this contact "This object indicates the time when this contact
information was accepted. If the contact information information was accepted. If the contact information
is updated via a subsequent REGISTER of the same is updated via a subsequent REGISTER of the same
information, this object is also updated." information, this object is also updated."
::= { sipContactEntry 4 } ::= { sipContactEntry 4 }
skipping to change at page 70, line 20 skipping to change at page 71, line 29
information was accepted. If the contact information information was accepted. If the contact information
is updated via a subsequent REGISTER of the same is updated via a subsequent REGISTER of the same
information, this object is also updated." information, 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
information will no longer be valid. Such times may be contact information will no longer be valid. Such
specified by the user at registration (Expires header times may be specified by the user at registration
or expiry parameter in the Contact information), or a (Expires header or expiry parameter in the Contact
system default can be applied." information), or a system default can be applied."
::= { sipContactEntry 5 } ::= { sipContactEntry 5 }
sipContactPreference OBJECT-TYPE sipContactPreference OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a relative preference for the "This object indicates a relative preference for the
particular Contact header field value compared to other particular Contact header field value compared to
bindings for this address-of-record. A registering user other bindings for this address-of-record. A
may provide this preference as a 'qvalue'parameter in registering user may provide this preference as a
the Contact header. 'qvalue'parameter in the Contact header.
The format of this item is a decimal number between 0 The format of this item is a decimal number between 0
and 1 (for example 0.9). Higher values indicate and 1 (for example 0.9). Higher values indicate
locations preferred by the user." locations preferred by the user."
REFERENCE REFERENCE
"RFC 3261, Section 10.2.1.2, 16.6 and 20.10" "RFC 3261, Section 10.2.1.2, 16.6 and 20.10"
::= { sipContactEntry 6 } ::= { sipContactEntry 6 }
-- --
-- Registrar Statistics -- Registrar Statistics
skipping to change at page 71, line 18 skipping to change at page 72, line 25
applicable to all SIP Registrars in this system." applicable to all SIP Registrars in this system."
::= { 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 Each row represents those objects for a particular
server present in this system. applIndex is used to SIP server present in this system. applIndex is used
uniquely identify these instances of SIP servers and to uniquely identify these instances of SIP servers
correlate them through the common framework of the and correlate them through the common framework of
NETWORK-SERVICES-MIB (RFC 2788). The same value of the NETWORK-SERVICES-MIB (RFC 2788). The same value
applIndex used in the corresponding SIP-COMMON-MIB of applIndex used in the corresponding SIP-COMMON-MIB
is used here." is used here."
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
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 REGISTER "This object contains a count of the number of
requests that have been accepted (status code 200) by REGISTER requests that have been accepted (status code
the Registrar. This includes additions of new contact 200) by the Registrar. This includes additions of new
information, refreshing contact information, as well as contact information, refreshing contact information,
requests for deletion of contact information." as well as requests for deletion of contact
information."
::= { sipRegStatsEntry 1 } ::= { sipRegStatsEntry 1 }
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 }
skipping to change at page 73, line 14 skipping to change at page 74, line 25
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipServerConfigGroup OBJECT-GROUP sipServerConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipServerHostAddrType, sipServerHostAddrType,
sipServerHostAddr sipServerHostAddr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration common "A collection of objects providing configuration
to SIP Proxy and Redirect servers." common to SIP Proxy and Redirect servers."
::= { sipServerMIBGroups 1 } ::= { sipServerMIBGroups 1 }
sipProxyConfigGroup OBJECT-GROUP sipProxyConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipProxyStatefulness, sipProxyStatefulness,
sipProxyRecursion, sipProxyRecursion,
sipProxyRecordRoute, sipProxyRecordRoute,
sipProxyAuthMethod, sipProxyAuthMethod,
sipProxyAuthRealm sipProxyAuthRealm
} }
skipping to change at page 74, line 36 skipping to change at page 76, line 5
sipContactExpiry, sipContactExpiry,
sipContactPreference sipContactPreference
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects related to registered users." "A collection of objects related to registered users."
::= { sipServerMIBGroups 6 } ::= { sipServerMIBGroups 6 }
END END
8. Changes from Previous Draft Revisions 8. IANA Considerations
The MIB modules defined in this document use the following IANA-
assigned OBJECT IDENTIFIER values recorded in the SMI Numbers
registry:
+--------------+-------------------------+
| Descriptor | OBJECT IDENTIFIER value |
+--------------+-------------------------+
| sipTC | { mib-2 XXX1 } |
| sipCommonMIB | { mib-2 XXX2 } |
| sipUAMIB | { mib-2 XXX3 } |
| sipServerMIB | { mib-2 XXX4} |
+--------------+-------------------------+
-- RFC Ed:(note to be removed prior to publication): the IANA is
requested to assign 4 values in the SMI Numbers registry for "XXX1",
"XXX2", "XXX3", and "XXX4", all under the 'mib-2' sub-tree and to
record the assignments in the SMI Numbers registry. When the
assignments have been made, the RFC Editor is asked to replace "XXX1"
through "XXX4" (here and in the 4 MIB modules) with the corresponding
assigned value and to remove this note.
9. Security Considerations
There are a number of management objects defined in the SIP-COMMON-
MIB MIB module with a MAX-ACCESS clause of read-write and/or read-
create. Such objects may be considered sensitive or vulnerable in
some network environments. The support for SET operations in a non-
secure environment without proper protection can have a negative
effect on network operations.
The following read-create object in SIP-COMMON-MIB is used to
configure the status code statistics that will be monitored by the
SIP entity:
sipStatusCodeRowStatus:
if this object is SET maliciously, it may result in an over
allocation of resources in a system for the purpose of
accumulating and maintaining statistics.
The following read-write objects in SIP-COMMON-MIB are used to
configure the behavior of certain SNMP notifications potentially
generated by a SIP entity:
sipStatusCodeNotifSend, sipStatusCodeNotifEmitMode,
sipStatusCodeNotifThresh, sipStatusCodeNotifInterval,
sipServiceNotifEnable:
If these objects are SET maliciously, it may result in a system
and/or network performance impact due to the generation of SNMP
notifications.
Some of the readable objects in the MIB modules (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP.
The following object values may contain private or confidential
customer information like first name, last name, customer
identification, location, company affiliation, the time the
information was updated, etc.
sipContactDisplayName, sipContactURI, sipContactLastUpdated and
sipOrganization.
The sipCommonCfgTable table contains some objects that may help
attackers gain knowledge about the status and operations of the SIP
service. In particular, the object value of sipServiceOperStatus may
indicate that the SIP entity is in congested state and may lead
attackers to build additional service attacks to overload the system.
The sipEntityType object indicates the type of SIP entity and the
sipMethodSupportedTable table contains in the SIP-COMMON-MIB MIB
module list of SIP methods supported by each entity in the system.
Gaining access to this information may allow attackers to build
method specific attacks or use unsupported methods to create denial
of service attack scenarios.
In the SIP-UA-MIB MIB module, the sipUACfgServerTable contains the
address of the SIP servers providing services to the UA and obtaining
this information may disclose some private or sensitive information
about the SIP service usage.
In the SIP-SERVER-MIB MIB module, the sipProxyAuthMethod object
defines the authentication methods supported by the server and may be
used to build specific denial of service attackers targeted at the
security mechanisms employed by the SIP entity.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network 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 GET/SET (read/change/create/delete) the objects
in this set of MIB modules.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see RFC 3410 [RFC3410]), including
full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
10. Contributor Acknowledgments
We wish to thank the members of the IETF SIP and SIPPING working
groups, and the SIP-MIB Design team for their comments and
suggestions. Detailed comments were provided by Tom Taylor, Kavitha
Patchayappan, Dan Romascanu, Cullen Jennins, Orit Levin, AC
Mahendran, Mary Barnes, Rohan Mahy, Bob Penfield, Charles Eckel and
Dean Willis.
11. Changes from Previous Draft Revisions
-- RFC Ed: this entire section to be removed by RFC Editor before -- RFC Ed: this entire section to be removed by RFC Editor before
publication. publication.
Changes from draft-ietf-sip-mib-09.
The changes were minimal and mostly done to address MIB doctor
comments on SipMethodIdentifier. The list of changes includes:
o removal of SipMethodIdentifier textual convention per MIB doctor
feedback
o updates of normative references (e.g. RFC 3291 --> RFC 4001)
o added a new section to provide a citation to IMPORTed RFCs as they
are norm. references
Changes from draft-ietf-sip-mib-08. Changes from draft-ietf-sip-mib-08.
The majority of changes are in response to additional SIP Working The majority of changes are in response to additional SIP Working
Group comments. Group comments.
o General o General
* The IANA Consideration section was updated and a new section * The IANA Consideration section was updated and a new section
9.2 was added to conform with the Guidelines for Authors and 9.2 was added to conform with the Guidelines for Authors and
Reviewers of MIB Documents, Reviewers of MIB Documents,
draft-ietf-ops-mib-review-guidelines-03.txt, section 3.7. draft-ietf-ops-mib-review-guidelines-03.txt, section 3.7.
* In general the ability to configure SIP entities via * In general the ability to configure SIP entities via read-
read-create or read-write objects was removed and those objects create or read-write objects was removed and those objects MAX-
MAX-ACCESS constrained to read-only. This change was made ACCESS constrained to read-only. This change was made based on
based on general consensus that SNMP should be limited to general consensus that SNMP should be limited to monitoring
monitoring rather than configuring/provisoning. rather than configuring/provisoning.
* The section 5.2 (Relationship to the Network Services MIB) was * The section 5.2 (Relationship to the Network Services MIB) was
updated to allow each instance of a SIP entity to have its own updated to allow each instance of a SIP entity to have its own
row in the applTable (a unique aplication identifier should now row in the applTable (a unique aplication identifier should now
be appended to the "sip_xxx" entity-name). We also lowered the be appended to the "sip_xxx" entity-name). We also lowered the
level of requirement on the naming convention to a SHOULD level of requirement on the naming convention to a SHOULD
instead of a MUST per wg input. instead of a MUST per wg input.
* Updated the ORGANISATION clause of all MIB modules to include * Updated the ORGANISATION clause of all MIB modules to include
the full SIP working group name. the full SIP working group name.
* Minor other editorial changes were made to the document. * Minor other editorial changes were made to the document.
* Updated Security consideration section. * Updated Security consideration section.
skipping to change at page 77, line 7 skipping to change at page 81, line 7
reviewers suggested a change based on some change of terms in reviewers suggested a change based on some change of terms in
the standard. Transactions seemed the appropriate term. The the standard. Transactions seemed the appropriate term. The
object description was also enhanced. object description was also enhanced.
* sipRequestUriHostMatching object removed based on comments from * sipRequestUriHostMatching object removed based on comments from
workgroup last call comments. workgroup last call comments.
* sipEntityType changed from enumerated INTEGER to SipEntityRole * sipEntityType changed from enumerated INTEGER to SipEntityRole
textual convention syntax. textual convention syntax.
* sipServiceAdminStatus enumerated value 'quiesceSessions' * sipServiceAdminStatus enumerated value 'quiesceSessions'
changed to 'quiesceDialogs'. changed to 'quiesceDialogs'.
* sipPortTable was redesigned. sipTransportSnd object was * sipPortTable was redesigned. sipTransportSnd object was removed
removed as it did not make much sense. sipPortStatus was as it did not make much sense. sipPortStatus was removed to
removed to prevent any row creation deletion. The remaining prevent any row creation deletion. The remaining object,
object, sipTransportRcv was made read-only. sipTransportRcv was made read-only.
* sipUriSupportedTable was removed as it was not deemed useful * sipUriSupportedTable was removed as it was not deemed useful
anymore. anymore.
* sipExtMethodSupportedTable replaced with a general * sipExtMethodSupportedTable replaced with a general
sipMethodSupportedTable. IANA SIP method identifiers/numbers sipMethodSupportedTable. IANA SIP method identifiers/numbers
will be used in this new table. The previous concept of will be used in this new table. The previous concept of
explicitly defining objects per the current well-know methods explicitly defining objects per the current well-know methods
and then providing separate, semantically similar, 'extension and then providing separate, semantically similar, 'extension
methods' tables has been eliminated. methods' tables has been eliminated.
* sipCommonCfgTimerExtMethodTable was removed. No more need for * sipCommonCfgTimerExtMethodTable was removed. No more need for
'extension methods' tables. 'extension methods' tables.
skipping to change at page 77, line 41 skipping to change at page 81, line 41
SipMethodIdentifer textual convention. The objects were SipMethodIdentifer textual convention. The objects were
generalized to two: sipStatsOutbound and sipStatsInbound. The generalized to two: sipStatsOutbound and sipStatsInbound. The
indexing object (sipStatsMethod) has syntax SipMethodIdentifier indexing object (sipStatsMethod) has syntax SipMethodIdentifier
and thereby identifies the method associated with the instances and thereby identifies the method associated with the instances
of in/out counter objects. of in/out counter objects.
* sipCurrentTransactions description changed to reflect that in * sipCurrentTransactions description changed to reflect that in
the case of forked request, _each_ branch rather than _all_ the case of forked request, _each_ branch rather than _all_
branches count as a single transaction. branches count as a single transaction.
* sipCommonStatsRetryTable was redesigned, taking into account * sipCommonStatsRetryTable was redesigned, taking into account
the new SipMethodIdentifer textual convention. A single, the new SipMethodIdentifer textual convention. A single,
generalize object (sipStatsRetries) replaces several generalize object (sipStatsRetries) replaces several method-
method-specific objects. The new, additional indexing object specific objects. The new, additional indexing object
(sipStatsRetryMethod) has syntax SipMethodIdentifier and (sipStatsRetryMethod) has syntax SipMethodIdentifier and
thereby identifies the method associated with the instances of thereby identifies the method associated with the instances of
the counter objects in each row. the counter objects in each row.
* sipCommonStatsRetryExtMethodTable was removed. * sipCommonStatsRetryExtMethodTable was removed.
* sipStatusCodeClassesTable removed. * sipStatusCodeClassesTable removed.
* sipOtherStatsTable has two new objects added: * sipOtherStatsTable has two new objects added:
sipNumUnsupportedMethods and sipOtherwiseDiscardedMsgs. sipNumUnsupportedMethods and sipOtherwiseDiscardedMsgs.
* The following object-groups were removed because their * The following object-groups were removed because their
associated objects were removed: associated objects were removed:
sipCommonConfigTimerExtMethodGroup, sipCommonConfigRetryGroup, sipCommonConfigTimerExtMethodGroup, sipCommonConfigRetryGroup,
sipCommonConfigRetryExtMethodGroup, sipCommonConfigRetryExtMethodGroup,
sipCommonStatsRetryExtMethodsGroup, and sipCommonStatsRetryExtMethodsGroup, and
sipCommonConfigExpiresGroup. The references to these sipCommonConfigExpiresGroup. The references to these object-
object-groups as optional in the module-compliance was updated groups as optional in the module-compliance was updated
accordingly. accordingly.
* GROUP clause for sipCommonStatsRetryGroup in module-compliance * GROUP clause for sipCommonStatsRetryGroup in module-compliance
was udpated to no longer state any dependency on was udpated to no longer state any dependency on
sipCommonConfigRetryGroup (now removed). sipCommonConfigRetryGroup (now removed).
* New OBJECT clauses were added to the module-compliance to * New OBJECT clauses were added to the module-compliance to
formalize MIN-ACCESS read-only for objects in formalize MIN-ACCESS read-only for objects in
sipCommonCfgTimerTable. sipCommonCfgTimerTable.
* sipCommonConfigGroup udpated with new objects (sipOptionTag, * sipCommonConfigGroup udpated with new objects (sipOptionTag,
sipOptionTagHeaderField, sipMethodName), removed objects sipOptionTagHeaderField, sipMethodName), removed objects
(sipTransportSnd, sipPortStatus, sipUriSupported, (sipTransportSnd, sipPortStatus, sipUriSupported,
skipping to change at page 78, line 46 skipping to change at page 82, line 46
(sipStatsRetries) and removed objects (sipStatsRetryInvites, (sipStatsRetries) and removed objects (sipStatsRetryInvites,
sipStatsRetryByes, sipStatsRetryCancels, sipStatsRetryByes, sipStatsRetryCancels,
sipStatsRetryRegisters, sipStatsRetryOptions). sipStatsRetryRegisters, sipStatsRetryOptions).
o SIP-SERVER-MIB o SIP-SERVER-MIB
* Module description of various SIP entities enhanced. * Module description of various SIP entities enhanced.
* sipServerStats 'placeholder' IOD removed. No objects were ever * sipServerStats 'placeholder' IOD removed. No objects were ever
defined under that subtree. defined under that subtree.
* Removed the following objects from sipProxyCfgTable: * Removed the following objects from sipProxyCfgTable:
sipRequestMaxExpires, sipProxySendsCancel, sipRequestMaxExpires, sipProxySendsCancel,
sipProxyForwardAll1xx, sipProxyProvideAlternatives, and sipProxyForwardAll1xx, sipProxyProvideAlternatives, and
sipProxyNonceLifeTime. sipProxyConfigGroup updated sipProxyNonceLifeTime. sipProxyConfigGroup updated accordingly.
accordingly.
* sipProxyStatefulness MAX-ACCESS changed to read-only. * sipProxyStatefulness MAX-ACCESS changed to read-only.
* DEFVAL removed from sipRegMaxContactExpiryDuration. * DEFVAL removed from sipRegMaxContactExpiryDuration.
* sipContactRetryAfter removed from sipContactTable. * sipContactRetryAfter removed from sipContactTable.
* sipUser* and sipContact* objects were moved from * sipUser* and sipContact* objects were moved from
sipRegistrarConfigGroup to a new object-group: sipRegistrarConfigGroup to a new object-group:
sipRegistrarUsersGroup. The new group was made an optional sipRegistrarUsersGroup. The new group was made an optional
group in the MODULE-COMPLIANCE. group in the MODULE-COMPLIANCE.
o SIP-UA-MIB o SIP-UA-MIB
* SipEntityRole imported from SIP-TC module and used as the * SipEntityRole imported from SIP-TC module and used as the
skipping to change at page 79, line 26 skipping to change at page 83, line 26
* DEFVAL { ipv4 } removed from sipUACfgServerAddrType. * DEFVAL { ipv4 } removed from sipUACfgServerAddrType.
o SIP-TC o SIP-TC
* New textual conventions: SipEntityRole, SipOptionTagHeaders, * New textual conventions: SipEntityRole, SipOptionTagHeaders,
and SipMethodIdentifier added. and SipMethodIdentifier added.
Changes from draft-ietf-sip-mib-06 Changes from draft-ietf-sip-mib-06
o General o General
* Minor editorial changes in the Textual Conventions section. * Minor editorial changes in the Textual Conventions section.
o SIP-COMMON-MIB o SIP-COMMON-MIB
* sipStatusCodeValue SYNTAX changed from INTEGER to Unsigned32. * sipStatusCodeValue SYNTAX changed from INTEGER to Unsigned32.
* Optional sipCommonNotifObjectsGroup explicitly added to * Optional sipCommonNotifObjectsGroup explicitly added to MODULE-
MODULE-COMPLIANCE. COMPLIANCE.
* Removed OBJECT refinement for sipStatusCodeRowStatus added to * Removed OBJECT refinement for sipStatusCodeRowStatus added to
compliance in previous revision. SMIC MIB compiler issues compliance in previous revision. SMIC MIB compiler issues
required it to be commented out. Instead, simply removed it. required it to be commented out. Instead, simply removed it.
o SIP-SERVER-MIB o SIP-SERVER-MIB
* Removed OID placeholders: sipRedirCfg, sipRedirStats. * Removed OID placeholders: sipRedirCfg, sipRedirStats. sipRegCfg
sipRegCfg and sipRegStats OID values subsequently changed as a and sipRegStats OID values subsequently changed as a result.
result.
o SIP-UA-MIB o SIP-UA-MIB
* Removed OBJECT refinement for sipUACfgSipServerStatus added to * Removed OBJECT refinement for sipUACfgSipServerStatus added to
compliance in previous revision. SMIC MIB compiler issues compliance in previous revision. SMIC MIB compiler issues
required it to be commented out. Instead, simply removed it. required it to be commented out. Instead, simply removed it.
Changes from draft-ietf-sip-mib-05 Changes from draft-ietf-sip-mib-05
o Front paper/Back paper and General changes o Front paper/Back paper and General changes
* Removed all references and special handling of SIP INFO method * Removed all references and special handling of SIP INFO method
Removed references and objects specific to RFC 2976: INFO will Removed references and objects specific to RFC 2976: INFO will
be treated as any SIP extension method. be treated as any SIP extension method.
skipping to change at page 80, line 29 skipping to change at page 84, line 29
notifications: sipStatusCodeThreshExceededOutNotif and notifications: sipStatusCodeThreshExceededOutNotif and
sipStatusCodeThreshExceededInNotif. sipStatusCodeThreshExceededInNotif.
* Re-arranged the enumerated value of sipServiceOperStatus; * Re-arranged the enumerated value of sipServiceOperStatus;
making 'unknown' the first value. Added some words to the making 'unknown' the first value. Added some words to the
DESCRIPTION of that object stating the values are not based on DESCRIPTION of that object stating the values are not based on
anything in the SIP standard. anything in the SIP standard.
* Clarified rules for capitalization of sipExtMethodName. * Clarified rules for capitalization of sipExtMethodName.
* All counters in the MIB are consistent with respect to * All counters in the MIB are consistent with respect to
resetting to zero. No counters can be reset to zero. Entries resetting to zero. No counters can be reset to zero. Entries
in sipStatusCodesTable can simply be created or destroyed - no in sipStatusCodesTable can simply be created or destroyed - no
ability to set to 'notInService' where there was the ability to set to 'notInService' where there was the question/
question/possibility of resetting the counters to zero. possibility of resetting the counters to zero.
sipStatsExtMethodTable no longer has its own RowStatus object, sipStatsExtMethodTable no longer has its own RowStatus object,
so it too can no longer be set to 'notInService' where there so it too can no longer be set to 'notInService' where there
was the question/possibility of resetting the counters to zero. was the question/possibility of resetting the counters to zero.
sipStatsExtMethodTable rows are augmentations of sipStatsExtMethodTable rows are augmentations of
sipExtMethodSupportedEntry. sipExtMethodSupportedEntry.
* OBJECT refinement for sipStatusCodeRowStatus added to * OBJECT refinement for sipStatusCodeRowStatus added to
compliance. compliance.
* Clarified the relationship between * Clarified the relationship between
sipCommonStatusCodeNotifEmitMode and sipCommonStatusCodeNotifEmitMode and
sipCommonStatusCodeNotifSend. sipCommonStatusCodeNotifSend.
skipping to change at page 84, line 29 skipping to change at page 88, line 29
Specifically, noting that not all values of the object are Specifically, noting that not all values of the object are
applicable to all transaction types. applicable to all transaction types.
* sipTransTo, sipTransFrom, sipTransCallId, and sipTransCSeq all * sipTransTo, sipTransFrom, sipTransCallId, and sipTransCSeq all
had clarifying changes to their DESCRIPTIONs. Specifically, had clarifying changes to their DESCRIPTIONs. Specifically,
the header name will be part of the object value and example the header name will be part of the object value and example
values were given. values were given.
* Minor grammatical change to the DESCRIPTION of * Minor grammatical change to the DESCRIPTION of
sipOtherStatsEntry. sipOtherStatsEntry.
* sipCommonStatusCodeIns and sipCommonStatusCodeOuts objects were * sipCommonStatusCodeIns and sipCommonStatusCodeOuts objects were
added to the varbind of sipStatusCodeNotif. added to the varbind of sipStatusCodeNotif.
* Appropriate changes were made to sipCommonStatsGroup * Appropriate changes were made to sipCommonStatsGroup OBJECT-
OBJECT-GROUP based on objects being added and/or removed from GROUP based on objects being added and/or removed from the MIB.
the MIB.
o SIP-SERVER-MIB o SIP-SERVER-MIB
* CONTACT-INFO "SIP MIB email" changed to sip@ietf.org * CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
* The statement "Unlike a Proxy server it does not initiate * The statement "Unlike a Proxy server it does not initiate
requests." was removed from where a Redirect Server is defined requests." was removed from where a Redirect Server is defined
in the MIB's DESCRIPTION. in the MIB's DESCRIPTION.
* sipServerMIBNotifs OID removed. No notifications were ever * sipServerMIBNotifs OID removed. No notifications were ever
defined under this subtree. defined under this subtree.
* Clarifying text added to all of the Table DESCRIPTIONS stating * Clarifying text added to all of the Table DESCRIPTIONS stating
that the value of applIndex used in this MIB corresponds to the that the value of applIndex used in this MIB corresponds to the
value of applIndex used in the SIP-COMMON-MIB. value of applIndex used in the SIP-COMMON-MIB.
skipping to change at page 86, line 10 skipping to change at page 90, line 10
o SIP-UA-MIB o SIP-UA-MIB
* IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex. * IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex.
* sipUACfgSipServerEntry was referencing the wrong auxiliary * sipUACfgSipServerEntry was referencing the wrong auxiliary
object and listing that object in the conformance section. object and listing that object in the conformance section.
* sipUACfgSipServerEntry listed sipUACfgSipServerStatus when it * sipUACfgSipServerEntry listed sipUACfgSipServerStatus when it
should have been listing sipUACfgSipServerAddrStatus. should have been listing sipUACfgSipServerAddrStatus.
* SIP-UA-MIB IMPORTed Counter32, but never used it. Removed the * SIP-UA-MIB IMPORTed Counter32, but never used it. Removed the
IMPORT of Counter32. IMPORT of Counter32.
9. IANA Considerations 12. Normative References
9.1 Registration of Numeric Identifiers for SIP methods
The SIP specification RFC 3261 [RFC3261] section 27.4 establishes the
sub-registries for SIP Methods and Response Codes under
http://www.iana.org/assignments/sip-parameters. This document
augments the existing sub-registry for SIP Methods to include a
unique numeric method identifier for each registered SIP method.
The SIP-TC and SIP-COMMON-MIB modules require that a unique numeric
identifier be assigned by IANA for each SIP Method registered in the
above registry. In the SIP-TC module, we have indeed defined a
textual-convention to represent a SIP method by a unique numeric
identifier, SipMethodIdentifier. In the SIP-COMMON-MIB module, a
number of MIB objects use this textual-convention where it is
sufficient or more effective to refer to a method by a number rather
than by a character string. For example, the SIP methods supported
by a SIP entity can be found in the sipSupportedMethodTable, a table
indexed by an object of type SipMethodIdentifier. The mapping of
method identifiers to method names - as assigned by IANA can then be
represented in the SIP MIB by the sipSupportedMethodTable in the
SIP-COMMON-MIB as follows:
+-------------------------+------------------------+
| sipMethodSupportedIndex | sipMethodSupportedName |
+-------------------------+------------------------+
| 1 | "ACK" |
| 2 | "BYE" |
| 3 | "CANCEL" |
| 5 | "INVITE" |
| 8 | "OPTIONS" |
+-------------------------+------------------------+
The following section requests the assignment of a unique numeric
identifier for all the SIP methods already registered. For new SIP
method, their registration will automatically trigger the assignment
of a new numeric method identifier. In other words, this
sub-registration is completely linked with the existing procedures to
register SIP methods as specified in RFC 3261 [RFC3261] and RFC 3427
[RFC3427].
This document modifies the IANA registry for SIP Method names by
adding a new column called "Method Identifiers", as shown in the
table below:
+-----------+-----------+--------------------+
| Methods | Reference | Method Identifiers |
+-----------+-----------+--------------------+
| ACK | [RFC3261] | 1 |
| BYE | [RFC3261] | 2 |
| CANCEL | [RFC3261] | 3 |
| INFO | [RFC2976] | 4 |
| INVITE | [RFC3261] | 5 |
| MESSAGE | [RFC3428] | 6 |
| NOTIFY | [RFC3265] | 7 |
| OPTIONS | [RFC3261] | 8 |
| PRACK | [RFC3262] | 9 |
| PUBLISH | [RFC3903] | 10 |
| REFER | [RFC3515] | 11 |
| REGISTER | [RFC3261] | 12 |
| SUBSCRIBE | [RFC3265] | 13 |
| UPDATE | [RFC3311] | 14 |
+-----------+-----------+--------------------+
Note that the response code table is not affected by this update and
the procedures defined in RFC 3261 [RFC3261] section 27.4 must be
followed.
In addition, this document modifies the procedures for registering a
new SIP method. When a new SIP Method is added to the SIP Method
names registry, this document instructs IANA to assign the next whole
number in sequence to the newly registered method. If multiple
method names are registered at the same time, the RFC with the lowest
number should be assigned its number first. If more than one method
is assigned in the same document, the method name alphabetically
first should be registered first.
9.2 IANA-assigned OBJECT IDENTIFIER values for the SIP MIB modules
The MIB modules defined in this document use the following
IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers
registry:
+--------------+-------------------------+
| Descriptor | OBJECT IDENTIFIER value |
+--------------+-------------------------+
| sipTC | { mib-2 XXX1 } |
| sipCommonMIB | { mib-2 XXX2 } |
| sipUAMIB | { mib-2 XXX3 } |
| sipServerMIB | { mib-2 XXX4} |
+--------------+-------------------------+
-- RFC Ed:(note to be removed prior to publication): the IANA is
requested to assign 4 values in the SMI Numbers registry for "XXX1",
"XXX2", "XXX3", and "XXX4", all under the 'mib-2' sub-tree and to
record the assignments in the SMI Numbers registry. When the
assignments have been made, the RFC Editor is asked to replace "XXX1"
through "XXX4" (here and in the 4 MIB modules) with the corresponding
assigned value and to remove this note.
10. Security Considerations
There are a number of management objects defined in the
SIP-COMMON-MIB MIB module with a MAX-ACCESS clause of read-write
and/or read-create. Such objects may be considered sensitive or
vulnerable in some network environments. The support for SET
operations in a non-secure environment without proper protection can
have a negative effect on network operations.
The following read-create object in SIP-COMMON-MIB is used to
configure the status code statistics that will be monitored by the
SIP entity:
sipStatusCodeRowStatus:
if this object is SET maliciously, it may result in an over
allocation of resources in a system for the purpose of
accumulating and maintaining statistics.
The following read-write objects in SIP-COMMON-MIB are used to
configure the behavior of certain SNMP notifications potentially
generated by a SIP entity:
sipStatusCodeNotifSend, sipStatusCodeNotifEmitMode,
sipStatusCodeNotifThresh, sipStatusCodeNotifInterval,
sipServiceNotifEnable:
If these objects are SET maliciously, it may result in a system
and/or network performance impact due to the generation of SNMP
notifications.
Some of the readable objects in the MIB modules (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP.
The following object values may contain private or confidential
customer information like first name, last name, customer
identification, location, company affiliation, the time the
information was updated, etc.
sipContactDisplayName, sipContactURI, sipContactLastUpdated and
sipOrganization.
The sipCommonCfgTable table contains some objects that may help
attackers gain knowledge about the status and operations of the SIP
service. In particular, the object value of sipServiceOperStatus may
indicate that the SIP entity is in congested state and may lead
attackers to build additional service attacks to overload the system.
The sipEntityType object indicates the type of SIP entity and the
sipMethodSupportedTable table contains in the SIP-COMMON-MIB MIB
module list of SIP methods supported by each entity in the system.
Gaining access to this information may allow attackers to build
method specific attacks or use unsupported methods to create denial
of service attack scenarios.
In the SIP-UA-MIB MIB module, the sipUACfgServerTable contains the
address of the SIP servers providing services to the UA and obtaining
this information may disclose some private or sensitive information
about the SIP service usage.
In the SIP-SERVER-MIB MIB module, the sipProxyAuthMethod object
defines the authentication methods supported by the server and may be
used to build specific denial of service attackers targeted at the
security mechanisms employed by the SIP entity.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network 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 GET/SET (read/change/create/delete) the objects
in this set of MIB modules.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see RFC 3410 [RFC3410]), including
full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
11. Contributor Acknowledgments
We wish to thank the members of the IETF SIP and SIPPING working
groups, and the SIP-MIB Design team for their comments and
suggestions. Detailed comments were provided by Tom Taylor, Kavitha
Patchayappan, Dan Romascanu, Cullen Jennins, Orit Levin, AC
Mahendran, Mary Barnes, Rohan Mahy, Bob Penfield, Charles Eckel and
Dean Willis.
12. References
12.1 Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
"Introduction and Applicability Statements for A., Peterson, J., Sparks, R., Handley, M., and E.
Internet-Standard Management Framework", RFC 3410, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
December 2002. June 2002.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of "Introduction and Applicability Statements for Internet-
Management Information Version 2 (SMIv2)", STD 58, Standard Management Framework", RFC 3410, December 2002.
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual Schoenwaelder, Ed., "Structure of Management Information
Conventions for SMIv2", STD 58, RFC 2579, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC2788] Freed, N. and S. Kille, "Network Services Monitoring MIB", [RFC2788] Freed, N. and S. Kille, "Network Services Monitoring MIB",
RFC 2788, March 2000. RFC 2788, March 2000.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
A., Peterson, J., Sparks, R., Handley, M. and E. Schooler, Architecture for Describing Simple Network Management
"SIP: Session Initiation Protocol", RFC 3261, June 2002. Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002.
[RFC3291] Daniele, M., Haberman, B., Routhier, S. and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 3291, May 2002. Addresses", RFC 4001, February 2005.
[RFC3427] Mankin, A., Bradner, S., Mahy, R., Willis, D., Ott, J. and
B. Rosen, "Change Process for the Session Initiation
Protocol (SIP)", BCP 67, RFC 3427, December 2002.
[RFC3515] Sparks, R., "The Session Initiation Protocol (SIP) Refer
Method", RFC 3515, April 2003.
12.2 Informational References
[RFC2368] Hoffman, P., Masinter, L. and J. Zawinski, "The mailto URL
scheme", RFC 2368, July 1998.
[RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396,
August 1998.
[RFC2543] Handley, M., Schulzrinne, H., Schooler, E. and J.
Rosenberg, "SIP: Session Initiation Protocol", RFC 2543,
March 1999.
[RFC2976] Donovan, S., "The SIP INFO Method", RFC 2976, October
2000.
[RFC3262] Rosenberg, J. and H. Schulzrinne, "Reliability of
Provisional Responses in Session Initiation Protocol
(SIP)", RFC 3262, June 2002.
[RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific
Event Notification", RFC 3265, June 2002.
[RFC3311] Rosenberg, J., "The Session Initiation Protocol (SIP)
UPDATE Method", RFC 3311, October 2002.
[RFC3428] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C.
and D. Gurle, "Session Initiation Protocol (SIP) Extension
for Instant Messaging", RFC 3428, December 2002.
[RFC3903] Niemi, A., "Session Initiation Protocol (SIP) Extension
for Event State Publication", RFC 3903, October 2004.
Authors' Addresses Authors' 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 Research Triangle Park, NC 27709
US US
Phone: +1 919 392 2029 Phone: +1 919 392 2029
Email: klingle@cisco.com Email: klingle@cisco.com
Jean-Francois Mule Jean-Francois Mule
CableLabs CableLabs
858 Coal Creek Circle 858 Coal Creek Circle
Louisville, CO 80027 Louisville, CO 80027
US US
Phone: +1 303 661 9100 Phone: +1 303 661 9100
Email: jfm@cablelabs.com Email: jf.mule@cablelabs.com
Joon Maeng Joon Maeng
5612 Sedona Drive 5612 Sedona Drive
Austin, TX 78759 Austin, TX 78759
US US
Phone: +1 512 418 0590 Phone: +1 512 418 0590
Email: jmaeng@austin.rr.com Email: jmaeng@austin.rr.com
Dave Walker Dave Walker
Email: drwalker@rogers.com Email: drwalker@rogers.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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 Rights or other rights that might be claimed to Intellectual Property Rights 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; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 93, line 29 skipping to change at page 92, line 34
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
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 that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 194 change blocks. 
724 lines changed or deleted 664 lines changed or added

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