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 7, line 50 skipping to change at page 8, line 4
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:
+-----------+-------------------+----------------------+ +-----------+-------------------+----------------------+
| applIndex | applName | applDescription | | applIndex | applName | applDescription |
+-----------+-------------------+----------------------+ +-----------+-------------------+----------------------+
| 1 | "sip_proxy10" | "ACME SIP Proxy" | | 1 | "sip_proxy10" | "ACME SIP Proxy" |
| 2 | "sip_registrar17" | "ACME SIP Registrar" | | 2 | "sip_registrar17" | "ACME SIP Registrar" |
+-----------+-------------------+----------------------+ +-----------+-------------------+----------------------+
The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for the The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for the
proxy (applIndex=1) and one for the registrar (applIndex=2). The proxy (applIndex=1) and one for the registrar (applIndex=2). The
SIP-SERVER-MIB tables would, however, only be populated with one row SIP-SERVER-MIB tables would, however, only be populated with one row
indexed by applIndex=1 and applIndex=2 respectively if the server indexed by applIndex=1 and applIndex=2 respectively if the server
provides either proxy or registrar. provides either proxy or registrar.
SIP-COMMON-MIB sipCommonCfgTable might be populated as: SIP-COMMON-MIB sipCommonCfgTable might be populated as:
+-----------+--------------------+----------------------+-----+ +---------+------------------------+--------------------------+-----+
| applIndex | 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 | |
| | to --> | |
+-------------------------------+---------------+-------------------+
| up | --> | up | | up | --> | up |
| down | --> | down | | down | --> | down |
| congested | --> | congested | | congested | --> | congested |
| restarting | --> | restarting | | restarting | --> | restarting |
| quiescing | --> | quiescing | | quiescing | --> | quiescing |
| testing | --> | up | | testing | --> | up |
| unknown | --> | --indeterminate-- | | unknown | --> | --indeterminate-- |
+----------------------+-----------------------+-------------------+ +-------------------------------+---------------+-------------------+
If the sipOperStatus is 'unknown' there is no corresponding value of If the sipOperStatus is 'unknown' there is no corresponding value of
applOperStatus. Therefore, the last known value of applOperStatus applOperStatus. Therefore, the last known value of applOperStatus
SHOULD be maintained until the sipOperStatus transitions to a value SHOULD be maintained until the sipOperStatus transitions to a value
that can be mapped appropriately. that can be mapped appropriately.
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
skipping to change at page 12, line 11 skipping to change at page 12, line 15
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) MIB Textual "Session Initiation Protocol (SIP) MIB Textual Conventions
Conventions module used by other SIP-related module used by other SIP-related MIB Modules.
MIB Modules.
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 not
REVISION "200605171700Z" REVISION "200609121700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-TC module. "Initial version of the IETF SIP-TC-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 XXX1 } ::= { mib-2 XXX1 }
-- RFC Ed: replace XXX1 with actual IANA assigned number for this -- RFC Ed: replace XXX1 with actual IANA assigned number for this
-- sipTC mib module and remove this note -- sipTC mib module and remove this note
-- --
-- Textual Conventions -- Textual Conventions
-- --
SipTransportProtocol ::= TEXTUAL-CONVENTION SipTCTransportProtocol ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention is a bit map. Each bit represents a "This convention is a bit map. Each bit represents a transport
transport protocol. If a bit has value 1, then that protocol. If a bit has value 1, then that selected transport
selected transport protocol is in some way dependent protocol is in some way dependent on the context of the object
on the context of the object using this convention. using this convention. If a bit has value 0, then that
If a bit has value 0, then that transport protocol transport protocol is not selected. Combinations of bits can
is not selected. Combinations of bits can be be set when multiple transport protocols are selected.
set when multiple transport protocols are selected.
bit 0 : a protocol other than those defined here bit 0 : a protocol other than those defined here
bit 1 : User Datagram Protocol bit 1: User Datagram Protocol bit 2 : Transmission Control
bit 2 : Transmission Control Protocol Protocol
bit 3 : Stream Control Transmission Protocol bit 3 : Stream Control Transmission Protocol
bit 4 : Transport Layer Security Protocol over TCP bit 4 : Transport Layer Security Protocol over TCP
bit 5 : Transport Layer Security Protocol over SCTP" bit 5: Transport Layer Security Protocol over SCTP
"
REFERENCE "RFC 3261, Section 18 and RFC 4168"
SYNTAX BITS { SYNTAX BITS {
other(0), -- none of the following other(0), -- none of the following
udp(1), udp(1),
tcp(2), tcp(2),
sctp(3), -- RFC4168 sctp(3), -- RFC4168
tlsTcp(4), tlsTcp(4),
tlsSctp(5) -- RFC 4168 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."
User Agent (UA): A logical entity that can act as both a user
agent client and user agent server. User Agent Client (UAC):
A logical entity that creates a new request, and then uses the
client transaction state machinery to send it. The role of UAC
lasts only for the duration of that transaction. In other
words, if a piece of software initiates a request, it acts as
a UAC for the duration of that transaction. If it receives a
request later, it assumes the role of a user agent server for
the processing of that transaction. User Agent Server (UAS):
a 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 as both
a server and a client for the purpose of making requests on
behalf of other clients. A proxy server primarily plays the
role of routing, which means its job is to ensure that a
request is sent to another entity 'closer' to the targeted
user. Proxies are also useful for enforcing policy. A proxy
interprets, and, if necessary, rewrites specific parts of a
request message before forwarding it.
Redirect Server: A redirect server is a user agent server that
generates 3xx responses to requests it receives, directing the
client to contact an alternate set of URIs.
Registrar: A registrar is a server that accepts REGISTER
requests and places the information it receives in those
requests into the location service for the domain it handles."
REFERENCE
"RFC 3261, Section 6"
SYNTAX BITS { SYNTAX BITS {
other(0), other(0),
userAgent(1), userAgent(1),
proxyServer(2), proxyServer(2),
redirectServer(3), redirectServer(3),
registrarServer(4) registrarServer(4)
} }
SipOptionTagHeaders ::= TEXTUAL-CONVENTION SipTCOptionTagHeaders ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention defines the header fields that use "This convention defines the header fields that use the option
the option tags per section 19.2 of RFC 3261. tags per section 19.2 of RFC 3261. These tags are used in
These tags are used in Require (Section 20.32), Require (Section 20.32), Proxy-Require (Section 20.29),
Proxy-Require (Section 20.29), Supported Supported (Section 20.37) and Unsupported (Section 20.40)
(Section 20.37) and Unsupported (Section 20.40)
header fields." header fields."
REFERENCE
"RFC 3261, Sections 19.2, 20.32, 20.29, 20.37 and 20.40"
SYNTAX BITS { SYNTAX BITS {
require(0), -- Require header require(0), -- Require header
proxyRequire(1), -- Proxy-Require header proxyRequire(1), -- Proxy-Require header
supported(2), -- Supported header supported(2), -- Supported header
unsupported(3) -- Unsupported header unsupported(3) -- Unsupported header
} }
-- REFERENCE "RFC 3261, Section 19.2"
SipMethodName ::= TEXTUAL-CONVENTION SipTCMethodName ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is a string that uniquely "This textual convention is a string that uniquely identifies a
identifies a SIP method. The scope of uniqueness SIP method. The scope of uniqueness is the context of all
is the context of all defined SIP methods. defined SIP methods.
Experimental support of extension methods is Experimental support of extension methods is acceptable and
acceptable and expected. Extension methods are expected. Extension methods are those defined in
those defined in Internet-Draft documents but Internet-Draft documents but not yet allocated an official
not yet allocated an official sanctioned by IANA. sanctioned by IANA.
To support experimental extension methods, any To support experimental extension methods, any object using
object using this textual convention as syntax this textual convention as syntax MAY return/accept a method
MAY return/accept a method identifier value other identifier value other than those sanctioned by IANA. That
than those sanctioned by IANA. That system MUST system MUST ensure no collisions with officially assigned
ensure no collisions with officially assigned
method names." method names."
SYNTAX OCTET STRING (SIZE (1..128)) REFERENCE
"RFC 3261, Section 27.4"
SYNTAX OCTET STRING (SIZE (1..100))
END END
7.2. SIP Common MIB Module 7.2. SIP Common MIB Module
SIP-COMMON-MIB DEFINITIONS ::= BEGIN SIP-COMMON-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
Counter32, Counter32,
Gauge32, Gauge32,
TimeTicks, TimeTicks,
Unsigned32, Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
RowStatus, RowStatus,
TimeStamp,
TruthValue TruthValue
FROM SNMPv2-TC -- RFC 2579 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
skipping to change at page 15, line 39 skipping to change at page 16, line 29
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
creating, modifying and terminating multimedia
sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 3261 (June
2002).
This MIB is defined for managing objects which are
common to SIP User Agents (UAs), Proxy, Redirect
and Registrar servers. Objects specific to each of
these entities MAY be managed using entity specific
MIBs defined in other modules.
User Agent (UA): A logical entity that can act as both
a user agent client and user agent server.
User Agent Client (UAC): A logical entity that creates
a new request, and then uses the client
transaction state machinery to send it. The role of UAC
lasts only for the duration of that transaction. In
other words, if a piece of software initiates a
request, it acts as a UAC for the duration of that
transaction. If it receives a request later, it
assumes the role of a user agent server for the
processing of that transaction.
User Agent Server (UAS): a 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
as both a server and a client for the purpose of making
requests on behalf of other clients. A proxy server
primarily plays the role of routing, which means its
job is to ensure that a request is sent to another
entity 'closer' to the targeted user.
Proxies are also useful for enforcing policy. A proxy
interprets, and, if necessary, rewrites specific parts
of a request message before forwarding it.
Redirect Server: A redirect server is a user agent SIP is an application-layer signaling protocol for creating,
server that generates 3xx responses to requests it modifying and terminating multimedia sessions with one or more
receives, directing the client to contact an alternate participants. These sessions include Internet multimedia
set of URIs. conferences and Internet telephone calls. SIP is defined in
RFC 3261 (June 2002).
Registrar: A registrar is a server that accepts This MIB is defined for managing objects which are common to
REGISTER requests and places the information it SIP User Agents (UAs), Proxy, Redirect and Registrar servers.
receives in those requests into the location service Objects specific to each of these entities MAY be managed using
for the domain it handles. entity specific MIBs defined in other modules.
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 -- RFC Ed: replace XXXX with actual RFC number and
-- remove this note -- remove this note
REVISION "200605171700Z" REVISION "200609121700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-COMMON-MIB module. "Initial version of the IETF SIP-COMMON-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 XXX2 } ::= { mib-2 XXX2 }
-- RFC Ed: replace XXX2 with actual IANA assigned number and -- RFC Ed: replace XXX2 with actual IANA assigned number and
-- remove this note -- remove this note
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 } sipCommonMIBNotifications OBJECT IDENTIFIER ::= { sipCommonMIB 0 }
sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 } sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
sipCommonMIBConform OBJECT IDENTIFIER ::= { sipCommonMIB 2 } sipCommonMIBConformance OBJECT IDENTIFIER ::= { sipCommonMIB 2 }
-- --
-- This MIB contains objects that are common to all SIP entities. -- This MIB contains objects that are common to all SIP entities.
-- --
-- Common basic configuration -- Common basic configuration
sipCommonCfgBase OBJECT IDENTIFIER sipCommonCfgBase OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 }
::= { sipCommonMIBObjects 1 }
-- Protocol timer configuration -- Protocol timer configuration
sipCommonCfgTimer OBJECT IDENTIFIER sipCommonCfgTimer OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 }
::= { sipCommonMIBObjects 2 }
-- SIP message summary statistics -- SIP message summary statistics
sipCommonStatsSummary OBJECT IDENTIFIER sipCommonSummaryStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 }
::= { sipCommonMIBObjects 3 }
-- Per method statistics -- Per method statistics
sipCommonStatsMethod OBJECT IDENTIFIER sipCommonMethodStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 }
::= { sipCommonMIBObjects 4 }
-- Per Status code or status code class statistics -- Per Status code or status code class statistics
sipCommonStatusCode OBJECT IDENTIFIER sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 }
::= { sipCommonMIBObjects 5 }
-- Transaction statistics -- Transaction statistics
sipCommonStatsTrans OBJECT IDENTIFIER sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 }
::= { sipCommonMIBObjects 6 }
-- Method retry statistics -- Method retry statistics
sipCommonStatsRetry OBJECT IDENTIFIER sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 }
::= { sipCommonMIBObjects 7 }
-- Other statistics -- Other statistics
sipCommonStatsOther OBJECT IDENTIFIER sipCommonOtherStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 }
::= { sipCommonMIBObjects 8 }
-- Accessible-for-notify objects -- Accessible-for-notify objects
sipCommonNotifObjects OBJECT IDENTIFIER sipCommonNotifObjects OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 }
::= { sipCommonMIBObjects 9 }
-- --
-- Common Configuration Objects -- Common Configuration Objects
-- --
sipCommonCfgTable OBJECT-TYPE sipCommonCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgEntry SYNTAX SEQUENCE OF SipCommonCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the common configuration objects "This table contains the common configuration objects applicable
applicable to all SIP entities." to all SIP entities."
::= { sipCommonCfgBase 1 } ::= { sipCommonCfgBase 1 }
sipCommonCfgEntry OBJECT-TYPE sipCommonCfgEntry OBJECT-TYPE
SYNTAX SipCommonCfgEntry SYNTAX SipCommonCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common configuration. "A row of common configuration.
Each row represents objects for a particular SIP Each row represents objects for a particular SIP entity
entity instance present in this system. applIndex instance present in this system. applIndex is used to uniquely
is used to uniquely identify these instances of SIP identify these instances of SIP entities and correlate them
entities and correlate them through the common through the common framework of the NETWORK-SERVICES-MIB (RFC
framework of the NETWORK-SERVICES-MIB (RFC 2788)." 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipCommonCfgTable 1 } ::= { sipCommonCfgTable 1 }
SipCommonCfgEntry ::= SipCommonCfgEntry ::= SEQUENCE {
SEQUENCE { sipCommonCfgProtocolVersion SnmpAdminString,
sipProtocolVersion SnmpAdminString, sipCommonCfgServiceOperStatus INTEGER,
sipServiceOperStatus INTEGER, sipCommonCfgServiceStartTime TimeTicks,
sipServiceStartTime TimeTicks, sipCommonCfgServiceLastChange TimeTicks,
sipServiceLastChange TimeTicks, sipCommonCfgOrganization SnmpAdminString,
sipOrganization SnmpAdminString, sipCommonCfgMaxTransactions Unsigned32,
sipMaxTransactions Unsigned32, sipCommonCfgServiceNotifEnable BITS,
sipServiceNotifEnable BITS, sipCommonCfgEntityType SipTCEntityRole
sipEntityType SipEntityRole
} }
sipProtocolVersion OBJECT-TYPE sipCommonCfgProtocolVersion OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will reflect the version of SIP supported by "This object will reflect the version of SIP supported by this
this SIP entity. It will follow the same format as SIP SIP entity. It will follow the same format as SIP version
version information contained in the SIP messages information contained in the SIP messages generated by this SIP
generated by this SIP entity. For example, entities entity. For example, entities supporting SIP version 2 will
supporting SIP version 2 will return 'SIP/2.0' as return 'SIP/2.0' as dictated by the standard."
dictated by the standard."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipCommonCfgEntry 1 } ::= { sipCommonCfgEntry 1 }
sipServiceOperStatus OBJECT-TYPE sipCommonCfgServiceOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
up(2), up(2),
down(3), down(3),
congested(4), congested(4),
restarting(5), restarting(5),
quiescing(6), quiescing(6),
testing(7) testing(7)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the current operational state of "This object contains the current operational state of
the SIP application. the SIP application.
unknown : The operational status cannot be determined unknown : The operational status cannot be determined
for some reason. for some reason.
up : The application is operating normally, and up : The application is operating normally, and is
is processing (receiving and possibly processing (receiving and possibly issuing) SIP
issuing) SIP requests and responses. requests and responses.
down : The application is currently unable to down : The application is currently unable to process
process SIP messages.
congested : The application is operational but no
additional inbound transactions can be
accommodated at the 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. SIP messages.
congested : The application is operational but no additional
inbound transactions can be accommodated at the
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 quiescing : The application is currently operational
but has been administratively put into but has been administratively put into
quiescence mode. Additional inbound quiescence mode. Additional inbound
transactions MAY be rejected. transactions MAY be rejected.
testing : The application is currently in test mode testing : The application is currently in test mode
and MAY not be able to process SIP and MAY not be able to process SIP messages.
messages.
The operational status values defined for this object The operational status values defined for this object are not
are not based on any specific information contained in based on any specific information contained in the SIP
the SIP standard." standard."
::= { sipCommonCfgEntry 2 } ::= { sipCommonCfgEntry 2 }
sipServiceStartTime OBJECT-TYPE sipCommonCfgServiceStartTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the SIP entity was "The value of sysUpTime at the time the SIP entity was last
last started. If started prior to the last started. If started prior to the last re-initialization of the
re-initialization of the local network management local network management subsystem, then this object contains a
subsystem, then this object contains a zero value." zero value."
::= { sipCommonCfgEntry 3 } ::= { sipCommonCfgEntry 3 }
sipCommonCfgServiceLastChange OBJECT-TYPE
sipServiceLastChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the SIP entity "The value of sysUpTime at the time the SIP entity entered its
entered its current operational state. If the current current operational state. If the current state was entered
state was entered prior to the last re-initialization of prior to the last re-initialization of the local network
the local network management subsystem, then this object management subsystem, then this object contains a zero value."
contains a zero value."
::= { sipCommonCfgEntry 4 } ::= { sipCommonCfgEntry 4 }
sipOrganization OBJECT-TYPE sipCommonCfgOrganization OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the organization name which the SIP "This object contains the organization name which the SIP entity
entity inserts into Organization headers of SIP messages inserts into Organization headers of SIP messages processed by
processed by this system. If the string is empty, no this system. If the string is empty, no Organization header is
Organization header is to be generated." to be generated."
REFERENCE REFERENCE
"RFC 3261, Section 20.25" "RFC 3261, Section 20.25"
::= { sipCommonCfgEntry 5 } ::= { sipCommonCfgEntry 5 }
sipMaxTransactions OBJECT-TYPE sipCommonCfgMaxTransactions OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum number of simultaneous "This object indicates the maximum number of simultaneous
transactions per second that the SIP entity can manage. transactions per second that the SIP entity can manage. In
In general, the value of this object SHOULD reflect a general, the value of this object SHOULD reflect a level of
level of transaction processing per second that is transaction processing per second that is considered high
considered high enough to impact the system's CPU and/or enough to impact the system's CPU and/or memory resources to
memory resources to the point of deteriorating SIP call the point of deteriorating SIP call processing but not high
processing but not high enough to cause catastrophic enough to cause catastrophic system failure."
system failure."
::= { sipCommonCfgEntry 6 } ::= { sipCommonCfgEntry 6 }
sipServiceNotifEnable OBJECT-TYPE sipCommonCfgServiceNotifEnable OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
sipServiceColdStart(0), sipCommonServiceColdStart(0),
sipServiceWarmStart(1), sipCommonServiceWarmStart(1),
sipServiceStatusChanged(2) sipCommonServiceStatusChanged(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies which SIP service related "This object specifies which SIP service related notifications
notifications are enabled. Each bit represents are enabled. Each bit represents a specific notification. If
a specific notification. If a bit has a value 1, a bit has a value 1, the associated notification is enabled and
the associated notification is enabled and will will be generated by the SIP entity at the appropriate time.
be generated by the SIP entity at the appropriate
time. The notifications are OPTIONAL, and if they Support for these notifications is OPTIONAL: either none or all
are not implemented this object's value has no notification values are supported. If an implementation does
meaning and MUST be 0. Setting this object in that not support this object, it should return a 'noSuchObject'
circumstance SHOULD result in a badValue error. exception to an SNMP GET operation. If notifications are
If notifications are supported, this object's default supported, this object's default value SHOULD reflect
value SHOULD reflect sipServiceColdStart and sipCommonServiceColdStart and sipCommonServiceWarmStart enabled
sipServiceWarmStart enabled and sipServiceStatusChanged and sipCommonServiceStatusChanged disabled.
disabled."
This object value SHOULD persist across reboots."
DEFVAL { { sipCommonServiceColdStart,
sipCommonServiceWarmStart } }
::= { sipCommonCfgEntry 7 } ::= { sipCommonCfgEntry 7 }
sipEntityType OBJECT-TYPE sipCommonCfgEntityType OBJECT-TYPE
SYNTAX SipEntityRole SYNTAX SipTCEntityRole
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object identifies the list of SIP entities this "This object identifies the list of SIP entities this row is
row is related to. It is defined as a bit map. Each related to. It is defined as a bit map. Each bit represents a
bit represents a type of SIP entity. type of SIP entity. If a bit has value 1, the SIP entity
If a bit has value 1, the SIP entity represented by represented by this row plays the role of this entity type. If
this row plays the role of this entity type. a bit has value 0, the SIP entity represented by this row does
If a bit has value 0, the SIP entity represented by not act as this entity type Combinations of bits can be set
this row does not act as this entity type when the SIP entity plays multiple SIP roles."
Combinations of bits can be set when the SIP entity
plays multiple SIP roles."
::= { sipCommonCfgEntry 8 } ::= { sipCommonCfgEntry 8 }
-- --
-- Support for multiple ports -- Support for multiple ports
-- --
sipPortTable OBJECT-TYPE sipCommonPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipPortEntry SYNTAX SEQUENCE OF SipCommonPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the list of ports that each SIP "This table contains the list of ports that each SIP entity in
entity in this system is allowed to use. These ports this system is allowed to use. These ports can be advertised
can be advertised using the Contact header in a REGISTER using the Contact header in a REGISTER request or response."
request or response."
::= { sipCommonCfgBase 2 } ::= { sipCommonCfgBase 2 }
sipPortEntry OBJECT-TYPE sipCommonPortEntry OBJECT-TYPE
SYNTAX SipPortEntry SYNTAX SipCommonPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specification of a particular port. "Specification of a particular port.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP entity
entity present in this system. applIndex is used to present in this system. applIndex is used to uniquely identify
uniquely identify these instances of SIP entities and these instances of SIP entities and correlate them through the
correlate them through the common framework of the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
NETWORK-SERVICES-MIB (RFC 2788)." INDEX { applIndex, sipCommonPort }
INDEX { applIndex, sipPort } ::= { sipCommonPortTable 1 }
::= { sipPortTable 1 }
SipPortEntry ::= SipCommonPortEntry ::= SEQUENCE {
SEQUENCE { sipCommonPort InetPortNumber,
sipPort InetPortNumber, sipCommonPortTransportRcv SipTCTransportProtocol
sipTransportRcv SipTransportProtocol
} }
sipPort OBJECT-TYPE sipCommonPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber (1..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects a particular port that can be used "This object reflects a particular port that can be used by the
by the SIP application." SIP application."
::= { sipPortEntry 1 } ::= { sipCommonPortEntry 1 }
sipTransportRcv OBJECT-TYPE
SYNTAX SipTransportProtocol sipCommonPortTransportRcv OBJECT-TYPE
SYNTAX SipTCTransportProtocol
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the transport protocol the SIP "This object will specify the transport protocol the SIP entity
entity will use to receive SIP messages. will use to receive SIP messages.
This object is a bit map. Each bit represents a This object is a bit map. Each bit represents a transport
transport protocol. If a bit has value 1, then that protocol. If a bit has value 1, then that transport protocol
transport protocol is currently being used. If a bit is currently being used. If a bit has value 0, then that
has value 0, then that transport protocol is currently transport protocol is currently not being used."
not being used." ::= { sipCommonPortEntry 2 }
::= { sipPortEntry 2 }
-- --
-- Support for SIP option tags (SIP extensions). -- Support for SIP option tags (SIP extensions).
-- SIP extensions MAY be supported or required by SIP entities. -- SIP extensions MAY be supported or required by SIP entities.
-- --
sipOptionTagTable OBJECT-TYPE sipCommonOptionTagTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipOptionTagEntry SYNTAX SEQUENCE OF SipCommonOptionTagEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of the SIP option tags "This table contains a list of the SIP option tags (SIP
(SIP extensions) that either required, supported, or extensions) that either required, supported, or unsupported by
unsupported by the SIP entity. the SIP entity. These option tags are used in the Require,
These option tags are used in the Require,
Proxy-Require, Supported and Unsupported header fields. 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 Example: if a user agent client supports and requires the
(indicated in a Require header to a UAS, or in a server to support reliability of provisional responses (IETF
Proxy-Require to a Proxy Server), the server returns a RFC 3262), this table contains a row with the option tag string
420 Bad Extension listing the feature in an Unsupported '100rel' in sipCommonOptionTag and the OCTET STRING value of
header. '1010 0000' or '0xA0' in sipCommonOptionTagHeaderField.
Normally the list of such features supported by an If a server does not support the required feature (indicated in
entity is static (i.e. will not change over time)." a Require header to a UAS, or in a Proxy-Require to a Proxy
Server), the server returns a 420 Bad Extension listing the
feature in an Unsupported header.
Normally the list of such features supported by an entity is
static (i.e. will not change over time)."
REFERENCE REFERENCE
"RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40" "RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40"
::= { sipCommonCfgBase 3 } ::= { sipCommonCfgBase 3 }
sipOptionTagEntry OBJECT-TYPE
SYNTAX SipOptionTagEntry sipCommonOptionTagEntry OBJECT-TYPE
SYNTAX SipCommonOptionTagEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular SIP option tag (extension) supported or "A particular SIP option tag (extension) supported or
unsupported by the SIP entity, and which may be unsupported by the SIP entity, and which may be supported or
supported or required by a peer. required by a peer.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP entity
entity present in this system. applIndex is used to present in this system. applIndex is used to uniquely identify
uniquely identify these instances of SIP entities and these instances of SIP entities and correlate them through the
correlate them through the common framework of the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
NETWORK-SERVICES-MIB (RFC 2788). INDEX { applIndex, sipCommonOptionTagIndex }
The objects in this table entry SHOULD be non-volatile ::= { sipCommonOptionTagTable 1 }
and their value SHOULD be kept at reboot."
INDEX { applIndex, sipOptionTagIndex }
::= { sipOptionTagTable 1 }
SipOptionTagEntry ::= SipCommonOptionTagEntry ::= SEQUENCE {
SEQUENCE { sipCommonOptionTagIndex Unsigned32,
sipOptionTagIndex Unsigned32, sipCommonOptionTag SnmpAdminString,
sipOptionTag SnmpAdminString, sipCommonOptionTagHeaderField SipTCOptionTagHeaders
sipOptionTagHeaderField SipOptionTagHeaders
} }
sipOptionTagIndex OBJECT-TYPE sipCommonOptionTagIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in "This object uniquely identifies a conceptual row in the table."
the table." ::= { sipCommonOptionTagEntry 1 }
::= { sipOptionTagEntry 1 }
sipOptionTag OBJECT-TYPE sipCommonOptionTag OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the SIP option tag. "This object indicates the SIP option tag. The option tag names
The option tag names are registered with are registered with IANA and available at http://www.iana.org."
IANA and available at http://www.iana.org." REFERENCE "RFC 3261, Section 27.1"
::= { sipOptionTagEntry 2 } ::= { sipCommonOptionTagEntry 2 }
sipOptionTagHeaderField OBJECT-TYPE sipCommonOptionTagHeaderField OBJECT-TYPE
SYNTAX SipOptionTagHeaders SYNTAX SipTCOptionTagHeaders
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the SIP option tag is "This object indicates whether the SIP option tag is supported
supported (Supported header), unsupported (Unsupported (Supported header), unsupported (Unsupported header), required
header), required (Require or Proxy-Require header) by (Require or Proxy-Require header) by the SIP entity. A SIP
the SIP entity. option tag may be both supported and required."
A SIP option tag may be both supported and required." ::= { sipCommonOptionTagEntry 3 }
::= { sipOptionTagEntry 3 }
-- --
-- Supported SIP Methods -- Supported SIP Methods
-- --
sipMethodSupportedTable OBJECT-TYPE sipCommonMethodSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipMethodSupportedEntry SYNTAX SEQUENCE OF SipCommonMethodSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of methods supported "This table contains a list of methods supported by each SIP
by each SIP entity in this system. This MAY include, entity in this system (see the standard set of SIP methods in
but is not limited to, the standard set of SIP methods Section 7.1 of RFC 3261). Any additional methods that may be
discussed in Section 7.1 of RFC 3261. Any additional incorporated into the SIP protocol can be represented by this
methods that MAY be incorporated into the SIP protocol table without any requirement to update this MIB module.
can be represented by this table without any requirement
to update this MIB.
The table is informational in nature; conveying to the NMS The table is informational in nature; conveying to the NMS
capabilities of the managed system. capabilities of the managed system.
From a protocol point of view, the list of methods From a protocol point of view, the list of methods advertised
advertised by the SIP entity in the Allow header (Section by the SIP entity in the Allow header (Section 20.5 of RFC
20.5 of RFC 3261) MUST be consistent with the methods 3261) MUST be consistent with the methods reflected in this
reflected in this table." table."
::= { sipCommonCfgBase 4 } ::= { sipCommonCfgBase 4 }
sipCommonMethodSupportedEntry OBJECT-TYPE
sipMethodSupportedEntry OBJECT-TYPE SYNTAX SipCommonMethodSupportedEntry
SYNTAX SipMethodSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular method supported by the SIP entity. "A particular method supported by the SIP entity.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP entity
entity present in this system. applIndex is used to present in this system. applIndex is used to uniquely identify
uniquely identify these instances of SIP entities and these instances of SIP entities and correlate them through the
correlate them through the common framework of the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
NETWORK-SERVICES-MIB (RFC 2788). INDEX { applIndex, sipCommonMethodSupportedIndex }
::= { sipCommonMethodSupportedTable 1 }
The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot."
INDEX { applIndex, sipMethodSupportedIndex }
::= { sipMethodSupportedTable 1 }
SipMethodSupportedEntry ::= SipCommonMethodSupportedEntry ::= SEQUENCE {
SEQUENCE { sipCommonMethodSupportedIndex Unsigned32,
sipMethodSupportedIndex Unsigned32, sipCommonMethodSupportedName SipTCMethodName
sipMethodName SnmpAdminString
} }
sipMethodSupportedIndex OBJECT-TYPE sipCommonMethodSupportedIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row "This object uniquely identifies a conceptual row in the table
in the table and reflects an assigned number used and reflects an assigned number used to identifier a specific
to identifier a specific SIP method. SIP method.
This identifier is suitable for referencing the This identifier is suitable for referencing the associated
associated method throughout this and other MIBs method throughout this and other MIBs supported by this managed
supported by this managed system." system."
::= { sipMethodSupportedEntry 1 } ::= { sipCommonMethodSupportedEntry 1 }
sipMethodName OBJECT-TYPE sipCommonMethodSupportedName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SipTCMethodName
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the supported method's name. "This object reflects the supported method's name. The method
The method name MUST be all upper case name MUST be all upper case (e.g, 'INVITE')."
(e.g, 'INVITE')." ::= { sipCommonMethodSupportedEntry 2 }
::= { sipMethodSupportedEntry 2 }
-- --
-- SIP Timer Configuration -- SIP Timer Configuration
-- --
sipCommonCfgTimerTable OBJECT-TYPE sipCommonCfgTimerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgTimerEntry SYNTAX SEQUENCE OF SipCommonCfgTimerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains timer configuration objects "This table contains timer configuration objects applicable to
applicable to SIP user agent and SIP stateful Proxy SIP user agent and SIP stateful Proxy Server entities."
Server entities."
::= { sipCommonCfgTimer 1 } ::= { sipCommonCfgTimer 1 }
sipCommonCfgTimerEntry OBJECT-TYPE sipCommonCfgTimerEntry OBJECT-TYPE
SYNTAX SipCommonCfgTimerEntry SYNTAX SipCommonCfgTimerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of timer configuration. "A row of timer configuration.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP entity
entity present in this system. applIndex is used to present in this system. applIndex is used to uniquely identify
uniquely identify these instances of SIP entities and these instances of SIP entities and correlate them through the
correlate them through the common framework of the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
NETWORK-SERVICES-MIB (RFC 2788). objects in this table entry SHOULD be non-volatile and their
The objects in this table entry SHOULD be non-volatile value SHOULD be kept at reboot."
and their value SHOULD be kept at reboot."
INDEX { applIndex } INDEX { applIndex }
::= { sipCommonCfgTimerTable 1 } ::= { sipCommonCfgTimerTable 1 }
SipCommonCfgTimerEntry ::= SipCommonCfgTimerEntry ::= SEQUENCE {
SEQUENCE { sipCommonCfgTimerA Unsigned32,
sipCfgTimerA Unsigned32, sipCommonCfgTimerB Unsigned32,
sipCfgTimerB Unsigned32, sipCommonCfgTimerC Unsigned32,
sipCfgTimerC Unsigned32, sipCommonCfgTimerD Unsigned32,
sipCfgTimerD Unsigned32, sipCommonCfgTimerE Unsigned32,
sipCfgTimerE Unsigned32, sipCommonCfgTimerF Unsigned32,
sipCfgTimerF Unsigned32, sipCommonCfgTimerG Unsigned32,
sipCfgTimerG Unsigned32, sipCommonCfgTimerH Unsigned32,
sipCfgTimerH Unsigned32, sipCommonCfgTimerI Unsigned32,
sipCfgTimerI Unsigned32, sipCommonCfgTimerJ Unsigned32,
sipCfgTimerJ Unsigned32, sipCommonCfgTimerK Unsigned32,
sipCfgTimerK Unsigned32, sipCommonCfgTimerT1 Unsigned32,
sipCfgTimerT1 Unsigned32, sipCommonCfgTimerT2 Unsigned32,
sipCfgTimerT2 Unsigned32, sipCommonCfgTimerT4 Unsigned32
sipCfgTimerT4 Unsigned32
} }
sipCfgTimerA OBJECT-TYPE sipCommonCfgTimerA OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the initial value for the "This object reflects the initial value for the retransmit timer
retransmit timer for the INVITE method. The retransmit for the INVITE method. The retransmit timer doubles after each
timer doubles after each retransmission, ensuring an retransmission, ensuring an exponential backoff in network
exponential backoff in network traffic. This object traffic. This object represents the initial time a SIP entity
represents the initial time a SIP entity will wait to will wait to receive a provisional response to an INVITE before
receive a provisional response to an INVITE before
resending the INVITE request." resending the INVITE request."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.1.2" "RFC 3261, Section 17.1.1.2"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 1 } ::= { sipCommonCfgTimerEntry 1 }
sipCfgTimerB OBJECT-TYPE sipCommonCfgTimerB OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP entity will "This object reflects the maximum time a SIP entity will wait to
wait to receive a final response to an INVITE. The receive a final response to an INVITE. The timer is started
timer is started upon transmission of the initial INVITE upon transmission of the initial INVITE request."
request."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.1.2" "RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 2 } ::= { sipCommonCfgTimerEntry 2 }
sipCfgTimerC OBJECT-TYPE sipCommonCfgTimerC OBJECT-TYPE
SYNTAX Unsigned32 (180000..300000) SYNTAX Unsigned32 (180000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP Proxy Server "This object reflects the maximum time a SIP Proxy Server will
will wait to receive a provisional response to an wait to receive a provisional response to an INVITE. The Timer
INVITE. C MUST be set for each client transaction when an INVITE
The Timer C MUST be set for each client transaction when request is proxied."
an INVITE request is proxied."
REFERENCE REFERENCE
"RFC 3261, Section 16.6" "RFC 3261, Section 16.6"
DEFVAL { 180000 } DEFVAL { 180000 }
::= { sipCommonCfgTimerEntry 3 } ::= { sipCommonCfgTimerEntry 3 }
sipCfgTimerD OBJECT-TYPE sipCommonCfgTimerD OBJECT-TYPE
SYNTAX Unsigned32 (0..300000) SYNTAX Unsigned32 (0..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the amount of time that the server "This object reflects the amount of time that the server
transaction can remain in the 'Completed' state when transaction can remain in the 'Completed' state when unreliable
unreliable transports are used. The default value MUST transports are used. The default value MUST be equal or greater
be greater than 32000 for UDP transport and its value than 32000 for UDP transport and its value MUST be 0 for
MUST be 0 for TCP/SCTP transport." TCP/SCTP transport."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.1.2" "RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 4 } ::= { sipCommonCfgTimerEntry 4 }
sipCfgTimerE OBJECT-TYPE sipCommonCfgTimerE OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the initial value for the retransmit "This object reflects the initial value for the retransmit timer
timer for a non-INVITE method while in 'Trying State'. for a non-INVITE method while in 'Trying State'. The
The retransmit timer doubles after each retransmission retransmit timer doubles after each retransmission until it
until it reaches T2 to ensure an exponential backoff reaches T2 to ensure an exponential backoff in network traffic.
in network traffic. This object represents the initial This object represents the initial time a SIP entity will wait
time a SIP entity will wait to receive a provisional to receive a provisional response to the request before
response to the request before resending the non-INVITE resending the non-INVITE request."
request."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.2.2" "RFC 3261, Section 17.1.2.2"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 5 } ::= { sipCommonCfgTimerEntry 5 }
sipCfgTimerF OBJECT-TYPE sipCommonCfgTimerF OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP entity will "This object reflects the maximum time a SIP entity will wait to
wait to receive a final response to a non-INVITE request. receive a final response to a non-INVITE request. The timer is
The timer is started upon transmission of the started upon transmission of the initial request."
initial request."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.2.2" "RFC 3261, Section 17.1.2.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 6 } ::= { sipCommonCfgTimerEntry 6 }
sipCfgTimerG OBJECT-TYPE sipCommonCfgTimerG OBJECT-TYPE
SYNTAX Unsigned32 (0..1000) SYNTAX Unsigned32 (0..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the initial value for the "This object reflects the initial value for the retransmit timer
retransmit timer for final responses to INVITE requests. for final responses to INVITE requests. If timer G fires, the
response is passed to the transport layer once more for
If timer G fires, the response is passed to the retransmission, and timer G is set to fire in MIN(2*T1, T2)
transport layer once more for retransmission, and seconds. From then on, when timer G fires, the response is
timer G is set to fire in MIN(2*T1, T2) seconds. From passed to the transport again for transmission, and timer G is
then on, when timer G fires, the response is passed to reset with a value that doubles, unless that value exceeds T2,
the transport again for transmission, and timer G is in which case it is reset with the value of T2. The default
reset with a value that doubles, unless that value value MUST be T1 for UDP transport and its value MUST be 0 for
exceeds T2, in which case it is reset with the value of reliable transport like TCP/SCTP."
T2. The default value MUST be T1 for UDP transport and
its value MUST be 0 for reliable transport like
TCP/SCTP."
REFERENCE REFERENCE
"RFC 3261, Section 17.2.1" "RFC 3261, Section 17.2.1"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 7 } ::= { sipCommonCfgTimerEntry 7 }
sipCfgTimerH OBJECT-TYPE sipCommonCfgTimerH OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a server will wait "This object reflects the maximum time a server will wait to
to receive an ACK before it abandons retransmitting the receive an ACK before it abandons retransmitting the response.
response. The timer is started upon entering the The timer is started upon entering the 'Completed' state."
'Completed' state."
REFERENCE REFERENCE
"RFC 3261, Section 17.2.1" "RFC 3261, Section 17.2.1"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 8 } ::= { sipCommonCfgTimerEntry 8 }
sipCfgTimerI OBJECT-TYPE sipCommonCfgTimerI OBJECT-TYPE
SYNTAX Unsigned32 (0..10000) SYNTAX Unsigned32 (0..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP entity will "This object reflects the maximum time a SIP entity will wait to
wait to receive additional ACK message retransmissions. receive additional ACK message retransmissions.
The timer is started upon entering the 'Confirmed' state.
The default value MUST be T4 for UDP transport and its The timer is started upon entering the 'Confirmed' state. The
value MUST be 0 for reliable transport like TCP/SCTP." default value MUST be T4 for UDP transport and its value MUST
be 0 for reliable transport like TCP/SCTP."
REFERENCE REFERENCE
"RFC 3261, Section 17.2.1" "RFC 3261, Section 17.2.1"
DEFVAL { 5000 } DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 9 } ::= { sipCommonCfgTimerEntry 9 }
sipCfgTimerJ OBJECT-TYPE sipCommonCfgTimerJ OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP server will "This object reflects the maximum time a SIP server will wait to
wait to receive retransmissions of non-INVITE request. receive retransmissions of non-INVITE request. The timer is
The timer is started upon entering the 'Completed' state started upon entering the 'Completed' state for non-INVITE
for non-INVITE transactions. When timer J fires, the transactions. When timer J fires, the server MUST transition to
server MUST transition to the 'Terminated' state." the 'Terminated' state."
REFERENCE "RFC 3261, Section 17.2.2" REFERENCE
"RFC 3261, Section 17.2.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 10 } ::= { sipCommonCfgTimerEntry 10 }
sipCfgTimerK OBJECT-TYPE sipCommonCfgTimerK OBJECT-TYPE
SYNTAX Unsigned32 (0..10000) SYNTAX Unsigned32 (0..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum time a SIP client will "This object reflects the maximum time a SIP client will wait to
wait to receive retransmissions of responses to receive retransmissions of responses to non-INVITE requests.
non-INVITE requests. The timer is started upon entering the 'Completed' state for
The timer is started upon entering the 'Completed' state non-INVITE transactions. When timer K fires, the server MUST
for non-INVITE transactions. When timer K fires, the transition to the 'Terminated' state. The default value MUST
server MUST transition to the 'Terminated' state. be T4 for UDP transport and its value MUST be 0 for reliable
The default value MUST be T4 for UDP transport and its transport like TCP/SCTP."
value MUST be 0 for reliable transport like TCP/SCTP."
REFERENCE REFERENCE
"RFC 3261, Section 17.1.2.2" "RFC 3261, Section 17.1.2.2"
DEFVAL { 5000 } DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 11 } ::= { sipCommonCfgTimerEntry 11 }
sipCfgTimerT1 OBJECT-TYPE sipCommonCfgTimerT1 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 T1 timer for a SIP entity. T1 is an
is an estimate of the round-trip time (RTT) between the estimate of the round-trip time (RTT) between the client and
client and server transactions." server transactions."
REFERENCE REFERENCE
"RFC 3261, Section 17" "RFC 3261, Section 17"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 12 } ::= { sipCommonCfgTimerEntry 12 }
sipCfgTimerT2 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 T2 timer for a SIP entity. "This object reflects the T2 timer for a SIP entity. T2 is the
T2 is the maximum retransmit interval for non-INVITE maximum retransmit interval for non-INVITE requests and INVITE
requests and INVITE responses. It's used in various responses. It's used in various parts of the protocol to reset
parts of the protocol to reset other Timer* objects other Timer* objects to this value."
to this value."
REFERENCE REFERENCE
"RFC 3261, Section 17" "RFC 3261, Section 17"
DEFVAL { 4000 } DEFVAL { 4000 }
::= { sipCommonCfgTimerEntry 13 } ::= { sipCommonCfgTimerEntry 13 }
sipCfgTimerT4 OBJECT-TYPE 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 T4 timer for a SIP entity. "This object reflects the T4 timer for a SIP entity. T4 is the
T4 is the maximum duration a message will remain in maximum duration a message will remain in the network. It
the network. It represents the amount of time the represents the amount of time the network will take to clear
network will take to clear messages between client messages between client and server transactions. It's used in
and server transactions. It's used in various parts various parts of the protocol to reset other Timer* objects to
of the protocol to reset other Timer* objects to this this value."
value."
REFERENCE REFERENCE
"RFC 3261, Section 17" "RFC 3261, Section 17"
DEFVAL { 5000 } DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 14 } ::= { sipCommonCfgTimerEntry 14 }
-- --
-- Common Statistics Objects -- Common Statistics Objects
-- --
-- --
-- Summary Statistics -- Summary Statistics
-- --
sipSummaryStatsTable OBJECT-TYPE sipCommonSummaryStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipSummaryStatsEntry SYNTAX SEQUENCE OF SipCommonSummaryStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the summary statistics objects "This table contains the summary statistics objects applicable
applicable to all SIP entities. Each row represents to all SIP entities. Each row represents those objects for a
those objects for a particular SIP entity present in particular SIP entity present in this system."
this system." ::= { sipCommonSummaryStats 1 }
::= { sipCommonStatsSummary 1 }
sipSummaryStatsEntry OBJECT-TYPE sipCommonSummaryStatsEntry OBJECT-TYPE
SYNTAX SipSummaryStatsEntry SYNTAX SipCommonSummaryStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics. "A row of summary statistics.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP entity
entity present in this system. applIndex is used to present in this system. applIndex is used to uniquely identify
uniquely identify these instances of SIP entities and these instances of SIP entities and correlate them through the
correlate them through the common framework of the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipSummaryStatsTable 1 } ::= { sipCommonSummaryStatsTable 1 }
SipSummaryStatsEntry ::= SipCommonSummaryStatsEntry ::= SEQUENCE {
SEQUENCE { sipCommonSummaryInRequests Counter32,
sipSummaryInRequests Counter32, sipCommonSummaryOutRequests Counter32,
sipSummaryOutRequests Counter32, sipCommonSummaryInResponses Counter32,
sipSummaryInResponses Counter32, sipCommonSummaryOutResponses Counter32,
sipSummaryOutResponses Counter32, sipCommonSummaryTotalTransactions Counter32,
sipSummaryTotalTransactions Counter32 sipCommonSummaryDisconTime TimeStamp
} }
sipSummaryInRequests OBJECT-TYPE sipCommonSummaryInRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the total number of SIP request "This object indicates the total number of SIP request messages
messages received by the SIP entity including received by the SIP entity including retransmissions.
retransmissions."
::= { sipSummaryStatsEntry 1 }
sipSummaryOutRequests OBJECT-TYPE Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same
row."
::= { sipCommonSummaryStatsEntry 1 }
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
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same
row."
::= { sipCommonSummaryStatsEntry 2 }
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 received by the SIP entity including received by the SIP entity including retransmissions.
retransmissions."
::= { sipSummaryStatsEntry 3 }
sipSummaryOutResponses OBJECT-TYPE Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same
row."
::= { sipCommonSummaryStatsEntry 3 }
sipCommonSummaryOutResponses 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 sent (originated and relayed) by the SIP entity including
including retransmissions." retransmissions.
::= { sipSummaryStatsEntry 4 }
sipSummaryTotalTransactions OBJECT-TYPE Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same
row."
::= { sipCommonSummaryStatsEntry 4 }
sipCommonSummaryTotalTransactions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of "This object contains a count of the number of transactions that
transactions that are in progress and transactions that are in progress and transactions that have reached the
have reached the terminated state. It is not applicable terminated state. It is not applicable to stateless SIP Proxy
to stateless SIP Proxy Servers. Servers.
A SIP transaction occurs between a client and a server A SIP transaction occurs between a client and a server and
and comprises all messages from the first request sent comprises all messages from the first request sent from the
from the client to the server up to a final (non-1xx) client to the server up to a final (non-1xx) response sent from
response sent from the server to the client. the server to the client.
If the request is INVITE and the final response is a If the request is INVITE and the final response is a non-2xx,
non-2xx, the transaction also include an ACK to the the transaction also include an ACK to the response. The ACK
response. The ACK for a 2xx response to an INVITE for a 2xx response to an INVITE request is a separate
request is a separate transaction. transaction.
The branch ID parameter in the Via header field values The branch ID parameter in the Via header field values serves
serves as a transaction identifier. as a transaction identifier.
A transaction is identified by the CSeq sequence number A transaction is identified by the CSeq sequence number within
within a single call leg. The ACK request has the same a single call leg. The ACK request has the same CSeq number as
CSeq number as the corresponding INVITE request, but the corresponding INVITE request, but comprises a transaction
comprises a transaction of its own. of its own.
In the case of a forked request, each branch counts as a In the case of a forked request, each branch counts as a single
single transaction. transaction.
For a transaction stateless Proxy Server, this counter For a transaction stateless Proxy Server, this counter is
is always 0." always 0.
::= { sipSummaryStatsEntry 5 }
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same
row."
::= { sipCommonSummaryStatsEntry 5 }
sipCommonSummaryDisconTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the sysUpTime object when the counters for the
summary statistics objects in this row last experienced a
discontinuity."
::= { sipCommonSummaryStatsEntry 6 }
-- --
-- SIP Method Statistics -- SIP Method Statistics
-- Total counts for each SIP method. -- Total counts for each SIP method.
-- --
sipMethodStatsTable OBJECT-TYPE sipCommonMethodStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipMethodStatsEntry SYNTAX SEQUENCE OF SipCommonMethodStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the method statistics objects "This table contains the method statistics objects for SIP
for SIP entities. Each row represents those objects entities. Each row represents those objects for a particular
for a particular SIP entity present in this system." SIP entity present in this system."
::= { sipCommonStatsMethod 1 } ::= { sipCommonMethodStats 1 }
sipMethodStatsEntry OBJECT-TYPE sipCommonMethodStatsEntry OBJECT-TYPE
SYNTAX SipMethodStatsEntry SYNTAX SipCommonMethodStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of per entity method statistics. "A row of per entity method statistics.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP entity
entity present in this system. applIndex is used to present in this system. applIndex is used to uniquely identify
uniquely identify these instances of SIP entities and these instances of SIP entities and correlate them through the
correlate them through the common framework of the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
NETWORK-SERVICES-MIB (RFC 2788)." INDEX { applIndex, sipCommonMethodStatsName }
INDEX { applIndex, sipStatsMethod } ::= { sipCommonMethodStatsTable 1 }
::= { sipMethodStatsTable 1 }
SipCommonMethodStatsEntry ::= SEQUENCE {
sipCommonMethodStatsName SipTCMethodName,
sipCommonMethodStatsOutbounds Counter32,
sipCommonMethodStatsInbounds Counter32,
sipCommonMethodStatsDisconTime TimeStamp
SipMethodStatsEntry ::=
SEQUENCE {
sipStatsMethod SipMethodName,
sipStatsOutbounds Counter32,
sipStatsInbounds Counter32
} }
sipStatsMethod 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 the SIP method "This object uniquely identifies the SIP method related to the
related to the objects in a particular row." objects in a particular row."
::= { sipMethodStatsEntry 1 } ::= { sipCommonMethodStatsEntry 1 }
sipStatsOutbounds OBJECT-TYPE sipCommonMethodStatsOutbounds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of requests "This object reflects the total number of requests sent by the
sent by the SIP entity, excluding retransmissions. SIP entity, excluding retransmissions. Retransmissions are
Retransmissions are counted separately and are not counted separately and are not reflected in this counter. A
reflected in this counter." Management Station can detect discontinuities in this counter
by monitoring the sipCommonMethodStatsDisconTime object in the
same row."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 2 } ::= { sipCommonMethodStatsEntry 2 }
sipCommonMethodStatsInbounds OBJECT-TYPE
sipStatsInbounds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of requests "This object reflects the total number of requests received by
received by the SIP entity. Retransmissions are the SIP entity. Retransmissions are counted separately and are
counted separately and are not reflected in this not reflected in this counter. A Management Station can detect
counter." discontinuities in this counter by monitoring the
sipCommonMethodStatsDisconTime object in the same row."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 3 } ::= { sipCommonMethodStatsEntry 3 }
sipCommonMethodStatsDisconTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the sysUpTime object when the counters for the
method statistics objects in this row last experienced a
discontinuity."
::= { sipCommonMethodStatsEntry 4 }
-- --
-- Support for specific status codes -- Support for specific status codes
-- --
sipStatusCodesTable OBJECT-TYPE sipCommonStatusCodeTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatusCodesEntry SYNTAX SEQUENCE OF SipCommonStatusCodeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the list of SIP status codes which "This table contains the list of SIP status codes which each SIP
each SIP entity in this system has been requested to entity in this system has been requested to monitor. It is the
monitor. It is the mechanism by which specific status mechanism by which specific status codes are monitored.
codes are monitored." Entries created in this table must not persist across reboots"
::= { sipCommonStatusCode 2 } ::= { sipCommonStatusCode 1 }
sipStatusCodesEntry OBJECT-TYPE sipCommonStatusCodeEntry OBJECT-TYPE
SYNTAX SipStatusCodesEntry SYNTAX SipCommonStatusCodeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information on a particular SIP status "This row contains information on a particular SIP status code
code that the SIP entity has been requested to monitor. that the SIP entity has been requested to monitor. Entries
created in this table must not persist across reboots.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP entity
entity present in this system. applIndex is used to present in this system. applIndex is used to uniquely identify
uniquely identify these instances of SIP entities and these instances of SIP entities and correlate them through the
correlate them through the common framework of the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
NETWORK-SERVICES-MIB (RFC 2788)." INDEX { applIndex, sipCommonStatusCodeMethod,
INDEX { applIndex, sipStatusCodeMethod, sipStatusCodeValue } sipCommonStatusCodeValue }
::= { sipStatusCodesTable 1 } ::= { sipCommonStatusCodeTable 1 }
SipStatusCodesEntry ::= SipCommonStatusCodeEntry ::= SEQUENCE {
SEQUENCE { sipCommonStatusCodeMethod SipTCMethodName,
sipStatusCodeMethod SipMethodName, sipCommonStatusCodeValue Unsigned32,
sipStatusCodeValue Unsigned32, sipCommonStatusCodeIns Counter32,
sipStatusCodeIns Counter32, sipCommonStatusCodeOuts Counter32,
sipStatusCodeOuts Counter32, sipCommonStatusCodeRowStatus RowStatus,
sipStatusCodeRowStatus RowStatus sipCommonStatusCodeDisconTime TimeStamp
} }
sipStatusCodeMethod OBJECT-TYPE sipCommonStatusCodeMethod 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 a conceptual row in the table
in the table and reflects an assigned number used and reflects an assigned number used to identify a specific SIP
to identifier a specific SIP method." method."
::= { sipStatusCodesEntry 1 } ::= { sipCommonStatusCodeEntry 1 }
sipStatusCodeValue OBJECT-TYPE sipCommonStatusCodeValue OBJECT-TYPE
SYNTAX Unsigned32 (100..999) SYNTAX Unsigned32 (100..999)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a SIP status code value that the "This object contains a SIP status code value that the SIP
SIP entity has been requested to monitor. All of the entity has been requested to monitor. All of the other
other information in the row is related to this value." information in the row is related to this value."
::= { sipStatusCodesEntry 2 } ::= { sipCommonStatusCodeEntry 2 }
sipStatusCodeIns OBJECT-TYPE sipCommonStatusCodeIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of response "This object reflects the total number of response messages
messages received by the SIP entity with the status code received by the SIP entity with the status code value contained
value contained in the sipStatusCodeValue column." in the sipCommonStatusCodeValue column.
::= { sipStatusCodesEntry 3 }
sipStatusCodeOuts OBJECT-TYPE Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service, or when the
monitoring of the Status code is temporarily disabled. A
Management Station can detect discontinuities in this counter
by monitoring the sipCommonStatusCodeDisconTime object in the
same row."
::= { sipCommonStatusCodeEntry 3 }
sipCommonStatusCodeOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of response "This object reflects the total number of response messages sent
messages sent by the SIP entity with the status code by the SIP entity with the status code value contained in the
value contained in the sipStatusCodeValue column." sipCommonStatusCodeValue column.
::= { sipStatusCodesEntry 4 }
sipStatusCodeRowStatus OBJECT-TYPE Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service, or when the
monitoring of the Status code is temporarily disabled. A
Management Station can detect discontinuities in this counter
by monitoring the sipCommonStatusCodeDisconTime object in the
same row."
::= { sipCommonStatusCodeEntry 4 }
sipCommonStatusCodeRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row augmentation in sipStatusCodeNotifTable "The row augmentation in sipCommonStatusCodeNotifTable will be
will be governed by the value of this RowStatus. governed by the value of this RowStatus.
This object is REQUIRED to create or delete rows The values 'createAndGo' and 'destroy' are the only valid
by a manager. values allowed for this object. If a row exists, it will
reflect a status of 'active' when queried."
::= { sipCommonStatusCodeEntry 5 }
The values 'createAndGo' and 'destroy' are the sipCommonStatusCodeDisconTime OBJECT-TYPE
only valid values allowed for this object. SYNTAX TimeStamp
If a row exists, it will reflect a status of MAX-ACCESS read-only
'active' when queried." STATUS current
::= { sipStatusCodesEntry 5 } 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 }
-- --
-- support for specific status code notifications -- Support for specific status code notifications
-- --
sipStatusCodeNotifTable OBJECT-TYPE sipCommonStatusCodeNotifTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatusCodeNotifEntry SYNTAX SEQUENCE OF SipCommonStatusCodeNotifEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains objects to control notifications "This table contains objects to control notifications related to
related to particular status codes each SIP entity in particular status codes each SIP entity in this system has been
this system has been requested to monitor. requested to monitor.
There is an entry in this table corresponding to each There is an entry in this table corresponding to each entry in
entry in sipStatusCodesTable. Therefore, this sipCommonStatusCodeTable. Therefore, this table augments that
table augments that table and utilizes the same index table and utilizes the same index methodology.
methodology.
The objects in this table are not included directly The objects in this table are not included directly in the
in the sipStatusCodesTable simply to keep the sipCommonStatusCodeTable simply to keep the status code
status code notification control objects separate from notification control objects separate from the actual status
the actual status code statistics." code statistics."
::= { sipCommonStatusCode 3 } ::= { sipCommonStatusCode 2 }
sipStatusCodeNotifEntry OBJECT-TYPE sipCommonStatusCodeNotifEntry OBJECT-TYPE
SYNTAX SipStatusCodeNotifEntry SYNTAX SipCommonStatusCodeNotifEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information controlling notifications "This row contains information controlling notifications for a
for a particular SIP status code that the SIP entity has particular SIP status code that the SIP entity has been
been requested to monitor." requested to monitor."
AUGMENTS { sipStatusCodesEntry } AUGMENTS { sipCommonStatusCodeEntry }
::= { sipStatusCodeNotifTable 1 } ::= { sipCommonStatusCodeNotifTable 1 }
SipStatusCodeNotifEntry ::= SipCommonStatusCodeNotifEntry ::= SEQUENCE {
SEQUENCE { sipCommonStatusCodeNotifSend TruthValue,
sipStatusCodeNotifSend TruthValue, sipCommonStatusCodeNotifEmitMode INTEGER,
sipStatusCodeNotifEmitMode INTEGER, sipCommonStatusCodeNotifThresh Unsigned32,
sipStatusCodeNotifThresh Unsigned32, sipCommonStatusCodeNotifInterval Unsigned32
sipStatusCodeNotifInterval Unsigned32
} }
sipStatusCodeNotifSend OBJECT-TYPE sipCommonStatusCodeNotifSend OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls whether a sipStatusCodeNotif "This object controls whether a sipCommonStatusCodeNotif is
is emitted when the status code value specified in emitted when the status code value specified in by
by sipStatusCodeValue is sent or received. sipCommonStatusCodeValue is sent or received. If the value of
If the value of this object is 'true', then a this object is 'true', then a notification is sent. If it is
notification is sent. If it is 'false', no notification 'false', no notification is sent.
is sent.
Note well, that a notification MAY be emitted for Note well, that a notification MAY be emitted for every message
every message sent or received that contains the sent or received that contains the particular status code.
particular status code. Depending on the status code Depending on the status code involved, this can cause a
involved, this can cause a significant number of significant number of notification emissions that could be
notification emissions that could be detrimental to detrimental to network performance. Managers are forewarned to
network performance. be prudent in the use of this object to enable notifications.
Managers are forewarned to be prudent in the use of Look to sipCommonStatusCodeNotifEmitMode for alternative
this object to enable notifications. Look to controls for sipCommonStatusCodeNotif emissions."
sipStatusCodeNotifEmitMode for alternative
controls for sipStatusCodeNotif emissions."
DEFVAL { false } DEFVAL { false }
::= { sipStatusCodeNotifEntry 1 } ::= { sipCommonStatusCodeNotifEntry 1 }
sipStatusCodeNotifEmitMode OBJECT-TYPE sipCommonStatusCodeNotifEmitMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
normal(1), normal(1),
oneShot(2), oneShot(2),
triggered(3) -- read-only triggered(3) -- read-only
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object sipStatusCodeNotifSend MUST be set "The object sipCommonStatusCodeNotifSend MUST be set to 'true'
to 'true' for the values of this object to have any for the values of this object to have any effect. It is
effect. It is RECOMMENDED that the desired emit mode RECOMMENDED that the desired emit mode be established by this
be established by this object prior to setting object prior to setting sipCommonStatusCodeNotifSend to 'true'.
sipStatusCodeNotifSend to 'true'. This object and This object and the sipCommonStatusCodeNotifSend object can
the sipStatusCodeNotifSend object can obviously be obviously be set independently, but their respective values
set independently, but their respective values will will have a dependency on each other and the resulting
have a dependency on each other and the resulting
notifications. notifications.
This object specifies the mode for emissions of This object specifies the mode for emissions of
sipStatusCodeNotif notifications. sipCommonStatusCodeNotif notifications.
normal : sipStatusCodeNotif notifications will
be emitted by the system for each
SIP response messages sent or received
that contains the desired status code.
oneShot : Only one sipStatusCodeNotif notification normal : sipCommonStatusCodeNotif notifications will be
will be emitted. It will be the next emitted by the system for each SIP response
SIP response messages sent or received messages sent or received that contains the
that contains the desired status code. desired status code.
No more notifications are emitted until this oneShot : Only one sipCommonStatusCodeNotif notification
object is set to either 'oneShot' again will be emitted. It will be the next SIP response
or 'normal'. This option is provided messages sent or received that contains the
as a means of quelling the potential desired status code.
promiscuous behavior that can be associated
with the sipStatusCodeNotif.
triggered : This value is only readable and cannot be No more notifications are emitted until this object
set. It reflects the default value of the is set to either 'oneShot' again or 'normal'. This
object or that the 'oneShot' case has option is provided as a means of quelling the
occurred and indicates the mode needs to potential promiscuous behavior that can be
be reset to get further notifications. associated with the sipCommonStatusCodeNotif.
The mode is reset by setting this object triggered : This value is only readable and cannot be set. It
to 'oneShot' or 'normal'." reflects the default value of the object or that
DEFVAL { triggered } the 'oneShot' case has occurred and indicates the
::= { sipStatusCodeNotifEntry 2 } mode needs to be reset to get further
notifications. The mode is reset by setting this
object to 'oneShot' or 'normal'."
DEFVAL { oneShot }
::= { sipCommonStatusCodeNotifEntry 2 }
sipStatusCodeNotifThresh OBJECT-TYPE sipCommonStatusCodeNotifThresh OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the number of response messages "This object specifies the number of response messages sent or
sent or received by this system that are considered received by this system that are considered excessive. Based
excessive. Based on crossing that threshold, a on crossing that threshold, a
sipStatusCodeThreshExceededInNotif notification or a sipCommonStatusCodeThreshExceededInNotif notification or a
sipStatusCodeThreshExceededOutNotif will be sent. sipCommonStatusCodeThreshExceededOutNotif will be sent. The
The sipStatusCodeThreshExceededInNotif and sipCommonStatusCodeThreshExceededInNotif and
sipStatusCodeThreshExceededOutNotif notifications can sipCommonStatusCodeThreshExceededOutNotif notifications can be
be used as an early warning mechanism in lieu of used as an early warning mechanism in lieu of using
using sipStatusCodeNotif. sipCommonStatusCodeNotif.
Note that the configuration applied by this object Note that the configuration applied by this object will be
will be applied equally to inbound and outbound applied equally to inbound and outbound response messages."
response messages."
DEFVAL { 500 } DEFVAL { 500 }
::= { sipStatusCodeNotifEntry 3 } ::= { sipCommonStatusCodeNotifEntry 3 }
sipStatusCodeNotifInterval OBJECT-TYPE sipCommonStatusCodeNotifInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the time interval over which "This object specifies the time interval over which if
if sipCommonStatusCodeThresh is exceeded, with sipCommonStatusCodeThresh is exceeded, with respect to sent or
respect to sent or received messages, a received messages, a sipCommonStatusCodeThreshExceededInNotif
sipStatusCodeThreshExceededInNotif or or sipCommonStatusCodeThreshExceededOutNotif notification will
sipStatusCodeThreshExceededOutNotif notification will
be sent. be sent.
Note that the configuration applied by this object Note that the configuration applied by this object will be
will be applied equally to inbound and outbound applied equally to inbound and outbound response messages."
response messages."
DEFVAL { 60 } DEFVAL { 60 }
::= { sipStatusCodeNotifEntry 4 } ::= { sipCommonStatusCodeNotifEntry 4 }
-- --
-- Transaction Statistics -- Transaction Statistics
-- --
sipCurrentTransTable OBJECT-TYPE sipCommonTransCurrentTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCurrentTransEntry SYNTAX SEQUENCE OF SipCommonTransCurrentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on the transactions "This table contains information on the transactions currently
currently awaiting definitive responses by each SIP awaiting definitive responses by each SIP entity in this
entity in this system. system.
This table does not apply to transaction stateless This table does not apply to transaction stateless Proxy
Proxy Servers." Servers."
::= { sipCommonStatsTrans 1 } ::= { sipCommonStatsTrans 1 }
sipCurrentTransEntry OBJECT-TYPE sipCommonTransCurrentEntry OBJECT-TYPE
SYNTAX SipCurrentTransEntry SYNTAX SipCommonTransCurrentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular SIP entity's current "Information on a particular SIP entity's current transactions.
transactions.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP entity
entity present in this system. applIndex is used to present in this system. applIndex is used to uniquely identify
uniquely identify these instances of SIP entities and these instances of SIP entities and correlate them through the
correlate them through the common framework of the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipCurrentTransTable 1 } ::= { sipCommonTransCurrentTable 1 }
SipCurrentTransEntry ::= SipCommonTransCurrentEntry ::= SEQUENCE {
SEQUENCE { sipCommonTransCurrentactions Gauge32
sipCurrentTransactions Gauge32
} }
sipCurrentTransactions OBJECT-TYPE sipCommonTransCurrentactions OBJECT-TYPE
SYNTAX Gauge32 (0..4294967295) SYNTAX Gauge32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the number of transactions awaiting "This object contains the number of transactions awaiting
definitive (non-1xx) response. In the case of a forked definitive (non-1xx) response. In the case of a forked
request, each branch counts as a single transaction request, each branch counts as a single transaction
corresponding to the entity identified by applIndex." corresponding to the entity identified by applIndex."
::= { sipCurrentTransEntry 1 } ::= { sipCommonTransCurrentEntry 1 }
-- --
-- SIP Retry Statistics -- SIP Retry Statistics
-- --
-- This group contains various statistic objects about -- This group contains various statistic objects about
-- retransmission counts. -- retransmission counts.
-- --
sipCommonStatsRetryTable OBJECT-TYPE sipCommonStatsRetryTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonStatsRetryEntry SYNTAX SEQUENCE OF SipCommonStatsRetryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains retry statistics objects applicable "This table contains retry statistics objects applicable to each
to each SIP entity in this system." SIP entity in this system."
::= { sipCommonStatsRetry 1 } ::= { sipCommonStatsRetry 1 }
sipCommonStatsRetryEntry OBJECT-TYPE sipCommonStatsRetryEntry OBJECT-TYPE
SYNTAX SipCommonStatsRetryEntry SYNTAX SipCommonStatsRetryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of retry statistics. "A row of retry statistics.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP entity
entity present in this system. applIndex is used to present in this system. applIndex is used to uniquely identify
uniquely identify these instances of SIP entities and these instances of SIP entities and correlate them through the
correlate them through the common framework of the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
NETWORK-SERVICES-MIB (RFC 2788)." INDEX { applIndex, sipCommonStatsRetryMethod }
INDEX { applIndex, sipStatsRetryMethod }
::= { sipCommonStatsRetryTable 1 } ::= { sipCommonStatsRetryTable 1 }
SipCommonStatsRetryEntry ::= SipCommonStatsRetryEntry ::= SEQUENCE {
SEQUENCE { sipCommonStatsRetryMethod SipTCMethodName,
sipStatsRetryMethod SipMethodName, sipCommonStatsRetries Counter32,
sipStatsRetries Counter32, sipCommonStatsRetryFinalResponses Counter32,
sipStatsRetryFinalResponses Counter32, sipCommonStatsRetryNonFinalResponses Counter32,
sipStatsRetryNonFinalResponses Counter32 sipCommonStatsRetryDisconTime TimeStamp
} }
sipStatsRetryMethod OBJECT-TYPE sipCommonStatsRetryMethod OBJECT-TYPE
SYNTAX SipMethodName SYNTAX SipTCMethodName
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies the SIP method "This object uniquely identifies the SIP method related to the
related to the objects in a row." objects in a row."
::= { sipCommonStatsRetryEntry 1 } ::= { sipCommonStatsRetryEntry 1 }
sipStatsRetries OBJECT-TYPE sipCommonStatsRetries 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 request "This object reflects the total number of request
retransmissions that have been sent by the SIP retransmissions that have been sent by the SIP entity. Note
entity. Note that there could be multiple that there could be multiple retransmissions per request.
retransmissions per request."
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonStatsRetryDisconTime object in the same
row."
::= { sipCommonStatsRetryEntry 2 } ::= { sipCommonStatsRetryEntry 2 }
sipStatsRetryFinalResponses OBJECT-TYPE sipCommonStatsRetryFinalResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of Final Response "This object reflects the total number of Final Response retries
retries that have been sent by the SIP entity. that have been sent by the SIP entity. Note that there could
Note that there could be multiple retransmissions be multiple retransmissions per request.
per request."
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonStatsRetryDisconTime object in the same
row."
::= { sipCommonStatsRetryEntry 3 } ::= { sipCommonStatsRetryEntry 3 }
sipStatsRetryNonFinalResponses OBJECT-TYPE sipCommonStatsRetryNonFinalResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of non-Final "This object reflects the total number of non-Final RResponse
Response retries that have been sent by the SIP entity." retries that have been sent by the SIP entity.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonStatsRetryDisconTime object in the same
row."
::= { sipCommonStatsRetryEntry 4 } ::= { sipCommonStatsRetryEntry 4 }
sipCommonStatsRetryDisconTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the sysUpTime object when the counters for the
retry statistics objects in this row last experienced a
discontinuity."
::= { sipCommonStatsRetryEntry 5 }
-- --
-- Other Common Statistics -- Other Common Statistics
-- --
sipOtherStatsTable OBJECT-TYPE sipCommonOtherStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipOtherStatsEntry SYNTAX SEQUENCE OF SipCommonOtherStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains other common statistics supported by "This table contains other common statistics supported by each
each SIP entity in this system." SIP entity in this system."
::= { sipCommonStatsOther 1 } ::= { sipCommonOtherStats 1 }
sipOtherStatsEntry OBJECT-TYPE sipCommonOtherStatsEntry OBJECT-TYPE
SYNTAX SipOtherStatsEntry SYNTAX SipCommonOtherStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular SIP entity's other common "Information on a particular SIP entity's other common
statistics. statistics.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP entity
entity present in this system. applIndex is used to present in this system. applIndex is used to uniquely identify
uniquely identify these instances of SIP entities and these instances of SIP entities and correlate them through the
correlate them through the common framework of the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipOtherStatsTable 1 } ::= { sipCommonOtherStatsTable 1 }
SipOtherStatsEntry ::= SipCommonOtherStatsEntry ::= SEQUENCE {
SEQUENCE { sipCommonOtherStatsNumUnsupportedUris Counter32,
sipNumUnsupportedUris Counter32, sipCommonOtherStatsNumUnsupportedMethods Counter32,
sipNumUnsupportedMethods Counter32, sipCommonOtherStatsOtherwiseDiscardedMsgs Counter32,
sipOtherwiseDiscardedMsgs Counter32 sipCommonOtherStatsDisconTime TimeStamp
} }
sipNumUnsupportedUris OBJECT-TYPE sipCommonOtherStatsNumUnsupportedUris OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of RequestURIs received with unsupported scheme. "Number of RequestURIs received with unsupported scheme. A
A server normally responds to such requests with a 400 server normally responds to such requests with a 400 Bad
Bad Request status code." Request status code.
::= { sipOtherStatsEntry 1 }
sipNumUnsupportedMethods OBJECT-TYPE Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonOtherStatsDisconTime object in the same
row."
::= { sipCommonOtherStatsEntry 1 }
sipCommonOtherStatsNumUnsupportedMethods OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of SIP requests received with unsupported "Number of SIP requests received with unsupported methods. A
methods. server normally responds to such requests with a 501 (Not
A server normally responds to such requests with a Implemented) or 405 (Method Not Allowed).
501 (Not Implemented) or 405 (Method Not Allowed)."
::= { sipOtherStatsEntry 2 }
sipOtherwiseDiscardedMsgs OBJECT-TYPE Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonOtherStatsDisconTime object in the same
row."
::= { sipCommonOtherStatsEntry 2 }
sipCommonOtherStatsOtherwiseDiscardedMsgs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of SIP messages received that for any number "Number of SIP messages received that for any number of reasons
of reasons was discarded without a response." was discarded without a response.
::= { sipOtherStatsEntry 3 }
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonOtherStatsDisconTime object in the same
row."
::= { sipCommonOtherStatsEntry 3 }
sipCommonOtherStatsDisconTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the sysUpTime object when the counters for the
statistics objects in this row last experienced a
discontinuity."
::= { sipCommonOtherStatsEntry 4 }
-- --
-- Notification related objects -- Notification related objects
-- --
-- --
-- Status code related notification objects. -- Status code related notification objects.
-- --
sipStatusCodeNotifTo OBJECT-TYPE sipCommonStatusCodeNotifTo OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the To header in the "This object contains the value of the To header in the message
message containing the status code that caused the containing the status code that caused the notification. The
notification. The header name will be part of header name will be part of this object value. For example,
this object value. 'To: Watson '."
For example, 'To: Watson '."
::= { sipCommonNotifObjects 1 } ::= { sipCommonNotifObjects 1 }
sipStatusCodeNotifFrom OBJECT-TYPE sipCommonStatusCodeNotifFrom OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the From header in the "This object contains the value of the From header in the
message containing the status code that caused the message containing the status code that caused the
notification. The header name will be part of notification. The header name will be part of this object
this object value. value. For example, 'From: Watson '."
For example, 'From: Watson '."
::= { sipCommonNotifObjects 2 } ::= { sipCommonNotifObjects 2 }
sipStatusCodeNotifCallId OBJECT-TYPE sipCommonStatusCodeNotifCallId OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the CallId in the "This object contains the value of the Call-ID in the message
message containing the status code that caused the containing the status code that caused the notification. The
notification. The header name will be part of header name will be part of this object value. For example,
this object value. 'Call-ID: 5551212@example.com'."
For example, 'Call-ID: 5551212@example.com'."
::= { sipCommonNotifObjects 3 } ::= { sipCommonNotifObjects 3 }
sipStatusCodeNotifCSeq OBJECT-TYPE sipCommonStatusCodeNotifCSeq OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the CSeq value in the message "This object contains the CSeq value in the message containing
containing the status code that caused the notification. the status code that caused the notification. The header name
The header name will be part of this object value. will be part of this object value. For example, 'CSeq: 1722
For example, 'CSeq: 1722 INVITE'." INVITE'."
::= { sipCommonNotifObjects 4 } ::= { sipCommonNotifObjects 4 }
-- --
-- General notification related objects. -- General notification related objects.
-- --
sipNotifApplIndex OBJECT-TYPE sipCommonNotifApplIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the applIndex as described "This object contains the applIndex as described in RFC 2788.
in RFC 2788. This object is created in order to This object is created in order to allow a variable binding
allow a variable binding containing a value of containing a value of applIndex in a notification."
applIndex in a notification."
::= { sipCommonNotifObjects 5 } ::= { sipCommonNotifObjects 5 }
sipNotifSequenceNumber OBJECT-TYPE sipCommonNotifSequenceNumber OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a sequence number for each "This object contains a sequence number for each notification
notification generated by this SIP entity. Each generated by this SIP entity. Each notification SHOULD have a
notification SHOULD have a unique sequence number. unique sequence number. A network manager can use this
A network manager can use this information to information to determine whether notifications from a
determine whether notifications from a particular particular SIP entity have been missed. The value of this
SIP entity have been missed. The value of this object MUST start at 1 and increase by one with each generated
object MUST start at 1 and increase by one with notification. If a system restarts, the sequence number MAY
each generated notification. If a system restarts, start again from 1."
the sequence number MAY start again from 1."
::= { sipCommonNotifObjects 6 } ::= { sipCommonNotifObjects 6 }
-- --
-- Notifications -- Notifications
-- --
sipStatusCodeNotif NOTIFICATION-TYPE sipCommonStatusCodeNotif NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifSequenceNumber, sipCommonNotifSequenceNumber,
sipNotifApplIndex, sipCommonNotifApplIndex,
sipStatusCodeNotifTo, sipCommonStatusCodeNotifTo,
sipStatusCodeNotifFrom, sipCommonStatusCodeNotifFrom,
sipStatusCodeNotifCallId, sipCommonStatusCodeNotifCallId,
sipStatusCodeNotifCSeq, sipCommonStatusCodeNotifCSeq,
sipStatusCodeIns, sipCommonStatusCodeIns,
sipStatusCodeOuts sipCommonStatusCodeOuts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that a specific status code has been sent "Signifies that a specific status code has been sent or received
or received by the system." by the system."
::= { sipCommonMIBNotifs 1 } ::= { sipCommonMIBNotifications 1 }
sipStatusCodeThreshExceededInNotif NOTIFICATION-TYPE sipCommonStatusCodeThreshExceededInNotif NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifSequenceNumber, sipCommonNotifSequenceNumber,
sipNotifApplIndex, sipCommonNotifApplIndex,
sipStatusCodeIns sipCommonStatusCodeIns
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that a specific status code was found to "Signifies that a specific status code was found to have been
have been received by the system enough to received by the system enough to exceed the configured
exceed the configured threshold. This notification threshold. This notification can be used as an early warning
can be used as an early warning mechanism in lieu mechanism in lieu of using sipCommonStatusCodeNotif."
of using sipStatusCodeNotif." ::= { sipCommonMIBNotifications 2 }
::= { sipCommonMIBNotifs 2 }
sipStatusCodeThreshExceededOutNotif NOTIFICATION-TYPE sipCommonStatusCodeThreshExceededOutNotif NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifSequenceNumber, sipCommonNotifSequenceNumber,
sipNotifApplIndex, sipCommonNotifApplIndex,
sipStatusCodeOuts sipCommonStatusCodeOuts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that a specific status code was found to "Signifies that a specific status code was found to have been
have been sent by the system enough to sent by the system enough to exceed the configured threshold.
exceed the configured threshold. This notification This notification can be used as an early warning mechanism in
can be used as an early warning mechanism in lieu lieu of using sipCommonStatusCodeNotif."
of using sipStatusCodeNotif." ::= { sipCommonMIBNotifications 3 }
::= { sipCommonMIBNotifs 3 }
sipServiceColdStart NOTIFICATION-TYPE sipCommonServiceColdStart NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifSequenceNumber, sipCommonNotifSequenceNumber,
sipNotifApplIndex, sipCommonNotifApplIndex,
sipServiceStartTime sipCommonCfgServiceStartTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that the SIP service has reinitialized "Signifies that the SIP service has reinitialized itself or
itself or started for the first time. This SHOULD started for the first time. This SHOULD result from a hard
result from a hard 'down' to 'up' administrative 'down' to 'up' administrative status change. The configuration
status change. or behavior of the service MAY be altered."
The configuration or behavior of the service ::= { sipCommonMIBNotifications 4 }
MAY be altered."
::= { sipCommonMIBNotifs 4 }
sipServiceWarmStart NOTIFICATION-TYPE sipCommonServiceWarmStart NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifSequenceNumber, sipCommonNotifSequenceNumber,
sipNotifApplIndex, sipCommonNotifApplIndex,
sipServiceLastChange sipCommonCfgServiceLastChange
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that the SIP service has reinitialized "Signifies that the SIP service has reinitialized itself and is
itself and is restarting after an administrative restarting after an administrative 'reset'. The configuration
'reset'. The configuration or behavior of the service or behavior of the service MAY be altered."
MAY be altered." ::= { sipCommonMIBNotifications 5 }
::= { sipCommonMIBNotifs 5 }
sipServiceStatusChanged NOTIFICATION-TYPE sipCommonServiceStatusChanged NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifSequenceNumber, sipCommonNotifSequenceNumber,
sipNotifApplIndex, sipCommonNotifApplIndex,
sipServiceLastChange, sipCommonCfgServiceLastChange,
sipServiceOperStatus sipCommonCfgServiceOperStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that the SIP service operational status "Signifies that the SIP service operational status has changed."
has changed." ::= { sipCommonMIBNotifications 6 }
::= { sipCommonMIBNotifs 6 }
-- --
-- Conformance -- Conformance
-- --
sipCommonMIBCompliances sipCommonMIBCompliances
OBJECT IDENTIFIER ::= { sipCommonMIBConform 1 } OBJECT IDENTIFIER ::= { sipCommonMIBConformance 1 }
sipCommonMIBGroups sipCommonMIBGroups
OBJECT IDENTIFIER ::= { sipCommonMIBConform 2 } OBJECT IDENTIFIER ::= { sipCommonMIBConformance 2 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
sipCommonCompliance MODULE-COMPLIANCE sipCommonCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities." "The compliance statement for SIP entities."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipCommonConfigGroup, MANDATORY-GROUPS { sipCommonConfigGroup,
sipCommonStatsGroup } 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 GROUP sipCommonInformationalGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to not provide
not provide any support for these objects as they any support for these objects as they provide optional
provide optional information." information."
GROUP sipCommonConfigTimerGroup GROUP sipCommonConfigTimerGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to not provide
not provide any timer configuration." any timer configuration."
GROUP sipCommonStatsRetryGroup GROUP sipCommonStatsRetryGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to not provide
not provide any retry statistics." any retry statistics."
GROUP sipCommonNotifGroup GROUP sipCommonNotifGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to not provide
not provide any notifications. If implemented, the any notifications. If implemented, the
sipCommonStatusCodeNotifGroup and sipCommonStatusCodeNotifGroup and sipCommonNotifObjectsGroup
sipCommonNotifObjectsGroup MUST also be implemented." MUST also be implemented."
GROUP sipCommonStatusCodeNotifGroup GROUP sipCommonStatusCodeNotifGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to not provide
not provide any notifications. If implemented, the any notifications. If implemented, the sipCommonNotifGroup and
sipCommonNotifGroup and sipCommonNotifObjectsGroup sipCommonNotifObjectsGroup MUST also be implemented."
MUST also be implemented."
GROUP sipCommonNotifObjectsGroup GROUP sipCommonNotifObjectsGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to not provide
not provide any notifications. If implemented, the any notifications. If implemented, the
sipCommonStatusCodeNotifGroup and sipCommonStatusCodeNotifGroup and sipCommonNotifGroup MUST also
sipCommonNotifGroup MUST also be implemented." be implemented."
::= { sipCommonMIBCompliances 1 } ::= { sipCommonMIBCompliances 1 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipCommonConfigGroup OBJECT-GROUP sipCommonConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipProtocolVersion, sipCommonCfgProtocolVersion,
sipServiceOperStatus, sipCommonCfgServiceOperStatus,
sipServiceStartTime, sipCommonCfgServiceStartTime,
sipServiceLastChange, sipCommonCfgServiceLastChange,
sipTransportRcv, sipCommonPortTransportRcv,
sipOptionTag, sipCommonOptionTag,
sipOptionTagHeaderField, sipCommonOptionTagHeaderField,
sipMaxTransactions, sipCommonCfgMaxTransactions,
sipServiceNotifEnable, sipCommonCfgServiceNotifEnable,
sipEntityType, sipCommonCfgEntityType,
sipMethodName sipCommonMethodSupportedName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration common "A collection of objects providing configuration common to all
to all SIP entities." SIP entities."
::= { sipCommonMIBGroups 1 } ::= { sipCommonMIBGroups 1 }
sipCommonInformationalGroup OBJECT-GROUP sipCommonInformationalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipOrganization sipCommonCfgOrganization
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration common to all
common to all SIP entities." SIP entities."
::= { sipCommonMIBGroups 2 } ::= { sipCommonMIBGroups 2 }
sipCommonConfigTimerGroup OBJECT-GROUP sipCommonConfigTimerGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgTimerA, sipCommonCfgTimerA,
sipCfgTimerB, sipCommonCfgTimerB,
sipCfgTimerC, sipCommonCfgTimerC,
sipCfgTimerD, sipCommonCfgTimerD,
sipCfgTimerE, sipCommonCfgTimerE,
sipCfgTimerF, sipCommonCfgTimerF,
sipCfgTimerG, sipCommonCfgTimerG,
sipCfgTimerH, sipCommonCfgTimerH,
sipCfgTimerI, sipCommonCfgTimerI,
sipCfgTimerJ, sipCommonCfgTimerJ,
sipCfgTimerK, sipCommonCfgTimerK,
sipCfgTimerT1, sipCommonCfgTimerT1,
sipCfgTimerT2, sipCommonCfgTimerT2,
sipCfgTimerT4 sipCommonCfgTimerT4
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing timer configuration "A collection of objects providing timer configuration common to
common to all SIP entities." all SIP entities."
::= { sipCommonMIBGroups 3 } ::= { sipCommonMIBGroups 3 }
sipCommonStatsGroup OBJECT-GROUP sipCommonStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipSummaryInRequests, sipCommonSummaryInRequests,
sipSummaryOutRequests, sipCommonSummaryOutRequests,
sipSummaryInResponses, sipCommonSummaryInResponses,
sipSummaryOutResponses, sipCommonSummaryOutResponses,
sipSummaryTotalTransactions, sipCommonSummaryTotalTransactions,
sipStatsOutbounds, sipCommonSummaryDisconTime,
sipStatsInbounds, sipCommonMethodStatsOutbounds,
sipStatusCodeIns, sipCommonMethodStatsInbounds,
sipStatusCodeOuts, sipCommonMethodStatsDisconTime,
sipStatusCodeRowStatus, sipCommonStatusCodeIns,
sipCurrentTransactions, sipCommonStatusCodeOuts,
sipNumUnsupportedUris, sipCommonStatusCodeRowStatus,
sipNumUnsupportedMethods, sipCommonStatusCodeDisconTime,
sipOtherwiseDiscardedMsgs sipCommonTransCurrentactions,
sipCommonOtherStatsNumUnsupportedUris,
sipCommonOtherStatsNumUnsupportedMethods,
sipCommonOtherStatsOtherwiseDiscardedMsgs,
sipCommonOtherStatsDisconTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics common "A collection of objects providing statistics common to all SIP
to all SIP entities." entities."
::= { sipCommonMIBGroups 4 } ::= { sipCommonMIBGroups 4 }
sipCommonStatsRetryGroup OBJECT-GROUP sipCommonStatsRetryGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatsRetries, sipCommonStatsRetries,
sipStatsRetryFinalResponses, sipCommonStatsRetryFinalResponses,
sipStatsRetryNonFinalResponses sipCommonStatsRetryNonFinalResponses,
sipCommonStatsRetryDisconTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing retry statistics." "A collection of objects providing retry statistics."
::= { sipCommonMIBGroups 5 } ::= { sipCommonMIBGroups 5 }
sipCommonNotifGroup NOTIFICATION-GROUP sipCommonNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
sipStatusCodeNotif, sipCommonStatusCodeNotif,
sipStatusCodeThreshExceededInNotif, sipCommonStatusCodeThreshExceededInNotif,
sipStatusCodeThreshExceededOutNotif, sipCommonStatusCodeThreshExceededOutNotif,
sipServiceColdStart, sipCommonServiceColdStart,
sipServiceWarmStart, sipCommonServiceWarmStart,
sipServiceStatusChanged sipCommonServiceStatusChanged
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications common to all SIP "A collection of notifications common to all SIP entities."
entities."
::= { sipCommonMIBGroups 6 } ::= { sipCommonMIBGroups 6 }
sipCommonStatusCodeNotifGroup OBJECT-GROUP sipCommonStatusCodeNotifGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatusCodeNotifSend, sipCommonStatusCodeNotifSend,
sipStatusCodeNotifEmitMode, sipCommonStatusCodeNotifEmitMode,
sipStatusCodeNotifThresh, sipCommonStatusCodeNotifThresh,
sipStatusCodeNotifInterval sipCommonStatusCodeNotifInterval
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects related to controlling and "A collection of objects related to controlling and attribution
attribution of notifications common to all SIP of notifications common to all SIP entities."
entities."
::= { sipCommonMIBGroups 7 } ::= { sipCommonMIBGroups 7 }
sipCommonNotifObjectsGroup OBJECT-GROUP sipCommonNotifObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatusCodeNotifTo, sipCommonStatusCodeNotifTo,
sipStatusCodeNotifFrom, sipCommonStatusCodeNotifFrom,
sipStatusCodeNotifCallId, sipCommonStatusCodeNotifCallId,
sipStatusCodeNotifCSeq, sipCommonStatusCodeNotifCSeq,
sipNotifApplIndex, sipCommonNotifApplIndex,
sipNotifSequenceNumber sipCommonNotifSequenceNumber
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of accessible-for-notify objects "A collection of accessible-for-notify objects related to the
related to the notification defined in this notification defined in this MIB module."
MIB module."
::= { sipCommonMIBGroups 8 } ::= { sipCommonMIBGroups 8 }
END END
7.3. SIP User Agent MIB Module 7.3. SIP User Agent MIB Module
SIP-UA-MIB DEFINITIONS ::= BEGIN SIP-UA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
skipping to change at page 54, line 20 skipping to change at page 55, line 13
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
skipping to change at page 55, line 6 skipping to change at page 55, line 45
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.
The objects in this table entry SHOULD be non-volatile
and their value SHOULD be kept at reboot."
INDEX { applIndex, sipUACfgServerIndex } INDEX { applIndex, sipUACfgServerIndex }
::= { sipUACfgServerTable 1 } ::= { sipUACfgServerTable 1 }
SipUACfgServerEntry ::= SipUACfgServerEntry ::= SEQUENCE {
SEQUENCE {
sipUACfgServerIndex Unsigned32, sipUACfgServerIndex Unsigned32,
sipUACfgServerAddrType InetAddressType, sipUACfgServerAddressType InetAddressType,
sipUACfgServerAddr InetAddress, sipUACfgServerAddress InetAddress,
sipUACfgServerFunction SipEntityRole sipUACfgServerRole SipTCEntityRole
} }
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
"INET-ADDRESS-MIB (RFC 4001)"
::= { sipUACfgServerEntry 2 } ::= { 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
address is determined by the value of the
sipUACfgServerAddressType object."
REFERENCE "INET-ADDRESS-MIB (RFC 4001)" REFERENCE "INET-ADDRESS-MIB (RFC 4001)"
::= { sipUACfgServerEntry 3 } ::= { sipUACfgServerEntry 3 }
sipUACfgServerRole OBJECT-TYPE
sipUACfgServerFunction OBJECT-TYPE SYNTAX SipTCEntityRole
SYNTAX SipEntityRole
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the function of the SIP server "This object reflects the function of the SIP server this user
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
SIP-UA-MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipUAConfigGroup } MANDATORY-GROUPS { sipUAConfigGroup }
::= { sipUAMIBCompliances 1 } ::= { sipUAMIBCompliances 1 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipUAConfigGroup OBJECT-GROUP sipUAConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipUACfgServerAddrType, 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 IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Counter32, Counter32,
Unsigned32, Unsigned32,
Gauge32, Gauge32,
mib-2 mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
skipping to change at page 59, line 4 skipping to change at page 59, line 34
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 DESCRIPTION
"Session Initiation Protocol (SIP) Server MIB module. "Session Initiation Protocol (SIP) Server MIB module. SIP is an
SIP is an application-layer signaling protocol for application-layer signaling protocol for creating, modifying
creating, modifying and terminating multimedia and terminating multimedia sessions with one or more
sessions with one or more participants. These participants. These sessions include Internet multimedia
sessions include Internet multimedia conferences and conferences and Internet telephone calls. SIP is defined in
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 } sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 }
sipServerMIBConform OBJECT IDENTIFIER ::= { sipServerMIB 2 } sipServerMIBConformance OBJECT IDENTIFIER ::= { sipServerMIB 2 }
-- --
-- These groups contain objects common to all SIP servers. -- These groups contain objects common to all SIP servers.
-- --
sipServerCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 1 } sipServerCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 1 }
-- --
-- Common Server Configuration Objects -- Common Server Configuration Objects
-- --
sipServerCfgTable OBJECT-TYPE sipServerCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerCfgEntry SYNTAX SEQUENCE OF SipServerCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable "This table contains configuration objects applicable to SIP
to SIP Redirect and Proxy Servers." Redirect and Proxy Servers."
::= { sipServerCfg 1 } ::= { sipServerCfg 1 }
sipServerCfgEntry OBJECT-TYPE sipServerCfgEntry OBJECT-TYPE
SYNTAX SipServerCfgEntry SYNTAX SipServerCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common configuration. "A row of common configuration.
Each row represents those objects for a particular Each row represents those objects for a particular SIP server
SIP server present in this system. applIndex is used present in this system. applIndex is used to uniquely identify
to uniquely identify these instances of SIP servers these instances of SIP servers and correlate them through the
and correlate them through the common framework of common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
the NETWORK-SERVICES-MIB (RFC 2788). The same value same value of applIndex used in the corresponding
of applIndex used in the corresponding SIP-COMMON-MIB SIP-COMMON-MIB is used here."
is used here.
The objects in this table entry SHOULD be
non-volatile and their value SHOULD be kept at
reboot."
INDEX { applIndex } INDEX { applIndex }
::= { sipServerCfgTable 1 } ::= { sipServerCfgTable 1 }
SipServerCfgEntry ::= SipServerCfgEntry ::=
SEQUENCE { SEQUENCE {
sipServerHostAddrType InetAddressType, sipServerCfgHostAddressType InetAddressType,
sipServerHostAddr InetAddress sipServerCfgHostAddress InetAddress
} }
sipServerHostAddrType OBJECT-TYPE sipServerCfgHostAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of Internet address by which the SIP server "The type of Internet address by which the SIP server is
is reachable." reachable."
REFERENCE REFERENCE
"RFC 3261, Section 19.1.1" "RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 1 } ::= { sipServerCfgEntry 1 }
sipServerHostAddr OBJECT-TYPE sipServerCfgHostAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the host portion of a SIP URI that is "This is the host portion of a SIP URI that is assigned to the
assigned to the SIP server. It MAY contain a fully SIP server. It MAY contain a fully qualified domain name, or
qualified domain name, or an IP address. The length an IP address. The length of the value will depend on the type
of the value will depend on the type of address of address specified. The type of address given by this object
specified. is controlled by sipServerCfgHostAddressType."
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 REFERENCE
"RFC 3261, Section 19.1.1" "RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 2 } ::= { sipServerCfgEntry 2 }
-- --
-- This group contains MIB objects -- This group contains MIB objects
-- related to SIP Proxy Servers. -- related to SIP Proxy Servers.
-- --
sipProxyCfg OBJECT IDENTIFIER ::= sipServerProxyCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 3 }
{ sipServerMIBObjects 3 } sipServerProxyStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 4 }
sipProxyStats OBJECT IDENTIFIER ::=
{ sipServerMIBObjects 4 }
-- --
-- Proxy Server Configuration -- Proxy Server Configuration
-- --
sipProxyCfgTable OBJECT-TYPE sipServerProxyCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipProxyCfgEntry SYNTAX SEQUENCE OF SipServerProxyCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable "This table contains configuration objects applicable to SIP
to SIP Proxy Servers." Proxy Servers."
::= { sipProxyCfg 1 } ::= { sipServerProxyCfg 1 }
sipProxyCfgEntry OBJECT-TYPE sipServerProxyCfgEntry OBJECT-TYPE
SYNTAX SipProxyCfgEntry SYNTAX SipServerProxyCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common proxy configuration. "A row of common proxy configuration.
Each row represents those objects for a particular Each row represents those objects for a particular SIP server
SIP server present in this system. applIndex is used present in this system. applIndex is used to uniquely identify
to uniquely identify these instances of SIP servers these instances of SIP servers and correlate them through the
and correlate them through the common framework of common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
the NETWORK-SERVICES-MIB (RFC 2788). The same value same value of applIndex used in the corresponding
of applIndex used in the corresponding SIP-COMMON-MIB SIP-COMMON-MIB is used here."
is used here.
The objects in this table entry SHOULD be
non-volatile and their value SHOULD be kept at
reboot."
INDEX { applIndex } INDEX { applIndex }
::= { sipProxyCfgTable 1 } ::= { sipServerProxyCfgTable 1 }
SipProxyCfgEntry ::= SipServerProxyCfgEntry ::=
SEQUENCE { SEQUENCE {
sipProxyStatefulness INTEGER, sipServerCfgProxyStatefulness INTEGER,
sipProxyRecursion TruthValue, sipServerCfgProxyRecursion TruthValue,
sipProxyRecordRoute TruthValue, sipServerCfgProxyRecordRoute TruthValue,
sipProxyAuthMethod BITS, sipServerCfgProxyAuthMethod BITS,
sipProxyAuthRealm SnmpAdminString sipServerCfgProxyAuthDefaultRealm SnmpAdminString
} }
sipProxyStatefulness OBJECT-TYPE
sipServerCfgProxyStatefulness OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
stateless(1), stateless(1),
transactionStateful(2), transactionStateful(2),
callStateful(3) callStateful(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the default mode of operation "This object reflects the default mode of operation for the
for the Proxy Server entity. Proxy Server entity.
A stateless proxy is a logical entity that does not A stateless proxy is a logical entity that does not maintain
maintain the client or server transaction state the client or server transaction state machines when it
machines when it processes requests. A stateless processes requests. A stateless proxy forwards every request it
proxy forwards every request it receives downstream receives downstream and every response it receives upstream. If
and every response it receives upstream. If the value the value of this object is stateless(1), the proxy defaults to
of this object is stateless(1), the proxy defaults to
stateless operations. stateless operations.
A transaction stateful proxy, or simply a 'stateful A transaction stateful proxy, or simply a 'stateful proxy', is
proxy', is a logical entity that maintains the client a logical entity that maintains the client and server
and server transaction state machines during the transaction state machines during the processing of a request.
processing of a request. A (transaction) stateful A (transaction) stateful proxy is not the same as a call
proxy is not the same as a call stateful proxy. If stateful proxy. If the value if this object is
the value if this object is transactionStateful(2), transactionStateful(2), the proxy is stateful on a transaction
the proxy is stateful on a transaction basis. basis.
A call stateful proxy is a logical entity if it A call stateful proxy is a logical entity if it retains state
retains state for a dialog from the initiating INVITE for a dialog from the initiating INVITE to the terminating BYE
to the terminating BYE request. A call stateful request. A call stateful proxy is always transaction stateful,
proxy is always transaction stateful, but the but the converse is not necessarily true. If the value of this
converse is not necessarily true. If the value of object is callStateful(3), the proxy is call stateful."
this object is callStateful(3), the proxy is call
stateful."
REFERENCE REFERENCE
"RFC 3261, Section 16" "RFC 3261, Section 16"
::= { sipProxyCfgEntry 1 } ::= { sipServerProxyCfgEntry 1 }
sipProxyRecursion OBJECT-TYPE sipServerCfgProxyRecursion OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects whether or not the Proxy "This object reflects whether or not the Proxy performs
performs recursive search on the Contacts provided in recursive search on the Contacts provided in 3xx redirects.
3xx redirects.
If the value of this object is 'true', a recursive If the value of this object is 'true', a recursive search is
search is performed. If the value is 'false', no performed. If the value is 'false', no search is performed,
search is performed, the 3xx response is sent the 3xx response is sent upstream towards the source of the
upstream towards the source of the request." request."
REFERENCE REFERENCE
"RFC 3261 Sections 16.5 and 16.6" "RFC 3261 Sections 16.5 and 16.6"
::= { sipProxyCfgEntry 2 } ::= { sipServerProxyCfgEntry 2 }
sipProxyRecordRoute OBJECT-TYPE sipServerCfgProxyRecordRoute OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects whether or not the proxy adds "This object reflects whether or not the proxy adds itself to
itself to the Record-Route header as a default the Record-Route header as a default action. This header is
action. used to list the proxies that insist on being in the signaling
This header is used to list the proxies that insist path for subsequent requests related to the call-leg.
on being in the signaling path for subsequent
requests related to the call-leg.
If the value of this object is 'true', the proxy adds If the value of this object is 'true', the proxy adds itself to
itself to the end of the Record-Route header, the end of the Record-Route header, creating the header if
creating the header if required. If the value is required. If the value is 'false', the proxy does not add
'false', the proxy does not add itself to the itself to the Record-Route header."
Record-Route header."
REFERENCE REFERENCE
"RFC 3261, Section 20.30" "RFC 3261, Section 20.30"
::= { sipProxyCfgEntry 3 } ::= { sipServerProxyCfgEntry 3 }
-- --
-- Security -- Security
-- --
sipProxyAuthMethod OBJECT-TYPE sipServerCfgProxyAuthMethod OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
none(0), none(0),
tls(1), tls(1),
digest(2) digest(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the authentication methods that "This object reflects the authentication methods that MAY be
MAY be used to authenticate request originators. used to authenticate request originators.
bit 0 no authentication is performed bit 0 no authentication is performed
bit 1 TLS is used bit 1 TLS is used
bit 2 HTTP Digest is used." bit 2 HTTP Digest is used."
REFERENCE REFERENCE
"RFC 3261 Sections 22, 23, 26, 26.2.3" "RFC 3261 Sections 22, 23, 26, 26.2.3"
::= { sipProxyCfgEntry 4 } ::= { sipServerProxyCfgEntry 4 }
sipProxyAuthRealm OBJECT-TYPE sipServerCfgProxyAuthDefaultRealm OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the default realm value used in "This object reflects the default realm value used in
Proxy-Authenticate headers. Note that this MAY need Proxy-Authenticate headers. Note that this MAY need to be
to be stored per user, in which case, this default stored per user, in which case, this default value is ignored.
value is ignored." "
REFERENCE REFERENCE
"RFC 3261, Section 22.1" "RFC 3261, Section 22.1"
::= { sipProxyCfgEntry 5 } ::= { sipServerProxyCfgEntry 5 }
-- --
-- Proxy Server Statistics -- Proxy Server Statistics
-- --
sipProxyStatsTable OBJECT-TYPE sipServerProxyStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipProxyStatsEntry SYNTAX SEQUENCE OF SipServerProxyStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the statistics objects applicable "This table contains the statistics objects applicable to all
to all SIP Proxy Servers in this system." SIP Proxy Servers in this system."
::= { sipProxyStats 1 } ::= { sipServerProxyStats 1 }
sipProxyStatsEntry OBJECT-TYPE sipServerProxyStatsEntry OBJECT-TYPE
SYNTAX SipProxyStatsEntry SYNTAX SipServerProxyStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics. "A row of summary statistics.
Each row represents those objects for a particular Each row represents those objects for a particular SIP server
SIP server present in this system. applIndex is used present in this system. applIndex is used to uniquely identify
to uniquely identify these instances of SIP servers these instances of SIP servers and correlate them through the
and correlate them through the common framework of common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
the NETWORK-SERVICES-MIB (RFC 2788). The same value same value of applIndex used in the corresponding
of applIndex used in the corresponding SIP-COMMON-MIB SIP-COMMON-MIB is used here."
is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipProxyStatsTable 1 } ::= { sipServerProxyStatsTable 1 }
SipProxyStatsEntry ::=
SipServerProxyStatsEntry ::=
SEQUENCE { SEQUENCE {
sipNumProxyRequireFailures Counter32 sipServerProxyStatProxyReqFailures Counter32,
sipServerProxyStatsDisconTime TimeStamp
} }
sipNumProxyRequireFailures OBJECT-TYPE sipServerProxyStatProxyReqFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the number of occurrences of "This object contains the number of occurrences of unsupported
unsupported options being specified in received options being specified in received Proxy-Require headers.
Proxy- Require headers. Such occurrences result in a Such occurrences result in a 420 Bad Extension status code
420 Bad Extension status code being returned." being returned.
::= { sipProxyStatsEntry 1 }
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipServerProxyStatsDisconTime object in the same
row."
::= { sipServerProxyStatsEntry 1 }
sipServerProxyStatsDisconTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the sysUpTime object when the counters for the server
statistics objects in this row last experienced a discontinuity."
::= { sipServerProxyStatsEntry 2 }
-- --
-- This group contains MIB objects related to SIP Registrars. -- This group contains MIB objects related to SIP Registrars.
-- --
sipRegCfg OBJECT IDENTIFIER ::= sipServerRegCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 5 }
{ sipServerMIBObjects 5 } sipServerRegStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 6 }
sipRegStats OBJECT IDENTIFIER ::=
{ sipServerMIBObjects 6 }
-- --
-- Registrar Configuration -- Registrar Configuration
-- --
sipRegCfgTable OBJECT-TYPE sipServerRegCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegCfgEntry SYNTAX SEQUENCE OF SipServerRegCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable "This table contains configuration objects applicable SIP
SIP Registrars." Registrars."
::= { sipRegCfg 1 } ::= { sipServerRegCfg 1 }
sipRegCfgEntry OBJECT-TYPE sipServerRegCfgEntry OBJECT-TYPE
SYNTAX SipRegCfgEntry SYNTAX SipServerRegCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common Registrar configuration. "A row of common Registrar configuration.
Each row represents those objects for a particular Each row represents those objects for a particular SIP server
SIP server present in this system. applIndex is used present in this system. applIndex is used to uniquely identify
to uniquely identify these instances of SIP servers these instances of SIP servers and correlate them through the
and correlate them through the common framework of common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
the NETWORK-SERVICES-MIB (RFC 2788). The same value same value of applIndex used in the corresponding
of applIndex used in the corresponding SIP-COMMON-MIB SIP-COMMON-MIB is used here."
is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipRegCfgTable 1 } ::= { sipServerRegCfgTable 1 }
SipRegCfgEntry ::= SipServerRegCfgEntry ::=
SEQUENCE { SEQUENCE {
sipRegMaxContactExpiryDuration Unsigned32, sipServerRegMaxContactExpiryDuration Unsigned32,
sipRegMaxUsers Unsigned32, sipServerRegMaxUsers Unsigned32,
sipRegCurrentUsers Gauge32, sipServerRegCurrentUsers Gauge32,
sipRegDfltRegActiveInterval Unsigned32 sipServerRegDfltRegActiveInterval Unsigned32
} }
sipRegMaxContactExpiryDuration OBJECT-TYPE sipServerRegMaxContactExpiryDuration OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum expiry that may be "This object reflects the maximum expiry that may be requested
requested by a User Agent for a particular Contact. by a User Agent for a particular Contact. User Agents can
User Agents can specify expiry using either an Expiry specify expiry using either an Expiry header in a REGISTER
header in a REGISTER request, or using an Expires request, or using an Expires parameter in a Contact header in
parameter in a Contact header in a REGISTER request. a REGISTER request. If the value requested by the User Agent
If the value requested by the User Agent is greater is greater than the value of this object, then the contact
than the value of this object, then the contact information is given the duration specified by this object, and
information is given the duration specified by this that duration is indicated to the User Agent in the response."
object, and that duration is indicated to the User ::= { sipServerRegCfgEntry 1 }
Agent in the response." sipServerRegMaxUsers OBJECT-TYPE
::= { sipRegCfgEntry 1 }
sipRegMaxUsers OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum number of users that "This object reflects the maximum number of users that the
the Registrar supports. The current number of users Registrar supports. The current number of users is reflected
is reflected by sipRegCurrentUsers." by sipServerRegCurrentUsers."
::= { sipRegCfgEntry 2 } ::= { sipServerRegCfgEntry 2 }
sipRegCurrentUsers OBJECT-TYPE sipServerRegCurrentUsers OBJECT-TYPE
SYNTAX Gauge32 (0..4294967295) SYNTAX Gauge32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of users currently "This object reflects the number of users currently registered
registered with the Registrar." with the Registrar."
::= { sipRegCfgEntry 3 } ::= { sipServerRegCfgEntry 3 }
sipRegDfltRegActiveInterval OBJECT-TYPE sipServerRegDfltRegActiveInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the default time interval the "This object reflects the default time interval the Registrar
Registrar considers registrations to be active. The considers registrations to be active. The value is used to
value is used to compute the Expires header in the compute the Expires header in the REGISTER response. If a user
REGISTER response. If a user agent requests a time agent requests a time interval shorter than specified by this
interval shorter than specified by this object, the object, the Registrar SHOULD honor that request. If a Contact
Registrar SHOULD honor that request. If a Contact entry does not have an 'expires' parameter, the value of the
entry does not have an 'expires' parameter, the value Expires header field is used instead. If a Contact entry has no
of the Expires header field is used instead. If a 'expires' parameter and no the Expires header field is present,
Contact entry has no 'expires' parameter and no the the value of this object is used as the default value."
Expires header field is present, the value of this REFERENCE
object is used as the default value. "RFC 3261, Section 10.2"
This object SHOULD be non-volatile and its value ::= { sipServerRegCfgEntry 4 }
SHOULD be kept at reboot."
REFERENCE "RFC 3261, Section 10.2"
::= { sipRegCfgEntry 4 }
-- --
-- Per User Information -- Per User Information
-- --
sipRegUserTable OBJECT-TYPE sipServerRegUserTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegUserEntry SYNTAX SEQUENCE OF SipServerRegUserEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on all users "This table contains information on all users registered to each
registered to each Registrar in this system." Registrar in this system."
::= { sipRegCfg 2 } ::= { sipServerRegCfg 2 }
sipServerRegUserEntry OBJECT-TYPE
sipRegUserEntry OBJECT-TYPE SYNTAX SipServerRegUserEntry
SYNTAX SipRegUserEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single user "This entry contains information for a single user registered to
registered to this Registrar. this Registrar.
Each row represents those objects for a particular Each row represents those objects for a particular SIP server
SIP server present in this system. applIndex is used present in this system. applIndex is used to uniquely identify
to uniquely identify these instances of SIP servers these instances of SIP servers and correlate them through the
and correlate them through the common framework of common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
the NETWORK-SERVICES-MIB (RFC 2788). The same value same value of applIndex used in the corresponding
of applIndex used in the corresponding SIP-COMMON-MIB SIP-COMMON-MIB is used here."
is used here." INDEX { applIndex, sipServerRegUserIndex }
INDEX { applIndex, sipUserIndex } ::= { sipServerRegUserTable 1 }
::= { sipRegUserTable 1 }
SipRegUserEntry ::= SipServerRegUserEntry ::=
SEQUENCE { SEQUENCE {
sipUserIndex Unsigned32, sipServerRegUserIndex Unsigned32,
sipUserUri SnmpAdminString, sipServerRegUserUri SnmpAdminString,
sipUserAuthenticationFailures Counter32 sipServerRegUserAuthenticationFailures Counter32,
sipServerRegUserDisconTime TimeStamp
} }
sipUserIndex OBJECT-TYPE sipServerRegUserIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in "This object uniquely identifies a conceptual row in the table."
the table." ::= { sipServerRegUserEntry 1 }
::= { sipRegUserEntry 1 }
sipUserUri OBJECT-TYPE sipServerRegUserUri OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the user's address-of-record. "This object contains the user's address-of-record. It is the
It is the main form by which the Registrar knows the main form by which the Registrar knows the user. The format is
user. The format is typically 'user@domain'. It is typically 'user@domain'. It is contained in the To header for
contained in the To header for all REGISTER all REGISTER requests."
requests." ::= { sipServerRegUserEntry 2 }
::= { sipRegUserEntry 2 }
sipUserAuthenticationFailures OBJECT-TYPE sipServerRegUserAuthenticationFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of times "This object contains a count of the number of times the user
the user has failed authentication." has failed authentication.
::= { sipRegUserEntry 3 }
Discontinuities in the value of this counter can occur due to
successful user authentications, and at re-initialization of
the SIP entity or service. A Management Station can detect
discontinuities in this counter by monitoring the
sipServerRegUserDisconTime object in the same row."
::= { sipServerRegUserEntry 3 }
sipServerRegUserDisconTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the sysUpTime object when the counters for the
user registration statistic objects in this row last
experienced a discontinuity."
::= { sipServerRegUserEntry 4 }
-- --
-- Per Contact Information -- Per Contact Information
-- --
sipContactTable OBJECT-TYPE sipServerRegContactTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipContactEntry SYNTAX SEQUENCE OF SipServerRegContactEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on every location "This table contains information on every location where a
where a registered user (specified by sipUserIndex) registered user (specified by sipServerRegUserIndex) wishes to
wishes to be found (i.e. the user has provided Contact be found (i.e. the user has provided Contact information to
information to each SIP Registrar in this system)." each SIP Registrar in this system)."
::= { sipRegCfg 3 } ::= { sipServerRegCfg 3 }
sipContactEntry OBJECT-TYPE sipServerRegContactEntry OBJECT-TYPE
SYNTAX SipContactEntry SYNTAX SipServerRegContactEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single Contact. "This entry contains information for a single Contact. Multiple
Multiple contacts may exist for a single user. contacts may exist for a single user.
Each row represents those objects for a particular Each row represents those objects for a particular SIP server
SIP server present in this system. applIndex is used present in this system. applIndex is used to uniquely identify
to uniquely identify these instances of SIP servers these instances of SIP servers and correlate them through the
and correlate them through the common framework of common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
the NETWORK-SERVICES-MIB (RFC 2788). The same value same value of applIndex used in the corresponding
of applIndex used in the corresponding SIP-COMMON-MIB SIP-COMMON-MIB is used here."
is used here." INDEX { applIndex,
INDEX { applIndex, sipUserIndex, sipContactIndex } sipServerRegUserIndex,
::= { sipContactTable 1 } sipServerRegContactIndex
}
::= { sipServerRegContactTable 1 }
SipContactEntry ::= SipServerRegContactEntry ::=
SEQUENCE { SEQUENCE {
sipContactIndex Unsigned32, sipServerRegContactIndex Unsigned32,
sipContactDisplayName SnmpAdminString, sipServerRegContactDisplayName SnmpAdminString,
sipContactURI SnmpAdminString, sipServerRegContactURI SnmpAdminString,
sipContactLastUpdated TimeStamp, sipServerRegContactLastUpdated TimeStamp,
sipContactExpiry DateAndTime, sipServerRegContactExpiry DateAndTime,
sipContactPreference SnmpAdminString sipServerRegContactPreference SnmpAdminString
} }
sipContactIndex OBJECT-TYPE sipServerRegContactIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Along with the sipUserIndex, this object uniquely "Along with the sipServerRegUserIndex, this object uniquely
identifies a conceptual row in the table." identifies a conceptual row in the table."
::= { sipContactEntry 1 } ::= { sipServerRegContactEntry 1 }
sipContactDisplayName OBJECT-TYPE
sipServerRegContactDisplayName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the display name for the "This object contains the display name for the Contact. For
Contact. example, 'Santa at Home', or 'Santa on his Sled', corresponding
For example, 'Santa at Home', or 'Santa on his Sled', to contact URIs of sip:BigGuy@example.com or
corresponding to contact URIs of
sip:BigGuy@example.com or
sip:sclaus817@example.com, respectively." sip:sclaus817@example.com, respectively."
::= { sipContactEntry 2 } ::= { sipServerRegContactEntry 2 }
sipContactURI OBJECT-TYPE sipServerRegContactURI OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains either a SIP URI where "This object contains either a SIP URI where the user can be
the user can be contacted. This URI is normally contacted. This URI is normally returned to a client from a
returned to a client from a Redirect Server, or is Redirect Server, or is used as the RequestURI in a SIP request
used as the RequestURI in a SIP request line for line for requests forwarded by a proxy."
requests forwarded by a proxy." ::= { sipServerRegContactEntry 3 }
::= { sipContactEntry 3 }
sipContactLastUpdated OBJECT-TYPE sipServerRegContactLastUpdated OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the time when this contact "This object indicates the time when this contact information
information was accepted. If the contact information was accepted. If the contact information is updated via a
is updated via a subsequent REGISTER of the same subsequent REGISTER of the same information, this object is
information, this object is also updated." also updated."
::= { sipContactEntry 4 } ::= { sipServerRegContactEntry 4 }
sipContactExpiry OBJECT-TYPE sipServerRegContactExpiry OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the date and time when the "This object contains the date and time when the contact
contact information will no longer be valid. Such information will no longer be valid. Such times may be
times may be specified by the user at registration specified by the user at registration (Expires header or expiry
(Expires header or expiry parameter in the Contact parameter in the Contact information), or a system default can
information), or a system default can be applied." be applied."
::= { sipContactEntry 5 } ::= { sipServerRegContactEntry 5 }
sipContactPreference OBJECT-TYPE
sipServerRegContactPreference OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a relative preference for the "This object indicates a relative preference for the particular
particular Contact header field value compared to Contact header field value compared to other bindings for this
other bindings for this address-of-record. A address-of-record. A registering user may provide this
registering user may provide this preference as a preference as a 'qvalue' parameter in the Contact header.
'qvalue' parameter in the Contact header.
The format of this item is a decimal number between 0 The format of this item is a decimal number between 0 and 1
and 1 (for example 0.9). Higher values indicate (for example 0.9). Higher values indicate locations preferred
locations preferred by the user." by the user."
REFERENCE REFERENCE
"RFC 3261, Section 10.2.1.2, 16.6 and 20.10" "RFC 3261, Section 10.2.1.2, 16.6 and 20.10"
::= { sipContactEntry 6 } ::= { sipServerRegContactEntry 6 }
-- --
-- Registrar Statistics -- Registrar Statistics
-- --
sipRegStatsTable OBJECT-TYPE sipServerRegStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegStatsEntry SYNTAX SEQUENCE OF SipServerRegStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the summary statistics objects "This table contains the summary statistics objects applicable
applicable to all SIP Registrars in this system." to all SIP Registrars in this system."
::= { sipRegStats 1 } ::= { sipServerRegStats 1 }
sipRegStatsEntry OBJECT-TYPE sipServerRegStatsEntry OBJECT-TYPE
SYNTAX SipRegStatsEntry SYNTAX SipServerRegStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics. "A row of summary statistics.
Each row represents those objects for a particular Each row represents those objects for a particular SIP server
SIP server present in this system. applIndex is used present in this system. applIndex is used to uniquely identify
to uniquely identify these instances of SIP servers these instances of SIP servers and correlate them through the
and correlate them through the common framework of common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
the NETWORK-SERVICES-MIB (RFC 2788). The same value same value of applIndex used in the corresponding
of applIndex used in the corresponding SIP-COMMON-MIB SIP-COMMON-MIB is used here."
is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipRegStatsTable 1 } ::= { sipServerRegStatsTable 1 }
SipRegStatsEntry ::=
SipServerRegStatsEntry ::=
SEQUENCE { SEQUENCE {
sipRegAcceptedRegistrations Counter32, sipServerRegStatsAcceptedRegs Counter32,
sipRegRejectedRegistrations Counter32 sipServerRegStatsRejectedRegs Counter32,
sipServerRegStatsDisconTime TimeStamp
} }
sipRegAcceptedRegistrations OBJECT-TYPE sipServerRegStatsAcceptedRegs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of "This object contains a count of the number of REGISTER requests
REGISTER requests that have been accepted (status code that have been accepted (status code 200) by the Registrar.
200) by the Registrar. This includes additions of new This includes additions of new contact information, refreshing
contact information, refreshing contact information, contact information, as well as requests for deletion of
as well as requests for deletion of contact contact information.
information."
::= { sipRegStatsEntry 1 }
sipRegRejectedRegistrations OBJECT-TYPE Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipServerRegStatsDisconTime object in the same
row."
::= { sipServerRegStatsEntry 1 }
sipServerRegStatsRejectedRegs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number REGISTER "This object contains a count of the number REGISTER requests
requests that have been rejected by the Registrar." that have been rejected by the Registrar.
::= { sipRegStatsEntry 2 }
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipServerRegStatsDisconTime object in the same
row."
::= { sipServerRegStatsEntry 2 }
sipServerRegStatsDisconTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the sysUpTime object when the counters for the
registrar statistic objects in this row last experienced a
discontinuity."
::= { sipServerRegStatsEntry 3 }
-- --
-- Conformance -- Conformance
-- --
sipServerMIBCompliances sipServerMIBCompliances
OBJECT IDENTIFIER ::= { sipServerMIBConform 1 } OBJECT IDENTIFIER ::= { sipServerMIBConformance 1 }
sipServerMIBGroups sipServerMIBGroups
OBJECT IDENTIFIER ::= { sipServerMIBConform 2 } OBJECT IDENTIFIER ::= { sipServerMIBConformance 2 }
-- --
-- Compliance Statements -- Compliance Statements
-- --
sipProxyServerCompliance MODULE-COMPLIANCE sipServerProxyServerCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities acting "The compliance statement for SIP entities acting as Proxy
as Proxy Servers." Servers."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup, MANDATORY-GROUPS { sipServerConfigGroup,
sipProxyConfigGroup, sipServerProxyConfigGroup,
sipProxyStatsGroup } sipServerProxyStatsGroup
}
::= { sipServerMIBCompliances 1 } ::= { sipServerMIBCompliances 1 }
sipRedirectServerCompliance MODULE-COMPLIANCE sipRedirectServerCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities acting "The compliance statement for SIP entities acting as Redirect
as Redirect Servers." Servers."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup } MANDATORY-GROUPS { sipServerConfigGroup }
::= { sipServerMIBCompliances 2 } ::= { sipServerMIBCompliances 2 }
sipRegistrarServerCompliance MODULE-COMPLIANCE sipServerRegistrarServerCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities acting "The compliance statement for SIP entities acting as
as Registrars." Registrars."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup, MANDATORY-GROUPS { sipServerConfigGroup,
sipRegistrarConfigGroup, sipServerRegistrarConfigGroup,
sipRegistrarStatsGroup } sipServerRegistrarStatsGroup }
GROUP sipRegistrarUsersGroup GROUP sipServerRegistrarUsersGroup
DESCRIPTION DESCRIPTION
"This is an optional group." "This is an optional group."
::= { sipServerMIBCompliances 3 } ::= { sipServerMIBCompliances 3 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipServerConfigGroup OBJECT-GROUP sipServerConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipServerHostAddrType, sipServerCfgHostAddressType,
sipServerHostAddr sipServerCfgHostAddress
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration common to SIP
common to SIP Proxy and Redirect servers." Proxy and Redirect servers."
::= { sipServerMIBGroups 1 } ::= { sipServerMIBGroups 1 }
sipProxyConfigGroup OBJECT-GROUP sipServerProxyConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipProxyStatefulness, sipServerCfgProxyStatefulness,
sipProxyRecursion, sipServerCfgProxyRecursion,
sipProxyRecordRoute, sipServerCfgProxyRecordRoute,
sipProxyAuthMethod, sipServerCfgProxyAuthMethod,
sipProxyAuthRealm sipServerCfgProxyAuthDefaultRealm
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration for "A collection of objects providing configuration for SIP Proxy
SIP Proxy servers." servers."
::= { sipServerMIBGroups 2 } ::= { sipServerMIBGroups 2 }
sipProxyStatsGroup OBJECT-GROUP sipServerProxyStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipNumProxyRequireFailures sipServerProxyStatProxyReqFailures,
sipServerProxyStatsDisconTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics for "A collection of objects providing statistics for SIP Proxy
SIP Proxy servers." servers."
::= { sipServerMIBGroups 3 } ::= { sipServerMIBGroups 3 }
sipRegistrarConfigGroup OBJECT-GROUP sipServerRegistrarConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipRegMaxContactExpiryDuration, sipServerRegMaxContactExpiryDuration,
sipRegMaxUsers, sipServerRegMaxUsers,
sipRegCurrentUsers, sipServerRegCurrentUsers,
sipRegDfltRegActiveInterval sipServerRegDfltRegActiveInterval
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration for "A collection of objects providing configuration for SIP
SIP Registrars." Registrars."
::= { sipServerMIBGroups 4 } ::= { sipServerMIBGroups 4 }
sipRegistrarStatsGroup OBJECT-GROUP sipServerRegistrarStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipRegAcceptedRegistrations, sipServerRegStatsAcceptedRegs,
sipRegRejectedRegistrations sipServerRegStatsRejectedRegs,
sipServerRegStatsDisconTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics for "A collection of objects providing statistics for SIP
SIP Registrars." Registrars."
::= { sipServerMIBGroups 5 } ::= { sipServerMIBGroups 5 }
sipRegistrarUsersGroup OBJECT-GROUP sipServerRegistrarUsersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipUserUri, sipServerRegUserUri,
sipUserAuthenticationFailures, sipServerRegUserAuthenticationFailures,
sipContactDisplayName, sipServerRegUserDisconTime,
sipContactURI, sipServerRegContactDisplayName,
sipContactLastUpdated, sipServerRegContactURI,
sipContactExpiry, sipServerRegContactLastUpdated,
sipContactPreference sipServerRegContactExpiry,
sipServerRegContactPreference
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects related to registered users." "A collection of objects related to registered users."
::= { sipServerMIBGroups 6 } ::= { sipServerMIBGroups 6 }
END END
8. IANA Considerations 8. IANA Considerations
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).
skipping to change at page 78, line 22 skipping to change at page 79, line 18
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 sipMaxTransactions to reflect that it is max transactions o changed sipCommonCfgMaxTransactions to reflect that it is max
per second; transactions per second;
o removed sipOrganization from mandatory sipCommonConfigGroup in o removed sipCommonCfgOrganization from mandatory
MODULE-COMPLIANCE and created a new (opitonal) object group sipCommonConfigGroup in MODULE-COMPLIANCE and created a new
sipCommonInformationalGroup; (opitonal) object group sipCommonInformationalGroup;
o updated DESCRIPTION of sipProxyAuthRealm to indicate that this o updated DESCRIPTION of sipServerProxyDefaultAuthRealm to indicate
object is the *default* realm value used by the proxy in Proxy- that this object is the *default* realm value used by the proxy in
Authenticate headers and, added a note to say that in case of per Proxy-Authenticate headers and, added a note to say that in case
user storage, the default value is ignored by the proxy. 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 o removed sipServerRegAllowThirdParty because no registrar
list), and a registrar would have to implement new logic in order implementer seems to track them differently internally (no comment
to be able to exercise this part of the mib. 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
compli