draft-ietf-sip-mib-07.txt   draft-ietf-sip-mib-08.txt 
SIP WG K. Lingle SIP WG K. Lingle
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: December 30, 2003 J. Maeng Expires: January 14, 2005 J. Maeng
ipDialog, Inc.
J-F. Mule
CableLabs
D. Walker D. Walker
SS8 Networks, Inc. July 16, 2004
July 2003
Management Information Base for Session Initiation Protocol (SIP) Management Information Base for Session Initiation Protocol (SIP)
draft-ietf-sip-mib-07.txt draft-ietf-sip-mib-08.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as
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 http:// The list of current Internet-Drafts can be accessed at
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 December 30, 2003. This Internet-Draft will expire on January 14, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
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 servers, Redirect servers and Registrars. Agents, Proxy/Redirect servers and Registrars.
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 . . . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . 10 6. Accommodating SIP Extension Methods . . . . . . . . . . . . . 9
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . 10 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1 SIP Textual Conventions . . . . . . . . . . . . . . . . . . 10 7.1 SIP Textual Conventions . . . . . . . . . . . . . . . . . 9
7.2 SIP Common MIB Module . . . . . . . . . . . . . . . . . . . 12 7.2 SIP Common MIB Module . . . . . . . . . . . . . . . . . . 13
7.3 SIP User Agent MIB Module . . . . . . . . . . . . . . . . . 73 7.3 SIP User Agent MIB Module . . . . . . . . . . . . . . . . 54
7.4 SIP Server (Registrar, Redirect & Proxy Server) MIB Module . 78 7.4 SIP Server (Registrar & Proxy/Redirect Server) MIB
8. Changes from Previous Draft Revisions . . . . . . . . . . . 98 Module . . . . . . . . . . . . . . . . . . . . . . . . . . 59
9. Security Considerations . . . . . . . . . . . . . . . . . . 108 8. Changes from Previous Draft Revisions . . . . . . . . . . . . 77
10. Contributor Acknowledgments . . . . . . . . . . . . . . . . 112 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 87
Normative References . . . . . . . . . . . . . . . . . . . . 112 10. Security Considerations . . . . . . . . . . . . . . . . . . 88
Informational References . . . . . . . . . . . . . . . . . . 113 11. Contributor Acknowledgments . . . . . . . . . . . . . . . . 91
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 113 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 91
Intellectual Property and Copyright Statements . . . . . . . 115 12.1 Normative References . . . . . . . . . . . . . . . . . . . . 91
12.2 Informational References . . . . . . . . . . . . . . . . . . 92
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 92
Intellectual Property and Copyright Statements . . . . . . . . 93
1. Conventions 1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [1]. document are to be interpreted as described in RFC 2119 [1].
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 servers, Redirect servers and Registrars. Agents, Proxy/Redirect servers and Registrars. The managed objects
defined in this document are intended to provide basic SIP protocol
management for SIP entities. The management of application-specific
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 [2]. Managed objects are accessed via a virtual information
store, termed the Management Information Base or MIB. MIB objects store, termed the Management Information Base or MIB. MIB objects
are generally accessed through the Simple Network Management Protocol are generally accessed through the Simple Network Management Protocol
(SNMP). Objects in the MIB are defined using the mechanisms defined (SNMP). Objects in the MIB are defined using the mechanisms defined
in the Structure of Management Information (SMI). This memo in the Structure of Management Information (SMI). This memo
specifies a MIB module that is compliant to the SMIv2, which is specifies a MIB module that is compliant to the SMIv2, which is
described in STD 58, RFC 2578 [3], STD 58, RFC 2579 [4] and STD 58, described in STD 58, comprised of RFC 2578 [3], RFC 2579 [4], and
RFC 2580 [5]. RFC 2580 [5].
4. Overview 4. Overview
The Session Initiation Protocol (SIP) RFC 3261 [7] is an application- The Session Initiation Protocol (SIP) RFC 3261 [7] is an application-
layer control (signaling) protocol for creating, modifying, and layer control (signaling) protocol for creating, modifying, and
terminating sessions with one or more participants. These sessions terminating sessions with one or more participants. These sessions
include Internet telephone calls, multimedia distribution, and include Internet telephone calls, multimedia distribution, and
multimedia conferences. This MIB provides some managed objects for multimedia conferences. This MIB provides some managed objects for
SIP entities defined in RFC 3261 - User Agent, Proxy Server, Redirect SIP entities defined in RFC 3261 - User Agent, Proxy/Redirect Server
Server and Registrar. It is provided as a base for the work within and Registrar. It is provided as a base for the work within the
the working group to define a MIB. This MIB is intended to provide working group to define a MIB. This MIB is intended to provide
management of the basic SIP entities. It provides for monitoring of management of the basic SIP entities. It provides for monitoring of
status and protocol statistics, as well as for configuration of SIP status and protocol statistics, as well as for 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, SIP-
SERVER-MIB, SIP-UA-MIB and SIP-TC. SIP-COMMON-MIB contains common SERVER-MIB, SIP-UA-MIB and SIP-TC. SIP-COMMON-MIB contains common
objects used in all the SIP entities. SIP-SERVER-MIB contains objects objects used in all the SIP entities. SIP-SERVER-MIB contains
specific to Registrars, Proxies and Redirect Servers, and SIP-UA-MIB objects specific to Registrars, Proxies/Redirect Servers, and
includes objects specific to User Agents. SIP-TC defines the textual SIP-UA-MIB includes objects specific to User Agents. SIP-TC defines
conventions used throughout MIB modules. The MIB Modules contain the textual conventions used throughout MIB modules. The MIB Modules
following groups of objects: contain following groups of objects:
SIP-COMMON-MIB: Common to all the SIP entities SIP-COMMON-MIB: 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 SIP protocol
version, operational and administrative status, SIP version, operational and administrative status, SIP
organization name, max number of SIP sessions an entity can organization name, max number of SIP dialogs an entity can
manage, etc. 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 SIP
stateful proxy entities. stateful proxy entities.
* sipCommonCfgRetry: This object group defines retry counter
configuration objects applicable to SIP user agent and SIP
stateful proxy entities.
* sipCommonCfgExpires: This object group defines Expires header
value configuration objects applicable to SIP user agent and
SIP stateful proxies
* 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 SIP requests &
responses in/out, total number of transactions, etc. responses in/out, total number of transactions, etc.
* 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 per method statistics objects applicable to all
SIP entities, including the total number of SIP requests for SIP entities, including the total number of SIP requests for
the Invite, Ack, Bye, Cancel, Options and /Register methods. the Invite, Ack, Bye, Cancel, Options and Register methods.
Retransmissions, where appropriate, are also included in these
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/out per class of
response (1xx, 2xx, etc.) response (1xx, 2xx, 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 retries sent on a per method
basis. 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 a counter of the number of SIP
requests received with unsupported URIs. requests received with unsupported URIs.
* sipCommonNotifObjects: This object group defines * sipCommonNotifObjects: This object group defines
accessible-for-notify objects that are relate to the SNMP accessible-for-notify objects that 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, Proxy and Redirect SIP-SERVER-MIB: Groups of objects for Registrars and Proxy/Redirect
Servers 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.
* sipServerStats: This object group is currently empty and is
created for future extensions of the SIP MIB.
* sipProxyCfg: This object group defines Proxy Server * sipProxyCfg: This object group defines Proxy Server
configuration objects including the maximum duration in the configuration objects including the maximum duration in the
Expires header, the proxy mode of operation (stateless, Expires header, the proxy mode of operation (stateless,
stateful, call stateful), the cancellation of outstanding stateful, call stateful), the cancellation of outstanding
branch requests 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 all 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
* sipRedirCfg: This object group is currently empty and is configuration objects including the ability for a registrar to
created for future extensions of the SIP MIB. accept third-party registration, the maximum expiry that may be
requested by UAs, the maximum number of users, currently
* sipRedirStats: This object group is currently empty and is registered users, etc.
created for future extensions of the SIP MIB. * sipRegStats: This object group contains the summary statistics
objects for Registrar servers, including the number of REGISTER
* sipRegCfg: This object group is currently empty and is created requests that have been accepted or rejected.
for future extensions of the SIP MIB.
* sipRegStats: This object group is currently empty and is
created for future extensions of the SIP MIB.
SIP-UA-MIB: Group of objects for User Agents. SIP-UA-MIB: Group of objects for User Agents.
o sipUAMIBObjects o sipUAMIBObjects
* sipUACfgServer: This group specifies SIP server configuration
* sipUACfgSipServer: This 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 proxy or calls.
redirect calls.
To conform with this specification, an SNMP agent MUST implement To conform with this specification, an SNMP agent MUST implement
SIP-TC, plus the SIP-COMMON-MIB and one of the SIP entity-type- SIP-TC, plus the SIP-COMMON-MIB and one of the SIP entity-type-
specific MIB modules (SIP-SERVER-MIB or SIP-UA-MIB) as applicable for specific MIB modules (SIP-SERVER-MIB or SIP-UA-MIB) as applicable for
each instance of a SIP entity being managed. If a device has more each instance of a SIP entity being managed. If a device has more
than one SIP entity or multiple instances of the same entity, type it than one SIP entity or multiple instances of the same entity type, it
MUST implement multiple SIP modules. Section 4.2 describes handling MUST implement multiple SIP modules. Section 4.2 describes handling
of multiple instances in detail. of multiple instances in detail.
5.1 Textual Conventions 5.1 Textual Conventions
The data type SipTransportProtocol is used as Textual Conventions in The data types SipTransportProtocol, SipEntityRole,
this document. These Textual Conventions have NO effect on either SipOptionTagHeaders, and SipMethodIdentifier are used as Textual
the syntax or the semantics of any managed object. Objects defined Conventions in this document. These Textual Conventions have NO
using these conventions are always encoded by means of the rules that effect on either the syntax or the semantics of any managed object.
define their primitive type. Hence, no changes to the SMI or the Objects defined using these conventions are always encoded by means
SNMP are necessary to accommodate these Textual Conventions. They are of the rules that define their primitive type. Hence, no changes to
adopted merely for the convenience of readers. 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 There is a requirement to be able to support multiple instances of
various SIP MIB modules in the context of a single system having a various SIP MIB modules in the context of a single system having a
single SNMP agent. single SNMP agent.
This requirement is solved by using the framework provided by the This requirement is solved by using the framework provided by the
NETWORK-SERVICES-MIB, RFC 2788 [6]. A device implementing the SIP MIB NETWORK-SERVICES-MIB, RFC 2788 [6]. A device implementing the SIP
MUST support the NETWORK-SERVICES-MIB and, at a minimum, it MUST MIB MUST support the NETWORK-SERVICES-MIB and, at a minimum, it MUST
support the applIndex and applName objects in applTable. The support the applIndex and applName objects in applTable. The
following applName conventions will be adopted: following applName conventions will be adopted:
o for a SIP Proxy entity, applName MUST be equal to "sip_proxy" o for a SIP Proxy entity, applName MUST be equal to "sip_proxy"
o for a SIP Redirect entity, applName MUST be equal to
"sip_redirect"
o for a SIP Registrar entity, applName MUST be equal to o for a SIP Registrar entity, applName MUST be equal to
"sip_registrar" "sip_registrar"
o for a SIP User Agent entity, applName MUST be equal to "sip_ua" o for a SIP User Agent entity, applName MUST be equal to "sip_ua"
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 for the
combined server entity MUST reflect the appropriate combination. combined server entity MUST reflect the appropriate combination.
For example, "sip_proxy_redirect" or "sip_proxy_registrar". In order to faciliate consistent agent behavior and management
application expectations, the following order of names is
RECOMMENDED:
* if Proxy exists, list first.
* if Proxy & Redirect exists, list Redirect second.
* if Registrar exists, always list last.
For example "sip_proxy", "sip_proxy_registrar",
"sip_proxy_redirect", "sip_proxy_redirect_registrar", or
"sip_registrar".
The SNMP agent MAY support any combination of the other attributes in The SNMP agent MAY support any combination of the other attributes in
applTable. If the following objects are supported, the object values applTable. If the following objects are supported, the object values
SHOULD be populated as follows: SHOULD be 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: value MUST be identical to sipServiceStartTime defined
in the SIP-COMMON-MIB module, in the SIP-COMMON-MIB module,
o applOperStatus: value SHOULD reflect the operational status o applOperStatus: value SHOULD reflect the operational status
defined in sipServiceOperStatus, at least by means of a mapping, defined in sipServiceOperStatus, at least by means of a mapping,
o applLastChange: value MUST be identical to sipServiceLastChange o applLastChange: value MUST be identical to sipServiceLastChange
defined in the SIP-COMMON module. defined in the SIP-COMMON module.
Note: There are a number of other objects in the applTable. They are Note: There are a number of other objects in the applTable. They are
not included for the sake of brevity and for the fact that they do not included for the sake of brevity and for the fact that they do
not enhance the concept being presented. not enhance the concept being presented.
Example 1: Example 1:
The tables below illustrate how a system acting as both Proxy and The tables below illustrate how a system acting as both Proxy and
skipping to change at page 8, line 24 skipping to change at page 7, line 43
while sipProxyCfgTable in SIP-SERVER-MIB might be populated as: while sipProxyCfgTable in SIP-SERVER-MIB might be populated as:
+-----------+----------------------+----------------------+-----+ +-----------+----------------------+----------------------+-----+
| applIndex | sipRequestMaxExpires | sipProxyStatefulness | ... | | applIndex | sipRequestMaxExpires | sipProxyStatefulness | ... |
+-----------+----------------------+----------------------+-----+ +-----------+----------------------+----------------------+-----+
| 1 | 3600 | stateless(1) | | | 1 | 3600 | 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 | drwalker@ss8.com | | | 2 | 1 | bob@example.com | |
| 2 | 2 | jmaeng@ipdialog.com | | | 2 | 2 | alice@example.com | |
| 2 | 3 | klingle@cisco.com | | | 2 | 3 | jim@example.com | |
| 2 | 4 | jfm@cablelabs.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:
+-----------+-----------------------+------------------------------+ +-----------+-----------------------+------------------------------+
skipping to change at page 9, line 23 skipping to change at page 8, line 38
while sipProxyCfgTable in SIP-SERVER-MIB is populated as: while sipProxyCfgTable in SIP-SERVER-MIB is populated as:
+-----------+----------------------+----------------------+ +-----------+----------------------+----------------------+
| applIndex | sipMaxRequestExpires | sipProxyStatefulness | | applIndex | sipMaxRequestExpires | sipProxyStatefulness |
+-----------+----------------------+----------------------+ +-----------+----------------------+----------------------+
| 1 | 3600 | stateless(1) | | 1 | 3600 | 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 | drwalker@ss8.com | | | 2 | 1 | bob@example.com | |
| 2 | 2 | jmaeng@ipdialog.com | | | 2 | 2 | alice@example.com | |
| 2 | 3 | klingle@cisco.com | | | 2 | 3 | kevin@example.com | |
| 2 | 4 | jfm@cablelabs.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 NETWORK-SERVICES-
MIB compliance. MIB compliance.
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 |
skipping to change at page 10, line 9 skipping to change at page 9, line 27
| 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 The core set of SIP methods is defined in RFC 3261 [7]. Other IETF
Internet- Draft documents and RFCs define additional methods. In the RFCs define additional methods. In the future, more methods may be
future more methods may be defined. In order to avoid having to defined. In order to avoid having to update the SIP-COMMON-MIB
update the SIP-COMMON-MIB module to accommodate these extension module to accommodate these extension methods, we use a Method
methods, there are various extension method tables throughout the MIB Identifier (SipMethodIdentifier textual-convention) to represent all
module. There are no per method objects defined in the other MIB SIP methods registered with IANA. See IANA Consideration section.
modules.
The sipExtMethodSupportedTable is the main table for listing all of
the extension methods supported by a system. The table is
informational in nature and populated by the system. Entries cannot
be added or deleted by a SNMP manager. The other extension method
tables in the MIB are augmentations of this table.
The other extension method tables defined in the SIP-COMMON-MIB are: For example, the sipMethodSupportedTable is the main table for
sipCommonCfgTimerExtMethodTable, sipCommonCfgRetryExtMethodTable, listing all of the SIP methods supported by a system, including the
sipStatsExtMethodTable, and sipCommonStatsRetryExtMethodTable. SIP methods defined in RFC 3261 [7] and other SIP methods registered
with IANA. The table is informational in nature and 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,
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 "200307300000Z" LAST-UPDATED "200407160000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
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
ipDialog, Inc.
postal: 7701 N. Lamar Blvd., Suite 304 postal:
Austin, TX 78752-1023
USA email: jmaeng@austin.rr.com
email: jmaeng@ipdialog.com phone:
phone: +1 512 371 1770
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc.
postal: 495 March Road postal:
Kanata, ON K2K 3G1
Canada email: drwalker@rogers.com
email: drwalker@ss8.com phone:
phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 400 Centennial Parkway 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 "
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 (2003). This version Copyright (C) The Internet Society (2004). 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 "200307300000Z" REVISION "200407160000Z"
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 xx }
-- RFC Ed: replace xx with actual IANA assigned number and remove this note -- RFC Ed: replace xx with actual IANA assigned number and remove this note
-- --
-- Textual Conventions -- Textual Conventions
-- --
skipping to change at page 12, line 28 skipping to change at page 11, line 42
bit 3 : Stream Control Transmission Protocol. bit 3 : Stream Control Transmission Protocol.
bit 4 : Transport Layer Security Protocol." bit 4 : Transport Layer Security Protocol."
SYNTAX BITS { SYNTAX BITS {
other(0), -- none of the following other(0), -- none of the following
udp(1), udp(1),
tcp(2), tcp(2),
sctp(3), sctp(3),
tls(4) tls(4)
} }
-- REFERENCE "RFC 3261, Section 18" -- REFERENCE "RFC 3261, Section 18"
SipEntityRole ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This convention defines the role of a SIP entity.
Examples of SIP entities are proxies, user agents,
redirect servers, registrars or combinations of
the above."
SYNTAX BITS {
other(0),
userAgent(1),
proxyServer(2),
redirectServer(3),
registrarServer(4)
}
SipOptionTagHeaders ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This convention defines the header fields that use
the option tags per section 19.2 of RFC 3261.
These tags are used in Require (Section 20.32),
Proxy-Require (Section 20.29), Supported
(Section 20.37) and Unsupported (Section 20.40)
header fields."
SYNTAX BITS {
require(0), -- Require header
proxyRequire(1), -- Proxy-Require header
supported(2), -- Supported header
unsupported(3) -- Unsupported header
}
-- REFERENCE "RFC 3261, Section 19.2"
SipMethodIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This is an IETF Assigned Numbers Authority (IANA)
assigned number that uniquely identifies a SIP
method. The scope of uniqueness is the context
of all defined SIP methods.
Experimental support of extension methods is
acceptable and expected. Extention methods are
those defined in Internet-Draft documents but
not yet allocated an official number by IANA.
To support experimental extension methods, any
object using this textual convention as syntax
MAY return/accept a method identifier value other
than those defined by IANA. That system MUST
ensure no collisions with officially assigned
method identifier values and MUST provide a
identifier to method name mapping via a mechanism
like sipMethodSupportedTable."
SYNTAX Unsigned32 (1..4294967295)
END END
7.2 SIP Common MIB Module 7.2 SIP Common MIB Module
SIP-COMMON-MIB DEFINITIONS ::= BEGIN SIP-COMMON-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
Counter32, Counter32,
Gauge32, Gauge32,
TimeTicks, TimeTicks,
Unsigned32, Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
RowStatus, RowStatus,
TruthValue TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE,
MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
SipTransportProtocol SipTransportProtocol,
SipMethodIdentifier,
SipEntityRole,
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 "200307300000Z" LAST-UPDATED "200407160000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
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
ipDialog, Inc.
postal: 7701 N. Lamar Blvd., Suite 304 postal:
Austin, TX 78752-1023
USA email: jmaeng@austin.rr.com
email: jmaeng@ipdialog.com phone:
phone: +1 512 371 1770
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc.
postal: 495 March Road postal:
Kanata, ON K2K 3G1
Canada email: drwalker@rogers.com
email: drwalker@ss8.com phone:
phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 400 Centennial Parkway 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 "
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 and Redirect common to SIP User Agents (UAs), Proxy/Redirect
Servers, and Registrars. Objects specific to each of Servers, and Registrars. 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.
A User Agent is an application that contains both a User Agent (UA): A logical entity that can act as both
User Agent Client (UAC) and a User Agent Server (UAS). a user agent client and user agent server.
A UAC is an application that initiates a SIP request. User Agent Client (UAC): A user agent client is a logical
A UAS is an application that contacts the user when a entity that creates a new request, and then uses the client
SIP request is received and that returns a response on transaction state machinery to send it. The role of UAC
behalf of the user. The response accepts, rejects, or lasts only for the duration of that transaction. In other
redirects the request. words, if a piece of software initiates a request, it acts
as a UAC for the duration of that transaction. If it
receives a request later, it assumes the role of a user
agent server for the processing of that transaction.
User Agent Server (UAS): A user agent server is a logical
entity that generates a response to a SIP request. The
response accepts, rejects, or redirects the request. This
role lasts only for the duration of that transaction. In
other words, if a piece of software responds to a request,
it acts as a UAS for the 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.
A Proxy Server acts as both a client and a server. Proxy, Proxy Server: An intermediary entity that acts
It accepts requests from other clients, either as both a server and a client for the purpose of making
responding to them or passing them on to other requests on behalf of other clients. A proxy server
servers, possibly after modification. primarily plays the role of routing, which means its job
is to ensure that a request is sent to another entity
'closer' to the targeted user. Proxies are also useful
for enforcing policy. A proxy interprets, and, if
necessary, rewrites specific parts of a request message
before forwarding it.
A Redirect Server accepts requests from clients and Redirect Server: A redirect server is a user agent server
returns zero or more addresses to that client. Unlike that generates 3xx responses to requests it receives,
a Proxy Server it does not initiate requests. Unlike directing the client to contact an alternate set of URIs.
a User Agent Server it does not accept calls.
A Registrar Server accepts REGISTER requests. Registrar: A registrar is a server that accepts REGISTER
A Registrar Server is typically co-located with a requests and places the information it receives in those
Proxy or Redirect Server. requests into the location service for the domain it handles.
Copyright (C) The Internet Society (2003). This version Copyright (C) The Internet Society (2004). 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 "200307300000Z" REVISION "200407160000Z"
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 xx }
-- RFC Ed: replace xx with actual IANA assigned number and remove this note -- RFC Ed: replace xx 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
skipping to change at page 15, line 24 skipping to change at page 16, line 15
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 }
-- Method retry configuration
sipCommonCfgRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 }
-- Expires header configuration -- Expires header configuration
sipCommonCfgExpires OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 } sipCommonCfgExpires OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 }
-- SIP message summary statistics -- SIP message summary statistics
sipCommonStatsSummary OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 } sipCommonStatsSummary OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 }
-- Per method statistics -- Per method statistics
sipCommonStatsMethod OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 } sipCommonStatsMethod OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 }
-- Per Status code or status code class statistics -- Per Status code or status code class statistics
sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 } sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 }
-- Transaction statistics -- Transaction statistics
sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 } sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 }
-- Method retry statistics -- Method retry statistics
sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 } sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 }
-- Other statistics -- Other statistics
sipCommonStatsOther OBJECT IDENTIFIER ::= { sipCommonMIBObjects 10 } sipCommonStatsOther OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 }
-- Accessible-for-notify objects -- Accessible-for-notify objects
sipCommonNotifObjects OBJECT IDENTIFIER ::= { sipCommonMIBObjects 11 } sipCommonNotifObjects OBJECT IDENTIFIER ::= { sipCommonMIBObjects 10 }
-- --
-- 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 16, line 32 skipping to change at page 17, line 30
::= { sipCommonCfgTable 1 } ::= { sipCommonCfgTable 1 }
SipCommonCfgEntry ::= SipCommonCfgEntry ::=
SEQUENCE { SEQUENCE {
sipProtocolVersion SnmpAdminString, sipProtocolVersion SnmpAdminString,
sipServiceOperStatus INTEGER, sipServiceOperStatus INTEGER,
sipServiceAdminStatus INTEGER, sipServiceAdminStatus INTEGER,
sipServiceStartTime TimeTicks, sipServiceStartTime TimeTicks,
sipServiceLastChange TimeTicks, sipServiceLastChange TimeTicks,
sipOrganization SnmpAdminString, sipOrganization SnmpAdminString,
sipMaxSessions Unsigned32, sipMaxTransactions Unsigned32,
sipRequestUriHostMatching TruthValue,
sipServiceNotifEnable BITS, sipServiceNotifEnable BITS,
sipEntityType INTEGER 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
skipping to change at page 18, line 4 skipping to change at page 18, line 50
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 sipServiceAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noop(1), noop(1),
up(2), up(2),
down(3), down(3),
reset(4), reset(4),
quiesceSessions(5), quiesceDialogs(5),
quiesceApplication(6) quiesceApplication(6)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to affect the overall operational "This object is used to affect the overall operational
state of the SIP application. When read, this object state of the SIP application. When read, this object
always return a value of noop(1) since sipServiceOperStatus always return a value of noop(1) since sipServiceOperStatus
reflects the actual operational status. reflects the actual operational status.
noop : Setting this object to a noop value noop : Setting this object to a noop value
has no effect; when read, this value has no effect; when read, this value
is always returned. is always returned.
up : Enable the application. up : Enable the application.
down : Abrupt shutdown. Immediately terminate. down : Abrupt shutdown. Immediately terminate.
reset : Restart application, reinitialize data. reset : Restart application, reinitialize data.
quiesceSessions : Enable quiescence mode. Stop accepting quiesceDialogs : Enable quiescence mode. Stop accepting
any new SIP sessions. Stop processing any new SIP dialogs. Stop processing
new transactions except for transactions new transactions except for transactions
associated with an existing session or associated with an existing dialog or
call. call.
quiesceApplications : Enable quiescence mode. Stop processing quiesceApplications : Enable quiescence mode. Stop processing
new SIP transactions except for new SIP transactions except for
transactions associated with existing transactions associated with existing
applications. The exact application applications. The exact application
behavior SHOULD be specified by the behavior SHOULD be specified by the
implementation." implementation."
::= { sipCommonCfgEntry 3 } ::= { sipCommonCfgEntry 3 }
sipServiceStartTime OBJECT-TYPE sipServiceStartTime OBJECT-TYPE
skipping to change at page 19, line 22 skipping to change at page 20, line 20
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 6 }
sipMaxSessions 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
sessions that the SIP entity can manage." transactions that the SIP entity can manage. In general
the value of this object SHOULD reflect a level of
transaction processing that is considered high enough
to impact the systems CPU and/or memory resources to
the point of deteriorating SIP call processing but not
high enough to cause catastrophic system failure."
::= { sipCommonCfgEntry 7 } ::= { sipCommonCfgEntry 7 }
sipRequestUriHostMatching OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies whether or not the host in
RequestURI MUST match server's host name.
If the value of this object is 'true', then the server
requires a match, and if the RequestURI doesn't match the
server's host name, a Location Service MAY be used to
obtain information about a callee's possible location(s)
or a 404 Not Found status code is returned by the server.
If the value is 'false', then no match is required."
REFERENCE
"RFC 3261, Section 8.1.1.1"
::= { sipCommonCfgEntry 8 }
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
"This object specifies which SIP service related "This object specifies which SIP service related
skipping to change at page 20, line 19 skipping to change at page 21, line 4
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 9 } ::= { sipCommonCfgEntry 8 }
sipEntityType OBJECT-TYPE sipEntityType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX SipEntityRole
unknown(1),
userAgent(2),
proxyServer(3),
redirectServer(4),
proxyRedirectServer(5),
registrar(6)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the type of SIP entity " This object identifies the list of SIP entities this
this row if related to." row is related to. It is defined as a bit map. Each
::= { sipCommonCfgEntry 10 } bit represents a type of SIP entity.
If a bit has value 1, the SIP entity represented by
this row plays the role of this entity type.
If a bit has value 0, the SIP entity represented by
this row does not act as this entity type
Combinations of bits can be set when the SIP entity
plays multiple SIP roles."
::= { sipCommonCfgEntry 9 }
-- --
-- Support for multiple ports -- Support for multiple ports
-- --
sipPortTable OBJECT-TYPE sipPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipPortEntry SYNTAX SEQUENCE OF SipPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the list of ports that each SIP entity "This table contains the list of ports that each SIP entity
in this system is allowed to use. These ports can be in this system is allowed to use. These ports can be
advertised using the Contact header in a REGISTER request advertised using the Contact header in a REGISTER request
or response." or response."
::= { sipCommonCfgBase 2 } ::= { sipCommonCfgBase 2 }
sipPortEntry OBJECT-TYPE sipPortEntry OBJECT-TYPE
SYNTAX SipPortEntry SYNTAX SipPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 21, line 28 skipping to change at page 22, line 11
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, sipPort } INDEX { applIndex, sipPort }
::= { sipPortTable 1 } ::= { sipPortTable 1 }
SipPortEntry ::= SipPortEntry ::=
SEQUENCE { SEQUENCE {
sipPort InetPortNumber, sipPort InetPortNumber,
sipTransportRcv SipTransportProtocol, sipTransportRcv SipTransportProtocol
sipTransportSnd SipTransportProtocol,
sipPortStatus RowStatus
} }
sipPort OBJECT-TYPE sipPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects a particular port that can be used by "This object reflects a particular port that can be used by
the SIP application." the SIP application."
::= { sipPortEntry 1 } ::= { sipPortEntry 1 }
sipTransportRcv OBJECT-TYPE sipTransportRcv OBJECT-TYPE
SYNTAX SipTransportProtocol SYNTAX SipTransportProtocol
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the transport protocol the SIP "This object will specify the transport protocol the SIP
entity will use to receive SIP messages. entity will use to receive SIP messages.
This object is a bit map. Each bit represents a transport This object is a bit map. Each bit represents a transport
protocol. If a bit has value 1, then that transport protocol protocol. If a bit has value 1, then that transport protocol
is currently being used. If a bit has value 0, then that is currently being used. If a bit has value 0, then that
transport protocol is currently not being used." transport protocol is currently not being used."
::= { sipPortEntry 2 } ::= { sipPortEntry 2 }
sipTransportSnd OBJECT-TYPE
SYNTAX SipTransportProtocol
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object will specify the transport protocol the SIP
entity will use to send SIP messages.
This object is a bit map. Each bit represents a transport
protocol. If a bit has value 1, then that transport protocol
is currently being used. If a bit has value 0, then that
transport protocol is currently not being used."
::= { sipPortEntry 3 }
sipPortStatus 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 by a manager. The row
associated with port 5060 need not be created and cannot
be deleted. It is always present in the table. It is
implementation specific as to whether objects in this table
can be set while a row is 'active'."
::= { sipPortEntry 4 }
-- --
-- Support for multiple non-SIP URI schemes -- Support for SIP option tags (SIP extensions).
-- SIP extensions MAY be supported or required by SIP entities.
-- --
sipUriSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUriSupportedEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains a list of URI schemes supported by each
SIP entity in this system. These are in addition to the SIP
URI which MUST necessarily be supported. Normally the
list of URI schemes supported by an entity is static
(i.e. will not change over time).
A URI is a Uniform Resource Identifier (as defined in RFC
2396).
URI schemes could, for example, contain URLs for phones, fax,
or irc (if they were defined) or a mailto: (RFC 2368) URL."
REFERENCE
"RFC 3261, Section 20.10"
::= { sipCommonCfgBase 3 }
sipUriSupportedEntry OBJECT-TYPE
SYNTAX SipUriSupportedEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A particular non-SIP URI supported by the SIP entity.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot."
INDEX { applIndex, sipUriSupportedIndex }
::= { sipUriSupportedTable 1 }
SipUriSupportedEntry ::=
SEQUENCE {
sipUriSupportedIndex Unsigned32,
sipUriSupported SnmpAdminString
}
sipUriSupportedIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object uniquely identifies a conceptual row
in the table."
::= { sipUriSupportedEntry 1 }
sipUriSupported OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates a particular non-SIP URI scheme
supported by the SIP entity. Only the scheme itself
(as described in RFC 2396) is indicated. For example,
if the mailto: URLs are supported, then the table entry
contains 'mailto' without the colon."
REFERENCE
"RFC 2396 section 3"
::= { sipUriSupportedEntry 2 }
-- sipOptionTagTable OBJECT-TYPE
-- Support for features which MAY be requested in Proxy-Require SYNTAX SEQUENCE OF SipOptionTagEntry
-- and Require headers
--
sipFtrSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipFtrSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of the features "This table contains a list of the SIP option tags
supported by each SIP entity in this system, and which (SIP extensions) that either required, supported, or
MAY be REQUIRED by a peer. Definition of non-standard unsupported by the SIP entity.
features is outside the scope of SIP, which only provides These option tags are used in the Require, Proxy-Require,
mechanisms whereby support for specific features MAY be Supported and Unsupported header fields.
signalled or requested.
As and example of a non-standard feature, a user agent Example: if a user agent client supports and requires the
client MAY require that a server support the server to support reliability of provisional
'com.example.billing' feature, which it would responses, this table contains a row with the
indicate in a Require header. Such a client would have string '100rel' in sipOptionTag and the value
a row in its sipFtrSupportedTable containing the string 0xA0 in sipOptionTagHeaderField.
'com.example.billing'. Similarly, a server which is
capable of handling requests for such features would list
the string in its sipFtrSupportedTable.
If a server does not support the required feature If a server does not support the required feature
(indicated in a Require header to a UAS, or in a Proxy- (indicated in a Require header to a UAS, or in a Proxy-
Require to a Proxy Server), the server returns a 420 Bad Require to a Proxy Server), the server returns a 420 Bad
Extension listing the feature in an Unsupported header. Extension listing the feature in an Unsupported header.
Normally the list of such features supported by an entity Normally the list of such features supported by an entity
is static (i.e. will not change over time)." is static (i.e. will not change over time)."
REFERENCE REFERENCE
"RFC 3261, Section 19.2" "RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40"
::= { sipCommonCfgBase 4 } ::= { sipCommonCfgBase 3 }
sipFtrSupportedEntry OBJECT-TYPE sipOptionTagEntry OBJECT-TYPE
SYNTAX SipFtrSupportedEntry SYNTAX SipOptionTagEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular feature supported by the SIP "A particular SIP option tag (extension) supported or
entity, and which MAY be REQUIRED by a peer. unsupported by the SIP entity, and which may be supported
or required by a peer.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and uniquely identify these instances of SIP entities and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788). NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot." and their value SHOULD be kept at reboot."
INDEX { applIndex, sipFtrSupportedIndex } INDEX { applIndex, sipOptionTagIndex }
::= { sipFtrSupportedTable 1 } ::= { sipOptionTagTable 1 }
SipFtrSupportedEntry ::= SipOptionTagEntry ::=
SEQUENCE { SEQUENCE {
sipFtrSupportedIndex Unsigned32, sipOptionTagIndex Unsigned32,
sipFtrSupported SnmpAdminString sipOptionTag SnmpAdminString,
sipOptionTagHeaderField SipOptionTagHeaders
} }
sipFtrSupportedIndex OBJECT-TYPE sipOptionTagIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in the "This object uniquely identifies a conceptual row in the
table." table."
::= { sipFtrSupportedEntry 1 } ::= { sipOptionTagEntry 1 }
sipFtrSupported OBJECT-TYPE sipOptionTag OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a particular feature "This object indicates the SIP option tag.
which is supported by the SIP entity." The option tag names are registered with
::= { sipFtrSupportedEntry 2 } IANA and available at http://www.iana.org."
::= { sipOptionTagEntry 2 }
sipOptionTagHeaderField OBJECT-TYPE
SYNTAX SipOptionTagHeaders
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether the SIP option tag is
supported (Supported header), unsupported (Unsupported
header), required (Require or Proxy-Require header) by
the SIP entity.
A SIP option tag may be both supported and required."
::= { sipOptionTagEntry 3 }
-- --
-- Support for extension methods -- Supported SIP Methods
-- --
sipExtMethodSupportedTable OBJECT-TYPE sipMethodSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipExtMethodSupportedEntry SYNTAX SEQUENCE OF SipMethodSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of extension methods supported "This table contains a list of methods supported
by each SIP entity in this system. These are in addition by each SIP entity in this system. This MAY include,
to the standard set of SIP methods discussed in Section but is not limited to, the standard set of SIP methods
7.1 of RFC 3261. Any additional methods that MAY be discussed in Section 7.1 of RFC 3261. Any additional
incorporated into the SIP protocol SHOULD be represented methods that MAY be incorporated into the SIP protocol
by this table without any requirement to update this MIB. can be represented by this table without any requirement
to update this MIB.
The table is informational in nature; conveying to the NMS The table is informational in nature; conveying to the NMS
capabilities of the managed system." capabilities of the managed system.
::= { sipCommonCfgBase 5 }
sipExtMethodSupportedEntry OBJECT-TYPE From a protocol point of view, the list of methods
SYNTAX SipExtMethodSupportedEntry advertised by the SIP entity in the Allow header (Section
20.5 of RFC 3261) MUST be consistent with the methods
reflected in this table."
::= { sipCommonCfgBase 4 }
sipMethodSupportedEntry OBJECT-TYPE
SYNTAX SipMethodSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular extension method supported by the SIP entity. "A particular method supported by the SIP entity.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and uniquely identify these instances of SIP entities and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788). NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot." and their value SHOULD be kept at reboot."
INDEX { applIndex, sipExtMethodSupportedIndex } INDEX { applIndex, sipMethodSupportedIndex }
::= { sipExtMethodSupportedTable 1 } ::= { sipMethodSupportedTable 1 }
SipExtMethodSupportedEntry ::= SipMethodSupportedEntry ::=
SEQUENCE { SEQUENCE {
sipExtMethodSupportedIndex Unsigned32, sipMethodSupportedIndex SipMethodIdentifier,
sipExtMethodName SnmpAdminString sipMethodName SnmpAdminString
} }
sipExtMethodSupportedIndex OBJECT-TYPE sipMethodSupportedIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX SipMethodIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row "This object uniquely identifies a conceptual row
in the table." in the table and reflects an assigned number used
::= { sipExtMethodSupportedEntry 1 } to identifier a specific SIP method.
sipExtMethodName OBJECT-TYPE This identifier is suitable for referenceing the
associated method throughout this and other MIBs
supported by this managed system."
::= { sipMethodSupportedEntry 1 }
sipMethodName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the supported extension method's name. "This object reflects the supported method's name.
The method name MUST be all upper case (eg, 'FOO')." The method name MUST be all upper case (eg, 'FOO')."
::= { sipExtMethodSupportedEntry 2 } ::= { sipMethodSupportedEntry 2 }
-- --
-- SIP Timer Configuration -- SIP Timer Configuration
-- --
sipCommonCfgTimerTable OBJECT-TYPE sipCommonCfgTimerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgTimerEntry SYNTAX SEQUENCE OF SipCommonCfgTimerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains timer configuration objects applicable "This table contains timer configuration objects applicable
skipping to change at page 32, line 44 skipping to change at page 31, line 47
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 }
-- --
-- Initial Timers Extensions: support for extension methods
--
sipCommonCfgTimerExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgTimerExtMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains retransmit timers for each SIP
extension method this entity supports.
The applicable T2 timer value for timers configured
in this table is that of the sipCfgTimerT2 object
with the same applIndex value."
::= { sipCommonCfgTimer 2 }
sipCommonCfgTimerExtMethodEntry OBJECT-TYPE
SYNTAX SipCommonCfgTimerExtMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This row contains timer value information for
a particular extension method.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot."
AUGMENTS { sipExtMethodSupportedEntry }
::= { sipCommonCfgTimerExtMethodTable 1 }
SipCommonCfgTimerExtMethodEntry ::=
SEQUENCE {
sipCfgTimerExtMethodTimer Unsigned32
}
sipCfgTimerExtMethodTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the time a SIP entity will wait
for a response to the extension method request before
retransmitting. The retransmit timer doubles after
each retransmission, ensuring an exponential backoff
in network traffic."
::= { sipCommonCfgTimerExtMethodEntry 1 }
--
-- SIP Retry Configuration
--
sipCommonCfgRetryTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgRetryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains retry configuration objects applicable
to SIP user agent and SIP proxies."
::= { sipCommonCfgRetry 1 }
sipCommonCfgRetryEntry OBJECT-TYPE
SYNTAX SipCommonCfgRetryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of retry configuration.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot."
INDEX { applIndex }
::= { sipCommonCfgRetryTable 1 }
SipCommonCfgRetryEntry ::=
SEQUENCE {
sipCfgRetryInvite Unsigned32,
sipCfgRetryBye Unsigned32,
sipCfgRetryCancel Unsigned32,
sipCfgRetryRegister Unsigned32,
sipCfgRetryOptions Unsigned32,
sipCfgRetryFinalResponse Unsigned32,
sipCfgRetryNonFinalResponse Unsigned32
}
sipCfgRetryInvite OBJECT-TYPE
SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object will specify the number of times a SIP entity
will retry sending an INVITE request."
DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 1 }
sipCfgRetryBye OBJECT-TYPE
SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object will specify the number of times a SIP entity
will retry sending a BYE request."
DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 2 }
sipCfgRetryCancel OBJECT-TYPE
SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object will specify the number of times a SIP entity
will retry sending a CANCEL request."
DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 3 }
sipCfgRetryRegister OBJECT-TYPE
SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object will specify the number of times a SIP entity
will retry sending a REGISTER request."
DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 4 }
sipCfgRetryOptions OBJECT-TYPE
SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object will specify the number of times a SIP entity
will retry sending an OPTIONS request."
DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 5 }
sipCfgRetryFinalResponse OBJECT-TYPE
SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object will specify the number of times a SIP entity
will retry sending a final response and expecting an ACK."
DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 6 }
sipCfgRetryNonFinalResponse OBJECT-TYPE
SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object will specify the number of times a SIP entity
will retry sending a non-final response."
DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 7 }
--
-- Retry Extensions: support for extension methods
--
sipCommonCfgRetryExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgRetryExtMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains retry configuration for each SIP
extension method this entity supports."
::= { sipCommonCfgRetry 2 }
sipCommonCfgRetryExtMethodEntry OBJECT-TYPE
SYNTAX SipCommonCfgRetryExtMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This row contains retry configuration information for
a particular extension method.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot."
AUGMENTS { sipExtMethodSupportedEntry }
::= { sipCommonCfgRetryExtMethodTable 1 }
SipCommonCfgRetryExtMethodEntry ::=
SEQUENCE {
sipCfgRetryExtMethodRetry Unsigned32
}
sipCfgRetryExtMethodRetry OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the number of times a SIP entity
will retry sending its request for this particular
extension method."
::= { sipCommonCfgRetryExtMethodEntry 1 }
--
-- Per Method Expires Configuration
--
sipCommonCfgExpiresMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgExpiresMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains Expires header value configuration
objects applicable to SIP user agent and SIP stateful
Proxy Server entities."
::= { sipCommonCfgExpires 1 }
sipCommonCfgExpiresMethodEntry OBJECT-TYPE
SYNTAX SipCommonCfgExpiresMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of Expires header configuration for SIP Methods.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot."
INDEX { applIndex }
::= { sipCommonCfgExpiresMethodTable 1 }
SipCommonCfgExpiresMethodEntry ::=
SEQUENCE {
sipCfgExpiresInvite Unsigned32,
sipCfgExpiresRegister Unsigned32,
sipCfgExpiresHeaderMethod BITS
}
sipCfgExpiresInvite OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"For user agent clients, this value is inserted into the
Expires header.
For Proxy Servers, if a received request contained an
Expires header, then the value in the header takes
precedence."
::= { sipCommonCfgExpiresMethodEntry 1 }
sipCfgExpiresRegister OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"For user agent clients, this value is inserted into the
Expires header.
For Registrar Servers, if a received request contained an
Expires header, then the value in the header takes
precedence."
::= { sipCommonCfgExpiresMethodEntry 2 }
sipCfgExpiresHeaderMethod OBJECT-TYPE
SYNTAX BITS {
invite(0),
register(1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This convention is a bit map. Each bit represents a
SIP method where the Expires header SHOULD be included.
If a bit has value 1, then the requests corresponding
to that SIP method MUST include an Expires header line.
If a bit has value 0, then the Expires header line will
not be added.
Combinations of bits can be set when the Expires header
line is REQUIRED in multiple SIP methods.
bit 0 : INVITE method.
bit 1 : REGISTER Method."
::= { sipCommonCfgExpiresMethodEntry 3 }
sipCommonCfgExpiresStatusCodeTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgExpiresStatusCodeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the Expires header configuration
objects for the SIP responses."
::= { sipCommonCfgExpires 2 }
sipCommonCfgExpiresStatusCodeEntry OBJECT-TYPE
SYNTAX SipCommonCfgExpiresStatusCodeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This row contains information on the configuration of
the Expires header value for a particular SIP status
code. Examples of SIP responses that MAY include an
Expires header are 302 and 504.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot."
INDEX { applIndex, sipCfgExpiresStatusCodeValue }
::= { sipCommonCfgExpiresStatusCodeTable 1 }
SipCommonCfgExpiresStatusCodeEntry ::=
SEQUENCE {
sipCfgExpiresStatusCodeValue Unsigned32,
sipCfgExpiresHeaderValue Unsigned32,
sipCfgExpiresStatusCodeStatus RowStatus
}
sipCfgExpiresStatusCodeValue OBJECT-TYPE
SYNTAX Unsigned32 (100..999)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object contains a SIP status code value for which
the Expires header value is configured. All of the other
information in the row is related to this value."
::= { sipCommonCfgExpiresStatusCodeEntry 1 }
sipCfgExpiresHeaderValue OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value is inserted into the Expires header for the
specific status code."
::= { sipCommonCfgExpiresStatusCodeEntry 2 }
sipCfgExpiresStatusCodeStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is REQUIRED to create or delete rows
by a manager.
A value for sipCfgExpiresHeaderValue MUST be specified when
creating rows by setting this row status to 'createAndGo'.
The row will automatically transition to 'active'.
The configuration specified by an entry will be made
active when this object is set to 'active'."
::= { sipCommonCfgExpiresStatusCodeEntry 3 }
--
-- Common Statistics Objects -- Common Statistics Objects
-- --
-- --
-- Summary Statistics -- Summary Statistics
-- --
sipSummaryStatsTable OBJECT-TYPE sipSummaryStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipSummaryStatsEntry SYNTAX SEQUENCE OF SipSummaryStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 42, line 46 skipping to change at page 34, line 18
transaction. transaction.
The branch ID parameter in the Via header field values The branch ID parameter in the Via header field values
serves as a transaction identifier. serves as a transaction identifier.
A transaction is identified by the CSeq sequence number A transaction is identified by the CSeq sequence number
within a single call leg. The ACK request has the same within a single call leg. The ACK request has the same
CSeq number as the corresponding INVITE request, but CSeq number as the corresponding INVITE request, but
comprises a transaction of its own. comprises a transaction of its own.
In the case of a forked request, all branches count as a In the case of a forked request, each branch counts as a
single transaction. single transaction.
For a transaction stateless Proxy Server, this counter For a transaction stateless Proxy Server, this counter
is always 0." is always 0."
::= { sipSummaryStatsEntry 5 } ::= { sipSummaryStatsEntry 5 }
-- --
-- SIP Method Statistics -- SIP Method Statistics
-- Total counts for each SIP method. -- Total counts for each SIP method.
-- --
skipping to change at page 43, line 32 skipping to change at page 34, line 51
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of per entity method statistics. "A row of per entity method statistics.
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 } INDEX { applIndex, sipStatsMethod }
::= { sipMethodStatsTable 1 } ::= { sipMethodStatsTable 1 }
SipMethodStatsEntry ::= SipMethodStatsEntry ::=
SEQUENCE { SEQUENCE {
sipStatsInviteIns Counter32, sipStatsMethod SipMethodIdentifier,
sipStatsInviteOuts Counter32, sipStatsOutbounds Counter32,
sipStatsAckIns Counter32, sipStatsInbounds Counter32
sipStatsAckOuts Counter32,
sipStatsByeIns Counter32,
sipStatsByeOuts Counter32,
sipStatsCancelIns Counter32,
sipStatsCancelOuts Counter32,
sipStatsOptionsIns Counter32,
sipStatsOptionsOuts Counter32,
sipStatsRegisterIns Counter32,
sipStatsRegisterOuts Counter32
} }
sipStatsInviteIns OBJECT-TYPE
SYNTAX Counter32 sipStatsMethod OBJECT-TYPE
MAX-ACCESS read-only SYNTAX SipMethodIdentifier
MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE requests "This object uniquely identifies the SIP method
received by the SIP entity including retransmissions." related to the objects in a particular row."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 1 } ::= { sipMethodStatsEntry 1 }
sipStatsInviteOuts OBJECT-TYPE sipStatsOutbounds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE requests "This object reflects the total number of requests
sent by the SIP entity including retransmissions." sent by the SIP entity, excluding retransmissions.
Retransmissions are counted separately and are not
reflected in this counter."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 2 } ::= { sipMethodStatsEntry 2 }
sipStatsAckIns 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 ACK requests "This object reflects the total number of requests
received by the SIP entity." received by the SIP entity."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 3 } ::= { sipMethodStatsEntry 3 }
sipStatsAckOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of ACK requests sent
by the SIP entity."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 4 }
sipStatsByeIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of BYE requests
received by the SIP entity including retransmissions."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 5 }
sipStatsByeOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of BYE requests sent
by the SIP entity including retransmissions."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 6 }
sipStatsCancelIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of CANCEL requests
received by the SIP entity including retransmissions."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 7 }
sipStatsCancelOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of CANCEL requests
sent by the SIP entity including retransmissions."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 8 }
sipStatsOptionsIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of OPTIONS requests
received by the SIP entity including retransmissions."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 9 }
sipStatsOptionsOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of OPTIONS requests
sent by the SIP entity including retransmissions."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 10 }
sipStatsRegisterIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of REGISTER requests
received by the SIP entity including retransmissions."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 11 }
sipStatsRegisterOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of REGISTER requests
sent by the SIP entity including retransmissions."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 12 }
--
-- support for extension methods
--
sipStatsExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatsExtMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the list of extension methods which
each SIP entity in this system has been requested to
monitor."
::= { sipCommonStatsMethod 2 }
sipStatsExtMethodEntry OBJECT-TYPE
SYNTAX SipStatsExtMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This row contains information on a particular extension
method that the SIP entity has been requested to monitor.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
AUGMENTS { sipExtMethodSupportedEntry }
::= { sipStatsExtMethodTable 1 }
SipStatsExtMethodEntry ::=
SEQUENCE {
sipStatsExtMethodIns Counter32,
sipStatsExtMethodOuts Counter32
}
sipStatsExtMethodIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of requests received
by the SIP entity which requested the method contained in
the sipStatsExtMethodName column including retransmissions
if appropriate for the method."
::= { sipStatsExtMethodEntry 1 }
sipStatsExtMethodOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of requests sent
by the SIP entity which requested the method contained in
the sipStatsExtMethodName column including retransmissions
if appropriate for the method."
::= { sipStatsExtMethodEntry 2 }
--
-- SIP Response Status Codes
--
sipStatusCodeClassesTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatusCodeClassesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains statistics on response status code
classes for each SIP entity in this system."
::= { sipCommonStatusCode 1 }
sipStatusCodeClassesEntry OBJECT-TYPE
SYNTAX SipStatusCodeClassesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This row contains statistics on response status codes.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex }
::= { sipStatusCodeClassesTable 1 }
SipStatusCodeClassesEntry ::=
SEQUENCE {
sipStatsInfoClassIns Counter32,
sipStatsInfoClassOuts Counter32,
sipStatsSuccessClassIns Counter32,
sipStatsSuccessClassOuts Counter32,
sipStatsRedirClassIns Counter32,
sipStatsRedirClassOuts Counter32,
sipStatsReqFailClassIns Counter32,
sipStatsReqFailClassOuts Counter32,
sipStatsServerFailClassIns Counter32,
sipStatsServerFailClassOuts Counter32,
sipStatsGlobalFailClassIns Counter32,
sipStatsGlobalFailClassOuts Counter32,
sipStatsOtherClassesIns Counter32,
sipStatsOtherClassesOuts Counter32
}
sipStatsInfoClassIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 1xx class
SIP responses received by the SIP entity.
This class of responses relates to providing some
information concerning the progress of processing
a SIP request."
REFERENCE
"RFC 3261, Section 21.1"
::= { sipStatusCodeClassesEntry 1 }
sipStatsInfoClassOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 1xx class
SIP responses sent by the SIP entity.
This class of responses relates to providing some
information concerning the progress of processing
a SIP request."
REFERENCE
"RFC 3261, Section 21.1"
::= { sipStatusCodeClassesEntry 2 }
sipStatsSuccessClassIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 2xx class SIP
responses received by the SIP entity. This class of
responses relate to successful completion of a SIP
request."
REFERENCE
"RFC 3261, Section 21.2"
::= { sipStatusCodeClassesEntry 3 }
sipStatsSuccessClassOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 2xx class SIP
responses sent by the SIP entity. This class of
responses relate to successful completion of a SIP
request."
REFERENCE
"RFC 3261, Section 21.2"
::= { sipStatusCodeClassesEntry 4 }
sipStatsRedirClassIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 3xx class SIP
responses received by the SIP entity. This class
of responses relate to redirections to addresses
where the callee might be reachable."
REFERENCE
"RFC 3261, Section 21.3"
::= { sipStatusCodeClassesEntry 5 }
sipStatsRedirClassOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 3xx class SIP
responses sent by the SIP entity. This class
of responses relate to redirections to addresses
where the callee might be reachable."
REFERENCE
"RFC 3261, Section 21.3"
::= { sipStatusCodeClassesEntry 6 }
sipStatsReqFailClassIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 4xx class SIP
responses received by the SIP entity. This class of
responses reflect request failure by a SIP entity
providing a client function."
REFERENCE
"RFC 3261, Section 21.4"
::= { sipStatusCodeClassesEntry 7 }
sipStatsReqFailClassOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 4xx class SIP
responses sent by the SIP entity. This class of
responses reflect request failure by a SIP entity
providing a server function."
REFERENCE
"RFC 3261, Section 21.4"
::= { sipStatusCodeClassesEntry 8 }
sipStatsServerFailClassIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 5xx class SIP
responses received by the SIP entity. This class of
responses reflect failure responses received by a
SIP entity providing a client function."
REFERENCE
"RFC 3261, Section 21.5"
::= { sipStatusCodeClassesEntry 9 }
sipStatsServerFailClassOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 5xx class SIP
responses sent by the SIP entity. This class of
responses reflect failure responses sent by a SIP
entity providing a server function."
REFERENCE
"RFC 3261, Section 21.5"
::= { sipStatusCodeClassesEntry 10 }
sipStatsGlobalFailClassIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 6xx class SIP
responses received by the SIP entity. This class of
responses reflect failure responses received by a
SIP entity providing a client function.
The responses generally indicate that a server has
definitive information about a particular called party,
not just the particular instance indicated in the
Request-URI."
REFERENCE
"RFC 3261, Section 21.6"
::= { sipStatusCodeClassesEntry 11 }
sipStatsGlobalFailClassOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of 6xx class SIP
responses sent by the SIP entity. This class of
responses reflect failure responses sent by a SIP
entity providing a server function.
The responses generally indicate that a server has
definitive information about a particular called party,
not just the particular instance indicated in the
Request-URI."
REFERENCE
"RFC 3261, Section 21.6"
::= { sipStatusCodeClassesEntry 12 }
sipStatsOtherClassesIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of SIP responses
received by the SIP entity for status code response
classes other than 1xx, 2xx, 3xx, 4xx, 5xx, or 6xx."
::= { sipStatusCodeClassesEntry 13 }
sipStatsOtherClassesOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of SIP responses
sent by the SIP entity for status code response
classes other than 1xx, 2xx, 3xx, 4xx, 5xx, or 6xx."
::= { sipStatusCodeClassesEntry 14 }
-- --
-- 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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the list of SIP status codes which "This table contains the list of SIP status codes which
each SIP entity in this system has been requested to each SIP entity in this system has been requested to
skipping to change at page 58, line 39 skipping to change at page 41, line 42
sipCurrentTransactions Gauge32 sipCurrentTransactions Gauge32
} }
sipCurrentTransactions OBJECT-TYPE sipCurrentTransactions OBJECT-TYPE
SYNTAX Gauge32 (0..4294967295) SYNTAX Gauge32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the number of transactions awaiting "This object contains the number of transactions awaiting
definitive (non-1xx) response. In the case of a forked definitive (non-1xx) response. In the case of a forked
request, all branches count as a single transaction request, each branch counts as a single transaction
corresponding to the entity identified by applIndex." corresponding to the entity identified by applIndex."
::= { sipCurrentTransEntry 1 } ::= { sipCurrentTransEntry 1 }
-- --
-- SIP Retry Statistics -- SIP Retry Statistics
-- --
-- The counter objects in this group correspond directly to the -- This group contains various statistic objects about
-- retry timers supported in sipCommonCfgRetry group. applIndex can -- retransmission counts.
-- be used to correlate the two groups.
-- --
sipCommonStatsRetryTable OBJECT-TYPE sipCommonStatsRetryTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonStatsRetryEntry SYNTAX SEQUENCE OF SipCommonStatsRetryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains retry statistics objects applicable "This table contains retry statistics objects applicable
to each SIP entity in this system." to each SIP entity in this system."
::= { sipCommonStatsRetry 1 } ::= { sipCommonStatsRetry 1 }
skipping to change at page 59, line 24 skipping to change at page 42, line 27
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of retry statistics. "A row of retry statistics.
Each row represents those objects for a particular SIP 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 } INDEX { applIndex, sipStatsRetryMethod }
::= { sipCommonStatsRetryTable 1 } ::= { sipCommonStatsRetryTable 1 }
SipCommonStatsRetryEntry ::= SipCommonStatsRetryEntry ::=
SEQUENCE { SEQUENCE {
sipStatsRetryInvites Counter32, sipStatsRetryMethod SipMethodIdentifier,
sipStatsRetryByes Counter32, sipStatsRetries Counter32,
sipStatsRetryCancels Counter32,
sipStatsRetryRegisters Counter32,
sipStatsRetryOptions Counter32,
sipStatsRetryFinalResponses Counter32, sipStatsRetryFinalResponses Counter32,
sipStatsRetryNonFinalResponses Counter32 sipStatsRetryNonFinalResponses Counter32
} }
sipStatsRetryInvites OBJECT-TYPE sipStatsRetryMethod OBJECT-TYPE
SYNTAX Counter32 SYNTAX SipMethodIdentifier
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE retries "This object uniquely identifies the SIP method
that have been sent by the SIP entity. If the number of related to the objects in a row."
'first attempt' INVITES is of interest, subtract the value
of this object from sipStatsInviteOuts."
::= { sipCommonStatsRetryEntry 1 } ::= { sipCommonStatsRetryEntry 1 }
sipStatsRetryByes 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 BYE retries that "This object reflects the total number of INVITE retries
have been sent by the SIP entity. If the number of that have been sent by the SIP entity."
'first attempt' BYEs is of interest, subtract the value
of this object from sipStatsByeOuts."
::= { sipCommonStatsRetryEntry 2 } ::= { sipCommonStatsRetryEntry 2 }
sipStatsRetryCancels OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of CANCEL retries
that have been sent by the SIP entity. If the number of
'first attempt' CANCELs is of interest, subtract the value
of this object from sipStatsCancelOuts."
::= { sipCommonStatsRetryEntry 3 }
sipStatsRetryRegisters OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of REGISTER retries
that have been sent by the SIP entity. If the number of
'first attempt' REGISTERSs is of interest, subtract the value
of this object from sipStatsRegisterOuts."
::= { sipCommonStatsRetryEntry 4 }
sipStatsRetryOptions OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of OPTIONS retries
that have been sent by the SIP entity. If the number of
'first attempt' OPTIONS is of interest, subtract the value
of this object from sipStatsOptionsOuts."
::= { sipCommonStatsRetryEntry 5 }
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."
::= { sipCommonStatsRetryEntry 6 } ::= { 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 7 } ::= { sipCommonStatsRetryEntry 4 }
--
-- Retry Extensions Stats: support for extension methods
--
sipCommonStatsRetryExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonStatsRetryExtMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains retry statistics for each SIP
extension method this entity supports."
::= { sipCommonStatsRetry 2 }
sipCommonStatsRetryExtMethodEntry OBJECT-TYPE
SYNTAX SipCommonStatsRetryExtMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This row contains retry statistics for
a particular extension method.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
AUGMENTS { sipExtMethodSupportedEntry }
::= { sipCommonStatsRetryExtMethodTable 1 }
SipCommonStatsRetryExtMethodEntry ::=
SEQUENCE {
sipStatsRetryExtMethodRetries Counter32
}
sipStatsRetryExtMethodRetries OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of retries
sent by the SIP entity for a given extension method."
::= { sipCommonStatsRetryExtMethodEntry 1 }
-- --
-- Other Common Statistics -- Other Common Statistics
-- --
sipOtherStatsTable OBJECT-TYPE sipOtherStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipOtherStatsEntry SYNTAX SEQUENCE OF SipOtherStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains other common statistics supported by "This table contains other common statistics supported by
skipping to change at page 62, line 43 skipping to change at page 44, line 8
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 } INDEX { applIndex }
::= { sipOtherStatsTable 1 } ::= { sipOtherStatsTable 1 }
SipOtherStatsEntry ::= SipOtherStatsEntry ::=
SEQUENCE { SEQUENCE {
sipNumUnsupportedUris Counter32 sipNumUnsupportedUris Counter32,
sipNumUnsupportedMethods Counter32,
sipOtherwiseDiscardedMsgs Counter32
} }
sipNumUnsupportedUris OBJECT-TYPE sipNumUnsupportedUris OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of RequestURIs received with unsupported scheme. "Number of RequestURIs received with unsupported scheme.
A server normally responds to such requests with a 400 Bad A server normally responds to such requests with a 400 Bad
Request status code." Request status code."
::= { sipOtherStatsEntry 1 } ::= { sipOtherStatsEntry 1 }
sipNumUnsupportedMethods OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of SIP requests received with unsupported methods.
A server normally responds to such requests with a
501 (Not Implemented) or 405 (Method Not Allowed)."
::= { sipOtherStatsEntry 2 }
sipOtherwiseDiscardedMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of SIP messages received that for any number
of reasons was discarded without a response."
::= { sipOtherStatsEntry 3 }
-- --
-- Notification related objects -- Notification related objects
-- --
-- --
-- Status code related notification objects. -- Status code related notification objects.
-- --
sipStatusCodeNotifTo OBJECT-TYPE sipStatusCodeNotifTo OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
skipping to change at page 67, line 23 skipping to change at page 49, line 8
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipCommonConfigGroup, MANDATORY-GROUPS { sipCommonConfigGroup,
sipCommonStatsGroup } sipCommonStatsGroup }
GROUP sipCommonConfigTimerGroup GROUP sipCommonConfigTimerGroup
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 timer configuration." not provide any timer configuration."
GROUP sipCommonConfigTimerExtMethodGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to
not provide any extension method timer configuration.
If implemented, the sipCommonConfigTimerGroup MUST also
be implemented because of a dependency on sipCfgTimerT2."
GROUP sipCommonConfigRetryGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to
not provide any retry configuration."
GROUP sipCommonConfigRetryExtMethodGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to
not provide any extension method retry configuration."
GROUP sipCommonStatsRetryGroup GROUP sipCommonStatsRetryGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to
not provide any retry statistics. If implemented, not provide any retry statistics."
the sipCommonConfigRetryGroup MUST also be implemented."
GROUP sipCommonStatsRetryExtMethodsGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to
not provide any extension method retry statistics.
If implemented, the sipCommonConfigRetryExtMethodGroup
MUST also be implemented."
GROUP sipCommonNotifGroup GROUP sipCommonNotifGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to
not provide any notifications. If implemented, the not provide any notifications. If implemented, the
sipCommonStatusCodeNotifGroup and sipCommonStatusCodeNotifGroup and
sipCommonNotifObjectsGroup MUST also be implemented." sipCommonNotifObjectsGroup MUST also be implemented."
GROUP sipCommonStatusCodeNotifGroup GROUP sipCommonStatusCodeNotifGroup
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
sipCommonNotifGroup and sipCommonNotifObjectsGroup sipCommonNotifGroup and sipCommonNotifObjectsGroup
MUST also be implemented." MUST also be implemented."
GROUP sipCommonConfigExpiresGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to
not provide any Expires header configuration."
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, sipServiceAdminStatus,
sipServiceStartTime, sipServiceStartTime,
sipServiceLastChange, sipServiceLastChange,
sipTransportRcv, sipTransportRcv,
sipTransportSnd, sipOptionTag,
sipPortStatus, sipOptionTagHeaderField,
sipUriSupported,
sipFtrSupported,
sipExtMethodName,
sipOrganization, sipOrganization,
sipMaxSessions, sipMaxTransactions,
sipRequestUriHostMatching,
sipServiceNotifEnable, sipServiceNotifEnable,
sipEntityType sipEntityType,
sipMethodName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration common "A collection of objects providing configuration common
to all SIP enities." to all SIP enities."
::= { sipCommonMIBGroups 1 } ::= { sipCommonMIBGroups 1 }
sipCommonConfigTimerGroup OBJECT-GROUP sipCommonConfigTimerGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgTimerA, sipCfgTimerA,
skipping to change at page 69, line 35 skipping to change at page 52, line 24
sipCfgTimerT1, sipCfgTimerT1,
sipCfgTimerT2, sipCfgTimerT2,
sipCfgTimerT4 sipCfgTimerT4
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing timer configuration "A collection of objects providing timer configuration
common to all SIP enities." common to all SIP enities."
::= { sipCommonMIBGroups 2 } ::= { sipCommonMIBGroups 2 }
sipCommonConfigTimerExtMethodGroup OBJECT-GROUP
OBJECTS {
sipCfgTimerExtMethodTimer
}
STATUS current
DESCRIPTION
"A collection of objects providing extension method timer
configuration."
::= { sipCommonMIBGroups 3 }
sipCommonConfigRetryGroup OBJECT-GROUP
OBJECTS {
sipCfgRetryInvite,
sipCfgRetryBye,
sipCfgRetryCancel,
sipCfgRetryRegister,
sipCfgRetryOptions,
sipCfgRetryFinalResponse,
sipCfgRetryNonFinalResponse
}
STATUS current
DESCRIPTION
"A collection of objects providing retry configuration
common to all SIP enities."
::= { sipCommonMIBGroups 4 }
sipCommonConfigRetryExtMethodGroup OBJECT-GROUP
OBJECTS {
sipCfgRetryExtMethodRetry
}
STATUS current
DESCRIPTION
"A collection of objects providing extension method retry
configuration."
::= { sipCommonMIBGroups 5 }
sipCommonStatsGroup OBJECT-GROUP sipCommonStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipSummaryInRequests, sipSummaryInRequests,
sipSummaryOutRequests, sipSummaryOutRequests,
sipSummaryInResponses, sipSummaryInResponses,
sipSummaryOutResponses, sipSummaryOutResponses,
sipSummaryTotalTransactions, sipSummaryTotalTransactions,
sipStatsInviteIns, sipStatsOutbounds,
sipStatsInviteOuts, sipStatsInbounds,
sipStatsAckIns,
sipStatsAckOuts,
sipStatsByeIns,
sipStatsByeOuts,
sipStatsCancelIns,
sipStatsCancelOuts,
sipStatsOptionsIns,
sipStatsOptionsOuts,
sipStatsRegisterIns,
sipStatsRegisterOuts,
sipStatsExtMethodIns,
sipStatsExtMethodOuts,
sipStatsInfoClassIns,
sipStatsInfoClassOuts,
sipStatsSuccessClassIns,
sipStatsSuccessClassOuts,
sipStatsRedirClassIns,
sipStatsRedirClassOuts,
sipStatsReqFailClassIns,
sipStatsReqFailClassOuts,
sipStatsServerFailClassIns,
sipStatsServerFailClassOuts,
sipStatsGlobalFailClassIns,
sipStatsGlobalFailClassOuts,
sipStatsOtherClassesIns,
sipStatsOtherClassesOuts,
sipStatusCodeIns, sipStatusCodeIns,
sipStatusCodeOuts, sipStatusCodeOuts,
sipStatusCodeRowStatus, sipStatusCodeRowStatus,
sipCurrentTransactions, sipCurrentTransactions,
sipNumUnsupportedUris sipNumUnsupportedUris,
sipNumUnsupportedMethods,
sipOtherwiseDiscardedMsgs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics common "A collection of objects providing statistics common
to all SIP entities." to all SIP entities."
::= { sipCommonMIBGroups 6 } ::= { sipCommonMIBGroups 3 }
sipCommonStatsRetryGroup OBJECT-GROUP sipCommonStatsRetryGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatsRetryInvites, sipStatsRetries,
sipStatsRetryByes,
sipStatsRetryCancels,
sipStatsRetryRegisters,
sipStatsRetryOptions,
sipStatsRetryFinalResponses, sipStatsRetryFinalResponses,
sipStatsRetryNonFinalResponses sipStatsRetryNonFinalResponses
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing retry statistics." "A collection of objects providing retry statistics."
::= { sipCommonMIBGroups 7 } ::= { sipCommonMIBGroups 4 }
sipCommonStatsRetryExtMethodsGroup OBJECT-GROUP
OBJECTS {
sipStatsRetryExtMethodRetries
}
STATUS current
DESCRIPTION
"A collection of objects providing extension method retry
statistics."
::= { sipCommonMIBGroups 8 }
sipCommonNotifGroup NOTIFICATION-GROUP sipCommonNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
sipStatusCodeNotif, sipStatusCodeNotif,
sipStatusCodeThreshExceededInNotif, sipStatusCodeThreshExceededInNotif,
sipStatusCodeThreshExceededOutNotif, sipStatusCodeThreshExceededOutNotif,
sipServiceColdStart, sipServiceColdStart,
sipServiceWarmStart, sipServiceWarmStart,
sipServiceStatusChanged sipServiceStatusChanged
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications common to all SIP entities." "A collection of notifications common to all SIP entities."
::= { sipCommonMIBGroups 9 } ::= { sipCommonMIBGroups 5 }
sipCommonStatusCodeNotifGroup OBJECT-GROUP sipCommonStatusCodeNotifGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatusCodeNotifSend, sipStatusCodeNotifSend,
sipStatusCodeNotifEmitMode, sipStatusCodeNotifEmitMode,
sipStatusCodeNotifThresh, sipStatusCodeNotifThresh,
sipStatusCodeNotifInterval sipStatusCodeNotifInterval
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects related to controlling and attribution "A collection of objects related to controlling and attribution
of notifications common to all SIP entities." of notifications common to all SIP entities."
::= { sipCommonMIBGroups 10 } ::= { sipCommonMIBGroups 6 }
sipCommonConfigExpiresGroup OBJECT-GROUP
OBJECTS {
sipCfgExpiresInvite,
sipCfgExpiresRegister,
sipCfgExpiresHeaderMethod,
sipCfgExpiresHeaderValue,
sipCfgExpiresStatusCodeStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration
related to Expires header."
::= { sipCommonMIBGroups 11 }
sipCommonNotifObjectsGroup OBJECT-GROUP sipCommonNotifObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatusCodeNotifTo, sipStatusCodeNotifTo,
sipStatusCodeNotifFrom, sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId, sipStatusCodeNotifCallId,
sipStatusCodeNotifCSeq, sipStatusCodeNotifCSeq,
sipNotifApplIndex, sipNotifApplIndex,
sipNotifSequenceNumber sipNotifSequenceNumber
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of accessible-for-notify objects "A collection of accessible-for-notify objects
related to the notification defined in this related to the notification defined in this
MIB module." MIB module."
::= { sipCommonMIBGroups 12 } ::= { sipCommonMIBGroups 7 }
END END
7.3 SIP User Agent MIB Module 7.3 SIP User Agent MIB Module
SIP-UA-MIB DEFINITIONS ::= BEGIN SIP-UA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Unsigned32, Unsigned32,
skipping to change at page 73, line 33 skipping to change at page 54, line 29
FROM SNMPv2-CONF FROM SNMPv2-CONF
RowStatus RowStatus
FROM SNMPv2-TC 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
FROM SIP-TC;
sipUAMIB MODULE-IDENTITY sipUAMIB MODULE-IDENTITY
LAST-UPDATED "200307300000Z" LAST-UPDATED "200407160000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
skipping to change at page 74, line 4 skipping to change at page 54, line 48
"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
ipDialog, Inc. postal:
postal: 7701 N. Lamar Blvd., Suite 304
Austin, TX 78752-1023 email: jmaeng@austin.rr.com
USA phone:
email: jmaeng@ipdialog.com
phone: +1 512 371 1770
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc.
postal: 495 March Road postal:
Kanata, ON K2K 3G1
Canada email: drwalker@rogers.com
email: drwalker@ss8.com phone:
phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 400 Centennial Parkway 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 "
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
skipping to change at page 74, line 46 skipping to change at page 55, line 42
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 (2003). This version Copyright (C) The Internet Society (2004). 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 "200307300000Z" REVISION "200407160000Z"
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 xx }
-- RFC Ed: replace xx with actual IANA assigned number -- RFC Ed: replace xx 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.
-- --
sipUACfgSipServer OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 } sipUACfgServer OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 }
-- --
-- SIP Server Configuration -- SIP Server Configuration
-- --
sipUACfgSipServerTable OBJECT-TYPE sipUACfgServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUACfgSipServerEntry SYNTAX SEQUENCE OF SipUACfgServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains SIP server configuration objects "This table contains SIP server configuration objects
applicable to each SIP user agent in this system." applicable to each SIP user agent in this system."
::= { sipUACfgSipServer 1 } ::= { sipUACfgServer 1 }
sipUACfgSipServerEntry OBJECT-TYPE sipUACfgServerEntry OBJECT-TYPE
SYNTAX SipUACfgSipServerEntry SYNTAX SipUACfgServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of server configuration. "A row of server configuration.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
user agent present in this system. applIndex is used to user agent present in this system. applIndex is used to
uniquely identify these instances of SIP user agents and uniquely identify these instances of SIP user agents and
correlate them through the common framework of the correlate them through the common framework of the
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 is applIndex used in the corresponding SIP-COMMON-MIB is
used here. used here.
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, sipUACfgSipServerIndex } INDEX { applIndex, sipUACfgServerIndex }
::= { sipUACfgSipServerTable 1 } ::= { sipUACfgServerTable 1 }
SipUACfgSipServerEntry ::= SipUACfgServerEntry ::=
SEQUENCE { SEQUENCE {
sipUACfgSipServerIndex Unsigned32, sipUACfgServerIndex Unsigned32,
sipUACfgSipServerAddrType InetAddressType, sipUACfgServerAddrType InetAddressType,
sipUACfgSipServerAddr InetAddress, sipUACfgServerAddr InetAddress,
sipUACfgSipServerStatus RowStatus sipUACfgServerFunction SipEntityRole,
sipUACfgServerStatus RowStatus
} }
sipUACfgSipServerIndex OBJECT-TYPE sipUACfgServerIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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."
::= { sipUACfgSipServerEntry 1 } ::= { sipUACfgServerEntry 1 }
sipUACfgSipServerAddrType OBJECT-TYPE sipUACfgServerAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the type of address contained "This object specifies the type of address contained
in the associated instance of sipUACfgSipServerAddr." in the associated instance of sipUACfgServerAddr."
REFERENCE "INET-ADDRESS-MIB (RFC 3291)" REFERENCE "INET-ADDRESS-MIB (RFC 3291)"
DEFVAL { ipv4 } ::= { sipUACfgServerEntry 2 }
::= { sipUACfgSipServerEntry 2 }
sipUACfgSipServerAddr OBJECT-TYPE sipUACfgServerAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the address of a SIP server "This object specifies 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)"
::= { sipUACfgSipServerEntry 3 } ::= { sipUACfgServerEntry 3 }
sipUACfgSipServerStatus OBJECT-TYPE sipUACfgServerFunction OBJECT-TYPE
SYNTAX SipEntityRole
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the function of the SIP server
this user agent should communicate with: registrar, proxy
(outbound proxy), etc."
::= { sipUACfgServerEntry 4 }
sipUACfgServerStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to control rows in this table. "This object is used to control rows in this table.
'active' : the row's information is completely 'active' : the row's information is completely
populated and that information is populated and that information is
being used by the user agent. being used by the user agent.
'notInService' : the row's address is not being used 'notInService' : the row's address is not being used
by the user agent, but will remain in by the user agent, but will remain in
the table. the table.
'notReady' : key information is missing thus, 'notReady' : key information is missing thus,
preventing the row from being made preventing the row from being made
'active' (eg, no address specified). 'active' (eg, no address specified).
'createAndGo' : only allowed if the manager also 'createAndGo' : only allowed if the manager also
provides a varbind for provides a varbind for
sipUACfgSipServerAddr object in the sipUACfgServerAddr object in the
same set operation. same set operation.
'createAndWait' : not applicable. 'createAndWait' : not applicable.
'destroy' : the row's address will no longer be used 'destroy' : the row's address will no longer be used
by the user agent and the row will be by the user agent and the row will be
removed from the table." removed from the table."
::= { sipUACfgSipServerEntry 4 } ::= { sipUACfgServerEntry 5 }
-- --
-- Conformance -- Conformance
-- --
sipUAMIBCompliances sipUAMIBCompliances
OBJECT IDENTIFIER ::= { sipUAMIBConform 1 } OBJECT IDENTIFIER ::= { sipUAMIBConform 1 }
sipUAMIBGroups sipUAMIBGroups
OBJECT IDENTIFIER ::= { sipUAMIBConform 2 } OBJECT IDENTIFIER ::= { sipUAMIBConform 2 }
-- --
skipping to change at page 77, line 43 skipping to change at page 59, line 4
-- --
-- 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 {
sipUACfgSipServerAddrType, sipUACfgServerAddrType,
sipUACfgSipServerAddr, sipUACfgServerAddr,
sipUACfgSipServerStatus 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, Redirect & Proxy Server) MIB Module 7.4 SIP Server (Registrar & Proxy/Redirect Server) MIB Module
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
skipping to change at page 78, line 42 skipping to change at page 60, line 4
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 "200307300000Z" LAST-UPDATED "200407160000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
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
ipDialog, Inc.
postal: 7701 N. Lamar Blvd., Suite 304 postal:
Austin, TX 78752-1023
USA email: jmaeng@austin.rr.com
email: jmaeng@ipdialog.com phone:
phone: +1 512 371 1770
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc.
postal: 495 March Road postal:
Kanata, ON K2K 3G1
Canada email: drwalker@rogers.com
email: drwalker@ss8.com phone:
phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 400 Centennial Parkway 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 "
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
skipping to change at page 80, line 17 skipping to change at page 61, line 24
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 (2003). Copyright (C) The Internet Society (2004).
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 "200307300000Z" REVISION "200407160000Z"
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 yy }
-- RFC Ed: replace yy with actual IANA assigned number and remove this note -- RFC Ed: replace yy 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 }
sipServerStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 2 }
-- --
-- Common Server Configuration Objects -- Common Server Configuration Objects
-- --
sipServerCfgTable OBJECT-TYPE sipServerCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerCfgEntry SYNTAX SEQUENCE OF SipServerCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable "This table contains configuration objects applicable
skipping to change at page 82, line 46 skipping to change at page 64, line 5
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.
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 } INDEX { applIndex }
::= { sipProxyCfgTable 1 } ::= { sipProxyCfgTable 1 }
SipProxyCfgEntry ::= SipProxyCfgEntry ::=
SEQUENCE { SEQUENCE {
sipRequestMaxExpires Unsigned32,
sipProxyStatefulness INTEGER, sipProxyStatefulness INTEGER,
sipProxySendsCancel TruthValue,
sipProxyForwardAll1xx TruthValue,
sipProxyRecursion TruthValue, sipProxyRecursion TruthValue,
sipProxyProvideAlternatives TruthValue,
sipProxyRecordRoute TruthValue, sipProxyRecordRoute TruthValue,
sipProxyAuthMethod BITS, sipProxyAuthMethod BITS,
sipProxyAuthRealm SnmpAdminString, sipProxyAuthRealm SnmpAdminString
sipProxyNonceLifeTime Unsigned32
} }
sipRequestMaxExpires OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the maximum duration that a SIP
server will accept from a client in the Expires
header."
REFERENCE
"RFC 3261 Section 20.19"
::= { sipProxyCfgEntry 1 }
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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default mode of operation for "This object specifies 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
skipping to change at page 84, line 11 skipping to change at page 64, line 48
stateful on a transaction basis. stateful on a transaction basis.
A call stateful proxy is a logical entity if it retains A call stateful proxy is a logical entity if it 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 2 } ::= { sipProxyCfgEntry 1 }
sipProxySendsCancel OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies whether or not a forking proxy sends
CANCEL on outstanding branch requests after receiving a
2xx or 6xx, or after the request times-out.
If the value of this object is 'true', the server sends
a CANCELs on branches where no definitive response has been
received. If 'false', the proxy does not send CANCELs."
REFERENCE
"RFC 3261, Section 10"
::= { sipProxyCfgEntry 3 }
sipProxyForwardAll1xx OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies whether or not the proxy forwards
all 1xx responses, except the 100 Trying response,
upstream towards the source of the request.
If the value of this object is 'true', the 1xx responses
are sent. If the value is 'false', duplicate 1xx
responses are not sent upstream."
::= { sipProxyCfgEntry 4 }
sipProxyRecursion OBJECT-TYPE sipProxyRecursion OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Proxy performs "This object specifies whether or not the Proxy performs
recursive search on the Contacts provided in 3xx recursive search on the Contacts provided in 3xx
redirects. redirects.
If the value of this object is 'true', a recursive search 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 5 } ::= { sipProxyCfgEntry 2 }
sipProxyProvideAlternatives OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The object specifies whether or not the Server provides
alternative Contacts in 3xx and 485 responses.
If the value of this object is 'true', the server inserts a
list of alternative URIs into a Contact header where the
request Originator may possibly find the desired called
party. If the value is 'false', the server doesn't add
Contact information to 3xx and 485 responses.
Note that the policies of a server MAY limit the
particular alternatives that are returned when this object
is set to 'true'."
REFERENCE
"RFC 3261, Sections 13.2.2.2 and 16.5"
DEFVAL { true }
::= { sipProxyCfgEntry 6 }
sipProxyRecordRoute OBJECT-TYPE sipProxyRecordRoute OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the proxy adds itself "This object specifies whether or not the proxy adds itself
to the Record-Route header 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 7 } ::= { 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) smime(3)
} }
skipping to change at page 86, line 26 skipping to change at page 66, line 13
DESCRIPTION DESCRIPTION
"This object specifies the authentication methods that "This object specifies 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." 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 8 } ::= { sipProxyCfgEntry 4 }
sipProxyAuthRealm OBJECT-TYPE sipProxyAuthRealm OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the realm used in Proxy-Authenticate "This object specifies the realm used in Proxy-Authenticate
headers. Note that this MAY need to be stored per user." headers. Note that this MAY need to be stored per user."
REFERENCE REFERENCE
"RFC 3261, Section 22.1" "RFC 3261, Section 22.1"
::= { sipProxyCfgEntry 9 } ::= { sipProxyCfgEntry 5 }
sipProxyNonceLifeTime OBJECT-TYPE
SYNTAX Unsigned32 (0..65535)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the lifetime of a given nonce. A
nonce is a server specified value whose contents are
opaque to the entity being authenticated and which is used
in calculating authentication data. If this object has a
value of zero, then nonces are not reused."
::= { sipProxyCfgEntry 10 }
-- --
-- Proxy Server Statistics -- Proxy Server Statistics
-- --
sipProxyStatsTable OBJECT-TYPE sipProxyStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipProxyStatsEntry SYNTAX SEQUENCE OF SipProxyStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the statistics objects applicable "This table contains the statistics objects applicable
to all SIP Proxy Servers in this system." to all SIP Proxy Servers in this system."
skipping to change at page 89, line 10 skipping to change at page 68, line 34
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Registrar SHOULD "This object specifies whether or not the Registrar SHOULD
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 thsipRegAllowThirdPartyis 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
skipping to change at page 89, line 28 skipping to change at page 69, line 4
::= { 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-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum expiry that may be "This object specifies the maximum expiry that may be
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."
DEFVAL { 4294967295 }
::= { 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 specifies 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 specifies the number of users currently
configured on 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-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default time interval the "This object specifies the default time interval the
Registrar considers registrations to be active. The Registrar considers registrations to be active. The
skipping to change at page 92, line 51 skipping to change at page 72, line 26
INDEX { applIndex, sipUserIndex, sipContactIndex } INDEX { applIndex, sipUserIndex, sipContactIndex }
::= { sipContactTable 1 } ::= { sipContactTable 1 }
SipContactEntry ::= SipContactEntry ::=
SEQUENCE { SEQUENCE {
sipContactIndex Unsigned32, sipContactIndex Unsigned32,
sipContactDisplayName SnmpAdminString, sipContactDisplayName SnmpAdminString,
sipContactURI SnmpAdminString, sipContactURI SnmpAdminString,
sipContactLastUpdated TimeStamp, sipContactLastUpdated TimeStamp,
sipContactExpiry DateAndTime, sipContactExpiry DateAndTime,
sipContactPreference SnmpAdminString, sipContactPreference SnmpAdminString
sipContactRetryAfter DateAndTime
} }
sipContactIndex OBJECT-TYPE sipContactIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Along with the sipUserIndex, this object uniquely "Along with the sipUserIndex, this object uniquely
identifies a conceptual row in the table." identifies a conceptual row in the table."
::= { sipContactEntry 1 } ::= { sipContactEntry 1 }
skipping to change at page 94, line 33 skipping to change at page 74, line 7
may provide this preference as a 'qvalue'parameter in may provide this preference as a 'qvalue'parameter in
the Contact header. the Contact header.
The format of this item is a decimal number between 0 The format of this item is a decimal number between 0
and 1 (for example 0.9). Higher values indicate and 1 (for example 0.9). Higher values indicate
locations preferred by the user." locations preferred by the user."
REFERENCE REFERENCE
"RFC 3261, Section 10.2.1.2, 16.6 and 20.10" "RFC 3261, Section 10.2.1.2, 16.6 and 20.10"
::= { sipContactEntry 6 } ::= { sipContactEntry 6 }
sipContactRetryAfter OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates that the contact information is
currently inactive, and that it SHOULD only be
activated after the date and time specified by the object.
This value is provided by a user when deleting contact
information using a REGISTER request containing a
Retry-After header."
REFERENCE
"RFC 3261, Section 20.33"
::= { sipContactEntry 7 }
-- --
-- Registrar Statistics -- Registrar Statistics
-- --
sipRegStatsTable OBJECT-TYPE sipRegStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegStatsEntry SYNTAX SEQUENCE OF SipRegStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the summary statistics objects "This table contains the summary statistics objects
applicable to all SIP Registrars in this system." applicable to all SIP Registrars in this system."
skipping to change at page 96, line 49 skipping to change at page 76, line 10
sipRegistrarServerCompliance MODULE-COMPLIANCE sipRegistrarServerCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities acting "The compliance statement for SIP entities acting
as Registrars." as Registrars."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup, MANDATORY-GROUPS { sipServerConfigGroup,
sipRegistrarConfigGroup, sipRegistrarConfigGroup,
sipRegistrarStatsGroup } sipRegistrarStatsGroup }
GROUP sipRegistrarUsersGroup
DESCRIPTION
"This is an optional group."
::= { sipServerMIBCompliances 3 } ::= { sipServerMIBCompliances 3 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipServerConfigGroup OBJECT-GROUP sipServerConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipServerHostAddrType, sipServerHostAddrType,
sipServerHostAddr sipServerHostAddr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 97, line 20 skipping to change at page 76, line 31
sipServerHostAddr sipServerHostAddr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration common "A collection of objects providing configuration common
to SIP Proxy and Redirect servers." to SIP Proxy and Redirect servers."
::= { sipServerMIBGroups 1 } ::= { sipServerMIBGroups 1 }
sipProxyConfigGroup OBJECT-GROUP sipProxyConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipRequestMaxExpires,
sipProxyStatefulness, sipProxyStatefulness,
sipProxySendsCancel,
sipProxyForwardAll1xx,
sipProxyRecursion, sipProxyRecursion,
sipProxyProvideAlternatives,
sipProxyRecordRoute, sipProxyRecordRoute,
sipProxyAuthMethod, sipProxyAuthMethod,
sipProxyAuthRealm, sipProxyAuthRealm
sipProxyNonceLifeTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration for "A collection of objects providing configuration for
SIP Proxy servers." SIP Proxy servers."
::= { sipServerMIBGroups 2 } ::= { sipServerMIBGroups 2 }
sipProxyStatsGroup OBJECT-GROUP sipProxyStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipNumProxyRequireFailures sipNumProxyRequireFailures
skipping to change at page 97, line 46 skipping to change at page 77, line 4
sipProxyStatsGroup OBJECT-GROUP sipProxyStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipNumProxyRequireFailures sipNumProxyRequireFailures
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics for "A collection of objects providing statistics for
SIP Proxy servers." SIP Proxy servers."
::= { sipServerMIBGroups 3 } ::= { sipServerMIBGroups 3 }
sipRegistrarConfigGroup OBJECT-GROUP sipRegistrarConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipRegAllowThirdParty, sipRegAllowThirdParty,
sipRegMaxContactExpiryDuration, sipRegMaxContactExpiryDuration,
sipRegMaxUsers, sipRegMaxUsers,
sipRegCurrentUsers, sipRegCurrentUsers,
sipRegDfltRegActiveInterval, sipRegDfltRegActiveInterval
sipUserUri,
sipUserAuthenticationFailures,
sipUserTableRowStatus,
sipContactDisplayName,
sipContactURI,
sipContactLastUpdated,
sipContactExpiry,
sipContactPreference,
sipContactRetryAfter
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration for "A collection of objects providing configuration for
SIP Registrars." SIP Registrars."
::= { sipServerMIBGroups 4 } ::= { sipServerMIBGroups 4 }
sipRegistrarStatsGroup OBJECT-GROUP sipRegistrarStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipRegAcceptedRegistrations, sipRegAcceptedRegistrations,
sipRegRejectedRegistrations sipRegRejectedRegistrations
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics for "A collection of objects providing statistics for
SIP Registrars." SIP Registrars."
::= { sipServerMIBGroups 5 } ::= { sipServerMIBGroups 5 }
sipRegistrarUsersGroup OBJECT-GROUP
OBJECTS {
sipUserUri,
sipUserAuthenticationFailures,
sipUserTableRowStatus,
sipContactDisplayName,
sipContactURI,
sipContactLastUpdated,
sipContactExpiry,
sipContactPreference
}
STATUS current
DESCRIPTION
"A collection of objects related to registered users."
::= { sipServerMIBGroups 6 }
END END
8. Changes from Previous Draft Revisions 8. Changes from Previous Draft Revisions
Changes from draft-ietf-sip-mib-06 This section to be removed by RFC Editor before publication.
Changes from draft-ietf-sip-mib-07. The vast majority of changes are
in response to the Working Group Last Call & expert review comments.
o General o General
* IANA requirements section added to specify the need for
registered numbers for all SIP methods. These will be used in
the MIB objects.
* Updated the security consideration section to reflect the
addition and deletion of a number of objects.
o SIP-COMMON-MIB
* Module description of various SIP entities enhanced.
* sipMaxSessions renamed sipMaxTransactions. Workgroup last call
reviewers suggested a change based on some change of terms in
the standard. Transactions seemed the appropriate term. The
object description was also enhanced.
* sipRequestUriHostMatching object removed based on comments from
workgroup last call comments.
* sipEntityType changed from enumerated INTEGER to SipEntityRole
textual convention syntax.
* sipServiceAdminStatus enumerated value 'quiesceSessions'
changed to 'quiesceDialogs'.
* sipPortTable was redesigned. sipTransportSnd object was
removed as it didn't make much sense. sipPortStatus was
removed to prevent any row creation deletion. The remaining
object, sipTransportRcv was made read-only.
* sipUriSupportedTable was removed as it was not deemed useful
anymore.
* sipExtMethodSupportedTable replaced with a general
sipMethodSupportedTable. IANA SIP method identifiers/numbers
will be used in this new table. The previous concept of
explicitly defining objects per the current well-know methods
and then providing seperate, semantically similar, 'extension
methods' tables has been eliminated.
* sipCommonCfgTimerExtMethodTable was removed. No more need for
'extension methods' tables.
* sipCommonCfgRetryTable was removed. Limits on retransmissions
are controlled by timers in the SIP standard now rather than by
maximum counts; therefore, these objects were no longer
relevant. sipCommonConfigRetryGroup was likewise removed.
* sipFtrSupportedTable was redesigned as sipOptionTagsTable.
* sipCommonCfgTimerExtMethodTable was removed.
* sipSummaryTotalTransactions description changed to reflect that
in the case of forked request, _each_ branch rather than _all_
branches count as a single transaction.
* sipMethodStatsTable was redesigned, taking into account the new
SipMethodIdentifer textual convention. The objects were
generalized to two: sipStatsOutbound and sipStatsInbound. The
indexing object (sipStatsMethod) has syntax SipMethodIdentifier
and thereby identifies the method associated with the instances
of in/out counter objects.
* sipCurrentTransactions description changed to reflect that in
the case of forked request, _each_ branch rather than _all_
branches count as a single transaction.
* sipCommonStatsRetryTable was redesigned, taking into account
the new SipMethodIdentifer textual convention. A single,
generalize object (sipStatsRetries) replaces several
method-specific objects. The new, additional indexing object
(sipStatsRetryMethod) has syntax SipMethodIdentifier and
thereby identifies the method associated with the instances of
the counter objects in each row.
* sipCommonStatsRetryExtMethodTable was removed.
* sipStatusCodeClassesTable removed.
* sipOtherStatsTable has two new objects added:
sipNumUnsupportedMethods & sipOtherwiseDiscardedMsgs.
* The following object-groups were removed because their
associated objects were removed:
sipCommonConfigTimerExtMethodGroup, sipCommonConfigRetryGroup,
sipCommonConfigRetryExtMethodGroup,
sipCommonStatsRetryExtMethodsGroup, and
sipCommonConfigExpiresGroup. The references to these
object-groups as optional in the module-compliance was updated
accordingly.
* GROUP clause for sipCommonStatsRetryGroup in module-compliance
was udpated to no longer state any dependency on
sipCommonConfigRetryGroup (now removed).
* New OBJECT clauses were added to the module-compliance to
formalize MIN-ACCESS read-only for objects in
sipCommonCfgTimerTable.
* sipCommonConfigGroup udpated with new objects (sipOptionTag,
sipOptionTagHeaderField, sipMethodName), removed objects
(sipTransportSnd, sipPortStatus, sipUriSupported,
sipFtrSupported, sipExtMethodName, sipRequestUriHostMatching),
and changed objects (sipMaxTransactions).
* sipCommonStatsGroup updated with new objects
(sipStatsOutbounds, sipStatsInbounds, sipNumUnsupportedMethods,
sipOtherwiseDiscardedMsgs) and removed objects
(sipStatsInviteIns, sipStatsInviteOuts, sipStatsAckIns,
sipStatsAckOuts, sipStatsByeIns, sipStatsByeOuts,
sipStatsCancelIns, sipStatsCancelOuts, sipStatsOptionsIns,
sipStatsOptionsOuts, sipStatsRegisterIns, sipStatsRegisterOuts,
sipStatsExtMethodIns, sipStatsExtMethodOuts,
sipStatsInfoClassIns, sipStatsInfoClassOuts,
sipStatsSuccessClassIns, sipStatsSuccessClassOuts,
sipStatsRedirClassIns, sipStatsRedirClassOuts,
sipStatsReqFailClassIns, sipStatsReqFailClassOuts,
sipStatsServerFailClassIns, sipStatsServerFailClassOuts,
sipStatsGlobalFailClassIns, sipStatsGlobalFailClassOuts,
sipStatsOtherClassesIns, sipStatsOtherClassesOuts).
* sipCommonStatsRetryGroup updated with new object
(sipStatsRetries) and removed objects (sipStatsRetryInvites,
sipStatsRetryByes, sipStatsRetryCancels,
sipStatsRetryRegisters, sipStatsRetryOptions).
o SIP-SERVER-MIB
* Module description of various SIP entities enhanced.
* sipServerStats 'placeholder' IOD removed. No objects were ever
defined under that subtree.
* Removed the following objects from sipProxyCfgTable:
sipRequestMaxExpires, sipProxySendsCancel,
sipProxyForwardAll1xx, sipProxyProvideAlternatives, and
sipProxyNonceLifeTime. sipProxyConfigGroup updated
accordingly.
* sipProxyStatefulness MAX-ACCESS changed to read-only.
* DEFVAL removed from sipRegMaxContactExpiryDuration.
* sipContactRetryAfter removed from sipContactTable.
* sipUser* and sipContact* objects were moved from
sipRegistrarConfigGroup to a new object-group:
sipRegistrarUsersGroup. The new group was made an optional
group in the MODULE-COMPLIANCE.
o SIP-UA-MIB
* SipEntityRole imported from SIP-TC module and used as the
syntax for new object sipUACfgServerFunction.
* sipUACfgSipServerTable (and objects therein) have their
descriptors changed to sipUACfgServer* ("Sip" removed).
sipUAConfigGroup updated accordingly.
* sipUACfgServerFunction added to sipUACfgServerTable.
* DEFVAL { ipv4 } removed from sipUACfgServerAddrType.
o SIP-TC
* New textual conventions: SipEntityRole, SipOptionTagHeaders,
and SipMethodIdentifier added.
o
Changes from draft-ietf-sip-mib-06
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
required it to be commented out. Instead, simply removed it. required it to be commented out. Instead, simply removed it.
o SIP-SERVER-MIB o SIP-SERVER-MIB
* Removed OID placeholders: sipRedirCfg, sipRedirStats. * Removed OID placeholders: sipRedirCfg, sipRedirStats.
sipRegCfg and sipRegStats OID values subsequently changed as a sipRegCfg and sipRegStats OID values subsequently changed as a
result. result.
o SIP-UA-MIB o SIP-UA-MIB
* Removed OBJECT refinement for sipUACfgSipServerStatus added to * Removed OBJECT refinement for sipUACfgSipServerStatus added to
compliance in previous revision. SMIC MIB compiler issues compliance in previous revision. SMIC MIB compiler issues
required it to be commented out. Instead, simply removed it. required it to be commented out. Instead, simply removed it.
Changes from draft-ietf-sip-mib-05 Changes from draft-ietf-sip-mib-05
o Front paper/Back paper and General changes o Front paper/Back paper and General changes
* Removed all references and special handling of SIP INFO method * Removed all references and special handling of SIP INFO method
Removed references and objects specific to RFC 2976: INFO will Removed references and objects specific to RFC 2976: INFO will
be treated as any SIP extension method. be treated as any SIP extension method.
* Changed requirements verbs from lowercase to uppercase wherever * Changed requirements verbs from lowercase to uppercase wherever
appropriate. appropriate.
* Added RFC Editor notes. * Added RFC Editor notes.
* Updated all REFERENCE clauses and DESCRIPTIONS from RFC 2543 to * Updated all REFERENCE clauses and DESCRIPTIONS from RFC 2543 to
RFC 3261. RFC 3261.
* Explained the approach taken for extension methods that might * Explained the approach taken for extension methods that might
be defined in the future. be defined in the future.
* Defined a mapping of sipServiceOperStatus to applOperStatus. * Defined a mapping of sipServiceOperStatus to applOperStatus.
* Enhanced Security section with details on various objects. * Enhanced Security section with details on various objects.
* Added descriptive language to various Entry objects regarding * Added descriptive language to various Entry objects regarding
the expected persistence of data across system restarts. the expected persistence of data across system restarts.
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 &
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 question/
possibility of resetting the counters to zero. possibility of resetting the counters to zero.
sipStatsExtMethodTable no longer has it╚╦s own RowStatus sipStatsExtMethodTable no longer has it╚╦s own RowStatus
object, so it too can no longer be set to 'notInService╦ where object, so it too can no longer be set to 'notInService╦ where
there was the question/possibility of resetting the counters to there was the question/possibility of resetting the counters to
zero. sipStatsExtMethodTable rows are augmentations of zero. sipStatsExtMethodTable rows are augmentations of
sipExtMethodSupportedEntry. sipExtMethodSupportedEntry.
skipping to change at page 101, line 34 skipping to change at page 82, line 46
sipStatusCodeRowStatus sipCommonStatusCodeNotifTable renaemd to sipStatusCodeRowStatus sipCommonStatusCodeNotifTable renaemd 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, & 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 seperate 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 section 10.2 deprecates the 'action' parameter deleted 3
10.2 deprecates the 'action' parameter deleted 3 objects: objects: sipServerContactDfltAction, sipServerRespectUAAction,
sipServerContactDfltAction, sipServerRespectUAAction,
sipContactAction. sipContactAction.
* Deleted pgp-related objects. RFC 3261 section 23 deprecates
* Deleted pgp-related objects. RFC 3261 section 23 deprecates use use of pgp deleted 3 objects: sipProxyAuthPgpAlgorithm,
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 & 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.
Changes from draft-ietf-sip-mib-04 Changes from draft-ietf-sip-mib-04
o Started realignment with SIP RFC3261. o Started realignment with SIP RFC3261.
Changes from draft-ietf-sip-mib-03 Changes from draft-ietf-sip-mib-03
o Front paper/Back paper and General changes o Front paper/Back paper and General changes
* Rewrote section on Network Services MIB * Rewrote section on Network Services MIB
* Fixed minor editorial nits * Fixed minor editorial nits
o SIP-COMMON-MIB o SIP-COMMON-MIB
* CONTACT-INFO "SIP MIB email" changed to sip@ietf.org * CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
* sipInviteTimeout was removed from the MIB. See below regarding * sipInviteTimeout was removed from the MIB. See below regarding
new sipCommonCfgExpires objects. They provide equivalent new sipCommonCfgExpires objects. They provide equivalent
functionality with extensibility beyond INVITE. functionality with extensibility beyond INVITE.
* sipCommonCfgExpires OID subtree added. Per method Expires * sipCommonCfgExpires OID subtree added. Per method Expires
configuration objects were added there. This new high-level OID configuration objects were added there. This new high-level
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 & 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'
* Clarifying changes to the DESCRIPTION of sipUriSupportedTable. * Clarifying changes to the DESCRIPTION of sipUriSupportedTable.
* Clarifying changes to the DESCRIPTIONs of sipFtrSupportedTable, * Clarifying changes to the DESCRIPTIONs of sipFtrSupportedTable,
sipFtrSupportedEntry, and sipFtrSupported. Specifically, IETF sipFtrSupportedEntry, and sipFtrSupported. Specifically, IETF
standard features and non-standard features are now represented standard features and non-standard features are now represented
by this table. Only non-standard features were mentioned in by this table. Only non-standard features were mentioned in
prior revisions of the draft. prior revisions of the draft.
* Reference to usage of RFC 2788 applIndex moved from * Reference to usage of RFC 2788 applIndex moved from
sipCommonCfgTimerExtMethodTable to sipCommonCfgTimerExtMethodTable to
sipCommonCfgTimerExtMethodEntry. This was the convention for sipCommonCfgTimerExtMethodEntry. This was the convention for
other table/entry definitions in the MIB, so these objects were other table/entry definitions in the MIB, so these objects were
previously unconventional. previously unconventional.
* DEFVAL removed from sipCfgTimerExtMethodTimer. The generic * DEFVAL removed from sipCfgTimerExtMethodTimer. The generic
nature of the "extension" object does not lend itself to being nature of the "extension" object does not lend itself to being
able to specify a particular default value. able to specify a particular default value.
* Since the removal of the DEFVAL clause from * Since the removal of the DEFVAL clause from
sipCfgTimerExtMethodTimer, a value for that object must be sipCfgTimerExtMethodTimer, a value for that object must be
specified when creating a sipCommonCfgTimerExtMethodEntry. The specified when creating a sipCommonCfgTimerExtMethodEntry. The
description of sipCfgTimerExtMethodStatus was updated to description of sipCfgTimerExtMethodStatus was updated to
reflect this. reflect this.
* sipCommonCfgRetryExtMethodTable is now properly defined under * sipCommonCfgRetryExtMethodTable is now properly defined under
sipCommonCfgRetry OID space instead of under sipCommonCfgTimer sipCommonCfgRetry OID space instead of under sipCommonCfgTimer
OID space. OID space.
* DEFVAL removed from sipCfgRetryExtMethodRetry. The generic * DEFVAL removed from sipCfgRetryExtMethodRetry. The generic
nature of the "extension" object does not lend itself to being nature of the "extension" object does not lend itself to being
able to specify a particular default value. able to specify a particular default value.
* Since the removal of the DEFVAL clause from * Since the removal of the DEFVAL clause from
sipCfgRetryExtMethodRetry, a value for that object must be sipCfgRetryExtMethodRetry, a value for that object must be
specified when creating a sipCommonCfgRetryExtMethodEntry. The specified when creating a sipCommonCfgRetryExtMethodEntry. The
description of sipCfgRetryExtMethodStatus was updated to description of sipCfgRetryExtMethodStatus was updated to
reflect this. reflect this.
* Clarifying changes to the DESCRIPTION of * Clarifying changes to the DESCRIPTION of
sipSummaryTotalTransactions. Specifically, the object is not sipSummaryTotalTransactions. Specifically, the object is not
applicable to stateless SIP proxy servers and the object should applicable to stateless SIP proxy servers and the object should
always return a value of 0 if implemented by a stateless proxy. always return a value of 0 if implemented by a stateless proxy.
* Clarifying changes to the DESCRIPTION of * Clarifying changes to the DESCRIPTION of
sipStatsExtMethodStatus. sipStatsExtMethodStatus.
* sipStatsOtherClassesIns and sipStatsOtherClassesOuts counter * sipStatsOtherClassesIns and sipStatsOtherClassesOuts counter
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 gramatical 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, the had clarifying changes to their DESCRIPTIONs. Specifically,
header name will be part of the object value and example values the header name will be part of the object value and example
were given. values were given.
* Minor gramatical change to the DESCRIPTION of * Minor gramatical 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
in the MIB's DESCRIPTION. in the MIB's DESCRIPTION.
* sipServerMIBNotifs OID removed. No notifications were ever * sipServerMIBNotifs OID removed. No notifications were ever
defined under this subtree. defined under this subtree.
* Clarifying text added to all of the Table DESCRIPTIONS stating * Clarifying text added to all of the Table DESCRIPTIONS stating
that the value of applIndex used in this MIB corresponds to the that the value of applIndex used in this MIB corresponds to the
value of applIndex used in the SIP-COMMON-MIB. value of applIndex used in the SIP-COMMON-MIB.
* Clarifying changes to the DESCRIPTION of sipProxyStatefulness. * Clarifying changes to the DESCRIPTION of sipProxyStatefulness.
* sipContactPreference SYNTAX changed from OCTET STRING to * sipContactPreference SYNTAX changed from OCTET STRING to
SnmpAdminString. SnmpAdminString.
o SIP-UA-MIB o SIP-UA-MIB
* CONTACT-INFO "SIP MIB email" changed to sip@ietf.org * CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
* sipUAMIBNotifs OID removed. No notifications were ever defined * sipUAMIBNotifs OID removed. No notifications were ever defined
under this subtree. under this subtree.
* sipUAStats OID removed. No notifications were ever defined * sipUAStats OID removed. No notifications were ever defined
under this subtree. under this subtree.
* Clarifying text added to all of the Table DESCRIPTIONS stating * Clarifying text added to all of the Table DESCRIPTIONS stating
that the value of applIndex used in this MIB corresponds to the that the value of applIndex used in this MIB corresponds to the
value of applIndex used in the SIP-COMMON-MIB. value of applIndex used in the SIP-COMMON-MIB.
o SIP-TC o SIP-TC
* CONTACT-INFO "SIP MIB email" changed to sip@ietf.org * CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
Changes from draft-ietf-sip-mib-02 Changes from draft-ietf-sip-mib-02
o General o General
* Eliminated the SIP-MIB-SMI modules. Each MIB module will now * Eliminated the SIP-MIB-SMI modules. Each MIB module will now
get it's own IANA OID. get it's own IANA OID.
* Top-level OID subtrees restructured in each MIB. * Top-level OID subtrees restructured in each MIB.
* General cleanup/removal of "placeholder" OID subtrees for * General cleanup/removal of "placeholder" OID subtrees for
object groups and notifications that never materialized. object groups and notifications that never materialized.
o SIP-COMMON-MIB o SIP-COMMON-MIB
* Removed sipCfgInitialTimerAck. * Removed sipCfgInitialTimerAck.
* Removed sipCfgRetryAck. * Removed sipCfgRetryAck.
* Removed sipStatsRetryAcks. * Removed sipStatsRetryAcks.
* sipCommonStatsRetryExtMethodEntry was missing its INDEX clause. * sipCommonStatsRetryExtMethodEntry was missing its INDEX clause.
* sipNumUnsupportedUris OID was "5" when it was the only object * sipNumUnsupportedUris OID was "5" when it was the only object
in the table. OID is now "1". in the table. OID is now "1".
* High-level OID structure of the MIB is now sequential. * High-level OID structure of the MIB is now sequential.
* Incorrect object descriptor for sipCfgInitialTimerRsp * Incorrect object descriptor for sipCfgInitialTimerRsp
inconsistent with reference in compliance section. inconsistent with reference in compliance section.
* Inconsistencies between sipCommonStatsRetryGroup definition and * Inconsistencies between sipCommonStatsRetryGroup definition and
SipCommonStatsRetryEntry OBJECT-TYPE corrected. SipCommonStatsRetryEntry OBJECT-TYPE corrected.
* sipNotifApplIndex was not in any object group in the * sipNotifApplIndex was not in any object group in the
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 & 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 auxilliary
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. Security Considerations 9. IANA Considerations
The SIP specification RFC 3261 [7] Section 27.4 establishes the
Method and Response-Code sub-registries under
http://www.iana.org/assignments/sip-parameters.
The SIP-COMMON-MIB requires that unique numeric identifiers be
assigned by IANA for each Method in the above registry. It is
expected that IANA will create those method identifies in the same
sub-registry and assign a new method ID for registered methods. For
e.g., the mapping of method identifiers to methods will be
represented by a table in the MIB: sipSupportedMethodTable.
SIP-COMMON-MIB sipCommonCfgTable might be populated as:
+-------------------------+------------------------+
| sipMethodSupportedIndex | sipMethodSupportedName |
+-------------------------+------------------------+
| 1 | "INVITE" |
| 2 | "ACK" |
| 3 | "BYE" |
| 4 | "CANCEL" |
| 5 | "OPTIONS" |
| 6 | "CANCEL" |
| 7 | "INFO" |
| 8 | "SUBSCRIBE" |
| 9 | "NOTIFY" |
+-------------------------+------------------------+
etc.
The numeric identifiers will also be used in other MIB tables where
it is sufficient and/or more effective to refer to a method by a
number rather than by a string.
10. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
These are the tables and objects and their sensitivity/vulnerability: These are the tables and objects and their sensitivity/vulnerability:
o SIP-COMMON-MIB o SIP-COMMON-MIB
The following read-write object is used to control the overal
The following read-write object is used to control the overall
SIP service in any SIP entity: SIP service in any SIP entity:
sipServiceAdminStatus sipServiceAdminStatus
If this object is SET maliciously, it may result in unwanted If this object is SET maliciously, it may result in unwanted
operational status, or a failure to obtain SIP services. operational status, or a failure to obtain SIP services.
The following read-write and read-create objects are used to The following read-write and read-create objects are used to
control the behavior of the SIP protocol as exhibited by a SIP control the behavior of the SIP protocol as exhibited by a SIP
entity: entity:
sipOrganization, sipCfgTimerA, sipCfgTimerB, sipCfgTimerC,
sipOrganization, sipRequestUriHostMatching, sipCfgTimerA, sipCfgTimerD, sipCfgTimerE, sipCfgTimerF, sipCfgTimerG,
sipCfgTimerB, sipCfgTimerC, sipCfgTimerD, sipCfgTimerE, sipCfgTimerH, sipCfgTimerI, sipCfgTimerJ, sipCfgTimerK,
sipCfgTimerF, sipCfgTimerG, sipCfgTimerH, sipCfgTimerI, sipCfgTimerT1, sipCfgTimerT2, sipCfgTimerT4.
sipCfgTimerJ, sipCfgTimerK, sipCfgTimerT1, sipCfgTimerT2, If these objects are SET maliciously, it may result in serious
sipCfgTimerT4, sipCfgTimerExtMethodTimer, sipCfgRetryInvite, protocol misbehavior or misoperation. In particular, the
sipCfgRetryBye, sipCfgRetryCancel, sipCfgRetryRegister, objects are related to the core SIP protocol stack timers,
sipCfgRetryOptions, sipCfgRetryFinalResponse, retries and request expiration values: all of these control how
sipCfgRetryNonFinalResponse, sipCfgRetryExtMethodRetry, the SIP state machines are executed at runtime. It is
sipCfgExpiresInvite, sipCfgExpiresRegister, therefore possible that the SIP service be affected, stalled or
sipCfgExpiresHeaderMethod, sipCfgExpiresHeaderValue, completely stopped if erroneous values are SET maliciously.
sipCfgExpiresStatusCodeStatus
If these objects are SET maliciously, it may result in
incorrect or unwanted protocol operation.
The following read-create object is used to configure the The following read-create object is used to configure the
status code statistics that will be monitored by the SIP status code statistics that will be monitored by the SIP
entity: entity:
sipStatusCodeRowStatus sipStatusCodeRowStatus
If this object is SET maliciously, it may result in an over 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 The following read-write objects are used to configure the
behavior of certain SNMP notifications potentially generated by behavior of certain SNMP notifications potentially generated by
a SIP entity: 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 o SIP-UA-MIB
The following read-create objects are used to configure the The following read-create objects are used to configure the
Internet address of SIP servers a SIP User Agent will use to Internet address of SIP servers a SIP User Agent will use to
proxy/redirect SIP calls: proxy/redirect SIP calls:
sipUACfgServerAddrType, sipUACfgServerAddr,
sipUACfgSipServerAddrType, sipUACfgSipServerAddr, sipUACfgServerFunction, sipUACfgServerStatus.
sipUACfgSipServerStatus.
If these objects are SET maliciously, it may result in unwanted If these objects are SET maliciously, it may result in unwanted
operation, or a failure to obtain SIP services from the user operation, or a failure to obtain SIP services from the user
agent prospective or even theft of service. In particular, agent prospective or even theft of service. In particular,
setting the SipUACfgSipServerStatus object instance to the setting the SipUACfgSipServerStatus object instance to the
'destroy' value may result in service disruption. 'destroy' value may result in service disruption.
o SIP-SERVER-MIB o SIP-SERVER-MIB
The following read-create objects are managed by Registrar The following read-create objects are managed by Registrar
Servers and contain sensitive or private information about the Servers and contain sensitive or private information about the
address of record of registered users. address of record of registered users.
sipUserUri & sipUserTableRowStatus sipUserUri & sipUserTableRowStatus
The sensitivity of these objects depends on the role that The sensitivity of these objects depends on the role that
Registrar Servers play in the SIP service. In some cases, these Registrar Servers play in the SIP service. In some cases,
objects, if SET maliciously, may allow unregistered users to these objects, if SET maliciously, may allow unregistered users
steal service, or may prevent registered users from accessing to steal service, or may prevent registered users from
the SIP service. accessing the SIP service.
The following read-write objects, if SET maliciously will have The following read-write objects, if SET maliciously will have
an immediate serious impact on the service: an immediate serious impact on the service:
sipServerHostAddrType & sipServerHostAddr sipServerHostAddrType & sipServerHostAddr
These objects specify the host part of the URI for the server These objects specify the host part of the URI for the server
providing the SIP resource and it is widely used by SIP servers providing the SIP resource and it is widely used by SIP servers
in numerous header lines and field. For e.g., the host address 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 may be used with the Request-URI to check if the server is the
one resolved by the Request-URI, therefore determining whether one resolved by the Request-URI, therefore determining whether
to process or forward the request in the case of outbound to process or forward the request in the case of outbound
proxies, or, as an another common example, it is used by Proxy proxies, or, as an another common example, it is used by Proxy
Servers acting as strict routers to rewrite the Request-URI. Servers acting as strict routers to rewrite the Request-URI.
Setting these objects with improper values may result in Setting these objects with improper values may result in
serious service interference or failure. serious service interference or failure.
skipping to change at page 110, line 25 skipping to change at page 89, line 42
These objects specify the host part of the URI for the server These objects specify the host part of the URI for the server
providing the SIP resource and it is widely used by SIP servers providing the SIP resource and it is widely used by SIP servers
in numerous header lines and field. For e.g., the host address 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 may be used with the Request-URI to check if the server is the
one resolved by the Request-URI, therefore determining whether one resolved by the Request-URI, therefore determining whether
to process or forward the request in the case of outbound to process or forward the request in the case of outbound
proxies, or, as an another common example, it is used by Proxy proxies, or, as an another common example, it is used by Proxy
Servers acting as strict routers to rewrite the Request-URI. Servers acting as strict routers to rewrite the Request-URI.
Setting these objects with improper values may result in Setting these objects with improper values may result in
serious service interference or failure. serious service interference or failure.
sipRequestMaxExpires and sipRegMaxContactExpiryDuration: if set sipRequestMaxExpires and sipRegMaxContactExpiryDuration: if set
to a zero value and either SIP requests contain an Expires to a zero value and either SIP requests contain an Expires
header or Contact header contain an expires parameter, may header or Contact header contain an expires parameter, may
cause the server to never create bindings associated with an cause the server to never create bindings associated with an
address of record (case of REGISTER request) or may cause address of record (case of REGISTER request) or may cause
server to expire and cancel invitations (case of INVITE server to expire and cancel invitations (case of INVITE
request). request).
sipProxyStatefulness: changing the value of this object affects sipProxyStatefulness: changing the value of this object affects
how transaction states are being handled the Proxy Server and how transaction states are being handled the Proxy Server and
may result in call feature or service changes. may result in call feature or service changes.
sipProxyAuthMethod: this object specifies at a maximum what the sipProxyAuthMethod: this object specifies at a maximum what the
authentication methods that may be used by a server. If this authentication methods that may be used by a server. If this
object is SET maliciously, it may alter how the level of object is SET maliciously, it may alter how the level of
security used by the server to generate requests and may security used by the server to generate requests and may
compromise the network security policies. compromise the network security policies.
sipRegAllowThirdParty: depending on the authentication policy sipRegAllowThirdParty: depending on the authentication policy
associated with registration services, setting this object associated with registration services, setting this object
maliciously to 'true' may allow theft of identity or service. maliciously to 'true' may allow theft of identity or service.
sipProxyAuthRealm: if this object is SET improperly, and if the sipProxyAuthRealm: if this object is SET improperly, and if the
HTTP Digest authentication method is used, it may result in HTTP Digest authentication method is used, it may result in
clients being unable to authenticate and ultimately, in the clients being unable to authenticate and ultimately, in the
server denying service. server denying service.
The remaining read-write objects, if SET maliciously may have The remaining read-write objects, if SET maliciously may have
some effect on the service: some effect on the service:
SipProxySendsCancel: this is a configuration object defining
how a certain class of proxy servers (forking proxies) handle
cancellation of outstanding branch requests. If this object was
set to true and is maliciously changed to false, the impact is
considered moderate: the forking proxy may simply terminate the
outstanding branches at a later phase, either when a
transaction timer expires or when subsequent messages arrive
from the outstanding branches.
sipProxyRecordRoute: setting this object to true may cause sipProxyRecordRoute: setting this object to true may cause
additional SIP traffic to cross the proxy server and may result additional SIP traffic to cross the proxy server and may result
in message avalanches. in message avalanches.
The threats posed by the following read-write objects can The threats posed by the following read-write objects can
either be mitigated by other configuration settings like either be mitigated by other configuration settings like
read-only objects or they are considered to cause additional read-only objects or they are considered to cause additional
server operations without immediate impact on the server like server operations without immediate impact on the servive.
additional location look-ups (sipProxyProvideAlternatives), sipProxyRecursion and sipRegDfltRegActiveInterval
additional traffic due to expiration of nonce
(sipProxyNonceLifeTime).
sipProxyForwardAll1xx, sipProxyRecursion,
sipProxyProvideAlternatives sipProxyNonceLifeTime, and
sipRegDfltRegActiveInterval
Some of the readable objects in the MIB modules (i.e., objects Some of the readable objects in the MIB modules (i.e., objects
with a MAX-ACCESS other than not-accessible) may be considered with a MAX-ACCESS other than not-accessible) may be considered
sensitive or vulnerable in some network environments. It is sensitive or vulnerable in some network environments. It is
thus important to control even GET and/or NOTIFY access to thus important to control even GET and/or NOTIFY access to
these objects and possibly to even encrypt the values of these these objects and possibly to even encrypt the values of these
objects when sending them over the network via SNMP. 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, and
SipContactLastUpdated. SipContactLastUpdated.
The sipMethodSupportedTable table contains the 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.
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security.
if the network itself is secure (for example by using IPSec), even Even if the network itself is secure (for example by using IPSec),
then, there is no control as to who on the secure network is allowed even then, there is no control as to who on the secure network is
to access and GET/SET (read/change/create/delete) the objects in this allowed to access and GET/SET (read/change/create/delete) the objects
MIB module. in this MIB module.
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 [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including 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.
10. 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 & SIPPING working groups
& the SIP-MIB Design team for their comments and suggestions. & the SIP-MIB Design team for their comments and suggestions.
Detailed comments were provided by Tom Taylor, Kavitha Patchayappan Detailed comments were provided by Tom Taylor, Kavitha Patchayappan,
and Dan Romascanu. Dan Romascanu, Cullen Jennins, Orit Levin, AC Mahendran, Mary Barnes
and Rohan Mahy.
Normative References 12. References
12.1 Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction [2] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction
and Applicability Statements for Internet-Standard Management and Applicability Statements for Internet-Standard Management
Framework", RFC 3410, December 2002. Framework", RFC 3410, December 2002.
[3] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [3] 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
skipping to change at page 113, line 9 skipping to change at page 92, line 9
2788, March 2000. 2788, March 2000.
[7] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., [7] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:
Session Initiation Protocol", RFC 3261, June 2002. Session Initiation Protocol", RFC 3261, June 2002.
[8] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder, [8] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder,
"Textual Conventions for Internet Network Addresses", RFC 3291, "Textual Conventions for Internet Network Addresses", RFC 3291,
May 2002. May 2002.
Informational References 12.2 Informational References
[9] Hoffman, P., Masinter, L. and J. Zawinski, "The mailto URL [9] 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 [10] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396, August Resource Identifiers (URI): Generic Syntax", RFC 2396, August
1998. 1998.
Authors' Addresses Authors' Addresses
skipping to change at page 113, line 31 skipping to change at page 92, line 31
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
Joon Maeng Joon Maeng
ipDialog, Inc.
7701 N. Lamar Blvd., Suite 304
Austin, TX 78752-1023