draft-ietf-sip-mib-08.txt   draft-ietf-sip-mib-09.txt 
SIP WG K. Lingle
SIP Working Group K. Lingle
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: January 14, 2005 J. Maeng Expires: August 1, 2005 J. Mule
CableLabs
J. Maeng
D. Walker D. Walker
July 16, 2004 January 28, 2005
Management Information Base for Session Initiation Protocol (SIP) Management Information Base for Session Initiation Protocol (SIP)
draft-ietf-sip-mib-08.txt draft-ietf-sip-mib-09.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable This document is an Internet-Draft and is subject to all provisions
patent or other IPR claims of which I am aware have been disclosed, of Section 3 of RFC 3667. By submitting this Internet-Draft, each
and any of which I become aware will be disclosed, in accordance with author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with
RFC 3668. 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-Drafts. Internet-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 January 14, 2005. This Internet-Draft will expire on August 1, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005).
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 servers and Registrars. 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 SIP MIB . . . . . . . . . . . . . . . . . . . . 3
5.1 Textual Conventions . . . . . . . . . . . . . . . . . . . 5 5.1 Textual Conventions . . . . . . . . . . . . . . . . . . . 5
5.2 Relationship to the Network Services MIB . . . . . . . . . 6 5.2 Relationship to the Network Services MIB . . . . . . . . . 6
6. Accommodating SIP Extension Methods . . . . . . . . . . . . . 9 6. Accommodating SIP Extension Methods . . . . . . . . . . . . 9
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . 10
7.1 SIP Textual Conventions . . . . . . . . . . . . . . . . . 9 7.1 SIP Textual Conventions . . . . . . . . . . . . . . . . . 10
7.2 SIP Common MIB Module . . . . . . . . . . . . . . . . . . 13 7.2 SIP Common MIB Module . . . . . . . . . . . . . . . . . . 13
7.3 SIP User Agent MIB Module . . . . . . . . . . . . . . . . 54 7.3 SIP User Agent MIB Module . . . . . . . . . . . . . . . . 52
7.4 SIP Server (Registrar & Proxy/Redirect Server) MIB 7.4 SIP Server MIB Module (Proxy, Redirect and Registrar
Module . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Servers) . . . . . . . . . . . . . . . . . . . . . . . . . 56
8. Changes from Previous Draft Revisions . . . . . . . . . . . . 77 8. Changes from Previous Draft Revisions . . . . . . . . . . . 74
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 87 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . 86
9.1 Registration of Numeric Identifiers for SIP methods . . . 86
9.2 IANA-assigned OBJECT IDENTIFIER values for the SIP MIB
modules . . . . . . . . . . . . . . . . . . . . . . . . . 88
10. Security Considerations . . . . . . . . . . . . . . . . . . 88 10. Security Considerations . . . . . . . . . . . . . . . . . . 88
11. Contributor Acknowledgments . . . . . . . . . . . . . . . . 91 11. Contributor Acknowledgments . . . . . . . . . . . . . . . . 90
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 91 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 90
12.1 Normative References . . . . . . . . . . . . . . . . . . . . 91 12.1 Normative References . . . . . . . . . . . . . . . . . . 90
12.2 Informational References . . . . . . . . . . . . . . . . . . 92 12.2 Informational References . . . . . . . . . . . . . . . . 91
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 92
Intellectual Property and Copyright Statements . . . . . . . . 93 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 [1]. 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)
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 servers and Registrars. The managed objects Agents, Proxy, Redirect and Registrar servers. The managed objects
defined in this document are intended to provide basic SIP protocol defined in this document are intended to provide basic SIP protocol
management for SIP entities. The management of application-specific management for SIP entities. The management of application-specific
or service-specific SIP configuration is out of scope. or service-specific SIP configuration is out of scope.
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [2]. Managed objects are accessed via a virtual information RFC 3410 [RFC3410].
store, termed the Management Information Base or MIB. MIB objects
are generally accessed through the Simple Network Management Protocol Managed objects are accessed via a virtual information store, termed
(SNMP). Objects in the MIB are defined using the mechanisms defined the Management Information Base or MIB. MIB objects are generally
in the Structure of Management Information (SMI). This memo accessed through the Simple Network Management Protocol (SNMP).
specifies a MIB module that is compliant to the SMIv2, which is Objects in the MIB are defined using the mechanisms defined in the
described in STD 58, comprised of RFC 2578 [3], RFC 2579 [4], and Structure of Management Information (SMI). This memo specifies a set
RFC 2580 [5]. 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
2580 [RFC2580].
4. Overview 4. Overview
The Session Initiation Protocol (SIP) RFC 3261 [7] is an application- The Session Initiation Protocol (SIP) RFC 3261 [RFC3261] is an
layer control (signaling) protocol for creating, modifying, and application-layer control (signaling) protocol for creating,
terminating sessions with one or more participants. These sessions modifying, and terminating sessions with one or more participants.
include Internet telephone calls, multimedia distribution, and These sessions include Internet telephone calls, multimedia
multimedia conferences. This MIB provides some managed objects for distribution, and multimedia conferences. This MIB provides some
SIP entities defined in RFC 3261 - User Agent, Proxy/Redirect Server managed objects for SIP entities defined in RFC 3261 [RFC3261] - User
and Registrar. It is provided as a base for the work within the Agents, and Proxy, Redirect and Registrar servers: it is intended to
working group to define a MIB. This MIB is intended to provide provide management of the basic SIP entities. It provides for
management of the basic SIP entities. It provides for monitoring of monitoring of status and protocol statistics, as well as for
status and protocol statistics, as well as for configuration of SIP configuration of SIP entities.
entities.
5. Structure of SIP MIB 5. Structure of SIP MIB
This memo specifies four MIB modules. They are SIP-COMMON-MIB, SIP- This memo specifies four MIB modules. They are SIP-COMMON-MIB,
SERVER-MIB, SIP-UA-MIB and SIP-TC. SIP-COMMON-MIB contains common SIP-SERVER-MIB, SIP-UA-MIB and SIP-TC. SIP-COMMON-MIB contains
objects used in all the SIP entities. SIP-SERVER-MIB contains common objects used in all the SIP entities. SIP-SERVER-MIB contains
objects specific to Registrars, Proxies/Redirect Servers, and objects specific to Proxy, Redirect and Registrar servers, and
SIP-UA-MIB includes objects specific to User Agents. SIP-TC defines SIP-UA-MIB includes objects specific to User Agents. SIP-TC defines
the textual conventions used throughout MIB modules. The MIB Modules the textual conventions used throughout MIB modules. The MIB Modules
contain following groups of objects: contain following groups of objects:
SIP-COMMON-MIB: 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 SIP protocol objects common to all SIP entities including the SIP protocol
version, operational and administrative status, SIP version, the type of SIP entity (UA, proxy, redirect, registrar
organization name, max number of SIP dialogs an entity can server), the operational and administrative status, the SIP
manage, etc. organization name, the maximum number of SIP transactions an
entity can manage, etc.
* sipCommonCfgTimer: This object group defines timer * sipCommonCfgTimer: This object group defines timer
configuration objects applicable to SIP user agent and SIP configuration objects applicable to SIP user agent and stateful
stateful proxy entities. SIP proxy entities.
* sipCommonStatsSummary: This object group defines a table * sipCommonStatsSummary: This object group defines a table
containing the summary statistics objects applicable to all SIP containing the summary statistics objects applicable to all SIP
entities, including the total number of SIP requests & entities, including the total number of all SIP requests and
responses in/out, total number of transactions, etc. responses in/out, and the total number of transactions.
* sipCommonStatsMethod: This object group defines a table * sipCommonStatsMethod: This object group defines a table
containing the per method statistics objects applicable to all containing the SIP method statistics objects applicable to all
SIP entities, including the total number of SIP requests for SIP entities, including the number outbound and inbound
the Invite, Ack, Bye, Cancel, Options and Register methods. requests on a per method basis. Retransmissions, where
Retransmissions, where appropriate, are also included in these appropriate, are also included in these statistics.
statistics.
* sipCommonStatusCode: This object group defines a table * sipCommonStatusCode: This object group defines a table
indicating the number of SIP responses in/out per class of indicating the number of SIP responses (in and out) that the
response (1xx, 2xx, etc.) SIP entity has been requested to monitor on a per method basis
(100, 200, 302, etc.).
* sipCommonStatsTrans: This object group defines a table * sipCommonStatsTrans: This object group defines a table
containing a gauge reflecting the number of transactions containing a gauge reflecting the number of transactions
currently awaiting definitive responses by the managed SIP currently awaiting definitive responses by the managed SIP
entity. entity.
* sipCommonStatsRetry: This object group defines statistic * sipCommonStatsRetry: This object group defines statistic
objects indicating the number of retries sent on a per method objects indicating the number of retransmissions sent on a per
basis. method basis.
* sipCommonStatsOther: This object group defines additional * sipCommonStatsOther: This object group defines additional
statistic objects including a counter of the number of SIP statistic objects including the number of SIP requests received
requests received with unsupported URIs. with unsupported URIs, the number of requests received with
* sipCommonNotifObjects: This object group defines unsupported SIP methods, and the number of discarded messages.
accessible-for-notify objects that are related to the SNMP * sipCommonNotifObjects: This object group defines objects
accessible only via a notification (MAX ACCESS clause of
accessible-for-notify): they are related to the SNMP
notifications defined in this MIB module. notifications defined in this MIB module.
The SIP-COMMON-MIB also contains notifications, including: The SIP-COMMON-MIB also contains notifications, including:
o sipStatusCodeNotif: indicates that a specific status code has been o sipStatusCodeNotif: indicates that a specific status code has been
sent or received by the system. sent or received by the system.
o sipStatusCodeThreshExceededNotif: indicates that a specific status o sipStatusCodeThreshExceededNotif: indicates that a specific status
code has been sent or received by the system enough to exceed the code has been sent or received by the system enough to exceed the
configured threshold. configured threshold.
SIP-SERVER-MIB: Groups of objects for Registrars and Proxy/Redirect SIP-SERVER-MIB: Groups of objects for SIP Proxy, Redirect and
Servers Registrar servers
o sipServerMIBObjects o sipServerMIBObjects
* sipServerCfg: This object group defines common server * sipServerCfg: This object group defines common server
configuration objects including the SIP server host address. configuration objects including the SIP server host address.
* sipProxyCfg: This object group defines Proxy Server * sipProxyCfg: This object group defines configuration objects
configuration objects including the maximum duration in the for SIP Proxy servers including the proxy mode of operation
Expires header, the proxy mode of operation (stateless, (stateless, stateful, call stateful), the proxy authentication
stateful, call stateful), the cancellation of outstanding method(s) and realm, etc.
branch requests
* sipProxyStats: This object group defines a table containing the * sipProxyStats: This object group defines a table containing the
statistics objects applicable to all SIP Proxy Servers. It statistics objects applicable to SIP proxy servers. It
includes the number of occurrences of unsupported options being includes the number of occurrences of unsupported options being
specified in received Proxy-Require headers. specified in received Proxy-Require headers.
* sipRegCfg: This object group defines common registrar * sipRegCfg: This object group defines common configuration
configuration objects including the ability for a registrar to objects for SIP Registrar servers including the ability to
accept third-party registration, the maximum expiry that may be accept third-party registrations, the maximum registration
requested by UAs, the maximum number of users, currently expiry that may be requested by user agents, the maximum number
registered users, etc. of users the registrar can support, the number of currently
* sipRegStats: This object group contains the summary statistics registered users, per contact registration information, etc.
objects for Registrar servers, including the number of REGISTER * sipRegStats: This object group contains summary statistics
requests that have been accepted or rejected. objects for SIP Registrar servers, precisely, the number of
REGISTER requests that have been accepted or rejected.
SIP-UA-MIB: Group of objects for User Agents. SIP-UA-MIB: Group of objects for SIP User Agents.
o sipUAMIBObjects o sipUAMIBObjects
* sipUACfgServer: This group specifies SIP server configuration * sipUACfgServer: This object group specifies SIP server
objects applicable to SIP user agents including the Internet configuration objects applicable to SIP user agents including
address of the SIP Server to use to register, proxy or redirect the Internet address of the SIP Server to use to register,
calls. proxy or redirect calls.
To conform with this specification, an SNMP agent MUST implement To conform with this specification, an SNMP agent MUST implement the
SIP-TC, plus the SIP-COMMON-MIB and one of the SIP entity-type- SIP-TC MIB module, plus the SIP-COMMON-MIB module and one of the SIP
specific MIB modules (SIP-SERVER-MIB or SIP-UA-MIB) as applicable for entity-type- specific MIB modules (SIP-SERVER-MIB or SIP-UA-MIB) as
each instance of a SIP entity being managed. If a device has more applicable for each instance of a SIP entity being managed. If a
than one SIP entity or multiple instances of the same entity type, it device has more than one SIP entity or multiple instances of the same
MUST implement multiple SIP modules. Section 4.2 describes handling entity type, it MUST implement multiple SIP modules. Section 4.2
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 SipMethodIdentifier are used as Textual
Conventions in this document. These Textual Conventions have NO Conventions in this document. They are defined in the SIP-TC MIB
effect on either the syntax or the semantics of any managed object. module.
Objects defined using these conventions are always encoded by means
of the rules that define their primitive type. Hence, no changes to
the SMI or the SNMP are necessary to accommodate these Textual
Conventions. They are adopted merely for the convenience of readers.
5.2 Relationship to the Network Services MIB 5.2 Relationship to the Network Services MIB
There is a requirement to be able to support multiple instances of In the design of the SIP MIB, the authors considered the following
various SIP MIB modules in the context of a single system having a requirement: the SIP MIB must allow a single system with a single
single SNMP agent. SNMP agent to support multiple instances of various SIP MIB modules.
This requirement is met by using the framework provided by the
Network Services Monitoring MIB, NETWORK-SERVICES-MIB, RFC 2788
[RFC2788].
This requirement is solved by using the framework provided by the A device implementing the SIP MIB MUST support the
NETWORK-SERVICES-MIB, RFC 2788 [6]. A device implementing the SIP NETWORK-SERVICES-MIB and, at a minimum, it MUST support the index and
MIB MUST support the NETWORK-SERVICES-MIB and, at a minimum, it MUST name objects (applIndex and applName) in the application table
support the applIndex and applName objects in applTable. The (applTable). In order to allow each instance of a SIP entity to be
following applName conventions will be adopted: managed as a separate network service application, a naming
o for a SIP Proxy entity, applName MUST be equal to "sip_proxy" convention SHOULD be used to make the application name unique. For
o for a SIP Registrar entity, applName MUST be equal to example, if a system is running 2 SIP UAs that need to be managed as
"sip_registrar" 2 separate SIP entities, by convention, the application names used in
o for a SIP User Agent entity, applName MUST be equal to "sip_ua" the Network Services Monitoring MIB application table should be
"sip_ua1" and "sip_ua2". This convention allows each instance to
have its own row in the application table (applTable).
It is therefore RECOMMENDED to adopt the following application name
conventions:
o for a SIP Proxy entity, the applName value SHOULD be equal to a
character string starting with "sip_proxy" followed by a unique
application instance identifier, for example, "sip_proxy1",
"sip_proxy17"
o for a SIP Registrar entity, the applName value SHOULD be equal to
a character string starting with "sip_registrar" followed by a
unique application instance identifier, for example,
"sip_registrar1", "sip_registrar2"
o for a SIP User Agent entity, the applName value SHOULD be equal to
a character string starting with "sip_ua" followed by a unique
application instance identifier, for example, "sip_ua1", "sip_ua2"
o for any combination of Proxy, Registrar, or Redirect Server being o for any combination of Proxy, Registrar, or Redirect Server being
managed as a single aggregate entity, the applName for the managed as a single aggregate entity, the applName value for the
combined server entity MUST reflect the appropriate combination. combined server entity MUST reflect the appropriate combination
In order to faciliate consistent agent behavior and management followed by a unique application instance identifier. In order to
application expectations, the following order of names is facilitate consistent agent behavior and management application
RECOMMENDED: expectations, the following order of names is RECOMMENDED:
* if Proxy exists, list first. * if Proxy exists, list first.
* if Proxy & Redirect exists, list Redirect second. * if Proxy and Redirect exists, list Redirect second.
* if Registrar exists, always list last. * if Registrar exists, always list last.
For example "sip_proxy", "sip_proxy_registrar", For example "sip_proxy1", "sip_proxy_registrar1",
"sip_proxy_redirect", "sip_proxy_redirect_registrar", or "sip_proxy_redirect5", "sip_proxy_redirect_registrar2", or
"sip_registrar". "sip_registrar1".
o Note: the value of the network service application index
(applIndex) may be different from the instance identifier used in
the system (the applIndex is dynamically created and the value
assigned by the SNMP agent at the creation of the table entry
whereas the value of the instance identifier to be used in the
application name is provided as part of the application name
applName by the system administrator or configuration files of the
SIP entity). This note is illustrated in the first example
provided below.
The SNMP agent MAY support any combination of the other attributes in Finally, the SNMP agent MAY support any combination of the other
applTable. If the following objects are supported, the object values attributes in applTable. If supported, the following objects SHOULD
SHOULD be populated as follows: have values populated as follows:
o applVersion: version of the SIP application, o applVersion: version of the SIP application,
o applUptime: value MUST be identical to sipServiceStartTime defined o applUptime: the value of applUptime MUST be identical to the value
in the SIP-COMMON-MIB module, of sipServiceStartTime defined in the SIP-COMMON-MIB module,
o applOperStatus: value SHOULD reflect the operational status o applOperStatus: the value of applOperStatus SHOULD reflect the
defined in sipServiceOperStatus, at least by means of a mapping, operational status of sipServiceOperStatus, at least by means of a
o applLastChange: value MUST be identical to sipServiceLastChange mapping,
defined in the SIP-COMMON module. o applLastChange: the value of applLastChange MUST be identical to
the value of sipServiceLastChange defined in the SIP-COMMON
Note: There are a number of other objects in the applTable. They are module.
not included for the sake of brevity and for the fact that they do
not enhance the concept being presented.
Example 1: A number of other objects are defined as part of the applTable. They
are not included for the sake of brevity and due to the fact that
they do not enhance the concept being presented.
The tables below illustrate how a system acting as both Proxy and Example 1: The tables below illustrate how a system acting as both
Registrar server might be configured to maintain separate SIP- Proxy and Registrar server might be configured to maintain separate
COMMON-MIB instances. SIP-COMMON-MIB instances.
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" | "ACME SIP Proxy" | | 1 | "sip_proxy10" | "ACME SIP Proxy" |
| 2 | "sip_registrar" | "ACME SIP Registrar" | | 2 | "sip_registrar17" | "ACME SIP Registrar" |
+-----------+-----------------+----------------------+ +-----------+-------------------+----------------------+
The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for the The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for the
proxy (applIndex=1) and one for the registrar (applIndex=2). The proxy (applIndex=1) and one for the registrar (applIndex=2). The
SIP-SERVER-MIB tables would, however, only be populated with one row SIP-SERVER-MIB tables would, however, only be populated with one row
indexed by applIndex=1 and applIndex=2 respectively if the server indexed by applIndex=1 and applIndex=2 respectively if the server
provides either proxy or registrar. provides either proxy or registrar.
SIP-COMMON-MIB sipCommonCfgTable might be populated as: SIP-COMMON-MIB sipCommonCfgTable might be populated as:
+-----------+---------------------+----------------------+-----+ +-----------+--------------------+----------------------+-----+
| applIndex | sipProtocolVerfsion | sipServiceOperStatus | ... | | applIndex | sipProtocolVersion | sipServiceOperStatus | ... |
+-----------+---------------------+----------------------+-----+ +-----------+--------------------+----------------------+-----+
| 1 | "SIP/2.0" | up(1) | | | 1 | "SIP/2.0" | up(1) | 2 |
| 2 | "SIP/2.0" | restarting(4) | | | "SIP/2.0" | restarting(4) | | |
+-----------+---------------------+----------------------+-----+ +-----------+--------------------+----------------------+-----+
while sipProxyCfgTable in SIP-SERVER-MIB might be populated as: while sipProxyCfgTable in SIP-SERVER-MIB might be populated as:
+-----------+----------------------+----------------------+-----+ +-----------+----------------------+-----+
| applIndex | sipRequestMaxExpires | sipProxyStatefulness | ... | | applIndex | sipProxyStatefulness | ... |
+-----------+----------------------+----------------------+-----+ +-----------+----------------------+-----+
| 1 | 3600 | stateless(1) | | | 1 | stateless(1) | |
+-----------+----------------------+----------------------+-----+ +-----------+----------------------+-----+
and sipRegUserTable in SIP-SERVER-MIB might be populated as: and sipRegUserTable in SIP-SERVER-MIB might be populated as:
+-----------+--------------+-------------------+-----+ +-----------+--------------+-------------------+-----+
| applIndex | sipUserIndex | sipUserUri | ... | | applIndex | sipUserIndex | sipUserUri | ... |
+-----------+--------------+-------------------+-----+ +-----------+--------------+-------------------+-----+
| 2 | 1 | bob@example.com | | | 2 | 1 | bob@example.com | |
| 2 | 2 | alice@example.com | | | 2 | 2 | alice@example.com | |
| 2 | 3 | jim@example.com | | | 2 | 3 | jim@example.com | |
| 2 | 4 | john@example.com | | | 2 | 4 | john@example.com | |
+-----------+--------------+-------------------+-----+ +-----------+--------------+-------------------+-----+
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_registrar" | "ACME SIP Proxy & 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) |
+-----------+--------------------+----------------------+ +-----------+--------------------+----------------------+
while sipProxyCfgTable in SIP-SERVER-MIB is populated as: while sipRegUserTable in SIP-SERVER-MIB might be populated as:
+-----------+----------------------+----------------------+
| applIndex | sipMaxRequestExpires | sipProxyStatefulness |
+-----------+----------------------+----------------------+
| 1 | 3600 | stateless(1) |
+-----------+----------------------+----------------------+
and sipRegUserTable in SIP-SERVER-MIB might be populated as:
+-----------+--------------+-------------------+-----+ +-----------+--------------+-------------------+-----+
| applIndex | sipUserIndex | sipUserUri | ... | | applIndex | sipUserIndex | sipUserUri | ... |
+-----------+--------------+-------------------+-----+ +-----------+--------------+-------------------+-----+
| 2 | 1 | bob@example.com | | | 2 | 1 | bob@example.com | |
| 2 | 2 | alice@example.com | | | 2 | 2 | alice@example.com | |
| 2 | 3 | kevin@example.com | | | 2 | 3 | kevin@example.com | |
| 2 | 4 | jf@example.com | | | 2 | 4 | jf@example.com | |
+-----------+--------------+-------------------+-----+ +-----------+--------------+-------------------+-----+
The NETWORK-SERVICES-MIB assocTable is not considered a requirement The NETWORK-SERVICES-MIB assocTable is not considered a requirement
for SIP systems. It is not a mandatory group for NETWORK-SERVICES- for SIP systems. It is not a mandatory group for compliance with the
MIB compliance. NETWORK-SERVICES-MIB module.
The relationship between the value of applOperStatus and The relationship between the value of applOperStatus and
sipServiceOperStatus is as follows: sipServiceOperStatus is as follows:
+----------------------+-----------------------+-------------------+ +----------------------+-----------------------+-------------------+
| sipServiceOperStatus | -- corresponds to --> | applOperstatus | | sipServiceOperStatus | -- corresponds to --> | applOperStatus |
+----------------------+-----------------------+-------------------+ +----------------------+-----------------------+-------------------+
| up | --> | up | | up | --> | up |
| down | --> | down | | down | --> | down |
| congested | --> | congested | | congested | --> | congested |
| restarting | --> | restarting | | restarting | --> | restarting |
| 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.
6. Accommodating SIP Extension Methods 6. Accommodating SIP Extension Methods
The core set of SIP methods is defined in RFC 3261 [7]. Other IETF The core set of SIP methods is defined in RFC 3261 [RFC3261]. Other
RFCs define additional methods. In the future, more methods may be IETF RFCs define additional methods. In the future, additional
defined. In order to avoid having to update the SIP-COMMON-MIB methods may be defined. In order to avoid having to update the
module to accommodate these extension methods, we use a Method SIP-COMMON-MIB module to accommodate these extension methods, we use
Identifier (SipMethodIdentifier textual-convention) to represent all a method identifier (SipMethodIdentifier textual-convention) to
SIP methods registered with IANA. See IANA Consideration section. represent all SIP methods registered with IANA. See IANA
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 [7] and other SIP methods registered SIP methods defined in RFC 3261 [RFC3261] and other SIP methods
with IANA. The table is informational in nature and populated by the registered with IANA. The table is informational in nature and
system. Entries cannot be added or deleted by a SNMP manager. populated by the system. Entries cannot be added or deleted by a
SNMP manager.
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, Unsigned32,
skipping to change at page 10, line 4 skipping to change at page 10, line 27
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, 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 "200407160000Z" LAST-UPDATED "200501281700Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" 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
postal:
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
phone:
Co-editor Dave Walker
postal:
email: drwalker@rogers.com
phone:
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 3708
Co-editor Dave Walker
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 (2004). This version Copyright (C) The Internet Society (2005). 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 "200407160000Z" REVISION "200501281700Z"
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 xx } ::= { mib-2 XXX1 }
-- RFC Ed: replace xx with actual IANA assigned number and remove this note -- RFC Ed: replace XXX1 with actual IANA assigned number for this
-- sipTC mib module and remove this note
-- --
-- Textual Conventions -- Textual Conventions
-- --
SipTransportProtocol ::= TEXTUAL-CONVENTION SipTransportProtocol ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention is a bit map. Each bit represents a "This convention is a bit map. Each bit represents a
transport protocol. If a bit has value 1, then that transport protocol. If a bit has value 1, then that
skipping to change at page 13, line 45 skipping to change at page 14, line 15
SipOptionTagHeaders SipOptionTagHeaders
FROM SIP-TC FROM SIP-TC
applIndex applIndex
FROM NETWORK-SERVICES-MIB FROM NETWORK-SERVICES-MIB
InetPortNumber InetPortNumber
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
sipCommonMIB MODULE-IDENTITY sipCommonMIB MODULE-IDENTITY
LAST-UPDATED "200407160000Z" LAST-UPDATED "200501281700Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" 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
postal:
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
phone:
Co-editor Dave Walker
postal:
email: drwalker@rogers.com
phone:
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 3708
Co-editor Dave Walker
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
sessions with one or more participants. These sessions sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 3261 (June telephone calls. SIP is defined in RFC 3261 (June
2002). 2002).
This MIB is defined for managing objects which are This MIB is defined for managing objects which are
common to SIP User Agents (UAs), Proxy/Redirect common to SIP User Agents (UAs), Proxy, Redirect
Servers, and Registrars. Objects specific to each of and Registrar servers. Objects specific to each of
these entities MAY be managed using entity specific these entities MAY be managed using entity specific
MIBs defined in other modules. MIBs defined in other modules.
User Agent (UA): A logical entity that can act as both User Agent (UA): A logical entity that can act as both
a user agent client and user agent server. a user agent client and user agent server.
User Agent Client (UAC): A user agent client is a logical User Agent Client (UAC): A logical entity that creates
entity that creates a new request, and then uses the client a new request, and then uses the client
transaction state machinery to send it. The role of UAC transaction state machinery to send it. The role of UAC
lasts only for the duration of that transaction. In other lasts only for the duration of that transaction. In
words, if a piece of software initiates a request, it acts other words, if a piece of software initiates a
as a UAC for the duration of that transaction. If it request, it acts as a UAC for the duration of that
receives a request later, it assumes the role of a user transaction. If it receives a request later, it
agent server for the processing of that transaction. assumes the role of a user agent server for the
User Agent Server (UAS): A user agent server is a logical processing of that transaction.
entity that generates a response to a SIP request. The User Agent Server (UAS): a logical entity that
response accepts, rejects, or redirects the request. This generates a response to a SIP request. The
role lasts only for the duration of that transaction. In response accepts, rejects, or redirects the request.
other words, if a piece of software responds to a request, This role lasts only for the duration of that
it acts as a UAS for the duration of that transaction. If transaction. In other words, if a piece of software
it generates a request later, it assumes the role of a user responds to a request, it acts as a UAS for the
agent client for the processing of that transaction. duration of that transaction. If it generates a
request later, it assumes the role of a user
agent client for the processing of that
transaction.
Proxy, Proxy Server: An intermediary entity that acts Proxy, Proxy Server: An intermediary entity that acts
as both a server and a client for the purpose of making as both a server and a client for the purpose of making
requests on behalf of other clients. A proxy server requests on behalf of other clients. A proxy server
primarily plays the role of routing, which means its job primarily plays the role of routing, which means its
is to ensure that a request is sent to another entity job is to ensure that a request is sent to another
'closer' to the targeted user. Proxies are also useful entity 'closer' to the targeted user.
for enforcing policy. A proxy interprets, and, if Proxies are also useful for enforcing policy. A proxy
necessary, rewrites specific parts of a request message interprets, and, if necessary, rewrites specific parts
before forwarding it. of a request message before forwarding it.
Redirect Server: A redirect server is a user agent server Redirect Server: A redirect server is a user agent
that generates 3xx responses to requests it receives, server that generates 3xx responses to requests it
directing the client to contact an alternate set of URIs. receives, directing the client to contact an alternate
set of URIs.
Registrar: A registrar is a server that accepts REGISTER Registrar: A registrar is a server that accepts
requests and places the information it receives in those REGISTER requests and places the information it
requests into the location service for the domain it handles. receives in those requests into the location service
for the domain it handles.
Copyright (C) The Internet Society (2004). This version Copyright (C) The Internet Society (2005). 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
REVISION "200407160000Z" -- remove this note
REVISION "200501281700Z"
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 xx } ::= { mib-2 XXX2 }
-- RFC Ed: replace xx 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.
-- --
-- Common basic configuration -- Common basic configuration
sipCommonCfgBase OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 } sipCommonCfgBase OBJECT IDENTIFIER
::= { sipCommonMIBObjects 1 }
-- Protocol timer configuration -- Protocol timer configuration
sipCommonCfgTimer OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 } sipCommonCfgTimer OBJECT IDENTIFIER
::= { sipCommonMIBObjects 2 }
-- Expires header configuration
sipCommonCfgExpires OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 }
-- SIP message summary statistics -- SIP message summary statistics
sipCommonStatsSummary OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 } sipCommonStatsSummary OBJECT IDENTIFIER
::= { sipCommonMIBObjects 3 }
-- Per method statistics -- Per method statistics
sipCommonStatsMethod OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 } sipCommonStatsMethod OBJECT IDENTIFIER
::= { sipCommonMIBObjects 4 }
-- Per Status code or status code class statistics -- Per Status code or status code class statistics
sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 } sipCommonStatusCode OBJECT IDENTIFIER
::= { sipCommonMIBObjects 5 }
-- Transaction statistics -- Transaction statistics
sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 } sipCommonStatsTrans OBJECT IDENTIFIER
::= { sipCommonMIBObjects 6 }
-- Method retry statistics -- Method retry statistics
sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 } sipCommonStatsRetry OBJECT IDENTIFIER
::= { sipCommonMIBObjects 7 }
-- Other statistics -- Other statistics
sipCommonStatsOther OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 } sipCommonStatsOther OBJECT IDENTIFIER
::= { sipCommonMIBObjects 8 }
-- Accessible-for-notify objects -- Accessible-for-notify objects
sipCommonNotifObjects OBJECT IDENTIFIER ::= { sipCommonMIBObjects 10 } sipCommonNotifObjects OBJECT IDENTIFIER
::= { sipCommonMIBObjects 9 }
-- --
-- Common Configuration Objects -- Common Configuration Objects
-- --
sipCommonCfgTable OBJECT-TYPE sipCommonCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgEntry SYNTAX SEQUENCE OF SipCommonCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the common configuration objects "This table contains the common configuration objects
skipping to change at page 17, line 26 skipping to change at page 17, line 47
is used to uniquely identify these instances of SIP is used to uniquely identify these instances of SIP
entities and correlate them through the common entities and correlate them through the common
framework of the NETWORK-SERVICES-MIB (RFC 2788)." framework of the NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipCommonCfgTable 1 } ::= { sipCommonCfgTable 1 }
SipCommonCfgEntry ::= SipCommonCfgEntry ::=
SEQUENCE { SEQUENCE {
sipProtocolVersion SnmpAdminString, sipProtocolVersion SnmpAdminString,
sipServiceOperStatus INTEGER, sipServiceOperStatus INTEGER,
sipServiceAdminStatus INTEGER,
sipServiceStartTime TimeTicks, sipServiceStartTime TimeTicks,
sipServiceLastChange TimeTicks, sipServiceLastChange TimeTicks,
sipOrganization SnmpAdminString, sipOrganization SnmpAdminString,
sipMaxTransactions Unsigned32, sipMaxTransactions Unsigned32,
sipServiceNotifEnable BITS, sipServiceNotifEnable BITS,
sipEntityType SipEntityRole sipEntityType SipEntityRole
} }
sipProtocolVersion OBJECT-TYPE sipProtocolVersion OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will reflect the version of SIP supported by "This object will reflect the version of SIP supported by
this SIP entity. It will follow the same format as SIP this SIP entity. It will follow the same format as SIP
version information contained in the SIP messages version information contained in the SIP messages
generated by this SIP entity. For example, entities generated by this SIP entity. For example, entities
supporting SIP version 2 will return 'SIP/2.0' as dictated supporting SIP version 2 will return 'SIP/2.0' as
by the standard." dictated by the standard."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipCommonCfgEntry 1 } ::= { sipCommonCfgEntry 1 }
sipServiceOperStatus OBJECT-TYPE sipServiceOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
up(2), up(2),
down(3), down(3),
congested(4), congested(4),
restarting(5), restarting(5),
quiescing(6), quiescing(6),
testing(7) testing(7)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the current operational state of the "This object contains the current operational state of
SIP application. the SIP application.
unknown : The operational status cannot be determined unknown : The operational status cannot be determined
for some reason. for some reason.
up : The application is operating normally, and up : The application is operating normally, and
is processing (receiving and possibly is processing (receiving and possibly
issuing) SIP requests and responses. issuing) SIP requests and responses.
down : 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
skipping to change at page 18, line 32 skipping to change at page 19, line 4
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 transactions quiesce mode. Additional inbound
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 are
not based on any specific information contained in the SIP not based on any specific information contained in the SIP
standard." standard."
::= { sipCommonCfgEntry 2 } ::= { sipCommonCfgEntry 2 }
sipServiceAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
noop(1),
up(2),
down(3),
reset(4),
quiesceDialogs(5),
quiesceApplication(6)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object is used to affect the overall operational
state of the SIP application. When read, this object
always return a value of noop(1) since sipServiceOperStatus
reflects the actual operational status.
noop : Setting this object to a noop value
has no effect; when read, this value
is always returned.
up : Enable the application.
down : Abrupt shutdown. Immediately terminate.
reset : Restart application, reinitialize data.
quiesceDialogs : Enable quiescence mode. Stop accepting
any new SIP dialogs. Stop processing
new transactions except for transactions
associated with an existing dialog or
call.
quiesceApplications : Enable quiescence mode. Stop processing
new SIP transactions except for
transactions associated with existing
applications. The exact application
behavior SHOULD be specified by the
implementation."
::= { sipCommonCfgEntry 3 }
sipServiceStartTime OBJECT-TYPE sipServiceStartTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the SIP entity was last "The value of sysUpTime at the time the SIP entity was last
started. If started prior to the last re-initialization of started. If started prior to the last re-initialization of
the local network management subsystem, then this object the local network management subsystem, then this object
contains a zero value." contains a zero value."
::= { sipCommonCfgEntry 4 } ::= { 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 entered
its current operational state. If the current state was its current operational state. If the current state was
entered prior to the last re-initialization of the local entered prior to the last re-initialization of the local
network management subsystem, then this object contains a network management subsystem, then this object contains a
zero value." zero value."
::= { sipCommonCfgEntry 5 } ::= { sipCommonCfgEntry 4 }
sipOrganization OBJECT-TYPE sipOrganization OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write 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
Organization header is to be generated." Organization header is to be generated."
REFERENCE REFERENCE
"RFC 3261, Section 20.25" "RFC 3261, Section 20.25"
::= { sipCommonCfgEntry 6 } ::= { sipCommonCfgEntry 5 }
sipMaxTransactions OBJECT-TYPE sipMaxTransactions 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 indicates the maximum number of simultaneous "This object indicates the maximum number of simultaneous
transactions that the SIP entity can manage. In general transactions that the SIP entity can manage. In general
the value of this object SHOULD reflect a level of the value of this object SHOULD reflect a level of
transaction processing that is considered high enough transaction processing that is considered high enough
to impact the systems CPU and/or memory resources to to impact the systems CPU and/or memory resources to
the point of deteriorating SIP call processing but not the point of deteriorating SIP call processing but not
high enough to cause catastrophic system failure." high enough to cause catastrophic system failure."
::= { sipCommonCfgEntry 7 } ::= { sipCommonCfgEntry 6 }
sipServiceNotifEnable OBJECT-TYPE sipServiceNotifEnable OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
sipServiceColdStart(0), sipServiceColdStart(0),
sipServiceWarmStart(1), sipServiceWarmStart(1),
sipServiceStatusChanged(2) sipServiceStatusChanged(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 21, line 4 skipping to change at page 20, line 36
DESCRIPTION DESCRIPTION
"This object specifies which SIP service related "This object specifies which SIP service related
notifications are enabled. Each bit represents notifications are enabled. Each bit represents
a specific notification. If a bit has a value 1, a specific notification. If a bit has a value 1,
the associated notification is enabled and will the associated notification is enabled and will
be generated by the SIP entity at the approriate be generated by the SIP entity at the approriate
time. The notifications are OPTIONAL, and if they time. The notifications are OPTIONAL, and if they
are not implemented this object's value has no are not implemented this object's value has no
meaning and MUST be 0. Setting this object in that meaning and MUST be 0. Setting this object in that
circumstance SHOULD result in a badValue error. circumstance SHOULD result in a badValue error.
If notifications are supported, this object's default If notifications are supported, this object's default
value SHOULD reflect sipServiceColdStart and value SHOULD reflect sipServiceColdStart and
sipServiceWarmStart enabled and sipServiceStatusChanged sipServiceWarmStart enabled and sipServiceStatusChanged
disabled." disabled."
::= { sipCommonCfgEntry 8 } ::= { sipCommonCfgEntry 7 }
sipEntityType OBJECT-TYPE sipEntityType OBJECT-TYPE
SYNTAX SipEntityRole SYNTAX SipEntityRole
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object identifies the list of SIP entities this " This object identifies the list of SIP entities this
row is related to. It is defined as a bit map. Each row is related to. It is defined as a bit map. Each
bit represents a type of SIP entity. bit represents a type of SIP entity.
If a bit has value 1, the SIP entity represented by If a bit has value 1, the SIP entity represented by
skipping to change at page 21, line 21 skipping to change at page 21, line 4
sipEntityType OBJECT-TYPE sipEntityType OBJECT-TYPE
SYNTAX SipEntityRole SYNTAX SipEntityRole
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object identifies the list of SIP entities this " This object identifies the list of SIP entities this
row is related to. It is defined as a bit map. Each row is related to. It is defined as a bit map. Each
bit represents a type of SIP entity. bit represents a type of SIP entity.
If a bit has value 1, the SIP entity represented by If a bit has value 1, the SIP entity represented by
this row plays the role of this entity type. this row plays the role of this entity type.
If a bit has value 0, the SIP entity represented by If a bit has value 0, the SIP entity represented by
this row does not act as this entity type this row does not act as this entity type
Combinations of bits can be set when the SIP entity Combinations of bits can be set when the SIP entity
plays multiple SIP roles." plays multiple SIP roles."
::= { sipCommonCfgEntry 9 } ::= { 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 entity
skipping to change at page 27, line 10 skipping to change at page 26, line 41
sipCfgTimerJ Unsigned32, sipCfgTimerJ Unsigned32,
sipCfgTimerK Unsigned32, sipCfgTimerK Unsigned32,
sipCfgTimerT1 Unsigned32, sipCfgTimerT1 Unsigned32,
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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object reflects the initial value for the retransmit
timer for the INVITE method. The retransmit timer doubles timer for the INVITE method. The retransmit timer doubles
after each retransmission, ensuring an exponential backoff after each retransmission, ensuring an exponential backoff
in network traffic. This object represents the initial time in network traffic. This object represents the initial time
a SIP entity will wait to receive a provisional response to a SIP entity will wait to receive a provisional response to
an INVITE before resending the INVITE request." an INVITE before resending the INVITE request."
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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum time a SIP entity will "This object reflects the maximum time a SIP entity will
wait to receive a final response to an INVITE. The wait to receive a final response to an INVITE. The
timer is started upon transmission of the initial INVITE timer is started upon transmission of the initial INVITE
request." request."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.1.2" "RFC 3261, Section 17.1.1.2"
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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies 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 be
greater than 32000 for UDP transport and its value MUST greater than 32000 for UDP transport and its value MUST
be 0 for TCP/SCTP transport." 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies 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 time
a SIP entity will wait to receive a provisional response to a SIP entity will wait to receive a provisional response to
the request before resending the non-INVITE request." 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum time a SIP entity will "This object reflects the maximum time a SIP entity will
wait to receive a final response to a non-INVITE request. wait to receive a final response to a non-INVITE request.
The timer is started upon transmission of the The timer is started upon transmission of the
initial request." initial request."
REFERENCE REFERENCE
"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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object reflects the initial value for the retransmit
timer for final responses to INVITE requests. 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 transport
layer once more for retransmission, and timer G is set layer once more for retransmission, and timer G is set
to fire in MIN(2*T1, T2) seconds. From then on, when to fire in MIN(2*T1, T2) seconds. From then on, when
timer G fires, the response is passed to the transport timer G fires, the response is passed to the transport
again for transmission, and timer G is reset with a value again for transmission, and timer G is reset with a value
that doubles, unless that value exceeds T2, in which case that doubles, unless that value exceeds T2, in which case
it is reset with the value of T2. it is reset with the value of T2.
The default value MUST be T1 for UDP transport and its value The default value MUST be T1 for UDP transport and its value
MUST be 0 for reliable transport like TCP/SCTP." MUST be 0 for reliable transport like 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"
skipping to change at page 29, line 32 skipping to change at page 29, line 15
The default value MUST be T1 for UDP transport and its value The default value MUST be T1 for UDP transport and its value
MUST be 0 for reliable transport like TCP/SCTP." MUST be 0 for reliable transport like 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum time a server will wait "This object reflects the maximum time a server will wait
to receive an ACK before it abandons retransmitting the to receive an ACK before it abandons retransmitting the
response. The timer is started upon entering the response. The timer is started upon entering the
'Completed' state." 'Completed' state."
REFERENCE REFERENCE
"RFC 3261, Section 17.2.1" "RFC 3261, Section 17.2.1"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 8 } ::= { sipCommonCfgTimerEntry 8 }
sipCfgTimerI OBJECT-TYPE sipCfgTimerI OBJECT-TYPE
SYNTAX Unsigned32 (0..10000) SYNTAX Unsigned32 (0..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies 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 value
MUST be 0 for reliable transport like TCP/SCTP." 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)
skipping to change at page 30, line 16 skipping to change at page 29, line 46
The default value MUST be T4 for UDP transport and its value The default value MUST be T4 for UDP transport and its value
MUST be 0 for reliable transport like TCP/SCTP." 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies 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 server
MUST transition to the 'Terminated' state." 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies 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 non-INVITE
requests. 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 server
MUST transition to the 'Terminated' state. 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 value
MUST be 0 for reliable transport like TCP/SCTP." 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the T1 timer for a SIP entity. T1 "This object reflects the T1 timer for a SIP entity. T1
is an estimate of the round-trip time (RTT) between the is an estimate of the round-trip time (RTT) between the
client and server transactions." client and server transactions."
REFERENCE REFERENCE
"RFC 3261, Section 17" "RFC 3261, Section 17"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 12 } ::= { sipCommonCfgTimerEntry 12 }
sipCfgTimerT2 OBJECT-TYPE sipCfgTimerT2 OBJECT-TYPE
SYNTAX Unsigned32 (200..10000) SYNTAX Unsigned32 (200..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the T2 timer for a SIP entity. "This object reflects the T2 timer for a SIP entity.
T2 is the maximum retransmit interval for non-INVITE T2 is the maximum retransmit interval for non-INVITE
requests and INVITE responses. It's used in various requests and INVITE responses. It's used in various
parts of the protocol to reset other Timer* objects parts of the protocol to reset other Timer* objects
to this value." to this value."
REFERENCE REFERENCE
"RFC 3261, Section 17" "RFC 3261, Section 17"
DEFVAL { 4000 } DEFVAL { 4000 }
::= { sipCommonCfgTimerEntry 13 } ::= { sipCommonCfgTimerEntry 13 }
sipCfgTimerT4 OBJECT-TYPE sipCfgTimerT4 OBJECT-TYPE
SYNTAX Unsigned32 (200..10000) SYNTAX Unsigned32 (200..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the T4 timer for a SIP entity. "This object reflects the T4 timer for a SIP entity.
T4 is the maximum duration a message will remain in T4 is the maximum duration a message will remain in
the network. It represents the amount of time the the network. It represents the amount of time the
network will take to clear messages between client network will take to clear messages between client
and server transactions. It's used in various parts and server transactions. It's used in various parts
of the protocol to reset other Timer* objects to this of the protocol to reset other Timer* objects to this
value." value."
REFERENCE REFERENCE
"RFC 3261, Section 17" "RFC 3261, Section 17"
DEFVAL { 5000 } DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 14 } ::= { sipCommonCfgTimerEntry 14 }
skipping to change at page 35, line 41 skipping to change at page 35, line 23
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 2 } ::= { sipMethodStatsEntry 2 }
sipStatsInbounds OBJECT-TYPE sipStatsInbounds 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
received by the SIP entity." received by the SIP entity. Retransmissions are
counted separately and are not reflected in this
counter."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 3 } ::= { sipMethodStatsEntry 3 }
-- --
-- Support for specific status codes -- Support for specific status codes
-- --
sipStatusCodesTable OBJECT-TYPE sipStatusCodesTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatusCodesEntry SYNTAX SEQUENCE OF SipStatusCodesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 36, line 27 skipping to change at page 36, line 11
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information on a particular SIP status "This row contains information on a particular SIP status
code that the SIP entity has been requested to monitor. code that the SIP entity has been requested to monitor.
Each row represents those objects for a particular SIP 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, sipStatusCodeValue } INDEX { applIndex, sipStatusCodeMethod, sipStatusCodeValue }
::= { sipStatusCodesTable 1 } ::= { sipStatusCodesTable 1 }
SipStatusCodesEntry ::= SipStatusCodesEntry ::=
SEQUENCE { SEQUENCE {
sipStatusCodeMethod SipMethodIdentifier,
sipStatusCodeValue Unsigned32, sipStatusCodeValue Unsigned32,
sipStatusCodeIns Counter32, sipStatusCodeIns Counter32,
sipStatusCodeOuts Counter32, sipStatusCodeOuts Counter32,
sipStatusCodeRowStatus RowStatus sipStatusCodeRowStatus RowStatus
} }
sipStatusCodeMethod OBJECT-TYPE
SYNTAX SipMethodIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object uniquely identifies a conceptual row
in the table and reflects an assigned number used
to identifier a specific SIP method."
::= { 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 SIP
entity has been requested to monitor. All of the other entity has been requested to monitor. All of the other
information in the row is related to this value." information in the row is related to this value."
::= { sipStatusCodesEntry 1 } ::= { 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 messages
received by the SIP entity with the status code value received by the SIP entity with the status code value
contained in the sipStatusCodeValue column." contained in the sipStatusCodeValue column."
::= { sipStatusCodesEntry 2 } ::= { 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 messages
sent by the SIP entity with the status code value sent by the SIP entity with the status code value
contained in the sipStatusCodeValue column." contained in the sipStatusCodeValue column."
::= { sipStatusCodesEntry 3 } ::= { 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.
The values 'createAndGo' and 'destroy' are the The values 'createAndGo' and 'destroy' are the
only valid values allowed for this object. only valid values allowed for this object.
If a row exists, it will reflect a status of If a row exists, it will reflect a status of
'active' when queried." 'active' when queried."
::= { sipStatusCodesEntry 4 } ::= { sipStatusCodesEntry 5 }
-- --
-- support for specific status code notifications -- support for specific status code notifications
-- --
sipStatusCodeNotifTable OBJECT-TYPE sipStatusCodeNotifTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatusCodeNotifEntry SYNTAX SEQUENCE OF SipStatusCodeNotifEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains objects to control notifications "This table contains objects to control notifications
skipping to change at page 42, line 52 skipping to change at page 42, line 45
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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE retries "This object reflects the total number of request
that have been sent by the SIP entity." retransmissions that have been sent by the SIP
entity. Note that there could be multiple
retransmissions per request."
::= { sipCommonStatsRetryEntry 2 } ::= { sipCommonStatsRetryEntry 2 }
sipStatsRetryFinalResponses OBJECT-TYPE sipStatsRetryFinalResponses 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 Final Response "This object reflects the total number of Final Response
retries that have been sent by the SIP entity." retries that have been sent by the SIP entity.
Note that there could be multiple retransmissions
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 Response
retries that have been sent by the SIP entity." retries that have been sent by the SIP entity."
::= { sipCommonStatsRetryEntry 4 } ::= { sipCommonStatsRetryEntry 4 }
skipping to change at page 49, line 34 skipping to change at page 49, line 32
sipCommonNotifGroup and sipCommonNotifObjectsGroup sipCommonNotifGroup and sipCommonNotifObjectsGroup
MUST also be implemented." MUST also be implemented."
GROUP sipCommonNotifObjectsGroup GROUP sipCommonNotifObjectsGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to
not provide any notifications. If implemented, the not provide any notifications. If implemented, the
sipCommonStatusCodeNotifGroup and sipCommonStatusCodeNotifGroup and
sipCommonNotifGroup MUST also be implemented." sipCommonNotifGroup MUST also be implemented."
OBJECT sipCfgTimerA
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerB
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerC
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerD
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerE
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerF
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerG
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerH
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerI
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerJ
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerK
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerT1
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerT2
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
OBJECT sipCfgTimerT4
MIN-ACCESS read-only
DESCRIPTION
"Implementations may not allow the modification of SIP
timers; this may be read-only."
::= { sipCommonMIBCompliances 1 } ::= { sipCommonMIBCompliances 1 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipCommonConfigGroup OBJECT-GROUP sipCommonConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipProtocolVersion, sipProtocolVersion,
sipServiceOperStatus, sipServiceOperStatus,
sipServiceAdminStatus,
sipServiceStartTime, sipServiceStartTime,
sipServiceLastChange, sipServiceLastChange,
sipTransportRcv, sipTransportRcv,
sipOptionTag, sipOptionTag,
sipOptionTagHeaderField, sipOptionTagHeaderField,
sipOrganization, sipOrganization,
sipMaxTransactions, sipMaxTransactions,
sipServiceNotifEnable, sipServiceNotifEnable,
sipEntityType, sipEntityType,
sipMethodName sipMethodName
skipping to change at page 54, line 21 skipping to change at page 52, line 31
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Unsigned32, Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
RowStatus
FROM SNMPv2-TC
applIndex applIndex
FROM NETWORK-SERVICES-MIB FROM NETWORK-SERVICES-MIB
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
SipEntityRole SipEntityRole
FROM SIP-TC; FROM SIP-TC;
sipUAMIB MODULE-IDENTITY sipUAMIB MODULE-IDENTITY
LAST-UPDATED "200407160000Z" LAST-UPDATED "200501281700Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" 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
postal:
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
phone:
Co-editor Dave Walker
postal:
email: drwalker@rogers.com
phone:
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 3708
Co-editor Dave Walker
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
telephone calls. SIP is defined in RFC 3261 (June telephone calls. SIP is defined in RFC 3261 (June
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 (2004). This version Copyright (C) The Internet Society (2005). 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 "200407160000Z" REVISION "200501281700Z"
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 xx } ::= { mib-2 XXX3 }
-- RFC Ed: replace xx 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 }
skipping to change at page 57, line 6 skipping to change at page 55, line 4
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, sipUACfgServerIndex } INDEX { applIndex, sipUACfgServerIndex }
::= { sipUACfgServerTable 1 } ::= { sipUACfgServerTable 1 }
SipUACfgServerEntry ::= SipUACfgServerEntry ::=
SEQUENCE { SEQUENCE {
sipUACfgServerIndex Unsigned32, sipUACfgServerIndex Unsigned32,
sipUACfgServerAddrType InetAddressType, sipUACfgServerAddrType InetAddressType,
sipUACfgServerAddr InetAddress, sipUACfgServerAddr InetAddress,
sipUACfgServerFunction SipEntityRole, sipUACfgServerFunction SipEntityRole
sipUACfgServerStatus RowStatus
} }
sipUACfgServerIndex OBJECT-TYPE sipUACfgServerIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique identifier of a server address when "A unique identifier of a server address when
multiple addresses are configured by the SIP entity. multiple addresses are configured by the SIP entity.
If one address isn't reachable, then another can If one address isn't reachable, then another can
be tried." be tried."
::= { sipUACfgServerEntry 1 } ::= { sipUACfgServerEntry 1 }
sipUACfgServerAddrType OBJECT-TYPE sipUACfgServerAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies 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 3291)"
::= { sipUACfgServerEntry 2 } ::= { sipUACfgServerEntry 2 }
sipUACfgServerAddr OBJECT-TYPE sipUACfgServerAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies 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 3291)"
::= { sipUACfgServerEntry 3 } ::= { sipUACfgServerEntry 3 }
sipUACfgServerFunction OBJECT-TYPE sipUACfgServerFunction OBJECT-TYPE
SYNTAX SipEntityRole SYNTAX SipEntityRole
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies 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, proxy
(outbound proxy), etc." (outbound proxy), etc."
::= { sipUACfgServerEntry 4 } ::= { sipUACfgServerEntry 4 }
sipUACfgServerStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to control rows in this table.
'active' : the row's information is completely
populated and that information is
being used by the user agent.
'notInService' : the row's address is not being used
by the user agent, but will remain in
the table.
'notReady' : key information is missing thus,
preventing the row from being made
'active' (eg, no address specified).
'createAndGo' : only allowed if the manager also
provides a varbind for
sipUACfgServerAddr object in the
same set operation.
'createAndWait' : not applicable.
'destroy' : the row's address will no longer be used
by the user agent and the row will be
removed from the table."
::= { sipUACfgServerEntry 5 }
-- --
-- Conformance -- Conformance
-- --
sipUAMIBCompliances sipUAMIBCompliances
OBJECT IDENTIFIER ::= { sipUAMIBConform 1 } OBJECT IDENTIFIER ::= { sipUAMIBConform 1 }
sipUAMIBGroups sipUAMIBGroups
OBJECT IDENTIFIER ::= { sipUAMIBConform 2 } OBJECT IDENTIFIER ::= { sipUAMIBConform 2 }
-- --
-- Compliance Statements -- Compliance Statements
skipping to change at page 59, line 4 skipping to change at page 56, line 18
-- --
-- Compliance Statements -- Compliance Statements
-- --
sipUACompliance MODULE-COMPLIANCE sipUACompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities." "The compliance statement for SIP entities."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipUAConfigGroup } MANDATORY-GROUPS { sipUAConfigGroup }
::= { sipUAMIBCompliances 1 } ::= { sipUAMIBCompliances 1 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipUAConfigGroup OBJECT-GROUP sipUAConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipUACfgServerAddrType, sipUACfgServerAddrType,
sipUACfgServerAddr, sipUACfgServerAddr,
sipUACfgServerFunction, sipUACfgServerFunction
sipUACfgServerStatus
} }
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 (Registrar & Proxy/Redirect Server) MIB Module 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
RowStatus,
TruthValue, TruthValue,
TimeStamp, DateAndTime TimeStamp, DateAndTime
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
skipping to change at page 60, line 4 skipping to change at page 57, line 17
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
applIndex applIndex
FROM NETWORK-SERVICES-MIB FROM NETWORK-SERVICES-MIB
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
sipServerMIB MODULE-IDENTITY sipServerMIB MODULE-IDENTITY
LAST-UPDATED "200407160000Z" LAST-UPDATED "200501281700Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" 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
postal:
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
phone:
Co-editor Dave Walker
postal:
email: drwalker@rogers.com
phone:
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 3708
Co-editor Dave Walker
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 sessions
include Internet multimedia conferences and Internet include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 3261 (June telephone calls. SIP is defined in RFC 3261 (June
2002). 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 a
Proxy or Redirect Server. Proxy or Redirect Server.
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2005).
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 "200407160000Z" REVISION "200501281700Z"
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 yy } ::= { mib-2 XXX4 }
-- RFC Ed: replace yy 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 62, line 36 skipping to change at page 59, line 39
::= { sipServerCfgTable 1 } ::= { sipServerCfgTable 1 }
SipServerCfgEntry ::= SipServerCfgEntry ::=
SEQUENCE { SEQUENCE {
sipServerHostAddrType InetAddressType, sipServerHostAddrType InetAddressType,
sipServerHostAddr InetAddress sipServerHostAddr InetAddress
} }
sipServerHostAddrType OBJECT-TYPE sipServerHostAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of Internet address by which the SIP server "The type of Internet address by which the SIP server
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-write 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 assigned
to the SIP server. It MAY contain a fully qualified to the SIP server. It MAY contain a fully qualified
domain name, or an IP address. The length of the value domain name, or an IP address. The length of the value
will depend on the type of address specified. 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."
skipping to change at page 64, line 21 skipping to change at page 61, line 24
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 specifies the default mode of operation for "This object reflects the default mode of operation for
the Proxy Server entity. 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 machines
when it processes requests. A stateless proxy forwards when it processes requests. A stateless proxy forwards
every request it receives downstream and every response every request it receives downstream and every response
it receives upstream. If the value of this object is it receives upstream. If the value of this object is
stateless(1), the proxy defaults to stateless stateless(1), the proxy defaults to stateless
operations. operations.
skipping to change at page 64, line 49 skipping to change at page 62, line 4
A call stateful proxy is a logical entity if it retains A call stateful proxy is a logical entity if it retains
state for a dialog from the initiating INVITE to the state for a dialog from the initiating INVITE to the
terminating BYE request. A call stateful proxy is terminating BYE request. A call stateful proxy is
always transaction stateful, but the converse is not always transaction stateful, but the converse is not
necessarily true. If the value of this object is necessarily true. If the value of this object is
callStateful(3), the proxy is call stateful." 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Proxy performs "This object reflects whether or not the Proxy performs
recursive search on the Contacts provided in 3xx recursive search on the Contacts provided in 3xx
redirects. redirects.
If the value of this object is 'true', a recursive search If the value of this object is 'true', a recursive search
is performed. If the value is 'false', no search is is performed. If the value is 'false', no search is
performed, the 3xx response is sent upstream towards the performed, the 3xx response is sent upstream towards the
source of the request." 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the proxy adds itself "This object reflects whether or not the proxy adds itself
to the Record-Route header as a default action. This to the Record-Route header as a default action. This
header is used to list the proxies that insist on being in header is used to list the proxies that insist on being in
the signaling path for subsequent requests related to the the signaling path for subsequent requests related to the
call-leg. call-leg.
If the value of this object is 'true', the proxy adds itself If the value of this object is 'true', the proxy adds itself
to the end of the Record-Route header, creating the header to the end of the Record-Route header, creating the header
if required. If the value is 'false', the proxy does if required. If the value is 'false', the proxy does
not add itself to the Record-Route header." 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),
tls(1), tls(1),
digest(2), digest(2)
smime(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the authentication methods that "This object reflects the authentication methods that
MAY be used to authenticate request originators. MAY be used to authenticate request originators.
bit 0 no authentication is performed bit 0 no authentication is performed
bit 1 TLS is used bit 1 TLS is used
bit 2 HTTP Digest is used bit 2 HTTP Digest is used."
bit 3 S/MIME 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the realm used in Proxy-Authenticate "This object reflects the realm used in Proxy-Authenticate
headers. Note that this MAY need to be stored per user." headers. Note that this MAY need to be stored per user."
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
skipping to change at page 68, line 24 skipping to change at page 65, line 24
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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Registrar SHOULD "This object reflects whether or not the Registrar SHOULD
allow third party registrations. In third-party 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 registered
(in the To header) to whom the provided Contact information (in the To header) to whom the provided Contact information
applies. applies.
If the value of this object is 'true', If the value of this object is 'true',
the Registrar allows third-party registrations. If the the Registrar allows third-party registrations. If the
value is 'false', third-party registrations are rejected: value is 'false', third-party registrations are rejected:
a 403 (Forbidden) status code is returned to the requester. a 403 (Forbidden) status code is returned to the requester.
This object SHOULD be non-volatile and its value SHOULD This object SHOULD be non-volatile and its value SHOULD
be kept at reboot." 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies 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 parameter
in a Contact header in a REGISTER request. If the value in a Contact header in a REGISTER request. If the value
requested by the User Agent is greater than the value requested by the User Agent is greater than the value
of this object, then the contact information is given the of this object, then the contact information is given the
duration specified by this object, and that duration duration specified by this object, and that duration
is indicated to the User Agent in the response." is indicated to the User Agent in the response."
::= { 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 specifies 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 is
reflected by sipRegCurrentUsers." 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 specifies 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 }
sipRegDfltRegActiveInterval OBJECT-TYPE sipRegDfltRegActiveInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default time interval the "This object reflects the default time interval the
Registrar considers registrations to be active. The Registrar considers registrations to be active. The
value is used to compute the Expires header in the value is used to compute the Expires header in the
REGISTER response. If a user agent requests a time REGISTER response. If a user agent requests a time
interval shorter than specified by this object, the interval shorter than specified by this object, the
Registrar SHOULD honor that request. 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.
skipping to change at page 70, line 40 skipping to change at page 67, line 40
NETWORK-SERVICES-MIB (RFC 2788). The same value of NETWORK-SERVICES-MIB (RFC 2788). The same value of
applIndex used in the corresponding SIP-COMMON-MIB 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
sipUserTableRowStatus RowStatus
} }
sipUserIndex OBJECT-TYPE sipUserIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in the "This object uniquely identifies a conceptual row in the
table." table."
::= { sipRegUserEntry 1 } ::= { sipRegUserEntry 1 }
skipping to change at page 71, line 5 skipping to change at page 68, line 4
} }
sipUserIndex OBJECT-TYPE sipUserIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in the "This object uniquely identifies a conceptual row in the
table." table."
::= { sipRegUserEntry 1 } ::= { sipRegUserEntry 1 }
sipUserUri OBJECT-TYPE sipUserUri OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create 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. It
is the main form by which the Registrar knows the user. is the main form by which the Registrar knows the user.
The format is typically 'user@domain'. It is contained The format is typically 'user@domain'. It is contained
in the To header for all REGISTER requests." 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 the
user has failed authentication." user has failed authentication."
::= { sipRegUserEntry 3 } ::= { sipRegUserEntry 3 }
sipUserTableRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The row status of the entry. This object is required
to create or delete rows remotely by a manager."
::= { sipRegUserEntry 4 }
-- --
-- Per Contact Information -- Per Contact Information
-- --
sipContactTable OBJECT-TYPE sipContactTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipContactEntry SYNTAX SEQUENCE OF SipContactEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on every location where "This table contains information on every location where
a registered user (specified by sipUserIndex) wishes to a registered user (specified by sipUserIndex) wishes to
skipping to change at page 77, line 33 skipping to change at page 74, line 23
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics for "A collection of objects providing statistics for
SIP Registrars." SIP Registrars."
::= { sipServerMIBGroups 5 } ::= { sipServerMIBGroups 5 }
sipRegistrarUsersGroup OBJECT-GROUP sipRegistrarUsersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipUserUri, sipUserUri,
sipUserAuthenticationFailures, sipUserAuthenticationFailures,
sipUserTableRowStatus,
sipContactDisplayName, sipContactDisplayName,
sipContactURI, sipContactURI,
sipContactLastUpdated, sipContactLastUpdated,
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. Changes from Previous Draft Revisions
This section to be removed by RFC Editor before publication. -- RFC Ed: this entire section to be removed by RFC Editor before
publication.
Changes from draft-ietf-sip-mib-07. The vast majority of changes are Changes from draft-ietf-sip-mib-08.
in response to the Working Group Last Call & expert review comments.
The majority of changes are in response to additional SIP Working
Group comments.
o General
* The IANA Consideration section was updated and a new section
9.2 was added to conform with the Guidelines for Authors and
Reviewers of MIB Documents,
draft-ietf-ops-mib-review-guidelines-03.txt, section 3.7.
* In general the ability to configure SIP entities via
read-create or read-write objects was removed and those objects
MAX-ACCESS constrained to read-only. This change was made
based on general consensus that SNMP should be limited to
monitoring rather than configuring/provisoning.
* The section 5.2 (Relationship to the Network Services MIB) was
updated to allow each instance of a SIP entity to have its own
row in the applTable (a unique aplication identifier should now
be appended to the "sip_xxx" entity-name). We also lowered the
level of requirement on the naming convention to a SHOULD
instead of a MUST per wg input.
* Updated the ORGANISATION clause of all MIB modules to include
the full SIP working group name.
* Minor other editorial changes were made to the document.
* Updated Security consideration section.
o SIP-COMMON-MIB
* Module description of various SIP entities enhanced.
* sipServiceAdminStatus removed from the MIB due to general
removal of configuration capability. Resulting OID value
changes to succeeding entry objects.
* sipOrganization MAX-ACCESS changed to read-only.
* sipCfgTimerA MAX-ACCESS changed to read-only.
* sipCfgTimerB MAX-ACCESS changed to read-only.
* sipCfgTimerC MAX-ACCESS changed to read-only.
* sipCfgTimerD MAX-ACCESS changed to read-only.
* sipCfgTimerE MAX-ACCESS changed to read-only.
* sipCfgTimerF MAX-ACCESS changed to read-only.
* sipCfgTimerG MAX-ACCESS changed to read-only.
* sipCfgTimerH MAX-ACCESS changed to read-only.
* sipCfgTimerI MAX-ACCESS changed to read-only.
* sipCfgTimerJ MAX-ACCESS changed to read-only.
* sipCfgTimerK MAX-ACCESS changed to read-only.
* sipCfgTimerT1 MAX-ACCESS changed to read-only.
* sipCfgTimerT2 MAX-ACCESS changed to read-only.
* sipCfgTimerT4 MAX-ACCESS changed to read-only.
* sipStatusCodesTable indexing changed to also include
sipStatusCodeMethod. Thusly, introducing sipStatusCodeMethod
as a new not-accessible object in that table. Resulting OID
value changes to succeeding entry objects.
* sipCfgTimer* OBJECT clauses regarding MIN-ACCESS levels in the
MODULE-COMPLIANCE were no longer needed due to MAX-ACCESS
changes for those objects.
* The description clause of sipStatsInbounds was changed to state
that retransmissions are not counted.
* The description clause of sipStatsRetries was changed to
indicate there could be multiple retries per request (we also
corrected a typo by removing the specific mention to INVITE
requests).
* The description clause of sipStatsRetryFinalResponses was
changed to indicate there could be multiple retries per
response.
o SIP-SERVER-MIB
* Removed sipCommonCfgExpires OID declaration as this object
group no longer exists since draft08.
* sipUserTableRowStatus removed from the MIB due to general
removal of configuration capability. In conjuction, RowStatus
textual convention is no longer imported.
* sipServerHostAddrType MAX-ACCESS changed to read-only.
* sipServerHostAddr MAX-ACCESS changed to read-only.
* sipProxyRecursion MAX-ACCESS changed to read-only.
* sipProxyRecordRoute MAX-ACCESS changed to read-only.
* sipProxyAuthMethod MAX-ACCESS changed to read-only.
* sipRegAllowThirdParty MAX-ACCESS changed to read-only.
* sipRegMaxContactExpiryDuration MAX-ACCESS changed to read-only.
* sipRegDfltRegActiveInterval MAX-ACCESS changed to read-only.
* sipUserUri MAX-ACCESS changed to read-only.
* 'smime' removed as a possible value for sipProxyAuthMethod.
o SIP-UA-MIB
* sipUACfgServerStatus removed from the MIB due to general
removal of configuration capability. In conjuction, RowStatus
textual convention is no longer imported.
* sipUACfgServerAddrType MAX-ACCESS changed to read-only.
* sipUACfgServerAddr MAX-ACCESS changed to read-only.
* sipUACfgServerFunction MAX-ACCESS changed to read-only.
Changes from draft-ietf-sip-mib-07.
The vast majority of changes are in response to the Working Group
Last Call and expert review comments.
o General o General
* IANA requirements section added to specify the need for * IANA requirements section added to specify the need for
registered numbers for all SIP methods. These will be used in registered numbers for all SIP methods. These will be used in
the MIB objects. the MIB objects.
* Updated the security consideration section to reflect the * Updated the security consideration section to reflect the
addition and deletion of a number of objects. addition and deletion of a number of objects.
o SIP-COMMON-MIB o SIP-COMMON-MIB
* Module description of various SIP entities enhanced. * Module description of various SIP entities enhanced.
* sipMaxSessions renamed sipMaxTransactions. Workgroup last call * sipMaxSessions renamed sipMaxTransactions. Workgroup last call
reviewers suggested a change based on some change of terms in reviewers suggested a change based on some change of terms in
skipping to change at page 78, line 23 skipping to change at page 77, line 4
o SIP-COMMON-MIB o SIP-COMMON-MIB
* Module description of various SIP entities enhanced. * Module description of various SIP entities enhanced.
* sipMaxSessions renamed sipMaxTransactions. Workgroup last call * sipMaxSessions renamed sipMaxTransactions. Workgroup last call
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 as it didn't make much sense. sipPortStatus was removed as it did not make much sense. sipPortStatus was
removed to prevent any row creation deletion. The remaining removed to prevent any row creation deletion. The remaining
object, sipTransportRcv was made read-only. object, 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 seperate, 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.
* sipCommonCfgRetryTable was removed. Limits on retransmissions * sipCommonCfgRetryTable was removed. Limits on retransmissions
are controlled by timers in the SIP standard now rather than by are controlled by timers in the SIP standard now rather than by
maximum counts; therefore, these objects were no longer maximum counts; therefore, these objects were no longer
relevant. sipCommonConfigRetryGroup was likewise removed. relevant. sipCommonConfigRetryGroup was likewise removed.
* sipFtrSupportedTable was redesigned as sipOptionTagsTable. * sipFtrSupportedTable was redesigned as sipOptionTagsTable.
* sipCommonCfgTimerExtMethodTable was removed. * sipCommonCfgTimerExtMethodTable was removed.
* sipSummaryTotalTransactions description changed to reflect that * sipSummaryTotalTransactions description changed to reflect that
skipping to change at page 79, line 18 skipping to change at page 77, line 49
* 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-specific objects. The new, additional indexing object method-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 & 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-groups as optional in the module-compliance was updated object-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
skipping to change at page 80, line 36 skipping to change at page 79, line 20
* SipEntityRole imported from SIP-TC module and used as the * SipEntityRole imported from SIP-TC module and used as the
syntax for new object sipUACfgServerFunction. syntax for new object sipUACfgServerFunction.
* sipUACfgSipServerTable (and objects therein) have their * sipUACfgSipServerTable (and objects therein) have their
descriptors changed to sipUACfgServer* ("Sip" removed). descriptors changed to sipUACfgServer* ("Sip" removed).
sipUAConfigGroup updated accordingly. sipUAConfigGroup updated accordingly.
* sipUACfgServerFunction added to sipUACfgServerTable. * sipUACfgServerFunction added to sipUACfgServerTable.
* 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.
o
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-COMPLIANCE. MODULE-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
skipping to change at page 81, line 36 skipping to change at page 80, line 19
o SIP-COMMON-MIB o SIP-COMMON-MIB
* Removed sipTransactionTable after input from SIP community. * Removed sipTransactionTable after input from SIP community.
* Made all extension method tables augmentations of * Made all extension method tables augmentations of
sipExtMethodSupportedTable. This resulted in the removal of sipExtMethodSupportedTable. This resulted in the removal of
the following objects: sipCfgTimerExtMethodName, the following objects: sipCfgTimerExtMethodName,
sipCfgRetryExtMethodName, sipStatsExtMethodName, sipCfgRetryExtMethodName, sipStatsExtMethodName,
sipStatsRetryExtMethodName. sipStatsRetryExtMethodName.
* sipCommonStatusCodeNotifEmitMode default value changed to * sipCommonStatusCodeNotifEmitMode default value changed to
'triggered'. 'triggered'.
* sipStatusCodeThreshExceededNotif was replaced by two * sipStatusCodeThreshExceededNotif was replaced by two
notifications: sipStatusCodeThreshExceededOutNotif & 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 question/ ability to set to 'notInService' where there was the
possibility of resetting the counters to zero. question/possibility of resetting the counters to zero.
sipStatsExtMethodTable no longer has it╚╦s own RowStatus sipStatsExtMethodTable no longer has its own RowStatus object,
object, so it too can no longer be set to 'notInService╦ where so it too can no longer be set to 'notInService' where there
there was the question/possibility of resetting the counters to was the question/possibility of resetting the counters to zero.
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.
* Explained the existence of sipNotifApplIndex object better. * Explained the existence of sipNotifApplIndex object better.
* sipCfgExpiresStatusCodeValue syntax changed from INTEGER to * sipCfgExpiresStatusCodeValue syntax changed from INTEGER to
Unsigned32. Unsigned32.
* sipEntityType object added to sipCommonCfgTable. * sipEntityType object added to sipCommonCfgTable.
* All accessible-for-notify objects are moved into * All accessible-for-notify objects are moved into
skipping to change at page 82, line 21 skipping to change at page 81, line 4
* sipCfgExpiresStatusCodeValue syntax changed from INTEGER to * sipCfgExpiresStatusCodeValue syntax changed from INTEGER to
Unsigned32. Unsigned32.
* sipEntityType object added to sipCommonCfgTable. * sipEntityType object added to sipCommonCfgTable.
* All accessible-for-notify objects are moved into * All accessible-for-notify objects are moved into
sipCommonNotifObjects group. OIDs for actual notifications are sipCommonNotifObjects group. OIDs for actual notifications are
re-assigned as a result. re-assigned as a result.
* sipNotifSequenceNumber accessible-for-notify object added as a * sipNotifSequenceNumber accessible-for-notify object added as a
way for managers to gain insight into possible missed way for managers to gain insight into possible missed
notifications. It is bound to each notification defined in the notifications. It is bound to each notification defined in the
MIB. MIB.
* New notifications related to SIP service operational status are * New notifications related to SIP service operational status are
added: sipServiceColdStart, sipServiceWarmStart, & added: sipServiceColdStart, sipServiceWarmStart, and
sipServiceLastChanged. sipServiceLastChanged.
* New object sipServiceNotifEnable added to control the new SIP * New object sipServiceNotifEnable added to control the new SIP
related notifications. related notifications.
* Minor object descriptor changes: sipStatusCodesTable renamed to * Minor object descriptor changes: sipStatusCodesTable renamed to
sipStatusCodeClassesTable SipStatusCodesEntry renamed to sipStatusCodeClassesTable SipStatusCodesEntry renamed to
SipStatusCodeClassesEntry sipStatusCodesEntry renamed to SipStatusCodeClassesEntry sipStatusCodesEntry renamed to
sipStatusCodeClassesEntry sipCommonStatusCodeTable renamed to sipStatusCodeClassesEntry sipCommonStatusCodeTable renamed to
sipStatusCodesTable SipCommonStatusCodeEntry renamed to sipStatusCodesTable SipCommonStatusCodeEntry renamed to
SipStatusCodesEntry sipCommonStatusCodeEntry renamed to SipStatusCodesEntry sipCommonStatusCodeEntry renamed to
sipStatusCodesEntry sipCommonStatusCodeValue renamed to sipStatusCodesEntry sipCommonStatusCodeValue renamed to
sipStatusCodeValue sipCommonStatusCodeIns renamed to sipStatusCodeValue sipCommonStatusCodeIns renamed to
sipStatusCodeIns sipCommonStatusCodeOuts renamed to sipStatusCodeIns sipCommonStatusCodeOuts renamed to
sipStatusCodeOuts sipCommonStatusCodeStatus renamed to sipStatusCodeOuts sipCommonStatusCodeStatus renamed to
sipStatusCodeRowStatus sipCommonStatusCodeNotifTable renaemd to sipStatusCodeRowStatus sipCommonStatusCodeNotifTable renamed to
sipStatusCodeNotifTable SipCommonStatusCodeNotifEntry renamed sipStatusCodeNotifTable SipCommonStatusCodeNotifEntry renamed
to SipStatusCodeNotifEntry sipCommonStatusCodeNotifEntry to SipStatusCodeNotifEntry sipCommonStatusCodeNotifEntry
renamed to sipStatusCodeNotifEntry sipCommonStatusCodeNotifSend renamed to sipStatusCodeNotifEntry sipCommonStatusCodeNotifSend
renamed to sipStatusCodeNotifSend renamed to sipStatusCodeNotifSend
sipCommonStatusCodeNotifEmitMode renamed to sipCommonStatusCodeNotifEmitMode renamed to
sipStatusCodeNotifEmitMode sipCommonStatusCodeNotifThresh sipStatusCodeNotifEmitMode sipCommonStatusCodeNotifThresh
renamed to sipStatusCodeNotifThresh renamed to sipStatusCodeNotifThresh
sipCommonStatusCodeNotifInterval renamed to sipCommonStatusCodeNotifInterval renamed to
sipStatusCodeNotifInterval sipStatusCodeNotifInterval
* Removed all INFO method specific objects: sipCfgRetryInfo, * Removed all INFO method specific objects: sipCfgRetryInfo,
sipStatsInfoIns, sipStatsInfoOuts, & sipStatsRetryInfos sipStatsInfoIns, sipStatsInfoOuts, and sipStatsRetryInfos
* Clarifying words added to sipStatusCodeNotifTable DESCRIPTION * Clarifying words added to sipStatusCodeNotifTable DESCRIPTION
to explain why it's a seperate table from sipStatusCodesTable. to explain why it's a separate table from sipStatusCodesTable.
o SIP-SERVER-MIB o SIP-SERVER-MIB
* Deleted objects related to 'action' parameter. RFC 3261 * Deleted objects related to 'action' parameter. RFC 3261
section 10.2 deprecates the 'action' parameter deleted 3 section 10.2 deprecates the 'action' parameter deleted 3
objects: sipServerContactDfltAction, sipServerRespectUAAction, objects: sipServerContactDfltAction, sipServerRespectUAAction,
sipContactAction. sipContactAction.
* Deleted pgp-related objects. RFC 3261 section 23 deprecates * Deleted pgp-related objects. RFC 3261 section 23 deprecates
use of pgp deleted 3 objects: sipProxyAuthPgpAlgorithm, use of pgp deleted 3 objects: sipProxyAuthPgpAlgorithm,
sipPgpPrivateKey, sipPgpVersion. sipPgpPrivateKey, sipPgpVersion.
* Removed sipProxyStateTimeout object. Timers G and timer H have * Removed sipProxyStateTimeout object. Timers G and timer H have
been introduced in RFC 3261 for this purpose (see RFC 3261 been introduced in RFC 3261 for this purpose (see RFC 3261
section 17.2.1). section 17.2.1).
* Updated description clause of sipProxyStatefulness. The 3 * Updated description clause of sipProxyStatefulness. The 3
definitions of stateless/statefulness now match the text in RFC definitions of stateless/statefulness now match the text in RFC
3261. 3261.
* Changed DEFVAL for object sipProxyProvideAlternatives. Changed * Changed DEFVAL for object sipProxyProvideAlternatives. Changed
DEFVAL to true to align with RFC 3261 that states that 485 DEFVAL to true to align with RFC 3261 that states that 485
responses SHOULD contain a contact header & 303 MAY... and responses SHOULD contain a contact header and 303 MAY... and
updated REFERENCE clause to "RFC 3261 Sections 13.2.2.2 and updated REFERENCE clause to "RFC 3261 Sections 13.2.2.2 and
16.5". 16.5".
* Removed basic authentication value from sipProxyAuthMethod * Removed basic authentication value from sipProxyAuthMethod
object Per section 22 of rfc 3261, deprecated. object Per section 22 of RFC 3261, deprecated.
* Changed SYNTAX of sipProxyNonceLifeTime from Integer32 to * Changed SYNTAX of sipProxyNonceLifeTime from Integer32 to
Unsigned32. Unsigned32.
* Updated description clause of sipRegDfltRegActiveInterval Per * Updated description clause of sipRegDfltRegActiveInterval Per
RFC 3261 Section 10.2. RFC 3261 Section 10.2.
o SIP-UA-MIB o SIP-UA-MIB
* OBJECT refinement for sipUACfgSipServerStatus added to * OBJECT refinement for sipUACfgSipServerStatus added to
compliance. compliance.
* Changed the object descriptors of sipUACfgSipServerAddrIndex to * Changed the object descriptors of sipUACfgSipServerAddrIndex to
sipUACfgSipServerIndex, and sipUACfgSipServerAddrStatus to sipUACfgSipServerIndex, and sipUACfgSipServerAddrStatus to
sipUACfgSipServerStatus. sipUACfgSipServerStatus.
skipping to change at page 84, line 8 skipping to change at page 82, line 41
configuration objects were added there. This new high-level configuration objects were added there. This new high-level
OID was placed under the existing sipCommonCfgRetry OID and OID was placed under the existing sipCommonCfgRetry OID and
therefore, caused the OIDs for the subsequent groups to change therefore, caused the OIDs for the subsequent groups to change
(incrementing by one). (incrementing by one).
* Objects from tables under sipCommonCfgExpires were added to a * Objects from tables under sipCommonCfgExpires were added to a
new OBJECT-GROUP sipCommonConfigExpiresGroup, and that group new OBJECT-GROUP sipCommonConfigExpiresGroup, and that group
was listed as optional in sipCommonCompliance. was listed as optional in sipCommonCompliance.
* Minor DESCRIPTION change for sipCommonCfgEntry. No behavior * Minor DESCRIPTION change for sipCommonCfgEntry. No behavior
change. change.
* sipServiceOperStatus SYNTAX changed. New values added: * sipServiceOperStatus SYNTAX changed. New values added:
congested & quiescing Old values removed: halted The order of congested and quiescing Old values removed: halted The order of
the enumeration was altered as well. the enumeration was altered as well.
* sipServiceAdminStatus SYNTAX changed. New values added: noop, * sipServiceAdminStatus SYNTAX changed. New values added: noop,
up, down, quieseSessions, and quieseApplications Old values up, down, quieseSessions, and quieseApplications Old values
removed: shutdown, restart, stop, rts. These changes were made removed: shutdown, restart, stop, rts. These changes were made
based on comments from last call reviewer and general known based on comments from last call reviewer and general known
ambiguities in the previous design of the object. ambiguities in the previous design of the object.
* Clarifying changes to the DESCRIPTION of sipServiceStartTime. * Clarifying changes to the DESCRIPTION of sipServiceStartTime.
* Clarifying changes to the DESCRIPTION of sipServiceStartTime. * Clarifying changes to the DESCRIPTION of sipServiceStartTime.
* Clarification of behavior for sipPortStatus while row is * Clarification of behavior for sipPortStatus while row is
'active' 'active'
skipping to change at page 85, line 18 skipping to change at page 84, line 4
objects were added to sipStatusCodesTable to handle possible objects were added to sipStatusCodesTable to handle possible
future classes of response status codes. future classes of response status codes.
* Text referring specifically to Redirect Server in * Text referring specifically to Redirect Server in
sipStatsRedirClassIns and sipStatsRedirClassOuts was removed. sipStatsRedirClassIns and sipStatsRedirClassOuts was removed.
* Text defining protocol behavior in sipStatsServerFailClassIns, * Text defining protocol behavior in sipStatsServerFailClassIns,
sipStatsServerFailClassOuts, sipStatsGlobalFailClassIns, and sipStatsServerFailClassOuts, sipStatsGlobalFailClassIns, and
sipStatsGlobalFailClassOuts was removed. sipStatsGlobalFailClassOuts was removed.
* sipCommonStatusCodeNotifInterval SYNTAX changed from TimeTicks * sipCommonStatusCodeNotifInterval SYNTAX changed from TimeTicks
to Unsigned32 w/ a UNITS of "seconds" added to the definition. to Unsigned32 w/ a UNITS of "seconds" added to the definition.
DEFVAL clause changed accordingly. DEFVAL clause changed accordingly.
* sipStatusCodeNotifTo, sipStatusCodeNotifFrom, * sipStatusCodeNotifTo, sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId, and sipStatusCodeNotifCSeq all had sipStatusCodeNotifCallId, and sipStatusCodeNotifCSeq all had
clarifying changes to their DESCRIPTIONs. Specifically, the clarifying changes to their DESCRIPTIONs. Specifically, the
header name will be part of the object value and example values header name will be part of the object value and example values
were given. were given.
* Clarifying changes to the DESCRIPTION of sipCurrentTransTable * Clarifying changes to the DESCRIPTION of sipCurrentTransTable
and sipTransactionTable. Specifically, these tables are not and sipTransactionTable. Specifically, these tables are not
applicable to transaction stateless SIP Proxy Servers. applicable to transaction stateless SIP Proxy Servers.
* Minor gramatical change to the DESCRIPTION of * Minor grammatical change to the DESCRIPTION of
sipCurrentTransEntry. sipCurrentTransEntry.
* sipTransMethod and sipTransActivityInfo objects were added to * sipTransMethod and sipTransActivityInfo objects were added to
sipTransactionTable while sipTransCallingPartyContentType and sipTransactionTable while sipTransCallingPartyContentType and
sipTransCalledPartyContentType were removed. sipTransCalledPartyContentType were removed.
* Clarifying changes to the DESCRIPTION of sipTransState. * Clarifying changes to the DESCRIPTION of sipTransState.
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 gramatical 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-GROUP based on objects being added and/or removed from OBJECT-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
skipping to change at page 87, line 4 skipping to change at page 85, line 38
conformance section. conformance section.
o SIP-SERVER-MIB o SIP-SERVER-MIB
* Removed sipInformationTryingInterval. * Removed sipInformationTryingInterval.
* Removed sipRxProxyAuthTable. * Removed sipRxProxyAuthTable.
* Removed sipRegRespHasContacts. * Removed sipRegRespHasContacts.
* Removed sipRegContactDfltExpiryDate. * Removed sipRegContactDfltExpiryDate.
* Removed sipRegContactDfltExpiryDuration. * Removed sipRegContactDfltExpiryDuration.
* Removed sipUserPassword. * Removed sipUserPassword.
* sipRequestMaxExpires DESCRIPTION changed to no longer * sipRequestMaxExpires DESCRIPTION changed to no longer
specifically mention 400 response. specifically mention 400 response.
* sipProxyStateful object descriptor changed to * sipProxyStateful object descriptor changed to
sipProxyStatefullness and the SYNTAX changed from TruthValue to sipProxyStatefullness and the SYNTAX changed from TruthValue to
an enumerated INTEGER. an enumerated INTEGER.
* sipProxyStateTimeout DESCRIPTION changed to now reflect only * sipProxyStateTimeout DESCRIPTION changed to now reflect only
INVITE. INVITE.
* Gauge32 was not being IMPORTed. * Gauge32 was not being IMPORTed.
* sipServerContactDfltAction showed up in conformance and other * sipServerContactDfltAction showed up in conformance and other
object descriptions in an older form. object descriptions in an older form.
* sipServerHost replaced with InetAddressType/InetAddress object * sipServerHost replaced with InetAddressType/InetAddress object
pair (sipServerHostAddrType & sipServerHostAddr). pair (sipServerHostAddrType and sipServerHostAddr).
o SIP-UA-MIB o SIP-UA-MIB
* IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex. * IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex.
* sipUACfgSipServerEntry was referencing the wrong auxilliary * 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 9. IANA Considerations
The SIP specification RFC 3261 [7] Section 27.4 establishes the 9.1 Registration of Numeric Identifiers for SIP methods
Method and Response-Code sub-registries under
http://www.iana.org/assignments/sip-parameters.
The SIP-COMMON-MIB requires that unique numeric identifiers be The SIP specification RFC 3261 [RFC3261] section 27.4 establishes the
assigned by IANA for each Method in the above registry. It is sub-registries for SIP Methods and Response Codes under
expected that IANA will create those method identifies in the same http://www.iana.org/assignments/sip-parameters. This document
sub-registry and assign a new method ID for registered methods. For augments the existing sub-registry for SIP Methods to include a
e.g., the mapping of method identifiers to methods will be unique numeric method identifier for each registered SIP method.
represented by a table in the MIB: sipSupportedMethodTable.
SIP-COMMON-MIB sipCommonCfgTable might be populated as: 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 | | sipMethodSupportedIndex | sipMethodSupportedName |
+-------------------------+------------------------+ +-------------------------+------------------------+
| 1 | "INVITE" | | 1 | "ACK" |
| 2 | "ACK" | | 2 | "BYE" |
| 3 | "BYE" | | 3 | "CANCEL" |
| 4 | "CANCEL" | | 5 | "INVITE" |
| 5 | "OPTIONS" | | 8 | "OPTIONS" |
| 6 | "CANCEL" |
| 7 | "INFO" |
| 8 | "SUBSCRIBE" |
| 9 | "NOTIFY" |
+-------------------------+------------------------+ +-------------------------+------------------------+
etc.
The numeric identifiers will also be used in other MIB tables where The following section requests the assignment of a unique numeric
it is sufficient and/or more effective to refer to a method by a identifier for all the SIP methods already registered. For new SIP
number rather than by a string. 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 10. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in the
with a MAX-ACCESS clause of read-write and/or read-create. Such SIP-COMMON-MIB MIB module with a MAX-ACCESS clause of read-write
objects may be considered sensitive or vulnerable in some network and/or read-create. Such objects may be considered sensitive or
environments. The support for SET operations in a non-secure vulnerable in some network environments. The support for SET
environment without proper protection can have a negative effect on operations in a non-secure environment without proper protection can
network operations. have a negative effect on network operations.
These are the tables and objects and their sensitivity/vulnerability: The following read-create object in SIP-COMMON-MIB is used to
o SIP-COMMON-MIB configure the status code statistics that will be monitored by the
The following read-write object is used to control the overal SIP entity:
SIP service in any SIP entity: sipStatusCodeRowStatus:
sipServiceAdminStatus if this object is SET maliciously, it may result in an over
If this object is SET maliciously, it may result in unwanted
operational status, or a failure to obtain SIP services.
The following read-write and read-create objects are used to
control the behavior of the SIP protocol as exhibited by a SIP
entity:
sipOrganization, sipCfgTimerA, sipCfgTimerB, sipCfgTimerC,
sipCfgTimerD, sipCfgTimerE, sipCfgTimerF, sipCfgTimerG,
sipCfgTimerH, sipCfgTimerI, sipCfgTimerJ, sipCfgTimerK,
sipCfgTimerT1, sipCfgTimerT2, sipCfgTimerT4.
If these objects are SET maliciously, it may result in serious
protocol misbehavior or misoperation. In particular, the
objects are related to the core SIP protocol stack timers,
retries and request expiration values: all of these control how
the SIP state machines are executed at runtime. It is
therefore possible that the SIP service be affected, stalled or
completely stopped if erroneous values are SET maliciously.
The following read-create object 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 allocation of resources in a system for the purpose of
accumulating and maintaining statistics. accumulating and maintaining statistics.
The following read-write objects are used to configure the
behavior of certain SNMP notifications potentially generated by The following read-write objects in SIP-COMMON-MIB are used to
a SIP entity: configure the behavior of certain SNMP notifications potentially
generated by a SIP entity:
sipStatusCodeNotifSend, sipStatusCodeNotifEmitMode, sipStatusCodeNotifSend, sipStatusCodeNotifEmitMode,
sipStatusCodeNotifThresh, sipStatusCodeNotifInterval, sipStatusCodeNotifThresh, sipStatusCodeNotifInterval,
sipServiceNotifEnable sipServiceNotifEnable:
If these objects are SET maliciously, it may result in a system If these objects are SET maliciously, it may result in a system
and/or network performance impact due to the generation of SNMP and/or network performance impact due to the generation of SNMP
notifications. notifications.
o SIP-UA-MIB
The following read-create objects are used to configure the
Internet address of SIP servers a SIP User Agent will use to
proxy/redirect SIP calls:
sipUACfgServerAddrType, sipUACfgServerAddr,
sipUACfgServerFunction, sipUACfgServerStatus.
If these objects are SET maliciously, it may result in unwanted
operation, or a failure to obtain SIP services from the user
agent prospective or even theft of service. In particular,
setting the SipUACfgSipServerStatus object instance to the
'destroy' value may result in service disruption.
o SIP-SERVER-MIB
The following read-create objects are managed by Registrar
Servers and contain sensitive or private information about the
address of record of registered users.
sipUserUri & sipUserTableRowStatus
The sensitivity of these objects depends on the role that
Registrar Servers play in the SIP service. In some cases,
these objects, if SET maliciously, may allow unregistered users
to steal service, or may prevent registered users from
accessing the SIP service.
The following read-write objects, if SET maliciously will have
an immediate serious impact on the service:
sipServerHostAddrType & sipServerHostAddr
These objects specify the host part of the URI for the server
providing the SIP resource and it is widely used by SIP servers
in numerous header lines and field. For e.g., the host address
may be used with the Request-URI to check if the server is the
one resolved by the Request-URI, therefore determining whether
to process or forward the request in the case of outbound
proxies, or, as an another common example, it is used by Proxy
Servers acting as strict routers to rewrite the Request-URI.
Setting these objects with improper values may result in
serious service interference or failure.
sipRequestMaxExpires and sipRegMaxContactExpiryDuration: if set
to a zero value and either SIP requests contain an Expires
header or Contact header contain an expires parameter, may
cause the server to never create bindings associated with an
address of record (case of REGISTER request) or may cause
server to expire and cancel invitations (case of INVITE
request).
sipProxyStatefulness: changing the value of this object affects
how transaction states are being handled the Proxy Server and
may result in call feature or service changes.
sipProxyAuthMethod: this object specifies at a maximum what the Some of the readable objects in the MIB modules (i.e., objects with a
authentication methods that may be used by a server. If this MAX-ACCESS other than not-accessible) may be considered sensitive or
object is SET maliciously, it may alter how the level of vulnerable in some network environments. It is thus important to
security used by the server to generate requests and may control even GET and/or NOTIFY access to these objects and possibly
compromise the network security policies. to even encrypt the values of these objects when sending them over
sipRegAllowThirdParty: depending on the authentication policy the network via SNMP.
associated with registration services, setting this object
maliciously to 'true' may allow theft of identity or service.
sipProxyAuthRealm: if this object is SET improperly, and if the
HTTP Digest authentication method is used, it may result in
clients being unable to authenticate and ultimately, in the
server denying service.
The remaining read-write objects, if SET maliciously may have
some effect on the service:
sipProxyRecordRoute: setting this object to true may cause
additional SIP traffic to cross the proxy server and may result
in message avalanches.
The threats posed by the following read-write objects can
either be mitigated by other configuration settings like
read-only objects or they are considered to cause additional
server operations without immediate impact on the servive.
sipProxyRecursion and sipRegDfltRegActiveInterval
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 The following object values may contain private or confidential
customer information like first name, last name, customer customer information like first name, last name, customer
identification, location, company affiliation, the time the identification, location, company affiliation, the time the
information was updated, etc. information was updated, etc.
SipContactDisplayName, SipContactURI, and sipContactDisplayName, sipContactURI, sipContactLastUpdated and
SipContactLastUpdated. sipOrganization.
The sipMethodSupportedTable table contains the list of SIP
methods supported by each entity in the system. Gaining access The sipCommonCfgTable table contains some objects that may help
to this information may allow attackers to build method attackers gain knowledge about the status and operations of the SIP
specific attacks or use unsupported methods to create denial of service. In particular, the object value of sipServiceOperStatus may
service attack scenarios. 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. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), 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 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 allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this set of MIB modules.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see RFC 3410 [RFC3410]), including
including full support for the SNMPv3 cryptographic mechanisms (for full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
11. Contributor Acknowledgments 11. Contributor Acknowledgments
We wish to thank the members of the IETF SIP & SIPPING working groups We wish to thank the members of the IETF SIP and SIPPING working
& the SIP-MIB Design team for their comments and suggestions. groups, and the SIP-MIB Design team for their comments and
Detailed comments were provided by Tom Taylor, Kavitha Patchayappan, suggestions. Detailed comments were provided by Tom Taylor, Kavitha
Dan Romascanu, Cullen Jennins, Orit Levin, AC Mahendran, Mary Barnes Patchayappan, Dan Romascanu, Cullen Jennins, Orit Levin, AC
and Rohan Mahy. Mahendran, Mary Barnes, Rohan Mahy, Bob Penfield, Charles Eckel and
Dean Willis.
12. References 12. References
12.1 Normative References 12.1 Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[2] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
and Applicability Statements for Internet-Standard Management "Introduction and Applicability Statements for
Framework", RFC 3410, December 2002. Internet-Standard Management Framework", RFC 3410,
December 2002.
[3] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC 2578, Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "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,
April 1999. April 1999.
[4] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2788] Freed, N. and S. Kille, "Network Services Monitoring MIB",
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual Conventions RFC 2788, March 2000.
for SMIv2", STD 58, RFC 2579, April 1999.
[5] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
Statements for SMIv2", STD 58, RFC 2580, April 1999. A., Peterson, J., Sparks, R., Handley, M. and E. Schooler,
"SIP: Session Initiation Protocol", RFC 3261, June 2002.
[6] Freed, N. and S. Kille, "Network Services Monitoring MIB", RFC [RFC3291] Daniele, M., Haberman, B., Routhier, S. and J.
2788, March 2000. Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 3291, May 2002.
[7] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., [RFC3427] Mankin, A., Bradner, S., Mahy, R., Willis, D., Ott, J. and
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: B. Rosen, "Change Process for the Session Initiation
Session Initiation Protocol", RFC 3261, June 2002. Protocol (SIP)", BCP 67, RFC 3427, December 2002.
[8] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder, [RFC3515] Sparks, R., "The Session Initiation Protocol (SIP) Refer
"Textual Conventions for Internet Network Addresses", RFC 3291, Method", RFC 3515, April 2003.
May 2002.
12.2 Informational References 12.2 Informational References
[9] Hoffman, P., Masinter, L. and J. Zawinski, "The mailto URL [RFC2368] Hoffman, P., Masinter, L. and J. Zawinski, "The mailto URL
scheme", RFC 2368, July 1998. scheme", RFC 2368, July 1998.
[10] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396, August Resource Identifiers (URI): Generic Syntax", RFC 2396,
1998. 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
CableLabs
858 Coal Creek Circle
Louisville, CO 80027
US
Phone: +1 303 661 9100
Email: jfm@cablelabs.com
Joon Maeng Joon Maeng
5612 Sedona Drive
Austin, TX 78759
US
Phone: Phone: +1 512 418 0590
EMail: jmaeng@ipdialog.com Email: jmaeng@austin.rr.com
Dave Walker Dave Walker
Phone: Email: drwalker@rogers.com
EMail: drwalker@rogers.com
Intellectual Property Statement Intellectual Property Statement
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
skipping to change at page 93, line 41 skipping to change at page 93, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. 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. 

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