draft-ietf-sip-mib-06.txt   draft-ietf-sip-mib-07.txt 
Internet Engineering Task Force K. Lingle SIP WG K. Lingle
Internet Draft Cisco Systems Internet-Draft Cisco Systems, Inc.
Document: draft-ietf-sip-mib-06.txt J. Maeng Expires: December 30, 2003 J. Maeng
July 2003 ipDialog, Inc. ipDialog, Inc.
Expires: December 2003 J-F. Mule J-F. Mule
CableLabs CableLabs
D. Walker D. Walker
SS8 Networks, Inc. SS8 Networks, Inc.
July 2003
Management Information Base Management Information Base for Session Initiation Protocol (SIP)
for Session Initiation Protocol draft-ietf-sip-mib-07.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [RFC2026]. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that other
other groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-Drafts.
Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other documents and may be updated, replaced, or obsoleted by other documents at any
at any time. It is inappropriate to use Internet-Drafts as time. It is inappropriate to use Internet-Drafts as reference
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://
www.ietf.org/ietf/1id-abstracts.txt.
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This particular draft is being developed in the Session Initiation This Internet-Draft will expire on December 30, 2003.
Protocol Working Group. Discussion of it therefore belongs on that
list. The charter for Session Initiation Protocol may be found at Copyright Notice
http://www.ietf.org/html.charters/sip-charter.html
Copyright (C) The Internet Society (2003). 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 In particular, it describes a set of managed objects that are used to
to manage Session Initiation Protocol (SIP) entities, which include manage Session Initiation Protocol (SIP) entities, which include User
User Agents, Proxy servers, Redirect servers and Registrars. Agents, Proxy servers, Redirect servers and Registrars.
Table of Contents Table of Contents
Abstract.........................................................1 1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction..................................................2 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework....................2 3. The Internet-Standard Management Framework . . . . . . . . . 3
3. Overview......................................................3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Structure of SIP MIB..........................................3 5. Structure of SIP MIB . . . . . . . . . . . . . . . . . . . . 3
4.1. Textual Conventions........................................5 5.1 Textual Conventions . . . . . . . . . . . . . . . . . . . . 6
4.2. Relationship to Other MIBs.................................6 5.2 Relationship to the Network Services MIB . . . . . . . . . . 6
5. Definitions...................................................9 6. Accommodating SIP Extension Methods . . . . . . . . . . . . 10
5.1. SIP Textual Conventions....................................9 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2. SIP Common................................................11 7.1 SIP Textual Conventions . . . . . . . . . . . . . . . . . . 10
5.3. SIP User Agent............................................66 7.2 SIP Common MIB Module . . . . . . . . . . . . . . . . . . . 12
5.4. SIP Server (Registrar, Redirect & Proxy Server)...........71 7.3 SIP User Agent MIB Module . . . . . . . . . . . . . . . . . 73
6. Changes from previous drafts.................................89 7.4 SIP Server (Registrar, Redirect & Proxy Server) MIB Module . 78
7. Security Considerations......................................97 8. Changes from Previous Draft Revisions . . . . . . . . . . . 98
8. Intellectual Property.......................................101 9. Security Considerations . . . . . . . . . . . . . . . . . . 108
9. Full Copyright Statement....................................101 10. Contributor Acknowledgments . . . . . . . . . . . . . . . . 112
10. Normative References......................................103 Normative References . . . . . . . . . . . . . . . . . . . . 112
11. Informative References....................................103 Informational References . . . . . . . . . . . . . . . . . . 113
12. Acknowledgments...........................................104 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 113
13. Author's Addresses........................................104 Intellectual Property and Copyright Statements . . . . . . . 115
1. Introduction
This memo defines a portion of the Management Information Base (MIB) 1. Conventions
for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that are used
to manage Session Initiation Protocol (SIP) entities, which include
User Agents, Proxy servers, Redirect servers and Registrars.
Conventions used in this document
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 BCP 14, RFC 2119 document are to be interpreted as described in RFC 2119 [1].
[RFC2119].
2. The Internet-Standard Management Framework 2. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that are used to
manage Session Initiation Protocol (SIP) entities, which include User
Agents, Proxy servers, Redirect servers and Registrars.
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 [RFC3410]. RFC 3410 [2]. Managed objects are accessed via a virtual information
store, termed the Management Information Base or MIB. MIB objects
Managed objects are accessed via a virtual information store, termed are generally accessed through the Simple Network Management Protocol
the Management Information Base or MIB. MIB objects are generally (SNMP). Objects in the MIB are defined using the mechanisms defined
accessed through the Simple Network Management Protocol (SNMP). in the Structure of Management Information (SMI). This memo
Objects in the MIB are defined using the mechanisms defined in the specifies a MIB module that is compliant to the SMIv2, which is
Structure of Management Information (SMI). This memo specifies a described in STD 58, RFC 2578 [3], STD 58, RFC 2579 [4] and STD 58,
MIB module that is compliant to the SMIv2, which is described in STD RFC 2580 [5].
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
2580 [RFC2580].
3. Overview 4. Overview
The Session Initiation Protocol (SIP) [RFC3261] 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, SIP entities defined in RFC 3261 - User Agent, Proxy Server, Redirect
Redirect Server and Registrar. It is provided as a base for the work Server and Registrar. It is provided as a base for the work within
within the working group to define a MIB. the working group to define a MIB. This MIB is intended to provide
management of the basic SIP entities. It provides for monitoring of
This MIB is intended to provide management of the basic SIP status and protocol statistics, as well as for configuration of SIP
entities. It provides for monitoring of status and protocol entities.
statistics, as well as for configuration of SIP entities.
4. 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 used in all the SIP entities. SIP-SERVER-MIB contains objects
objects specific to Registrars, Proxies and Redirect Servers, and specific to Registrars, Proxies and Redirect Servers, and SIP-UA-MIB
SIP-UA-MIB includes objects specific to User Agents. SIP-TC defines includes objects specific to User Agents. SIP-TC defines the textual
the textual conventions used throughout MIB modules. conventions used throughout MIB modules. The MIB Modules contain
following groups of objects:
The MIB Modules 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
sipCommonMIBObjects * sipCommonCfgBase: This object group defines configuration
| objects common to all SIP entities including SIP protocol
+ sipCommonCfgBase version, operational and administrative status, SIP
| This object group defines configuration objects common to organization name, max number of SIP sessions an entity can
| all SIP entities including SIP protocol version, operational manage, etc.
| and administrative status, SIP organization name, max number
| of SIP sessions an entity can manage, etc. * sipCommonCfgTimer: This object group defines timer
| configuration objects applicable to SIP user agent and SIP
+ sipCommonCfgTimer stateful proxy entities.
| This object group defines timer configuration objects
| applicable to SIP user agent and SIP stateful proxy entities. * sipCommonCfgRetry: This object group defines retry counter
| configuration objects applicable to SIP user agent and SIP
+ sipCommonCfgRetry stateful proxy entities.
| 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
+ sipCommonCfgExpires SIP stateful proxies
| 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
| containing the summary statistics objects applicable to all SIP
+ sipCommonStatsSummary entities, including the total number of SIP requests &
| This object group defines a table containing the summary responses in/out, total number of transactions, etc.
| statistics objects applicable to all SIP entities, including
| the total number of SIP requests & responses in/out, total * sipCommonStatsMethod: This object group defines a table
| number of transactions, etc. containing the per method statistics objects applicable to all
| SIP entities, including the total number of SIP requests for
+ sipCommonStatsMethod the Invite, Ack, Bye, Cancel, Options and /Register methods.
| This object group defines a table containing the per method
| statistics objects applicable to all SIP entities, including * sipCommonStatusCode: This object group defines a table
| the total number of SIP requests for the Invite, Ack, Bye, indicating the number of SIP responses in/out per class of
| Cancel, Options and /Register methods. response (1xx, 2xx, etc.)
|
+ sipCommonStatusCode * sipCommonStatsTrans: This object group defines a table
| This object group defines a table indicating the number of containing a gauge reflecting the number of transactions
| SIP responses in/out per class of response (1xx, 2xx, etc.) currently awaiting definitive responses by the managed SIP
| entity.
+ sipCommonStatsTrans
| This object group defines a table containing a gauge * sipCommonStatsRetry: This object group defines statistic
| reflecting the number of transactions currently awaiting objects indicating the number of retries sent on a per method
| definitive responses by the managed SIP entity. basis.
|
+ sipCommonStatsRetry * sipCommonStatsOther: This object group defines additional
| This object group defines statistic objects indicating the statistic objects including a counter of the number of SIP
| number of retries sent on a per method basis. requests received with unsupported URIs.
|
+ sipCommonStatsOther * sipCommonNotifObjects: This object group defines
| This object group defines additional statistic objects accessible-for-notify objects that are relate to the SNMP
| including a counter of the number of SIP requests received notifications defined in this MIB module.
| with unsupported URIs.
|
+ sipCommonNotifObjects
This object group defines accessible-for-notify objects
that are relate to the SNMP notifications defined in this
MIB module.
The SIP-COMMON-MIB also contains notifications, including: The SIP-COMMON-MIB also contains notifications, including:
+ sipStatusCodeNotif
| indicates that a specific status code has been sent or
| received by the system.
|
+ sipStatusCodeThreshExceededNotif
| indicates that a specific status code has been sent or
| received by the system enough to exceed the configured
| threshold.
-- SIP-SERVER-MIB: Groups of objects for Registrars, Proxy and o sipStatusCodeNotif: indicates that a specific status code has been
-- Redirect Servers sent or received by the system.
sipServerMIBObjects
|
+ sipServerCfg
| This object group defines common server configuration objects
| including the SIP server host address.
| o sipStatusCodeThreshExceededNotif: indicates that a specific status
+ sipServerStats code has been sent or received by the system enough to exceed the
| This object group is currently empty and is created for configured threshold.
| future extensions of the SIP MIB.
|
+ sipProxyCfg
| This object group defines Proxy Server configuration objects
| including the maximum duration in the Expires header, the
| proxy mode of operation (stateless, stateful, call stateful),
| the cancellation of outstanding branch requests
|
+ sipProxyStats
| This object group defines a table containing the statistics
| objects applicable to all SIP Proxy Servers. It
| includes the number of occurrences of unsupported options
| being specified in received Proxy-Require headers.
|
+ sipRedirCfg
| This object group is currently empty and is created for
| future extensions of the SIP MIB.
|
+ sipRedirStats
| This object group is currently empty and is created for
| future extensions of the SIP MIB.
|
+ sipRegCfg
| This object group is currently empty and is created 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-SERVER-MIB: Groups of objects for Registrars, Proxy and Redirect
sipUAMIBObjects Servers
|
+ sipUACfgSipServer o sipServerMIBObjects
This group specifies SIP server configuration objects
applicable to SIP user agents including the Internet address * sipServerCfg: This object group defines common server
of the SIP Server to use to proxy or redirect calls. 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
configuration objects including the maximum duration in the
Expires header, the proxy mode of operation (stateless,
stateful, call stateful), the cancellation of outstanding
branch requests
* sipProxyStats: This object group defines a table containing the
statistics objects applicable to all SIP Proxy Servers. It
includes the number of occurrences of unsupported options being
specified in received Proxy-Require headers.
* sipRedirCfg: This object group is currently empty and is
created for future extensions of the SIP MIB.
* sipRedirStats: This object group is currently empty and is
created for future extensions of the SIP MIB.
* sipRegCfg: This object group is currently empty and is created
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.
o sipUAMIBObjects
* sipUACfgSipServer: This group specifies SIP server
configuration objects applicable to SIP user agents including
the Internet address of the SIP Server to use to proxy or
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 specific MIB modules (SIP-SERVER-MIB or SIP-UA-MIB) as applicable for
for each instance of a SIP entity being managed. If a device has each instance of a SIP entity being managed. If a device has more
more than one SIP entity or multiple instances of the same entity, than one SIP entity or multiple instances of the same entity, type it
type it MUST implement multiple SIP modules. Section 4.2 describes MUST implement multiple SIP modules. Section 4.2 describes handling
handling of multiple instances in detail. of multiple instances in detail.
4.1. Textual Conventions 5.1 Textual Conventions
The data type SipTransportProtocol is used as textual conventions in The data type SipTransportProtocol is used as Textual Conventions in
this document. These textual conventions have NO effect on either this document. These Textual Conventions have NO effect on either
the syntax or the semantics of any managed object. Objects defined the syntax or the semantics of any managed object. Objects defined
using these conventions are always encoded by means of the rules using these conventions are always encoded by means of the rules that
that define their primitive type. Hence, no changes to the SMI or define their primitive type. Hence, no changes to the SMI or the
the SNMP are necessary to accommodate these textual conventions, SNMP are necessary to accommodate these Textual Conventions. They are
which are adopted merely for the convenience of readers. adopted merely for the convenience of readers.
4.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 [RFC2788]. A device implementing the NETWORK-SERVICES-MIB, RFC 2788 [6]. A device implementing the SIP MIB
SIP MIB MUST support the NETWORK-SERVICES-MIB and, at a minimum, it MUST support the NETWORK-SERVICES-MIB and, at a minimum, it MUST
MUST support the applIndex and applName objects in applTable. The support the applIndex and applName objects in applTable. The
following applName conventions will be adopted: following applName conventions will be adopted:
o for a SIP Proxy entity, applName MUST be equal to "sip_proxy" o for a SIP Proxy entity, applName MUST be equal to "sip_proxy"
o for a SIP Redirect entity, applName MUST be equal to o for a SIP Redirect entity, applName MUST be equal to
"sip_redirect" "sip_redirect"
o for a SIP Registrar entity, applName MUST be equal to o for a SIP Registrar entity, applName MUST be equal to
"sip_registrar" "sip_registrar"
o for a SIP User Agent entity, applName MUST be equal to
"sip_ua"
o for any combination of Proxy, Registrar, or Redirect Server
being managed as a single aggregate entity, the applName for
the combined server entity MUST reflect the appropriate
combination. For example, "sip_proxy_redirect" or
"sip_proxy_registrar".
The SNMP agent MAY support any combination of the other attributes o for a SIP User Agent entity, applName MUST be equal to "sip_ua"
in applTable. If the following objects are supported, the object
values SHOULD be populated as follows: o for any combination of Proxy, Registrar, or Redirect Server being
managed as a single aggregate entity, the applName for the
combined server entity MUST reflect the appropriate combination.
For example, "sip_proxy_redirect" or "sip_proxy_registrar".
The SNMP agent MAY support any combination of the other attributes in
applTable. If the following objects are supported, the object values
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 in the SIP-COMMON-MIB module, o applUptime: value MUST be identical to sipServiceStartTime defined
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 defined in sipServiceOperStatus, at least by means of a mapping,
mapping,
o applLastChange: value MUST be identical to
sipServiceLastChange defined in the SIP-COMMON module.
Note: There are a number of other objects in the applTable. They o applLastChange: value MUST be identical to sipServiceLastChange
are not included for the sake of brevity and for the fact that they defined in the SIP-COMMON module.
do not enhance the concept being presented.
Note: There are a number of other objects in the applTable. They are
not included for the sake of brevity and for the fact that they do
not enhance the concept being presented.
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
Registrar server might be configured to maintain separate SIP- Registrar server might be configured to maintain separate SIP-
COMMON-MIB instances. COMMON-MIB instances.
The NETWORK-SERVICES-MIB applTable might be populated as follows: The NETWORK-SERVICES-MIB applTable might be populated as follows:
applIndex | applName | applDescription +-----------+-----------------+----------------------+
----------+-----------------+------------------------------ | applIndex | applName | applDescription |
1 | "sip_proxy" | "ACME SIP Proxy" +-----------+-----------------+----------------------+
----------+-----------------+------------------------------ | 1 | "sip_proxy" | "ACME SIP Proxy" |
2 | "sip_registrar" | "ACME SIP Registrar" | 2 | "sip_registrar" | "ACME SIP Registrar" |
----------+-----------------+------------------------------ +-----------+-----------------+----------------------+
The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for the
the proxy (applIndex=1) and one for the registrar (applIndex=2). proxy (applIndex=1) and one for the registrar (applIndex=2). The
The SIP-SERVER-MIB tables would, however, only be populated with one SIP-SERVER-MIB tables would, however, only be populated with one row
row indexed by applIndex=1 and applIndex=2 respectively if the indexed by applIndex=1 and applIndex=2 respectively if the server
server provides either proxy or registrar. provides either proxy or registrar.
SIP-COMMON-MIB sipCommonCfgTable might be populated as: SIP-COMMON-MIB sipCommonCfgTable might be populated as:
applIndex | sipProtocolVersion | sipServiceOperStatus | ... +-----------+---------------------+----------------------+-----+
----------+--------------------+----------------------+---- | applIndex | sipProtocolVerfsion | sipServiceOperStatus | ... |
1 | "SIP/2.0" | up(1) | +-----------+---------------------+----------------------+-----+
----------+--------------------+----------------------+---- | 1 | "SIP/2.0" | up(1) | |
2 | "SIP/2.0" | restarting(4) | | 2 | "SIP/2.0" | restarting(4) | |
----------+--------------------+----------------------+---- +-----------+---------------------+----------------------+-----+
while sipProxyCfgTable in SIP-SERVER-MIB might be populated as: while sipProxyCfgTable in SIP-SERVER-MIB might be populated as:
applIndex | sipRequestMaxExpires | sipProxyStatefulness | ... +-----------+----------------------+----------------------+-----+
----------+----------------------+----------------------+---- | applIndex | 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 | drwalker@ss8.com | |
2 | 2 | jmaeng@ipdialog.com | | 2 | 2 | jmaeng@ipdialog.com | |
----------+--------------+--------------------------+---- | 2 | 3 | klingle@cisco.com | |
2 | 3 | klingle@cisco.com | | 2 | 4 | jfm@cablelabs.com | |
----------+--------------+--------------------------+---- +-----------+--------------+---------------------+-----+
2 | 4 | jfm@cablelabs.com |
----------+--------------+--------------------------+----
Example 2: Example 2:
This example illustrates how to represent a system acting as both This example illustrates how to represent a system acting as both
Proxy and Registrar server, where the two entities share a single Proxy and Registrar server, where the two entities share a single
instance of SIP-COMMON-MIB. instance of SIP-COMMON-MIB.
The NETWORK-SERVICES-MIB applTable might be populated as follows: The NETWORK-SERVICES-MIB applTable might be populated as follows:
applIndex | applName | applDescription +-----------+-----------------------+------------------------------+
----------+----------------------+--------------------------- | applIndex | applName | applDescription |
1 | "sip_proxy_registrar"| "ACME SIP Proxy&Registrar" +-----------+-----------------------+------------------------------+
----------+----------------------+--------------------------- | 1 | "sip_proxy_registrar" | "ACME SIP Proxy & Registrar" |
+-----------+-----------------------+------------------------------+
The SIP-COMMON-MIB sipCommonCfgTable would have only one row to The SIP-COMMON-MIB sipCommonCfgTable would have only one row to cover
cover both the proxy and the registrar. both the proxy and the registrar.
SIP-COMMON-MIB sipCommonCfgTable might be populated as: SIP-COMMON-MIB sipCommonCfgTable might be populated as:
applIndex | sipProtocolVersion | sipServiceOperStatus | ... +-----------+--------------------+----------------------+
----------+--------------------+----------------------+---- | applIndex | sipProtocolVersion | sipServiceOperStatus |
1 | "SIP/2.0" | up(1) | +-----------+--------------------+----------------------+
----------+--------------------+----------------------+---- | 1 | "SIP/2.0" | up(1) |
+-----------+--------------------+----------------------+
while sipProxyCfgTable in SIP-SERVER-MIB is populated as: while sipProxyCfgTable in SIP-SERVER-MIB is populated as:
applIndex | sipRequestMaxExpires | 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 | ... |
1 | 1 | drwalker@ss8networks.com | +-----------+--------------+---------------------+-----+
----------+--------------+--------------------------+---- | 2 | 1 | drwalker@ss8.com | |
1 | 2 | jmaeng@ipdialog.com | | 2 | 2 | jmaeng@ipdialog.com | |
----------+--------------+--------------------------+---- | 2 | 3 | klingle@cisco.com | |
1 | 3 | klingle@cisco.com | | 2 | 4 | jfm@cablelabs.com | |
----------+--------------+--------------------------+---- +-----------+--------------+---------------------+-----+
1 | 4 | jfm@cablelabs.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 applOperStatus
-------------------- -------------- +----------------------+-----------------------+-------------------+
up --> up | sipServiceOperStatus | -- corresponds to --> | applOperstatus |
down --> down +----------------------+-----------------------+-------------------+
congested --> congested | up | --> | up |
restarting --> restarting | down | --> | down |
quiescing --> quiescing | congested | --> | congested |
testing --> up | restarting | --> | restarting |
unknown --> --indeterminate-- | quiescing | --> | quiescing |
- | testing | --> | up |
- | 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.
4.3. Accommodating SIP Extension Methods 6. Accommodating SIP Extension Methods
The core set of SIP methods is defined in RFC3261. Other Internet- The core set of SIP methods is defined in RFC 3261 [7]. Other
Draft documents and RFCs define additional methods. In the future Internet- Draft documents and RFCs define additional methods. In the
more methods may be defined. In order to avoid having to update the future more methods may be defined. In order to avoid having to
SIP-COMMON-MIB module to accommodate these extension methods, there update the SIP-COMMON-MIB module to accommodate these extension
are various extension method tables throughout the MIB module. methods, there are various extension method tables throughout the MIB
There is no per method objects defined in the other MIB modules. module. There are no per method objects defined in the other MIB
modules.
The sipExtMethodSupportedTable is the main table for listing all of The sipExtMethodSupportedTable is the main table for listing all of
the extension methods supported by a system. The table is the extension methods supported by a system. The table is
informational in nature and populated by the system. Entries cannot informational in nature and populated by the system. Entries cannot
be added or deleted by a SNMP manager. The other extension method be added or deleted by a SNMP manager. The other extension method
tables in the MIB are augmentations of this table. tables in the MIB are augmentations of this table.
The other extension method tables defined in the SIP-COMMON-MIB are: The other extension method tables defined in the SIP-COMMON-MIB are:
sipCommonCfgTimerExtMethodTable, sipCommonCfgRetryExtMethodTable, sipCommonCfgTimerExtMethodTable, sipCommonCfgRetryExtMethodTable,
sipStatsExtMethodTable, and sipCommonStatsRetryExtMethodTable. sipStatsExtMethodTable, and sipCommonStatsRetryExtMethodTable.
5. Definitions 7. Definitions
5.1. SIP Textual Conventions 7.1 SIP Textual Conventions
SIP-TC DEFINITIONS ::= BEGIN SIP-TC DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
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 "200306250000Z" LAST-UPDATED "200307300000Z"
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 10, line 40 skipping to change at page 11, line 36
postal: 400 Centennial Parkway postal: 400 Centennial Parkway
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 Copyright (C) The Internet Society (2003). This version
version of this MIB module is part of RFC XXXX; see of this MIB module is part of RFC XXXX; see the RFC
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 "200306250000Z" REVISION "200307300000Z"
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 -- RFC Ed: replace xx with actual IANA assigned number and remove this note
-- this note
-- --
-- Textual Conventions -- Textual Conventions
-- --
SipTransportProtocol ::= TEXTUAL-CONVENTION SipTransportProtocol ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention is a bit map. Each bit represents "This convention is a bit map. Each bit represents a
a transport protocol. If a bit has value 1, then transport protocol. If a bit has value 1, then that
that selected transport protocol is in some way selected transport protocol is in some way dependent
dependent on the context of the object using this on the context of the object using this convention.
convention.
If a bit has value 0, then that transport protocol If a bit has value 0, then that transport protocol
is not selected. Combinations of bits can be is not selected. Combinations of bits can be
set when multiple transport protocols are selected. set when multiple transport protocols are selected.
bit 0 : a protocol other than those defined here. bit 0 : a protocol other than those defined here.
bit 1 : User Datagram Protocol. bit 1 : User Datagram Protocol.
bit 2 : Transmission Control Protocol. bit 2 : Transmission Control Protocol.
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"
END END
5.2. SIP Common 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,
skipping to change at page 12, line 14 skipping to change at page 13, line 20
SipTransportProtocol SipTransportProtocol
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 "200306250000Z" LAST-UPDATED "200307300000Z"
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 13, line 37 skipping to change at page 14, line 49
A Redirect Server accepts requests from clients and A Redirect Server accepts requests from clients and
returns zero or more addresses to that client. Unlike returns zero or more addresses to that client. Unlike
a Proxy Server it does not initiate requests. Unlike a Proxy Server it does not initiate requests. Unlike
a User Agent Server it does not accept calls. a User Agent Server it does not accept calls.
A Registrar Server accepts REGISTER requests. A Registrar Server accepts REGISTER requests.
A Registrar Server is typically co-located with a A Registrar Server is typically co-located with a
Proxy or Redirect Server. Proxy or Redirect Server.
Copyright (C) The Internet Society (2003). This Copyright (C) The Internet Society (2003). This version
version of this MIB module is part of RFC XXXX; see of this MIB module is part of RFC XXXX; see the RFC
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 "200306250000Z" REVISION "200307300000Z"
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 -- RFC Ed: replace xx with actual IANA assigned number and remove this note
-- this note
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 } sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 }
sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 } sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
sipCommonMIBConform OBJECT IDENTIFIER ::= { sipCommonMIB 2 } sipCommonMIBConform OBJECT IDENTIFIER ::= { sipCommonMIB 2 }
-- --
-- This MIB contains objects that are common to all SIP entities. -- This MIB contains objects that are common to all SIP entities.
-- --
-- Common basic configuration -- Common basic configuration
sipCommonCfgBase sipCommonCfgBase OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 }
OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 }
-- Protocol timer configuration -- Protocol timer configuration
sipCommonCfgTimer sipCommonCfgTimer OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 }
OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 }
-- Method retry configuration -- Method retry configuration
sipCommonCfgRetry sipCommonCfgRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 }
OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 }
-- Expires header configuration -- Expires header configuration
sipCommonCfgExpires sipCommonCfgExpires OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 }
OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 }
-- SIP message summary statistics -- SIP message summary statistics
sipCommonStatsSummary sipCommonStatsSummary OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 }
OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 }
-- Per method statistics -- Per method statistics
sipCommonStatsMethod sipCommonStatsMethod OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 }
OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 }
-- Per Status code or status code class statistics -- Per Status code or status code class statistics
sipCommonStatusCode sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 }
OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 }
-- Transaction statistics -- Transaction statistics
sipCommonStatsTrans sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 }
OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 }
-- Method retry statistics -- Method retry statistics
sipCommonStatsRetry sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 }
OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 }
-- Other statistics -- Other statistics
sipCommonStatsOther sipCommonStatsOther OBJECT IDENTIFIER ::= { sipCommonMIBObjects 10 }
OBJECT IDENTIFIER ::= { sipCommonMIBObjects 10 }
-- Accessible-for-notify objects -- Accessible-for-notify objects
sipCommonNotifObjects sipCommonNotifObjects OBJECT IDENTIFIER ::= { sipCommonMIBObjects 11 }
OBJECT IDENTIFIER ::= { sipCommonMIBObjects 11 }
-- --
-- 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 15, line 32 skipping to change at page 16, line 43
sipRequestUriHostMatching TruthValue, sipRequestUriHostMatching TruthValue,
sipServiceNotifEnable BITS, sipServiceNotifEnable BITS,
sipEntityType INTEGER sipEntityType INTEGER
} }
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 "This object will reflect the version of SIP supported by
by this SIP entity. It will follow the same format as this SIP entity. It will follow the same format as SIP
SIP version information contained in the SIP messages version information contained in the SIP messages
generated by this SIP entity. For example, entities generated by this SIP entity. For example, entities
supporting SIP version 2 will return 'SIP/2.0' as supporting SIP version 2 will return 'SIP/2.0' as dictated
dictated by the standard." by the standard."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipCommonCfgEntry 1 } ::= { sipCommonCfgEntry 1 }
sipServiceOperStatus OBJECT-TYPE sipServiceOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
up(2), up(2),
down(3), down(3),
congested(4), congested(4),
restarting(5), restarting(5),
quiescing(6), quiescing(6),
testing(7) testing(7)
} }
skipping to change at page 15, line 55 skipping to change at page 17, line 17
up(2), up(2),
down(3), down(3),
congested(4), congested(4),
restarting(5), restarting(5),
quiescing(6), quiescing(6),
testing(7) testing(7)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the current operational state of "This object contains the current operational state of the
the SIP application. SIP application.
unknown : The operational status cannot be unknown : The operational status cannot be determined
determined for some reason. for some reason.
up : The application is operating normally, and up : The application is operating normally, and
is processing (receiving and possibly is processing (receiving and possibly
issuing) SIP requests and responses. issuing) SIP requests and responses.
down : The application is currently unable to down : The application is currently unable to
process SIP messages. process SIP messages.
congested : The application is operational but no congested : The application is operational but no
additional inbound transactions can be additional inbound transactions can be
accommodated at the moment. accommodated at the moment.
restarting : The application is currently unavailable restarting : The application is currently unavailable
but it is in the process of restarting and but it is in the process of restarting and
will, presumably, soon be able to process will, presumably, soon be able to process
SIP messages. SIP messages.
quiescing : The application is currently operational quiescing : The application is currently operational
but has been administratively put into but has been administratively put into
quiesce mode. Additional inbound quiesce mode. Additional inbound transactions
transactions MAY be rejected. MAY be rejected.
testing : The application is currently in test mode testing : The application is currently in test mode
and MAY not be able to process SIP and MAY not be able to process SIP messages.
messages.
The operational status values defined for this object The operational status values defined for this object are
are not based on any specific information contained in not based on any specific information contained in the SIP
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), quiesceSessions(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 always return a value of noop(1) since sipServiceOperStatus
sipServiceOperStatus reflects the actual operational reflects the actual operational status.
status.
noop : Setting this object to a noop noop : Setting this object to a noop value
value has no effect; when read, has no effect; when read, this value
this value is always returned. is always returned.
up : Enable the application. up : Enable the application.
down : Abrupt shutdown. Immediately down : Abrupt shutdown. Immediately terminate.
terminate. reset : Restart application, reinitialize data.
reset : Restart application, reinitialize quiesceSessions : Enable quiescence mode. Stop accepting
data. any new SIP sessions. Stop processing
quiesceSessions : Enable quiescence mode. Stop new transactions except for transactions
accepting any new SIP sessions. associated with an existing session or
call.
Stop processing new transactions quiesceApplications : Enable quiescence mode. Stop processing
except for transactions new SIP transactions except for
associated with an existing transactions associated with existing
session or call. applications. The exact application
quiesceApplications : Enable quiescence mode. Stop behavior SHOULD be specified by the
processing new SIP transactions
except for transactions associated
with existing applications. The
exact application behavior SHOULD
be specified by the
implementation." implementation."
::= { sipCommonCfgEntry 3 } ::= { sipCommonCfgEntry 3 }
sipServiceStartTime OBJECT-TYPE sipServiceStartTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the SIP entity was "The value of sysUpTime at the time the SIP entity was last
last started. If started prior to the last started. If started prior to the last re-initialization of
re-initialization of the local network management the local network management subsystem, then this object
subsystem, then this object contains a zero value." contains a zero value."
::= { sipCommonCfgEntry 4 } ::= { sipCommonCfgEntry 4 }
sipServiceLastChange OBJECT-TYPE sipServiceLastChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the SIP entity "The value of sysUpTime at the time the SIP entity entered
entered its current operational state. If the current its current operational state. If the current state was
state was entered prior to the last re-initialization entered prior to the last re-initialization of the local
of the local network management subsystem, then this network management subsystem, then this object contains a
object contains a zero value." zero value."
::= { sipCommonCfgEntry 5 } ::= { sipCommonCfgEntry 5 }
sipOrganization OBJECT-TYPE sipOrganization OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the organization name which the "This object contains the organization name which the SIP
SIP entity inserts into Organization headers of SIP entity inserts into Organization headers of SIP messages
messages processed by this system. If the string is processed by this system. If the string is empty, no
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 sipMaxSessions 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 "This object indicates the maximum number of simultaneous
simultaneous sessions that the SIP entity can manage." sessions that the SIP entity can manage."
::= { sipCommonCfgEntry 7 } ::= { sipCommonCfgEntry 7 }
sipRequestUriHostMatching OBJECT-TYPE sipRequestUriHostMatching 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 host in "This object specifies whether or not the host in
RequestURI MUST match server's host name. RequestURI MUST match server's host name.
If the value of this object is 'true', then the server If the value of this object is 'true', then the server
requires a match, and if the RequestURI doesn't match requires a match, and if the RequestURI doesn't match the
the server's host name, a Location Service MAY be used server's host name, a Location Service MAY be used to
to obtain information about a callee's possible obtain information about a callee's possible location(s)
location(s) or a 404 Not Found status code is returned or a 404 Not Found status code is returned by the server.
by the server.
If the value is 'false', then no match is required." If the value is 'false', then no match is required."
REFERENCE REFERENCE
"RFC 3261, Section 8.1.1.1" "RFC 3261, Section 8.1.1.1"
::= { sipCommonCfgEntry 8 } ::= { sipCommonCfgEntry 8 }
sipServiceNotifEnable OBJECT-TYPE sipServiceNotifEnable OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
sipServiceColdStart(0), sipServiceColdStart(0),
sipServiceWarmStart(1), sipServiceWarmStart(1),
sipServiceStatusChanged(2) sipServiceStatusChanged(2)
skipping to change at page 19, line 23 skipping to change at page 21, line 4
-- --
-- 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 "This table contains the list of ports that each SIP entity
entity in this system is allowed to use. These ports in this system is allowed to use. These ports can be
can be advertised using the Contact header in a advertised using the Contact header in a REGISTER request
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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specification of a particular port. "Specification of a particular port.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
skipping to change at page 20, line 5 skipping to change at page 21, line 38
sipTransportRcv SipTransportProtocol, sipTransportRcv SipTransportProtocol,
sipTransportSnd SipTransportProtocol, sipTransportSnd SipTransportProtocol,
sipPortStatus RowStatus 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 "This object reflects a particular port that can be used by
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-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the transport protocol the SIP "This object will specify the transport protocol the SIP
entity will use to receive SIP messages. entity will use to receive SIP messages.
This object is a bit map. Each bit represents a This object is a bit map. Each bit represents a transport
transport protocol. If a bit has value 1, then that protocol. If a bit has value 1, then that transport protocol
transport protocol is currently being used. If a bit is currently being used. If a bit has value 0, then that
has value 0, then that transport protocol is currently transport protocol is currently not being used."
not being used."
::= { sipPortEntry 2 } ::= { sipPortEntry 2 }
sipTransportSnd OBJECT-TYPE sipTransportSnd OBJECT-TYPE
SYNTAX SipTransportProtocol SYNTAX SipTransportProtocol
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the transport protocol the SIP "This object will specify the transport protocol the SIP
entity will use to send SIP messages. entity will use to send SIP messages.
This object is a bit map. Each bit represents a This object is a bit map. Each bit represents a transport
transport protocol. If a bit has value 1, then that protocol. If a bit has value 1, then that transport protocol
transport protocol is currently being used. If a bit is currently being used. If a bit has value 0, then that
has value 0, then that transport protocol is currently transport protocol is currently not being used."
not being used."
::= { sipPortEntry 3 } ::= { sipPortEntry 3 }
sipPortStatus OBJECT-TYPE sipPortStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row status of the entry. This object is REQUIRED to "The row status of the entry. This object is REQUIRED to
create or delete rows by a manager. The row create or delete rows by a manager. The row
associated with port 5060 need not be created and associated with port 5060 need not be created and cannot
cannot be deleted. It is always present in the table. be deleted. It is always present in the table. It is
It is implementation specific as to whether objects in implementation specific as to whether objects in this table
this table can be set while a row is 'active'." can be set while a row is 'active'."
::= { sipPortEntry 4 } ::= { sipPortEntry 4 }
-- --
-- Support for multiple non-SIP URI schemes -- Support for multiple non-SIP URI schemes
-- --
sipUriSupportedTable OBJECT-TYPE sipUriSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUriSupportedEntry SYNTAX SEQUENCE OF SipUriSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of URI schemes supported by "This table contains a list of URI schemes supported by each
each SIP entity in this system. These are in addition SIP entity in this system. These are in addition to the SIP
to the SIP URI which MUST necessarily be supported. URI which MUST necessarily be supported. Normally the
Normally the list of URI schemes supported by an entity list of URI schemes supported by an entity is static
is static (i.e. will not change over time). (i.e. will not change over time).
A URI is a Uniform Resource Identifier (as defined in A URI is a Uniform Resource Identifier (as defined in RFC
RFC 2396). 2396).
URI schemes could, for example, contain URLs for URI schemes could, for example, contain URLs for phones, fax,
phones, fax, or irc (if they were defined) or a mailto: or irc (if they were defined) or a mailto: (RFC 2368) URL."
(RFC 2368) URL."
REFERENCE REFERENCE
"RFC 3261, Section 20.10" "RFC 3261, Section 20.10"
::= { sipCommonCfgBase 3 } ::= { sipCommonCfgBase 3 }
sipUriSupportedEntry OBJECT-TYPE sipUriSupportedEntry OBJECT-TYPE
SYNTAX SipUriSupportedEntry SYNTAX SipUriSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular non-SIP URI supported by the SIP entity. "A particular non-SIP URI supported by the SIP entity.
skipping to change at page 22, line 27 skipping to change at page 24, line 23
-- and Require headers -- and Require headers
-- --
sipFtrSupportedTable OBJECT-TYPE sipFtrSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipFtrSupportedEntry SYNTAX SEQUENCE OF SipFtrSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of the features "This table contains a list of the features
supported by each SIP entity in this system, and which supported by each SIP entity in this system, and which
MAY be REQUIRED by a peer. Definition of non-standard MAY be REQUIRED by a peer. Definition of non-standard
features is outside the scope of SIP, which only features is outside the scope of SIP, which only provides
provides mechanisms whereby support for specific mechanisms whereby support for specific features MAY be
features MAY be signalled or requested. signalled or requested.
As and example of a non-standard feature, a user agent As and example of a non-standard feature, a user agent
client MAY require that a server support the client MAY require that a server support the
'com.example.billing' feature, which it would 'com.example.billing' feature, which it would
indicate in a Require header. Such a client would have indicate in a Require header. Such a client would have
a row in its sipFtrSupportedTable containing the string a row in its sipFtrSupportedTable containing the string
'com.example.billing'. Similarly, a server which is 'com.example.billing'. Similarly, a server which is
capable of handling requests for such features would capable of handling requests for such features would list
list the string in its sipFtrSupportedTable. the string in its sipFtrSupportedTable.
If a server does not support the required feature If a server does not support the required feature
(indicated in a Require header to a UAS, or in a Proxy- (indicated in a Require header to a UAS, or in a Proxy-
Require to a Proxy Server), the server returns a 420 Require to a Proxy Server), the server returns a 420 Bad
Bad Extension listing the feature in an Unsupported Extension listing the feature in an Unsupported header.
header.
Normally the list of such features supported by an Normally the list of such features supported by an entity
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, Section 19.2"
::= { sipCommonCfgBase 4 } ::= { sipCommonCfgBase 4 }
sipFtrSupportedEntry OBJECT-TYPE sipFtrSupportedEntry OBJECT-TYPE
SYNTAX SipFtrSupportedEntry SYNTAX SipFtrSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular feature supported by the SIP "A particular feature supported by the SIP
skipping to change at page 23, line 49 skipping to change at page 25, line 50
::= { sipFtrSupportedEntry 2 } ::= { sipFtrSupportedEntry 2 }
-- --
-- Support for extension methods -- Support for extension methods
-- --
sipExtMethodSupportedTable OBJECT-TYPE sipExtMethodSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipExtMethodSupportedEntry SYNTAX SEQUENCE OF SipExtMethodSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of extension methods "This table contains a list of extension methods supported
supported by each SIP entity in this system. These are by each SIP entity in this system. These are in addition
in addition to the standard set of SIP methods to the standard set of SIP methods discussed in Section
discussed in Section 7.1 of RFC 3261. Any additional 7.1 of RFC 3261. Any additional methods that MAY be
methods that MAY be incorporated into the SIP protocol incorporated into the SIP protocol SHOULD be represented
SHOULD be represented by this table without any by this table without any requirement to update this MIB.
requirement to update this MIB. The table is informational in nature; conveying to the NMS
The table is informational in nature; conveying to the capabilities of the managed system."
NMS capabilities of the managed system."
::= { sipCommonCfgBase 5 } ::= { sipCommonCfgBase 5 }
sipExtMethodSupportedEntry OBJECT-TYPE sipExtMethodSupportedEntry OBJECT-TYPE
SYNTAX SipExtMethodSupportedEntry SYNTAX SipExtMethodSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular extension method supported by the SIP "A particular extension method supported by the SIP entity.
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, sipExtMethodSupportedIndex }
::= { sipExtMethodSupportedTable 1 } ::= { sipExtMethodSupportedTable 1 }
skipping to change at page 24, line 45 skipping to change at page 26, line 50
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row "This object uniquely identifies a conceptual row
in the table." in the table."
::= { sipExtMethodSupportedEntry 1 } ::= { sipExtMethodSupportedEntry 1 }
sipExtMethodName OBJECT-TYPE sipExtMethodName 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 "This object reflects the supported extension method's name.
name. The method name MUST be all upper case (eg, The method name MUST be all upper case (eg, 'FOO')."
'FOO')."
::= { sipExtMethodSupportedEntry 2 } ::= { sipExtMethodSupportedEntry 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 "This table contains timer configuration objects applicable
applicable to SIP user agent and SIP stateful Proxy to SIP user agent and SIP stateful Proxy Server entities."
Server entities."
::= { sipCommonCfgTimer 1 } ::= { sipCommonCfgTimer 1 }
sipCommonCfgTimerEntry OBJECT-TYPE sipCommonCfgTimerEntry OBJECT-TYPE
SYNTAX SipCommonCfgTimerEntry SYNTAX SipCommonCfgTimerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of timer configuration. "A row of timer configuration.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
skipping to change at page 25, line 51 skipping to change at page 28, line 12
sipCfgTimerT2 Unsigned32, sipCfgTimerT2 Unsigned32,
sipCfgTimerT4 Unsigned32 sipCfgTimerT4 Unsigned32
} }
sipCfgTimerA OBJECT-TYPE sipCfgTimerA OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the "This object specifies the initial value for the retransmit
retransmit timer for the INVITE method. The retransmit timer for the INVITE method. The retransmit timer doubles
timer doubles after each retransmission, ensuring an after each retransmission, ensuring an exponential backoff
exponential backoff in network traffic. This object in network traffic. This object represents the initial time
represents the initial time a SIP entity will wait to a SIP entity will wait to receive a provisional response to
receive a provisional response to an INVITE before an INVITE before resending the INVITE request."
resending the INVITE request."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.1.2" "RFC 3261, Section 17.1.1.2"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 1 } ::= { sipCommonCfgTimerEntry 1 }
sipCfgTimerB OBJECT-TYPE sipCfgTimerB OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 26, line 30 skipping to change at page 28, line 44
"RFC 3261, Section 17.1.1.2" "RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 2 } ::= { sipCommonCfgTimerEntry 2 }
sipCfgTimerC OBJECT-TYPE sipCfgTimerC OBJECT-TYPE
SYNTAX Unsigned32 (180000..300000) SYNTAX Unsigned32 (180000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum time a SIP Proxy "This object specifies the maximum time a SIP Proxy Server
Server will wait to receive a provisional response to will wait to receive a provisional response to an INVITE.
an INVITE. The Timer C MUST be set for each client The Timer C MUST be set for each client transaction when
transaction when an INVITE request is proxied." an INVITE request is proxied."
REFERENCE REFERENCE
"RFC 3261, Section 16.6" "RFC 3261, Section 16.6"
DEFVAL { 180000 } DEFVAL { 180000 }
::= { sipCommonCfgTimerEntry 3 } ::= { sipCommonCfgTimerEntry 3 }
sipCfgTimerD OBJECT-TYPE sipCfgTimerD OBJECT-TYPE
SYNTAX Unsigned32 (0..300000) SYNTAX Unsigned32 (0..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the amount of time that the "This object specifies the amount of time that the server
server transaction can remain in the 'Completed' state transaction can remain in the 'Completed' state when
when unreliable transports are used. The default value unreliable transports are used. The default value MUST be
MUST be greater than 32000 for UDP transport and its greater than 32000 for UDP transport and its value MUST
value MUST be 0 for TCP/SCTP transport." be 0 for TCP/SCTP transport."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.1.2" "RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 4 } ::= { sipCommonCfgTimerEntry 4 }
sipCfgTimerE OBJECT-TYPE sipCfgTimerE OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the "This object specifies the initial value for the retransmit
retransmit timer for a non-INVITE method while in timer for a non-INVITE method while in 'Trying State'.
'Trying State'. The retransmit timer doubles after each The retransmit timer doubles after each retransmission
retransmission until it reaches T2 to ensure an until it reaches T2 to ensure an exponential backoff
exponential backoff in network traffic. This object in network traffic. This object represents the initial time
represents the initial time a SIP entity will wait to a SIP entity will wait to receive a provisional response to
receive a provisional response to the request before the request before resending the non-INVITE request."
resending the non-INVITE request."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.2.2" "RFC 3261, Section 17.1.2.2"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 5 } ::= { sipCommonCfgTimerEntry 5 }
sipCfgTimerF OBJECT-TYPE sipCfgTimerF OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum time a SIP entity will "This object specifies the maximum time a SIP entity will
wait to receive a final response to a non-INVITE wait to receive a final response to a non-INVITE request.
request. The timer is started upon transmission of the The timer is started upon transmission of the
initial request." initial request."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.2.2" "RFC 3261, Section 17.1.2.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 6 } ::= { sipCommonCfgTimerEntry 6 }
sipCfgTimerG OBJECT-TYPE sipCfgTimerG OBJECT-TYPE
SYNTAX Unsigned32 (0..1000) SYNTAX Unsigned32 (0..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the "This object specifies the initial value for the retransmit
retransmit timer for final responses to INVITE timer for final responses to INVITE requests.
requests. If timer G fires, the response is passed to the transport
If timer G fires, the response is passed to the layer once more for retransmission, and timer G is set
transport layer once more for retransmission, and timer to fire in MIN(2*T1, T2) seconds. From then on, when
G is set to fire in MIN(2*T1, T2) seconds. From then timer G fires, the response is passed to the transport
on, when timer G fires, the response is passed to the again for transmission, and timer G is reset with a value
transport again for transmission, and timer G is reset that doubles, unless that value exceeds T2, in which case
with a value that doubles, unless that value exceeds it is reset with the value of T2.
T2, in which case it is reset with the value of T2. The default value MUST be T1 for UDP transport and its value
The default value MUST be T1 for UDP transport and its MUST be 0 for reliable transport like TCP/SCTP."
Value MUST be 0 for reliable transport like TCP/SCTP."
REFERENCE REFERENCE
"RFC 3261, Section 17.2.1" "RFC 3261, Section 17.2.1"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 7 } ::= { sipCommonCfgTimerEntry 7 }
sipCfgTimerH OBJECT-TYPE sipCfgTimerH OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum time a server will "This object specifies the maximum time a server will wait
wait to receive an ACK before it abandons to receive an ACK before it abandons retransmitting the
retransmitting the response. The timer is started upon response. The timer is started upon entering the
entering the 'Completed' state." 'Completed' state."
REFERENCE REFERENCE
"RFC 3261, Section 17.2.1" "RFC 3261, Section 17.2.1"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 8 } ::= { sipCommonCfgTimerEntry 8 }
sipCfgTimerI OBJECT-TYPE sipCfgTimerI OBJECT-TYPE
SYNTAX Unsigned32 (0..10000) SYNTAX Unsigned32 (0..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum time a SIP entity "This object specifies the maximum time a SIP entity will
will wait to receive additional ACK message wait to receive additional ACK message retransmissions.
retransmissions. The timer is started upon entering the The timer is started upon entering the 'Confirmed' state.
'Confirmed' state. The default value MUST be T4 for UDP The default value MUST be T4 for UDP transport and its value
transport and its value MUST be 0 for reliable MUST be 0 for reliable transport like TCP/SCTP."
transport like TCP/SCTP."
REFERENCE REFERENCE
"RFC 3261, Section 17.2.1" "RFC 3261, Section 17.2.1"
DEFVAL { 5000 } DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 9 } ::= { sipCommonCfgTimerEntry 9 }
sipCfgTimerJ OBJECT-TYPE sipCfgTimerJ OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum time a SIP server "This object specifies the maximum time a SIP server will
will wait to receive retransmissions of non-INVITE wait to receive retransmissions of non-INVITE request.
request. The timer is started upon entering the The timer is started upon entering the 'Completed' state
'Completed' state for non-INVITE transactions. When for non-INVITE transactions. When timer J fires, the server
timer J fires, the server MUST transition to the MUST transition to the 'Terminated' state."
'Terminated' state."
REFERENCE "RFC 3261, Section 17.2.2" REFERENCE "RFC 3261, Section 17.2.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 10 } ::= { sipCommonCfgTimerEntry 10 }
sipCfgTimerK OBJECT-TYPE sipCfgTimerK OBJECT-TYPE
SYNTAX Unsigned32 (0..10000) SYNTAX Unsigned32 (0..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum time a SIP client "This object specifies the maximum time a SIP client will
will wait to receive retransmissions of responses to wait to receive retransmissions of responses to non-INVITE
non-INVITE requests. The timer is started upon entering requests.
the 'Completed' state for non-INVITE transactions. When The timer is started upon entering the 'Completed' state
timer K fires, the server MUST transition to the for non-INVITE transactions. When timer K fires, the server
'Terminated' state. The default value MUST be T4 for MUST transition to the 'Terminated' state.
UDP transport and its value MUST be 0 for reliable The default value MUST be T4 for UDP transport and its value
transport like TCP/SCTP." MUST be 0 for reliable transport like TCP/SCTP."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.2.2" "RFC 3261, Section 17.1.2.2"
DEFVAL { 5000 } DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 11 } ::= { sipCommonCfgTimerEntry 11 }
sipCfgTimerT1 OBJECT-TYPE sipCfgTimerT1 OBJECT-TYPE
SYNTAX Unsigned32 (200..10000) SYNTAX Unsigned32 (200..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 31, line 13 skipping to change at page 34, line 4
"This object specifies the time a SIP entity will wait "This object specifies the time a SIP entity will wait
for a response to the extension method request before for a response to the extension method request before
retransmitting. The retransmit timer doubles after retransmitting. The retransmit timer doubles after
each retransmission, ensuring an exponential backoff each retransmission, ensuring an exponential backoff
in network traffic." in network traffic."
::= { sipCommonCfgTimerExtMethodEntry 1 } ::= { sipCommonCfgTimerExtMethodEntry 1 }
-- --
-- SIP Retry Configuration -- SIP Retry Configuration
-- --
sipCommonCfgRetryTable OBJECT-TYPE sipCommonCfgRetryTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgRetryEntry SYNTAX SEQUENCE OF SipCommonCfgRetryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains retry configuration objects "This table contains retry configuration objects applicable
applicable to SIP user agent and SIP proxies." to SIP user agent and SIP proxies."
::= { sipCommonCfgRetry 1 } ::= { sipCommonCfgRetry 1 }
sipCommonCfgRetryEntry OBJECT-TYPE sipCommonCfgRetryEntry OBJECT-TYPE
SYNTAX SipCommonCfgRetryEntry SYNTAX SipCommonCfgRetryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of retry configuration. "A row of retry configuration.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
skipping to change at page 31, line 56 skipping to change at page 34, line 46
sipCfgRetryOptions Unsigned32, sipCfgRetryOptions Unsigned32,
sipCfgRetryFinalResponse Unsigned32, sipCfgRetryFinalResponse Unsigned32,
sipCfgRetryNonFinalResponse Unsigned32 sipCfgRetryNonFinalResponse Unsigned32
} }
sipCfgRetryInvite OBJECT-TYPE sipCfgRetryInvite OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a SIP "This object will specify the number of times a SIP entity
entity will retry sending an INVITE request." will retry sending an INVITE request."
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 1 } ::= { sipCommonCfgRetryEntry 1 }
sipCfgRetryBye OBJECT-TYPE sipCfgRetryBye OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a SIP "This object will specify the number of times a SIP entity
entity will retry sending a BYE request." will retry sending a BYE request."
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 2 } ::= { sipCommonCfgRetryEntry 2 }
sipCfgRetryCancel OBJECT-TYPE sipCfgRetryCancel OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a SIP "This object will specify the number of times a SIP entity
entity will retry sending a CANCEL request." will retry sending a CANCEL request."
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 3 } ::= { sipCommonCfgRetryEntry 3 }
sipCfgRetryRegister OBJECT-TYPE sipCfgRetryRegister OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a SIP "This object will specify the number of times a SIP entity
entity will retry sending a REGISTER request." will retry sending a REGISTER request."
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 4 } ::= { sipCommonCfgRetryEntry 4 }
sipCfgRetryOptions OBJECT-TYPE sipCfgRetryOptions OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a SIP "This object will specify the number of times a SIP entity
entity will retry sending an OPTIONS request." will retry sending an OPTIONS request."
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 5 } ::= { sipCommonCfgRetryEntry 5 }
sipCfgRetryFinalResponse OBJECT-TYPE sipCfgRetryFinalResponse OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a SIP "This object will specify the number of times a SIP entity
entity will retry sending a final response and will retry sending a final response and expecting an ACK."
expecting an ACK."
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 6 } ::= { sipCommonCfgRetryEntry 6 }
sipCfgRetryNonFinalResponse OBJECT-TYPE sipCfgRetryNonFinalResponse OBJECT-TYPE
SYNTAX Unsigned32 (1..10) SYNTAX Unsigned32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the number of times a SIP "This object will specify the number of times a SIP entity
entity will retry sending a non-final response." will retry sending a non-final response."
DEFVAL { 6 } DEFVAL { 6 }
::= { sipCommonCfgRetryEntry 7 } ::= { sipCommonCfgRetryEntry 7 }
-- --
-- Retry Extensions: support for extension methods -- Retry Extensions: support for extension methods
-- --
sipCommonCfgRetryExtMethodTable OBJECT-TYPE sipCommonCfgRetryExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgRetryExtMethodEntry SYNTAX SEQUENCE OF SipCommonCfgRetryExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 35, line 4 skipping to change at page 38, line 14
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For user agent clients, this value is inserted into the "For user agent clients, this value is inserted into the
Expires header. Expires header.
For Proxy Servers, if a received request contained an For Proxy Servers, if a received request contained an
Expires header, then the value in the header takes Expires header, then the value in the header takes
precedence." precedence."
::= { sipCommonCfgExpiresMethodEntry 1 } ::= { sipCommonCfgExpiresMethodEntry 1 }
sipCfgExpiresRegister OBJECT-TYPE sipCfgExpiresRegister 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
"For user agent clients, this value is inserted into the "For user agent clients, this value is inserted into the
Expires header. Expires header.
For Registrar Servers, if a received request contained For Registrar Servers, if a received request contained an
an Expires header, then the value in the header takes Expires header, then the value in the header takes
precedence." precedence."
::= { sipCommonCfgExpiresMethodEntry 2 } ::= { sipCommonCfgExpiresMethodEntry 2 }
sipCfgExpiresHeaderMethod OBJECT-TYPE sipCfgExpiresHeaderMethod OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
invite(0), invite(0),
register(1) register(1)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 36, line 28 skipping to change at page 39, line 44
sipCfgExpiresHeaderValue Unsigned32, sipCfgExpiresHeaderValue Unsigned32,
sipCfgExpiresStatusCodeStatus RowStatus sipCfgExpiresStatusCodeStatus RowStatus
} }
sipCfgExpiresStatusCodeValue OBJECT-TYPE sipCfgExpiresStatusCodeValue OBJECT-TYPE
SYNTAX Unsigned32 (100..999) SYNTAX Unsigned32 (100..999)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a SIP status code value for which "This object contains a SIP status code value for which
the Expires header value is configured. All of the the Expires header value is configured. All of the other
other information in the row is related to this value." information in the row is related to this value."
::= { sipCommonCfgExpiresStatusCodeEntry 1 } ::= { sipCommonCfgExpiresStatusCodeEntry 1 }
sipCfgExpiresHeaderValue OBJECT-TYPE sipCfgExpiresHeaderValue OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value is inserted into the Expires header for the "This value is inserted into the Expires header for the
specific status code." specific status code."
::= { sipCommonCfgExpiresStatusCodeEntry 2 } ::= { sipCommonCfgExpiresStatusCodeEntry 2 }
sipCfgExpiresStatusCodeStatus OBJECT-TYPE sipCfgExpiresStatusCodeStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is REQUIRED to create or delete rows "This object is REQUIRED to create or delete rows
by a manager. by a manager.
A value for sipCfgExpiresHeaderValue MUST be specified A value for sipCfgExpiresHeaderValue MUST be specified when
when creating rows by setting this row status to creating rows by setting this row status to 'createAndGo'.
'createAndGo'. The row will automatically transition The row will automatically transition to 'active'.
to 'active'.
The configuration specified by an entry will be made The configuration specified by an entry will be made
active when this object is set to 'active'." active when this object is set to 'active'."
::= { sipCommonCfgExpiresStatusCodeEntry 3 } ::= { 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
skipping to change at page 38, line 11 skipping to change at page 41, line 41
::= { sipSummaryStatsEntry 1 } ::= { sipSummaryStatsEntry 1 }
sipSummaryOutRequests OBJECT-TYPE sipSummaryOutRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the total number of SIP request "This object contains the total number of SIP request
messages sent out (originated and relayed) by the SIP messages sent out (originated and relayed) by the SIP
entity. Where a particular message is sent more than entity. Where a particular message is sent more than
once, for example as a retransmission, or as a result once, for example as a retransmission, or as a result of
of forking, each transmission is counted separately." forking, each transmission is counted separately."
::= { sipSummaryStatsEntry 2 } ::= { sipSummaryStatsEntry 2 }
sipSummaryInResponses OBJECT-TYPE sipSummaryInResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the total number of SIP response "This object contains the total number of SIP response
messages received by the SIP entity including messages received by the SIP entity including
retransmissions." retransmissions."
skipping to change at page 38, line 30 skipping to change at page 42, line 12
"This object contains the total number of SIP response "This object contains the total number of SIP response
messages received by the SIP entity including messages received by the SIP entity including
retransmissions." retransmissions."
::= { sipSummaryStatsEntry 3 } ::= { sipSummaryStatsEntry 3 }
sipSummaryOutResponses OBJECT-TYPE sipSummaryOutResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the total number of SIP response "This object contains the total number of SIP response
messages sent (originated and relayed) by the SIP messages sent (originated and relayed) by the SIP entity
entity including retransmissions." including retransmissions."
::= { sipSummaryStatsEntry 4 } ::= { sipSummaryStatsEntry 4 }
sipSummaryTotalTransactions OBJECT-TYPE sipSummaryTotalTransactions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of "This object contains a count of the number of transactions
transactions that are in progress and transactions that that are in progress and transactions that have reached the
have reached the terminated state. It is not terminated state. It is not applicable to stateless
applicable to stateless SIP Proxy Servers. SIP Proxy Servers.
A SIP transaction occurs between a client and a server A SIP transaction occurs between a client and a server and
and comprises all messages from the first request sent comprises all messages from the first request sent from
from the client to the server up to a final (non-1xx) the client to the server up to a final (non-1xx) response
response sent from the server to the client. sent from the server to the client.
If the request is INVITE and the final response is a If the request is INVITE and the final response is a non-2xx,
non-2xx, the transaction also include an ACK to the the transaction also include an ACK to the response. The ACK
response. The ACK for a 2xx response to an INVITE for a 2xx response to an INVITE request is a separate
request is a separate 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 In the case of a forked request, all branches count as a
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.
-- --
sipMethodStatsTable OBJECT-TYPE sipMethodStatsTable OBJECT-TYPE
skipping to change at page 40, line 7 skipping to change at page 44, line 4
sipStatsAckOuts Counter32, sipStatsAckOuts Counter32,
sipStatsByeIns Counter32, sipStatsByeIns Counter32,
sipStatsByeOuts Counter32, sipStatsByeOuts Counter32,
sipStatsCancelIns Counter32, sipStatsCancelIns Counter32,
sipStatsCancelOuts Counter32, sipStatsCancelOuts Counter32,
sipStatsOptionsIns Counter32, sipStatsOptionsIns Counter32,
sipStatsOptionsOuts Counter32, sipStatsOptionsOuts Counter32,
sipStatsRegisterIns Counter32, sipStatsRegisterIns Counter32,
sipStatsRegisterOuts Counter32 sipStatsRegisterOuts Counter32
} }
sipStatsInviteIns OBJECT-TYPE sipStatsInviteIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE "This object reflects the total number of INVITE requests
requests received by the SIP entity including received by the SIP entity including retransmissions."
retransmissions."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 1 } ::= { sipMethodStatsEntry 1 }
sipStatsInviteOuts OBJECT-TYPE sipStatsInviteOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE "This object reflects the total number of INVITE requests
requests sent by the SIP entity including sent by the SIP entity including retransmissions."
retransmissions."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 2 } ::= { sipMethodStatsEntry 2 }
sipStatsAckIns OBJECT-TYPE sipStatsAckIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of ACK requests "This object reflects the total number of ACK requests
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 sipStatsAckOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of ACK requests "This object reflects the total number of ACK requests sent
sent by the SIP entity." by the SIP entity."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 4 } ::= { sipMethodStatsEntry 4 }
sipStatsByeIns OBJECT-TYPE sipStatsByeIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of BYE requests "This object reflects the total number of BYE requests
received by the SIP entity including retransmissions." received by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 5 } ::= { sipMethodStatsEntry 5 }
sipStatsByeOuts OBJECT-TYPE sipStatsByeOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of BYE requests "This object reflects the total number of BYE requests sent
sent by the SIP entity including retransmissions." by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 6 } ::= { sipMethodStatsEntry 6 }
sipStatsCancelIns OBJECT-TYPE sipStatsCancelIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of CANCEL "This object reflects the total number of CANCEL requests
requests received by the SIP entity including received by the SIP entity including retransmissions."
retransmissions."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 7 } ::= { sipMethodStatsEntry 7 }
sipStatsCancelOuts OBJECT-TYPE sipStatsCancelOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of CANCEL "This object reflects the total number of CANCEL requests
requests sent by the SIP entity including sent by the SIP entity including retransmissions."
retransmissions."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 8 } ::= { sipMethodStatsEntry 8 }
sipStatsOptionsIns OBJECT-TYPE sipStatsOptionsIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of OPTIONS "This object reflects the total number of OPTIONS requests
requests received by the SIP entity including received by the SIP entity including retransmissions."
retransmissions."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 9 } ::= { sipMethodStatsEntry 9 }
sipStatsOptionsOuts OBJECT-TYPE sipStatsOptionsOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of OPTIONS "This object reflects the total number of OPTIONS requests
requests sent by the SIP entity including sent by the SIP entity including retransmissions."
retransmissions."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 10 } ::= { sipMethodStatsEntry 10 }
sipStatsRegisterIns OBJECT-TYPE sipStatsRegisterIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of REGISTER "This object reflects the total number of REGISTER requests
requests received by the SIP entity including received by the SIP entity including retransmissions."
retransmissions."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 11 } ::= { sipMethodStatsEntry 11 }
sipStatsRegisterOuts OBJECT-TYPE sipStatsRegisterOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of REGISTER "This object reflects the total number of REGISTER requests
requests sent by the SIP entity including sent by the SIP entity including retransmissions."
retransmissions."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 12 } ::= { sipMethodStatsEntry 12 }
-- --
-- Support for extension methods -- support for extension methods
-- --
sipStatsExtMethodTable OBJECT-TYPE sipStatsExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatsExtMethodEntry SYNTAX SEQUENCE OF SipStatsExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the list of extension methods which "This table contains the list of extension methods which
each SIP entity in this system has been requested to each SIP entity in this system has been requested to
monitor." monitor."
::= { sipCommonStatsMethod 2 } ::= { sipCommonStatsMethod 2 }
sipStatsExtMethodEntry OBJECT-TYPE sipStatsExtMethodEntry OBJECT-TYPE
SYNTAX SipStatsExtMethodEntry SYNTAX SipStatsExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information on a particular extension "This row contains information on a particular extension
method that the SIP entity has been requested to method that the SIP entity has been requested to monitor.
monitor.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and uniquely identify these instances of SIP entities and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788)."
AUGMENTS { sipExtMethodSupportedEntry } AUGMENTS { sipExtMethodSupportedEntry }
::= { sipStatsExtMethodTable 1 } ::= { sipStatsExtMethodTable 1 }
SipStatsExtMethodEntry ::= SipStatsExtMethodEntry ::=
SEQUENCE { SEQUENCE {
sipStatsExtMethodIns Counter32, sipStatsExtMethodIns Counter32,
sipStatsExtMethodOuts Counter32 sipStatsExtMethodOuts Counter32
} }
sipStatsExtMethodIns OBJECT-TYPE sipStatsExtMethodIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of requests "This object reflects the total number of requests received
received by the SIP entity which requested the method by the SIP entity which requested the method contained in
contained in the sipStatsExtMethodName column including the sipStatsExtMethodName column including retransmissions
retransmissions if appropriate for the method." if appropriate for the method."
::= { sipStatsExtMethodEntry 1 } ::= { sipStatsExtMethodEntry 1 }
sipStatsExtMethodOuts OBJECT-TYPE sipStatsExtMethodOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of requests sent "This object reflects the total number of requests sent
by the SIP entity which requested the method contained by the SIP entity which requested the method contained in
in the sipStatsExtMethodName column including the sipStatsExtMethodName column including retransmissions
retransmissions if appropriate for the method." if appropriate for the method."
::= { sipStatsExtMethodEntry 2 } ::= { sipStatsExtMethodEntry 2 }
-- --
-- SIP Response Status Codes -- SIP Response Status Codes
-- --
sipStatusCodeClassesTable OBJECT-TYPE sipStatusCodeClassesTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatusCodeClassesEntry SYNTAX SEQUENCE OF SipStatusCodeClassesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains statistics on response status code "This table contains statistics on response status code
classes for each SIP entity in this system." classes for each SIP entity in this system."
skipping to change at page 48, line 30 skipping to change at page 53, line 18
each SIP entity in this system has been requested to each SIP entity in this system has been requested to
monitor. It is the mechanism by which specific status monitor. It is the mechanism by which specific status
codes are monitored." codes are monitored."
::= { sipCommonStatusCode 2 } ::= { sipCommonStatusCode 2 }
sipStatusCodesEntry OBJECT-TYPE sipStatusCodesEntry OBJECT-TYPE
SYNTAX SipStatusCodesEntry SYNTAX SipStatusCodesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information on a particular SIP "This row contains information on a particular SIP status
status code that the SIP entity has been requested to code that the SIP entity has been requested to monitor.
monitor.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and uniquely identify these instances of SIP entities and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipStatusCodeValue } INDEX { applIndex, sipStatusCodeValue }
::= { sipStatusCodesTable 1 } ::= { sipStatusCodesTable 1 }
SipStatusCodesEntry ::= SipStatusCodesEntry ::=
SEQUENCE { SEQUENCE {
sipStatusCodeValue INTEGER, sipStatusCodeValue Unsigned32,
sipStatusCodeIns Counter32, sipStatusCodeIns Counter32,
sipStatusCodeOuts Counter32, sipStatusCodeOuts Counter32,
sipStatusCodeRowStatus RowStatus sipStatusCodeRowStatus RowStatus
} }
sipStatusCodeValue OBJECT-TYPE sipStatusCodeValue OBJECT-TYPE
SYNTAX INTEGER (100..999) SYNTAX Unsigned32 (100..999)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a SIP status code value that the "This object contains a SIP status code value that the SIP
SIP entity has been requested to monitor. All of the entity has been requested to monitor. All of the other
other information in the row is related to this value." information in the row is related to this value."
::= { sipStatusCodesEntry 1 } ::= { sipStatusCodesEntry 1 }
sipStatusCodeIns OBJECT-TYPE sipStatusCodeIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of response "This object reflects the total number of response messages
messages received by the SIP entity with the status received by the SIP entity with the status code value
code value contained in the sipStatusCodeValue column." contained in the sipStatusCodeValue column."
::= { sipStatusCodesEntry 2 } ::= { sipStatusCodesEntry 2 }
sipStatusCodeOuts OBJECT-TYPE sipStatusCodeOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of response "This object reflects the total number of response messages
messages sent by the SIP entity with the status code sent by the SIP entity with the status code value
value contained in the sipStatusCodeValue column." contained in the sipStatusCodeValue column."
::= { sipStatusCodesEntry 3 } ::= { sipStatusCodesEntry 3 }
sipStatusCodeRowStatus OBJECT-TYPE sipStatusCodeRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row augmentation in sipStatusCodeNotifTable "The row augmentation in sipStatusCodeNotifTable
will be governed by the value of this RowStatus. will be governed by the value of this RowStatus.
skipping to change at page 50, line 22 skipping to change at page 55, line 18
status code notification control objects seperate from status code notification control objects seperate from
the actual status code statistics." the actual status code statistics."
::= { sipCommonStatusCode 3 } ::= { sipCommonStatusCode 3 }
sipStatusCodeNotifEntry OBJECT-TYPE sipStatusCodeNotifEntry OBJECT-TYPE
SYNTAX SipStatusCodeNotifEntry SYNTAX SipStatusCodeNotifEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information controlling notifications "This row contains information controlling notifications
for a particular SIP status code that the SIP entity for a particular SIP status code that the SIP entity has
has been requested to monitor." been requested to monitor."
AUGMENTS { sipStatusCodesEntry } AUGMENTS { sipStatusCodesEntry }
::= { sipStatusCodeNotifTable 1 } ::= { sipStatusCodeNotifTable 1 }
SipStatusCodeNotifEntry ::= SipStatusCodeNotifEntry ::=
SEQUENCE { SEQUENCE {
sipStatusCodeNotifSend TruthValue, sipStatusCodeNotifSend TruthValue,
sipStatusCodeNotifEmitMode INTEGER, sipStatusCodeNotifEmitMode INTEGER,
sipStatusCodeNotifThresh Unsigned32, sipStatusCodeNotifThresh Unsigned32,
sipStatusCodeNotifInterval Unsigned32 sipStatusCodeNotifInterval Unsigned32
} }
sipStatusCodeNotifSend OBJECT-TYPE sipStatusCodeNotifSend OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls whether a sipStatusCodeNotif "This object controls whether a sipStatusCodeNotif
is emitted when the status code value specified in is emitted when the status code value specified in
by sipStatusCodeValue is sent or received. by sipStatusCodeValue is sent or received.
If the value of this object is 'true', then a If the value of this object is 'true', then a notification
notification is sent. If it is 'false', no is sent. If it is 'false', no notification is sent.
notification is sent.
Note well, that a notification MAY be emitted for Note well, that a notification MAY be emitted for
every message sent or received that contains the every message sent or received that contains the particular
particular status code. Depending on the status code status code. Depending on the status code involved,
involved, this can cause a significant number of this can cause a significant number of notification
notification emissions that could be detrimental to emissions that could be detrimental to network performance.
network performance.
Managers are forewarned to be prudent in the use of Managers are forewarned to be prudent in the use of
this object to enable notifications. Look to this object to enable notifications. Look to
sipStatusCodeNotifEmitMode for alternative sipStatusCodeNotifEmitMode for alternative
controls for sipStatusCodeNotif emissions." controls for sipStatusCodeNotif emissions."
DEFVAL { false } DEFVAL { false }
::= { sipStatusCodeNotifEntry 1 } ::= { sipStatusCodeNotifEntry 1 }
sipStatusCodeNotifEmitMode OBJECT-TYPE sipStatusCodeNotifEmitMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
normal(1), normal(1),
oneShot(2), oneShot(2),
skipping to change at page 51, line 36 skipping to change at page 56, line 36
normal : sipStatusCodeNotif notifications will normal : sipStatusCodeNotif notifications will
be emitted by the system for each be emitted by the system for each
SIP response messages sent or received SIP response messages sent or received
that contains the desired status code. that contains the desired status code.
oneShot : Only one sipStatusCodeNotif notification oneShot : Only one sipStatusCodeNotif notification
will be emitted. It will be the next will be emitted. It will be the next
SIP response messages sent or received SIP response messages sent or received
that contains the desired status code. that contains the desired status code.
No more notifications are emitted until No more notifications are emitted until this
this object is set to either 'oneShot' object is set to either 'oneShot' again
again or 'normal'. This option is provided or 'normal'. This option is provided
as a means of quelling the potential as a means of quelling the potential
promiscuous behavior that can be associated promiscuous behavior that can be associated
with the sipStatusCodeNotif. with the sipStatusCodeNotif.
triggered : This value is only readable and cannot be triggered : This value is only readable and cannot be
set. It reflects the default value of the set. It reflects the default value of the
object or that the 'oneShot' case has object or that the 'oneShot' case has
occurred and indicates the mode needs to occurred and indicates the mode needs to
be reset to get further notifications. be reset to get further notifications.
The mode is reset by setting this object The mode is reset by setting this object
skipping to change at page 53, line 26 skipping to change at page 58, line 37
SipCurrentTransEntry ::= SipCurrentTransEntry ::=
SEQUENCE { SEQUENCE {
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 "This object contains the number of transactions awaiting
awaiting definitive (non-1xx) response. In the case of definitive (non-1xx) response. In the case of a forked
a forked request, all branches count as a single request, all branches count as a single transaction
transaction corresponding to the entity identified by corresponding to the entity identified by applIndex."
applIndex."
::= { sipCurrentTransEntry 1 } ::= { sipCurrentTransEntry 1 }
-- --
-- SIP Retry Statistics -- SIP Retry Statistics
-- --
-- The counter objects in this group correspond directly to the -- The counter objects in this group correspond directly to the
-- retry timers supported in sipCommonCfgRetry group. applIndex -- retry timers supported in sipCommonCfgRetry group. applIndex can
-- can be used to correlate the two groups. -- 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 54, line 28 skipping to change at page 59, line 44
sipStatsRetryFinalResponses Counter32, sipStatsRetryFinalResponses Counter32,
sipStatsRetryNonFinalResponses Counter32 sipStatsRetryNonFinalResponses Counter32
} }
sipStatsRetryInvites OBJECT-TYPE sipStatsRetryInvites OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE retries "This object reflects the total number of INVITE retries
that have been sent by the SIP entity. If the number that have been sent by the SIP entity. If the number of
of 'first attempt' INVITES is of interest, subtract the 'first attempt' INVITES is of interest, subtract the value
value of this object from sipStatsInviteOuts." of this object from sipStatsInviteOuts."
::= { sipCommonStatsRetryEntry 1 } ::= { sipCommonStatsRetryEntry 1 }
sipStatsRetryByes OBJECT-TYPE sipStatsRetryByes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of BYE retries "This object reflects the total number of BYE retries that
that have been sent by the SIP entity. If the number of have been sent by the SIP entity. If the number of
'first attempt' BYEs is of interest, subtract the value 'first attempt' BYEs is of interest, subtract the value
of this object from sipStatsByeOuts." of this object from sipStatsByeOuts."
::= { sipCommonStatsRetryEntry 2 } ::= { sipCommonStatsRetryEntry 2 }
sipStatsRetryCancels OBJECT-TYPE sipStatsRetryCancels OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of CANCEL retries "This object reflects the total number of CANCEL retries
that have been sent by the SIP entity. If the number of that have been sent by the SIP entity. If the number of
'first attempt' CANCELs is of interest, subtract the 'first attempt' CANCELs is of interest, subtract the value
value of this object from sipStatsCancelOuts." of this object from sipStatsCancelOuts."
::= { sipCommonStatsRetryEntry 3 } ::= { sipCommonStatsRetryEntry 3 }
sipStatsRetryRegisters OBJECT-TYPE sipStatsRetryRegisters OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of REGISTER "This object reflects the total number of REGISTER retries
retries that have been sent by the SIP entity. If the that have been sent by the SIP entity. If the number of
number of 'first attempt' REGISTERSs is of interest, 'first attempt' REGISTERSs is of interest, subtract the value
subtract the value of this object from of this object from sipStatsRegisterOuts."
sipStatsRegisterOuts."
::= { sipCommonStatsRetryEntry 4 } ::= { sipCommonStatsRetryEntry 4 }
sipStatsRetryOptions OBJECT-TYPE sipStatsRetryOptions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of OPTIONS "This object reflects the total number of OPTIONS retries
retries that have been sent by the SIP entity. If the that have been sent by the SIP entity. If the number of
number of 'first attempt' OPTIONS is of interest, 'first attempt' OPTIONS is of interest, subtract the value
subtract the value of this object from of this object from sipStatsOptionsOuts."
sipStatsOptionsOuts."
::= { sipCommonStatsRetryEntry 5 } ::= { 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 6 }
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 "This object reflects the total number of non-Final Response
Response retries that have been sent by the SIP retries that have been sent by the SIP entity."
entity."
::= { sipCommonStatsRetryEntry 7 } ::= { sipCommonStatsRetryEntry 7 }
-- --
-- Retry Extensions Stats: support for extension methods -- Retry Extensions Stats: support for extension methods
-- --
sipCommonStatsRetryExtMethodTable OBJECT-TYPE sipCommonStatsRetryExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonStatsRetryExtMethodEntry SYNTAX SEQUENCE OF SipCommonStatsRetryExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 56, line 42 skipping to change at page 62, line 20
::= { sipCommonStatsRetryExtMethodEntry 1 } ::= { 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 "This table contains other common statistics supported by
by each SIP entity in this system." each SIP entity in this system."
::= { sipCommonStatsOther 1 } ::= { sipCommonStatsOther 1 }
sipOtherStatsEntry OBJECT-TYPE sipOtherStatsEntry OBJECT-TYPE
SYNTAX SipOtherStatsEntry SYNTAX SipOtherStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular SIP entity's other common "Information on a particular SIP entity's other common
statistics. 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 }
skipping to change at page 57, line 21 skipping to change at page 63, line 6
SEQUENCE { SEQUENCE {
sipNumUnsupportedUris Counter32 sipNumUnsupportedUris Counter32
} }
sipNumUnsupportedUris OBJECT-TYPE sipNumUnsupportedUris OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of RequestURIs received with unsupported scheme. "Number of RequestURIs received with unsupported scheme.
A server normally responds to such requests with a 400 A server normally responds to such requests with a 400 Bad
Bad Request status code." Request status code."
::= { sipOtherStatsEntry 1 } ::= { sipOtherStatsEntry 1 }
-- --
-- Notification related objects -- Notification related objects
-- --
-- --
-- Status code related notification objects. -- Status code related notification objects.
-- --
sipStatusCodeNotifTo OBJECT-TYPE sipStatusCodeNotifTo OBJECT-TYPE
skipping to change at page 57, line 49 skipping to change at page 63, line 34
notification. The header name will be part of notification. The header name will be part of
this object value. this object value.
For example, 'To: Watson ." For example, 'To: Watson ."
::= { sipCommonNotifObjects 1 } ::= { sipCommonNotifObjects 1 }
sipStatusCodeNotifFrom OBJECT-TYPE sipStatusCodeNotifFrom OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the From header in "This object contains the value of the From header in the
the message containing the status code that caused the message containing the status code that caused the
notification. The header name will be part of notification. The header name will be part of
this object value. For example, 'From: Watson '." this object value.
For example, 'From: Watson '."
::= { sipCommonNotifObjects 2 } ::= { sipCommonNotifObjects 2 }
sipStatusCodeNotifCallId OBJECT-TYPE sipStatusCodeNotifCallId OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the CallId in the "This object contains the value of the CallId in the
message containing the status code that caused the message containing the status code that caused the
notification. The header name will be part of notification. The header name will be part of
skipping to change at page 58, line 12 skipping to change at page 64, line 4
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the CallId in the "This object contains the value of the CallId in the
message containing the status code that caused the message containing the status code that caused the
notification. The header name will be part of notification. The header name will be part of
this object value. this object value.
For example, 'Call-ID: 5551212@information.com'." For example, 'Call-ID: 5551212@information.com'."
::= { sipCommonNotifObjects 3 } ::= { sipCommonNotifObjects 3 }
sipStatusCodeNotifCSeq OBJECT-TYPE sipStatusCodeNotifCSeq OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the CSeq value in the message "This object contains the CSeq value in the message
containing the status code that caused the containing the status code that caused the notification.
notification.
The header name will be part of this object value. The header name will be part of this object value.
For example, 'CSeq: 1722 INVITE'." For example, 'CSeq: 1722 INVITE'."
::= { sipCommonNotifObjects 4 } ::= { sipCommonNotifObjects 4 }
-- --
-- General notification related objects. -- General notification related objects.
-- --
sipNotifApplIndex OBJECT-TYPE sipNotifApplIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
skipping to change at page 61, line 20 skipping to change at page 67, line 28
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 GROUP sipCommonConfigTimerExtMethodGroup
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 extension method timer configuration. not provide any extension method timer configuration.
If implemented, the sipCommonConfigTimerGroup MUST also If implemented, the sipCommonConfigTimerGroup MUST also
be implemented because of a dependency on be implemented because of a dependency on sipCfgTimerT2."
sipCfgTimerT2."
GROUP sipCommonConfigRetryGroup GROUP sipCommonConfigRetryGroup
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 configuration." not provide any retry configuration."
GROUP sipCommonConfigRetryExtMethodGroup GROUP sipCommonConfigRetryExtMethodGroup
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 extension method retry configuration." 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. If implemented,
the sipCommonConfigRetryGroup MUST also be the sipCommonConfigRetryGroup MUST also be implemented."
implemented."
GROUP sipCommonStatsRetryExtMethodsGroup GROUP sipCommonStatsRetryExtMethodsGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to
not provide any extension method retry statistics. not provide any extension method retry statistics.
If implemented, the sipCommonConfigRetryExtMethodGroup If implemented, the sipCommonConfigRetryExtMethodGroup
MUST also be implemented." MUST also be implemented."
GROUP sipCommonNotifGroup GROUP sipCommonNotifGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to
not provide any notifications. If implemented, the not provide any notifications. If implemented, the
sipCommonStatusCodeNotifGroup MUST also be sipCommonStatusCodeNotifGroup and
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 GROUP sipCommonConfigExpiresGroup
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 Expires header configuration." not provide any Expires header configuration."
-- SMIC compiler problems GROUP sipCommonNotifObjectsGroup
-- OBJECT sipStatusCodeRowStatus DESCRIPTION
-- SYNTAX RowStatus { active(1) } "This group is OPTIONAL. A SIP entity can elect to
-- WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } not provide any notifications. If implemented, the
-- DESCRIPTION sipCommonStatusCodeNotifGroup and
-- "Other RowStatus values SHOULD not be supported." sipCommonNotifGroup MUST also be implemented."
::= { sipCommonMIBCompliances 1 } ::= { sipCommonMIBCompliances 1 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipCommonConfigGroup OBJECT-GROUP sipCommonConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipProtocolVersion, sipProtocolVersion,
sipServiceOperStatus, sipServiceOperStatus,
skipping to change at page 63, line 24 skipping to change at page 69, line 41
"A collection of objects providing timer configuration "A collection of objects providing timer configuration
common to all SIP enities." common to all SIP enities."
::= { sipCommonMIBGroups 2 } ::= { sipCommonMIBGroups 2 }
sipCommonConfigTimerExtMethodGroup OBJECT-GROUP sipCommonConfigTimerExtMethodGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgTimerExtMethodTimer sipCfgTimerExtMethodTimer
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing extension method "A collection of objects providing extension method timer
timer configuration." configuration."
::= { sipCommonMIBGroups 3 } ::= { sipCommonMIBGroups 3 }
sipCommonConfigRetryGroup OBJECT-GROUP sipCommonConfigRetryGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgRetryInvite, sipCfgRetryInvite,
sipCfgRetryBye, sipCfgRetryBye,
sipCfgRetryCancel, sipCfgRetryCancel,
sipCfgRetryRegister, sipCfgRetryRegister,
sipCfgRetryOptions, sipCfgRetryOptions,
sipCfgRetryFinalResponse, sipCfgRetryFinalResponse,
skipping to change at page 63, line 50 skipping to change at page 70, line 19
"A collection of objects providing retry configuration "A collection of objects providing retry configuration
common to all SIP enities." common to all SIP enities."
::= { sipCommonMIBGroups 4 } ::= { sipCommonMIBGroups 4 }
sipCommonConfigRetryExtMethodGroup OBJECT-GROUP sipCommonConfigRetryExtMethodGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgRetryExtMethodRetry sipCfgRetryExtMethodRetry
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing extension method "A collection of objects providing extension method retry
retry configuration." configuration."
::= { sipCommonMIBGroups 5 } ::= { sipCommonMIBGroups 5 }
sipCommonStatsGroup OBJECT-GROUP sipCommonStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipSummaryInRequests, sipSummaryInRequests,
sipSummaryOutRequests, sipSummaryOutRequests,
sipSummaryInResponses, sipSummaryInResponses,
sipSummaryOutResponses, sipSummaryOutResponses,
sipSummaryTotalTransactions, sipSummaryTotalTransactions,
sipStatsInviteIns, sipStatsInviteIns,
skipping to change at page 65, line 14 skipping to change at page 71, line 43
DESCRIPTION DESCRIPTION
"A collection of objects providing retry statistics." "A collection of objects providing retry statistics."
::= { sipCommonMIBGroups 7 } ::= { sipCommonMIBGroups 7 }
sipCommonStatsRetryExtMethodsGroup OBJECT-GROUP sipCommonStatsRetryExtMethodsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatsRetryExtMethodRetries sipStatsRetryExtMethodRetries
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing extension method "A collection of objects providing extension method retry
retry statistics." statistics."
::= { sipCommonMIBGroups 8 } ::= { 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 "A collection of notifications common to all SIP entities."
entities."
::= { sipCommonMIBGroups 9 } ::= { sipCommonMIBGroups 9 }
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 "A collection of objects related to controlling and attribution
attribution of notifications common to all SIP of notifications common to all SIP entities."
entities."
::= { sipCommonMIBGroups 10 } ::= { sipCommonMIBGroups 10 }
sipCommonConfigExpiresGroup OBJECT-GROUP sipCommonConfigExpiresGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgExpiresInvite, sipCfgExpiresInvite,
sipCfgExpiresRegister, sipCfgExpiresRegister,
sipCfgExpiresHeaderMethod, sipCfgExpiresHeaderMethod,
sipCfgExpiresHeaderValue, sipCfgExpiresHeaderValue,
sipCfgExpiresStatusCodeStatus sipCfgExpiresStatusCodeStatus
} }
skipping to change at page 66, line 25 skipping to change at page 73, line 10
} }
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 12 }
END END
5.3. SIP User Agent 7.3 SIP User Agent MIB Module
SIP-UA-MIB DEFINITIONS ::= BEGIN SIP-UA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Unsigned32, Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
skipping to change at page 66, line 51 skipping to change at page 73, line 36
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;
sipUAMIB MODULE-IDENTITY sipUAMIB MODULE-IDENTITY
LAST-UPDATED "200306250000Z" LAST-UPDATED "200307300000Z"
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. ipDialog, Inc.
postal: 7701 N. Lamar Blvd., Suite 304 postal: 7701 N. Lamar Blvd., Suite 304
Austin, TX 78752-1023 Austin, TX 78752-1023
USA USA
email: jmaeng@ipdialog.com email: jmaeng@ipdialog.com
phone: +1 512 371 1770 phone: +1 512 371 1770
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
skipping to change at page 67, line 55 skipping to change at page 74, line 46
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 Copyright (C) The Internet Society (2003). This version
Version of this MIB module is part of RFC XXXX; see of this MIB module is part of RFC XXXX; see the RFC
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 "200306250000Z" REVISION "200307300000Z"
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 }
skipping to change at page 68, line 43 skipping to change at page 75, line 40
::= { sipUACfgSipServer 1 } ::= { sipUACfgSipServer 1 }
sipUACfgSipServerEntry OBJECT-TYPE sipUACfgSipServerEntry OBJECT-TYPE
SYNTAX SipUACfgSipServerEntry SYNTAX SipUACfgSipServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of server configuration. "A row of server configuration.
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 user agent present in this system. applIndex is used to
to uniquely identify these instances of SIP user agents uniquely identify these instances of SIP user agents and
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, sipUACfgSipServerIndex }
::= { sipUACfgSipServerTable 1 } ::= { sipUACfgSipServerTable 1 }
SipUACfgSipServerEntry ::= SipUACfgSipServerEntry ::=
SEQUENCE { SEQUENCE {
skipping to change at page 70, line 12 skipping to change at page 77, line 21
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 sipUACfgSipServerAddr object in the
same set operation. same set operation.
'createAndWait' : not applicable. 'createAndWait' : not applicable.
'destroy' : the row's address will no longer be 'destroy' : the row's address will no longer be used
used by the user agent and the row by the user agent and the row will be
will be removed from the table." removed from the table."
::= { sipUACfgSipServerEntry 4 } ::= { sipUACfgSipServerEntry 4 }
-- --
-- Conformance -- Conformance
-- --
sipUAMIBCompliances sipUAMIBCompliances
OBJECT IDENTIFIER ::= { sipUAMIBConform 1 } OBJECT IDENTIFIER ::= { sipUAMIBConform 1 }
sipUAMIBGroups sipUAMIBGroups
OBJECT IDENTIFIER ::= { sipUAMIBConform 2 } OBJECT IDENTIFIER ::= { sipUAMIBConform 2 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
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 }
-- SMIC compiler problems
-- OBJECT sipUACfgSipServerStatus
-- SYNTAX RowStatus { active(1), notReady(3) }
-- WRITE-SYNTAX RowStatus { notInService(2), createAndGo(4),
-- destroy(6) }
-- DESCRIPTION
-- "createAndWait is not applicable."
::= { sipUAMIBCompliances 1 } ::= { sipUAMIBCompliances 1 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipUAConfigGroup OBJECT-GROUP sipUAConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipUACfgSipServerAddrType, sipUACfgSipServerAddrType,
sipUACfgSipServerAddr, sipUACfgSipServerAddr,
sipUACfgSipServerStatus sipUACfgSipServerStatus
} }
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
5.4. SIP Server (Registrar, Redirect & Proxy Server) 7.4 SIP Server (Registrar, Redirect & Proxy 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 71, line 41 skipping to change at page 78, line 48
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 "200306250000Z" LAST-UPDATED "200307300000Z"
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 72, line 25 skipping to change at page 79, line 39
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 400 Centennial Parkway postal: 400 Centennial Parkway
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 "Session Initiation Protocol (SIP) Server MIB module.
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 with one or more participants. These sessions
sessions include Internet multimedia conferences include Internet multimedia conferences and Internet
and Internet telephone calls. SIP is defined in telephone calls. SIP is defined in RFC 3261 (June
RFC 3261 (June 2002). 2002).
This MIB is defined for the management of SIP This MIB is defined for the management of SIP Proxy,
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 Unlike a User Agent Server it does not accept calls.
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 requests. A Registrar is typically co-located with a
a Proxy or Redirect Server. Proxy or Redirect Server.
Copyright (C) The Internet Society (2003). Copyright (C) The Internet Society (2003).
This version of this MIB module is part of RFC This version of this MIB module is part of RFC XXXX;
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 "200306250000Z" REVISION "200307300000Z"
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 -- RFC Ed: replace yy with actual IANA assigned number and remove this note
-- 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 } sipServerStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 2 }
skipping to change at page 73, line 40 skipping to change at page 81, line 9
to SIP Redirect and Proxy Servers." to SIP Redirect and Proxy Servers."
::= { sipServerCfg 1 } ::= { sipServerCfg 1 }
sipServerCfgEntry OBJECT-TYPE sipServerCfgEntry OBJECT-TYPE
SYNTAX SipServerCfgEntry SYNTAX SipServerCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common configuration. "A row of common configuration.
Each row represents those objects for a particular Each row represents those objects for a particular SIP
SIP server present in this system. applIndex is server present in this system. applIndex is used to
used to uniquely identify these instances of SIP uniquely identify these instances of SIP servers and
servers and correlate them through the common correlate them through the common framework of the
framework of the NETWORK-SERVICES-MIB (RFC 2788). NETWORK-SERVICES-MIB (RFC 2788). The same value of
The same value of applIndex used in the applIndex used in the corresponding SIP-COMMON-MIB
corresponding SIP-COMMON-MIB is used here. is used here.
The objects in this table entry SHOULD be non- The objects in this table entry SHOULD be non-volatile
volatile and their value SHOULD be kept at reboot." and their value SHOULD be kept at reboot."
INDEX { applIndex } INDEX { applIndex }
::= { sipServerCfgTable 1 } ::= { sipServerCfgTable 1 }
SipServerCfgEntry ::= SipServerCfgEntry ::=
SEQUENCE { SEQUENCE {
sipServerHostAddrType InetAddressType, sipServerHostAddrType InetAddressType,
sipServerHostAddr InetAddress sipServerHostAddr InetAddress
} }
sipServerHostAddrType OBJECT-TYPE sipServerHostAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of Internet address by which the SIP server "The type of Internet address by which the SIP server
is reachable." is reachable."
REFERENCE REFERENCE
"RFC 3261, Section 19.1.1" "RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 1 } ::= { sipServerCfgEntry 1 }
skipping to change at page 74, line 20 skipping to change at page 81, line 43
is reachable." is reachable."
REFERENCE REFERENCE
"RFC 3261, Section 19.1.1" "RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 1 } ::= { sipServerCfgEntry 1 }
sipServerHostAddr OBJECT-TYPE sipServerHostAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the host portion of a SIP URI that is "This is the host portion of a SIP URI that is assigned
assigned to the SIP server. It MAY contain a fully to the SIP server. It MAY contain a fully qualified
qualified domain name, or an IP address. The length domain name, or an IP address. The length of the value
of the value will depend on the type of address will depend on the type of address specified.
specified. sipServerHostAddrType formalizes the sipServerHostAddrType formalizes the type of address
type of address given by this object. It is the given by this object. It is the users responsibility
users responsibility to maintain consistency between to maintain consistency between this object and the
this object and the type specified by type specified by sipServerHostAddrType."
sipServerHostAddrType."
REFERENCE REFERENCE
"RFC 3261, Section 19.1.1" "RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 2 } ::= { sipServerCfgEntry 2 }
-- --
-- This group contains MIB objects related to SIP Proxy -- This group contains MIB objects related to SIP Proxy Servers.
-- Servers.
-- --
sipProxyCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 3 } sipProxyCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 3 }
sipProxyStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 4 } sipProxyStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 4 }
-- --
-- Proxy Server Configuration -- Proxy Server Configuration
-- --
sipProxyCfgTable OBJECT-TYPE sipProxyCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipProxyCfgEntry SYNTAX SEQUENCE OF SipProxyCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 75, line 5 skipping to change at page 82, line 32
to SIP Proxy Servers." to SIP Proxy Servers."
::= { sipProxyCfg 1 } ::= { sipProxyCfg 1 }
sipProxyCfgEntry OBJECT-TYPE sipProxyCfgEntry OBJECT-TYPE
SYNTAX SipProxyCfgEntry SYNTAX SipProxyCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common proxy configuration. "A row of common proxy configuration.
Each row represents those objects for a particular Each row represents those objects for a particular SIP
SIP server present in this system. applIndex is server present in this system. applIndex is used to
used to uniquely identify these instances of SIP uniquely identify these instances of SIP servers and
servers and correlate them through the common correlate them through the common framework of the
framework of the NETWORK-SERVICES-MIB (RFC 2788). NETWORK-SERVICES-MIB (RFC 2788). The same value of
The same value of applIndex used in the applIndex used in the corresponding SIP-COMMON-MIB
corresponding SIP-COMMON-MIB is used here. is used here.
The objects in this table entry SHOULD be non- The objects in this table entry SHOULD be non-volatile
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, sipRequestMaxExpires Unsigned32,
sipProxyStatefulness INTEGER, sipProxyStatefulness INTEGER,
sipProxySendsCancel TruthValue, sipProxySendsCancel TruthValue,
sipProxyForwardAll1xx TruthValue, sipProxyForwardAll1xx TruthValue,
sipProxyRecursion TruthValue, sipProxyRecursion TruthValue,
skipping to change at page 75, line 37 skipping to change at page 83, line 16
sipProxyAuthRealm SnmpAdminString, sipProxyAuthRealm SnmpAdminString,
sipProxyNonceLifeTime Unsigned32 sipProxyNonceLifeTime Unsigned32
} }
sipRequestMaxExpires OBJECT-TYPE sipRequestMaxExpires OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum duration that a "This object specifies the maximum duration that a SIP
SIP server will accept from a client in the Expires server will accept from a client in the Expires
header." header."
REFERENCE REFERENCE
"RFC 3261 Section 20.19" "RFC 3261 Section 20.19"
::= { sipProxyCfgEntry 1 } ::= { 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-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default mode of operation "This object specifies the default mode of operation for
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 maintain the client or server transaction state machines
machines when it processes requests. A stateless when it processes requests. A stateless proxy forwards
proxy forwards every request it receives downstream every request it receives downstream and every response
and every response it receives upstream. If the it receives upstream. If the value of this object is
value of this object is stateless(1), the proxy stateless(1), the proxy defaults to stateless
defaults to stateless operations. operations.
A transaction stateful proxy, or simply a 'stateful A transaction stateful proxy, or simply a 'stateful
proxy', is a logical entity that maintains the proxy', is a logical entity that maintains the client
client and server transaction state machines during and server transaction state machines during the
the processing of a request. A (transaction) processing of a request. A (transaction) stateful proxy
stateful proxy is not the same as a call stateful is not the same as a call stateful proxy. If the value
proxy. If the value if this object is if this object is transactionStateful(2), the proxy is
transactionStateful(2), the proxy is stateful on a stateful on a transaction basis.
transaction basis.
A call stateful proxy is a logical entity if it A call stateful proxy is a logical entity if it retains
retains state for a dialog from the initiating \ state for a dialog from the initiating INVITE to the
INVITE to the terminating BYE request. A call terminating BYE request. A call stateful proxy is
stateful proxy is always transaction stateful, but always transaction stateful, but the converse is not
the converse is not necessarily true. If the value necessarily true. If the value of this object is
of this object is callStateful(3), the proxy is call callStateful(3), the proxy is call stateful."
stateful."
REFERENCE REFERENCE
"RFC 3261, Section 16" "RFC 3261, Section 16"
::= { sipProxyCfgEntry 2 } ::= { sipProxyCfgEntry 2 }
sipProxySendsCancel OBJECT-TYPE sipProxySendsCancel OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not a forking proxy "This object specifies whether or not a forking proxy sends
sends CANCEL on outstanding branch requests after CANCEL on outstanding branch requests after receiving a
receiving a 2xx or 6xx, or after the request times- 2xx or 6xx, or after the request times-out.
out.
If the value of this object is 'true', the server If the value of this object is 'true', the server sends
Sends a CANCELs on branches where no definitive a CANCELs on branches where no definitive response has been
response has been received. If 'false', the proxy received. If 'false', the proxy does not send CANCELs."
does not send CANCELs."
REFERENCE REFERENCE
"RFC 3261, Section 10" "RFC 3261, Section 10"
::= { sipProxyCfgEntry 3 } ::= { sipProxyCfgEntry 3 }
sipProxyForwardAll1xx OBJECT-TYPE sipProxyForwardAll1xx OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the proxy "This object specifies whether or not the proxy forwards
forwards all 1xx responses, except the 100 Trying all 1xx responses, except the 100 Trying response,
response, upstream towards the source of the upstream towards the source of the request.
request.
If the value of this object is 'true', the 1xx If the value of this object is 'true', the 1xx responses
responses are sent. If the value is 'false', are sent. If the value is 'false', duplicate 1xx
duplicate 1xx responses are not sent upstream." responses are not sent upstream."
::= { sipProxyCfgEntry 4 } ::= { sipProxyCfgEntry 4 }
sipProxyRecursion OBJECT-TYPE sipProxyRecursion OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Proxy "This object specifies whether or not the Proxy performs
performs recursive search on the Contacts provided recursive search on the Contacts provided in 3xx
in 3xx redirects. redirects.
If the value of this object is 'true', a recursive If the value of this object is 'true', a recursive search
search is performed. If the value is 'false', no is performed. If the value is 'false', no search is
search is performed, the 3xx response is sent performed, the 3xx response is sent upstream towards the
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 5 }
sipProxyProvideAlternatives OBJECT-TYPE sipProxyProvideAlternatives OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object specifies whether or not the Server "The object specifies whether or not the Server provides
provides alternative Contacts in 3xx and 485 alternative Contacts in 3xx and 485 responses.
responses.
If the value of this object is 'true', the server If the value of this object is 'true', the server inserts a
inserts a list of alternative URIs into a Contact list of alternative URIs into a Contact header where the
header where the request Originator may possibly request Originator may possibly find the desired called
find the desired called party. If the value is party. If the value is 'false', the server doesn't add
'false', the server doesn't add Contact information Contact information to 3xx and 485 responses.
to 3xx and 485 responses.
Note that the policies of a server MAY limit the Note that the policies of a server MAY limit the
particular alternatives that are returned when this particular alternatives that are returned when this object
object is set to 'true'." is set to 'true'."
REFERENCE REFERENCE
"RFC 3261, Sections 13.2.2.2 and 16.5" "RFC 3261, Sections 13.2.2.2 and 16.5"
DEFVAL { true } DEFVAL { true }
::= { sipProxyCfgEntry 6 } ::= { sipProxyCfgEntry 6 }
sipProxyRecordRoute OBJECT-TYPE sipProxyRecordRoute OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the proxy adds "This object specifies whether or not the proxy adds itself
itself to the Record-Route header as a default to the Record-Route header as a default action. This
action. This header is used to list the proxies header is used to list the proxies that insist on being in
that insist on being in the signaling path for the signaling path for subsequent requests related to the
subsequent requests related to a call-leg. call-leg.
If the value of this object is 'true', the proxy If the value of this object is 'true', the proxy adds itself
adds itself to the end of the Record-Route header, to the end of the Record-Route header, creating the header
creating the header if required. If the value is if required. If the value is 'false', the proxy does
'false', the proxy does not add itself to the not add itself to the Record-Route header."
Record-Route header."
REFERENCE REFERENCE
"RFC 3261, Section 20.30" "RFC 3261, Section 20.30"
::= { sipProxyCfgEntry 7 } ::= { sipProxyCfgEntry 7 }
-- --
-- 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 78, line 30 skipping to change at page 86, line 17
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)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the authentication methods "This object specifies the authentication methods that
that MAY be used to authenticate request MAY be used to authenticate request originators.
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 8 }
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- "This object specifies the realm used in Proxy-Authenticate
Authenticate headers. Note that this MAY need to be headers. Note that this MAY need to be stored per user."
stored per user."
REFERENCE REFERENCE
"RFC 3261, Section 22.1" "RFC 3261, Section 22.1"
::= { sipProxyCfgEntry 9 } ::= { sipProxyCfgEntry 9 }
sipProxyNonceLifeTime OBJECT-TYPE sipProxyNonceLifeTime OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the lifetime of a given nonce. "This object specifies the lifetime of a given nonce. A
A nonce is a server specified value whose contents nonce is a server specified value whose contents are
are opaque to the entity being authenticated and opaque to the entity being authenticated and which is used
which is used in calculating authentication data. in calculating authentication data. If this object has a
If this object has a value of zero, then nonces are value of zero, then nonces are not reused."
not reused."
::= { sipProxyCfgEntry 10 } ::= { 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 "This table contains the statistics objects applicable
applicable to all SIP Proxy Servers in this system." to all SIP Proxy Servers in this system."
::= { sipProxyStats 1 } ::= { sipProxyStats 1 }
sipProxyStatsEntry OBJECT-TYPE sipProxyStatsEntry OBJECT-TYPE
SYNTAX SipProxyStatsEntry SYNTAX SipProxyStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics. "A row of summary statistics.
Each row represents those objects for a particular Each row represents those objects for a particular SIP
SIP server present in this system. applIndex is server present in this system. applIndex is used to
used to uniquely identify these instances of SIP uniquely identify these instances of SIP servers and
servers and correlate them through the common correlate them through the common framework of the
framework of the NETWORK-SERVICES-MIB (RFC 2788). NETWORK-SERVICES-MIB (RFC 2788). The same value of
The same value of applIndex used in the applIndex used in the corresponding SIP-COMMON-MIB
corresponding SIP-COMMON-MIB is used here." is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipProxyStatsTable 1 } ::= { sipProxyStatsTable 1 }
SipProxyStatsEntry ::= SipProxyStatsEntry ::=
SEQUENCE { SEQUENCE {
sipNumProxyRequireFailures Counter32 sipNumProxyRequireFailures Counter32
} }
sipNumProxyRequireFailures OBJECT-TYPE sipNumProxyRequireFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the number of occurrences of "This object contains the number of occurrences of
unsupported options being specified in received unsupported options being specified in received Proxy-
Proxy-Require headers. Such occurrences result in a Require headers. Such occurrences result in a 420 Bad
420 Bad Extension status code being returned." Extension status code being
returned."
::= { sipProxyStatsEntry 1 } ::= { sipProxyStatsEntry 1 }
-- --
-- This group contains MIB objects related to SIP Redirect
-- Servers.
--
sipRedirCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 5 }
sipRedirStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 6 }
-- none at this time
--
-- This group contains MIB objects related to SIP Registrars. -- This group contains MIB objects related to SIP Registrars.
-- --
sipRegCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 7 } sipRegCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 5 }
sipRegStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 8 } sipRegStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 6 }
-- --
-- Registrar Configuration -- Registrar Configuration
-- --
sipRegCfgTable OBJECT-TYPE sipRegCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegCfgEntry SYNTAX SEQUENCE OF SipRegCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable "This table contains configuration objects applicable
SIP Registrars." SIP Registrars."
::= { sipRegCfg 1 } ::= { sipRegCfg 1 }
sipRegCfgEntry OBJECT-TYPE sipRegCfgEntry OBJECT-TYPE
SYNTAX SipRegCfgEntry SYNTAX SipRegCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common Registrar configuration. "A row of common Registrar configuration.
Each row represents those objects for a particular Each row represents those objects for a particular SIP
SIP server present in this system. applIndex is server present in this system. applIndex is used to
used to uniquely identify these instances of SIP uniquely identify these instances of SIP servers and
servers and correlate them through the common correlate them through the common framework of the
framework of the NETWORK-SERVICES-MIB (RFC 2788). NETWORK-SERVICES-MIB (RFC 2788). The same value of
The same value of applIndex used in the applIndex used in the corresponding SIP-COMMON-MIB
corresponding SIP-COMMON-MIB is used here." is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipRegCfgTable 1 } ::= { sipRegCfgTable 1 }
SipRegCfgEntry ::= SipRegCfgEntry ::=
SEQUENCE { SEQUENCE {
sipRegAllowThirdParty TruthValue, sipRegAllowThirdParty TruthValue,
sipRegMaxContactExpiryDuration Unsigned32, sipRegMaxContactExpiryDuration Unsigned32,
sipRegMaxUsers Unsigned32, sipRegMaxUsers Unsigned32,
sipRegCurrentUsers Gauge32, sipRegCurrentUsers Gauge32,
sipRegDfltRegActiveInterval Unsigned32 sipRegDfltRegActiveInterval Unsigned32
} }
sipRegAllowThirdParty OBJECT-TYPE sipRegAllowThirdParty OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Registrar "This object specifies whether or not the Registrar SHOULD
SHOULD allow third party registrations. In third- allow third party registrations. In third-party
party registration, the entity issuing the request registration, the entity issuing the request (in the
(in the From header) is different from the entity From header) is different from the entity being registered
being registered (in the To header) to whom the (in the To header) to whom the provided Contact information
provided Contact information applies. applies.
If the value of thsipRegAllowThirdPartyis object is
'true', the Registrar allows third-party
registrations. If the value is 'false', third-party
registrations are rejected: a 403 (Forbidden) status
code is returned to the requester.
This object SHOULD be non-volatile and its value If the value of thsipRegAllowThirdPartyis object is 'true',
SHOULD be kept at reboot." the Registrar allows third-party registrations. If the
value is 'false', third-party registrations are rejected:
a 403 (Forbidden) status code is returned to the requester.
This object SHOULD be non-volatile and its value SHOULD
be kept at reboot."
REFERENCE REFERENCE
"RFC 3261, Section 10.2" "RFC 3261, Section 10.2"
::= { sipRegCfgEntry 1 } ::= { sipRegCfgEntry 1 }
sipRegMaxContactExpiryDuration OBJECT-TYPE sipRegMaxContactExpiryDuration OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-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 User Agents can specify expiry using either an Expiry
Expiry header in a REGISTER request, or using an header in a REGISTER request, or using an Expires parameter
Expires parameter in a Contact header in a REGISTER in a Contact header in a REGISTER request. If the value
request. If the value requested by the User Agent requested by the User Agent is greater than the value
is greater than the value of this object, then the of this object, then the contact information is given the
contact information is given the duration specified duration specified by this object, and that duration
by this object, and that duration is indicated to is indicated to the User Agent in the response."
the User Agent in the response."
DEFVAL { 4294967295 } 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 "This object specifies the maximum number of users that
that the Registrar supports. The current number of the Registrar supports. The current number of users is
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." configured on the Registrar."
::= { sipRegCfgEntry 4 } ::= { sipRegCfgEntry 4 }
sipRegDfltRegActiveInterval OBJECT-TYPE sipRegDfltRegActiveInterval OBJECT-TYPE
skipping to change at page 82, line 25 skipping to change at page 90, line 21
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default time interval the "This object specifies the default time interval the
Registrar considers registrations to be active. The Registrar considers registrations to be active. The
value is used to compute the Expires header in the value is used to compute the Expires header in the
REGISTER response. If a user agent requests a time REGISTER response. If a user agent requests a time
interval shorter than specified by this object, the interval shorter than specified by this object, the
Registrar SHOULD honor that request. If a Contact Registrar SHOULD honor that request. If a Contact
entry does not have an 'expires' parameter, the entry does not have an 'expires' parameter, the value
value of the Expires header field is used instead. of the Expires header field is used instead. If a
If a Contact entry has no 'expires' parameter and no Contact entry has no 'expires' parameter and no the
the Expires header field is present, the value of Expires header field is present, the value of this
this object is used as the default value. object is used as the default value.
This object SHOULD be non-volatile and its value This object SHOULD be non-volatile and its value SHOULD
SHOULD be kept at reboot." be kept at reboot."
REFERENCE "RFC 3261, Section 10.2" REFERENCE "RFC 3261, Section 10.2"
::= { sipRegCfgEntry 5 } ::= { sipRegCfgEntry 5 }
-- --
-- Per User Information -- Per User Information
-- --
sipRegUserTable OBJECT-TYPE sipRegUserTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegUserEntry SYNTAX SEQUENCE OF SipRegUserEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on all users "This table contains information on all users registered
registered to each Registrar in this system." to each Registrar in this system."
::= { sipRegCfg 2 } ::= { sipRegCfg 2 }
sipRegUserEntry OBJECT-TYPE sipRegUserEntry OBJECT-TYPE
SYNTAX SipRegUserEntry SYNTAX SipRegUserEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single user "This entry contains information for a single user
registered to this Registrar. registered to this Registrar.
Each row represents those objects for a particular Each row represents those objects for a particular SIP
SIP server present in this system. applIndex is server present in this system. applIndex is used to
used to uniquely identify these instances of SIP uniquely identify these instances of SIP servers and
servers and correlate them through the common correlate them through the common framework of the
framework of the NETWORK-SERVICES-MIB (RFC 2788). NETWORK-SERVICES-MIB (RFC 2788). The same value of
The same value of applIndex used in the applIndex used in the corresponding SIP-COMMON-MIB
corresponding SIP-COMMON-MIB is used here." is used here."
INDEX { applIndex, sipUserIndex } INDEX { applIndex, sipUserIndex }
::= { sipRegUserTable 1 } ::= { sipRegUserTable 1 }
SipRegUserEntry ::= SipRegUserEntry ::=
SEQUENCE { SEQUENCE {
sipUserIndex Unsigned32, sipUserIndex Unsigned32,
sipUserUri SnmpAdminString, sipUserUri SnmpAdminString,
sipUserAuthenticationFailures Counter32, sipUserAuthenticationFailures Counter32,
sipUserTableRowStatus RowStatus sipUserTableRowStatus RowStatus
} }
sipUserIndex OBJECT-TYPE sipUserIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in "This object uniquely identifies a conceptual row in the
the table." table."
::= { sipRegUserEntry 1 } ::= { sipRegUserEntry 1 }
sipUserUri OBJECT-TYPE sipUserUri OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the user's address-of-record. "This object contains the user's address-of-record. It
It is the main form by which the Registrar knows the is the main form by which the Registrar knows the user.
user. The format is typically 'user@domain'. It is The format is typically 'user@domain'. It is contained
contained in the To header for all REGISTER in the To header for all REGISTER requests."
requests."
::= { sipRegUserEntry 2 } ::= { sipRegUserEntry 2 }
sipUserAuthenticationFailures OBJECT-TYPE sipUserAuthenticationFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of times "This object contains a count of the number of times the
the user has failed authentication." user has failed authentication."
::= { sipRegUserEntry 3 } ::= { sipRegUserEntry 3 }
sipUserTableRowStatus OBJECT-TYPE sipUserTableRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row status of the entry. This object is required "The row status of the entry. This object is required
to create or delete rows remotely by a manager." to create or delete rows remotely by a manager."
::= { sipRegUserEntry 4 } ::= { sipRegUserEntry 4 }
-- --
-- Per Contact Information -- Per Contact Information
-- --
sipContactTable OBJECT-TYPE sipContactTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipContactEntry SYNTAX SEQUENCE OF SipContactEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on every location "This table contains information on every location where
where a registered user (specified by sipUserIndex) a registered user (specified by sipUserIndex) wishes to
wishes to be found (i.e. the user has provided be found (i.e. the user has provided Contact information
Contact information to each SIP Registrar in this to each SIP Registrar in this system)."
system)."
::= { sipRegCfg 3 } ::= { sipRegCfg 3 }
sipContactEntry OBJECT-TYPE sipContactEntry OBJECT-TYPE
SYNTAX SipContactEntry SYNTAX SipContactEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single "This entry contains information for a single Contact.
Contact. Multiple contacts may exist for a single Multiple contacts may exist for a single user.
user.
Each row represents those objects for a particular Each row represents those objects for a particular SIP
SIP server present in this system. applIndex is server present in this system. applIndex is used to
used to uniquely identify these instances of SIP uniquely identify these instances of SIP servers and
servers and correlate them through the common correlate them through the common framework of the
framework of the NETWORK-SERVICES-MIB (RFC 2788). NETWORK-SERVICES-MIB (RFC 2788). The same value of
The same value of applIndex used in the applIndex used in the corresponding SIP-COMMON-MIB
corresponding SIP-COMMON-MIB is used here." is used here."
INDEX { applIndex, sipUserIndex, sipContactIndex } INDEX { applIndex, sipUserIndex, sipContactIndex }
::= { sipContactTable 1 } ::= { sipContactTable 1 }
SipContactEntry ::= SipContactEntry ::=
SEQUENCE { SEQUENCE {
sipContactIndex Unsigned32, sipContactIndex Unsigned32,
sipContactDisplayName SnmpAdminString, sipContactDisplayName SnmpAdminString,
sipContactURI SnmpAdminString, sipContactURI SnmpAdminString,
sipContactLastUpdated TimeStamp, sipContactLastUpdated TimeStamp,
sipContactExpiry DateAndTime, sipContactExpiry DateAndTime,
skipping to change at page 85, line 11 skipping to change at page 93, line 21
DESCRIPTION DESCRIPTION
"Along with the sipUserIndex, this object uniquely "Along with the sipUserIndex, this object uniquely
identifies a conceptual row in the table." identifies a conceptual row in the table."
::= { sipContactEntry 1 } ::= { sipContactEntry 1 }
sipContactDisplayName OBJECT-TYPE sipContactDisplayName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the display name for the "This object contains the display name for the Contact.
Contact. For example, 'Santa at Home', or 'Santa on his Sled',
For example, 'Santa at Home', or 'Santa on his corresponding to contact URIs of
Sled', corresponding to contact URIs of
sip:BigGuy@sip.northpole.ca or sip:BigGuy@sip.northpole.ca or
sip:sclaus817@sip.mobile.com, respectively." sip:sclaus817@sip.mobile.com, respectively."
::= { sipContactEntry 2 } ::= { sipContactEntry 2 }
sipContactURI OBJECT-TYPE sipContactURI OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains either a SIP URI where "This object contains either a SIP URI where
the user can be contacted. This URI is normally the user can be contacted. This URI is normally returned
returned to a client from a Redirect Server, or is to a client from a Redirect Server, or is used as the
used as the RequestURI in a SIP request line for RequestURI in a SIP request line for requests forwarded
requests forwarded by a proxy." by a proxy."
::= { sipContactEntry 3 } ::= { sipContactEntry 3 }
sipContactLastUpdated OBJECT-TYPE sipContactLastUpdated OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the time when this contact "This object indicates the time when this contact
information was accepted. If the contact information was accepted. If the contact information
information is updated via a subsequent REGISTER of is updated via a subsequent REGISTER of the same
the same information, this object is also updated." information, this object is also updated."
::= { sipContactEntry 4 } ::= { sipContactEntry 4 }
sipContactExpiry OBJECT-TYPE sipContactExpiry OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the date and time when the "This object contains the date and time when the contact
contact information will no longer be valid. Such information will no longer be valid. Such times may be
times may be specified by the user at registration specified by the user at registration (Expires header
(Expires header or expiry parameter in the Contact or expiry parameter in the Contact information), or a
information), or a system default can be applied." system default can be applied."
::= { sipContactEntry 5 } ::= { sipContactEntry 5 }
sipContactPreference OBJECT-TYPE sipContactPreference OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a relative preference for the "This object indicates a relative preference for the
particular Contact header field value compared to particular Contact header field value compared to other
other bindings for this address-of-record. A bindings for this address-of-record. A registering user
registering user may provide this preference as a may provide this preference as a 'qvalue'parameter in
'qvalue'parameter in the Contact header. the Contact header.
The format of this item is a decimal number between The format of this item is a decimal number between 0
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 sipContactRetryAfter OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates that the contact information "This object indicates that the contact information is
is currently inactive, and that it SHOULD only be currently inactive, and that it SHOULD only be
activated after the date and time specified by the activated after the date and time specified by the object.
object. This value is provided by a user when This value is provided by a user when deleting contact
deleting contact information using a REGISTER information using a REGISTER request containing a
request containing a Retry-After header." Retry-After header."
REFERENCE REFERENCE
"RFC 3261, Section 20.33" "RFC 3261, Section 20.33"
::= { sipContactEntry 7 } ::= { 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
skipping to change at page 86, line 52 skipping to change at page 95, line 20
applicable to all SIP Registrars in this system." applicable to all SIP Registrars in this system."
::= { sipRegStats 1 } ::= { sipRegStats 1 }
sipRegStatsEntry OBJECT-TYPE sipRegStatsEntry OBJECT-TYPE
SYNTAX SipRegStatsEntry SYNTAX SipRegStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics. "A row of summary statistics.
Each row represents those objects for a particular Each row represents those objects for a particular SIP
SIP server present in this system. applIndex is server present in this system. applIndex is used to
used to uniquely identify these instances of SIP uniquely identify these instances of SIP servers and
servers and correlate them through the common correlate them through the common framework of the
framework of the NETWORK-SERVICES-MIB (RFC 2788). NETWORK-SERVICES-MIB (RFC 2788). The same value of
applIndex used in the corresponding SIP-COMMON-MIB
The same value of applIndex used in the is used here."
corresponding SIP-COMMON-MIB is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipRegStatsTable 1 } ::= { sipRegStatsTable 1 }
SipRegStatsEntry ::= SipRegStatsEntry ::=
SEQUENCE { SEQUENCE {
sipRegAcceptedRegistrations Counter32, sipRegAcceptedRegistrations Counter32,
sipRegRejectedRegistrations Counter32 sipRegRejectedRegistrations Counter32
} }
sipRegAcceptedRegistrations OBJECT-TYPE sipRegAcceptedRegistrations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of "This object contains a count of the number of REGISTER
REGISTER requests that have been accepted (status requests that have been accepted (status code 200) by
code 200) by the Registrar. This includes additions the Registrar. This includes additions of new contact
of new contact information, refreshing contact information, refreshing contact information, as well as
information, as well as requests for deletion of requests for deletion of contact information."
contact information."
::= { sipRegStatsEntry 1 } ::= { sipRegStatsEntry 1 }
sipRegRejectedRegistrations OBJECT-TYPE sipRegRejectedRegistrations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number REGISTER "This object contains a count of the number REGISTER
requests that have been rejected by the Registrar." requests that have been rejected by the Registrar."
::= { sipRegStatsEntry 2 } ::= { sipRegStatsEntry 2 }
skipping to change at page 88, line 36 skipping to change at page 97, line 14
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipServerConfigGroup OBJECT-GROUP sipServerConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipServerHostAddrType, sipServerHostAddrType,
sipServerHostAddr sipServerHostAddr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration common
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, sipRequestMaxExpires,
sipProxyStatefulness, sipProxyStatefulness,
sipProxySendsCancel, sipProxySendsCancel,
sipProxyForwardAll1xx, sipProxyForwardAll1xx,
sipProxyRecursion, sipProxyRecursion,
sipProxyProvideAlternatives, sipProxyProvideAlternatives,
skipping to change at page 89, line 50 skipping to change at page 98, line 35
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 }
END END
6. Changes from previous drafts 8. Changes from Previous Draft Revisions
o Changes from draft-ietf-sip-mib-05 Changes from draft-ietf-sip-mib-06
Front paper/Back paper and General changes o General
o Removed all references and special handling of SIP INFO method
Removed references and objects specific to RFC 2976: INFO will be
treated as any SIP extension method.
o Changed requirements verbs from lowercase to uppercase wherever * Minor editorial changes in the Textual Conventions section.
o SIP-COMMON-MIB
* sipStatusCodeValue SYNTAX changed from INTEGER to Unsigned32.
* Optional sipCommonNotifObjectsGroup explicitly added to
MODULE-COMPLIANCE.
* Removed OBJECT refinement for sipStatusCodeRowStatus added to
compliance in previous revision. SMIC MIB compiler issues
required it to be commented out. Instead, simply removed it.
o SIP-SERVER-MIB
* Removed OID placeholders: sipRedirCfg, sipRedirStats.
sipRegCfg and sipRegStats OID values subsequently changed as a
result.
o SIP-UA-MIB
* Removed OBJECT refinement for sipUACfgSipServerStatus added to
compliance in previous revision. SMIC MIB compiler issues
required it to be commented out. Instead, simply removed it.
Changes from draft-ietf-sip-mib-05
o Front paper/Back paper and General changes
* Removed all references and special handling of SIP INFO method
Removed references and objects specific to RFC 2976: INFO will
be treated as any SIP extension method.
* Changed requirements verbs from lowercase to uppercase wherever
appropriate. appropriate.
o Added RFC Editor notes. * Added RFC Editor notes.
o Updated all REFERENCE clauses and DESCRIPTIONS from RFC 2543 * Updated all REFERENCE clauses and DESCRIPTIONS from RFC 2543 to
to RFC 3261. RFC 3261.
o Explained the approach taken for extension methods that might be * Explained the approach taken for extension methods that might
defined in the future. be defined in the future.
o Defined a mapping of sipServiceOperStatus to applOperStatus. * Defined a mapping of sipServiceOperStatus to applOperStatus.
o Enhanced Security section with details on various objects. * Enhanced Security section with details on various objects.
o 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.
SIP-COMMON-MIB o SIP-COMMON-MIB
o Removed sipTransactionTable after input from SIP community. * Removed sipTransactionTable after input from SIP community.
o Made all extension method tables augmentations of * Made all extension method tables augmentations of
sipExtMethodSupportedTable. This resulted in the removal sipExtMethodSupportedTable. This resulted in the removal of
of the following objects: sipCfgTimerExtMethodName, the following objects: sipCfgTimerExtMethodName,
sipCfgRetryExtMethodName, sipStatsExtMethodName, sipCfgRetryExtMethodName, sipStatsExtMethodName,
sipStatsRetryExtMethodName. sipStatsRetryExtMethodName.
o sipCommonStatusCodeNotifEmitMode default value changed to * sipCommonStatusCodeNotifEmitMode default value changed to
'triggered'. 'triggered'.
o sipStatusCodeThreshExceededNotif was replaced by two * sipStatusCodeThreshExceededNotif was replaced by two
notifications: sipStatusCodeThreshExceededOutNotif & notifications: sipStatusCodeThreshExceededOutNotif &
sipStatusCodeThreshExceededInNotif. sipStatusCodeThreshExceededInNotif.
o Re-arranged the enumerated value of sipServiceOperStatus; making * Re-arranged the enumerated value of sipServiceOperStatus;
'unknown' the first value. Added some words to the DESCRIPTION making 'unknown' the first value. Added some words to the
of that object stating the values are not based on anything in DESCRIPTION of that object stating the values are not based on
the SIP standard. anything in the SIP standard.
o Clarified rules for capitalization of sipExtMethodName.
o All counters in the MIB are consistent with respect to * Clarified rules for capitalization of sipExtMethodName.
resetting to zero. No counters can be reset to zero.
Entries in sipStatusCodesTable can simply be created or
destroyed - no ability to set to 'notInService' where there
was the question/possibility of resetting the counters to zero.
sipStatsExtMethodTable no longer has it√∆s own RowStatus object,
so it too can no longer be set to 'notInService∆ where there
was the question/possibility of resetting the counters to zero.
sipStatsExtMethodTable rows are augmentations of * All counters in the MIB are consistent with respect to
resetting to zero. No counters can be reset to zero. Entries
in sipStatusCodesTable can simply be created or destroyed - no
ability to set to 'notInService' where there was the question/
possibility of resetting the counters to zero.
sipStatsExtMethodTable no longer has it»ňs own RowStatus
object, so it too can no longer be set to 'notInServiceň where
there was the question/possibility of resetting the counters to
zero. sipStatsExtMethodTable rows are augmentations of
sipExtMethodSupportedEntry. sipExtMethodSupportedEntry.
o OBJECT refinement for sipStatusCodeRowStatus added to compliance. * OBJECT refinement for sipStatusCodeRowStatus added to
compliance.
o Clarified the relationship between * Clarified the relationship between
sipCommonStatusCodeNotifEmitMode and sipCommonStatusCodeNotifSend. sipCommonStatusCodeNotifEmitMode and
sipCommonStatusCodeNotifSend.
o Explained the existence of sipNotifApplIndex object better. * Explained the existence of sipNotifApplIndex object better.
o sipCfgExpiresStatusCodeValue syntax changed from INTEGER to * sipCfgExpiresStatusCodeValue syntax changed from INTEGER to
Unsigned32. Unsigned32.
o sipEntityType object added to sipCommonCfgTable. * sipEntityType object added to sipCommonCfgTable.
o All accessible-for-notify objects are moved into * All accessible-for-notify objects are moved into
sipCommonNotifObjects group. OIDs for actual notifications sipCommonNotifObjects group. OIDs for actual notifications are
are re-assigned as a result. re-assigned as a result.
o sipNotifSequenceNumber accessible-for-notify object added as a * sipNotifSequenceNumber accessible-for-notify object added as a
way for managers to gain insight into possible missed way for managers to gain insight into possible missed
notifications. It is bound to each notification defined in notifications. It is bound to each notification defined in the
the MIB. MIB.
o New notifications related to SIP service operational status are * New notifications related to SIP service operational status are
added: sipServiceColdStart, sipServiceWarmStart, & added: sipServiceColdStart, sipServiceWarmStart, &
sipServiceLastChanged. sipServiceLastChanged.
o New object sipServiceNotifEnable added to control the new SIP * New object sipServiceNotifEnable added to control the new SIP
related notifications. related notifications.
o Minor object descriptor changes: * Minor object descriptor changes: sipStatusCodesTable renamed to
sipStatusCodesTable renamed to sipStatusCodeClassesTable sipStatusCodeClassesTable SipStatusCodesEntry renamed to
SipStatusCodesEntry renamed to SipStatusCodeClassesEntry SipStatusCodeClassesEntry sipStatusCodesEntry renamed to
sipStatusCodesEntry renamed to sipStatusCodeClassesEntry sipStatusCodeClassesEntry sipCommonStatusCodeTable renamed to
sipCommonStatusCodeTable renamed to sipStatusCodesTable sipStatusCodesTable SipCommonStatusCodeEntry renamed to
SipCommonStatusCodeEntry renamed to SipStatusCodesEntry SipStatusCodesEntry sipCommonStatusCodeEntry renamed to
sipCommonStatusCodeEntry renamed to sipStatusCodesEntry sipStatusCodesEntry sipCommonStatusCodeValue renamed to
sipCommonStatusCodeValue renamed to sipStatusCodeValue sipStatusCodeValue sipCommonStatusCodeIns renamed to
sipCommonStatusCodeIns renamed to sipStatusCodeIns sipStatusCodeIns sipCommonStatusCodeOuts renamed to
sipCommonStatusCodeOuts renamed to sipStatusCodeOuts sipStatusCodeOuts sipCommonStatusCodeStatus renamed to
sipCommonStatusCodeStatus renamed to sipStatusCodeRowStatus sipStatusCodeRowStatus sipCommonStatusCodeNotifTable renaemd to
sipCommonStatusCodeNotifTable renaemd to sipStatusCodeNotifTable sipStatusCodeNotifTable SipCommonStatusCodeNotifEntry renamed
SipCommonStatusCodeNotifEntry renamed to SipStatusCodeNotifEntry to SipStatusCodeNotifEntry sipCommonStatusCodeNotifEntry
sipCommonStatusCodeNotifEntry renamed to sipStatusCodeNotifEntry renamed to sipStatusCodeNotifEntry sipCommonStatusCodeNotifSend
sipCommonStatusCodeNotifSend renamed to sipStatusCodeNotifSend renamed to sipStatusCodeNotifSend
sipCommonStatusCodeNotifEmitMode renamed to sipCommonStatusCodeNotifEmitMode renamed to
sipStatusCodeNotifEmitMode sipStatusCodeNotifEmitMode sipCommonStatusCodeNotifThresh
sipCommonStatusCodeNotifThresh renamed to sipStatusCodeNotifThresh renamed to sipStatusCodeNotifThresh
sipCommonStatusCodeNotifInterval renamed to sipCommonStatusCodeNotifInterval renamed to
sipStatusCodeNotifInterval sipStatusCodeNotifInterval
o Removed all INFO method specific objects: * Removed all INFO method specific objects: sipCfgRetryInfo,
sipCfgRetryInfo, sipStatsInfoIns, sipStatsInfoOuts, & sipStatsInfoIns, sipStatsInfoOuts, & sipStatsRetryInfos
sipStatsRetryInfos
o Clarifying words added to sipStatusCodeNotifTable * Clarifying words added to sipStatusCodeNotifTable DESCRIPTION
DESCRIPTION to explain why it's a seperate table from to explain why it's a seperate table from sipStatusCodesTable.
sipStatusCodesTable.
SIP-SERVER-MIB o SIP-SERVER-MIB
o Deleted objects related to 'action∆ parameter. * Deleted objects related to 'action' parameter. RFC 3261 section
RFC 3261 section 10.2 deprecates the 'action∆ parameter 10.2 deprecates the 'action' parameter deleted 3 objects:
=> deleted 3 objects: sipServerContactDfltAction, sipServerRespectUAAction,
- sipServerContactDfltAction, sipServerRespectUAAction sipContactAction.
- sipContactAction.
o Deleted pgp-related objects. * Deleted pgp-related objects. RFC 3261 section 23 deprecates use
RFC 3261 section 23 deprecates use of pgp of pgp deleted 3 objects: sipProxyAuthPgpAlgorithm,
=> deleted 3 objects: sipPgpPrivateKey, sipPgpVersion.
- sipProxyAuthPgpAlgorithm, sipPgpPrivateKey, sipPgpVersion.
o Removed sipProxyStateTimeout object. * Removed sipProxyStateTimeout object. Timers G and timer H have
Timers G and timer H have been introduced in RFC 3261 for this been introduced in RFC 3261 for this purpose (see RFC 3261
purpose (see RFC 3261 section 17.2.1). section 17.2.1).
o Updated description clause of sipProxyStatefulness. * Updated description clause of sipProxyStatefulness. The 3
The 3 definitions of stateless/statefulness now match the text definitions of stateless/statefulness now match the text in RFC
in RFC 3261. 3261.
o Changed DEFVAL for object sipProxyProvideAlternatives. * Changed DEFVAL for object sipProxyProvideAlternatives. Changed
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 updated responses SHOULD contain a contact header & 303 MAY... and
REFERENCE clause to "RFC 3261 Sections 13.2.2.2 and 16.5". updated REFERENCE clause to "RFC 3261 Sections 13.2.2.2 and
16.5".
o Removed basic authentication value from sipProxyAuthMethod object * Removed basic authentication value from sipProxyAuthMethod
Per section 22 of rfc 3261, deprecated. object Per section 22 of rfc 3261, deprecated.
o Changed SYNTAX of sipProxyNonceLifeTime from Integer32 to * Changed SYNTAX of sipProxyNonceLifeTime from Integer32 to
Unsigned32. Unsigned32.
o Updated description clause of sipRegDfltRegActiveInterval * Updated description clause of sipRegDfltRegActiveInterval Per
Per RFC 3261 Section 10.2. RFC 3261 Section 10.2.
SIP-UA-MIB o SIP-UA-MIB
o OBJECT refinement for sipUACfgSipServerStatus added to compliance. * OBJECT refinement for sipUACfgSipServerStatus added to
compliance.
o Changed the object descriptors of sipUACfgSipServerAddrIndex to * Changed the object descriptors of sipUACfgSipServerAddrIndex to
sipUACfgSipServerIndex, and sipUACfgSipServerAddrStatus to sipUACfgSipServerIndex, and sipUACfgSipServerAddrStatus to
sipUACfgSipServerStatus. sipUACfgSipServerStatus.
o Changes from draft-ietf-sip-mib-04 Changes from draft-ietf-sip-mib-04
Started realignment with SIP RFC3261. o Started realignment with SIP RFC3261.
o Changes from draft-ietf-sip-mib-03 Changes from draft-ietf-sip-mib-03
These are the specific draft-ietf-sip-mib-04 changes to the MIB o Front paper/Back paper and General changes
modules based on what they looked like for draft-ietf-sip-mib-03.
Front paper/Back paper * Rewrote section on Network Services MIB
o Rewrote parts of section 4.2
o Fixed minor editorial nits
SIP-COMMON-MIB * Fixed minor editorial nits
o CONTACT-INFO "SIP MIB email" changed to sip@ietf.org o SIP-COMMON-MIB
o sipInviteTimeout was removed from the MIB. See below regarding * CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
* 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.
o sipCommonCfgExpires OID subtree added. Per method Expires * sipCommonCfgExpires OID subtree added. Per method Expires
configuration objects were added there. configuration objects were added there. This new high-level OID
This new high-level OID was placed under the existing was placed under the existing sipCommonCfgRetry OID and
sipCommonCfgRetry OID and therefore, caused the OIDs for the therefore, caused the OIDs for the subsequent groups to change
subsequent groups to change (incrementing by one). (incrementing by one).
o Objects from tables under sipCommonCfgExpires were added to a new * Objects from tables under sipCommonCfgExpires were added to a
OBJECT-GROUP sipCommonConfigExpiresGroup, and that group was listed new OBJECT-GROUP sipCommonConfigExpiresGroup, and that group
as optional in sipCommonCompliance. was listed as optional in sipCommonCompliance.
o Minor DESCRIPTION change for sipCommonCfgEntry. No behavior * Minor DESCRIPTION change for sipCommonCfgEntry. No behavior
change. change.
o sipServiceOperStatus SYNTAX changed. * sipServiceOperStatus SYNTAX changed. New values added:
New values added: congested & quiescing congested & quiescing Old values removed: halted The order of
Old values removed: halted the enumeration was altered as well.
The order of the enumeration was altered as well.
o sipServiceAdminStatus SYNTAX changed. * sipServiceAdminStatus SYNTAX changed. New values added: noop,
New values added: noop, up, down, quieseSessions, and up, down, quieseSessions, and quieseApplications Old values
quieseApplications removed: shutdown, restart, stop, rts. These changes were made
Old values removed: shutdown, restart, stop, rts. based on comments from last call reviewer and general known
These changes were made based on comments from last call reviewer ambiguities in the previous design of the object.
and general known ambiguities in the previous design of the object.
o Clarifying changes to the DESCRIPTION of sipServiceStartTime. * Clarifying changes to the DESCRIPTION of sipServiceStartTime.
o Clarifying changes to the DESCRIPTION of sipOrganization. * Clarifying changes to the DESCRIPTION of sipServiceStartTime.
o Clarification of behavior for sipPortStatus while row is * Clarification of behavior for sipPortStatus while row is
'active'. 'active'
o Clarifying changes to the DESCRIPTION of sipUriSupportedTable * Clarifying changes to the DESCRIPTION of sipUriSupportedTable.
o Clarifying changes to the DESCRIPTIONs of sipFtrSupportedTable, * Clarifying changes to the DESCRIPTIONs of sipFtrSupportedTable,
sipFtrSupportedEntry, and sipFtrSupported. sipFtrSupportedEntry, and sipFtrSupported. Specifically, IETF
Specifically, IETF standard features and non-standard features are standard features and non-standard features are now represented
now represented by this table. Only non-standard features were by this table. Only non-standard features were mentioned in
mentioned in prior revisions of the draft. prior revisions of the draft.
o Reference to usage of RFC 2788 applIndex moved from * Reference to usage of RFC 2788 applIndex moved from
sipCommonCfgTimerExtMethodTable to sipCommonCfgTimerExtMethodTable to
sipCommonCfgTimerExtMethodEntry. sipCommonCfgTimerExtMethodEntry. This was the convention for
This was the convention for other table/entry definitions in other table/entry definitions in the MIB, so these objects were
the MIB, so these objects were previously unconventional. previously unconventional.
o DEFVAL removed from sipCfgTimerExtMethodTimer. The generic nature * DEFVAL removed from sipCfgTimerExtMethodTimer. The generic
of the "extension" object does not lend itself to being able to nature of the "extension" object does not lend itself to being
specify a particular default value. able to specify a particular default value.
o Since the removal of the DEFVAL clause from * Since the removal of the DEFVAL clause from
sipCfgTimerExtMethodTimer, sipCfgTimerExtMethodTimer, a value for that object must be
a value for that object must be specified when creating a specified when creating a sipCommonCfgTimerExtMethodEntry. The
sipCommonCfgTimerExtMethodEntry. The description of description of sipCfgTimerExtMethodStatus was updated to
sipCfgTimerExtMethodStatus was updated to reflect this. reflect this.
o 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.
o DEFVAL removed from sipCfgRetryExtMethodRetry. The generic nature * DEFVAL removed from sipCfgRetryExtMethodRetry. The generic
of the "extension" object does not lend itself to being able to nature of the "extension" object does not lend itself to being
specify a particular default value. able to specify a particular default value.
o Since the removal of the DEFVAL clause from * Since the removal of the DEFVAL clause from
sipCfgRetryExtMethodRetry, sipCfgRetryExtMethodRetry, a value for that object must be
a value for that object must be specified when creating a specified when creating a sipCommonCfgRetryExtMethodEntry. The
sipCommonCfgRetryExtMethodEntry. The description of description of sipCfgRetryExtMethodStatus was updated to
sipCfgRetryExtMethodStatus was updated to reflect this. reflect this.
o Clarifying changes to the DESCRIPTION of * Clarifying changes to the DESCRIPTION of
sipSummaryTotalTransactions. sipSummaryTotalTransactions. Specifically, the object is not
Specifically, the object is not applicable to stateless SIP proxy applicable to stateless SIP proxy servers and the object should
servers and the object should always return a value of 0 if always return a value of 0 if implemented by a stateless proxy.
implemented by a stateless proxy.
o Clarifying changes to the DESCRIPTION of sipStatsExtMethodStatus. * Clarifying changes to the DESCRIPTION of
sipStatsExtMethodStatus.
o 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.
o Text referring specifically to Redirect Server in * Text referring specifically to Redirect Server in
sipStatsRedirClassIns and sipStatsRedirClassOuts was removed. sipStatsRedirClassIns and sipStatsRedirClassOuts was removed.
o Text defining protocol behavior in sipStatsServerFailClassIns, * Text defining protocol behavior in sipStatsServerFailClassIns,
sipStatsServerFailClassOuts, sipStatsGlobalFailClassIns, and sipStatsServerFailClassOuts, sipStatsGlobalFailClassIns, and
sipStatsGlobalFailClassOuts was removed. sipStatsGlobalFailClassOuts was removed.
o 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.
o sipStatusCodeNotifTo, sipStatusCodeNotifFrom, * sipStatusCodeNotifTo, sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId, sipStatusCodeNotifCallId, and sipStatusCodeNotifCSeq all had
and sipStatusCodeNotifCSeq all had clarifying changes to their clarifying changes to their DESCRIPTIONs. Specifically, the
DESCRIPTIONs. Specifically, the header name will be part of the header name will be part of the object value and example values
object value and example values were given. were given.
o 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.
o Minor gramatical change to the DESCRIPTION of * Minor gramatical change to the DESCRIPTION of
sipCurrentTransEntry. sipCurrentTransEntry.
o 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.
o Clarifying changes to the DESCRIPTION of sipTransState. * Clarifying changes to the DESCRIPTION of sipTransState.
Specifically, noting that not all values of the object Specifically, noting that not all values of the object are
are applicable to all transaction types. applicable to all transaction types.
o sipTransTo, sipTransFrom, sipTransCallId, and sipTransCSeq * sipTransTo, sipTransFrom, sipTransCallId, and sipTransCSeq all
all had clarifying changes to their DESCRIPTIONs. had clarifying changes to their DESCRIPTIONs. Specifically, the
Specifically, the header name will be part of the object header name will be part of the object value and example values
value and example values were given. were given.
o Minor gramatical change to the DESCRIPTION of sipOtherStatsEntry. * Minor gramatical change to the DESCRIPTION of
sipOtherStatsEntry.
o sipCommonStatusCodeIns and sipCommonStatusCodeOuts objects were * sipCommonStatusCodeIns and sipCommonStatusCodeOuts objects were
added to the varbind of sipStatusCodeNotif. added to the varbind of sipStatusCodeNotif.
o Appropriate changes were made to sipCommonStatsGroup OBJECT-GROUP * Appropriate changes were made to sipCommonStatsGroup
based on objects being added and/or removed from the MIB. OBJECT-GROUP based on objects being added and/or removed from
the MIB.
SIP-SERVER-MIB o SIP-SERVER-MIB
o CONTACT-INFO "SIP MIB email" changed to sip@ietf.org * CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
o 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 requests." was removed from where a Redirect Server is defined
defined in the MIB's DESCRIPTION. in the MIB's DESCRIPTION.
o sipServerMIBNotifs OID removed. No notifications were * sipServerMIBNotifs OID removed. No notifications were ever
ever defined under this subtree. defined under this subtree.
o Clarifying text added to all of the Table DESCRIPTIONS * Clarifying text added to all of the Table DESCRIPTIONS stating
stating that the value of applIndex used in this MIB that the value of applIndex used in this MIB corresponds to the
corresponds to the value of applIndex used in the value of applIndex used in the SIP-COMMON-MIB.
SIP-COMMON-MIB.
o Clarifying changes to the DESCRIPTION of sipProxyStatefulness. * Clarifying changes to the DESCRIPTION of sipProxyStatefulness.
o sipContactPreference SYNTAX changed from OCTET STRING to * sipContactPreference SYNTAX changed from OCTET STRING to
SnmpAdminString. SnmpAdminString.
SIP-UA-MIB o SIP-UA-MIB
o CONTACT-INFO "SIP MIB email" changed to sip@ietf.org * CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
o sipUAMIBNotifs OID removed. No notifications were * sipUAMIBNotifs OID removed. No notifications were ever defined
ever defined under this subtree. under this subtree.
o sipUAStats OID removed. No notifications were * sipUAStats OID removed. No notifications were ever defined
ever defined under this subtree. under this subtree.
o Clarifying text added to all of the Table DESCRIPTIONS * Clarifying text added to all of the Table DESCRIPTIONS stating
stating that the value of applIndex used in this MIB that the value of applIndex used in this MIB corresponds to the
corresponds to the value of applIndex used in the value of applIndex used in the SIP-COMMON-MIB.
SIP-COMMON-MIB.
SIP-TC o SIP-TC
o CONTACT-INFO "SIP MIB email" changed to sip@ietf.org * CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
o Changes from draft-ietf-sip-mib-02 Changes from draft-ietf-sip-mib-02
The following changes were made based on review comments to the o General
previous version of the draft.
In general * Eliminated the SIP-MIB-SMI modules. Each MIB module will now
o Eliminated the SIP-MIB-SMI modules. Each MIB module will now
get it's own IANA OID. get it's own IANA OID.
o Top-level OID subtrees restructured in each MIB.
o General cleanup/removal of "placeholder" OID subtrees
for object groups and notifications that never materialized.
Regarding SIP-COMMON-MIB * Top-level OID subtrees restructured in each MIB.
o Removed sipCfgInitialTimerAck.
o Removed sipCfgRetryAck.
o Removed sipStatsRetryAcks.
o sipCommonStatsRetryExtMethodEntry was missing its INDEX * General cleanup/removal of "placeholder" OID subtrees for
clause. object groups and notifications that never materialized.
o sipNumUnsupportedUris OID was "5" when it was the
only object in the table. OID is now "1". o SIP-COMMON-MIB
o High-level OID structure of the MIB is now sequential.
o Incorrect object descriptor for sipCfgInitialTimerRsp * Removed sipCfgInitialTimerAck.
* Removed sipCfgRetryAck.
* Removed sipStatsRetryAcks.
* sipCommonStatsRetryExtMethodEntry was missing its INDEX clause.
* sipNumUnsupportedUris OID was "5" when it was the only object
in the table. OID is now "1".
* High-level OID structure of the MIB is now sequential.
* Incorrect object descriptor for sipCfgInitialTimerRsp
inconsistent with reference in compliance section. inconsistent with reference in compliance section.
o Inconsistencies between sipCommonStatsRetryGroup definition
and SipCommonStatsRetryEntry OBJECT-TYPE corrected. * Inconsistencies between sipCommonStatsRetryGroup definition and
o sipNotifApplIndex was not in any object group in the SipCommonStatsRetryEntry OBJECT-TYPE corrected.
* sipNotifApplIndex was not in any object group in the
conformance section. conformance section.
Regarding SIP-SERVER-MIB o SIP-SERVER-MIB
o Removed sipInformationTryingInterval.
o Removed sipRxProxyAuthTable. * Removed sipInformationTryingInterval.
o Removed sipRegRespHasContacts.
o Removed sipRegContactDfltExpiryDate. * Removed sipRxProxyAuthTable.
o Removed sipRegContactDfltExpiryDuration.
o Removed sipUserPassword. * Removed sipRegRespHasContacts.
o sipRequestMaxExpires DESCRIPTION changed to no
longer specifically mention 400 response. * Removed sipRegContactDfltExpiryDate.
o sipProxyStateful object descriptor changed to
sipProxyStatefullness and the SYNTAX changed * Removed sipRegContactDfltExpiryDuration.
from TruthValue to an enumerated INTEGER.
o sipProxyStateTimeout DESCRIPTION changed to now reflect only * Removed sipUserPassword.
* sipRequestMaxExpires DESCRIPTION changed to no longer
specifically mention 400 response.
* sipProxyStateful object descriptor changed to
sipProxyStatefullness and the SYNTAX changed from TruthValue to
an enumerated INTEGER.
* sipProxyStateTimeout DESCRIPTION changed to now reflect only
INVITE. INVITE.
o Gauge32 was not being IMPORTed.
o sipServerContactDfltAction showed up in conformance
and other object descriptions in an older form.
o sipServerHost replaced with InetAddressType/InetAddress
object pair (sipServerHostAddrType & sipServerHostAddr).
Regarding SIP-UA-MIB * Gauge32 was not being IMPORTed.
o IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex.
o sipUACfgSipServerEntry was referencing the wrong
auxilliary object and listing that object in the conformance
section.
o sipUACfgSipServerEntry listed sipUACfgSipServerStatus
when it should have been listing sipUACfgSipServerAddrStatus.
o SIP-UA-MIB IMPORTed Counter32, but never used it.
Removed the IMPORT of Counter32.
7. Security Considerations * sipServerContactDfltAction showed up in conformance and other
object descriptions in an older form.
* sipServerHost replaced with InetAddressType/InetAddress object
pair (sipServerHostAddrType & sipServerHostAddr).
o SIP-UA-MIB
* IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex.
* sipUACfgSipServerEntry was referencing the wrong auxilliary
object and listing that object in the conformance section.
* sipUACfgSipServerEntry listed sipUACfgSipServerStatus when it
should have been listing sipUACfgSipServerAddrStatus.
* SIP-UA-MIB IMPORTed Counter32, but never used it. Removed the
IMPORT of Counter32.
9. 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 These are the tables and objects and their sensitivity/vulnerability:
sensitivity/vulnerability:
o SIP-COMMON-MIB o SIP-COMMON-MIB
The following read-write object is used to control the overall SIP The following read-write object is used to control the overall
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 control The following read-write and read-create objects are used to
the behavior of the SIP protocol as exhibited by a SIP entity: control the behavior of the SIP protocol as exhibited by a SIP
sipOrganization, entity:
sipRequestUriHostMatching,
sipCfgTimerA, sipOrganization, sipRequestUriHostMatching, sipCfgTimerA,
sipCfgTimerB, sipCfgTimerB, sipCfgTimerC, sipCfgTimerD, sipCfgTimerE,
sipCfgTimerC, sipCfgTimerF, sipCfgTimerG, sipCfgTimerH, sipCfgTimerI,
sipCfgTimerD, sipCfgTimerJ, sipCfgTimerK, sipCfgTimerT1, sipCfgTimerT2,
sipCfgTimerE, sipCfgTimerT4, sipCfgTimerExtMethodTimer, sipCfgRetryInvite,
sipCfgTimerF, sipCfgRetryBye, sipCfgRetryCancel, sipCfgRetryRegister,
sipCfgTimerG, sipCfgRetryOptions, sipCfgRetryFinalResponse,
sipCfgTimerH, sipCfgRetryNonFinalResponse, sipCfgRetryExtMethodRetry,
sipCfgTimerI, sipCfgExpiresInvite, sipCfgExpiresRegister,
sipCfgTimerJ, sipCfgExpiresHeaderMethod, sipCfgExpiresHeaderValue,
sipCfgTimerK, sipCfgExpiresStatusCodeStatus
sipCfgTimerT1, If these objects are SET maliciously, it may result in
sipCfgTimerT2, incorrect or unwanted protocol operation.
sipCfgTimerT4,
sipCfgTimerExtMethodTimer, The following read-create object is used to configure the
sipCfgRetryInvite, status code statistics that will be monitored by the SIP
sipCfgRetryBye, entity:
sipCfgRetryCancel,
sipCfgRetryRegister,
sipCfgRetryOptions,
sipCfgRetryFinalResponse,
sipCfgRetryNonFinalResponse,
sipCfgRetryExtMethodRetry,
sipCfgExpiresInvite,
sipCfgExpiresRegister,
sipCfgExpiresHeaderMethod,
sipCfgExpiresHeaderValue,
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 status
code statistics that will be monitored by the SIP 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 accumulating allocation of resources in a system for the purpose of
and maintaining statistics. accumulating and maintaining statistics.
The following read-write objects are used to configure the behavior The following read-write objects are used to configure the
of certain SNMP notifications potentially generated by a SIP entity: behavior of certain SNMP notifications potentially generated by
sipStatusCodeNotifSend, a SIP entity:
sipStatusCodeNotifEmitMode,
sipStatusCodeNotifThresh, sipStatusCodeNotifSend, sipStatusCodeNotifEmitMode,
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 Internet The following read-create objects are used to configure the
address of SIP servers a SIP User Agent will use to proxy/redirect Internet address of SIP servers a SIP User Agent will use to
SIP calls: proxy/redirect SIP calls:
sipUACfgSipServerAddrType,
sipUACfgSipServerAddr, sipUACfgSipServerAddrType, sipUACfgSipServerAddr,
sipUACfgSipServerStatus. 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 agent operation, or a failure to obtain SIP services from the user
prospective or even theft of service. In particular, setting the agent prospective or even theft of service. In particular,
SipUACfgSipServerStatus object instance to the √śdestroy√∆ value may setting the SipUACfgSipServerStatus object instance to the
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 Servers The following read-create objects are managed by Registrar
and contain sensitive or private information about the address of Servers and contain sensitive or private information about the
record of registered users. address of record of registered users.
sipUserUri
sipUserTableRowStatus sipUserUri & sipUserTableRowStatus
The sensitivity of these objects depends on the role that Registrar The sensitivity of these objects depends on the role that
Servers play in the SIP service. In some cases, these objects, if Registrar Servers play in the SIP service. In some cases, these
SET maliciously, may allow unregistered users to steal service, or objects, if SET maliciously, may allow unregistered users to
may prevent registered users from accessing the SIP service. steal service, or may prevent registered users from accessing
the SIP service.
The following read-write objects, if SET maliciously will have
an immediate serious impact on the service:
sipServerHostAddrType & sipServerHostAddr
These objects specify the host part of the URI for the server
providing the SIP resource and it is widely used by SIP servers
in numerous header lines and field. For e.g., the host address
may be used with the Request-URI to check if the server is the
one resolved by the Request-URI, therefore determining whether
to process or forward the request in the case of outbound
proxies, or, as an another common example, it is used by Proxy
Servers acting as strict routers to rewrite the Request-URI.
Setting these objects with improper values may result in
serious service interference or failure.
The following read-write objects, if SET maliciously will have an
immediate serious impact on the service:
sipServerHostAddrType & sipServerHostAddr -
- these objects specify
the host part of the URI for the server providing the SIP resource
and it is widely used by SIP servers in numerous header lines and
field. For e.g., the host address may be used with the Request-URI
to check if the server is the one resolved by the Request-URI,
therefore determining whether to process or forward the request in
the case of outbound proxies, or, as an another common example, it
is used by Proxy Servers acting as strict routers to rewrite the
Request-URI. Setting these objects with improper values may result
in serious service interference or failure.
sipRequestMaxExpires and sipRegMaxContactExpiryDuration: if set sipRequestMaxExpires and sipRegMaxContactExpiryDuration: if set
to a zero value and either SIP requests contain an Expires header or to a zero value and either SIP requests contain an Expires
Contact header contain an expires parameter, may cause the server to header or Contact header contain an expires parameter, may
never create bindings associated with an address of record (case of cause the server to never create bindings associated with an
REGISTER request) or may cause server to expire and cancel address of record (case of REGISTER request) or may cause
invitations (case of INVITE request). server to expire and cancel invitations (case of INVITE
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 may how transaction states are being handled the Proxy Server and
result in call feature or service changes. may result in call feature or service changes.
SipProxyAuthMethod: this object specifies at a maximum what the
authentication methods that may be used by a server. If this object sipProxyAuthMethod: this object specifies at a maximum what the
is SET maliciously, it may alter how the level of security used by authentication methods that may be used by a server. If this
the server to generate requests and may compromise the network object is SET maliciously, it may alter how the level of
security policies. security used by the server to generate requests and may
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 clients HTTP Digest authentication method is used, it may result in
being unable to authenticate and ultimately, in the server denying clients being unable to authenticate and ultimately, in the
service. server denying service.
The remaining read-write objects, if SET maliciously may have some The remaining read-write objects, if SET maliciously may have
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 SipProxySendsCancel: this is a configuration object defining
cancellation of outstanding branch requests. If this object was set how a certain class of proxy servers (forking proxies) handle
to true and is maliciously changed to false, the impact is 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 considered moderate: the forking proxy may simply terminate the
outstanding branches at a later phase, either when a transaction outstanding branches at a later phase, either when a
timer expires or when subsequent messages arrive from the transaction timer expires or when subsequent messages arrive
outstanding branches. 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 in additional SIP traffic to cross the proxy server and may result
message avalanches. in message avalanches.
The threats posed by the following read-write objects can either be
mitigated by other configuration settings like read-only objects or The threats posed by the following read-write objects can
they are considered to cause additional server operations without either be mitigated by other configuration settings like
immediate impact on the server like additional location look-ups read-only objects or they are considered to cause additional
(sipProxyProvideAlternatives), additional traffic due to expiration server operations without immediate impact on the server like
of nonce (sipProxyNonceLifeTime). additional location look-ups (sipProxyProvideAlternatives),
sipProxyForwardAll1xx additional traffic due to expiration of nonce
sipProxyRecursion (sipProxyNonceLifeTime).
sipProxyProvideAlternatives
sipProxyNonceLifeTime sipProxyForwardAll1xx, sipProxyRecursion,
sipProxyProvideAlternatives sipProxyNonceLifeTime, and
sipRegDfltRegActiveInterval sipRegDfltRegActiveInterval
Some of the readable objects in the MIB modules (i.e., objects with Some of the readable objects in the MIB modules (i.e., objects
a MAX-ACCESS other than not-accessible) may be considered sensitive with a MAX-ACCESS other than not-accessible) may be considered
or vulnerable in some network environments. It is thus important to sensitive or vulnerable in some network environments. It is
control even GET and/or NOTIFY access to these objects and possibly thus important to control even GET and/or NOTIFY access to
to even encrypt the values of these objects when sending them over these objects and possibly to even encrypt the values of these
the network via SNMP. objects when sending them over the network via SNMP.
o SIP-SERVER-MIB
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, SipContactDisplayName, SipContactURI, and
SipContactLastUpdated. SipContactLastUpdated.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security. Even
Even if the network itself is secure (for example by using IPSec), if the network itself is secure (for example by using IPSec), even
even then, there is no control as to who on the secure network is then, there is no control as to who on the secure network is allowed
allowed to access and GET/SET (read/change/create/delete) the to access and GET/SET (read/change/create/delete) the objects in this
objects in this MIB module. MIB module.
It is RECOMMENDED that implementers consider the security features It is RECOMMENDED that implementers consider the security features as
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.
8. Intellectual Property 10. Contributor Acknowledgments
We wish to thank the members of the IETF SIP & SIPPING working groups
& the SIP-MIB Design team for their comments and suggestions.
Detailed comments were provided by Tom Taylor, Kavitha Patchayappan
and Dan Romascanu.
Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[2] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction
and Applicability Statements for Internet-Standard Management
Framework", RFC 3410, December 2002.
[3] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
[4] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
[5] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999.
[6] Freed, N. and S. Kille, "Network Services Monitoring MIB", RFC
2788, March 2000.
[7] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:
Session Initiation Protocol", RFC 3261, June 2002.
[8] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder,
"Textual Conventions for Internet Network Addresses", RFC 3291,
May 2002.
Informational References
[9] Hoffman, P., Masinter, L. and J. Zawinski, "The mailto URL
scheme", RFC 2368, July 1998.
[10] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396, August
1998.
Authors' Addresses
Kevin Lingle
Cisco Systems, Inc.
7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709
US
Phone: +1 919 392 2029
EMail: klingle@cisco.com
Joon Maeng
ipDialog, Inc.
7701 N. Lamar Blvd., Suite 304
Austin, TX 78752-1023
US
Phone: +1 512 371 1770
EMail: jmaeng@ipdialog.com
Jean-Francois Mule
CableLabs
400 Centennial Parkway
Louisville, CO 80027
US
Phone: +1 303 661 9100
EMail: jfm@cablelabs.com
Dave Walker
SS8 Networks, Inc.
495 March Road
Kanata, ON K2K 3G1
CA
Phone: +1 613 592 2100
EMail: drwalker@ss8.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances claims of rights made available for publication and any assurances of
of licenses to be made available, or the result of an attempt made licenses to be made available, or the result of an attempt made to
to obtain a general license or permission for the use of such obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification proprietary rights by implementors or users of this specification can
can be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
9. Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph are
are included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
10. Normative References Acknowledgment
[RFC2026] Bradner, S., "The Internet Standards Process -
- Revision
3", BCP 9, RFC 2026, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[RFC2788] Freed, N. and S. Kille, "Network Services Monitor MIB",
RFC 2788, March 2000.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M. and E. Schooler,
"SIP: Session Initiation Protocol", RFC 3261, June 2002.
[RFC3291] Daniele, M., Haberman, B., Routhier, S. and J.,
Schoenwaelder "Textual Conventions for Internet Network
Addresses", RFC 3291, May 2002.
11. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC3291] Daniele, M., Haberman, B., Routhier, S., Schoenwaelder,
J., "Textual Conventions for Internet Network Addresses",
RFC 3291, May 2002.
[RFC2368] Hoffman, P., Masinter, L., Zawinski, J., "The mailto URL
scheme", RFC 2368, July 1998.
[RFC2396] Berners-Lee, T., Fielding, R., Masinter, L., "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396,
August 1998.
12. Acknowledgments
We wish to thank the members of the IETF SIP & SIPPING working groups &
the SIP-MIB Design team for their comments and suggestions. Detailed
comments were provided by Tom Taylor, Kavitha Patchayappan and Dan
Romascanu.
13. Author's Addresses
Kevin Lingle
Cisco Systems, Inc.
7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709
USA
email: klingle@cisco.com
phone: +1 919 392 2029
Joon Maeng
ipDialog, Inc.
7701 N. Lamar Blvd., Suite 304
Austin, TX 78752-1023
USA
email: jmaeng@ipdialog.com
phone: +1 512 371 1770
Jean-Francois Mule√∆
CableLabs
400 Centennial Parkway
Louisville, CO 80027
USA
email: jfm@cablelabs.com
mibs@cablelabs.com
phone: +1 303 661 9100
Dave Walker Funding for the RFC Editor function is currently provided by the
SS8 Networks, Inc. Internet Society.
495 March Road
Kanata, ON K2K 3G1
Canada
email: drwalker@ss8.com
phone: +1 613 592 2100
 End of changes. 

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