< draft-ietf-sip-mib-11.txt   draft-ietf-sip-mib-12.txt >
SIP Working Group K. Lingle SIP Working Group K. Lingle
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: November 18, 2006 J-F. Mule Intended status: Standards Track J-F. Mule
CableLabs Expires: March 19, 2007 CableLabs
J. Maeng J. Maeng
D. Walker D. Walker
May 17, 2006 September 15, 2006
Management Information Base for the Session Initiation Protocol (SIP) Management Information Base for the Session Initiation Protocol (SIP)
draft-ietf-sip-mib-11.txt draft-ietf-sip-mib-12.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 18, 2006. This Internet-Draft will expire on March 19, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that are used to In particular, it describes a set of managed objects that are used to
skipping to change at page 2, line 18 skipping to change at page 2, line 18
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . . 3 3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Structure of the SIP MIB . . . . . . . . . . . . . . . . . . . 4 5. Structure of the SIP MIB . . . . . . . . . . . . . . . . . . . 4
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6
5.2. Relationship to the Network Services MIB . . . . . . . . . 6 5.2. Relationship to the Network Services MIB . . . . . . . . . 6
5.3. IMPORTed MIB Modules and REFERENCE Clauses . . . . . . . . 10 5.3. IMPORTed MIB Modules and REFERENCE Clauses . . . . . . . . 10
6. Accommodating SIP Extension Methods . . . . . . . . . . . . . 10 6. Accommodating SIP Extension Methods . . . . . . . . . . . . . 10
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. SIP Textual Conventions . . . . . . . . . . . . . . . . . 11 7.1. SIP Textual Conventions . . . . . . . . . . . . . . . . . 11
7.2. SIP Common MIB Module . . . . . . . . . . . . . . . . . . 14 7.2. SIP Common MIB Module . . . . . . . . . . . . . . . . . . 15
7.3. SIP User Agent MIB Module . . . . . . . . . . . . . . . . 53 7.3. SIP User Agent MIB Module . . . . . . . . . . . . . . . . 54
7.4. SIP Server MIB Module (Proxy, Redirect and Registrar 7.4. SIP Server MIB Module (Proxy, Redirect and Registrar
Servers) . . . . . . . . . . . . . . . . . . . . . . . . . 58 Servers) . . . . . . . . . . . . . . . . . . . . . . . . . 58
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 76 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 77
9. Security Considerations . . . . . . . . . . . . . . . . . . . 76 9. Security Considerations . . . . . . . . . . . . . . . . . . . 77
10. Contributor Acknowledgments . . . . . . . . . . . . . . . . . 78 10. Contributor Acknowledgments . . . . . . . . . . . . . . . . . 79
11. Changes from Previous Draft Revisions . . . . . . . . . . . . 78 11. Changes from Previous Draft Revisions . . . . . . . . . . . . 79
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 90 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 93
12.1. Normative References . . . . . . . . . . . . . . . . . . . 90 12.1. Normative References . . . . . . . . . . . . . . . . . . . 93
12.2. Informative References . . . . . . . . . . . . . . . . . . 91 12.2. Informative References . . . . . . . . . . . . . . . . . . 94
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 91 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 94
Intellectual Property and Copyright Statements . . . . . . . . . . 92 Intellectual Property and Copyright Statements . . . . . . . . . . 96
1. Conventions 1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Introduction 2. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
skipping to change at page 4, line 8 skipping to change at page 4, line 8
This MIB provides some managed objects for SIP entities defined in This MIB provides some managed objects for SIP entities defined in
RFC 3261 [RFC3261] - User Agents, and Proxy, Redirect and Registrar RFC 3261 [RFC3261] - User Agents, and Proxy, Redirect and Registrar
servers: it is intended to provide management of the basic SIP servers: it is intended to provide management of the basic SIP
entities. It provides for monitoring of status and protocol entities. It provides for monitoring of status and protocol
statistics, as well as for configuration of SIP entities. statistics, as well as for configuration of SIP entities.
5. Structure of the SIP MIB 5. Structure of the SIP MIB
Four MIB modules are specified: SIP-COMMON-MIB, SIP-SERVER-MIB, SIP- Four MIB modules are specified: SIP-COMMON-MIB, SIP-SERVER-MIB, SIP-
UA-MIB and SIP-TC. SIP-COMMON-MIB contains common MIB objects used UA-MIB and SIP-TC-MIB. SIP-COMMON-MIB contains common MIB objects
in all the SIP entities. SIP-SERVER-MIB contains objects specific to used in all the SIP entities. SIP-SERVER-MIB contains objects
Proxy, Redirect and Registrar servers, and SIP-UA-MIB includes specific to Proxy, Redirect and Registrar servers, and SIP-UA-MIB
objects specific to User Agents. SIP-TC defines the textual includes objects specific to User Agents. SIP-TC-MIB defines the
conventions used throughout MIB modules. textual conventions used throughout MIB modules.
The MIB modules contain following groups of objects: The MIB modules contain following groups of objects:
SIP-COMMON-MIB: Management objects common to all the SIP entities SIP-COMMON-MIB: Management objects common to all the SIP entities
o sipCommonMIBObjects o sipCommonMIBObjects
* sipCommonCfgBase: This object group defines configuration * sipCommonCfgBase: This object group defines configuration
objects common to all SIP entities including the SIP protocol objects common to all SIP entities including the SIP protocol
version, the type of SIP entity (UA, proxy, redirect, registrar version, the type of SIP entity (UA, proxy, redirect, registrar
server), the operational and administrative status, the SIP server), the operational and administrative status, the SIP
organization name, the maximum number of SIP transactions an organization name, the maximum number of SIP transactions an
entity can manage, etc. entity can manage, etc.
* sipCommonCfgTimer: This object group defines timer * sipCommonCfgTimer: This object group defines timer
configuration objects applicable to SIP user agent and stateful configuration objects applicable to SIP user agent and stateful
SIP proxy entities. SIP proxy entities.
* sipCommonStatsSummary: This object group defines a table * sipCommonSummaryStats: This object group defines a table
containing the summary statistics objects applicable to all SIP containing the summary statistics objects applicable to all SIP
entities, including the total number of all SIP requests and entities, including the total number of all SIP requests and
responses in/out, and the total number of transactions. responses in/out, and the total number of transactions.
* sipCommonStatsMethod: This object group defines a table * sipCommonMethodStats: This object group defines a table
containing the SIP method statistics objects applicable to all containing the SIP method statistics objects applicable to all
SIP entities, including the number outbound and inbound SIP entities, including the number outbound and inbound
requests on a per method basis. Retransmissions, where requests on a per method basis. Retransmissions, where
appropriate, are also included in these statistics. appropriate, are also included in these statistics.
* sipCommonStatusCode: This object group defines a table * sipCommonStatusCode: This object group defines a table
indicating the number of SIP responses (in and out) that the indicating the number of SIP responses (in and out) that the
SIP entity has been requested to monitor on a per method basis SIP entity has been requested to monitor on a per method basis
(100, 200, 302, etc.). (100, 200, 302, etc.).
* sipCommonStatsTrans: This object group defines a table * sipCommonStatsTrans: This object group defines a table
containing a gauge reflecting the number of transactions containing a gauge reflecting the number of transactions
currently awaiting definitive responses by the managed SIP currently awaiting definitive responses by the managed SIP
entity. entity.
* sipCommonStatsRetry: This object group defines statistic * sipCommonStatsRetry: This object group defines statistic
objects indicating the number of retransmissions sent on a per objects indicating the number of retransmissions sent on a per
method basis. method basis.
* sipCommonStatsOther: This object group defines additional * sipCommonOtherStats: This object group defines additional
statistic objects including the number of SIP requests received statistic objects including the number of SIP requests received
with unsupported URIs, the number of requests received with with unsupported URIs, the number of requests received with
unsupported SIP methods, and the number of discarded messages. unsupported SIP methods, and the number of discarded messages.
* sipCommonNotifObjects: This object group defines objects * sipCommonNotifObjects: This object group defines objects
accessible only via a notification (MAX ACCESS clause of accessible only via a notification (MAX ACCESS clause of
accessible-for-notify): they are related to the SNMP accessible-for-notify): they are related to the SNMP
notifications defined in this MIB module. notifications defined in this MIB module.
The SIP-COMMON-MIB also contains notifications, including: The SIP-COMMON-MIB also contains notifications, including:
o sipStatusCodeNotif: indicates that a specific status code has been o sipCommonStatusCodeNotif: indicates that a specific status code
sent or received by the system. has been sent or received by the system.
o sipStatusCodeThreshExceededNotif: indicates that a specific status o sipCommonStatusCodeThreshExceededNotif: indicates that a specific
code has been sent or received by the system enough to exceed the status code has been sent or received by the system enough to
configured threshold. exceed the configured threshold.
SIP-SERVER-MIB: Groups of objects for SIP Proxy, Redirect and SIP-SERVER-MIB: Groups of objects for SIP Proxy, Redirect and
Registrar servers Registrar servers
o sipServerMIBObjects o sipServerMIBObjects
* sipServerCfg: This object group defines common server * sipServerCfg: This object group defines common server
configuration objects including the SIP server host address. configuration objects including the SIP server host address.
* sipProxyCfg: This object group defines configuration objects * sipServerProxyCfg: This object group defines configuration
for SIP Proxy servers including the proxy mode of operation objects for SIP Proxy servers including the proxy mode of
(stateless, stateful, call stateful), the proxy authentication operation (stateless, stateful, call stateful), the proxy
method(s) and realm, etc. authentication method(s) and realm, etc.
* sipProxyStats: This object group defines a table containing the * sipServerProxyStats: This object group defines a table
statistics objects applicable to SIP proxy servers. It containing the statistics objects applicable to SIP proxy
includes the number of occurrences of unsupported options being servers. It includes the number of occurrences of unsupported
specified in received Proxy-Require headers. options being specified in received Proxy-Require headers.
* sipRegCfg: This object group defines common configuration * sipServerRegCfg: This object group defines common configuration
objects for SIP Registrar servers including the ability to objects for SIP Registrar servers including the ability to
accept third-party registrations, the maximum registration accept third-party registrations, the maximum registration
expiry that may be requested by user agents, the maximum number expiry that may be requested by user agents, the maximum number
of users the registrar can support, the number of currently of users the registrar can support, the number of currently
registered users, per contact registration information, etc. registered users, per contact registration information, etc.
* sipRegStats: This object group contains summary statistics * sipServerRegStats: This object group contains summary
objects for SIP Registrar servers, precisely, the number of statistics objects for SIP Registrar servers, precisely, the
REGISTER requests that have been accepted or rejected. number of REGISTER requests that have been accepted or
rejected.
SIP-UA-MIB: Group of objects for SIP User Agents. SIP-UA-MIB: Group of objects for SIP User Agents.
o sipUAMIBObjects o sipUAMIBObjects
* sipUACfgServer: This object group specifies SIP server * sipUACfgServer: This object group specifies SIP server
configuration objects applicable to SIP user agents including configuration objects applicable to SIP user agents including
the Internet address of the SIP Server to use to register, the Internet address of the SIP Server to use to register,
proxy or redirect calls. proxy or redirect calls.
To conform with this specification, an SNMP agent MUST implement the To conform with this specification, an SNMP agent MUST implement the
SIP-TC MIB module, plus the SIP-COMMON-MIB module and one of the SIP SIP-TC-MIB module, plus the SIP-COMMON-MIB module and one of the SIP
entity-type- specific MIB modules (SIP-SERVER-MIB or SIP-UA-MIB) as entity-type- specific MIB modules (SIP-SERVER-MIB or SIP-UA-MIB) as
applicable for each instance of a SIP entity being managed. If a applicable for each instance of a SIP entity being managed. If a
device has more than one SIP entity or multiple instances of the same device has more than one SIP entity or multiple instances of the same
entity type, it MUST implement multiple SIP modules. Section 4.2 entity type, it MUST implement multiple SIP modules. Section 5.2
describes handling of multiple instances in detail. describes handling of multiple instances in detail.
5.1. Textual Conventions 5.1. Textual Conventions
The data types SipTransportProtocol, SipEntityRole, The data types SipTCTransportProtocol, SipTCEntityRole,
SipOptionTagHeaders, and SipMethodName are defined in the SIP-TC MIB SipTCOptionTagHeaders, and SipTCMethodName are defined in the SIP-TC-
module and used as Textual Conventions in this document. MIB module and used as Textual Conventions in this document.
5.2. Relationship to the Network Services MIB 5.2. Relationship to the Network Services MIB
In the design of the SIP MIB, the authors considered the following In the design of the SIP MIB, the authors considered the following
requirement: the SIP MIB must allow a single system with a single requirement: the SIP MIB must allow a single system with a single
SNMP agent to support multiple instances of various SIP MIB modules. SNMP agent to support multiple instances of various SIP MIB modules.
This requirement is met by using the framework provided by the This requirement is met by using the framework provided by the
Network Services Monitoring MIB, NETWORK-SERVICES-MIB, RFC 2788 Network Services Monitoring MIB, NETWORK-SERVICES-MIB, RFC 2788
[RFC2788]. [RFC2788].
skipping to change at page 6, line 48 skipping to change at page 6, line 49
"sip_proxy17" "sip_proxy17"
o for a SIP Registrar entity, the applName value SHOULD be equal to o for a SIP Registrar entity, the applName value SHOULD be equal to
a character string starting with "sip_registrar" followed by a a character string starting with "sip_registrar" followed by a
unique application instance identifier, for example, unique application instance identifier, for example,
"sip_registrar1", "sip_registrar2" "sip_registrar1", "sip_registrar2"
o for a SIP User Agent entity, the applName value SHOULD be equal to o for a SIP User Agent entity, the applName value SHOULD be equal to
a character string starting with "sip_ua" followed by a unique a character string starting with "sip_ua" followed by a unique
application instance identifier, for example, "sip_ua1", "sip_ua2" application instance identifier, for example, "sip_ua1", "sip_ua2"
o for any combination of Proxy, Registrar, or Redirect Server being o for any combination of Proxy, Registrar, or Redirect Server being
managed as a single aggregate entity, the applName value for the managed as a single aggregate entity, the applName value for the
combined server entity MUST reflect the appropriate combination combined server entity SHOULD reflect the appropriate combination
followed by a unique application instance identifier. In order to followed by a unique application instance identifier. In order to
facilitate consistent agent behavior and management application facilitate consistent agent behavior and management application
expectations, the following order of names is RECOMMENDED: expectations, the following order of names is RECOMMENDED:
* if Proxy exists, list first. * if Proxy exists, list first.
* if Proxy and Redirect exists, list Redirect second. * if Proxy and Redirect exists, list Redirect second.
* if Registrar exists, always list last. * if Registrar exists, always list last.
For example "sip_proxy1", "sip_proxy_registrar1", For example "sip_proxy1", "sip_proxy_registrar1",
"sip_proxy_redirect5", "sip_proxy_redirect_registrar2", or "sip_proxy_redirect5", "sip_proxy_redirect_registrar2", or
"sip_registrar1". "sip_registrar1".
o Note: the value of the network service application index o Note: the value of the network service application index
(applIndex) may be different from the instance identifier used in (applIndex) may be different from the instance identifier used in
the system (the applIndex is dynamically created and the value the system (the applIndex is dynamically created and the value
assigned by the SNMP agent at the creation of the table entry assigned by the SNMP agent at the creation of the table entry
skipping to change at page 7, line 26 skipping to change at page 7, line 26
application name is provided as part of the application name application name is provided as part of the application name
applName by the system administrator or configuration files of the applName by the system administrator or configuration files of the
SIP entity). This note is illustrated in the first example SIP entity). This note is illustrated in the first example
provided below. provided below.
Finally, the SNMP agent MAY support any combination of the other Finally, the SNMP agent MAY support any combination of the other
attributes in applTable. If supported, the following objects SHOULD attributes in applTable. If supported, the following objects SHOULD
have values populated as follows: have values populated as follows:
o applVersion: version of the SIP application, o applVersion: version of the SIP application,
o applUptime: the value of applUptime MUST be identical to the value o applUptime: the value of applUptime MUST be identical to the value
of sipServiceStartTime defined in the SIP-COMMON-MIB module, of sipCommonCfgServiceStartTime defined in the SIP-COMMON-MIB
module,
o applOperStatus: the value of applOperStatus SHOULD reflect the o applOperStatus: the value of applOperStatus SHOULD reflect the
operational status of sipServiceOperStatus, at least by means of a operational status of sipCommonCfgServiceOperStatus, at least by
mapping, means of a mapping,
o applLastChange: the value of applLastChange MUST be identical to o applLastChange: the value of applLastChange MUST be identical to
the value of sipServiceLastChange defined in the SIP-COMMON the value of sipCommonCfgServiceLastChange defined in the SIP-
module. COMMON module.
A number of other objects are defined as part of the applTable. They A number of other objects are defined as part of the applTable. They
are not included for the sake of brevity and due to the fact that are not included for the sake of brevity and due to the fact that
they do not enhance the concept being presented. they do not enhance the concept being presented.
Example 1: The tables below illustrate how a system acting as both Example 1: The tables below illustrate how a system acting as both
Proxy and Registrar server might be configured to maintain separate Proxy and Registrar server might be configured to maintain separate
SIP-COMMON-MIB instances. SIP-COMMON-MIB instances.
The NETWORK-SERVICES-MIB applTable might be populated as follows: The NETWORK-SERVICES-MIB applTable might be populated as follows:
skipping to change at page 8, line 10 skipping to change at page 8, line 13
+-----------+-------------------+----------------------+ +-----------+-------------------+----------------------+
The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for the The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for the
proxy (applIndex=1) and one for the registrar (applIndex=2). The proxy (applIndex=1) and one for the registrar (applIndex=2). The
SIP-SERVER-MIB tables would, however, only be populated with one row SIP-SERVER-MIB tables would, however, only be populated with one row
indexed by applIndex=1 and applIndex=2 respectively if the server indexed by applIndex=1 and applIndex=2 respectively if the server
provides either proxy or registrar. provides either proxy or registrar.
SIP-COMMON-MIB sipCommonCfgTable might be populated as: SIP-COMMON-MIB sipCommonCfgTable might be populated as:
+-----------+--------------------+----------------------+-----+ +---------+------------------------+--------------------------+-----+
| applIndex | sipProtocolVersion | sipServiceOperStatus | ... | | applInd | sipCommonCfgProtocolVe | sipCommonCfgServiceOperS | ... |
+-----------+--------------------+----------------------+-----+ | e x | r sion | t atus | |
| 1 | "SIP/2.0" | up(1) | 2 | +---------+------------------------+--------------------------+-----+
| "SIP/2.0" | restarting(4) | | | | 1 | "SIP/2.0" | up(1) | |
+-----------+--------------------+----------------------+-----+ | 2 | "SIP/2.0" | restarting(4) | |
+---------+------------------------+--------------------------+-----+
while sipProxyCfgTable in SIP-SERVER-MIB might be populated as: while sipServerProxyCfgTable in SIP-SERVER-MIB might be populated as:
+-----------+----------------------+-----+ +-----------+-------------------------------+-----+
| applIndex | sipProxyStatefulness | ... | | applIndex | sipServerCfgProxyStatefulness | ... |
+-----------+----------------------+-----+ +-----------+-------------------------------+-----+
| 1 | stateless(1) | | | 1 | stateless(1) | |
+-----------+----------------------+-----+ +-----------+-------------------------------+-----+
and sipRegUserTable in SIP-SERVER-MIB might be populated as: and sipServerRegUserTable in SIP-SERVER-MIB might be populated as:
+-----------+--------------+-------------------+-----+ +-----------+-----------------------+---------------------+-----+
| applIndex | sipUserIndex | sipUserUri | ... | | applIndex | sipServerRegUserIndex | sipServerRegUserUri | ... |
+-----------+--------------+-------------------+-----+ +-----------+-----------------------+---------------------+-----+
| 2 | 1 | bob@example.com | | | 2 | 1 | bob@example.com | |
| 2 | 2 | alice@example.com | | | 2 | 2 | alice@example.com | |
| 2 | 3 | jim@example.com | | | 2 | 3 | jim@example.com | |
| 2 | 4 | john@example.com | | | 2 | 4 | john@example.com | |
+-----------+--------------+-------------------+-----+ +-----------+-----------------------+---------------------+-----+
Example 2: Example 2:
This example illustrates how to represent a system acting as both This example illustrates how to represent a system acting as both
Proxy and Registrar server, where the two entities share a single Proxy and Registrar server, where the two entities share a single
instance of SIP-COMMON-MIB. instance of SIP-COMMON-MIB.
The NETWORK-SERVICES-MIB applTable might be populated as follows: The NETWORK-SERVICES-MIB applTable might be populated as follows:
+-----------+------------------------+------------------------------+ +-----------+------------------------+------------------------------+
skipping to change at page 9, line 8 skipping to change at page 9, line 17
+-----------+------------------------+------------------------------+ +-----------+------------------------+------------------------------+
| 1 | "sip_proxy_registrar1" | "ACME SIP Proxy and | | 1 | "sip_proxy_registrar1" | "ACME SIP Proxy and |
| | | Registrar" | | | | Registrar" |
+-----------+------------------------+------------------------------+ +-----------+------------------------+------------------------------+
The SIP-COMMON-MIB sipCommonCfgTable would have only one row to cover The SIP-COMMON-MIB sipCommonCfgTable would have only one row to cover
both the proxy and the registrar. both the proxy and the registrar.
SIP-COMMON-MIB sipCommonCfgTable might be populated as: SIP-COMMON-MIB sipCommonCfgTable might be populated as:
+-----------+--------------------+----------------------+ +----------+--------------------------+-----------------------------+
| applIndex | sipProtocolVersion | sipServiceOperStatus | | applInde | sipCommonCfgProtocolVers | sipCommonCfgServiceOperStat |
+-----------+--------------------+----------------------+ | x | i on | u s |
| 1 | "SIP/2.0" | up(1) | +----------+--------------------------+-----------------------------+
+-----------+--------------------+----------------------+ | 1 | "SIP/2.0" | up(1) |
+----------+--------------------------+-----------------------------+
while sipRegUserTable in SIP-SERVER-MIB might be populated as: while sipServerRegUserTable in SIP-SERVER-MIB might be populated as:
+-----------+--------------+-------------------+-----+ +-----------+-----------------------+---------------------+-----+
| applIndex | sipUserIndex | sipUserUri | ... | | applIndex | sipServerRegUserIndex | sipServerRegUserUri | ... |
+-----------+--------------+-------------------+-----+ +-----------+-----------------------+---------------------+-----+
| 2 | 1 | bob@example.com | | | 2 | 1 | bob@example.com | |
| 2 | 2 | alice@example.com | | | 2 | 2 | alice@example.com | |
| 2 | 3 | kevin@example.com | | | 2 | 3 | kevin@example.com | |
| 2 | 4 | jf@example.com | | | 2 | 4 | jf@example.com | |
+-----------+--------------+-------------------+-----+ +-----------+-----------------------+---------------------+-----+
The NETWORK-SERVICES-MIB assocTable is not considered a requirement The NETWORK-SERVICES-MIB assocTable is not considered a requirement
for SIP systems. It is not a mandatory group for compliance with the for SIP systems. It is not a mandatory group for compliance with the
NETWORK-SERVICES-MIB module. NETWORK-SERVICES-MIB module.
The relationship between the value of applOperStatus and The relationship between the value of applOperStatus and
sipServiceOperStatus is as follows: sipCommonCfgServiceOperStatus is as follows:
+----------------------+-----------------------+-------------------+ +-------------------------------+---------------+-------------------+
| sipServiceOperStatus | -- corresponds to --> | applOperStatus | | sipCommonCfgServiceOperStatus | -- | applOperStatus |
+----------------------+-----------------------+-------------------+ | | corresponds | |
| up | --> | up | | | to --> | |
| 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.
5.3. IMPORTed MIB Modules and REFERENCE Clauses 5.3. IMPORTed MIB Modules and REFERENCE Clauses
The SIP MIB modules defined in this document IMPORT definitions The SIP MIB modules defined in this document IMPORT definitions
normatively from the following MIB modules, beyond [RFC2578], normatively from the following MIB modules, beyond [RFC2578],
skipping to change at page 10, line 26 skipping to change at page 10, line 33
in some of the examples described in the DESCRIPTION clauses, in some of the examples described in the DESCRIPTION clauses,
including Reliability of Provisional Responses in SIP [RFC3262], and including Reliability of Provisional Responses in SIP [RFC3262], and
SIP over SCTP [RFC4168]. SIP over SCTP [RFC4168].
6. Accommodating SIP Extension Methods 6. Accommodating SIP Extension Methods
The core set of SIP methods is defined in RFC 3261 [RFC3261]. Other The core set of SIP methods is defined in RFC 3261 [RFC3261]. Other
IETF RFCs define additional methods. In the future, additional IETF RFCs define additional methods. In the future, additional
methods may be defined. In order to avoid having to update the SIP- methods may be defined. In order to avoid having to update the SIP-
COMMON-MIB module to accommodate these extension methods, we use a COMMON-MIB module to accommodate these extension methods, we use a
method identifier name (SipMethodName textual-convention) to method identifier name (SipTCMethodName textual-convention) to
represent all SIP methods registered with IANA. See IANA represent all SIP methods registered with IANA. See IANA
Consideration section. Consideration section.
For example, the sipMethodSupportedTable is the main table for For example, the sipCommonMethodSupportedTable is the main table for
listing all of the SIP methods supported by a system, including the listing all of the SIP methods supported by a system, including the
SIP methods defined in RFC 3261 [RFC3261] and other SIP methods SIP methods defined in RFC 3261 [RFC3261] and other SIP methods
registered with IANA. The table is informational in nature and registered with IANA. The table is informational in nature and
populated by the system. Entries cannot be added or deleted by a populated by the system. Entries cannot be added or deleted by a
SNMP manager. SNMP manager.
The SIP specification RFC 3261 [RFC3261] section 27.4 establishes the The SIP specification RFC 3261 [RFC3261] section 27.4 establishes the
sub-registries for SIP Methods and Response Codes under sub-registries for SIP Methods and Response Codes under
http://www.iana.org/assignments/sip-parameters. This document uses http://www.iana.org/assignments/sip-parameters. This document uses
the existing sub-registry for the names of registered SIP method. the existing sub-registry for the names of registered SIP method.
For example, in the sipSupportedMethodTable of SIP-COMMON-MIB, the For example, in the sipCommonMethodSupportedTable of SIP-COMMON-MIB,
sipMethodName values can be represented as follows: the sipCommonMethodSupportedName values can be represented as
follows:
+------------------------+ +------------------------------+
| sipMethodName | | sipCommonMethodSupportedName |
+------------------------+ +------------------------------+
| "ACK" | | "ACK" |
| "BYE" | | "BYE" |
| "CANCEL" | | "CANCEL" |
| "INVITE" | | "INVITE" |
| "OPTIONS" | | "OPTIONS" |
+------------------------+ +------------------------------+
7. Definitions 7. Definitions
7.1. SIP Textual Conventions 7.1. SIP Textual Conventions
SIP-TC DEFINITIONS ::= BEGIN SIP-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC; -- RFC 2579
sipTC MODULE-IDENTITY sipTC MODULE-IDENTITY
LAST-UPDATED "200605171700Z" LAST-UPDATED "200609121700Z"
ORGANIZATION "IETF Session Initiation Protocol Working Group" ORGANIZATION "IETF Session Initiation Protocol Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
Co-editor Joon Maeng Co-editor Joon Maeng
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule
CableLabs
postal: 858 Coal Creek Circle
Louisville, CO 80027
USA
email: jf.mule@cablelabs.com
phone: +1 303 661 9100
Co-editor Jean-Francois Mule Co-editor Dave Walker
CableLabs email: drwalker@rogers.com"
postal: 858 Coal Creek Circle DESCRIPTION
Louisville, CO 80027 "Session Initiation Protocol (SIP) MIB Textual Conventions
USA module used by other SIP-related MIB Modules.
email: jf.mule@cablelabs.com
phone: +1 303 661 9100
Co-editor Dave Walker Copyright (C) The Internet Society (2006). This version of
email: drwalker@rogers.com" this MIB module is part of RFC XXXX; see the RFC itself for
DESCRIPTION full legal notices."
"Session Initiation Protocol (SIP) MIB Textual -- RFC Ed: replace XXXX with actual RFC number and remove this not
Conventions module used by other SIP-related REVISION "200609121700Z"
MIB Modules. DESCRIPTION
"Initial version of the IETF SIP-TC-MIB module. This version
published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX1 }
-- RFC Ed: replace XXX1 with actual IANA assigned number for this
-- sipTC mib module and remove this note
Copyright (C) The Internet Society (2006). This version --
of this MIB module is part of RFC XXXX; see the RFC -- Textual Conventions
itself for full legal notices." --
-- RFC Ed: replace XXXX with actual RFC number and remove this note
REVISION "200605171700Z"
DESCRIPTION
"Initial version of the IETF SIP-TC module.
This version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX1 }
-- RFC Ed: replace XXX1 with actual IANA assigned number for this
-- sipTC mib module and remove this note
-- SipTCTransportProtocol ::= TEXTUAL-CONVENTION
-- Textual Conventions STATUS current
-- DESCRIPTION
"This convention is a bit map. Each bit represents a transport
protocol. If a bit has value 1, then that selected transport
protocol is in some way dependent on the context of the object
using this convention. If a bit has value 0, then that
transport protocol is not selected. Combinations of bits can
be set when multiple transport protocols are selected.
SipTransportProtocol ::= TEXTUAL-CONVENTION bit 0: a protocol other than those defined here
STATUS current bit 1: User Datagram Protocol bit 2 : Transmission Control
DESCRIPTION Protocol
"This convention is a bit map. Each bit represents a bit 3: Stream Control Transmission Protocol
transport protocol. If a bit has value 1, then that bit 4: Transport Layer Security Protocol over TCP
selected transport protocol is in some way dependent bit 5: Transport Layer Security Protocol over SCTP
on the context of the object using this convention. "
If a bit has value 0, then that transport protocol
is not selected. Combinations of bits can be
set when multiple transport protocols are selected.
bit 0 : a protocol other than those defined here REFERENCE "RFC 3261, Section 18 and RFC 4168"
bit 1 : User Datagram Protocol SYNTAX BITS {
bit 2 : Transmission Control Protocol other(0), -- none of the following
bit 3 : Stream Control Transmission Protocol udp(1),
bit 4 : Transport Layer Security Protocol over TCP tcp(2),
bit 5 : Transport Layer Security Protocol over SCTP" sctp(3), -- RFC4168
SYNTAX BITS { tlsTcp(4),
other(0), -- none of the following tlsSctp(5) -- RFC 4168
udp(1), }
tcp(2),
sctp(3), -- RFC4168
tlsTcp(4),
tlsSctp(5) -- RFC 4168
}
-- REFERENCE "RFC 3261, Section 18"
-- REFERENCE "RFC 4168"
SipEntityRole ::= TEXTUAL-CONVENTION SipTCEntityRole ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention defines the role of a SIP entity. "This convention defines the role of a SIP entity. Examples of
Examples of SIP entities are proxies, user agents, SIP entities are proxies, user agents, redirect servers,
redirect servers, registrars or combinations of registrars or combinations of the above.
the above."
SYNTAX BITS {
other(0),
userAgent(1),
proxyServer(2),
redirectServer(3),
registrarServer(4)
}
SipOptionTagHeaders ::= TEXTUAL-CONVENTION User Agent (UA): A logical entity that can act as both a user
STATUS current agent client and user agent server. User Agent Client (UAC):
DESCRIPTION A logical entity that creates a new request, and then uses the
"This convention defines the header fields that use client transaction state machinery to send it. The role of UAC
the option tags per section 19.2 of RFC 3261. lasts only for the duration of that transaction. In other
These tags are used in Require (Section 20.32), words, if a piece of software initiates a request, it acts as
Proxy-Require (Section 20.29), Supported a UAC for the duration of that transaction. If it receives a
(Section 20.37) and Unsupported (Section 20.40) request later, it assumes the role of a user agent server for
header fields." the processing of that transaction. User Agent Server (UAS):
SYNTAX BITS { a logical entity that generates a response to a SIP request.
require(0), -- Require header The response accepts, rejects, or redirects the request. This
proxyRequire(1), -- Proxy-Require header role lasts only for the duration of that transaction. In
supported(2), -- Supported header other words, if a piece of software responds to a request, it
unsupported(3) -- Unsupported header acts as a UAS for the duration of that transaction. If it
} generates a request later, it assumes the role of a user agent
-- REFERENCE "RFC 3261, Section 19.2" client for the processing of that transaction.
SipMethodName ::= TEXTUAL-CONVENTION Proxy, Proxy Server: An intermediary entity that acts as both
STATUS current a server and a client for the purpose of making requests on
DESCRIPTION behalf of other clients. A proxy server primarily plays the
"This textual convention is a string that uniquely role of routing, which means its job is to ensure that a
identifies a SIP method. The scope of uniqueness request is sent to another entity 'closer' to the targeted
is the context of all defined SIP methods. user. Proxies are also useful for enforcing policy. A proxy
interprets, and, if necessary, rewrites specific parts of a
request message before forwarding it.
Experimental support of extension methods is Redirect Server: A redirect server is a user agent server that
acceptable and expected. Extension methods are generates 3xx responses to requests it receives, directing the
those defined in Internet-Draft documents but client to contact an alternate set of URIs.
not yet allocated an official sanctioned by IANA.
To support experimental extension methods, any Registrar: A registrar is a server that accepts REGISTER
object using this textual convention as syntax requests and places the information it receives in those
MAY return/accept a method identifier value other requests into the location service for the domain it handles."
than those sanctioned by IANA. That system MUST REFERENCE
ensure no collisions with officially assigned "RFC 3261, Section 6"
method names." SYNTAX BITS {
SYNTAX OCTET STRING (SIZE (1..128)) other(0),
userAgent(1),
proxyServer(2),
redirectServer(3),
registrarServer(4)
}
END SipTCOptionTagHeaders ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This convention defines the header fields that use the option
tags per section 19.2 of RFC 3261. These tags are used in
Require (Section 20.32), Proxy-Require (Section 20.29),
Supported (Section 20.37) and Unsupported (Section 20.40)
header fields."
REFERENCE
"RFC 3261, Sections 19.2, 20.32, 20.29, 20.37 and 20.40"
SYNTAX BITS {
require(0), -- Require header
proxyRequire(1), -- Proxy-Require header
supported(2), -- Supported header
unsupported(3) -- Unsupported header
}
SipTCMethodName ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is a string that uniquely identifies a
SIP method. The scope of uniqueness is the context of all
defined SIP methods.
Experimental support of extension methods is acceptable and
expected. Extension methods are those defined in
Internet-Draft documents but not yet allocated an official
sanctioned by IANA.
To support experimental extension methods, any object using
this textual convention as syntax MAY return/accept a method
identifier value other than those sanctioned by IANA. That
system MUST ensure no collisions with officially assigned
method names."
REFERENCE
"RFC 3261, Section 27.4"
SYNTAX OCTET STRING (SIZE (1..100))
END
7.2. SIP Common MIB Module 7.2. SIP Common MIB Module
SIP-COMMON-MIB DEFINITIONS ::= BEGIN SIP-COMMON-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
Counter32, Counter32,
Gauge32, Gauge32,
TimeTicks, TimeTicks,
Unsigned32, Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
RowStatus, RowStatus,
TruthValue TimeStamp,
FROM SNMPv2-TC -- RFC 2579 TruthValue
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM SNMP-FRAMEWORK-MIB -- RFC 3411
SipTransportProtocol, SipTCTransportProtocol,
SipMethodName, SipTCMethodName,
SipEntityRole, SipTCEntityRole,
SipOptionTagHeaders SipTCOptionTagHeaders
FROM SIP-TC FROM SIP-TC-MIB
applIndex applIndex
FROM NETWORK-SERVICES-MIB -- RFC 2788 FROM NETWORK-SERVICES-MIB -- RFC 2788
InetPortNumber InetPortNumber
FROM INET-ADDRESS-MIB; -- RFC 4001 FROM INET-ADDRESS-MIB; -- RFC 4001
sipCommonMIB MODULE-IDENTITY sipCommonMIB MODULE-IDENTITY
LAST-UPDATED "200605171700Z" LAST-UPDATED "200609121700Z"
ORGANIZATION "IETF Session Initiation Protocol Working Group" ORGANIZATION "IETF Session Initiation Protocol Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
Co-editor Joon Maeng Co-editor Joon Maeng
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 858 Coal Creek Circle postal: 858 Coal Creek Circle
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 9100 phone: +1 303 661 9100
Co-editor Dave Walker Co-editor Dave Walker
email: drwalker@rogers.com" email: drwalker@rogers.com"
DESCRIPTION DESCRIPTION
"Session Initiation Protocol (SIP) Common MIB module. "Session Initiation Protocol (SIP) Common MIB module. This
This module defines objects which MAY be common to all module defines objects which may be common to all SIP entities.
SIP entities.
SIP is an application-layer signaling protocol for SIP is an application-layer signaling protocol for creating,
creating, modifying and terminating multimedia modifying and terminating multimedia sessions with one or more
sessions with one or more participants. These sessions participants. These sessions include Internet multimedia
include Internet multimedia conferences and Internet conferences 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 managing objects which are This MIB is defined for managing objects which are common to
common to SIP User Agents (UAs), Proxy, Redirect SIP User Agents (UAs), Proxy, Redirect and Registrar servers.
and Registrar servers. Objects specific to each of Objects specific to each of these entities MAY be managed using
these entities MAY be managed using entity specific entity specific MIBs defined in other modules.
MIBs defined in other modules.
User Agent (UA): A logical entity that can act as both Copyright (C) The Internet Society (2006). This version of
a user agent client and user agent server. this MIB module is part of RFC XXXX; see the RFC itself for
User Agent Client (UAC): A logical entity that creates full legal notices."
a new request, and then uses the client -- RFC Ed: replace XXXX with actual RFC number and
transaction state machinery to send it. The role of UAC -- remove this note
lasts only for the duration of that transaction. In REVISION "200609121700Z"
other words, if a piece of software initiates a DESCRIPTION
request, it acts as a UAC for the duration of that "Initial version of the IETF SIP-COMMON-MIB module. This
transaction. If it receives a request later, it version published as part of RFC XXXX."
assumes the role of a user agent server for the
processing of that transaction.
User Agent Server (UAS): a logical entity that
generates a response to a SIP request. The
response accepts, rejects, or redirects the request.
This role lasts only for the duration of that
transaction. In other words, if a piece of software
responds to a request, it acts as a UAS for the
duration of that transaction. If it generates a
request later, it assumes the role of a user
agent client for the processing of that
transaction.
Proxy, Proxy Server: An intermediary entity that acts -- RFC Ed: replace XXXX with actual RFC number and remove this note
as both a server and a client for the purpose of making ::= { mib-2 XXX2 }
requests on behalf of other clients. A proxy server -- RFC Ed: replace XXX2 with actual IANA assigned number and
primarily plays the role of routing, which means its -- remove this note
job is to ensure that a request is sent to another
entity 'closer' to the targeted user.
Proxies are also useful for enforcing policy. A proxy
interprets, and, if necessary, rewrites specific parts
of a request message before forwarding it.
Redirect Server: A redirect server is a user agent -- Top-Level Components of this MIB.
server that generates 3xx responses to requests it sipCommonMIBNotifications OBJECT IDENTIFIER ::= { sipCommonMIB 0 }
receives, directing the client to contact an alternate sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
set of URIs. sipCommonMIBConformance OBJECT IDENTIFIER ::= { sipCommonMIB 2 }
Registrar: A registrar is a server that accepts --
REGISTER requests and places the information it -- This MIB contains objects that are common to all SIP entities.
receives in those requests into the location service --
for the domain it handles.
Copyright (C) The Internet Society (2006). This version -- Common basic configuration
of this MIB module is part of RFC XXXX; see the RFC sipCommonCfgBase OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 }
itself for full legal notices."
-- RFC Ed: replace XXXX with actual RFC number and
-- remove this note
REVISION "200605171700Z"
DESCRIPTION
"Initial version of the IETF SIP-COMMON-MIB module.
This version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX2 }
-- RFC Ed: replace XXX2 with actual IANA assigned number and
-- remove this note
-- Top-Level Components of this MIB. -- Protocol timer configuration
sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 } sipCommonCfgTimer OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 }
sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
sipCommonMIBConform OBJECT IDENTIFIER ::= { sipCommonMIB 2 }
-- -- SIP message summary statistics
-- This MIB contains objects that are common to all SIP entities. sipCommonSummaryStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 }
--
-- Common basic configuration -- Per method statistics
sipCommonCfgBase OBJECT IDENTIFIER sipCommonMethodStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 }
::= { sipCommonMIBObjects 1 }
-- Protocol timer configuration -- Per Status code or status code class statistics
sipCommonCfgTimer OBJECT IDENTIFIER sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 }
::= { sipCommonMIBObjects 2 }
-- SIP message summary statistics -- Transaction statistics
sipCommonStatsSummary OBJECT IDENTIFIER sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 }
::= { sipCommonMIBObjects 3 }
-- Per method statistics -- Method retry statistics
sipCommonStatsMethod OBJECT IDENTIFIER sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 }
::= { sipCommonMIBObjects 4 }
-- Per Status code or status code class statistics -- Other statistics
sipCommonStatusCode OBJECT IDENTIFIER sipCommonOtherStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 }
::= { sipCommonMIBObjects 5 }
-- Transaction statistics -- Accessible-for-notify objects
sipCommonStatsTrans OBJECT IDENTIFIER sipCommonNotifObjects OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 }
::= { sipCommonMIBObjects 6 }
-- Method retry statistics --
sipCommonStatsRetry OBJECT IDENTIFIER -- Common Configuration Objects
::= { sipCommonMIBObjects 7 } --
sipCommonCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the common configuration objects applicable
to all SIP entities."
::= { sipCommonCfgBase 1 }
-- Other statistics sipCommonCfgEntry OBJECT-TYPE
sipCommonStatsOther OBJECT IDENTIFIER SYNTAX SipCommonCfgEntry
::= { sipCommonMIBObjects 8 } MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of common configuration.
-- Accessible-for-notify objects Each row represents objects for a particular SIP entity
sipCommonNotifObjects OBJECT IDENTIFIER instance present in this system. applIndex is used to uniquely
::= { sipCommonMIBObjects 9 } identify these instances of SIP entities and correlate them
through the common framework of the NETWORK-SERVICES-MIB (RFC
2788)."
INDEX { applIndex }
::= { sipCommonCfgTable 1 }
-- SipCommonCfgEntry ::= SEQUENCE {
-- Common Configuration Objects sipCommonCfgProtocolVersion SnmpAdminString,
-- sipCommonCfgServiceOperStatus INTEGER,
sipCommonCfgTable OBJECT-TYPE sipCommonCfgServiceStartTime TimeTicks,
SYNTAX SEQUENCE OF SipCommonCfgEntry sipCommonCfgServiceLastChange TimeTicks,
MAX-ACCESS not-accessible sipCommonCfgOrganization SnmpAdminString,
STATUS current sipCommonCfgMaxTransactions Unsigned32,
DESCRIPTION sipCommonCfgServiceNotifEnable BITS,
"This table contains the common configuration objects sipCommonCfgEntityType SipTCEntityRole
applicable to all SIP entities." }
::= { sipCommonCfgBase 1 }
sipCommonCfgEntry OBJECT-TYPE sipCommonCfgProtocolVersion OBJECT-TYPE
SYNTAX SipCommonCfgEntry SYNTAX SnmpAdminString
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common configuration. "This object will reflect the version of SIP supported by this
SIP entity. It will follow the same format as SIP version
information contained in the SIP messages generated by this SIP
entity. For example, entities supporting SIP version 2 will
return 'SIP/2.0' as dictated by the standard."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipCommonCfgEntry 1 }
Each row represents objects for a particular SIP sipCommonCfgServiceOperStatus OBJECT-TYPE
entity instance present in this system. applIndex SYNTAX INTEGER {
is used to uniquely identify these instances of SIP unknown(1),
entities and correlate them through the common up(2),
framework of the NETWORK-SERVICES-MIB (RFC 2788)." down(3),
INDEX { applIndex } congested(4),
::= { sipCommonCfgTable 1 } restarting(5),
quiescing(6),
testing(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the current operational state of
the SIP application.
SipCommonCfgEntry ::= unknown : The operational status cannot be determined
SEQUENCE { for some reason.
sipProtocolVersion SnmpAdminString, up : The application is operating normally, and is
sipServiceOperStatus INTEGER, processing (receiving and possibly issuing) SIP
sipServiceStartTime TimeTicks, requests and responses.
sipServiceLastChange TimeTicks, down : The application is currently unable to process
sipOrganization SnmpAdminString, SIP messages.
sipMaxTransactions Unsigned32, congested : The application is operational but no additional
sipServiceNotifEnable BITS, inbound transactions can be accommodated at the
sipEntityType SipEntityRole moment.
} restarting : The application is currently unavailable but it
is in the process of restarting and will,
presumably, soon be able to process SIP messages.
quiescing : The application is currently operational
but has been administratively put into
quiescence mode. Additional inbound
transactions MAY be rejected.
testing : The application is currently in test mode
and MAY not be able to process SIP messages.
sipProtocolVersion OBJECT-TYPE The operational status values defined for this object are not
SYNTAX SnmpAdminString based on any specific information contained in the SIP
MAX-ACCESS read-only standard."
STATUS current ::= { sipCommonCfgEntry 2 }
DESCRIPTION
"This object will reflect the version of SIP supported by
this SIP entity. It will follow the same format as SIP
version information contained in the SIP messages
generated by this SIP entity. For example, entities
supporting SIP version 2 will return 'SIP/2.0' as
dictated by the standard."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipCommonCfgEntry 1 }
sipServiceOperStatus OBJECT-TYPE sipCommonCfgServiceStartTime OBJECT-TYPE
SYNTAX INTEGER { SYNTAX TimeTicks
unknown(1), MAX-ACCESS read-only
up(2), STATUS current
down(3), DESCRIPTION
congested(4), "The value of sysUpTime at the time the SIP entity was last
restarting(5), started. If started prior to the last re-initialization of the
quiescing(6), local network management subsystem, then this object contains a
testing(7) zero value."
} ::= { sipCommonCfgEntry 3 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the current operational state of
the SIP application.
unknown : The operational status cannot be determined sipCommonCfgServiceLastChange OBJECT-TYPE
for some reason. SYNTAX TimeTicks
up : The application is operating normally, and MAX-ACCESS read-only
is processing (receiving and possibly STATUS current
issuing) SIP requests and responses. DESCRIPTION
down : The application is currently unable to "The value of sysUpTime at the time the SIP entity entered its
process SIP messages. current operational state. If the current state was entered
congested : The application is operational but no prior to the last re-initialization of the local network
additional inbound transactions can be management subsystem, then this object contains a zero value."
accommodated at the moment. ::= { sipCommonCfgEntry 4 }
restarting : The application is currently unavailable
but it is in the process of restarting and
will, presumably, soon be able to process
SIP messages.
quiescing : The application is currently operational
but has been administratively put into
quiescence mode. Additional inbound
transactions MAY be rejected.
testing : The application is currently in test mode sipCommonCfgOrganization OBJECT-TYPE
and MAY not be able to process SIP SYNTAX SnmpAdminString
messages. MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the organization name which the SIP entity
inserts into Organization headers of SIP messages processed by
this system. If the string is empty, no Organization header is
to be generated."
REFERENCE
"RFC 3261, Section 20.25"
::= { sipCommonCfgEntry 5 }
The operational status values defined for this object sipCommonCfgMaxTransactions OBJECT-TYPE
are not based on any specific information contained in SYNTAX Unsigned32 (1..4294967295)
the SIP standard." MAX-ACCESS read-only
::= { sipCommonCfgEntry 2 } STATUS current
DESCRIPTION
"This object indicates the maximum number of simultaneous
transactions per second that the SIP entity can manage. In
general, the value of this object SHOULD reflect a level of
transaction processing per second that is considered high
enough to impact the system's CPU and/or memory resources to
the point of deteriorating SIP call processing but not high
enough to cause catastrophic system failure."
::= { sipCommonCfgEntry 6 }
sipServiceStartTime OBJECT-TYPE sipCommonCfgServiceNotifEnable OBJECT-TYPE
SYNTAX TimeTicks SYNTAX BITS {
MAX-ACCESS read-only sipCommonServiceColdStart(0),
STATUS current sipCommonServiceWarmStart(1),
DESCRIPTION sipCommonServiceStatusChanged(2)
"The value of sysUpTime at the time the SIP entity was }
last started. If started prior to the last MAX-ACCESS read-write
re-initialization of the local network management STATUS current
subsystem, then this object contains a zero value." DESCRIPTION
::= { sipCommonCfgEntry 3 } "This object specifies which SIP service related notifications
are enabled. Each bit represents a specific notification. If
a bit has a value 1, the associated notification is enabled and
will be generated by the SIP entity at the appropriate time.
sipServiceLastChange OBJECT-TYPE Support for these notifications is OPTIONAL: either none or all
SYNTAX TimeTicks notification values are supported. If an implementation does
MAX-ACCESS read-only not support this object, it should return a 'noSuchObject'
STATUS current exception to an SNMP GET operation. If notifications are
DESCRIPTION supported, this object's default value SHOULD reflect
"The value of sysUpTime at the time the SIP entity sipCommonServiceColdStart and sipCommonServiceWarmStart enabled
entered its current operational state. If the current and sipCommonServiceStatusChanged disabled.
state was entered prior to the last re-initialization of
the local network management subsystem, then this object
contains a zero value."
::= { sipCommonCfgEntry 4 }
sipOrganization OBJECT-TYPE This object value SHOULD persist across reboots."
SYNTAX SnmpAdminString DEFVAL { { sipCommonServiceColdStart,
MAX-ACCESS read-only sipCommonServiceWarmStart } }
STATUS current ::= { sipCommonCfgEntry 7 }
DESCRIPTION
"This object contains the organization name which the SIP
entity inserts into Organization headers of SIP messages
processed by this system. If the string is empty, no
Organization header is to be generated."
REFERENCE
"RFC 3261, Section 20.25"
::= { sipCommonCfgEntry 5 }
sipMaxTransactions OBJECT-TYPE sipCommonCfgEntityType OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX SipTCEntityRole
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum number of simultaneous "This object identifies the list of SIP entities this row is
transactions per second that the SIP entity can manage. related to. It is defined as a bit map. Each bit represents a
In general, the value of this object SHOULD reflect a type of SIP entity. If a bit has value 1, the SIP entity
level of transaction processing per second that is represented by this row plays the role of this entity type. If
considered high enough to impact the system's CPU and/or a bit has value 0, the SIP entity represented by this row does
memory resources to the point of deteriorating SIP call not act as this entity type Combinations of bits can be set
processing but not high enough to cause catastrophic when the SIP entity plays multiple SIP roles."
system failure." ::= { sipCommonCfgEntry 8 }
::= { sipCommonCfgEntry 6 }
sipServiceNotifEnable OBJECT-TYPE --
SYNTAX BITS { -- Support for multiple ports
sipServiceColdStart(0), --
sipServiceWarmStart(1), sipCommonPortTable OBJECT-TYPE
sipServiceStatusChanged(2) SYNTAX SEQUENCE OF SipCommonPortEntry
} MAX-ACCESS not-accessible
MAX-ACCESS read-write STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This table contains the list of ports that each SIP entity in
"This object specifies which SIP service related this system is allowed to use. These ports can be advertised
notifications are enabled. Each bit represents using the Contact header in a REGISTER request or response."
a specific notification. If a bit has a value 1, ::= { sipCommonCfgBase 2 }
the associated notification is enabled and will
be generated by the SIP entity at the appropriate
time. The notifications are OPTIONAL, and if they
are not implemented this object's value has no
meaning and MUST be 0. Setting this object in that
circumstance SHOULD result in a badValue error.
If notifications are supported, this object's default
value SHOULD reflect sipServiceColdStart and
sipServiceWarmStart enabled and sipServiceStatusChanged
disabled."
::= { sipCommonCfgEntry 7 }
sipEntityType OBJECT-TYPE sipCommonPortEntry OBJECT-TYPE
SYNTAX SipEntityRole SYNTAX SipCommonPortEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object identifies the list of SIP entities this "Specification of a particular port.
row is related to. It is defined as a bit map. Each
bit represents a type of SIP entity.
If a bit has value 1, the SIP entity represented by
this row plays the role of this entity type.
If a bit has value 0, the SIP entity represented by
this row does not act as this entity type
Combinations of bits can be set when the SIP entity
plays multiple SIP roles."
::= { sipCommonCfgEntry 8 }
-- Each row represents those objects for a particular SIP entity
-- Support for multiple ports present in this system. applIndex is used to uniquely identify
-- these instances of SIP entities and correlate them through the
sipPortTable OBJECT-TYPE common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
SYNTAX SEQUENCE OF SipPortEntry INDEX { applIndex, sipCommonPort }
MAX-ACCESS not-accessible ::= { sipCommonPortTable 1 }
STATUS current
DESCRIPTION
"This table contains the list of ports that each SIP
entity in this system is allowed to use. These ports
can be advertised using the Contact header in a REGISTER
request or response."
::= { sipCommonCfgBase 2 }
sipPortEntry OBJECT-TYPE SipCommonPortEntry ::= SEQUENCE {
SYNTAX SipPortEntry sipCommonPort InetPortNumber,
MAX-ACCESS not-accessible sipCommonPortTransportRcv SipTCTransportProtocol
STATUS current }
DESCRIPTION
"Specification of a particular port.
Each row represents those objects for a particular SIP sipCommonPort OBJECT-TYPE
entity present in this system. applIndex is used to SYNTAX InetPortNumber (1..65535)
uniquely identify these instances of SIP entities and MAX-ACCESS not-accessible
correlate them through the common framework of the STATUS current
NETWORK-SERVICES-MIB (RFC 2788)." DESCRIPTION
INDEX { applIndex, sipPort } "This object reflects a particular port that can be used by the
::= { sipPortTable 1 } SIP application."
::= { sipCommonPortEntry 1 }
SipPortEntry ::= sipCommonPortTransportRcv OBJECT-TYPE
SEQUENCE { SYNTAX SipTCTransportProtocol
sipPort InetPortNumber, MAX-ACCESS read-only
sipTransportRcv SipTransportProtocol STATUS current
} DESCRIPTION
"This object will specify the transport protocol the SIP entity
will use to receive SIP messages.
sipPort OBJECT-TYPE This object is a bit map. Each bit represents a transport
SYNTAX InetPortNumber protocol. If a bit has value 1, then that transport protocol
MAX-ACCESS not-accessible is currently being used. If a bit has value 0, then that
STATUS current transport protocol is currently not being used."
DESCRIPTION ::= { sipCommonPortEntry 2 }
"This object reflects a particular port that can be used
by the SIP application."
::= { sipPortEntry 1 }
sipTransportRcv OBJECT-TYPE --
SYNTAX SipTransportProtocol -- Support for SIP option tags (SIP extensions).
MAX-ACCESS read-only -- SIP extensions MAY be supported or required by SIP entities.
STATUS current --
DESCRIPTION
"This object will specify the transport protocol the SIP
entity will use to receive SIP messages.
This object is a bit map. Each bit represents a sipCommonOptionTagTable OBJECT-TYPE
transport protocol. If a bit has value 1, then that SYNTAX SEQUENCE OF SipCommonOptionTagEntry
transport protocol is currently being used. If a bit MAX-ACCESS not-accessible
has value 0, then that transport protocol is currently STATUS current
not being used." DESCRIPTION
::= { sipPortEntry 2 } "This table contains a list of the SIP option tags (SIP
extensions) that either required, supported, or unsupported by
the SIP entity. These option tags are used in the Require,
Proxy-Require, Supported and Unsupported header fields.
-- Example: if a user agent client supports and requires the
-- Support for SIP option tags (SIP extensions). server to support reliability of provisional responses (IETF
-- SIP extensions MAY be supported or required by SIP entities. RFC 3262), this table contains a row with the option tag string
-- '100rel' in sipCommonOptionTag and the OCTET STRING value of
'1010 0000' or '0xA0' in sipCommonOptionTagHeaderField.
sipOptionTagTable OBJECT-TYPE If a server does not support the required feature (indicated in
SYNTAX SEQUENCE OF SipOptionTagEntry a Require header to a UAS, or in a Proxy-Require to a Proxy
MAX-ACCESS not-accessible Server), the server returns a 420 Bad Extension listing the
STATUS current feature in an Unsupported header.
DESCRIPTION
"This table contains a list of the SIP option tags
(SIP extensions) that either required, supported, or
unsupported by the SIP entity.
These option tags are used in the Require,
Proxy-Require, Supported and Unsupported header fields.
Example: if a user agent client supports and requires
the server to support reliability of provisional
responses (IETF RFC 3262), this table contains a
row with the option tag string '100rel' in sipOptionTag
and the OCTET STRING value of '1010 0000' or '0xA0' in
sipOptionTagHeaderField.
If a server does not support the required feature Normally the list of such features supported by an entity is
(indicated in a Require header to a UAS, or in a static (i.e. will not change over time)."
Proxy-Require to a Proxy Server), the server returns a REFERENCE
420 Bad Extension listing the feature in an Unsupported "RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40"
header. ::= { sipCommonCfgBase 3 }
Normally the list of such features supported by an sipCommonOptionTagEntry OBJECT-TYPE
entity is static (i.e. will not change over time)." SYNTAX SipCommonOptionTagEntry
REFERENCE MAX-ACCESS not-accessible
"RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40" STATUS current
::= { sipCommonCfgBase 3 } DESCRIPTION
"A particular SIP option tag (extension) supported or
unsupported by the SIP entity, and which may be supported or
required by a peer.
sipOptionTagEntry OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX SipOptionTagEntry present in this system. applIndex is used to uniquely identify
MAX-ACCESS not-accessible these instances of SIP entities and correlate them through the
STATUS current common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION INDEX { applIndex, sipCommonOptionTagIndex }
"A particular SIP option tag (extension) supported or ::= { sipCommonOptionTagTable 1 }
unsupported by the SIP entity, and which may be
supported or required by a peer.
Each row represents those objects for a particular SIP SipCommonOptionTagEntry ::= SEQUENCE {
entity present in this system. applIndex is used to sipCommonOptionTagIndex Unsigned32,
uniquely identify these instances of SIP entities and sipCommonOptionTag SnmpAdminString,
correlate them through the common framework of the sipCommonOptionTagHeaderField SipTCOptionTagHeaders
NETWORK-SERVICES-MIB (RFC 2788). }
The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot."
INDEX { applIndex, sipOptionTagIndex }
::= { sipOptionTagTable 1 }
SipOptionTagEntry ::= sipCommonOptionTagIndex OBJECT-TYPE
SEQUENCE { SYNTAX Unsigned32 (1..4294967295)
sipOptionTagIndex Unsigned32, MAX-ACCESS not-accessible
sipOptionTag SnmpAdminString, STATUS current
sipOptionTagHeaderField SipOptionTagHeaders DESCRIPTION
} "This object uniquely identifies a conceptual row in the table."
::= { sipCommonOptionTagEntry 1 }
sipOptionTagIndex OBJECT-TYPE sipCommonOptionTag OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX SnmpAdminString
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in "This object indicates the SIP option tag. The option tag names
the table." are registered with IANA and available at http://www.iana.org."
::= { sipOptionTagEntry 1 } REFERENCE "RFC 3261, Section 27.1"
::= { sipCommonOptionTagEntry 2 }
sipOptionTag OBJECT-TYPE sipCommonOptionTagHeaderField OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SipTCOptionTagHeaders
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the SIP option tag. "This object indicates whether the SIP option tag is supported
The option tag names are registered with (Supported header), unsupported (Unsupported header), required
IANA and available at http://www.iana.org." (Require or Proxy-Require header) by the SIP entity. A SIP
::= { sipOptionTagEntry 2 } option tag may be both supported and required."
::= { sipCommonOptionTagEntry 3 }
sipOptionTagHeaderField OBJECT-TYPE --
SYNTAX SipOptionTagHeaders -- Supported SIP Methods
MAX-ACCESS read-only --
STATUS current sipCommonMethodSupportedTable OBJECT-TYPE
DESCRIPTION SYNTAX SEQUENCE OF SipCommonMethodSupportedEntry
"This object indicates whether the SIP option tag is MAX-ACCESS not-accessible
supported (Supported header), unsupported (Unsupported STATUS current
header), required (Require or Proxy-Require header) by DESCRIPTION
the SIP entity. "This table contains a list of methods supported by each SIP
A SIP option tag may be both supported and required." entity in this system (see the standard set of SIP methods in
::= { sipOptionTagEntry 3 } Section 7.1 of RFC 3261). Any additional methods that may be
incorporated into the SIP protocol can be represented by this
table without any requirement to update this MIB module.
-- The table is informational in nature; conveying to the NMS
-- Supported SIP Methods capabilities of the managed system.
--
sipMethodSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipMethodSupportedEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains a list of methods supported
by each SIP entity in this system. This MAY include,
but is not limited to, the standard set of SIP methods
discussed in Section 7.1 of RFC 3261. Any additional
methods that MAY be incorporated into the SIP protocol
can be represented by this table without any requirement
to update this MIB.
The table is informational in nature; conveying to the NMS From a protocol point of view, the list of methods advertised
capabilities of the managed system. by the SIP entity in the Allow header (Section 20.5 of RFC
3261) MUST be consistent with the methods reflected in this
table."
::= { sipCommonCfgBase 4 }
From a protocol point of view, the list of methods sipCommonMethodSupportedEntry OBJECT-TYPE
advertised by the SIP entity in the Allow header (Section SYNTAX SipCommonMethodSupportedEntry
20.5 of RFC 3261) MUST be consistent with the methods MAX-ACCESS not-accessible
reflected in this table." STATUS current
::= { sipCommonCfgBase 4 } DESCRIPTION
"A particular method supported by the SIP entity.
sipMethodSupportedEntry OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX SipMethodSupportedEntry present in this system. applIndex is used to uniquely identify
MAX-ACCESS not-accessible these instances of SIP entities and correlate them through the
STATUS current common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION INDEX { applIndex, sipCommonMethodSupportedIndex }
"A particular method supported by the SIP entity. ::= { sipCommonMethodSupportedTable 1 }
Each row represents those objects for a particular SIP SipCommonMethodSupportedEntry ::= SEQUENCE {
entity present in this system. applIndex is used to sipCommonMethodSupportedIndex Unsigned32,
uniquely identify these instances of SIP entities and sipCommonMethodSupportedName SipTCMethodName
correlate them through the common framework of the }
NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile sipCommonMethodSupportedIndex OBJECT-TYPE
and their value SHOULD be kept at reboot." SYNTAX Unsigned32 (1..4294967295)
INDEX { applIndex, sipMethodSupportedIndex } MAX-ACCESS not-accessible
::= { sipMethodSupportedTable 1 } STATUS current
DESCRIPTION
"This object uniquely identifies a conceptual row in the table
and reflects an assigned number used to identifier a specific
SIP method.
SipMethodSupportedEntry ::= This identifier is suitable for referencing the associated
SEQUENCE { method throughout this and other MIBs supported by this managed
sipMethodSupportedIndex Unsigned32, system."
sipMethodName SnmpAdminString ::= { sipCommonMethodSupportedEntry 1 }
}
sipMethodSupportedIndex OBJECT-TYPE sipCommonMethodSupportedName OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX SipTCMethodName
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row "This object reflects the supported method's name. The method
in the table and reflects an assigned number used name MUST be all upper case (e.g, 'INVITE')."
to identifier a specific SIP method. ::= { sipCommonMethodSupportedEntry 2 }
This identifier is suitable for referencing the --
associated method throughout this and other MIBs -- SIP Timer Configuration
supported by this managed system." --
::= { sipMethodSupportedEntry 1 } sipCommonCfgTimerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgTimerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains timer configuration objects applicable to
SIP user agent and SIP stateful Proxy Server entities."
::= { sipCommonCfgTimer 1 }
sipMethodName OBJECT-TYPE sipCommonCfgTimerEntry OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SipCommonCfgTimerEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the supported method's name. "A row of timer configuration.
The method name MUST be all upper case
(e.g, 'INVITE')."
::= { sipMethodSupportedEntry 2 }
-- Each row represents those objects for a particular SIP entity
-- SIP Timer Configuration present in this system. applIndex is used to uniquely identify
-- these instances of SIP entities and correlate them through the
sipCommonCfgTimerTable OBJECT-TYPE common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
SYNTAX SEQUENCE OF SipCommonCfgTimerEntry objects in this table entry SHOULD be non-volatile and their
MAX-ACCESS not-accessible value SHOULD be kept at reboot."
STATUS current INDEX { applIndex }
DESCRIPTION ::= { sipCommonCfgTimerTable 1 }
"This table contains timer configuration objects
applicable to SIP user agent and SIP stateful Proxy
Server entities."
::= { sipCommonCfgTimer 1 } SipCommonCfgTimerEntry ::= SEQUENCE {
sipCommonCfgTimerA Unsigned32,
sipCommonCfgTimerB Unsigned32,
sipCommonCfgTimerC Unsigned32,
sipCommonCfgTimerD Unsigned32,
sipCommonCfgTimerE Unsigned32,
sipCommonCfgTimerF Unsigned32,
sipCommonCfgTimerG Unsigned32,
sipCommonCfgTimerH Unsigned32,
sipCommonCfgTimerI Unsigned32,
sipCommonCfgTimerJ Unsigned32,
sipCommonCfgTimerK Unsigned32,
sipCommonCfgTimerT1 Unsigned32,
sipCommonCfgTimerT2 Unsigned32,
sipCommonCfgTimerT4 Unsigned32
}
sipCommonCfgTimerEntry OBJECT-TYPE sipCommonCfgTimerA OBJECT-TYPE
SYNTAX SipCommonCfgTimerEntry SYNTAX Unsigned32 (100..1000)
MAX-ACCESS not-accessible UNITS "milliseconds"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"A row of timer configuration. DESCRIPTION
"This object reflects the initial value for the retransmit timer
for the INVITE method. The retransmit timer doubles after each
retransmission, ensuring an exponential backoff in network
traffic. This object represents the initial time a SIP entity
will wait to receive a provisional response to an INVITE before
resending the INVITE request."
REFERENCE
"RFC 3261, Section 17.1.1.2"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 1 }
Each row represents those objects for a particular SIP sipCommonCfgTimerB OBJECT-TYPE
entity present in this system. applIndex is used to SYNTAX Unsigned32 (32000..300000)
uniquely identify these instances of SIP entities and UNITS "milliseconds"
correlate them through the common framework of the MAX-ACCESS read-only
NETWORK-SERVICES-MIB (RFC 2788). STATUS current
The objects in this table entry SHOULD be non-volatile DESCRIPTION
and their value SHOULD be kept at reboot." "This object reflects the maximum time a SIP entity will wait to
INDEX { applIndex } receive a final response to an INVITE. The timer is started
::= { sipCommonCfgTimerTable 1 } upon transmission of the initial INVITE request."
REFERENCE
"RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 2 }
SipCommonCfgTimerEntry ::= sipCommonCfgTimerC OBJECT-TYPE
SEQUENCE { SYNTAX Unsigned32 (180000..300000)
sipCfgTimerA Unsigned32, UNITS "milliseconds"
sipCfgTimerB Unsigned32, MAX-ACCESS read-only
sipCfgTimerC Unsigned32, STATUS current
sipCfgTimerD Unsigned32, DESCRIPTION
sipCfgTimerE Unsigned32, "This object reflects the maximum time a SIP Proxy Server will
sipCfgTimerF Unsigned32, wait to receive a provisional response to an INVITE. The Timer
sipCfgTimerG Unsigned32, C MUST be set for each client transaction when an INVITE
sipCfgTimerH Unsigned32, request is proxied."
sipCfgTimerI Unsigned32, REFERENCE
sipCfgTimerJ Unsigned32, "RFC 3261, Section 16.6"
sipCfgTimerK Unsigned32, DEFVAL { 180000 }
sipCfgTimerT1 Unsigned32, ::= { sipCommonCfgTimerEntry 3 }
sipCfgTimerT2 Unsigned32,
sipCfgTimerT4 Unsigned32
}
sipCfgTimerA OBJECT-TYPE sipCommonCfgTimerD OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (0..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the initial value for the "This object reflects the amount of time that the server
retransmit timer for the INVITE method. The retransmit transaction can remain in the 'Completed' state when unreliable
timer doubles after each retransmission, ensuring an transports are used. The default value MUST be equal or greater
exponential backoff in network traffic. This object than 32000 for UDP transport and its value MUST be 0 for
represents the initial time a SIP entity will wait to TCP/SCTP transport."
receive a provisional response to an INVITE before
resending the INVITE request."
REFERENCE
"RFC 3261, Section 17.1.1.2"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 1 }
sipCfgTimerB OBJECT-TYPE REFERENCE
SYNTAX Unsigned32 (32000..300000) "RFC 3261, Section 17.1.1.2"
UNITS "milliseconds" DEFVAL { 32000 }
MAX-ACCESS read-only ::= { sipCommonCfgTimerEntry 4 }
STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP entity will
wait to receive a final response to an INVITE. The
timer is started upon transmission of the initial INVITE
request."
REFERENCE
"RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 2 }
sipCfgTimerC OBJECT-TYPE sipCommonCfgTimerE OBJECT-TYPE
SYNTAX Unsigned32 (180000..300000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP Proxy Server "This object reflects the initial value for the retransmit timer
will wait to receive a provisional response to an for a non-INVITE method while in 'Trying State'. The
INVITE. retransmit timer doubles after each retransmission until it
The Timer C MUST be set for each client transaction when reaches T2 to ensure an exponential backoff in network traffic.
an INVITE request is proxied." This object represents the initial time a SIP entity will wait
REFERENCE to receive a provisional response to the request before
"RFC 3261, Section 16.6" resending the non-INVITE request."
DEFVAL { 180000 } REFERENCE
::= { sipCommonCfgTimerEntry 3 } "RFC 3261, Section 17.1.2.2"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 5 }
sipCfgTimerD OBJECT-TYPE sipCommonCfgTimerF OBJECT-TYPE
SYNTAX Unsigned32 (0..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the amount of time that the server "This object reflects the maximum time a SIP entity will wait to
transaction can remain in the 'Completed' state when receive a final response to a non-INVITE request. The timer is
unreliable transports are used. The default value MUST started upon transmission of the initial request."
be greater than 32000 for UDP transport and its value REFERENCE
MUST be 0 for TCP/SCTP transport." "RFC 3261, Section 17.1.2.2"
REFERENCE DEFVAL { 32000 }
"RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 4 }
sipCfgTimerE OBJECT-TYPE ::= { sipCommonCfgTimerEntry 6 }
SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the initial value for the retransmit
timer for a non-INVITE method while in 'Trying State'.
The retransmit timer doubles after each retransmission
until it reaches T2 to ensure an exponential backoff
in network traffic. This object represents the initial
time a SIP entity will wait to receive a provisional
response to the request before resending the non-INVITE
request."
REFERENCE
"RFC 3261, Section 17.1.2.2"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 5 }
sipCfgTimerF OBJECT-TYPE sipCommonCfgTimerG OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (0..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP entity will "This object reflects the initial value for the retransmit timer
wait to receive a final response to a non-INVITE request. for final responses to INVITE requests. If timer G fires, the
The timer is started upon transmission of the response is passed to the transport layer once more for
initial request." retransmission, and timer G is set to fire in MIN(2*T1, T2)
REFERENCE seconds. From then on, when timer G fires, the response is
"RFC 3261, Section 17.1.2.2" passed to the transport again for transmission, and timer G is
DEFVAL { 32000 } reset with a value that doubles, unless that value exceeds T2,
::= { sipCommonCfgTimerEntry 6 } in which case it is reset with the value of T2. The default
value MUST be T1 for UDP transport and its value MUST be 0 for
reliable transport like TCP/SCTP."
REFERENCE
"RFC 3261, Section 17.2.1"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 7 }
sipCfgTimerG OBJECT-TYPE sipCommonCfgTimerH OBJECT-TYPE
SYNTAX Unsigned32 (0..1000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the initial value for the "This object reflects the maximum time a server will wait to
retransmit timer for final responses to INVITE requests. receive an ACK before it abandons retransmitting the response.
The timer is started upon entering the 'Completed' state."
REFERENCE
"RFC 3261, Section 17.2.1"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 8 }
If timer G fires, the response is passed to the sipCommonCfgTimerI OBJECT-TYPE
transport layer once more for retransmission, and SYNTAX Unsigned32 (0..10000)
timer G is set to fire in MIN(2*T1, T2) seconds. From UNITS "milliseconds"
then on, when timer G fires, the response is passed to MAX-ACCESS read-only
the transport again for transmission, and timer G is STATUS current
reset with a value that doubles, unless that value DESCRIPTION
exceeds T2, in which case it is reset with the value of "This object reflects the maximum time a SIP entity will wait to
T2. The default value MUST be T1 for UDP transport and receive additional ACK message retransmissions.
its value MUST be 0 for reliable transport like
TCP/SCTP."
REFERENCE
"RFC 3261, Section 17.2.1"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 7 }
sipCfgTimerH OBJECT-TYPE The timer is started upon entering the 'Confirmed' state. The
SYNTAX Unsigned32 (32000..300000) default value MUST be T4 for UDP transport and its value MUST
UNITS "milliseconds" be 0 for reliable transport like TCP/SCTP."
MAX-ACCESS read-only REFERENCE
STATUS current "RFC 3261, Section 17.2.1"
DESCRIPTION DEFVAL { 5000 }
"This object reflects the maximum time a server will wait ::= { sipCommonCfgTimerEntry 9 }
to receive an ACK before it abandons retransmitting the
response. The timer is started upon entering the
'Completed' state."
REFERENCE
"RFC 3261, Section 17.2.1"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 8 }
sipCfgTimerI OBJECT-TYPE sipCommonCfgTimerJ OBJECT-TYPE
SYNTAX Unsigned32 (0..10000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP entity will "This object reflects the maximum time a SIP server will wait to
wait to receive additional ACK message retransmissions. receive retransmissions of non-INVITE request. The timer is
The timer is started upon entering the 'Confirmed' state. started upon entering the 'Completed' state for non-INVITE
The default value MUST be T4 for UDP transport and its transactions. When timer J fires, the server MUST transition to
value MUST be 0 for reliable transport like TCP/SCTP." the 'Terminated' state."
REFERENCE REFERENCE
"RFC 3261, Section 17.2.1" "RFC 3261, Section 17.2.2"
DEFVAL { 5000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 9 } ::= { sipCommonCfgTimerEntry 10 }
sipCfgTimerJ OBJECT-TYPE sipCommonCfgTimerK OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (0..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP server will "This object reflects the maximum time a SIP client will wait to
wait to receive retransmissions of non-INVITE request. receive retransmissions of responses to non-INVITE requests.
The timer is started upon entering the 'Completed' state The timer is started upon entering the 'Completed' state for
for non-INVITE transactions. When timer J fires, the non-INVITE transactions. When timer K fires, the server MUST
server MUST transition to the 'Terminated' state." transition to the 'Terminated' state. The default value MUST
REFERENCE "RFC 3261, Section 17.2.2" be T4 for UDP transport and its value MUST be 0 for reliable
DEFVAL { 32000 } transport like TCP/SCTP."
::= { sipCommonCfgTimerEntry 10 } REFERENCE
"RFC 3261, Section 17.1.2.2"
DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 11 }
sipCfgTimerK OBJECT-TYPE sipCommonCfgTimerT1 OBJECT-TYPE
SYNTAX Unsigned32 (0..10000) SYNTAX Unsigned32 (200..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP client will "This object reflects the T1 timer for a SIP entity. T1 is an
wait to receive retransmissions of responses to estimate of the round-trip time (RTT) between the client and
non-INVITE requests. server transactions."
The timer is started upon entering the 'Completed' state REFERENCE
for non-INVITE transactions. When timer K fires, the "RFC 3261, Section 17"
server MUST transition to the 'Terminated' state. DEFVAL { 500 }
The default value MUST be T4 for UDP transport and its ::= { sipCommonCfgTimerEntry 12 }
value MUST be 0 for reliable transport like TCP/SCTP."
REFERENCE
"RFC 3261, Section 17.1.2.2"
DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 11 }
sipCfgTimerT1 OBJECT-TYPE sipCommonCfgTimerT2 OBJECT-TYPE
SYNTAX Unsigned32 (200..10000) SYNTAX Unsigned32 (200..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the T1 timer for a SIP entity. T1 "This object reflects the T2 timer for a SIP entity. T2 is the
is an estimate of the round-trip time (RTT) between the maximum retransmit interval for non-INVITE requests and INVITE
client and server transactions." responses. It's used in various parts of the protocol to reset
REFERENCE other Timer* objects to this value."
"RFC 3261, Section 17" REFERENCE
DEFVAL { 500 } "RFC 3261, Section 17"
::= { sipCommonCfgTimerEntry 12 } DEFVAL { 4000 }
::= { sipCommonCfgTimerEntry 13 }
sipCfgTimerT2 OBJECT-TYPE sipCommonCfgTimerT4 OBJECT-TYPE
SYNTAX Unsigned32 (200..10000) SYNTAX Unsigned32 (200..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the T2 timer for a SIP entity. "This object reflects the T4 timer for a SIP entity. T4 is the
T2 is the maximum retransmit interval for non-INVITE maximum duration a message will remain in the network. It
requests and INVITE responses. It's used in various represents the amount of time the network will take to clear
parts of the protocol to reset other Timer* objects messages between client and server transactions. It's used in
to this value." various parts of the protocol to reset other Timer* objects to
REFERENCE this value."
"RFC 3261, Section 17" REFERENCE
DEFVAL { 4000 } "RFC 3261, Section 17"
::= { sipCommonCfgTimerEntry 13 } DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 14 }
sipCfgTimerT4 OBJECT-TYPE --
SYNTAX Unsigned32 (200..10000) -- Common Statistics Objects
UNITS "milliseconds" --
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the T4 timer for a SIP entity.
T4 is the maximum duration a message will remain in
the network. It represents the amount of time the
network will take to clear messages between client
and server transactions. It's used in various parts
of the protocol to reset other Timer* objects to this
value."
REFERENCE
"RFC 3261, Section 17"
DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 14 }
-- --
-- Common Statistics Objects -- Summary Statistics
-- --
sipCommonSummaryStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonSummaryStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the summary statistics objects applicable
to all SIP entities. Each row represents those objects for a
particular SIP entity present in this system."
::= { sipCommonSummaryStats 1 }
-- sipCommonSummaryStatsEntry OBJECT-TYPE
-- Summary Statistics SYNTAX SipCommonSummaryStatsEntry
-- MAX-ACCESS not-accessible
sipSummaryStatsTable OBJECT-TYPE STATUS current
SYNTAX SEQUENCE OF SipSummaryStatsEntry DESCRIPTION
MAX-ACCESS not-accessible "A row of summary statistics.
STATUS current
DESCRIPTION
"This table contains the summary statistics objects
applicable to all SIP entities. Each row represents
those objects for a particular SIP entity present in
this system."
::= { sipCommonStatsSummary 1 }
sipSummaryStatsEntry OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX SipSummaryStatsEntry present in this system. applIndex is used to uniquely identify
MAX-ACCESS not-accessible these instances of SIP entities and correlate them through the
STATUS current common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION INDEX { applIndex }
"A row of summary statistics. ::= { sipCommonSummaryStatsTable 1 }
Each row represents those objects for a particular SIP SipCommonSummaryStatsEntry ::= SEQUENCE {
entity present in this system. applIndex is used to sipCommonSummaryInRequests Counter32,
uniquely identify these instances of SIP entities and sipCommonSummaryOutRequests Counter32,
correlate them through the common framework of the sipCommonSummaryInResponses Counter32,
NETWORK-SERVICES-MIB (RFC 2788)." sipCommonSummaryOutResponses Counter32,
INDEX { applIndex } sipCommonSummaryTotalTransactions Counter32,
::= { sipSummaryStatsTable 1 } sipCommonSummaryDisconTime TimeStamp
}
SipSummaryStatsEntry ::= sipCommonSummaryInRequests OBJECT-TYPE
SEQUENCE { SYNTAX Counter32
sipSummaryInRequests Counter32, MAX-ACCESS read-only
sipSummaryOutRequests Counter32, STATUS current
sipSummaryInResponses Counter32, DESCRIPTION
sipSummaryOutResponses Counter32, "This object indicates the total number of SIP request messages
sipSummaryTotalTransactions Counter32 received by the SIP entity including retransmissions.
}
sipSummaryInRequests OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX Counter32 re-initialization of the SIP entity or service. A Management
MAX-ACCESS read-only Station can detect discontinuities in this counter by
STATUS current monitoring the sipCommonSummaryDisconTime object in the same
DESCRIPTION row."
"This object indicates the total number of SIP request ::= { sipCommonSummaryStatsEntry 1 }
messages received by the SIP entity including
retransmissions."
::= { sipSummaryStatsEntry 1 }
sipSummaryOutRequests OBJECT-TYPE sipCommonSummaryOutRequests 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
messages sent out (originated and relayed) by the SIP sent out (originated and relayed) by the SIP entity. Where a
entity. Where a particular message is sent more than particular message is sent more than once, for example as a
once, for example as a retransmission, or as a result of retransmission, or as a result of forking, each transmission is
forking, each transmission is counted separately." counted separately.
::= { sipSummaryStatsEntry 2 }
sipSummaryInResponses OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX Counter32 re-initialization of the SIP entity or service. A Management
MAX-ACCESS read-only Station can detect discontinuities in this counter by
STATUS current monitoring the sipCommonSummaryDisconTime object in the same
DESCRIPTION row."
"This object contains the total number of SIP response ::= { sipCommonSummaryStatsEntry 2 }
messages received by the SIP entity including
retransmissions."
::= { sipSummaryStatsEntry 3 }
sipSummaryOutResponses OBJECT-TYPE sipCommonSummaryInResponses 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
messages sent (originated and relayed) by the SIP entity received by the SIP entity including retransmissions.
including retransmissions."
::= { sipSummaryStatsEntry 4 }
sipSummaryTotalTransactions OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX Counter32 re-initialization of the SIP entity or service. A Management
MAX-ACCESS read-only Station can detect discontinuities in this counter by
STATUS current monitoring the sipCommonSummaryDisconTime object in the same
DESCRIPTION row."
"This object contains a count of the number of ::= { sipCommonSummaryStatsEntry 3 }
transactions that are in progress and transactions that
have reached the terminated state. It is not applicable
to stateless SIP Proxy Servers.
A SIP transaction occurs between a client and a server sipCommonSummaryOutResponses OBJECT-TYPE
and comprises all messages from the first request sent SYNTAX Counter32
from the client to the server up to a final (non-1xx) MAX-ACCESS read-only
response sent from the server to the client. STATUS current
DESCRIPTION
"This object contains the total number of SIP response messages
sent (originated and relayed) by the SIP entity including
retransmissions.
If the request is INVITE and the final response is a Discontinuities in the value of this counter can occur at
non-2xx, the transaction also include an ACK to the re-initialization of the SIP entity or service. A Management
response. The ACK for a 2xx response to an INVITE Station can detect discontinuities in this counter by
request is a separate transaction. monitoring the sipCommonSummaryDisconTime object in the same
row."
::= { sipCommonSummaryStatsEntry 4 }
The branch ID parameter in the Via header field values sipCommonSummaryTotalTransactions OBJECT-TYPE
serves as a transaction identifier. SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains a count of the number of transactions that
are in progress and transactions that have reached the
terminated state. It is not applicable to stateless SIP Proxy
Servers.
A transaction is identified by the CSeq sequence number A SIP transaction occurs between a client and a server and
within a single call leg. The ACK request has the same comprises all messages from the first request sent from the
CSeq number as the corresponding INVITE request, but client to the server up to a final (non-1xx) response sent from
comprises a transaction of its own. the server to the client.
In the case of a forked request, each branch counts as a If the request is INVITE and the final response is a non-2xx,
single transaction. the transaction also include an ACK to the response. The ACK
for a 2xx response to an INVITE request is a separate
transaction.
For a transaction stateless Proxy Server, this counter The branch ID parameter in the Via header field values serves
is always 0." as a transaction identifier.
::= { sipSummaryStatsEntry 5 }
-- A transaction is identified by the CSeq sequence number within
-- SIP Method Statistics a single call leg. The ACK request has the same CSeq number as
-- Total counts for each SIP method. the corresponding INVITE request, but comprises a transaction
-- of its own.
sipMethodStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipMethodStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the method statistics objects
for SIP entities. Each row represents those objects
for a particular SIP entity present in this system."
::= { sipCommonStatsMethod 1 }
sipMethodStatsEntry OBJECT-TYPE In the case of a forked request, each branch counts as a single
SYNTAX SipMethodStatsEntry transaction.
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of per entity method statistics.
Each row represents those objects for a particular SIP For a transaction stateless Proxy Server, this counter is
entity present in this system. applIndex is used to always 0.
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipStatsMethod }
::= { sipMethodStatsTable 1 }
SipMethodStatsEntry ::= Discontinuities in the value of this counter can occur at
SEQUENCE { re-initialization of the SIP entity or service. A Management
sipStatsMethod SipMethodName, Station can detect discontinuities in this counter by
sipStatsOutbounds Counter32, monitoring the sipCommonSummaryDisconTime object in the same
sipStatsInbounds Counter32 row."
} ::= { sipCommonSummaryStatsEntry 5 }
sipStatsMethod OBJECT-TYPE sipCommonSummaryDisconTime OBJECT-TYPE
SYNTAX SipMethodName SYNTAX TimeStamp
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies the SIP method "The value of the sysUpTime object when the counters for the
related to the objects in a particular row." summary statistics objects in this row last experienced a
::= { sipMethodStatsEntry 1 } discontinuity."
::= { sipCommonSummaryStatsEntry 6 }
sipStatsOutbounds OBJECT-TYPE --
SYNTAX Counter32 -- SIP Method Statistics
MAX-ACCESS read-only -- Total counts for each SIP method.
STATUS current --
DESCRIPTION sipCommonMethodStatsTable OBJECT-TYPE
"This object reflects the total number of requests SYNTAX SEQUENCE OF SipCommonMethodStatsEntry
sent by the SIP entity, excluding retransmissions. MAX-ACCESS not-accessible
Retransmissions are counted separately and are not STATUS current
reflected in this counter." DESCRIPTION
REFERENCE "This table contains the method statistics objects for SIP
"RFC 3261, Section 7.1" entities. Each row represents those objects for a particular
::= { sipMethodStatsEntry 2 } SIP entity present in this system."
sipStatsInbounds OBJECT-TYPE ::= { sipCommonMethodStats 1 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of requests
received by the SIP entity. Retransmissions are
counted separately and are not reflected in this
counter."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 3 }
-- sipCommonMethodStatsEntry OBJECT-TYPE
-- Support for specific status codes SYNTAX SipCommonMethodStatsEntry
-- MAX-ACCESS not-accessible
sipStatusCodesTable OBJECT-TYPE STATUS current
SYNTAX SEQUENCE OF SipStatusCodesEntry DESCRIPTION
MAX-ACCESS not-accessible "A row of per entity method statistics.
STATUS current
DESCRIPTION
"This table contains the list of SIP status codes which
each SIP entity in this system has been requested to
monitor. It is the mechanism by which specific status
codes are monitored."
::= { sipCommonStatusCode 2 }
sipStatusCodesEntry OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX SipStatusCodesEntry present in this system. applIndex is used to uniquely identify
MAX-ACCESS not-accessible these instances of SIP entities and correlate them through the
STATUS current common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION INDEX { applIndex, sipCommonMethodStatsName }
"This row contains information on a particular SIP status ::= { sipCommonMethodStatsTable 1 }
code that the SIP entity has been requested to monitor.
Each row represents those objects for a particular SIP SipCommonMethodStatsEntry ::= SEQUENCE {
entity present in this system. applIndex is used to sipCommonMethodStatsName SipTCMethodName,
uniquely identify these instances of SIP entities and sipCommonMethodStatsOutbounds Counter32,
correlate them through the common framework of the sipCommonMethodStatsInbounds Counter32,
NETWORK-SERVICES-MIB (RFC 2788)." sipCommonMethodStatsDisconTime TimeStamp
INDEX { applIndex, sipStatusCodeMethod, sipStatusCodeValue }
::= { sipStatusCodesTable 1 }
SipStatusCodesEntry ::= }
SEQUENCE {
sipStatusCodeMethod SipMethodName,
sipStatusCodeValue Unsigned32,
sipStatusCodeIns Counter32,
sipStatusCodeOuts Counter32,
sipStatusCodeRowStatus RowStatus
}
sipStatusCodeMethod OBJECT-TYPE sipCommonMethodStatsName OBJECT-TYPE
SYNTAX SipMethodName SYNTAX SipTCMethodName
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row "This object uniquely identifies the SIP method related to the
in the table and reflects an assigned number used objects in a particular row."
to identifier a specific SIP method." ::= { sipCommonMethodStatsEntry 1 }
::= { sipStatusCodesEntry 1 }
sipStatusCodeValue OBJECT-TYPE sipCommonMethodStatsOutbounds OBJECT-TYPE
SYNTAX Unsigned32 (100..999) SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a SIP status code value that the "This object reflects the total number of requests sent by the
SIP entity has been requested to monitor. All of the SIP entity, excluding retransmissions. Retransmissions are
other information in the row is related to this value." counted separately and are not reflected in this counter. A
::= { sipStatusCodesEntry 2 } Management Station can detect discontinuities in this counter
by monitoring the sipCommonMethodStatsDisconTime object in the
same row."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipCommonMethodStatsEntry 2 }
sipStatusCodeIns OBJECT-TYPE sipCommonMethodStatsInbounds 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 requests received by
messages received by the SIP entity with the status code the SIP entity. Retransmissions are counted separately and are
value contained in the sipStatusCodeValue column." not reflected in this counter. A Management Station can detect
::= { sipStatusCodesEntry 3 } discontinuities in this counter by monitoring the
sipCommonMethodStatsDisconTime object in the same row."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipCommonMethodStatsEntry 3 }
sipStatusCodeOuts OBJECT-TYPE sipCommonMethodStatsDisconTime OBJECT-TYPE
SYNTAX Counter32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of response "The value of the sysUpTime object when the counters for the
messages sent by the SIP entity with the status code method statistics objects in this row last experienced a
value contained in the sipStatusCodeValue column." discontinuity."
::= { sipStatusCodesEntry 4 } ::= { sipCommonMethodStatsEntry 4 }
sipStatusCodeRowStatus OBJECT-TYPE --
SYNTAX RowStatus -- Support for specific status codes
MAX-ACCESS read-create --
STATUS current sipCommonStatusCodeTable OBJECT-TYPE
DESCRIPTION SYNTAX SEQUENCE OF SipCommonStatusCodeEntry
"The row augmentation in sipStatusCodeNotifTable MAX-ACCESS not-accessible
will be governed by the value of this RowStatus. STATUS current
DESCRIPTION
"This table contains the list of SIP status codes which each SIP
entity in this system has been requested to monitor. It is the
mechanism by which specific status codes are monitored.
Entries created in this table must not persist across reboots"
::= { sipCommonStatusCode 1 }
This object is REQUIRED to create or delete rows sipCommonStatusCodeEntry OBJECT-TYPE
by a manager. SYNTAX SipCommonStatusCodeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This row contains information on a particular SIP status code
that the SIP entity has been requested to monitor. Entries
created in this table must not persist across reboots.
The values 'createAndGo' and 'destroy' are the Each row represents those objects for a particular SIP entity
only valid values allowed for this object. present in this system. applIndex is used to uniquely identify
If a row exists, it will reflect a status of these instances of SIP entities and correlate them through the
'active' when queried." common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
::= { sipStatusCodesEntry 5 } INDEX { applIndex, sipCommonStatusCodeMethod,
sipCommonStatusCodeValue }
::= { sipCommonStatusCodeTable 1 }
-- SipCommonStatusCodeEntry ::= SEQUENCE {
-- support for specific status code notifications sipCommonStatusCodeMethod SipTCMethodName,
-- sipCommonStatusCodeValue Unsigned32,
sipStatusCodeNotifTable OBJECT-TYPE sipCommonStatusCodeIns Counter32,
SYNTAX SEQUENCE OF SipStatusCodeNotifEntry sipCommonStatusCodeOuts Counter32,
MAX-ACCESS not-accessible sipCommonStatusCodeRowStatus RowStatus,
STATUS current sipCommonStatusCodeDisconTime TimeStamp
DESCRIPTION }
"This table contains objects to control notifications
related to particular status codes each SIP entity in
this system has been requested to monitor.
There is an entry in this table corresponding to each sipCommonStatusCodeMethod OBJECT-TYPE
entry in sipStatusCodesTable. Therefore, this SYNTAX SipTCMethodName
table augments that table and utilizes the same index MAX-ACCESS not-accessible
methodology. STATUS current
DESCRIPTION
"This object uniquely identifies a conceptual row in the table
and reflects an assigned number used to identify a specific SIP
method."
::= { sipCommonStatusCodeEntry 1 }
The objects in this table are not included directly sipCommonStatusCodeValue OBJECT-TYPE
in the sipStatusCodesTable simply to keep the SYNTAX Unsigned32 (100..999)
status code notification control objects separate from MAX-ACCESS not-accessible
the actual status code statistics." STATUS current
::= { sipCommonStatusCode 3 } DESCRIPTION
"This object contains a SIP status code value that the SIP
entity has been requested to monitor. All of the other
information in the row is related to this value."
::= { sipCommonStatusCodeEntry 2 }
sipStatusCodeNotifEntry OBJECT-TYPE sipCommonStatusCodeIns OBJECT-TYPE
SYNTAX SipStatusCodeNotifEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information controlling notifications "This object reflects the total number of response messages
for a particular SIP status code that the SIP entity has received by the SIP entity with the status code value contained
been requested to monitor." in the sipCommonStatusCodeValue column.
AUGMENTS { sipStatusCodesEntry }
::= { sipStatusCodeNotifTable 1 }
SipStatusCodeNotifEntry ::= Discontinuities in the value of this counter can occur at
SEQUENCE { re-initialization of the SIP entity or service, or when the
sipStatusCodeNotifSend TruthValue, monitoring of the Status code is temporarily disabled. A
sipStatusCodeNotifEmitMode INTEGER, Management Station can detect discontinuities in this counter
sipStatusCodeNotifThresh Unsigned32, by monitoring the sipCommonStatusCodeDisconTime object in the
sipStatusCodeNotifInterval Unsigned32 same row."
} ::= { sipCommonStatusCodeEntry 3 }
sipStatusCodeNotifSend OBJECT-TYPE sipCommonStatusCodeOuts OBJECT-TYPE
SYNTAX TruthValue SYNTAX Counter32
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls whether a sipStatusCodeNotif "This object reflects the total number of response messages sent
is emitted when the status code value specified in by the SIP entity with the status code value contained in the
by sipStatusCodeValue is sent or received. sipCommonStatusCodeValue column.
If the value of this object is 'true', then a
notification is sent. If it is 'false', no notification
is sent.
Note well, that a notification MAY be emitted for
every message sent or received that contains the
particular status code. Depending on the status code
involved, this can cause a significant number of
notification emissions that could be detrimental to
network performance.
Managers are forewarned to be prudent in the use of
this object to enable notifications. Look to
sipStatusCodeNotifEmitMode for alternative
controls for sipStatusCodeNotif emissions."
DEFVAL { false }
::= { sipStatusCodeNotifEntry 1 }
sipStatusCodeNotifEmitMode OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX INTEGER { re-initialization of the SIP entity or service, or when the
normal(1), monitoring of the Status code is temporarily disabled. A
oneShot(2), Management Station can detect discontinuities in this counter
triggered(3) -- read-only by monitoring the sipCommonStatusCodeDisconTime object in the
} same row."
MAX-ACCESS read-write ::= { sipCommonStatusCodeEntry 4 }
STATUS current
DESCRIPTION
"The object sipStatusCodeNotifSend MUST be set
to 'true' for the values of this object to have any
effect. It is RECOMMENDED that the desired emit mode
be established by this object prior to setting
sipStatusCodeNotifSend to 'true'. This object and
the sipStatusCodeNotifSend object can obviously be
set independently, but their respective values will
have a dependency on each other and the resulting
notifications.
This object specifies the mode for emissions of sipCommonStatusCodeRowStatus OBJECT-TYPE
sipStatusCodeNotif notifications. SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The row augmentation in sipCommonStatusCodeNotifTable will be
governed by the value of this RowStatus.
normal : sipStatusCodeNotif notifications will The values 'createAndGo' and 'destroy' are the only valid
be emitted by the system for each values allowed for this object. If a row exists, it will
SIP response messages sent or received reflect a status of 'active' when queried."
that contains the desired status code. ::= { sipCommonStatusCodeEntry 5 }
oneShot : Only one sipStatusCodeNotif notification sipCommonStatusCodeDisconTime OBJECT-TYPE
will be emitted. It will be the next SYNTAX TimeStamp
SIP response messages sent or received MAX-ACCESS read-only
that contains the desired status code. STATUS current
DESCRIPTION
"The value of the sysUpTime object when the counters for the
status code statistic objects in this row last experienced a
discontinuity."
::= { sipCommonStatusCodeEntry 6 }
No more notifications are emitted until this --
object is set to either 'oneShot' again -- Support for specific status code notifications
or 'normal'. This option is provided --
as a means of quelling the potential sipCommonStatusCodeNotifTable OBJECT-TYPE
promiscuous behavior that can be associated SYNTAX SEQUENCE OF SipCommonStatusCodeNotifEntry
with the sipStatusCodeNotif. MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains objects to control notifications related to
particular status codes each SIP entity in this system has been
requested to monitor.
triggered : This value is only readable and cannot be There is an entry in this table corresponding to each entry in
set. It reflects the default value of the sipCommonStatusCodeTable. Therefore, this table augments that
object or that the 'oneShot' case has table and utilizes the same index methodology.
occurred and indicates the mode needs to
be reset to get further notifications.
The mode is reset by setting this object The objects in this table are not included directly in the
to 'oneShot' or 'normal'." sipCommonStatusCodeTable simply to keep the status code
DEFVAL { triggered } notification control objects separate from the actual status
::= { sipStatusCodeNotifEntry 2 } code statistics."
::= { sipCommonStatusCode 2 }
sipStatusCodeNotifThresh OBJECT-TYPE sipCommonStatusCodeNotifEntry OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX SipCommonStatusCodeNotifEntry
MAX-ACCESS read-write MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the number of response messages "This row contains information controlling notifications for a
sent or received by this system that are considered particular SIP status code that the SIP entity has been
excessive. Based on crossing that threshold, a requested to monitor."
sipStatusCodeThreshExceededInNotif notification or a AUGMENTS { sipCommonStatusCodeEntry }
sipStatusCodeThreshExceededOutNotif will be sent. ::= { sipCommonStatusCodeNotifTable 1 }
The sipStatusCodeThreshExceededInNotif and
sipStatusCodeThreshExceededOutNotif notifications can
be used as an early warning mechanism in lieu of
using sipStatusCodeNotif.
Note that the configuration applied by this object SipCommonStatusCodeNotifEntry ::= SEQUENCE {
will be applied equally to inbound and outbound sipCommonStatusCodeNotifSend TruthValue,
response messages." sipCommonStatusCodeNotifEmitMode INTEGER,
DEFVAL { 500 } sipCommonStatusCodeNotifThresh Unsigned32,
::= { sipStatusCodeNotifEntry 3 } sipCommonStatusCodeNotifInterval Unsigned32
}
sipStatusCodeNotifInterval OBJECT-TYPE sipCommonStatusCodeNotifSend OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TruthValue
UNITS "seconds" MAX-ACCESS read-write
MAX-ACCESS read-write STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This object controls whether a sipCommonStatusCodeNotif is
"This object specifies the time interval over which emitted when the status code value specified in by
if sipCommonStatusCodeThresh is exceeded, with sipCommonStatusCodeValue is sent or received. If the value of
respect to sent or received messages, a this object is 'true', then a notification is sent. If it is
sipStatusCodeThreshExceededInNotif or 'false', no notification is sent.
sipStatusCodeThreshExceededOutNotif notification will
be sent.
Note that the configuration applied by this object Note well, that a notification MAY be emitted for every message
will be applied equally to inbound and outbound sent or received that contains the particular status code.
response messages." Depending on the status code involved, this can cause a
DEFVAL { 60 } significant number of notification emissions that could be
::= { sipStatusCodeNotifEntry 4 } detrimental to network performance. Managers are forewarned to
be prudent in the use of this object to enable notifications.
Look to sipCommonStatusCodeNotifEmitMode for alternative
controls for sipCommonStatusCodeNotif emissions."
DEFVAL { false }
::= { sipCommonStatusCodeNotifEntry 1 }
-- sipCommonStatusCodeNotifEmitMode OBJECT-TYPE
-- Transaction Statistics SYNTAX INTEGER {
-- normal(1),
sipCurrentTransTable OBJECT-TYPE oneShot(2),
SYNTAX SEQUENCE OF SipCurrentTransEntry triggered(3) -- read-only
MAX-ACCESS not-accessible }
STATUS current MAX-ACCESS read-write
DESCRIPTION STATUS current
"This table contains information on the transactions DESCRIPTION
currently awaiting definitive responses by each SIP "The object sipCommonStatusCodeNotifSend MUST be set to 'true'
entity in this system. for the values of this object to have any effect. It is
RECOMMENDED that the desired emit mode be established by this
object prior to setting sipCommonStatusCodeNotifSend to 'true'.
This object and the sipCommonStatusCodeNotifSend object can
obviously be set independently, but their respective values
will have a dependency on each other and the resulting
notifications.
This table does not apply to transaction stateless This object specifies the mode for emissions of
Proxy Servers." sipCommonStatusCodeNotif notifications.
::= { sipCommonStatsTrans 1 }
sipCurrentTransEntry OBJECT-TYPE normal : sipCommonStatusCodeNotif notifications will be
SYNTAX SipCurrentTransEntry emitted by the system for each SIP response
MAX-ACCESS not-accessible messages sent or received that contains the
STATUS current desired status code.
DESCRIPTION
"Information on a particular SIP entity's current
transactions.
Each row represents those objects for a particular SIP oneShot : Only one sipCommonStatusCodeNotif notification
entity present in this system. applIndex is used to will be emitted. It will be the next SIP response
uniquely identify these instances of SIP entities and messages sent or received that contains the
correlate them through the common framework of the desired status code.
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex }
::= { sipCurrentTransTable 1 }
SipCurrentTransEntry ::= No more notifications are emitted until this object
SEQUENCE { is set to either 'oneShot' again or 'normal'. This
sipCurrentTransactions Gauge32 option is provided as a means of quelling the
} potential promiscuous behavior that can be
associated with the sipCommonStatusCodeNotif.
sipCurrentTransactions OBJECT-TYPE triggered : This value is only readable and cannot be set. It
SYNTAX Gauge32 (0..4294967295) reflects the default value of the object or that
MAX-ACCESS read-only the 'oneShot' case has occurred and indicates the
STATUS current mode needs to be reset to get further
DESCRIPTION notifications. The mode is reset by setting this
"This object contains the number of transactions awaiting object to 'oneShot' or 'normal'."
definitive (non-1xx) response. In the case of a forked DEFVAL { oneShot }
request, each branch counts as a single transaction ::= { sipCommonStatusCodeNotifEntry 2 }
corresponding to the entity identified by applIndex."
::= { sipCurrentTransEntry 1 }
-- sipCommonStatusCodeNotifThresh OBJECT-TYPE
-- SIP Retry Statistics SYNTAX Unsigned32
-- MAX-ACCESS read-write
-- This group contains various statistic objects about STATUS current
-- retransmission counts. DESCRIPTION
-- "This object specifies the number of response messages sent or
sipCommonStatsRetryTable OBJECT-TYPE received by this system that are considered excessive. Based
SYNTAX SEQUENCE OF SipCommonStatsRetryEntry on crossing that threshold, a
MAX-ACCESS not-accessible sipCommonStatusCodeThreshExceededInNotif notification or a
STATUS current sipCommonStatusCodeThreshExceededOutNotif will be sent. The
DESCRIPTION sipCommonStatusCodeThreshExceededInNotif and
"This table contains retry statistics objects applicable sipCommonStatusCodeThreshExceededOutNotif notifications can be
to each SIP entity in this system." used as an early warning mechanism in lieu of using
::= { sipCommonStatsRetry 1 } sipCommonStatusCodeNotif.
sipCommonStatsRetryEntry OBJECT-TYPE Note that the configuration applied by this object will be
SYNTAX SipCommonStatsRetryEntry applied equally to inbound and outbound response messages."
MAX-ACCESS not-accessible DEFVAL { 500 }
STATUS current ::= { sipCommonStatusCodeNotifEntry 3 }
DESCRIPTION
"A row of retry statistics.
Each row represents those objects for a particular SIP sipCommonStatusCodeNotifInterval OBJECT-TYPE
entity present in this system. applIndex is used to SYNTAX Unsigned32
uniquely identify these instances of SIP entities and UNITS "seconds"
correlate them through the common framework of the MAX-ACCESS read-write
NETWORK-SERVICES-MIB (RFC 2788)." STATUS current
INDEX { applIndex, sipStatsRetryMethod } DESCRIPTION
::= { sipCommonStatsRetryTable 1 } "This object specifies the time interval over which if
sipCommonStatusCodeThresh is exceeded, with respect to sent or
received messages, a sipCommonStatusCodeThreshExceededInNotif
or sipCommonStatusCodeThreshExceededOutNotif notification will
be sent.
SipCommonStatsRetryEntry ::= Note that the configuration applied by this object will be
SEQUENCE { applied equally to inbound and outbound response messages."
sipStatsRetryMethod SipMethodName, DEFVAL { 60 }
sipStatsRetries Counter32, ::= { sipCommonStatusCodeNotifEntry 4 }
sipStatsRetryFinalResponses Counter32,
sipStatsRetryNonFinalResponses Counter32
}
sipStatsRetryMethod OBJECT-TYPE --
SYNTAX SipMethodName -- Transaction Statistics
MAX-ACCESS not-accessible --
STATUS current sipCommonTransCurrentTable OBJECT-TYPE
DESCRIPTION SYNTAX SEQUENCE OF SipCommonTransCurrentEntry
"This object uniquely identifies the SIP method MAX-ACCESS not-accessible
related to the objects in a row." STATUS current
::= { sipCommonStatsRetryEntry 1 } DESCRIPTION
"This table contains information on the transactions currently
awaiting definitive responses by each SIP entity in this
system.
sipStatsRetries OBJECT-TYPE This table does not apply to transaction stateless Proxy
SYNTAX Counter32 Servers."
MAX-ACCESS read-only ::= { sipCommonStatsTrans 1 }
STATUS current
DESCRIPTION
"This object reflects the total number of request
retransmissions that have been sent by the SIP
entity. Note that there could be multiple
retransmissions per request."
::= { sipCommonStatsRetryEntry 2 }
sipStatsRetryFinalResponses OBJECT-TYPE sipCommonTransCurrentEntry OBJECT-TYPE
SYNTAX Counter32 SYNTAX SipCommonTransCurrentEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Final Response "Information on a particular SIP entity's current transactions.
retries that have been sent by the SIP entity.
Note that there could be multiple retransmissions
per request."
::= { sipCommonStatsRetryEntry 3 }
sipStatsRetryNonFinalResponses OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX Counter32 present in this system. applIndex is used to uniquely identify
MAX-ACCESS read-only these instances of SIP entities and correlate them through the
STATUS current common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION INDEX { applIndex }
"This object reflects the total number of non-Final ::= { sipCommonTransCurrentTable 1 }
Response retries that have been sent by the SIP entity."
::= { sipCommonStatsRetryEntry 4 }
-- SipCommonTransCurrentEntry ::= SEQUENCE {
-- Other Common Statistics sipCommonTransCurrentactions Gauge32
-- }
sipOtherStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipOtherStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains other common statistics supported by
each SIP entity in this system."
::= { sipCommonStatsOther 1 }
sipOtherStatsEntry OBJECT-TYPE sipCommonTransCurrentactions OBJECT-TYPE
SYNTAX SipOtherStatsEntry SYNTAX Gauge32 (0..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular SIP entity's other common "This object contains the number of transactions awaiting
statistics. definitive (non-1xx) response. In the case of a forked
request, each branch counts as a single transaction
corresponding to the entity identified by applIndex."
::= { sipCommonTransCurrentEntry 1 }
Each row represents those objects for a particular SIP --
entity present in this system. applIndex is used to -- SIP Retry Statistics
uniquely identify these instances of SIP entities and --
correlate them through the common framework of the -- This group contains various statistic objects about
NETWORK-SERVICES-MIB (RFC 2788)." -- retransmission counts.
INDEX { applIndex }
::= { sipOtherStatsTable 1 }
SipOtherStatsEntry ::= --
SEQUENCE { sipCommonStatsRetryTable OBJECT-TYPE
sipNumUnsupportedUris Counter32, SYNTAX SEQUENCE OF SipCommonStatsRetryEntry
sipNumUnsupportedMethods Counter32, MAX-ACCESS not-accessible
sipOtherwiseDiscardedMsgs Counter32 STATUS current
} DESCRIPTION
"This table contains retry statistics objects applicable to each
SIP entity in this system."
::= { sipCommonStatsRetry 1 }
sipNumUnsupportedUris OBJECT-TYPE sipCommonStatsRetryEntry OBJECT-TYPE
SYNTAX Counter32 SYNTAX SipCommonStatsRetryEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of RequestURIs received with unsupported scheme. "A row of retry statistics.
A server normally responds to such requests with a 400
Bad Request status code."
::= { sipOtherStatsEntry 1 }
sipNumUnsupportedMethods OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX Counter32 present in this system. applIndex is used to uniquely identify
MAX-ACCESS read-only these instances of SIP entities and correlate them through the
STATUS current common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION INDEX { applIndex, sipCommonStatsRetryMethod }
"Number of SIP requests received with unsupported ::= { sipCommonStatsRetryTable 1 }
methods.
A server normally responds to such requests with a
501 (Not Implemented) or 405 (Method Not Allowed)."
::= { sipOtherStatsEntry 2 }
sipOtherwiseDiscardedMsgs OBJECT-TYPE SipCommonStatsRetryEntry ::= SEQUENCE {
SYNTAX Counter32 sipCommonStatsRetryMethod SipTCMethodName,
MAX-ACCESS read-only sipCommonStatsRetries Counter32,
STATUS current sipCommonStatsRetryFinalResponses Counter32,
DESCRIPTION sipCommonStatsRetryNonFinalResponses Counter32,
"Number of SIP messages received that for any number sipCommonStatsRetryDisconTime TimeStamp
of reasons was discarded without a response." }
::= { sipOtherStatsEntry 3 }
-- sipCommonStatsRetryMethod OBJECT-TYPE
-- Notification related objects SYNTAX SipTCMethodName
-- MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object uniquely identifies the SIP method related to the
objects in a row."
::= { sipCommonStatsRetryEntry 1 }
-- sipCommonStatsRetries OBJECT-TYPE
-- Status code related notification objects. SYNTAX Counter32
-- MAX-ACCESS read-only
sipStatusCodeNotifTo OBJECT-TYPE STATUS current
SYNTAX SnmpAdminString DESCRIPTION
MAX-ACCESS accessible-for-notify "This object reflects the total number of request
STATUS current retransmissions that have been sent by the SIP entity. Note
DESCRIPTION that there could be multiple retransmissions per request.
"This object contains the value of the To header in the
message containing the status code that caused the
notification. The header name will be part of
this object value.
For example, 'To: Watson '."
::= { sipCommonNotifObjects 1 }
sipStatusCodeNotifFrom OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX SnmpAdminString re-initialization of the SIP entity or service. A Management
MAX-ACCESS accessible-for-notify Station can detect discontinuities in this counter by
STATUS current monitoring the sipCommonStatsRetryDisconTime object in the same
DESCRIPTION row."
"This object contains the value of the From header in the ::= { sipCommonStatsRetryEntry 2 }
message containing the status code that caused the
notification. The header name will be part of
this object value.
For example, 'From: Watson '."
::= { sipCommonNotifObjects 2 }
sipStatusCodeNotifCallId OBJECT-TYPE sipCommonStatsRetryFinalResponses OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX Counter32
MAX-ACCESS accessible-for-notify MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the CallId in the "This object reflects the total number of Final Response retries
message containing the status code that caused the that have been sent by the SIP entity. Note that there could
notification. The header name will be part of be multiple retransmissions per request.
this object value.
For example, 'Call-ID: 5551212@example.com'."
::= { sipCommonNotifObjects 3 }
sipStatusCodeNotifCSeq OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX Unsigned32 re-initialization of the SIP entity or service. A Management
MAX-ACCESS accessible-for-notify Station can detect discontinuities in this counter by
STATUS current monitoring the sipCommonStatsRetryDisconTime object in the same
DESCRIPTION row."
"This object contains the CSeq value in the message ::= { sipCommonStatsRetryEntry 3 }
containing the status code that caused the notification.
The header name will be part of this object value.
For example, 'CSeq: 1722 INVITE'."
::= { sipCommonNotifObjects 4 }
-- sipCommonStatsRetryNonFinalResponses OBJECT-TYPE
-- General notification related objects. SYNTAX Counter32
-- MAX-ACCESS read-only
sipNotifApplIndex OBJECT-TYPE STATUS current
SYNTAX Unsigned32 (1..2147483647) DESCRIPTION
MAX-ACCESS accessible-for-notify "This object reflects the total number of non-Final RResponse
STATUS current retries that have been sent by the SIP entity.
DESCRIPTION
"This object contains the applIndex as described
in RFC 2788. This object is created in order to
allow a variable binding containing a value of
applIndex in a notification."
::= { sipCommonNotifObjects 5 }
sipNotifSequenceNumber OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX Unsigned32 (1..2147483647) re-initialization of the SIP entity or service. A Management
MAX-ACCESS accessible-for-notify Station can detect discontinuities in this counter by
STATUS current monitoring the sipCommonStatsRetryDisconTime object in the same
DESCRIPTION row."
"This object contains a sequence number for each ::= { sipCommonStatsRetryEntry 4 }
notification generated by this SIP entity. Each
notification SHOULD have a unique sequence number.
A network manager can use this information to
determine whether notifications from a particular
SIP entity have been missed. The value of this
object MUST start at 1 and increase by one with
each generated notification. If a system restarts,
the sequence number MAY start again from 1."
::= { sipCommonNotifObjects 6 }
-- sipCommonStatsRetryDisconTime OBJECT-TYPE
-- Notifications SYNTAX TimeStamp
-- MAX-ACCESS read-only
sipStatusCodeNotif NOTIFICATION-TYPE STATUS current
OBJECTS { DESCRIPTION
sipNotifSequenceNumber, "The value of the sysUpTime object when the counters for the
sipNotifApplIndex, retry statistics objects in this row last experienced a
sipStatusCodeNotifTo, discontinuity."
sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId,
sipStatusCodeNotifCSeq,
sipStatusCodeIns,
sipStatusCodeOuts
}
STATUS current
DESCRIPTION
"Signifies that a specific status code has been sent
or received by the system."
::= { sipCommonMIBNotifs 1 }
sipStatusCodeThreshExceededInNotif NOTIFICATION-TYPE ::= { sipCommonStatsRetryEntry 5 }
OBJECTS {
sipNotifSequenceNumber,
sipNotifApplIndex,
sipStatusCodeIns
}
STATUS current
DESCRIPTION
"Signifies that a specific status code was found to
have been received by the system enough to
exceed the configured threshold. This notification
can be used as an early warning mechanism in lieu
of using sipStatusCodeNotif."
::= { sipCommonMIBNotifs 2 }
sipStatusCodeThreshExceededOutNotif NOTIFICATION-TYPE --
OBJECTS { -- Other Common Statistics
sipNotifSequenceNumber, --
sipNotifApplIndex, sipCommonOtherStatsTable OBJECT-TYPE
sipStatusCodeOuts SYNTAX SEQUENCE OF SipCommonOtherStatsEntry
} MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that a specific status code was found to "This table contains other common statistics supported by each
have been sent by the system enough to SIP entity in this system."
exceed the configured threshold. This notification ::= { sipCommonOtherStats 1 }
can be used as an early warning mechanism in lieu
of using sipStatusCodeNotif."
::= { sipCommonMIBNotifs 3 }
sipServiceColdStart NOTIFICATION-TYPE sipCommonOtherStatsEntry OBJECT-TYPE
OBJECTS { SYNTAX SipCommonOtherStatsEntry
sipNotifSequenceNumber, MAX-ACCESS not-accessible
sipNotifApplIndex, STATUS current
sipServiceStartTime DESCRIPTION
} "Information on a particular SIP entity's other common
STATUS current statistics.
DESCRIPTION
"Signifies that the SIP service has reinitialized
itself or started for the first time. This SHOULD
result from a hard 'down' to 'up' administrative
status change.
The configuration or behavior of the service
MAY be altered."
::= { sipCommonMIBNotifs 4 }
sipServiceWarmStart NOTIFICATION-TYPE Each row represents those objects for a particular SIP entity
OBJECTS { present in this system. applIndex is used to uniquely identify
sipNotifSequenceNumber, these instances of SIP entities and correlate them through the
sipNotifApplIndex, common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
sipServiceLastChange INDEX { applIndex }
} ::= { sipCommonOtherStatsTable 1 }
STATUS current
DESCRIPTION
"Signifies that the SIP service has reinitialized
itself and is restarting after an administrative
'reset'. The configuration or behavior of the service
MAY be altered."
::= { sipCommonMIBNotifs 5 }
sipServiceStatusChanged NOTIFICATION-TYPE SipCommonOtherStatsEntry ::= SEQUENCE {
OBJECTS { sipCommonOtherStatsNumUnsupportedUris Counter32,
sipNotifSequenceNumber, sipCommonOtherStatsNumUnsupportedMethods Counter32,
sipNotifApplIndex, sipCommonOtherStatsOtherwiseDiscardedMsgs Counter32,
sipServiceLastChange, sipCommonOtherStatsDisconTime TimeStamp
sipServiceOperStatus }
}
STATUS current
DESCRIPTION
"Signifies that the SIP service operational status
has changed."
::= { sipCommonMIBNotifs 6 }
-- sipCommonOtherStatsNumUnsupportedUris OBJECT-TYPE
-- Conformance SYNTAX Counter32
-- MAX-ACCESS read-only
sipCommonMIBCompliances STATUS current
OBJECT IDENTIFIER ::= { sipCommonMIBConform 1 } DESCRIPTION
sipCommonMIBGroups "Number of RequestURIs received with unsupported scheme. A
OBJECT IDENTIFIER ::= { sipCommonMIBConform 2 } server normally responds to such requests with a 400 Bad
Request status code.
-- Discontinuities in the value of this counter can occur at
-- Compliance Statements re-initialization of the SIP entity or service. A Management
-- Station can detect discontinuities in this counter by
sipCommonCompliance MODULE-COMPLIANCE monitoring the sipCommonOtherStatsDisconTime object in the same
STATUS current row."
DESCRIPTION ::= { sipCommonOtherStatsEntry 1 }
"The compliance statement for SIP entities."
MODULE -- this module sipCommonOtherStatsNumUnsupportedMethods OBJECT-TYPE
MANDATORY-GROUPS { sipCommonConfigGroup, SYNTAX Counter32
sipCommonStatsGroup } MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of SIP requests received with unsupported methods. A
server normally responds to such requests with a 501 (Not
Implemented) or 405 (Method Not Allowed).
GROUP sipCommonInformationalGroup Discontinuities in the value of this counter can occur at
DESCRIPTION re-initialization of the SIP entity or service. A Management
"This group is OPTIONAL. A SIP entity can elect to Station can detect discontinuities in this counter by
not provide any support for these objects as they monitoring the sipCommonOtherStatsDisconTime object in the same
provide optional information." row."
::= { sipCommonOtherStatsEntry 2 }
GROUP sipCommonConfigTimerGroup sipCommonOtherStatsOtherwiseDiscardedMsgs OBJECT-TYPE
DESCRIPTION SYNTAX Counter32
"This group is OPTIONAL. A SIP entity can elect to MAX-ACCESS read-only
not provide any timer configuration." STATUS current
DESCRIPTION
"Number of SIP messages received that for any number of reasons
was discarded without a response.
GROUP sipCommonStatsRetryGroup Discontinuities in the value of this counter can occur at
DESCRIPTION re-initialization of the SIP entity or service. A Management
"This group is OPTIONAL. A SIP entity can elect to Station can detect discontinuities in this counter by
not provide any retry statistics." monitoring the sipCommonOtherStatsDisconTime object in the same
row."
::= { sipCommonOtherStatsEntry 3 }
GROUP sipCommonNotifGroup sipCommonOtherStatsDisconTime OBJECT-TYPE
DESCRIPTION SYNTAX TimeStamp
"This group is OPTIONAL. A SIP entity can elect to MAX-ACCESS read-only
not provide any notifications. If implemented, the STATUS current
sipCommonStatusCodeNotifGroup and DESCRIPTION
sipCommonNotifObjectsGroup MUST also be implemented." "The value of the sysUpTime object when the counters for the
statistics objects in this row last experienced a
discontinuity."
::= { sipCommonOtherStatsEntry 4 }
GROUP sipCommonStatusCodeNotifGroup --
DESCRIPTION -- Notification related objects
"This group is OPTIONAL. A SIP entity can elect to --
not provide any notifications. If implemented, the --
sipCommonNotifGroup and sipCommonNotifObjectsGroup -- Status code related notification objects.
MUST also be implemented." --
sipCommonStatusCodeNotifTo OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This object contains the value of the To header in the message
containing the status code that caused the notification. The
header name will be part of this object value. For example,
'To: Watson '."
::= { sipCommonNotifObjects 1 }
GROUP sipCommonNotifObjectsGroup sipCommonStatusCodeNotifFrom OBJECT-TYPE
DESCRIPTION SYNTAX SnmpAdminString
"This group is OPTIONAL. A SIP entity can elect to MAX-ACCESS accessible-for-notify
not provide any notifications. If implemented, the STATUS current
sipCommonStatusCodeNotifGroup and DESCRIPTION
sipCommonNotifGroup MUST also be implemented." "This object contains the value of the From header in the
message containing the status code that caused the
notification. The header name will be part of this object
value. For example, 'From: Watson '."
::= { sipCommonNotifObjects 2 }
::= { sipCommonMIBCompliances 1 } sipCommonStatusCodeNotifCallId OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This object contains the value of the Call-ID in the message
containing the status code that caused the notification. The
header name will be part of this object value. For example,
'Call-ID: 5551212@example.com'."
::= { sipCommonNotifObjects 3 }
-- sipCommonStatusCodeNotifCSeq OBJECT-TYPE
-- Units of Conformance SYNTAX Unsigned32
-- MAX-ACCESS accessible-for-notify
sipCommonConfigGroup OBJECT-GROUP STATUS current
OBJECTS { DESCRIPTION
sipProtocolVersion, "This object contains the CSeq value in the message containing
sipServiceOperStatus, the status code that caused the notification. The header name
sipServiceStartTime, will be part of this object value. For example, 'CSeq: 1722
sipServiceLastChange, INVITE'."
sipTransportRcv, ::= { sipCommonNotifObjects 4 }
sipOptionTag,
sipOptionTagHeaderField,
sipMaxTransactions,
sipServiceNotifEnable,
sipEntityType,
sipMethodName
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration common
to all SIP entities."
::= { sipCommonMIBGroups 1 }
sipCommonInformationalGroup OBJECT-GROUP --
OBJECTS { -- General notification related objects.
sipOrganization --
} sipCommonNotifApplIndex OBJECT-TYPE
STATUS current SYNTAX Unsigned32 (1..2147483647)
DESCRIPTION MAX-ACCESS accessible-for-notify
"A collection of objects providing configuration STATUS current
common to all SIP entities." DESCRIPTION
::= { sipCommonMIBGroups 2 } "This object contains the applIndex as described in RFC 2788.
This object is created in order to allow a variable binding
containing a value of applIndex in a notification."
::= { sipCommonNotifObjects 5 }
sipCommonConfigTimerGroup OBJECT-GROUP sipCommonNotifSequenceNumber OBJECT-TYPE
OBJECTS { SYNTAX Unsigned32 (1..2147483647)
sipCfgTimerA, MAX-ACCESS accessible-for-notify
sipCfgTimerB, STATUS current
sipCfgTimerC, DESCRIPTION
sipCfgTimerD, "This object contains a sequence number for each notification
sipCfgTimerE, generated by this SIP entity. Each notification SHOULD have a
sipCfgTimerF, unique sequence number. A network manager can use this
sipCfgTimerG, information to determine whether notifications from a
sipCfgTimerH, particular SIP entity have been missed. The value of this
sipCfgTimerI, object MUST start at 1 and increase by one with each generated
sipCfgTimerJ, notification. If a system restarts, the sequence number MAY
sipCfgTimerK, start again from 1."
sipCfgTimerT1, ::= { sipCommonNotifObjects 6 }
sipCfgTimerT2,
sipCfgTimerT4
}
STATUS current
DESCRIPTION
"A collection of objects providing timer configuration
common to all SIP entities."
::= { sipCommonMIBGroups 3 }
sipCommonStatsGroup OBJECT-GROUP --
OBJECTS { -- Notifications
sipSummaryInRequests, --
sipSummaryOutRequests, sipCommonStatusCodeNotif NOTIFICATION-TYPE
sipSummaryInResponses, OBJECTS {
sipSummaryOutResponses, sipCommonNotifSequenceNumber,
sipSummaryTotalTransactions, sipCommonNotifApplIndex,
sipStatsOutbounds, sipCommonStatusCodeNotifTo,
sipStatsInbounds, sipCommonStatusCodeNotifFrom,
sipStatusCodeIns, sipCommonStatusCodeNotifCallId,
sipStatusCodeOuts, sipCommonStatusCodeNotifCSeq,
sipStatusCodeRowStatus, sipCommonStatusCodeIns,
sipCurrentTransactions, sipCommonStatusCodeOuts
sipNumUnsupportedUris, }
sipNumUnsupportedMethods, STATUS current
sipOtherwiseDiscardedMsgs DESCRIPTION
} "Signifies that a specific status code has been sent or received
STATUS current by the system."
DESCRIPTION ::= { sipCommonMIBNotifications 1 }
"A collection of objects providing statistics common
to all SIP entities."
::= { sipCommonMIBGroups 4 }
sipCommonStatsRetryGroup OBJECT-GROUP sipCommonStatusCodeThreshExceededInNotif NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipStatsRetries, sipCommonNotifSequenceNumber,
sipStatsRetryFinalResponses, sipCommonNotifApplIndex,
sipStatsRetryNonFinalResponses sipCommonStatusCodeIns
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing retry statistics." "Signifies that a specific status code was found to have been
::= { sipCommonMIBGroups 5 } received by the system enough to exceed the configured
threshold. This notification can be used as an early warning
mechanism in lieu of using sipCommonStatusCodeNotif."
::= { sipCommonMIBNotifications 2 }
sipCommonNotifGroup NOTIFICATION-GROUP sipCommonStatusCodeThreshExceededOutNotif NOTIFICATION-TYPE
NOTIFICATIONS { OBJECTS {
sipStatusCodeNotif, sipCommonNotifSequenceNumber,
sipStatusCodeThreshExceededInNotif, sipCommonNotifApplIndex,
sipStatusCodeThreshExceededOutNotif, sipCommonStatusCodeOuts
sipServiceColdStart, }
sipServiceWarmStart, STATUS current
sipServiceStatusChanged DESCRIPTION
} "Signifies that a specific status code was found to have been
STATUS current sent by the system enough to exceed the configured threshold.
DESCRIPTION This notification can be used as an early warning mechanism in
"A collection of notifications common to all SIP lieu of using sipCommonStatusCodeNotif."
entities." ::= { sipCommonMIBNotifications 3 }
::= { sipCommonMIBGroups 6 }
sipCommonStatusCodeNotifGroup OBJECT-GROUP sipCommonServiceColdStart NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipStatusCodeNotifSend, sipCommonNotifSequenceNumber,
sipStatusCodeNotifEmitMode, sipCommonNotifApplIndex,
sipStatusCodeNotifThresh, sipCommonCfgServiceStartTime
sipStatusCodeNotifInterval }
} STATUS current
STATUS current DESCRIPTION
DESCRIPTION "Signifies that the SIP service has reinitialized itself or
"A collection of objects related to controlling and started for the first time. This SHOULD result from a hard
attribution of notifications common to all SIP 'down' to 'up' administrative status change. The configuration
entities." or behavior of the service MAY be altered."
::= { sipCommonMIBGroups 7 } ::= { sipCommonMIBNotifications 4 }
sipCommonNotifObjectsGroup OBJECT-GROUP sipCommonServiceWarmStart NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipStatusCodeNotifTo, sipCommonNotifSequenceNumber,
sipStatusCodeNotifFrom, sipCommonNotifApplIndex,
sipStatusCodeNotifCallId, sipCommonCfgServiceLastChange
sipStatusCodeNotifCSeq, }
sipNotifApplIndex, STATUS current
sipNotifSequenceNumber DESCRIPTION
} "Signifies that the SIP service has reinitialized itself and is
STATUS current restarting after an administrative 'reset'. The configuration
DESCRIPTION or behavior of the service MAY be altered."
"A collection of accessible-for-notify objects ::= { sipCommonMIBNotifications 5 }
related to the notification defined in this
MIB module."
::= { sipCommonMIBGroups 8 }
END sipCommonServiceStatusChanged NOTIFICATION-TYPE
OBJECTS {
sipCommonNotifSequenceNumber,
sipCommonNotifApplIndex,
sipCommonCfgServiceLastChange,
sipCommonCfgServiceOperStatus
}
STATUS current
DESCRIPTION
"Signifies that the SIP service operational status has changed."
::= { sipCommonMIBNotifications 6 }
--
-- Conformance
--
sipCommonMIBCompliances
OBJECT IDENTIFIER ::= { sipCommonMIBConformance 1 }
sipCommonMIBGroups
OBJECT IDENTIFIER ::= { sipCommonMIBConformance 2 }
--
-- Compliance Statements
--
sipCommonCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SIP entities."
MODULE -- this module
MANDATORY-GROUPS { sipCommonConfigGroup,
sipCommonStatsGroup
}
OBJECT sipCommonStatusCodeRowStatus
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not required."
OBJECT sipCommonCfgServiceNotifEnable
MIN-ACCESS not-accessible
DESCRIPTION
"This object is optional and does not need to be supported."
GROUP sipCommonInformationalGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to not provide
any support for these objects as they provide optional
information."
GROUP sipCommonConfigTimerGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to not provide
any timer configuration."
GROUP sipCommonStatsRetryGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to not provide
any retry statistics."
GROUP sipCommonNotifGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to not provide
any notifications. If implemented, the
sipCommonStatusCodeNotifGroup and sipCommonNotifObjectsGroup
MUST also be implemented."
GROUP sipCommonStatusCodeNotifGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to not provide
any notifications. If implemented, the sipCommonNotifGroup and
sipCommonNotifObjectsGroup MUST also be implemented."
GROUP sipCommonNotifObjectsGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to not provide
any notifications. If implemented, the
sipCommonStatusCodeNotifGroup and sipCommonNotifGroup MUST also
be implemented."
::= { sipCommonMIBCompliances 1 }
--
-- Units of Conformance
--
sipCommonConfigGroup OBJECT-GROUP
OBJECTS {
sipCommonCfgProtocolVersion,
sipCommonCfgServiceOperStatus,
sipCommonCfgServiceStartTime,
sipCommonCfgServiceLastChange,
sipCommonPortTransportRcv,
sipCommonOptionTag,
sipCommonOptionTagHeaderField,
sipCommonCfgMaxTransactions,
sipCommonCfgServiceNotifEnable,
sipCommonCfgEntityType,
sipCommonMethodSupportedName
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration common to all
SIP entities."
::= { sipCommonMIBGroups 1 }
sipCommonInformationalGroup OBJECT-GROUP
OBJECTS {
sipCommonCfgOrganization
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration common to all
SIP entities."
::= { sipCommonMIBGroups 2 }
sipCommonConfigTimerGroup OBJECT-GROUP
OBJECTS {
sipCommonCfgTimerA,
sipCommonCfgTimerB,
sipCommonCfgTimerC,
sipCommonCfgTimerD,
sipCommonCfgTimerE,
sipCommonCfgTimerF,
sipCommonCfgTimerG,
sipCommonCfgTimerH,
sipCommonCfgTimerI,
sipCommonCfgTimerJ,
sipCommonCfgTimerK,
sipCommonCfgTimerT1,
sipCommonCfgTimerT2,
sipCommonCfgTimerT4
}
STATUS current
DESCRIPTION
"A collection of objects providing timer configuration common to
all SIP entities."
::= { sipCommonMIBGroups 3 }
sipCommonStatsGroup OBJECT-GROUP
OBJECTS {
sipCommonSummaryInRequests,
sipCommonSummaryOutRequests,
sipCommonSummaryInResponses,
sipCommonSummaryOutResponses,
sipCommonSummaryTotalTransactions,
sipCommonSummaryDisconTime,
sipCommonMethodStatsOutbounds,
sipCommonMethodStatsInbounds,
sipCommonMethodStatsDisconTime,
sipCommonStatusCodeIns,
sipCommonStatusCodeOuts,
sipCommonStatusCodeRowStatus,
sipCommonStatusCodeDisconTime,
sipCommonTransCurrentactions,
sipCommonOtherStatsNumUnsupportedUris,
sipCommonOtherStatsNumUnsupportedMethods,
sipCommonOtherStatsOtherwiseDiscardedMsgs,
sipCommonOtherStatsDisconTime
}
STATUS current
DESCRIPTION
"A collection of objects providing statistics common to all SIP
entities."
::= { sipCommonMIBGroups 4 }
sipCommonStatsRetryGroup OBJECT-GROUP
OBJECTS {
sipCommonStatsRetries,
sipCommonStatsRetryFinalResponses,
sipCommonStatsRetryNonFinalResponses,
sipCommonStatsRetryDisconTime
}
STATUS current
DESCRIPTION
"A collection of objects providing retry statistics."
::= { sipCommonMIBGroups 5 }
sipCommonNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS {
sipCommonStatusCodeNotif,
sipCommonStatusCodeThreshExceededInNotif,
sipCommonStatusCodeThreshExceededOutNotif,
sipCommonServiceColdStart,
sipCommonServiceWarmStart,
sipCommonServiceStatusChanged
}
STATUS current
DESCRIPTION
"A collection of notifications common to all SIP entities."
::= { sipCommonMIBGroups 6 }
sipCommonStatusCodeNotifGroup OBJECT-GROUP
OBJECTS {
sipCommonStatusCodeNotifSend,
sipCommonStatusCodeNotifEmitMode,
sipCommonStatusCodeNotifThresh,
sipCommonStatusCodeNotifInterval
}
STATUS current
DESCRIPTION
"A collection of objects related to controlling and attribution
of notifications common to all SIP entities."
::= { sipCommonMIBGroups 7 }
sipCommonNotifObjectsGroup OBJECT-GROUP
OBJECTS {
sipCommonStatusCodeNotifTo,
sipCommonStatusCodeNotifFrom,
sipCommonStatusCodeNotifCallId,
sipCommonStatusCodeNotifCSeq,
sipCommonNotifApplIndex,
sipCommonNotifSequenceNumber
}
STATUS current
DESCRIPTION
"A collection of accessible-for-notify objects related to the
notification defined in this MIB module."
::= { sipCommonMIBGroups 8 }
END
7.3. SIP User Agent MIB Module 7.3. SIP User Agent MIB Module
SIP-UA-MIB DEFINITIONS ::= BEGIN SIP-UA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Unsigned32, Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
applIndex applIndex
FROM NETWORK-SERVICES-MIB -- RFC 2788 FROM NETWORK-SERVICES-MIB -- RFC 2788
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB -- RFC 4001 FROM INET-ADDRESS-MIB -- RFC 4001
SipEntityRole SipTCEntityRole
FROM SIP-TC; FROM SIP-TC-MIB;
sipUAMIB MODULE-IDENTITY sipUAMIB MODULE-IDENTITY
LAST-UPDATED "200605171700Z" LAST-UPDATED "200609121700Z"
ORGANIZATION "IETF Session Initiation Protocol ORGANIZATION "IETF Session Initiation Protocol Working Group"
Working Group" CONTACT-INFO
CONTACT-INFO "SIP WG email: sip@ietf.org
"SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
Co-editor Joon Maeng Co-editor Joon Maeng
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 858 Coal Creek Circle postal: 858 Coal Creek Circle
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 9100 phone: +1 303 661 9100
Co-editor Dave Walker Co-editor Dave Walker
email: drwalker@rogers.com" email: drwalker@rogers.com"
DESCRIPTION DESCRIPTION
"Session Initiation Protocol (SIP) User Agent (UA) "Session Initiation Protocol (SIP) User Agent (UA) MIB module.
MIB module.
SIP is an application-layer signaling protocol for SIP is an application-layer signaling protocol for creating,
creating, modifying and terminating multimedia modifying and terminating multimedia sessions with one or more
sessions with one or more participants. These sessions participants. These sessions include Internet multimedia
include Internet multimedia conferences and Internet conferences and Internet telephone calls. SIP is defined in
telephone calls. SIP is defined in RFC 3261 (June RFC 3261 (June 2002).
2002).
A User Agent is an application that contains both a A User Agent is an application that contains both a User Agent
User Agent Client (UAC) and a User Agent Server (UAS). Client (UAC) and a User Agent Server (UAS). A UAC is an
A UAC is an application that initiates a SIP request. application that initiates a SIP request. A UAS is an
A UAS is an application that contacts the user when a application that contacts the user when a SIP request is
SIP request is received and that returns a response on received and that returns a response on behalf of the user.
behalf of the user. The response accepts, rejects, or The response accepts, rejects, or redirects the request.
redirects the request.
Copyright (C) The Internet Society (2006). This version Copyright (C) The Internet Society (2006). This version of
of this MIB module is part of RFC XXXX; see the RFC this MIB module is part of RFC XXXX; see the RFC itself for
itself for full legal notices." 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 "200605171700Z" REVISION "200609121700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-UA-MIB module. "Initial version of the IETF SIP-UA-MIB module. This version
This version published as part of RFC XXXX." published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX3 } ::= { mib-2 XXX3 }
-- RFC Ed: replace XXX3 with actual IANA assigned number -- RFC Ed: replace XXX3 with actual IANA assigned number
-- RFC Ed: and remove these notes -- RFC Ed: and remove these notes
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipUAMIBObjects OBJECT IDENTIFIER ::= { sipUAMIB 1 } sipUAMIBObjects OBJECT IDENTIFIER ::= { sipUAMIB 1 }
sipUAMIBConform OBJECT IDENTIFIER ::= { sipUAMIB 2 } sipUAMIBConformance OBJECT IDENTIFIER ::= { sipUAMIB 2 }
-- --
-- This MIB contains objects related to SIP User Agents. -- This MIB contains objects related to SIP User Agents.
-- --
sipUACfgServer OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 } sipUACfgServer OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 }
-- --
-- SIP Server Configuration -- SIP Server Configuration
-- --
sipUACfgServerTable OBJECT-TYPE sipUACfgServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUACfgServerEntry SYNTAX SEQUENCE OF SipUACfgServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains SIP server configuration objects "This table contains SIP server configuration objects applicable
applicable to each SIP user agent in this system." to each SIP user agent in this system."
::= { sipUACfgServer 1 } ::= { sipUACfgServer 1 }
sipUACfgServerEntry OBJECT-TYPE sipUACfgServerEntry OBJECT-TYPE
SYNTAX SipUACfgServerEntry SYNTAX SipUACfgServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of server configuration. "A row of server configuration.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP user
user agent present in this system. applIndex is used to agent present in this system. applIndex is used to uniquely
uniquely identify these instances of SIP user agents and identify these instances of SIP user agents and correlate them
correlate them through the common framework of the through the common framework of the NETWORK-SERVICES-MIB (RFC
NETWORK-SERVICES-MIB (RFC 2788). The same value of 2788). The same value of applIndex used in the corresponding
applIndex used in the corresponding SIP-COMMON-MIB is SIP-COMMON-MIB is used here."
used here. INDEX { applIndex, sipUACfgServerIndex }
The objects in this table entry SHOULD be non-volatile ::= { sipUACfgServerTable 1 }
and their value SHOULD be kept at reboot."
INDEX { applIndex, sipUACfgServerIndex }
::= { sipUACfgServerTable 1 }
SipUACfgServerEntry ::= SipUACfgServerEntry ::= SEQUENCE {
SEQUENCE { sipUACfgServerIndex Unsigned32,
sipUACfgServerIndex Unsigned32, sipUACfgServerAddressType InetAddressType,
sipUACfgServerAddrType InetAddressType, sipUACfgServerAddress InetAddress,
sipUACfgServerAddr InetAddress, sipUACfgServerRole SipTCEntityRole
sipUACfgServerFunction SipEntityRole }
}
sipUACfgServerIndex OBJECT-TYPE sipUACfgServerIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique identifier of a server address when "A unique identifier of a server address when multiple addresses
multiple addresses are configured by the SIP entity. are configured by the SIP entity. If one address isn't
If one address isn't reachable, then another can reachable, then another can be tried."
be tried." ::= { sipUACfgServerEntry 1 }
::= { sipUACfgServerEntry 1 }
sipUACfgServerAddrType OBJECT-TYPE sipUACfgServerAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the type of address contained "This object reflects the type of address contained in the
in the associated instance of sipUACfgServerAddr." associated instance of sipUACfgServerAddress."
REFERENCE "INET-ADDRESS-MIB (RFC 4001)" REFERENCE
::= { sipUACfgServerEntry 2 } "INET-ADDRESS-MIB (RFC 4001)"
::= { sipUACfgServerEntry 2 }
sipUACfgServerAddr OBJECT-TYPE sipUACfgServerAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the address of a SIP server "This object reflects the address of a SIP server this user
this user agent will use to proxy/redirect calls." agent will use to proxy/redirect calls. The type of this
REFERENCE "INET-ADDRESS-MIB (RFC 4001)" address is determined by the value of the
::= { sipUACfgServerEntry 3 } sipUACfgServerAddressType object."
REFERENCE "INET-ADDRESS-MIB (RFC 4001)"
::= { sipUACfgServerEntry 3 }
sipUACfgServerFunction OBJECT-TYPE sipUACfgServerRole OBJECT-TYPE
SYNTAX SipEntityRole SYNTAX SipTCEntityRole
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the function of the SIP server "This object reflects the function of the SIP server this user
this user agent should communicate with: registrar, agent should communicate with: registrar, proxy (outbound
proxy (outbound proxy), etc." proxy), etc."
::= { sipUACfgServerEntry 4 } ::= { sipUACfgServerEntry 4 }
-- --
-- Conformance -- Conformance
-- --
sipUAMIBCompliances sipUAMIBCompliances OBJECT IDENTIFIER ::= { sipUAMIBConformance 1 }
OBJECT IDENTIFIER ::= { sipUAMIBConform 1 } sipUAMIBGroups OBJECT IDENTIFIER ::= { sipUAMIBConformance 2 }
sipUAMIBGroups
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 that implement the
MODULE -- this module SIP-UA-MIB module."
MANDATORY-GROUPS { sipUAConfigGroup } MODULE -- this module
MANDATORY-GROUPS { sipUAConfigGroup }
::= { sipUAMIBCompliances 1 } ::= { sipUAMIBCompliances 1 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipUAConfigGroup OBJECT-GROUP sipUAConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipUACfgServerAddrType, sipUACfgServerAddressType,
sipUACfgServerAddr, sipUACfgServerAddress,
sipUACfgServerFunction sipUACfgServerRole
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration for "A collection of objects providing information about the
SIP User Agents." configuration of SIP User Agents."
::= { sipUAMIBGroups 1 } ::= { sipUAMIBGroups 1 }
END END
7.4. SIP Server MIB Module (Proxy, Redirect and Registrar Servers) 7.4. SIP Server MIB Module (Proxy, Redirect and Registrar Servers)
SIP-SERVER-MIB DEFINITIONS ::= BEGIN
SIP-SERVER-MIB DEFINITIONS ::= BEGIN IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
Counter32,
Unsigned32,
Gauge32,
mib-2
FROM SNMPv2-SMI -- RFC 2578
IMPORTS TruthValue,
MODULE-IDENTITY, TimeStamp, DateAndTime
OBJECT-TYPE, FROM SNMPv2-TC -- RFC 2579
Counter32,
Unsigned32,
Gauge32,
mib-2
FROM SNMPv2-SMI -- RFC 2578
TruthValue,
TimeStamp, DateAndTime
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM SNMP-FRAMEWORK-MIB -- RFC 3411
applIndex applIndex
FROM NETWORK-SERVICES-MIB -- RFC 2788 FROM NETWORK-SERVICES-MIB -- RFC 2788
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB; -- RFC 4001 FROM INET-ADDRESS-MIB; -- RFC 4001
sipServerMIB MODULE-IDENTITY sipServerMIB MODULE-IDENTITY
LAST-UPDATED "200605171700Z" LAST-UPDATED "200609121700Z"
ORGANIZATION "IETF Session Initiation Protocol ORGANIZATION "IETF Session Initiation Protocol
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor: Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
Co-editor Joon Maeng Co-editor: Joon Maeng
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule Co-editor: Jean-Francois Mule
CableLabs CableLabs
postal: 858 Coal Creek Circle postal: 858 Coal Creek Circle
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 9100 phone: +1 303 661 9100
Co-editor Dave Walker Co-editor: Dave Walker
email: drwalker@rogers.com" email: drwalker@rogers.com
DESCRIPTION "
"Session Initiation Protocol (SIP) Server MIB module. DESCRIPTION
SIP is an application-layer signaling protocol for "Session Initiation Protocol (SIP) Server MIB module. SIP is an
creating, modifying and terminating multimedia application-layer signaling protocol for creating, modifying
sessions with one or more participants. These and terminating multimedia sessions with one or more
sessions include Internet multimedia conferences and participants. These sessions include Internet multimedia
Internet telephone calls. SIP is defined in conferences and Internet telephone calls. SIP is defined in
RFC 3261 (June 2002). RFC 3261 (June 2002).
This MIB is defined for the management of SIP Proxy, This MIB is defined for the management of SIP Proxy, Redirect
Redirect and Registrar Servers. 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
It accepts requests from other clients, either requests from other clients, either responding to them or
responding to them or passing them on to other 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
returns zero or more addresses to that client. zero or more addresses to that client. Unlike a User Agent
Unlike a User Agent Server it does not accept calls. Server it does not accept calls.
A Registrar is a server that accepts REGISTER A Registrar is a server that accepts REGISTER requests. A
requests. A Registrar is typically co-located with Registrar is typically co-located with a Proxy or Redirect
a Proxy or Redirect Server. Server.
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006). This version of
This version of this MIB module is part of RFC XXXX; this MIB module is part of RFC XXXX; see the RFC itself for
see the RFC itself for full legal notices." 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 "200605171700Z" REVISION "200609121700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-SERVER-MIB module. "Initial version of the IETF SIP-SERVER-MIB module. This
This version published as part of RFC XXXX." version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX4 } ::= { mib-2 XXX4 }
-- RFC Ed: replace XXX4 with actual IANA assigned number -- RFC Ed: replace XXX4 with actual IANA assigned number
-- and remove this note -- and remove this note
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 }
sipServerMIBConform OBJECT IDENTIFIER ::= { sipServerMIB 2 }
-- sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 }
-- These groups contain objects common to all SIP servers. sipServerMIBConformance OBJECT IDENTIFIER ::= { sipServerMIB 2 }
--
sipServerCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 1 }
-- --
-- Common Server Configuration Objects -- These groups contain objects common to all SIP servers.
-- --
sipServerCfgTable OBJECT-TYPE sipServerCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 1 }
SYNTAX SEQUENCE OF SipServerCfgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains configuration objects applicable
to SIP Redirect and Proxy Servers."
::= { sipServerCfg 1 }
sipServerCfgEntry OBJECT-TYPE --
SYNTAX SipServerCfgEntry -- Common Server Configuration Objects
MAX-ACCESS not-accessible --
STATUS current sipServerCfgTable OBJECT-TYPE
DESCRIPTION SYNTAX SEQUENCE OF SipServerCfgEntry
"A row of common configuration. MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains configuration objects applicable to SIP
Redirect and Proxy Servers."
::= { sipServerCfg 1 }
Each row represents those objects for a particular sipServerCfgEntry OBJECT-TYPE
SIP server present in this system. applIndex is used SYNTAX SipServerCfgEntry
to uniquely identify these instances of SIP servers MAX-ACCESS not-accessible
and correlate them through the common framework of STATUS current
the NETWORK-SERVICES-MIB (RFC 2788). The same value DESCRIPTION
of applIndex used in the corresponding SIP-COMMON-MIB "A row of common configuration.
is used here.
The objects in this table entry SHOULD be
non-volatile and their value SHOULD be kept at
reboot."
INDEX { applIndex }
::= { sipServerCfgTable 1 }
SipServerCfgEntry ::= Each row represents those objects for a particular SIP server
SEQUENCE { present in this system. applIndex is used to uniquely identify
sipServerHostAddrType InetAddressType, these instances of SIP servers and correlate them through the
sipServerHostAddr InetAddress common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
} same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."
INDEX { applIndex }
::= { sipServerCfgTable 1 }
sipServerHostAddrType OBJECT-TYPE SipServerCfgEntry ::=
SYNTAX InetAddressType SEQUENCE {
MAX-ACCESS read-only sipServerCfgHostAddressType InetAddressType,
STATUS current sipServerCfgHostAddress InetAddress
DESCRIPTION }
"The type of Internet address by which the SIP server
is reachable."
REFERENCE
"RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 1 }
sipServerHostAddr OBJECT-TYPE sipServerCfgHostAddressType OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is the host portion of a SIP URI that is
assigned to the SIP server. It MAY contain a fully
qualified domain name, or an IP address. The length
of the value will depend on the type of address
specified.
sipServerHostAddrType formalizes the type of address
given by this object. It is the user's
responsibility to maintain consistency between this
object and the type specified by
sipServerHostAddrType."
REFERENCE
"RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 2 }
-- STATUS current
-- This group contains MIB objects DESCRIPTION
-- related to SIP Proxy Servers. "The type of Internet address by which the SIP server is
-- reachable."
sipProxyCfg OBJECT IDENTIFIER ::= REFERENCE
{ sipServerMIBObjects 3 } "RFC 3261, Section 19.1.1"
sipProxyStats OBJECT IDENTIFIER ::= ::= { sipServerCfgEntry 1 }
{ sipServerMIBObjects 4 }
-- sipServerCfgHostAddress OBJECT-TYPE
-- Proxy Server Configuration SYNTAX InetAddress
-- MAX-ACCESS read-only
sipProxyCfgTable OBJECT-TYPE STATUS current
SYNTAX SEQUENCE OF SipProxyCfgEntry DESCRIPTION
MAX-ACCESS not-accessible "This is the host portion of a SIP URI that is assigned to the
STATUS current SIP server. It MAY contain a fully qualified domain name, or
DESCRIPTION an IP address. The length of the value will depend on the type
"This table contains configuration objects applicable of address specified. The type of address given by this object
to SIP Proxy Servers." is controlled by sipServerCfgHostAddressType."
::= { sipProxyCfg 1 } REFERENCE
"RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 2 }
sipProxyCfgEntry OBJECT-TYPE --
SYNTAX SipProxyCfgEntry -- This group contains MIB objects
MAX-ACCESS not-accessible -- related to SIP Proxy Servers.
STATUS current --
DESCRIPTION sipServerProxyCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 3 }
"A row of common proxy configuration. sipServerProxyStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 4 }
Each row represents those objects for a particular --
SIP server present in this system. applIndex is used -- Proxy Server Configuration
to uniquely identify these instances of SIP servers --
and correlate them through the common framework of sipServerProxyCfgTable OBJECT-TYPE
the NETWORK-SERVICES-MIB (RFC 2788). The same value SYNTAX SEQUENCE OF SipServerProxyCfgEntry
of applIndex used in the corresponding SIP-COMMON-MIB MAX-ACCESS not-accessible
is used here. STATUS current
The objects in this table entry SHOULD be DESCRIPTION
non-volatile and their value SHOULD be kept at "This table contains configuration objects applicable to SIP
reboot." Proxy Servers."
INDEX { applIndex } ::= { sipServerProxyCfg 1 }
::= { sipProxyCfgTable 1 }
SipProxyCfgEntry ::= sipServerProxyCfgEntry OBJECT-TYPE
SEQUENCE { SYNTAX SipServerProxyCfgEntry
sipProxyStatefulness INTEGER, MAX-ACCESS not-accessible
sipProxyRecursion TruthValue, STATUS current
sipProxyRecordRoute TruthValue, DESCRIPTION
sipProxyAuthMethod BITS, "A row of common proxy configuration.
sipProxyAuthRealm SnmpAdminString
}
sipProxyStatefulness OBJECT-TYPE Each row represents those objects for a particular SIP server
SYNTAX INTEGER { present in this system. applIndex is used to uniquely identify
stateless(1), these instances of SIP servers and correlate them through the
transactionStateful(2), common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
callStateful(3) same value of applIndex used in the corresponding
} SIP-COMMON-MIB is used here."
MAX-ACCESS read-only INDEX { applIndex }
STATUS current ::= { sipServerProxyCfgTable 1 }
DESCRIPTION
"This object reflects the default mode of operation
for the Proxy Server entity.
A stateless proxy is a logical entity that does not SipServerProxyCfgEntry ::=
maintain the client or server transaction state SEQUENCE {
machines when it processes requests. A stateless sipServerCfgProxyStatefulness INTEGER,
proxy forwards every request it receives downstream sipServerCfgProxyRecursion TruthValue,
and every response it receives upstream. If the value sipServerCfgProxyRecordRoute TruthValue,
of this object is stateless(1), the proxy defaults to sipServerCfgProxyAuthMethod BITS,
stateless operations. sipServerCfgProxyAuthDefaultRealm SnmpAdminString
}
A transaction stateful proxy, or simply a 'stateful sipServerCfgProxyStatefulness OBJECT-TYPE
proxy', is a logical entity that maintains the client SYNTAX INTEGER {
and server transaction state machines during the stateless(1),
processing of a request. A (transaction) stateful transactionStateful(2),
proxy is not the same as a call stateful proxy. If callStateful(3)
the value if this object is transactionStateful(2), }
the proxy is stateful on a transaction basis. MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the default mode of operation for the
Proxy Server entity.
A call stateful proxy is a logical entity if it A stateless proxy is a logical entity that does not maintain
retains state for a dialog from the initiating INVITE the client or server transaction state machines when it
to the terminating BYE request. A call stateful processes requests. A stateless proxy forwards every request it
proxy is always transaction stateful, but the receives downstream and every response it receives upstream. If
converse is not necessarily true. If the value of the value of this object is stateless(1), the proxy defaults to
this object is callStateful(3), the proxy is call stateless operations.
stateful."
REFERENCE
"RFC 3261, Section 16"
::= { sipProxyCfgEntry 1 }
sipProxyRecursion OBJECT-TYPE A transaction stateful proxy, or simply a 'stateful proxy', is
SYNTAX TruthValue a logical entity that maintains the client and server
MAX-ACCESS read-only transaction state machines during the processing of a request.
STATUS current A (transaction) stateful proxy is not the same as a call
DESCRIPTION stateful proxy. If the value if this object is
"This object reflects whether or not the Proxy transactionStateful(2), the proxy is stateful on a transaction
performs recursive search on the Contacts provided in basis.
3xx redirects.
If the value of this object is 'true', a recursive A call stateful proxy is a logical entity if it retains state
search is performed. If the value is 'false', no for a dialog from the initiating INVITE to the terminating BYE
search is performed, the 3xx response is sent request. A call stateful proxy is always transaction stateful,
upstream towards the source of the request." but the converse is not necessarily true. If the value of this
REFERENCE object is callStateful(3), the proxy is call stateful."
"RFC 3261 Sections 16.5 and 16.6"
::= { sipProxyCfgEntry 2 }
sipProxyRecordRoute OBJECT-TYPE REFERENCE
SYNTAX TruthValue "RFC 3261, Section 16"
MAX-ACCESS read-only ::= { sipServerProxyCfgEntry 1 }
STATUS current
DESCRIPTION
"This object reflects whether or not the proxy adds
itself to the Record-Route header as a default
action.
This header is used to list the proxies that insist
on being in the signaling path for subsequent
requests related to the call-leg.
If the value of this object is 'true', the proxy adds sipServerCfgProxyRecursion OBJECT-TYPE
itself to the end of the Record-Route header, SYNTAX TruthValue
creating the header if required. If the value is MAX-ACCESS read-only
'false', the proxy does not add itself to the STATUS current
Record-Route header." DESCRIPTION
REFERENCE "This object reflects whether or not the Proxy performs
"RFC 3261, Section 20.30" recursive search on the Contacts provided in 3xx redirects.
::= { sipProxyCfgEntry 3 }
-- If the value of this object is 'true', a recursive search is
-- Security performed. If the value is 'false', no search is performed,
-- the 3xx response is sent upstream towards the source of the
sipProxyAuthMethod OBJECT-TYPE request."
SYNTAX BITS { REFERENCE
none(0), "RFC 3261 Sections 16.5 and 16.6"
tls(1), ::= { sipServerProxyCfgEntry 2 }
digest(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the authentication methods that
MAY be used to authenticate request originators.
bit 0 no authentication is performed sipServerCfgProxyRecordRoute OBJECT-TYPE
bit 1 TLS is used SYNTAX TruthValue
bit 2 HTTP Digest is used." MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects whether or not the proxy adds itself to
the Record-Route header as a default action. This header is
used to list the proxies that insist on being in the signaling
path for subsequent requests related to the call-leg.
REFERENCE If the value of this object is 'true', the proxy adds itself to
"RFC 3261 Sections 22, 23, 26, 26.2.3" the end of the Record-Route header, creating the header if
::= { sipProxyCfgEntry 4 } required. If the value is 'false', the proxy does not add
itself to the Record-Route header."
REFERENCE
"RFC 3261, Section 20.30"
::= { sipServerProxyCfgEntry 3 }
sipProxyAuthRealm OBJECT-TYPE --
SYNTAX SnmpAdminString -- Security
MAX-ACCESS read-only --
STATUS current sipServerCfgProxyAuthMethod OBJECT-TYPE
DESCRIPTION SYNTAX BITS {
"This object reflects the default realm value used in none(0),
Proxy-Authenticate headers. Note that this MAY need tls(1),
to be stored per user, in which case, this default digest(2)
value is ignored." }
REFERENCE MAX-ACCESS read-only
"RFC 3261, Section 22.1" STATUS current
::= { sipProxyCfgEntry 5 } DESCRIPTION
"This object reflects the authentication methods that MAY be
used to authenticate request originators.
-- bit 0 no authentication is performed
-- Proxy Server Statistics bit 1 TLS is used
-- bit 2 HTTP Digest is used."
sipProxyStatsTable OBJECT-TYPE REFERENCE
SYNTAX SEQUENCE OF SipProxyStatsEntry "RFC 3261 Sections 22, 23, 26, 26.2.3"
MAX-ACCESS not-accessible ::= { sipServerProxyCfgEntry 4 }
STATUS current
DESCRIPTION
"This table contains the statistics objects applicable
to all SIP Proxy Servers in this system."
::= { sipProxyStats 1 }
sipProxyStatsEntry OBJECT-TYPE sipServerCfgProxyAuthDefaultRealm OBJECT-TYPE
SYNTAX SipProxyStatsEntry SYNTAX SnmpAdminString
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics. "This object reflects the default realm value used in
Proxy-Authenticate headers. Note that this MAY need to be
stored per user, in which case, this default value is ignored.
"
REFERENCE
"RFC 3261, Section 22.1"
::= { sipServerProxyCfgEntry 5 }
Each row represents those objects for a particular --
SIP server present in this system. applIndex is used -- Proxy Server Statistics
to uniquely identify these instances of SIP servers --
and correlate them through the common framework of sipServerProxyStatsTable OBJECT-TYPE
the NETWORK-SERVICES-MIB (RFC 2788). The same value SYNTAX SEQUENCE OF SipServerProxyStatsEntry
of applIndex used in the corresponding SIP-COMMON-MIB MAX-ACCESS not-accessible
is used here."
INDEX { applIndex }
::= { sipProxyStatsTable 1 }
SipProxyStatsEntry ::= STATUS current
SEQUENCE { DESCRIPTION
sipNumProxyRequireFailures Counter32 "This table contains the statistics objects applicable to all
} SIP Proxy Servers in this system."
::= { sipServerProxyStats 1 }
sipNumProxyRequireFailures OBJECT-TYPE sipServerProxyStatsEntry OBJECT-TYPE
SYNTAX Counter32 SYNTAX SipServerProxyStatsEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the number of occurrences of "A row of summary statistics.
unsupported options being specified in received
Proxy- Require headers. Such occurrences result in a
420 Bad Extension status code being returned."
::= { sipProxyStatsEntry 1 }
-- Each row represents those objects for a particular SIP server
-- This group contains MIB objects related to SIP Registrars. present in this system. applIndex is used to uniquely identify
-- these instances of SIP servers and correlate them through the
sipRegCfg OBJECT IDENTIFIER ::= common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
{ sipServerMIBObjects 5 } same value of applIndex used in the corresponding
sipRegStats OBJECT IDENTIFIER ::= SIP-COMMON-MIB is used here."
{ sipServerMIBObjects 6 } INDEX { applIndex }
::= { sipServerProxyStatsTable 1 }
-- SipServerProxyStatsEntry ::=
-- Registrar Configuration SEQUENCE {
-- sipServerProxyStatProxyReqFailures Counter32,
sipRegCfgTable OBJECT-TYPE sipServerProxyStatsDisconTime TimeStamp
SYNTAX SEQUENCE OF SipRegCfgEntry }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains configuration objects applicable
SIP Registrars."
::= { sipRegCfg 1 }
sipRegCfgEntry OBJECT-TYPE sipServerProxyStatProxyReqFailures OBJECT-TYPE
SYNTAX SipRegCfgEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common Registrar configuration. "This object contains the number of occurrences of unsupported
options being specified in received Proxy-Require headers.
Such occurrences result in a 420 Bad Extension status code
being returned.
Each row represents those objects for a particular Discontinuities in the value of this counter can occur at
SIP server present in this system. applIndex is used re-initialization of the SIP entity or service. A Management
to uniquely identify these instances of SIP servers Station can detect discontinuities in this counter by
and correlate them through the common framework of monitoring the sipServerProxyStatsDisconTime object in the same
the NETWORK-SERVICES-MIB (RFC 2788). The same value row."
of applIndex used in the corresponding SIP-COMMON-MIB ::= { sipServerProxyStatsEntry 1 }
is used here."
INDEX { applIndex }
::= { sipRegCfgTable 1 }
SipRegCfgEntry ::= sipServerProxyStatsDisconTime OBJECT-TYPE
SEQUENCE { SYNTAX TimeStamp
sipRegMaxContactExpiryDuration Unsigned32, MAX-ACCESS read-only
sipRegMaxUsers Unsigned32, STATUS current
sipRegCurrentUsers Gauge32, DESCRIPTION
sipRegDfltRegActiveInterval Unsigned32 "The value of the sysUpTime object when the counters for the server
} statistics objects in this row last experienced a discontinuity."
::= { sipServerProxyStatsEntry 2 }
sipRegMaxContactExpiryDuration OBJECT-TYPE --
SYNTAX Unsigned32 (0..4294967295) -- This group contains MIB objects related to SIP Registrars.
UNITS "seconds" --
MAX-ACCESS read-only sipServerRegCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 5 }
STATUS current sipServerRegStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 6 }
DESCRIPTION
"This object reflects the maximum expiry that may be
requested by a User Agent for a particular Contact.
User Agents can specify expiry using either an Expiry
header in a REGISTER request, or using an Expires
parameter in a Contact header in a REGISTER request.
If the value requested by the User Agent is greater
than the value of this object, then the contact
information is given the duration specified by this
object, and that duration is indicated to the User
Agent in the response."
::= { sipRegCfgEntry 1 }
sipRegMaxUsers OBJECT-TYPE --
SYNTAX Unsigned32 (1..4294967295) -- Registrar Configuration
MAX-ACCESS read-only --
STATUS current sipServerRegCfgTable OBJECT-TYPE
DESCRIPTION SYNTAX SEQUENCE OF SipServerRegCfgEntry
"This object reflects the maximum number of users that MAX-ACCESS not-accessible
the Registrar supports. The current number of users STATUS current
is reflected by sipRegCurrentUsers." DESCRIPTION
::= { sipRegCfgEntry 2 } "This table contains configuration objects applicable SIP
Registrars."
::= { sipServerRegCfg 1 }
sipRegCurrentUsers OBJECT-TYPE sipServerRegCfgEntry OBJECT-TYPE
SYNTAX Gauge32 (0..4294967295) SYNTAX SipServerRegCfgEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of users currently "A row of common Registrar configuration.
registered with the Registrar."
::= { sipRegCfgEntry 3 } Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."
INDEX { applIndex }
::= { sipServerRegCfgTable 1 }
sipRegDfltRegActiveInterval OBJECT-TYPE SipServerRegCfgEntry ::=
SYNTAX Unsigned32 (1..4294967295) SEQUENCE {
UNITS "seconds" sipServerRegMaxContactExpiryDuration Unsigned32,
MAX-ACCESS read-only sipServerRegMaxUsers Unsigned32,
STATUS current sipServerRegCurrentUsers Gauge32,
DESCRIPTION sipServerRegDfltRegActiveInterval Unsigned32
"This object reflects the default time interval the }
Registrar considers registrations to be active. The
value is used to compute the Expires header in the
REGISTER response. If a user agent requests a time
interval shorter than specified by this object, the
Registrar SHOULD honor that request. If a Contact
entry does not have an 'expires' parameter, the value
of the Expires header field is used instead. If a
Contact entry has no 'expires' parameter and no the
Expires header field is present, the value of this
object is used as the default value.
This object SHOULD be non-volatile and its value
SHOULD be kept at reboot."
REFERENCE "RFC 3261, Section 10.2"
::= { sipRegCfgEntry 4 }
-- sipServerRegMaxContactExpiryDuration OBJECT-TYPE
-- Per User Information SYNTAX Unsigned32 (0..4294967295)
-- UNITS "seconds"
sipRegUserTable OBJECT-TYPE MAX-ACCESS read-only
SYNTAX SEQUENCE OF SipRegUserEntry STATUS current
MAX-ACCESS not-accessible DESCRIPTION
STATUS current "This object reflects the maximum expiry that may be requested
DESCRIPTION by a User Agent for a particular Contact. User Agents can
"This table contains information on all users specify expiry using either an Expiry header in a REGISTER
registered to each Registrar in this system." request, or using an Expires parameter in a Contact header in
::= { sipRegCfg 2 } a REGISTER request. If the value requested by the User Agent
is greater than the value of this object, then the contact
information is given the duration specified by this object, and
that duration is indicated to the User Agent in the response."
::= { sipServerRegCfgEntry 1 }
sipRegUserEntry OBJECT-TYPE sipServerRegMaxUsers OBJECT-TYPE
SYNTAX SipRegUserEntry SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single user "This object reflects the maximum number of users that the
registered to this Registrar. Registrar supports. The current number of users is reflected
by sipServerRegCurrentUsers."
::= { sipServerRegCfgEntry 2 }
Each row represents those objects for a particular sipServerRegCurrentUsers OBJECT-TYPE
SIP server present in this system. applIndex is used SYNTAX Gauge32 (0..4294967295)
to uniquely identify these instances of SIP servers MAX-ACCESS read-only
and correlate them through the common framework of STATUS current
the NETWORK-SERVICES-MIB (RFC 2788). The same value DESCRIPTION
of applIndex used in the corresponding SIP-COMMON-MIB "This object reflects the number of users currently registered
is used here." with the Registrar."
INDEX { applIndex, sipUserIndex } ::= { sipServerRegCfgEntry 3 }
::= { sipRegUserTable 1 }
SipRegUserEntry ::= sipServerRegDfltRegActiveInterval OBJECT-TYPE
SEQUENCE { SYNTAX Unsigned32 (1..4294967295)
sipUserIndex Unsigned32, UNITS "seconds"
sipUserUri SnmpAdminString, MAX-ACCESS read-only
sipUserAuthenticationFailures Counter32 STATUS current
} DESCRIPTION
"This object reflects the default time interval the Registrar
considers registrations to be active. The value is used to
compute the Expires header in the REGISTER response. If a user
agent requests a time interval shorter than specified by this
object, the Registrar SHOULD honor that request. If a Contact
entry does not have an 'expires' parameter, the value of the
Expires header field is used instead. If a Contact entry has no
'expires' parameter and no the Expires header field is present,
the value of this object is used as the default value."
REFERENCE
"RFC 3261, Section 10.2"
::= { sipServerRegCfgEntry 4 }
--
-- Per User Information
--
sipServerRegUserTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerRegUserEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information on all users registered to each
Registrar in this system."
::= { sipServerRegCfg 2 }
sipUserIndex OBJECT-TYPE sipServerRegUserEntry OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX SipServerRegUserEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in "This entry contains information for a single user registered to
the table." this Registrar.
::= { sipRegUserEntry 1 }
sipUserUri OBJECT-TYPE Each row represents those objects for a particular SIP server
SYNTAX SnmpAdminString present in this system. applIndex is used to uniquely identify
MAX-ACCESS read-only these instances of SIP servers and correlate them through the
STATUS current common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
DESCRIPTION same value of applIndex used in the corresponding
"This object contains the user's address-of-record. SIP-COMMON-MIB is used here."
It is the main form by which the Registrar knows the INDEX { applIndex, sipServerRegUserIndex }
user. The format is typically 'user@domain'. It is ::= { sipServerRegUserTable 1 }
contained in the To header for all REGISTER
requests."
::= { sipRegUserEntry 2 }
sipUserAuthenticationFailures OBJECT-TYPE SipServerRegUserEntry ::=
SYNTAX Counter32 SEQUENCE {
MAX-ACCESS read-only sipServerRegUserIndex Unsigned32,
STATUS current sipServerRegUserUri SnmpAdminString,
DESCRIPTION sipServerRegUserAuthenticationFailures Counter32,
"This object contains a count of the number of times sipServerRegUserDisconTime TimeStamp
the user has failed authentication." }
::= { sipRegUserEntry 3 }
-- sipServerRegUserIndex OBJECT-TYPE
-- Per Contact Information SYNTAX Unsigned32 (1..4294967295)
-- MAX-ACCESS not-accessible
sipContactTable OBJECT-TYPE STATUS current
SYNTAX SEQUENCE OF SipContactEntry DESCRIPTION
MAX-ACCESS not-accessible "This object uniquely identifies a conceptual row in the table."
STATUS current ::= { sipServerRegUserEntry 1 }
DESCRIPTION
"This table contains information on every location
where a registered user (specified by sipUserIndex)
wishes to be found (i.e. the user has provided Contact
information to each SIP Registrar in this system)."
::= { sipRegCfg 3 }
sipContactEntry OBJECT-TYPE sipServerRegUserUri OBJECT-TYPE
SYNTAX SipContactEntry SYNTAX SnmpAdminString
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single Contact. "This object contains the user's address-of-record. It is the
Multiple contacts may exist for a single user. main form by which the Registrar knows the user. The format is
typically 'user@domain'. It is contained in the To header for
all REGISTER requests."
::= { sipServerRegUserEntry 2 }
Each row represents those objects for a particular sipServerRegUserAuthenticationFailures OBJECT-TYPE
SIP server present in this system. applIndex is used SYNTAX Counter32
to uniquely identify these instances of SIP servers MAX-ACCESS read-only
and correlate them through the common framework of STATUS current
the NETWORK-SERVICES-MIB (RFC 2788). The same value DESCRIPTION
of applIndex used in the corresponding SIP-COMMON-MIB "This object contains a count of the number of times the user
is used here." has failed authentication.
INDEX { applIndex, sipUserIndex, sipContactIndex }
::= { sipContactTable 1 }
SipContactEntry ::= Discontinuities in the value of this counter can occur due to
SEQUENCE { successful user authentications, and at re-initialization of
sipContactIndex Unsigned32, the SIP entity or service. A Management Station can detect
sipContactDisplayName SnmpAdminString, discontinuities in this counter by monitoring the
sipContactURI SnmpAdminString, sipServerRegUserDisconTime object in the same row."
sipContactLastUpdated TimeStamp, ::= { sipServerRegUserEntry 3 }
sipContactExpiry DateAndTime,
sipContactPreference SnmpAdminString
}
sipContactIndex OBJECT-TYPE sipServerRegUserDisconTime OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX TimeStamp
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Along with the sipUserIndex, this object uniquely "The value of the sysUpTime object when the counters for the
identifies a conceptual row in the table." user registration statistic objects in this row last
::= { sipContactEntry 1 } experienced a discontinuity."
::= { sipServerRegUserEntry 4 }
--
-- Per Contact Information
--
sipServerRegContactTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerRegContactEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information on every location where a
registered user (specified by sipServerRegUserIndex) wishes to
be found (i.e. the user has provided Contact information to
each SIP Registrar in this system)."
::= { sipServerRegCfg 3 }
sipContactDisplayName OBJECT-TYPE sipServerRegContactEntry OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SipServerRegContactEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the display name for the "This entry contains information for a single Contact. Multiple
Contact. contacts may exist for a single user.
For example, 'Santa at Home', or 'Santa on his Sled',
corresponding to contact URIs of
sip:BigGuy@example.com or
sip:sclaus817@example.com, respectively."
::= { sipContactEntry 2 }
sipContactURI OBJECT-TYPE Each row represents those objects for a particular SIP server
SYNTAX SnmpAdminString present in this system. applIndex is used to uniquely identify
MAX-ACCESS read-only these instances of SIP servers and correlate them through the
STATUS current common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
DESCRIPTION same value of applIndex used in the corresponding
"This object contains either a SIP URI where SIP-COMMON-MIB is used here."
the user can be contacted. This URI is normally
returned to a client from a Redirect Server, or is
used as the RequestURI in a SIP request line for
requests forwarded by a proxy."
::= { sipContactEntry 3 }
sipContactLastUpdated OBJECT-TYPE INDEX { applIndex,
SYNTAX TimeStamp sipServerRegUserIndex,
MAX-ACCESS read-only sipServerRegContactIndex
STATUS current }
DESCRIPTION ::= { sipServerRegContactTable 1 }
"This object indicates the time when this contact
information was accepted. If the contact information
is updated via a subsequent REGISTER of the same
information, this object is also updated."
::= { sipContactEntry 4 }
sipContactExpiry OBJECT-TYPE SipServerRegContactEntry ::=
SYNTAX DateAndTime SEQUENCE {
MAX-ACCESS read-only sipServerRegContactIndex Unsigned32,
STATUS current sipServerRegContactDisplayName SnmpAdminString,
DESCRIPTION sipServerRegContactURI SnmpAdminString,
"This object contains the date and time when the sipServerRegContactLastUpdated TimeStamp,
contact information will no longer be valid. Such sipServerRegContactExpiry DateAndTime,
times may be specified by the user at registration sipServerRegContactPreference SnmpAdminString
(Expires header or expiry parameter in the Contact }
information), or a system default can be applied."
::= { sipContactEntry 5 }
sipContactPreference OBJECT-TYPE sipServerRegContactIndex OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a relative preference for the "Along with the sipServerRegUserIndex, this object uniquely
particular Contact header field value compared to identifies a conceptual row in the table."
other bindings for this address-of-record. A ::= { sipServerRegContactEntry 1 }
registering user may provide this preference as a
'qvalue' parameter in the Contact header.
The format of this item is a decimal number between 0 sipServerRegContactDisplayName OBJECT-TYPE
and 1 (for example 0.9). Higher values indicate SYNTAX SnmpAdminString
locations preferred by the user." MAX-ACCESS read-only
REFERENCE STATUS current
"RFC 3261, Section 10.2.1.2, 16.6 and 20.10" DESCRIPTION
::= { sipContactEntry 6 } "This object contains the display name for the Contact. For
example, 'Santa at Home', or 'Santa on his Sled', corresponding
to contact URIs of sip:BigGuy@example.com or
sip:sclaus817@example.com, respectively."
::= { sipServerRegContactEntry 2 }
-- sipServerRegContactURI OBJECT-TYPE
-- Registrar Statistics SYNTAX SnmpAdminString
-- MAX-ACCESS read-only
sipRegStatsTable OBJECT-TYPE STATUS current
SYNTAX SEQUENCE OF SipRegStatsEntry DESCRIPTION
MAX-ACCESS not-accessible "This object contains either a SIP URI where the user can be
STATUS current contacted. This URI is normally returned to a client from a
DESCRIPTION Redirect Server, or is used as the RequestURI in a SIP request
"This table contains the summary statistics objects line for requests forwarded by a proxy."
applicable to all SIP Registrars in this system." ::= { sipServerRegContactEntry 3 }
::= { sipRegStats 1 }
sipRegStatsEntry OBJECT-TYPE sipServerRegContactLastUpdated OBJECT-TYPE
SYNTAX SipRegStatsEntry SYNTAX TimeStamp
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics. "This object indicates the time when this contact information
was accepted. If the contact information is updated via a
subsequent REGISTER of the same information, this object is
also updated."
::= { sipServerRegContactEntry 4 }
Each row represents those objects for a particular sipServerRegContactExpiry OBJECT-TYPE
SIP server present in this system. applIndex is used SYNTAX DateAndTime
to uniquely identify these instances of SIP servers MAX-ACCESS read-only
and correlate them through the common framework of STATUS current
the NETWORK-SERVICES-MIB (RFC 2788). The same value DESCRIPTION
of applIndex used in the corresponding SIP-COMMON-MIB "This object contains the date and time when the contact
is used here." information will no longer be valid. Such times may be
INDEX { applIndex } specified by the user at registration (Expires header or expiry
::= { sipRegStatsTable 1 } parameter in the Contact information), or a system default can
be applied."
::= { sipServerRegContactEntry 5 }
SipRegStatsEntry ::= sipServerRegContactPreference OBJECT-TYPE
SEQUENCE { SYNTAX SnmpAdminString
sipRegAcceptedRegistrations Counter32, MAX-ACCESS read-only
sipRegRejectedRegistrations Counter32 STATUS current
} DESCRIPTION
"This object indicates a relative preference for the particular
Contact header field value compared to other bindings for this
address-of-record. A registering user may provide this
preference as a 'qvalue' parameter in the Contact header.
sipRegAcceptedRegistrations OBJECT-TYPE The format of this item is a decimal number between 0 and 1
SYNTAX Counter32 (for example 0.9). Higher values indicate locations preferred
MAX-ACCESS read-only by the user."
STATUS current REFERENCE
DESCRIPTION "RFC 3261, Section 10.2.1.2, 16.6 and 20.10"
"This object contains a count of the number of ::= { sipServerRegContactEntry 6 }
REGISTER requests that have been accepted (status code
200) by the Registrar. This includes additions of new
contact information, refreshing contact information,
as well as requests for deletion of contact
information."
::= { sipRegStatsEntry 1 }
sipRegRejectedRegistrations OBJECT-TYPE --
SYNTAX Counter32 -- Registrar Statistics
MAX-ACCESS read-only --
STATUS current sipServerRegStatsTable OBJECT-TYPE
DESCRIPTION SYNTAX SEQUENCE OF SipServerRegStatsEntry
"This object contains a count of the number REGISTER MAX-ACCESS not-accessible
requests that have been rejected by the Registrar." STATUS current
::= { sipRegStatsEntry 2 } DESCRIPTION
"This table contains the summary statistics objects applicable
to all SIP Registrars in this system."
::= { sipServerRegStats 1 }
-- sipServerRegStatsEntry OBJECT-TYPE
-- Conformance SYNTAX SipServerRegStatsEntry
-- MAX-ACCESS not-accessible
sipServerMIBCompliances STATUS current
OBJECT IDENTIFIER ::= { sipServerMIBConform 1 } DESCRIPTION
sipServerMIBGroups "A row of summary statistics.
OBJECT IDENTIFIER ::= { sipServerMIBConform 2 }
-- Each row represents those objects for a particular SIP server
-- Compliance Statements present in this system. applIndex is used to uniquely identify
-- these instances of SIP servers and correlate them through the
sipProxyServerCompliance MODULE-COMPLIANCE common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
STATUS current same value of applIndex used in the corresponding
DESCRIPTION SIP-COMMON-MIB is used here."
"The compliance statement for SIP entities acting INDEX { applIndex }
as Proxy Servers." ::= { sipServerRegStatsTable 1 }
MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup,
sipProxyConfigGroup,
sipProxyStatsGroup }
::= { sipServerMIBCompliances 1 }
sipRedirectServerCompliance MODULE-COMPLIANCE SipServerRegStatsEntry ::=
STATUS current SEQUENCE {
DESCRIPTION sipServerRegStatsAcceptedRegs Counter32,
"The compliance statement for SIP entities acting sipServerRegStatsRejectedRegs Counter32,
as Redirect Servers." sipServerRegStatsDisconTime TimeStamp
MODULE -- this module }
MANDATORY-GROUPS { sipServerConfigGroup }
::= { sipServerMIBCompliances 2 }
sipRegistrarServerCompliance MODULE-COMPLIANCE sipServerRegStatsAcceptedRegs OBJECT-TYPE
STATUS current SYNTAX Counter32
DESCRIPTION MAX-ACCESS read-only
"The compliance statement for SIP entities acting STATUS current
as Registrars." DESCRIPTION
MODULE -- this module "This object contains a count of the number of REGISTER requests
MANDATORY-GROUPS { sipServerConfigGroup, that have been accepted (status code 200) by the Registrar.
sipRegistrarConfigGroup, This includes additions of new contact information, refreshing
sipRegistrarStatsGroup } contact information, as well as requests for deletion of
GROUP sipRegistrarUsersGroup contact information.
DESCRIPTION
"This is an optional group."
::= { sipServerMIBCompliances 3 }
-- Discontinuities in the value of this counter can occur at
-- Units of Conformance re-initialization of the SIP entity or service. A Management
-- Station can detect discontinuities in this counter by
sipServerConfigGroup OBJECT-GROUP monitoring the sipServerRegStatsDisconTime object in the same
OBJECTS { row."
sipServerHostAddrType, ::= { sipServerRegStatsEntry 1 }
sipServerHostAddr
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration
common to SIP Proxy and Redirect servers."
::= { sipServerMIBGroups 1 }
sipProxyConfigGroup OBJECT-GROUP sipServerRegStatsRejectedRegs OBJECT-TYPE
OBJECTS { SYNTAX Counter32
sipProxyStatefulness, MAX-ACCESS read-only
sipProxyRecursion, STATUS current
sipProxyRecordRoute, DESCRIPTION
sipProxyAuthMethod, "This object contains a count of the number REGISTER requests
sipProxyAuthRealm that have been rejected by the Registrar.
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration for
SIP Proxy servers."
::= { sipServerMIBGroups 2 }
sipProxyStatsGroup OBJECT-GROUP Discontinuities in the value of this counter can occur at
OBJECTS { re-initialization of the SIP entity or service. A Management
sipNumProxyRequireFailures Station can detect discontinuities in this counter by
} monitoring the sipServerRegStatsDisconTime object in the same
STATUS current row."
DESCRIPTION ::= { sipServerRegStatsEntry 2 }
"A collection of objects providing statistics for
SIP Proxy servers."
::= { sipServerMIBGroups 3 }
sipRegistrarConfigGroup OBJECT-GROUP sipServerRegStatsDisconTime OBJECT-TYPE
OBJECTS { SYNTAX TimeStamp
sipRegMaxContactExpiryDuration, MAX-ACCESS read-only
sipRegMaxUsers, STATUS current
sipRegCurrentUsers, DESCRIPTION
sipRegDfltRegActiveInterval "The value of the sysUpTime object when the counters for the
} registrar statistic objects in this row last experienced a
STATUS current discontinuity."
DESCRIPTION ::= { sipServerRegStatsEntry 3 }
"A collection of objects providing configuration for
SIP Registrars."
::= { sipServerMIBGroups 4 }
sipRegistrarStatsGroup OBJECT-GROUP --
OBJECTS { -- Conformance
sipRegAcceptedRegistrations, --
sipRegRejectedRegistrations sipServerMIBCompliances
} OBJECT IDENTIFIER ::= { sipServerMIBConformance 1 }
STATUS current sipServerMIBGroups
DESCRIPTION OBJECT IDENTIFIER ::= { sipServerMIBConformance 2 }
"A collection of objects providing statistics for
SIP Registrars."
::= { sipServerMIBGroups 5 }
sipRegistrarUsersGroup OBJECT-GROUP --
OBJECTS { -- Compliance Statements
sipUserUri, --
sipUserAuthenticationFailures, sipServerProxyServerCompliance MODULE-COMPLIANCE
sipContactDisplayName, STATUS current
sipContactURI, DESCRIPTION
sipContactLastUpdated, "The compliance statement for SIP entities acting as Proxy
sipContactExpiry, Servers."
sipContactPreference MODULE -- this module
} MANDATORY-GROUPS { sipServerConfigGroup,
STATUS current sipServerProxyConfigGroup,
DESCRIPTION sipServerProxyStatsGroup
"A collection of objects related to registered users." }
::= { sipServerMIBGroups 6 } ::= { sipServerMIBCompliances 1 }
END sipRedirectServerCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SIP entities acting as Redirect
Servers."
MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup }
::= { sipServerMIBCompliances 2 }
sipServerRegistrarServerCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SIP entities acting as
Registrars."
MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup,
sipServerRegistrarConfigGroup,
sipServerRegistrarStatsGroup }
GROUP sipServerRegistrarUsersGroup
DESCRIPTION
"This is an optional group."
::= { sipServerMIBCompliances 3 }
--
-- Units of Conformance
--
sipServerConfigGroup OBJECT-GROUP
OBJECTS {
sipServerCfgHostAddressType,
sipServerCfgHostAddress
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration common to SIP
Proxy and Redirect servers."
::= { sipServerMIBGroups 1 }
sipServerProxyConfigGroup OBJECT-GROUP
OBJECTS {
sipServerCfgProxyStatefulness,
sipServerCfgProxyRecursion,
sipServerCfgProxyRecordRoute,
sipServerCfgProxyAuthMethod,
sipServerCfgProxyAuthDefaultRealm
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration for SIP Proxy
servers."
::= { sipServerMIBGroups 2 }
sipServerProxyStatsGroup OBJECT-GROUP
OBJECTS {
sipServerProxyStatProxyReqFailures,
sipServerProxyStatsDisconTime
}
STATUS current
DESCRIPTION
"A collection of objects providing statistics for SIP Proxy
servers."
::= { sipServerMIBGroups 3 }
sipServerRegistrarConfigGroup OBJECT-GROUP
OBJECTS {
sipServerRegMaxContactExpiryDuration,
sipServerRegMaxUsers,
sipServerRegCurrentUsers,
sipServerRegDfltRegActiveInterval
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration for SIP
Registrars."
::= { sipServerMIBGroups 4 }
sipServerRegistrarStatsGroup OBJECT-GROUP
OBJECTS {
sipServerRegStatsAcceptedRegs,
sipServerRegStatsRejectedRegs,
sipServerRegStatsDisconTime
}
STATUS current
DESCRIPTION
"A collection of objects providing statistics for SIP
Registrars."
::= { sipServerMIBGroups 5 }
sipServerRegistrarUsersGroup OBJECT-GROUP
OBJECTS {
sipServerRegUserUri,
sipServerRegUserAuthenticationFailures,
sipServerRegUserDisconTime,
sipServerRegContactDisplayName,
sipServerRegContactURI,
sipServerRegContactLastUpdated,
sipServerRegContactExpiry,
sipServerRegContactPreference
}
STATUS current
DESCRIPTION
"A collection of objects related to registered users."
::= { sipServerMIBGroups 6 }
END
8. IANA Considerations 8. IANA Considerations
The MIB modules defined in this document use the following IANA- The MIB modules defined in this document use the following IANA-
assigned OBJECT IDENTIFIER values recorded in the SMI Numbers assigned OBJECT IDENTIFIER values recorded in the SMI Numbers
registry: registry:
+--------------+-------------------------+ +--------------+-------------------------+
| Descriptor | OBJECT IDENTIFIER value | | Descriptor | OBJECT IDENTIFIER value |
+--------------+-------------------------+ +--------------+-------------------------+
skipping to change at page 77, line 4 skipping to change at page 77, line 44
There are a number of management objects defined in the SIP-COMMON- There are a number of management objects defined in the SIP-COMMON-
MIB MIB module with a MAX-ACCESS clause of read-write and/or read- MIB MIB module with a MAX-ACCESS clause of read-write and/or read-
create. Such objects may be considered sensitive or vulnerable in create. Such objects may be considered sensitive or vulnerable in
some network environments. The support for SET operations in a non- some network environments. The support for SET operations in a non-
secure environment without proper protection can have a negative secure environment without proper protection can have a negative
effect on network operations. effect on network operations.
The following read-create object in SIP-COMMON-MIB is used to The following read-create object in SIP-COMMON-MIB is used to
configure the status code statistics that will be monitored by the configure the status code statistics that will be monitored by the
SIP entity: SIP entity:
sipCommonStatusCodeRowStatus:
sipStatusCodeRowStatus:
if this object is SET maliciously, it may result in an over if this object is SET maliciously, it may result in an over
allocation of resources in a system for the purpose of allocation of resources in a system for the purpose of
accumulating and maintaining statistics. accumulating and maintaining statistics.
The following read-write objects in SIP-COMMON-MIB are used to The following read-write objects in SIP-COMMON-MIB are used to
configure the behavior of certain SNMP notifications potentially configure the behavior of certain SNMP notifications potentially
generated by a SIP entity: generated by a SIP entity:
sipStatusCodeNotifSend, sipStatusCodeNotifEmitMode, sipCommonStatusCodeNotifSend, sipCommonStatusCodeNotifEmitMode,
sipStatusCodeNotifThresh, sipStatusCodeNotifInterval, sipCommonStatusCodeNotifThresh, sipCommonStatusCodeNotifInterval,
sipServiceNotifEnable: sipCommonCfgServiceNotifEnable:
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.
Some of the readable objects in the MIB modules (i.e., objects with a Some of the readable objects in the MIB modules (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. the network via SNMP.
The following object values may contain private or confidential The following object values may contain private or confidential
customer information like first name, last name, customer customer information like first name, last name, customer
identification, location, company affiliation, the time the identification, location, company affiliation, the time the
information was updated, etc. information was updated, etc.
sipContactDisplayName, sipContactURI, sipContactLastUpdated and sipServerRegContactDisplayName, sipServerRegContactURI,
sipOrganization. sipServerRegContactLastUpdated and sipCommonCfgOrganization.
The sipCommonCfgTable table contains some objects that may help The sipCommonCfgTable table contains some objects that may help
attackers gain knowledge about the status and operations of the SIP attackers gain knowledge about the status and operations of the SIP
service. In particular, the object value of sipServiceOperStatus may service. In particular, the object value of
indicate that the SIP entity is in congested state and may lead sipCommonCfgServiceOperStatus may indicate that the SIP entity is in
attackers to build additional service attacks to overload the system. congested state and may lead attackers to build additional service
attacks to overload the system.
The sipEntityType object indicates the type of SIP entity and the The sipCommonCfgEntityType object indicates the type of SIP entity
sipMethodSupportedTable table contains in the SIP-COMMON-MIB MIB and the sipCommonMethodSupportedTable table contains in the SIP-
module list of SIP methods supported by each entity in the system. COMMON-MIB MIB module list of SIP methods supported by each entity in
Gaining access to this information may allow attackers to build the system. Gaining access to this information may allow attackers
method specific attacks or use unsupported methods to create denial to build method specific attacks or use unsupported methods to create
of service attack scenarios. denial of service attack scenarios.
In the SIP-UA-MIB MIB module, the sipUACfgServerTable contains the In the SIP-UA-MIB MIB module, the sipUACfgServerTable contains the
address of the SIP servers providing services to the UA and obtaining address of the SIP servers providing services to the UA and obtaining
this information may disclose some private or sensitive information this information may disclose some private or sensitive information
about the SIP service usage. about the SIP service usage.
In the SIP-SERVER-MIB MIB module, the sipProxyAuthMethod object In the SIP-SERVER-MIB MIB module, the sipServerCfgProxyAuthMethod
defines the authentication methods supported by the server and may be object defines the authentication methods supported by the server and
used to build specific denial of service attackers targeted at the may be used to build specific denial of service attackers targeted at
security mechanisms employed by the SIP entity. the security mechanisms employed by the SIP entity.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this set of MIB modules. in this set of MIB modules.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see RFC 3410 [RFC3410]), including provided by the SNMPv3 framework (see RFC 3410 [RFC3410]), including
full support for the SNMPv3 cryptographic mechanisms (for full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsi when bility to ensure that the SNMP entity giving access to
instance of this MIB module is properly configured to give access to an instance of this MIB module is properly configured to give access
the objects only to those principals (users) that have legitimate to the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
10. Contributor Acknowledgments 10. Contributor Acknowledgments
We wish to thank the members of the IETF SIP and SIPPING working We wish to thank the members of the IETF SIP and SIPPING working
groups, and the SIP-MIB Design team for their comments and groups, and the SIP-MIB Design team for their comments and
suggestions. Detailed comments were provided by Tom Taylor, Kavitha suggestions. Detailed comments were provided by Tom Taylor, Kavitha
Patchayappan, Dan Romascanu, Cullen Jennings, Orit Levin, AC Patchayappan, Dan Romascanu, Cullen Jennings, Orit Levin, AC
Mahendran, Mary Barnes, Rohan Mahy, Bob Penfield, Charles Eckel and Mahendran, Mary Barnes, Rohan Mahy, Bob Penfield, Charles Eckel and
Dean Willis. Dean Willis. Special thanks to Bert Wijnen for his expert reviews
which have greatly improved the SIP MIB modules.
11. Changes from Previous Draft Revisions 11. Changes from Previous Draft Revisions
-- RFC Ed: this entire section to be removed by RFC Editor before -- RFC Ed: this entire section to be removed by RFC Editor before
publication. publication.
Changes from draft-ietf-sip-mib-11.
The changes are due to IESG Review, additional comments from Bert
Wijnen's MIB doctor review and more editorial comments. The list of
changes includes:
o editorial nits included fixing a section number on page 5, table
identing on page 7, etc.
o technical change: in sipCommonCfgServiceNotifEnable, replaced the
error returned to inconsistentValue when this object is not
supported but SET per RFC 3416 and Bert's comments.
o Technical: changed the module name of SIP-TC to SIP-TC-MIB per
RFC4181, appendix C's naming conventions.
o Technical: added discontinuity timestamps for all counter tables
where discontinuity can occur per Bert's recommendation. This
includes: in SIP-COMMON-MIB sipCommonSummaryStatsTable,
sipCommonMethodStatsTable, sipCommonStatusCodeTable,
sipCommonStatsRetryTable, sipCommonOtherStatsTable, and in SIP-
SERVER-MIB, sipServerProxyStatsTable, sipServerRegUserTable,
sipServerRegStatsTable.
o removed the requirements on persistency of objects for non-
writeable objects.
o In section 5.2, changed MUST into SHOULD in the following
sentence: "the applName value for the combined server entity
SHOULD reflect the appropriate combination followed by a unique
application instance identifier".
o renamed all objects in all MIB modules to ensure the object names
start with either SipTC___, sipCommon____, sipServer___, sipUA____
per Bert Wijnen extensive set of comments and to avoid any to
avoid any possible future name clashes with RFC1694 (MIB module
named sipMIB where numerous objects start with sip___)
o changed naming of sipMethodName to sipCommonMethodSupportedName
because the object `sipMethodName' did differ from the old `SIP-
TC-MIB::SipMethodName' only in case (per Dan Romanescu's
comments).
o changed the size limit of sipMethodName TC due to its use in the
indexing of sipCommonMethodStatsEntry, sipCommonStatusCodeEntry
and sipCommonStatsRetryEntry (per Dan Romanescu's comments).
o in sipCommonCfgServiceNotifEnable, added a requirement that if an
agent does not support his object, it should return a noSuchObject
exception, per Bert's comments and clarified the optionality of
this object by adding an OBJECT statement in the MODULE-COMPLIANCE
section for SIP-COMMON.
Changes from draft-ietf-sip-mib-10. Changes from draft-ietf-sip-mib-10.
The changes were mainly due to Last Call comments. The list of The changes were mainly due to Last Call comments. The list of
changes includes: changes includes:
o minor editorial nits including updates of all examples to use the o minor editorial nits including updates of all examples to use the
example.com domain name; example.com domain name;
o technical changes and updates to SipTransportProtocol to clarify o technical changes and updates to SipTCTransportProtocol to clarify
the use of TLS over TCP and TLS over SCTP; the use of TLS over TCP and TLS over SCTP;
o changed sipCommonCfgMaxTransactions to reflect that it is max
transactions per second;
o removed sipCommonCfgOrganization from mandatory
sipCommonConfigGroup in MODULE-COMPLIANCE and created a new
(opitonal) object group sipCommonInformationalGroup;
o updated DESCRIPTION of sipServerProxyDefaultAuthRealm to indicate
that this object is the *default* realm value used by the proxy in
Proxy-Authenticate headers and, added a note to say that in case
of per user storage, the default value is ignored by the proxy.
o changed sipMaxTransactions to reflect that it is max transactions o removed sipServerRegAllowThirdParty because no registrar
per second; implementer seems to track them differently internally (no comment
o removed sipOrganization from mandatory sipCommonConfigGroup in on the list), and a registrar would have to implement new logic in
MODULE-COMPLIANCE and created a new (opitonal) object group order to be able to exercise this part of the mib.
sipCommonInformationalGroup;
o updated DESCRIPTION of sipProxyAuthRealm to indicate that this
object is the *default* realm value used by the proxy in Proxy-
Authenticate headers and, added a note to say that in case of per
user storage, the default value is ignored by the proxy.
o removed sipRegAllowThirdParty because no registrar implementer
seems to track them differently internally (no comment on the
list), and a registrar would have to implement new logic in order
to be able to exercise this part of the mib.
o added a couple of references like RFC 3262 and RFC 4168. o added a couple of references like RFC 3262 and RFC 4168.
Changes from draft-ietf-sip-mib-09. Changes from draft-ietf-sip-mib-09.
The changes were minimal and mostly done to address MIB doctor The changes were minimal and mostly done to address MIB doctor
comments on SipMethodIdentifier. The list of changes includes: comments on SipMethodIdentifier. The list of changes includes:
o removal of SipMethodIdentifier textual convention per MIB doctor o removal of SipMethodIdentifier textual convention per MIB doctor
feedback feedback
o updates of normative references (e.g. RFC 3291 --> RFC 4001) o updates of normative references (e.g. RFC 3291 --> RFC 4001)
o added a new section to provide a citation to IMPORTed RFCs as they o added a new section to provide a citation to IMPORTed RFCs as they
skipping to change at page 80, line 4 skipping to change at page 81, line 43
general consensus that SNMP should be limited to monitoring general consensus that SNMP should be limited to monitoring
rather than configuring/provisioning. rather than configuring/provisioning.
* The section 5.2 (Relationship to the Network Services MIB) was * The section 5.2 (Relationship to the Network Services MIB) was
updated to allow each instance of a SIP entity to have its own updated to allow each instance of a SIP entity to have its own
row in the applTable (a unique application identifier should row in the applTable (a unique application identifier should
now be appended to the "sip_xxx" entity-name). We also lowered now be appended to the "sip_xxx" entity-name). We also lowered
the level of requirement on the naming convention to a SHOULD the level of requirement on the naming convention to a SHOULD
instead of a MUST per wg input. instead of a MUST per wg input.
* Updated the ORGANISATION clause of all MIB modules to include * Updated the ORGANISATION clause of all MIB modules to include
the full SIP working group name. the full SIP working group name.
* Minor other editorial changes were made to the document. * Minor other editorial changes were made to the document.
* Updated Security consideration section. * Updated Security consideration section.
o SIP-COMMON-MIB o SIP-COMMON-MIB
* Module description of various SIP entities enhanced. * Module description of various SIP entities enhanced.
* sipServiceAdminStatus removed from the MIB due to general * sipCommonServiceAdminStatus removed from the MIB due to general
removal of configuration capability. Resulting OID value removal of configuration capability. Resulting OID value
changes to succeeding entry objects. changes to succeeding entry objects.
* sipOrganization MAX-ACCESS changed to read-only. * sipCommonCfgOrganization MAX-ACCESS changed to read-only.
* sipCfgTimerA MAX-ACCESS changed to read-only.
* sipCfgTimerB MAX-ACCESS changed to read-only. * sipCommonCfgTimerA MAX-ACCESS changed to read-only.
* sipCfgTimerC MAX-ACCESS changed to read-only. * sipCommonCfgTimerB MAX-ACCESS changed to read-only.
* sipCfgTimerD MAX-ACCESS changed to read-only. * sipCommonCfgTimerC MAX-ACCESS changed to read-only.
* sipCfgTimerE MAX-ACCESS changed to read-only. * sipCommonCfgTimerD MAX-ACCESS changed to read-only.
* sipCfgTimerF MAX-ACCESS changed to read-only. * sipCommonCfgTimerE MAX-ACCESS changed to read-only.
* sipCfgTimerG MAX-ACCESS changed to read-only. * sipCommonCfgTimerF MAX-ACCESS changed to read-only.
* sipCfgTimerH MAX-ACCESS changed to read-only. * sipCommonCfgTimerG MAX-ACCESS changed to read-only.
* sipCfgTimerI MAX-ACCESS changed to read-only. * sipCommonCfgTimerH MAX-ACCESS changed to read-only.
* sipCfgTimerJ MAX-ACCESS changed to read-only. * sipCommonCfgTimerI MAX-ACCESS changed to read-only.
* sipCfgTimerK MAX-ACCESS changed to read-only. * sipCommonCfgTimerJ MAX-ACCESS changed to read-only.
* sipCfgTimerT1 MAX-ACCESS changed to read-only. * sipCommonCfgTimerK MAX-ACCESS changed to read-only.
* sipCfgTimerT2 MAX-ACCESS changed to read-only. * sipCommonCfgTimerT1 MAX-ACCESS changed to read-only.
* sipCfgTimerT4 MAX-ACCESS changed to read-only. * sipCommonCfgTimerT2 MAX-ACCESS changed to read-only.
* sipStatusCodesTable indexing changed to also include * sipCommonCfgTimerT4 MAX-ACCESS changed to read-only.
sipStatusCodeMethod. Thusly, introducing sipStatusCodeMethod * sipCommonStatusCodeTable indexing changed to also include
as a new not-accessible object in that table. Resulting OID sipCommonStatusCodeMethod. Thusly, introducing
value changes to succeeding entry objects. sipCommonStatusCodeMethod as a new not-accessible object in
* sipCfgTimer* OBJECT clauses regarding MIN-ACCESS levels in the that table. Resulting OID value changes to succeeding entry
MODULE-COMPLIANCE were no longer needed due to MAX-ACCESS objects.
changes for those objects. * sipCommonCfgTimer* OBJECT clauses regarding MIN-ACCESS levels
* The description clause of sipStatsInbounds was changed to state in the MODULE-COMPLIANCE were no longer needed due to MAX-
that retransmissions are not counted. ACCESS changes for those objects.
* The description clause of sipStatsRetries was changed to * The description clause of sipCommonMethodStatsInbounds was
changed to state that retransmissions are not counted.
* The description clause of sipCommonStatsRetries was changed to
indicate there could be multiple retries per request (we also indicate there could be multiple retries per request (we also
corrected a typo by removing the specific mention to INVITE corrected a typo by removing the specific mention to INVITE
requests). requests).
* The description clause of sipStatsRetryFinalResponses was * The description clause of sipCommonStatsRetryFinalResponses was
changed to indicate there could be multiple retries per changed to indicate there could be multiple retries per
response. response.
o SIP-SERVER-MIB o SIP-SERVER-MIB
* Removed sipCommonCfgExpires OID declaration as this object * Removed sipCommonCfgExpires OID declaration as this object
group no longer exists since draft08. group no longer exists since draft08.
* sipUserTableRowStatus removed from the MIB due to general * sipUserTableRowStatus removed from the MIB due to general
removal of configuration capability. In conjunction, RowStatus removal of configuration capability. In conjunction, RowStatus
textual convention is no longer imported. textual convention is no longer imported.
* sipServerHostAddrType MAX-ACCESS changed to read-only. * sipServerCfgHostAddressType MAX-ACCESS changed to read-only.
* sipServerHostAddr MAX-ACCESS changed to read-only. * sipServerCfgHostAddress MAX-ACCESS changed to read-only.
* sipServerCfgProxyRecursion MAX-ACCESS changed to read-only.
* sipServerCfgProxyRecordRoute MAX-ACCESS changed to read-only.
* sipServerCfgProxyAuthMethod MAX-ACCESS changed to read-only.
* sipServerRegAllowThirdParty MAX-ACCESS changed to read-only.
* sipServerRegMaxContactExpiryDuration MAX-ACCESS changed to
read-only.
* sipServerRegDfltRegActiveInterval MAX-ACCESS changed to read-
only.
* sipProxyRecursion MAX-ACCESS changed to read-only. * sipServerRegUserUri MAX-ACCESS changed to read-only.
* sipProxyRecordRoute MAX-ACCESS changed to read-only. * 'smime' removed as a possible value for
* sipProxyAuthMethod MAX-ACCESS changed to read-only. sipServerCfgProxyAuthMethod.
* sipRegAllowThirdParty MAX-ACCESS changed to read-only.
* sipRegMaxContactExpiryDuration MAX-ACCESS changed to read-only.
* sipRegDfltRegActiveInterval MAX-ACCESS changed to read-only.
* sipUserUri MAX-ACCESS changed to read-only.
* 'smime' removed as a possible value for sipProxyAuthMethod.
o SIP-UA-MIB o SIP-UA-MIB
* sipUACfgServerStatus removed from the MIB due to general * sipUACfgServerStatus removed from the MIB due to general
removal of configuration capability. In conjunction, RowStatus removal of configuration capability. In conjunction, RowStatus
textual convention is no longer imported. textual convention is no longer imported.
* sipUACfgServerAddrType MAX-ACCESS changed to read-only. * sipUACfgServerAddressType MAX-ACCESS changed to read-only.
* sipUACfgServerAddr MAX-ACCESS changed to read-only. * sipUACfgServerAddress MAX-ACCESS changed to read-only.
* sipUACfgServerFunction MAX-ACCESS changed to read-only. * sipUACfgServerRole MAX-ACCESS changed to read-only.
Changes from draft-ietf-sip-mib-07. Changes from draft-ietf-sip-mib-07.
The vast majority of changes are in response to the Working Group The vast majority of changes are in response to the Working Group
Last Call and expert review comments. Last Call and expert review comments.
o General o General
* IANA requirements section added to specify the need for * IANA requirements section added to specify the need for
registered numbers for all SIP methods. These will be used in registered numbers for all SIP methods. These will be used in
the MIB objects. the MIB objects.
* Updated the security consideration section to reflect the * Updated the security consideration section to reflect the
addition and deletion of a number of objects. addition and deletion of a number of objects.
o SIP-COMMON-MIB o SIP-COMMON-MIB
* Module description of various SIP entities enhanced. * Module description of various SIP entities enhanced.
* sipMaxSessions renamed sipMaxTransactions. Workgroup last call * sipMaxSessions renamed sipCommonCfgMaxTransactions. Workgroup
reviewers suggested a change based on some change of terms in last call reviewers suggested a change based on some change of
the standard. Transactions seemed the appropriate term. The terms in the standard. Transactions seemed the appropriate
object description was also enhanced. term. The object description was also enhanced.
* sipRequestUriHostMatching object removed based on comments from * sipRequestUriHostMatching object removed based on comments from
workgroup last call comments. workgroup last call comments.
* sipEntityType changed from enumerated INTEGER to SipEntityRole * sipCommonCfgEntityType changed from enumerated INTEGER to
textual convention syntax. SipTCEntityRole textual convention syntax.
* sipServiceAdminStatus enumerated value 'quiesceSessions' * sipCommonServiceAdminStatus enumerated value 'quiesceSessions'
changed to 'quiesceDialogs'. changed to 'quiesceDialogs'.
* sipPortTable was redesigned. sipTransportSnd object was removed * sipCommonPortTable was redesigned. sipTransportSnd object was
as it did not make much sense. sipPortStatus was removed to removed as it did not make much sense. sipCommonPortStatus was
prevent any row creation deletion. The remaining object, removed to prevent any row creation deletion. The remaining
sipTransportRcv was made read-only. object, sipCommonPortTransportRcv was made read-only.
* sipUriSupportedTable was removed as it was not deemed useful * sipUriSupportedTable was removed as it was not deemed useful
anymore. anymore.
* sipExtMethodSupportedTable replaced with a general * sipExtMethodSupportedTable replaced with a general
sipMethodSupportedTable. IANA SIP method identifiers/numbers sipCommonMethodSupportedTable. IANA SIP method identifiers/
will be used in this new table. The previous concept of numbers will be used in this new table. The previous concept
explicitly defining objects per the current well-know methods of explicitly defining objects per the current well-know
and then providing separate, semantically similar, 'extension methods and then providing separate, semantically similar,
methods' tables has been eliminated. 'extension methods' tables has been eliminated.
* sipCommonCfgTimerExtMethodTable was removed. No more need for * sipCommonCfgTimerExtMethodTable was removed. No more need for
'extension methods' tables. 'extension methods' tables.
* sipCommonCfgRetryTable was removed. Limits on retransmissions * sipCommonCfgRetryTable was removed. Limits on retransmissions
are controlled by timers in the SIP standard now rather than by are controlled by timers in the SIP standard now rather than by
maximum counts; therefore, these objects were no longer maximum counts; therefore, these objects were no longer
relevant. sipCommonConfigRetryGroup was likewise removed. relevant. sipCommonConfigRetryGroup was likewise removed.
* sipFtrSupportedTable was redesigned as sipOptionTagsTable. * sipFtrSupportedTable was redesigned as
sipCommonOptionTagsTable.
* sipCommonCfgTimerExtMethodTable was removed. * sipCommonCfgTimerExtMethodTable was removed.
* sipSummaryTotalTransactions description changed to reflect that * sipCommonSummaryTotalTransactions description changed to
in the case of forked request, _each_ branch rather than _all_ reflect that in the case of forked request, _each_ branch
branches count as a single transaction. rather than _all_ branches count as a single transaction.
* sipMethodStatsTable was redesigned, taking into account the new * sipCommonMethodStatsTable was redesigned, taking into account
SipMethodIdentifer textual convention. The objects were the new SipMethodIdentifer textual convention. The objects
generalized to two: sipStatsOutbound and sipStatsInbound. The were generalized to two: sipCommonStatsOutbound and
indexing object (sipStatsMethod) has syntax SipMethodIdentifier sipCommonStatsInbound. The indexing object
and thereby identifies the method associated with the instances (sipCommonMethodStats) has syntax SipMethodIdentifier and
of in/out counter objects. thereby identifies the method associated with the instances of
* sipCurrentTransactions description changed to reflect that in in/out counter objects.
the case of forked request, _each_ branch rather than _all_ * sipCommonTransCurrentactions description changed to reflect
branches count as a single transaction. that in the case of forked request, _each_ branch rather than
_all_ branches count as a single transaction.
* sipCommonStatsRetryTable was redesigned, taking into account * sipCommonStatsRetryTable was redesigned, taking into account
the new SipMethodIdentifer textual convention. A single, the new SipMethodIdentifer textual convention. A single,
generalize object (sipStatsRetries) replaces several method- generalize object (sipCommonStatsRetries) replaces several
specific objects. The new, additional indexing object method-specific objects. The new, additional indexing object
(sipStatsRetryMethod) has syntax SipMethodIdentifier and (sipCommonStatsRetryMethod) has syntax SipMethodIdentifier and
thereby identifies the method associated with the instances of thereby identifies the method associated with the instances of
the counter objects in each row. the counter objects in each row.
* sipCommonStatsRetryExtMethodTable was removed. * sipCommonStatsRetryExtMethodTable was removed.
* sipStatusCodeClassesTable removed. * sipStatusCodeClassesTable removed.
* sipOtherStatsTable has two new objects added: * sipCommonOtherStatsTable has two new objects added:
sipNumUnsupportedMethods and sipOtherwiseDiscardedMsgs. sipCommonNumUnsupportedMethods and
sipCommonOtherStatsOtherwiseDiscardedMsgs.
* The following object-groups were removed because their * The following object-groups were removed because their
associated objects were removed: associated objects were removed:
sipCommonConfigTimerExtMethodGroup, sipCommonConfigRetryGroup, sipCommonConfigTimerExtMethodGroup, sipCommonConfigRetryGroup,
sipCommonConfigRetryExtMethodGroup, sipCommonConfigRetryExtMethodGroup,
sipCommonStatsRetryExtMethodsGroup, and sipCommonStatsRetryExtMethodsGroup, and
sipCommonConfigExpiresGroup. The references to these object- sipCommonConfigExpiresGroup. The references to these object-
groups as optional in the module-compliance was updated groups as optional in the module-compliance was updated
accordingly. accordingly.
* GROUP clause for sipCommonStatsRetryGroup in module-compliance * GROUP clause for sipCommonStatsRetryGroup in module-compliance
was udpated to no longer state any dependency on was udpated to no longer state any dependency on
sipCommonConfigRetryGroup (now removed). sipCommonConfigRetryGroup (now removed).
* New OBJECT clauses were added to the module-compliance to * New OBJECT clauses were added to the module-compliance to
formalize MIN-ACCESS read-only for objects in formalize MIN-ACCESS read-only for objects in
sipCommonCfgTimerTable. sipCommonCfgTimerTable.
* sipCommonConfigGroup udpated with new objects (sipOptionTag, * sipCommonConfigGroup udpated with new objects
sipOptionTagHeaderField, sipMethodName), removed objects (sipCommonOptionTag, sipCommonOptionTagHeaderField,
(sipTransportSnd, sipPortStatus, sipUriSupported, sipMethodName), removed objects (sipTransportSnd,
sipFtrSupported, sipExtMethodName, sipRequestUriHostMatching), sipCommonPortStatus, sipUriSupported, sipFtrSupported,
and changed objects (sipMaxTransactions). sipExtMethodName, sipRequestUriHostMatching), and changed
objects (sipCommonCfgMaxTransactions).
* sipCommonStatsGroup updated with new objects * sipCommonStatsGroup updated with new objects
(sipStatsOutbounds, sipStatsInbounds, sipNumUnsupportedMethods, (sipCommonMethodStatsOutbounds, sipCommonMethodStatsInbounds,
sipOtherwiseDiscardedMsgs) and removed objects sipCommonNumUnsupportedMethods,
(sipStatsInviteIns, sipStatsInviteOuts, sipStatsAckIns, sipCommonOtherStatsOtherwiseDiscardedMsgs) and removed objects
sipStatsAckOuts, sipStatsByeIns, sipStatsByeOuts, (sipCommonStatsInviteIns, sipCommonStatsInviteOuts,
sipStatsCancelIns, sipStatsCancelOuts, sipStatsOptionsIns, sipCommonStatsAckIns, sipCommonStatsAckOuts,
sipStatsOptionsOuts, sipStatsRegisterIns, sipStatsRegisterOuts, sipCommonStatsByeIns, sipCommonStatsByeOuts,
sipStatsExtMethodIns, sipStatsExtMethodOuts, sipCommonStatsCancelIns, sipCommonStatsCancelOuts,
sipStatsInfoClassIns, sipStatsInfoClassOuts, sipCommonStatsOptionsIns, sipCommonStatsOptionsOuts,
sipStatsSuccessClassIns, sipStatsSuccessClassOuts, sipCommonStatsRegisterIns, sipCommonStatsRegisterOuts,
sipStatsRedirClassIns, sipStatsRedirClassOuts, sipCommonStatsExtMethodIns, sipCommonStatsExtMethodOuts,
sipStatsReqFailClassIns, sipStatsReqFailClassOuts, sipCommonStatsInfoClassIns, sipCommonStatsInfoClassOuts,
sipStatsServerFailClassIns, sipStatsServerFailClassOuts, sipCommonStatsSuccessClassIns, sipCommonStatsSuccessClassOuts,
sipStatsGlobalFailClassIns, sipStatsGlobalFailClassOuts, sipCommonStatsRedirClassIns, sipCommonStatsRedirClassOuts,
sipStatsOtherClassesIns, sipStatsOtherClassesOuts). sipCommonStatsReqFailClassIns, sipCommonStatsReqFailClassOuts,
sipCommonStatsServerFailClassIns,
sipCommonStatsServerFailClassOuts,
sipCommonStatsGlobalFailClassIns,
sipCommonStatsGlobalFailClassOuts,
sipCommonOtherStatsClassesIns, sipCommonOtherStatsClassesOuts).
* sipCommonStatsRetryGroup updated with new object * sipCommonStatsRetryGroup updated with new object
(sipStatsRetries) and removed objects (sipStatsRetryInvites, (sipCommonStatsRetries) and removed objects
sipStatsRetryByes, sipStatsRetryCancels, (sipCommonStatsRetryInvites, sipCommonStatsRetryByes,
sipStatsRetryRegisters, sipStatsRetryOptions). sipCommonStatsRetryCancels, sipCommonStatsRetryRegisters,
sipCommonStatsRetryOptions).
o SIP-SERVER-MIB o SIP-SERVER-MIB
* Module description of various SIP entities enhanced. * Module description of various SIP entities enhanced.
* sipServerStats 'placeholder' IOD removed. No objects were ever * sipServerStats 'placeholder' IOD removed. No objects were ever
defined under that subtree. defined under that subtree.
* Removed the following objects from sipProxyCfgTable: * Removed the following objects from sipServerProxyCfgTable:
sipRequestMaxExpires, sipProxySendsCancel, sipRequestMaxExpires, sipServerProxySendsCancel,
sipProxyForwardAll1xx, sipProxyProvideAlternatives, and sipServerProxyForwardAll1xx, sipServerProxyProvideAlternatives,
sipProxyNonceLifeTime. sipProxyConfigGroup updated accordingly. and sipServerProxyNonceLifeTime. sipServerProxyConfigGroup
* sipProxyStatefulness MAX-ACCESS changed to read-only. updated accordingly.
* DEFVAL removed from sipRegMaxContactExpiryDuration. * sipServerCfgProxyStatefulness MAX-ACCESS changed to read-only.
* sipContactRetryAfter removed from sipContactTable. * DEFVAL removed from sipServerRegMaxContactExpiryDuration.
* sipUser* and sipContact* objects were moved from * sipServerRegContactRetryAfter removed from
sipRegistrarConfigGroup to a new object-group: sipServerRegContactTable.
sipRegistrarUsersGroup. The new group was made an optional * sipUser* and sipServerRegContact* objects were moved from
group in the MODULE-COMPLIANCE. sipServerRegistrarConfigGroup to a new object-group:
sipServerRegistrarUsersGroup. The new group was made an
optional group in the MODULE-COMPLIANCE.
o SIP-UA-MIB o SIP-UA-MIB
* SipEntityRole imported from SIP-TC module and used as the * SipTCEntityRole imported from SIP-TC-MIB module and used as the
syntax for new object sipUACfgServerFunction. syntax for new object sipUACfgServerRole.
* sipUACfgSipServerTable (and objects therein) have their * sipUACfgSipServerTable (and objects therein) have their
descriptors changed to sipUACfgServer* ("Sip" removed). descriptors changed to sipUACfgServer* ("Sip" removed).
sipUAConfigGroup updated accordingly. sipUAConfigGroup updated accordingly.
* sipUACfgServerFunction added to sipUACfgServerTable. * sipUACfgServerRole added to sipUACfgServerTable.
* DEFVAL { ipv4 } removed from sipUACfgServerAddressType.
* DEFVAL { ipv4 } removed from sipUACfgServerAddrType. o SIP-TC-MIB
o SIP-TC * New textual conventions: SipTCEntityRole,
* New textual conventions: SipEntityRole, SipOptionTagHeaders, SipTCOptionTagHeaders, and SipMethodIdentifier added.
and SipMethodIdentifier added.
Changes from draft-ietf-sip-mib-06 Changes from draft-ietf-sip-mib-06
o General o General
* Minor editorial changes in the Textual Conventions section. * Minor editorial changes in the Textual Conventions section.
o SIP-COMMON-MIB o SIP-COMMON-MIB
* sipStatusCodeValue SYNTAX changed from INTEGER to Unsigned32. * sipCommonStatusCodeValue SYNTAX changed from INTEGER to
Unsigned32.
* Optional sipCommonNotifObjectsGroup explicitly added to MODULE- * Optional sipCommonNotifObjectsGroup explicitly added to MODULE-
COMPLIANCE. COMPLIANCE.
* Removed OBJECT refinement for sipStatusCodeRowStatus added to * Removed OBJECT refinement for sipCommonStatusCodeRowStatus
compliance in previous revision. SMIC MIB compiler issues added to compliance in previous revision. SMIC MIB compiler
required it to be commented out. Instead, simply removed it. issues required it to be commented out. Instead, simply
removed it.
o SIP-SERVER-MIB o SIP-SERVER-MIB
* Removed OID placeholders: sipRedirCfg, sipRedirStats. sipRegCfg * Removed OID placeholders: sipRedirCfg, sipRedirStats.
and sipRegStats OID values subsequently changed as a result. sipServerRegCfg and sipServerRegStats OID values subsequently
changed as a result.
o SIP-UA-MIB o SIP-UA-MIB
* Removed OBJECT refinement for sipUACfgSipServerStatus added to * Removed OBJECT refinement for sipUACfgSipServerStatus added to
compliance in previous revision. SMIC MIB compiler issues compliance in previous revision. SMIC MIB compiler issues
required it to be commented out. Instead, simply removed it. required it to be commented out. Instead, simply removed it.
Changes from draft-ietf-sip-mib-05 Changes from draft-ietf-sip-mib-05
o Front paper/Back paper and General changes o Front paper/Back paper and General changes
* Removed all references and special handling of SIP INFO method * Removed all references and special handling of SIP INFO method
Removed references and objects specific to RFC 2976: INFO will Removed references and objects specific to RFC 2976: INFO will
be treated as any SIP extension method. be treated as any SIP extension method.
* Changed requirements verbs from lowercase to uppercase wherever * Changed requirements verbs from lowercase to uppercase wherever
appropriate. appropriate.
* Added RFC Editor notes. * Added RFC Editor notes.
* Updated all REFERENCE clauses and DESCRIPTIONS from RFC 2543 to * Updated all REFERENCE clauses and DESCRIPTIONS from RFC 2543 to
RFC 3261. RFC 3261.
* Explained the approach taken for extension methods that might * Explained the approach taken for extension methods that might
be defined in the future. be defined in the future.
* Defined a mapping of sipServiceOperStatus to applOperStatus. * Defined a mapping of sipCommonCfgServiceOperStatus to
applOperStatus.
* Enhanced Security section with details on various objects. * Enhanced Security section with details on various objects.
* Added descriptive language to various Entry objects regarding * Added descriptive language to various Entry objects regarding
the expected persistence of data across system restarts. the expected persistence of data across system restarts.
o SIP-COMMON-MIB o SIP-COMMON-MIB
* Removed sipTransactionTable after input from SIP community. * Removed sipTransactionTable after input from SIP community.
* Made all extension method tables augmentations of * Made all extension method tables augmentations of
sipExtMethodSupportedTable. This resulted in the removal of sipExtMethodSupportedTable. This resulted in the removal of
the following objects: sipCfgTimerExtMethodName, the following objects: sipCfgTimerExtMethodName,
sipCfgRetryExtMethodName, sipStatsExtMethodName, sipCfgRetryExtMethodName, sipCommonStatsExtMethodName,
sipStatsRetryExtMethodName. sipCommonStatsRetryExtMethodName.
* sipCommonStatusCodeNotifEmitMode default value changed to * sipCommonStatusCodeNotifEmitMode default value changed to
'triggered'. 'triggered'.
* sipStatusCodeThreshExceededNotif was replaced by two * sipCommonStatusCodeThreshExceededNotif was replaced by two
notifications: sipStatusCodeThreshExceededOutNotif and notifications: sipCommonStatusCodeThreshExceededOutNotif and
sipStatusCodeThreshExceededInNotif. sipCommonStatusCodeThreshExceededInNotif.
* Re-arranged the enumerated value of sipServiceOperStatus; * Re-arranged the enumerated value of
making 'unknown' the first value. Added some words to the sipCommonCfgServiceOperStatus; making 'unknown' the first
DESCRIPTION of that object stating the values are not based on value. Added some words to the DESCRIPTION of that object
anything in the SIP standard. stating the values are not based on anything in the SIP
standard.
* Clarified rules for capitalization of sipExtMethodName. * Clarified rules for capitalization of sipExtMethodName.
* All counters in the MIB are consistent with respect to * All counters in the MIB are consistent with respect to
resetting to zero. No counters can be reset to zero. Entries resetting to zero. No counters can be reset to zero. Entries
in sipStatusCodesTable can simply be created or destroyed - no in sipCommonStatusCodeTable can simply be created or destroyed
ability to set to 'notInService' where there was the question/ - no ability to set to 'notInService' where there was the
possibility of resetting the counters to zero. question/possibility of resetting the counters to zero.
sipStatsExtMethodTable no longer has its own RowStatus object, sipCommonStatsExtMethodTable no longer has its own RowStatus
so it too can no longer be set to 'notInService' where there object, so it too can no longer be set to 'notInService' where
was the question/possibility of resetting the counters to zero. there was the question/possibility of resetting the counters to
sipStatsExtMethodTable rows are augmentations of zero. sipCommonStatsExtMethodTable rows are augmentations of
sipExtMethodSupportedEntry. sipExtMethodSupportedEntry.
* OBJECT refinement for sipStatusCodeRowStatus added to * OBJECT refinement for sipCommonStatusCodeRowStatus added to
compliance. compliance.
* Clarified the relationship between * Clarified the relationship between
sipCommonStatusCodeNotifEmitMode and sipCommonStatusCodeNotifEmitMode and
sipCommonStatusCodeNotifSend. sipCommonStatusCodeNotifSend.
* Explained the existence of sipNotifApplIndex object better. * Explained the existence of sipCommonNotifApplIndex object
better.
* sipCfgExpiresStatusCodeValue syntax changed from INTEGER to * sipCfgExpiresStatusCodeValue syntax changed from INTEGER to
Unsigned32. Unsigned32.
* sipEntityType object added to sipCommonCfgTable. * sipCommonCfgEntityType object added to sipCommonCfgTable.
* All accessible-for-notify objects are moved into * All accessible-for-notify objects are moved into
sipCommonNotifObjects group. OIDs for actual notifications are sipCommonNotifObjects group. OIDs for actual notifications are
re-assigned as a result. re-assigned as a result.
* sipNotifSequenceNumber accessible-for-notify object added as a * sipCommonNotifSequenceNumber accessible-for-notify object added
way for managers to gain insight into possible missed as a way for managers to gain insight into possible missed
notifications. It is bound to each notification defined in the notifications. It is bound to each notification defined in the
MIB. MIB.
* New notifications related to SIP service operational status are * New notifications related to SIP service operational status are
added: sipServiceColdStart, sipServiceWarmStart, and added: sipCommonServiceColdStart, sipCommonServiceWarmStart,
sipServiceLastChanged. and sipCommonCfgServiceLastChange.
* New object sipServiceNotifEnable added to control the new SIP * New object sipCommonCfgServiceNotifEnable added to control the
related notifications. new SIP related notifications.
* Minor object descriptor changes: sipStatusCodesTable renamed to * Minor object descriptor changes: sipCommonStatusCodeTable
sipStatusCodeClassesTable SipStatusCodesEntry renamed to renamed to sipStatusCodeClassesTable SipCommonStatusCodeEntry
SipStatusCodeClassesEntry sipStatusCodesEntry renamed to renamed to SipStatusCodeClassesEntry sipCommonStatusCodeEntry
sipStatusCodeClassesEntry sipCommonStatusCodeTable renamed to renamed to sipStatusCodeClassesEntry sipCommonStatusCodeTable
sipStatusCodesTable SipCommonStatusCodeEntry renamed to renamed to sipCommonStatusCodeTable SipCommonStatusCodeEntry
SipStatusCodesEntry sipCommonStatusCodeEntry renamed to renamed to SipCommonStatusCodeEntry sipCommonStatusCodeEntry
sipStatusCodesEntry sipCommonStatusCodeValue renamed to renamed to sipCommonStatusCodeEntry sipCommonStatusCodeValue
sipStatusCodeValue sipCommonStatusCodeIns renamed to renamed to sipCommonStatusCodeValue sipCommonStatusCodeIns
sipStatusCodeIns sipCommonStatusCodeOuts renamed to renamed to sipCommonStatusCodeIns sipCommonStatusCodeOuts
sipStatusCodeOuts sipCommonStatusCodeStatus renamed to renamed to sipCommonStatusCodeOuts sipCommonStatusCodeStatus
sipStatusCodeRowStatus sipCommonStatusCodeNotifTable renamed to renamed to sipCommonStatusCodeRowStatus
sipStatusCodeNotifTable SipCommonStatusCodeNotifEntry renamed sipCommonStatusCodeNotifTable renamed to
to SipStatusCodeNotifEntry sipCommonStatusCodeNotifEntry sipCommonStatusCodeNotifTable SipCommonStatusCodeNotifEntry
renamed to sipStatusCodeNotifEntry sipCommonStatusCodeNotifSend renamed to SipCommonStatusCodeNotifEntry
renamed to sipStatusCodeNotifSend sipCommonStatusCodeNotifEntry renamed to
sipCommonStatusCodeNotifEntry sipCommonStatusCodeNotifSend
renamed to sipCommonStatusCodeNotifSend
sipCommonStatusCodeNotifEmitMode renamed to sipCommonStatusCodeNotifEmitMode renamed to
sipStatusCodeNotifEmitMode sipCommonStatusCodeNotifThresh sipCommonStatusCodeNotifEmitMode sipCommonStatusCodeNotifThresh
renamed to sipStatusCodeNotifThresh renamed to sipCommonStatusCodeNotifThresh
sipCommonStatusCodeNotifInterval renamed to sipCommonStatusCodeNotifInterval renamed to
sipStatusCodeNotifInterval sipCommonStatusCodeNotifInterval
* Removed all INFO method specific objects: sipCfgRetryInfo, * Removed all INFO method specific objects: sipCfgRetryInfo,
sipStatsInfoIns, sipStatsInfoOuts, and sipStatsRetryInfos sipCommonStatsInfoIns, sipCommonStatsInfoOuts, and
* Clarifying words added to sipStatusCodeNotifTable DESCRIPTION sipCommonStatsRetryInfos
to explain why it's a separate table from sipStatusCodesTable. * Clarifying words added to sipCommonStatusCodeNotifTable
DESCRIPTION to explain why it's a separate table from
sipCommonStatusCodeTable.
o SIP-SERVER-MIB o SIP-SERVER-MIB
* Deleted objects related to 'action' parameter. RFC 3261 * Deleted objects related to 'action' parameter. RFC 3261
section 10.2 deprecates the 'action' parameter deleted 3 section 10.2 deprecates the 'action' parameter deleted 3
objects: sipServerContactDfltAction, sipServerRespectUAAction, objects: sipServerContactDfltAction, sipServerRespectUAAction,
sipContactAction. sipServerRegContactAction.
* Deleted pgp-related objects. RFC 3261 section 23 deprecates * Deleted pgp-related objects. RFC 3261 section 23 deprecates
use of pgp deleted 3 objects: sipProxyAuthPgpAlgorithm, use of pgp deleted 3 objects: sipServerProxyAuthPgpAlgorithm,
sipPgpPrivateKey, sipPgpVersion. sipPgpPrivateKey, sipPgpVersion.
* Removed sipProxyStateTimeout object. Timers G and timer H have * Removed sipServerProxyStateTimeout object. Timers G and timer
been introduced in RFC 3261 for this purpose (see RFC 3261 H have been introduced in RFC 3261 for this purpose (see RFC
section 17.2.1). 3261 section 17.2.1).
* Updated description clause of sipProxyStatefulness. The 3 * Updated description clause of sipServerCfgProxyStatefulness.
definitions of stateless/statefulness now match the text in RFC The 3 definitions of stateless/statefulness now match the text
3261. in RFC 3261.
* Changed DEFVAL for object sipProxyProvideAlternatives. Changed
DEFVAL to true to align with RFC 3261 that states that 485 * Changed DEFVAL for object sipServerProxyProvideAlternatives.
responses SHOULD contain a contact header and 303 MAY... and Changed DEFVAL to true to align with RFC 3261 that states that
updated REFERENCE clause to "RFC 3261 Sections 13.2.2.2 and 485 responses SHOULD contain a contact header and 303 MAY...
and updated REFERENCE clause to "RFC 3261 Sections 13.2.2.2 and
16.5". 16.5".
* Removed basic authentication value from sipProxyAuthMethod * Removed basic authentication value from
object Per section 22 of RFC 3261, deprecated. sipServerCfgProxyAuthMethod object Per section 22 of RFC 3261,
* Changed SYNTAX of sipProxyNonceLifeTime from Integer32 to deprecated.
* Changed SYNTAX of sipServerProxyNonceLifeTime from Integer32 to
Unsigned32. Unsigned32.
* Updated description clause of sipRegDfltRegActiveInterval Per * Updated description clause of sipServerRegDfltRegActiveInterval
RFC 3261 Section 10.2. Per RFC 3261 Section 10.2.
o SIP-UA-MIB o SIP-UA-MIB
* OBJECT refinement for sipUACfgSipServerStatus added to * OBJECT refinement for sipUACfgSipServerStatus added to
compliance. compliance.
* Changed the object descriptors of sipUACfgSipServerAddrIndex to * Changed the object descriptors of sipUACfgSipServerAddrIndex to
sipUACfgSipServerIndex, and sipUACfgSipServerAddrStatus to sipUACfgSipServerIndex, and sipUACfgSipServerAddrStatus to
sipUACfgSipServerStatus. sipUACfgSipServerStatus.
Changes from draft-ietf-sip-mib-04 Changes from draft-ietf-sip-mib-04
o Started realignment with SIP RFC3261. o Started realignment with SIP RFC3261.
skipping to change at page 87, line 27 skipping to change at page 89, line 46
* sipCommonCfgExpires OID subtree added. Per method Expires * sipCommonCfgExpires OID subtree added. Per method Expires
configuration objects were added there. This new high-level configuration objects were added there. This new high-level
OID was placed under the existing sipCommonCfgRetry OID and OID was placed under the existing sipCommonCfgRetry OID and
therefore, caused the OIDs for the subsequent groups to change therefore, caused the OIDs for the subsequent groups to change
(incrementing by one). (incrementing by one).
* Objects from tables under sipCommonCfgExpires were added to a * Objects from tables under sipCommonCfgExpires were added to a
new OBJECT-GROUP sipCommonConfigExpiresGroup, and that group new OBJECT-GROUP sipCommonConfigExpiresGroup, and that group
was listed as optional in sipCommonCompliance. was listed as optional in sipCommonCompliance.
* Minor DESCRIPTION change for sipCommonCfgEntry. No behavior * Minor DESCRIPTION change for sipCommonCfgEntry. No behavior
change. change.
* sipServiceOperStatus SYNTAX changed. New values added: * sipCommonCfgServiceOperStatus SYNTAX changed. New values
congested and quiescing Old values removed: halted The order of added: congested and quiescing Old values removed: halted The
the enumeration was altered as well. order of the enumeration was altered as well.
* sipServiceAdminStatus SYNTAX changed. New values added: noop, * sipCommonServiceAdminStatus SYNTAX changed. New values added:
up, down, quieseSessions, and quieseApplications Old values noop, up, down, quieseSessions, and quieseApplications Old
removed: shutdown, restart, stop, rts. These changes were made values removed: shutdown, restart, stop, rts. These changes
based on comments from last call reviewer and general known were made based on comments from last call reviewer and general
ambiguities in the previous design of the object. known ambiguities in the previous design of the object.
* Clarifying changes to the DESCRIPTION of sipServiceStartTime. * Clarifying changes to the DESCRIPTION of
* Clarifying changes to the DESCRIPTION of sipServiceStartTime. sipCommonCfgServiceStartTime.
* Clarification of behavior for sipPortStatus while row is * Clarifying changes to the DESCRIPTION of
sipCommonCfgServiceStartTime.
* Clarification of behavior for sipCommonPortStatus while row is
'active' 'active'
* Clarifying changes to the DESCRIPTION of sipUriSupportedTable. * Clarifying changes to the DESCRIPTION of sipUriSupportedTable.
* Clarifying changes to the DESCRIPTIONs of sipFtrSupportedTable, * Clarifying changes to the DESCRIPTIONs of sipFtrSupportedTable,
sipFtrSupportedEntry, and sipFtrSupported. Specifically, IETF sipFtrSupportedEntry, and sipFtrSupported. Specifically, IETF
standard features and non-standard features are now represented standard features and non-standard features are now represented
by this table. Only non-standard features were mentioned in by this table. Only non-standard features were mentioned in
prior revisions of the draft. prior revisions of the draft.
* Reference to usage of RFC 2788 applIndex moved from * Reference to usage of RFC 2788 applIndex moved from
sipCommonCfgTimerExtMethodTable to sipCommonCfgTimerExtMethodTable to
sipCommonCfgTimerExtMethodEntry. This was the convention for sipCommonCfgTimerExtMethodEntry. This was the convention for
skipping to change at page 88, line 4 skipping to change at page 90, line 25
by this table. Only non-standard features were mentioned in by this table. Only non-standard features were mentioned in
prior revisions of the draft. prior revisions of the draft.
* Reference to usage of RFC 2788 applIndex moved from * Reference to usage of RFC 2788 applIndex moved from
sipCommonCfgTimerExtMethodTable to sipCommonCfgTimerExtMethodTable to
sipCommonCfgTimerExtMethodEntry. This was the convention for sipCommonCfgTimerExtMethodEntry. This was the convention for
other table/entry definitions in the MIB, so these objects were other table/entry definitions in the MIB, so these objects were
previously unconventional. previously unconventional.
* DEFVAL removed from sipCfgTimerExtMethodTimer. The generic * DEFVAL removed from sipCfgTimerExtMethodTimer. The generic
nature of the "extension" object does not lend itself to being nature of the "extension" object does not lend itself to being
able to specify a particular default value. able to specify a particular default value.
* Since the removal of the DEFVAL clause from * Since the removal of the DEFVAL clause from
sipCfgTimerExtMethodTimer, a value for that object must be sipCfgTimerExtMethodTimer, a value for that object must be
specified when creating a sipCommonCfgTimerExtMethodEntry. The specified when creating a sipCommonCfgTimerExtMethodEntry. The
description of sipCfgTimerExtMethodStatus was updated to description of sipCfgTimerExtMethodStatus was updated to
reflect this. reflect this.
* sipCommonCfgRetryExtMethodTable is now properly defined under * sipCommonCfgRetryExtMethodTable is now properly defined under
sipCommonCfgRetry OID space instead of under sipCommonCfgTimer sipCommonCfgRetry OID space instead of under sipCommonCfgTimer
OID space. OID space.
* DEFVAL removed from sipCfgRetryExtMethodRetry. The generic * DEFVAL removed from sipCfgRetryExtMethodRetry. The generic
nature of the "extension" object does not lend itself to being nature of the "extension" object does not lend itself to being
able to specify a particular default value. able to specify a particular default value.
* Since the removal of the DEFVAL clause from * Since the removal of the DEFVAL clause from
sipCfgRetryExtMethodRetry, a value for that object must be sipCfgRetryExtMethodRetry, a value for that object must be
specified when creating a sipCommonCfgRetryExtMethodEntry. The specified when creating a sipCommonCfgRetryExtMethodEntry. The
description of sipCfgRetryExtMethodStatus was updated to description of sipCfgRetryExtMethodStatus was updated to
reflect this. reflect this.
* Clarifying changes to the DESCRIPTION of * Clarifying changes to the DESCRIPTION of
sipSummaryTotalTransactions. Specifically, the object is not sipCommonSummaryTotalTransactions. Specifically, the object is
applicable to stateless SIP proxy servers and the object should not applicable to stateless SIP proxy servers and the object
always return a value of 0 if implemented by a stateless proxy. should always return a value of 0 if implemented by a stateless
proxy.
* Clarifying changes to the DESCRIPTION of * Clarifying changes to the DESCRIPTION of
sipStatsExtMethodStatus. sipCommonStatsExtMethodStatus.
* sipStatsOtherClassesIns and sipStatsOtherClassesOuts counter * sipCommonOtherStatsClassesIns and
objects were added to sipStatusCodesTable to handle possible sipCommonOtherStatsClassesOuts counter objects were added to
future classes of response status codes. sipCommonStatusCodeTable to handle possible future classes of
response status codes.
* Text referring specifically to Redirect Server in * Text referring specifically to Redirect Server in
sipStatsRedirClassIns and sipStatsRedirClassOuts was removed. sipCommonStatsRedirClassIns and sipCommonStatsRedirClassOuts
* Text defining protocol behavior in sipStatsServerFailClassIns, was removed.
sipStatsServerFailClassOuts, sipStatsGlobalFailClassIns, and * Text defining protocol behavior in
sipStatsGlobalFailClassOuts was removed. sipCommonStatsServerFailClassIns,
sipCommonStatsServerFailClassOuts,
sipCommonStatsGlobalFailClassIns, and
sipCommonStatsGlobalFailClassOuts was removed.
* sipCommonStatusCodeNotifInterval SYNTAX changed from TimeTicks * sipCommonStatusCodeNotifInterval SYNTAX changed from TimeTicks
to Unsigned32 w/ a UNITS of "seconds" added to the definition. to Unsigned32 w/ a UNITS of "seconds" added to the definition.
DEFVAL clause changed accordingly. DEFVAL clause changed accordingly.
* sipStatusCodeNotifTo, sipStatusCodeNotifFrom, * sipCommonStatusCodeNotifTo, sipCommonStatusCodeNotifFrom,
sipStatusCodeNotifCallId, and sipStatusCodeNotifCSeq all had sipCommonStatusCodeNotifCallId, and
clarifying changes to their DESCRIPTIONs. Specifically, the sipCommonStatusCodeNotifCSeq all had clarifying changes to
header name will be part of the object value and example values their DESCRIPTIONs. Specifically, the header name will be part
were given. of the object value and example values were given.
* Clarifying changes to the DESCRIPTION of sipCurrentTransTable * Clarifying changes to the DESCRIPTION of
and sipTransactionTable. Specifically, these tables are not sipCommonTransCurrentTable and sipTransactionTable.
applicable to transaction stateless SIP Proxy Servers. Specifically, these tables are not applicable to transaction
stateless SIP Proxy Servers.
* Minor grammatical change to the DESCRIPTION of * Minor grammatical change to the DESCRIPTION of
sipCurrentTransEntry. sipCommonTransCurrentEntry.
* sipTransMethod and sipTransActivityInfo objects were added to * sipTransMethod and sipTransActivityInfo objects were added to
sipTransactionTable while sipTransCallingPartyContentType and sipTransactionTable while sipTransCallingPartyContentType and
sipTransCalledPartyContentType were removed. sipTransCalledPartyContentType were removed.
* Clarifying changes to the DESCRIPTION of sipTransState. * Clarifying changes to the DESCRIPTION of sipTransState.
Specifically, noting that not all values of the object are Specifically, noting that not all values of the object are
applicable to all transaction types. applicable to all transaction types.
* sipTransTo, sipTransFrom, sipTransCallId, and sipTransCSeq all * sipTransTo, sipTransFrom, sipTransCallId, and sipTransCSeq all
had clarifying changes to their DESCRIPTIONs. Specifically, had clarifying changes to their DESCRIPTIONs. Specifically,
the header name will be part of the object value and example the header name will be part of the object value and example
values were given. values were given.
* Minor grammatical change to the DESCRIPTION of * Minor grammatical change to the DESCRIPTION of
sipOtherStatsEntry. sipCommonOtherStatsEntry.
* sipCommonStatusCodeIns and sipCommonStatusCodeOuts objects were * sipCommonStatusCodeIns and sipCommonStatusCodeOuts objects were
added to the varbind of sipStatusCodeNotif. added to the varbind of sipCommonStatusCodeNotif.
* Appropriate changes were made to sipCommonStatsGroup OBJECT- * Appropriate changes were made to sipCommonStatsGroup OBJECT-
GROUP based on objects being added and/or removed from the MIB. GROUP based on objects being added and/or removed from the MIB.
o SIP-SERVER-MIB o SIP-SERVER-MIB
* CONTACT-INFO "SIP MIB email" changed to sip@ietf.org * CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
* The statement "Unlike a Proxy server it does not initiate * The statement "Unlike a Proxy server it does not initiate
requests." was removed from where a Redirect Server is defined requests." was removed from where a Redirect Server is defined
in the MIB's DESCRIPTION. in the MIB's DESCRIPTION.
* sipServerMIBNotifs OID removed. No notifications were ever * sipServerMIBNotifs OID removed. No notifications were ever
defined under this subtree. defined under this subtree.
* Clarifying text added to all of the Table DESCRIPTIONS stating * Clarifying text added to all of the Table DESCRIPTIONS stating
that the value of applIndex used in this MIB corresponds to the that the value of applIndex used in this MIB corresponds to the
value of applIndex used in the SIP-COMMON-MIB. value of applIndex used in the SIP-COMMON-MIB.
* Clarifying changes to the DESCRIPTION of sipProxyStatefulness.
* sipContactPreference SYNTAX changed from OCTET STRING to * Clarifying changes to the DESCRIPTION of
SnmpAdminString. sipServerCfgProxyStatefulness.
* sipServerRegContactPreference SYNTAX changed from OCTET STRING
to SnmpAdminString.
o SIP-UA-MIB o SIP-UA-MIB
* CONTACT-INFO "SIP MIB email" changed to sip@ietf.org * CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
* sipUAMIBNotifs OID removed. No notifications were ever defined * sipUAMIBNotifs OID removed. No notifications were ever defined
under this subtree. under this subtree.
* sipUAStats OID removed. No notifications were ever defined * sipUAStats OID removed. No notifications were ever defined
under this subtree. under this subtree.
* Clarifying text added to all of the Table DESCRIPTIONS stating * Clarifying text added to all of the Table DESCRIPTIONS stating
that the value of applIndex used in this MIB corresponds to the that the value of applIndex used in this MIB corresponds to the
value of applIndex used in the SIP-COMMON-MIB. value of applIndex used in the SIP-COMMON-MIB.
o SIP-TC o SIP-TC-MIB
* CONTACT-INFO "SIP MIB email" changed to sip@ietf.org * CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
Changes from draft-ietf-sip-mib-02 Changes from draft-ietf-sip-mib-02
o General o General
* Eliminated the SIP-MIB-SMI modules. Each MIB module will now * Eliminated the SIP-MIB-SMI modules. Each MIB module will now
get it's own IANA OID. get it's own IANA OID.
* Top-level OID subtrees restructured in each MIB. * Top-level OID subtrees restructured in each MIB.
* General cleanup/removal of "placeholder" OID subtrees for * General cleanup/removal of "placeholder" OID subtrees for
object groups and notifications that never materialized. object groups and notifications that never materialized.
o SIP-COMMON-MIB o SIP-COMMON-MIB
* Removed sipCfgInitialTimerAck. * Removed sipCfgInitialTimerAck.
* Removed sipCfgRetryAck. * Removed sipCfgRetryAck.
* Removed sipStatsRetryAcks. * Removed sipCommonStatsRetryAcks.
* sipCommonStatsRetryExtMethodEntry was missing its INDEX clause. * sipCommonStatsRetryExtMethodEntry was missing its INDEX clause.
* sipNumUnsupportedUris OID was "5" when it was the only object * sipCommonOtherStatsNumUnsupportedUris OID was "5" when it was
in the table. OID is now "1". the only object in the table. OID is now "1".
* High-level OID structure of the MIB is now sequential. * High-level OID structure of the MIB is now sequential.
* Incorrect object descriptor for sipCfgInitialTimerRsp * Incorrect object descriptor for sipCfgInitialTimerRsp
inconsistent with reference in compliance section. inconsistent with reference in compliance section.
* Inconsistencies between sipCommonStatsRetryGroup definition and * Inconsistencies between sipCommonStatsRetryGroup definition and
SipCommonStatsRetryEntry OBJECT-TYPE corrected. SipCommonStatsRetryEntry OBJECT-TYPE corrected.
* sipNotifApplIndex was not in any object group in the * sipCommonNotifApplIndex was not in any object group in the
conformance section. conformance section.
o SIP-SERVER-MIB o SIP-SERVER-MIB
* Removed sipInformationTryingInterval. * Removed sipInformationTryingInterval.
* Removed sipRxProxyAuthTable. * Removed sipRxProxyAuthTable.
* Removed sipRegRespHasContacts. * Removed sipServerRegRespHasContacts.
* Removed sipRegContactDfltExpiryDate. * Removed sipServerRegContactDfltExpiryDate.
* Removed sipRegContactDfltExpiryDuration. * Removed sipServerRegContactDfltExpiryDuration.
* Removed sipUserPassword. * Removed sipUserPassword.
* sipRequestMaxExpires DESCRIPTION changed to no longer * sipRequestMaxExpires DESCRIPTION changed to no longer
specifically mention 400 response. specifically mention 400 response.
* sipProxyStateful object descriptor changed to
sipProxyStatefullness and the SYNTAX changed from TruthValue to * sipServerProxyStateful object descriptor changed to
an enumerated INTEGER. sipServerProxyStatefullness and the SYNTAX changed from
* sipProxyStateTimeout DESCRIPTION changed to now reflect only TruthValue to an enumerated INTEGER.
INVITE. * sipServerProxyStateTimeout DESCRIPTION changed to now reflect
only INVITE.
* Gauge32 was not being IMPORTed. * Gauge32 was not being IMPORTed.
* sipServerContactDfltAction showed up in conformance and other * sipServerContactDfltAction showed up in conformance and other
object descriptions in an older form. object descriptions in an older form.
* sipServerHost replaced with InetAddressType/InetAddress object * sipServerHost replaced with InetAddressType/InetAddress object
pair (sipServerHostAddrType and sipServerHostAddr). pair (sipServerCfgHostAddressType and sipServerCfgHostAddress).
o SIP-UA-MIB o SIP-UA-MIB
* IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex. * IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex.
* sipUACfgSipServerEntry was referencing the wrong auxiliary * sipUACfgSipServerEntry was referencing the wrong auxiliary
object and listing that object in the conformance section. object and listing that object in the conformance section.
* sipUACfgSipServerEntry listed sipUACfgSipServerStatus when it * sipUACfgSipServerEntry listed sipUACfgSipServerStatus when it
should have been listing sipUACfgSipServerAddrStatus. should have been listing sipUACfgSipServerAddrStatus.
* SIP-UA-MIB IMPORTed Counter32, but never used it. Removed the * SIP-UA-MIB IMPORTed Counter32, but never used it. Removed the
IMPORT of Counter32. IMPORT of Counter32.
12. References 12. References
skipping to change at page 93, line 36 skipping to change at page 96, line 47
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 447 change blocks. 
3144 lines changed or deleted 3307 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/