draft-ietf-sip-mib-12.txt   rfc4780.txt 
SIP Working Group K. Lingle Network Working Group K. Lingle
Internet-Draft Cisco Systems, Inc. Request for Comments: 4780 Cisco Systems, Inc.
Intended status: Standards Track J-F. Mule Category: Standards Track J-F. Mule
Expires: March 19, 2007 CableLabs CableLabs
J. Maeng J. Maeng
D. Walker D. Walker
September 15, 2006 April 2007
Management Information Base for the Session Initiation Protocol (SIP)
draft-ietf-sip-mib-12.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Management Information Base for
http://www.ietf.org/ietf/1id-abstracts.txt. the Session Initiation Protocol (SIP)
The list of Internet-Draft Shadow Directories can be accessed at Status of This Memo
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 19, 2007. This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that are used to In particular, it describes a set of managed objects that are used to
manage Session Initiation Protocol (SIP) entities, which include User manage Session Initiation Protocol (SIP) entities, which include User
Agents, Proxy, Redirect and Registrar servers. Agents, and Proxy, Redirect and Registrar servers.
Table of Contents Table of Contents
1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions .....................................................2
3. The Internet-Standard Management Framework . . . . . . . . . . 3 3. The Internet-Standard Management Framework ......................2
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview ........................................................3
5. Structure of the SIP MIB . . . . . . . . . . . . . . . . . . . 4 5. Structure of the SIP MIB ........................................3
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 ............................11
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. Definitions ....................................................12
7.1. SIP Textual Conventions . . . . . . . . . . . . . . . . . 11 7.1. SIP Textual Conventions ...................................12
7.2. SIP Common MIB Module . . . . . . . . . . . . . . . . . . 15 7.2. SIP Common MIB Module .....................................15
7.3. SIP User Agent MIB Module . . . . . . . . . . . . . . . . 54 7.3. SIP User Agent MIB Module .................................55
7.4. SIP Server MIB Module (Proxy, Redirect and Registrar 7.4. SIP Server MIB Module (Proxy, Redirect, and
Servers) . . . . . . . . . . . . . . . . . . . . . . . . . 58 Registrar Servers) ........................................59
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 77 8. IANA Considerations ............................................77
9. Security Considerations . . . . . . . . . . . . . . . . . . . 77 9. Security Considerations ........................................78
10. Contributor Acknowledgments . . . . . . . . . . . . . . . . . 79 10. Contributor Acknowledgments ...................................80
11. Changes from Previous Draft Revisions . . . . . . . . . . . . 79 11. References ....................................................80
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 93 11.1. Normative References .....................................80
12.1. Normative References . . . . . . . . . . . . . . . . . . . 93 11.2. Informative References ...................................81
12.2. Informative References . . . . . . . . . . . . . . . . . . 94
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 94
Intellectual Property and Copyright Statements . . . . . . . . . . 96
1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that are used to In particular, it describes a set of managed objects that are used to
manage Session Initiation Protocol (SIP) entities, which include User manage Session Initiation Protocol (SIP) entities, which include User
Agents, Proxy, Redirect and Registrar servers. The managed objects Agents, and Proxy, Redirect and Registrar servers. The managed
defined in this document are intended to provide basic SIP protocol objects defined in this document are intended to provide basic SIP
management for SIP entities. The management of application-specific protocol management for SIP entities. The management of
or service-specific SIP configuration is out of scope. application-specific or service-specific SIP configuration is out of
scope.
2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 3, line 45 skipping to change at page 3, line 22
2580 [RFC2580]. 2580 [RFC2580].
4. Overview 4. Overview
SIP [RFC3261] is an application-layer control (signaling) protocol SIP [RFC3261] is an application-layer control (signaling) protocol
for creating, modifying, and terminating sessions with one or more for creating, modifying, and terminating sessions with one or more
participants. These sessions include Internet telephone calls, participants. These sessions include Internet telephone calls,
multimedia distribution, and multimedia conferences. multimedia distribution, and multimedia conferences.
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 (UA), and Proxy, Redirect, and
servers: it is intended to provide management of the basic SIP Registrar servers. It is intended to provide management of the basic
entities. It provides for monitoring of status and protocol SIP 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-MIB. SIP-COMMON-MIB contains common MIB objects UA-MIB, and SIP-TC-MIB. SIP-COMMON-MIB contains common MIB objects
used in all the SIP entities. SIP-SERVER-MIB contains objects used in all the SIP entities. SIP-SERVER-MIB contains objects
specific to Proxy, Redirect and Registrar servers, and SIP-UA-MIB specific to Proxy, Redirect, and Registrar servers. SIP-UA-MIB
includes objects specific to User Agents. SIP-TC-MIB defines the includes objects specific to User Agents. SIP-TC-MIB defines the
textual conventions used throughout MIB modules. textual conventions used throughout the MIB modules.
The MIB modules contain following groups of objects: The MIB modules contain the 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 servers), 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.
* sipCommonSummaryStats: 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.
* sipCommonMethodStats: 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 of 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
method basis. per-method basis.
* sipCommonOtherStats: This object group defines additional * sipCommonOtherStats: This object group defines additional
statistic objects including the number of SIP requests received statistics objects including the number of SIP requests
with unsupported URIs, the number of requests received with received with unsupported URIs, the number of requests received
unsupported SIP methods, and the number of discarded messages. with 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 sipCommonStatusCodeNotif: indicates that a specific status code o sipCommonStatusCodeNotif: indicates that a specific status code
has been sent or received by the system. has been sent or received by the system.
o sipCommonStatusCodeThreshExceededNotif: indicates that a specific o sipCommonStatusCodeThreshExceededNotif: indicates that a specific
status code has been sent or received by the system enough to status code has been sent or received by the system frequently
exceed the configured threshold. enough to 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.
* sipServerProxyCfg: This object group defines configuration * sipServerProxyCfg: This object group defines configuration
objects for SIP Proxy servers including the proxy mode of objects for SIP Proxy Servers including the proxy mode of
operation (stateless, stateful, call stateful), the proxy operation (stateless, stateful, call stateful), the proxy
authentication method(s) and realm, etc. authentication method(s), realm, etc.
* sipServerProxyStats: This object group defines a table * sipServerProxyStats: This object group defines a table
containing the statistics objects applicable to SIP proxy containing the statistics objects applicable to SIP Proxy
servers. It includes the number of occurrences of unsupported Servers. It includes the number of occurrences of unsupported
options being specified in received Proxy-Require headers. options being specified in received Proxy-Require headers.
* sipServerRegCfg: 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, such as the maximum
expiry that may be requested by user agents, the maximum number registration expiry that may be requested by user agents, the
of users the registrar can support, the number of currently maximum number of users the registrar can support, the number
registered users, per contact registration information, etc. of currently registered users, per contact registration
information, etc.
* sipServerRegStats: This object group contains summary * sipServerRegStats: This object group contains summary
statistics objects for SIP Registrar servers, precisely, the statistics objects for SIP Registrar servers. Precisely, it
number of REGISTER requests that have been accepted or contains the number of REGISTER requests that have been
rejected. 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 the UA uses 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 5.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 SipTCTransportProtocol, SipTCEntityRole, The data types SipTCTransportProtocol, SipTCEntityRole,
SipTCOptionTagHeaders, and SipTCMethodName are defined in the SIP-TC- SipTCOptionTagHeaders, and SipTCMethodName are defined in the SIP-
MIB module and used as Textual Conventions in this document. TC-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].
A device implementing the SIP MIB MUST support the NETWORK-SERVICES- A device implementing the SIP MIB MUST support the NETWORK-SERVICES-
MIB and, at a minimum, it MUST support the index and name objects MIB and, at a minimum, MUST support the index and name objects
(applIndex and applName) in the application table (applTable). In (applIndex and applName) in the application table (applTable). In
order to allow each instance of a SIP entity to be managed as a order to allow each instance of a SIP entity to be managed as a
separate network service application, a naming convention SHOULD be separate network service application, a naming convention SHOULD be
used to make the application name unique. For example, if a system used to make the application name unique. For example, if a system
is running 2 SIP UAs that need to be managed as 2 separate SIP is running 2 SIP UAs that need to be managed as 2 separate SIP
entities, by convention, the application names used in the Network entities, by convention, the application names used in the Network
Services Monitoring MIB application table should be "sip_ua1" and Services Monitoring MIB application table should be "sip_ua1" and
"sip_ua2". This convention allows each instance to have its own row "sip_ua2". This convention allows each instance to have its own row
in the application table (applTable). in the application table (applTable).
It is therefore RECOMMENDED to adopt the following application name It is therefore RECOMMENDED that the following application name
conventions: conventions be adopted:
o for a SIP Proxy entity, the applName value SHOULD be equal to a o for a SIP Proxy entity, the applName value SHOULD be equal to a
character string starting with "sip_proxy" followed by a unique character string starting with "sip_proxy" followed by a unique
application instance identifier, for example, "sip_proxy1", application instance identifier, for example, "sip_proxy1",
"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 SHOULD 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 and Redirect exists, list Redirect second. * if Proxy exists, list first.
* if Registrar exists, always list last. * if Proxy and Redirect exists, list Redirect second.
* 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 is 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,
whereas the value of the instance identifier to be used in the whereas the value of the instance identifier to be used in the
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 sipCommonCfgServiceStartTime defined in the SIP-COMMON-MIB of sipCommonCfgServiceStartTime defined in the SIP-COMMON-MIB
module, module.
o applOperStatus: the value of applOperStatus SHOULD reflect the o applOperStatus: the value of applOperStatus SHOULD reflect the
operational status of sipCommonCfgServiceOperStatus, at least by operational status of sipCommonCfgServiceOperStatus, at least by
means of a 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 sipCommonCfgServiceLastChange defined in the SIP- the value of sipCommonCfgServiceLastChange defined in the SIP-
COMMON 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:
Proxy and Registrar server might be configured to maintain separate
SIP-COMMON-MIB instances.
The NETWORK-SERVICES-MIB applTable might be populated as follows: The tables below illustrate how a system acting as both Proxy and
Registrar server might be configured to maintain separate SIP-
COMMON-MIB instances.
+-----------+-------------------+----------------------+ The NETWORK-SERVICES-MIB applTable might be populated as follows:
| applIndex | applName | applDescription |
+-----------+-------------------+----------------------+ +-----------+-------------------+----------------------+
| 1 | "sip_proxy10" | "ACME SIP Proxy" | | applIndex | applName | applDescription |
| 2 | "sip_registrar17" | "ACME SIP Registrar" | +-----------+-------------------+----------------------+
+-----------+-------------------+----------------------+ | 1 | "sip_proxy10" | "ACME SIP Proxy" |
| 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: The SIP-COMMON-MIB sipCommonCfgTable might be populated as:
+---------+------------------------+--------------------------+-----+ +---------+------------------------+--------------------------+-----+
| applInd | sipCommonCfgProtocolVe | sipCommonCfgServiceOperS | ... | |applIndex| sipCommonCfgProtocol | sipCommonCfgServiceOper | ... |
| e x | r sion | t atus | | | | Version | Status | |
+---------+------------------------+--------------------------+-----+ +---------+------------------------+--------------------------+-----+
| 1 | "SIP/2.0" | up(1) | | | 1 | "SIP/2.0" | up(1) | |
| 2 | "SIP/2.0" | restarting(4) | | | 2 | "SIP/2.0" | restarting(4) | |
+---------+------------------------+--------------------------+-----+ +---------+------------------------+--------------------------+-----+
while sipServerProxyCfgTable in SIP-SERVER-MIB might be populated as: while the sipServerProxyCfgTable in SIP-SERVER-MIB might be populated
as:
+-----------+-------------------------------+-----+ +-----------+-------------------------------+-----+
| applIndex | sipServerCfgProxyStatefulness | ... | | applIndex | sipServerCfgProxyStatefulness | ... |
+-----------+-------------------------------+-----+ +-----------+-------------------------------+-----+
| 1 | stateless(1) | | | 1 | stateless(1) | |
+-----------+-------------------------------+-----+ +-----------+-------------------------------+-----+
and sipServerRegUserTable in SIP-SERVER-MIB might be populated as: and the sipServerRegUserTable in SIP-SERVER-MIB might be populated
as:
+-----------+-----------------------+---------------------+-----+ +-----------+-----------------------+---------------------+-----+
| applIndex | sipServerRegUserIndex | sipServerRegUserUri | ... | | 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:
+-----------+------------------------+------------------------------+ +-----------+------------------------+------------------------------+
| applIndex | applName | applDescription | | applIndex | applName | applDescription |
+-----------+------------------------+------------------------------+ +-----------+------------------------+------------------------------+
| 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: The SIP-COMMON-MIB sipCommonCfgTable might be populated as:
+----------+--------------------------+-----------------------------+
| applInde | sipCommonCfgProtocolVers | sipCommonCfgServiceOperStat |
| x | i on | u s |
+----------+--------------------------+-----------------------------+
| 1 | "SIP/2.0" | up(1) |
+----------+--------------------------+-----------------------------+
while sipServerRegUserTable in SIP-SERVER-MIB might be populated as: +----------+---------------------------+-----------------------------+
|applIndex |sipCommonCfgProtocolVersion|sipCommonCfgServiceOperStatus|
+----------+---------------------------+-----------------------------+
| 1 | "SIP/2.0" | up(1) |
+----------+---------------------------+-----------------------------+
while the sipServerRegUserTable in SIP-SERVER-MIB might be populated
as:
+-----------+-----------------------+---------------------+-----+ +-----------+-----------------------+---------------------+-----+
| applIndex | sipServerRegUserIndex | sipServerRegUserUri | ... | | 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
sipCommonCfgServiceOperStatus is as follows: sipCommonCfgServiceOperStatus is as follows:
+-------------------------------+---------------+-------------------+ +-------------------------------+---------------+-------------------+
| sipCommonCfgServiceOperStatus | -- | applOperStatus | | sipCommonCfgServiceOperStatus | -- | applOperStatus |
| | corresponds | | | | corresponds | |
| | to --> | | | | 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],
[RFC2579] and [RFC2580]: INET-ADDRESS-MIB [RFC4001], NETWORK- [RFC2579], and [RFC2580]: INET-ADDRESS-MIB [RFC4001], NETWORK-
SERVICES-MIB [RFC2788], SNMP-FRAMEWORK-MIB [RFC3411]. SERVICES-MIB [RFC2788], SNMP-FRAMEWORK-MIB [RFC3411].
This MIB module also includes REFERENCE clauses that normatively This MIB module also includes REFERENCE clauses that normatively
refer to SIP [RFC3261], and INET-ADDRESS-MIB [RFC4001]. refer to SIP [RFC3261] and INET-ADDRESS-MIB [RFC4001].
Finally, this MIB module makes informative references to several RFCs Finally, this MIB module makes informative references to several RFCs
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 (SipTCMethodName 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.
Consideration section.
For example, the sipCommonMethodSupportedTable 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 an
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
sub-registries for SIP Methods and Response Codes under the 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 methods.
For example, in the sipCommonMethodSupportedTable of SIP-COMMON-MIB, For example, in the sipCommonMethodSupportedTable of SIP-COMMON-MIB,
the sipCommonMethodSupportedName values can be represented as the sipCommonMethodSupportedName values can be represented as
follows: follows:
+------------------------------+ +------------------------------+
| sipCommonMethodSupportedName | | 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-MIB DEFINITIONS ::= BEGIN SIP-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
mib-2 mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- RFC 2579 FROM SNMPv2-TC; -- RFC 2579
sipTC MODULE-IDENTITY sipTC MODULE-IDENTITY
LAST-UPDATED "200609121700Z" LAST-UPDATED "200704200000Z"
ORGANIZATION "IETF Session Initiation Protocol Working Group" ORGANIZATION "IETF Session Initiation Protocol Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 476 2029
Co-editor Joon Maeng Co-editor Joon Maeng
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule
CableLabs
postal: 858 Coal Creek Circle
Louisville, CO 80027
USA
email: jf.mule@cablelabs.com
phone: +1 303 661 9100
Co-editor Dave Walker Co-editor Jean-Francois Mule
email: drwalker@rogers.com" CableLabs
DESCRIPTION postal: 858 Coal Creek Circle
"Session Initiation Protocol (SIP) MIB Textual Conventions Louisville, CO 80027
module used by other SIP-related MIB Modules. USA
email: jf.mule@cablelabs.com
phone: +1 303 661 9100
Copyright (C) The Internet Society (2006). This version of Co-editor Dave Walker
this MIB module is part of RFC XXXX; see the RFC itself for email: drwalker@rogers.com"
full legal notices." DESCRIPTION
-- RFC Ed: replace XXXX with actual RFC number and remove this not "Session Initiation Protocol (SIP) MIB TEXTUAL-CONVENTION
REVISION "200609121700Z" module used by other SIP-related MIB Modules.
DESCRIPTION
"Initial version of the IETF SIP-TC-MIB module. This version
published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX1 }
-- RFC Ed: replace XXX1 with actual IANA assigned number for this
-- sipTC mib module and remove this note
-- Copyright (C) The IETF Trust (2007). This version of
-- Textual Conventions this MIB module is part of RFC 4780; see the RFC itself for
-- full legal notices."
REVISION "200704200000Z"
DESCRIPTION
"Initial version of the IETF SIP-TC-MIB module. This version
published as part of RFC 4780."
::= { mib-2 148 }
SipTCTransportProtocol ::= TEXTUAL-CONVENTION --
STATUS current -- Textual Conventions
DESCRIPTION --
"This convention is a bit map. Each bit represents a transport
protocol. If a bit has value 1, then that selected transport
protocol is in some way dependent on the context of the object
using this convention. If a bit has value 0, then that
transport protocol is not selected. Combinations of bits can
be set when multiple transport protocols are selected.
bit 0: a protocol other than those defined here SipTCTransportProtocol ::= TEXTUAL-CONVENTION
bit 1: User Datagram Protocol bit 2 : Transmission Control STATUS current
Protocol DESCRIPTION
bit 3: Stream Control Transmission Protocol "This convention is a bit map. Each bit represents a transport
bit 4: Transport Layer Security Protocol over TCP protocol. If a bit has value 1, then that selected transport
bit 5: Transport Layer Security Protocol over SCTP protocol is in some way dependent on the context of the object
" using this convention. If a bit has value 0, then that
transport protocol is not selected. Combinations of bits can
be set when multiple transport protocols are selected.
REFERENCE "RFC 3261, Section 18 and RFC 4168" bit 0: a protocol other than those defined here
SYNTAX BITS { bit 1: User Datagram Protocol
other(0), -- none of the following bit 2: Transmission Control Protocol
udp(1), bit 3: Stream Control Transmission Protocol
tcp(2), bit 4: Transport Layer Security Protocol over TCP
sctp(3), -- RFC4168 bit 5: Transport Layer Security Protocol over SCTP
tlsTcp(4), "
tlsSctp(5) -- RFC 4168 REFERENCE "RFC 3261, Section 18 and RFC 4168"
} SYNTAX BITS {
other(0), -- none of the following
udp(1),
tcp(2),
sctp(3), -- RFC4168
tlsTcp(4),
tlsSctp(5) -- RFC 4168
}
SipTCEntityRole ::= TEXTUAL-CONVENTION SipTCEntityRole ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention defines the role of a SIP entity. Examples of "This convention defines the role of a SIP entity. Examples of
SIP entities are proxies, user agents, redirect servers, SIP entities are proxies, user agents, redirect servers,
registrars or combinations of the above. registrars, or combinations of the above.
User Agent (UA): A logical entity that can act as both a user User Agent (UA): A logical entity that can act as both a user
agent client and user agent server. User Agent Client (UAC): agent client and user agent server.
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 User Agent Client (UAC): A logical entity that creates a new
a server and a client for the purpose of making requests on request, and then uses the client transaction state machinery
behalf of other clients. A proxy server primarily plays the to send it. The role of UAC lasts only for the duration of
role of routing, which means its job is to ensure that a that transaction. In other words, if a piece of software
request is sent to another entity 'closer' to the targeted initiates a request, it acts as a UAC for the duration of that
user. Proxies are also useful for enforcing policy. A proxy transaction. If it receives a request later, it assumes the
interprets, and, if necessary, rewrites specific parts of a role of a user agent server for the processing of that
request message before forwarding it. transaction.
Redirect Server: A redirect server is a user agent server that User Agent Server (UAS): A logical entity that generates a
generates 3xx responses to requests it receives, directing the response to a SIP request. The response accepts, rejects,
client to contact an alternate set of URIs. 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.
Registrar: A registrar is a server that accepts REGISTER Proxy, Proxy Server: An intermediary entity that acts as both
requests and places the information it receives in those a server and a client for the purpose of making requests on
requests into the location service for the domain it handles." behalf of other clients. A proxy server primarily plays the
REFERENCE role of routing, which means its job is to ensure that a
"RFC 3261, Section 6" request is sent to another entity 'closer' to the targeted
SYNTAX BITS { user. Proxies are also useful for enforcing policy. A proxy
other(0), interprets and, if necessary, rewrites specific parts of a
userAgent(1), request message before forwarding it.
proxyServer(2),
redirectServer(3),
registrarServer(4)
}
SipTCOptionTagHeaders ::= TEXTUAL-CONVENTION Redirect Server: A redirect server is a user agent server that
STATUS current generates 3xx responses to requests it receives, directing the
DESCRIPTION client to contact an alternate set of URIs.
"This convention defines the header fields that use the option
tags per section 19.2 of RFC 3261. These tags are used in
Require (Section 20.32), Proxy-Require (Section 20.29),
Supported (Section 20.37) and Unsupported (Section 20.40)
header fields."
REFERENCE
"RFC 3261, Sections 19.2, 20.32, 20.29, 20.37 and 20.40"
SYNTAX BITS {
require(0), -- Require header
proxyRequire(1), -- Proxy-Require header
supported(2), -- Supported header
unsupported(3) -- Unsupported header
}
SipTCMethodName ::= TEXTUAL-CONVENTION Registrar: A registrar is a server that accepts REGISTER
STATUS current requests and places the information it receives in those
DESCRIPTION requests into the location service for the domain it handles."
"This textual convention is a string that uniquely identifies a REFERENCE
SIP method. The scope of uniqueness is the context of all "RFC 3261, Section 6"
defined SIP methods. SYNTAX BITS {
other(0),
userAgent(1),
proxyServer(2),
redirectServer(3),
registrarServer(4)
}
Experimental support of extension methods is acceptable and SipTCOptionTagHeaders ::= TEXTUAL-CONVENTION
expected. Extension methods are those defined in STATUS current
Internet-Draft documents but not yet allocated an official DESCRIPTION
sanctioned by IANA. "This convention defines the header fields that use the option
tags per Section 19.2 of RFC 3261. These tags are used in
Require (Section 20.32), Proxy-Require (Section 20.29),
Supported (Section 20.37), and Unsupported (Section 20.40)
header fields."
REFERENCE
"RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40"
SYNTAX BITS {
require(0), -- Require header
proxyRequire(1), -- Proxy-Require header
supported(2), -- Supported header
unsupported(3) -- Unsupported header
}
To support experimental extension methods, any object using SipTCMethodName ::= TEXTUAL-CONVENTION
this textual convention as syntax MAY return/accept a method STATUS current
identifier value other than those sanctioned by IANA. That DESCRIPTION
system MUST ensure no collisions with officially assigned "This TEXTUAL-CONVENTION is a string that uniquely identifies a
method names." SIP method. The scope of uniqueness is the context of all
REFERENCE defined SIP methods.
"RFC 3261, Section 27.4"
SYNTAX OCTET STRING (SIZE (1..100)) Experimental support of extension methods is acceptable and
expected. Extension methods are those defined in
Internet-Draft documents but not yet allocated and
officially sanctioned by IANA.
END To support experimental extension methods, any object using
this TEXTUAL-CONVENTION as syntax MAY return/accept a method
identifier value other than those sanctioned by IANA. That
system MUST ensure no collisions with officially assigned
method names."
REFERENCE
"RFC 3261, Section 27.4"
SYNTAX OCTET STRING (SIZE (1..100))
END
7.2. SIP Common MIB Module 7.2. SIP Common MIB Module
SIP-COMMON-MIB DEFINITIONS ::= BEGIN SIP-COMMON-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
Counter32, Counter32,
Gauge32, Gauge32,
TimeTicks, TimeTicks,
Unsigned32, Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
RowStatus, RowStatus,
TimeStamp, 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
SipTCTransportProtocol, SipTCTransportProtocol,
SipTCMethodName, SipTCMethodName,
SipTCEntityRole, SipTCEntityRole,
SipTCOptionTagHeaders SipTCOptionTagHeaders
FROM SIP-TC-MIB FROM SIP-TC-MIB -- RFC 4780
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 "200609121700Z" LAST-UPDATED "200704200000Z"
ORGANIZATION "IETF Session Initiation Protocol Working Group" ORGANIZATION "IETF Session Initiation Protocol Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 476 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
Louisville, CO 80027
USA
email: jf.mule@cablelabs.com
phone: +1 303 661 9100
Co-editor Dave Walker postal: 858 Coal Creek Circle
email: drwalker@rogers.com" Louisville, CO 80027
DESCRIPTION USA
"Session Initiation Protocol (SIP) Common MIB module. This email: jf.mule@cablelabs.com
module defines objects which may be common to all SIP entities. phone: +1 303 661 9100
SIP is an application-layer signaling protocol for creating, Co-editor Dave Walker
modifying and terminating multimedia sessions with one or more email: drwalker@rogers.com"
participants. These sessions include Internet multimedia DESCRIPTION
conferences and Internet telephone calls. SIP is defined in "Session Initiation Protocol (SIP) Common MIB module. This
RFC 3261 (June 2002). module defines objects that may be common to all SIP entities.
This MIB is defined for managing objects which are common to SIP is an application-layer signaling protocol for creating,
SIP User Agents (UAs), Proxy, Redirect and Registrar servers. modifying and terminating multimedia sessions with one or more
Objects specific to each of these entities MAY be managed using participants. These sessions include Internet multimedia
entity specific MIBs defined in other modules. conferences and Internet telephone calls. SIP is defined in
RFC 3261 (June 2002).
Copyright (C) The Internet Society (2006). This version of This MIB is defined for managing objects that are common to
this MIB module is part of RFC XXXX; see the RFC itself for SIP User Agents (UAs), Proxy, Redirect, and Registrar servers.
full legal notices." Objects specific to each of these entities MAY be managed using
-- RFC Ed: replace XXXX with actual RFC number and entity specific MIBs defined in other modules.
-- remove this note
REVISION "200609121700Z"
DESCRIPTION
"Initial version of the IETF SIP-COMMON-MIB module. This
version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note Copyright (C) The IETF Trust (2007). This version of
::= { mib-2 XXX2 } this MIB module is part of RFC 4780; see the RFC itself for
-- RFC Ed: replace XXX2 with actual IANA assigned number and full legal notices."
-- remove this note REVISION "200704200000Z"
DESCRIPTION
"Initial version of the IETF SIP-COMMON-MIB module. This
version published as part of RFC 4780."
::= { mib-2 149 }
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipCommonMIBNotifications OBJECT IDENTIFIER ::= { sipCommonMIB 0 } sipCommonMIBNotifications OBJECT IDENTIFIER ::= { sipCommonMIB 0 }
sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 } sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
sipCommonMIBConformance 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 ::= { sipCommonMIBObjects 1 }
sipCommonCfgBase OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 }
-- Protocol timer configuration -- Protocol timer configuration
sipCommonCfgTimer OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 } sipCommonCfgTimer OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 }
-- SIP message summary statistics -- SIP message summary statistics
sipCommonSummaryStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 } sipCommonSummaryStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 }
-- Per method statistics -- Per method statistics
sipCommonMethodStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 } sipCommonMethodStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 }
-- Per Status code or status code class statistics -- Per Status code or status code class statistics
sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 } sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 }
-- Transaction statistics -- Transaction statistics
sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 } sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 }
-- Method retry statistics -- Method retry statistics
sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 } sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 }
-- Other statistics -- Other statistics
sipCommonOtherStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 } sipCommonOtherStats OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 }
-- Accessible-for-notify objects -- Accessible-for-notify objects
sipCommonNotifObjects OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 } sipCommonNotifObjects OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 }
-- --
-- Common Configuration Objects -- Common Configuration Objects
-- --
sipCommonCfgTable OBJECT-TYPE sipCommonCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgEntry SYNTAX SEQUENCE OF SipCommonCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the common configuration objects applicable "This table contains the common configuration objects 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 entity Each row represents objects for a particular SIP entity
instance present in this system. applIndex is used to uniquely instance present in this system. applIndex is used to uniquely
identify these instances of SIP entities and correlate them identify these instances of SIP entities and correlate them
through the common framework of the NETWORK-SERVICES-MIB (RFC through the common framework of the NETWORK-SERVICES-MIB (RFC
2788)." 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipCommonCfgTable 1 } ::= { sipCommonCfgTable 1 }
SipCommonCfgEntry ::= SEQUENCE { SipCommonCfgEntry ::= SEQUENCE {
sipCommonCfgProtocolVersion SnmpAdminString, sipCommonCfgProtocolVersion SnmpAdminString,
sipCommonCfgServiceOperStatus INTEGER, sipCommonCfgServiceOperStatus INTEGER,
sipCommonCfgServiceStartTime TimeTicks, sipCommonCfgServiceStartTime TimeTicks,
sipCommonCfgServiceLastChange TimeTicks, sipCommonCfgServiceLastChange TimeTicks,
sipCommonCfgOrganization SnmpAdminString, sipCommonCfgOrganization SnmpAdminString,
sipCommonCfgMaxTransactions Unsigned32, sipCommonCfgMaxTransactions Unsigned32,
sipCommonCfgServiceNotifEnable BITS, sipCommonCfgServiceNotifEnable BITS,
sipCommonCfgEntityType SipTCEntityRole sipCommonCfgEntityType SipTCEntityRole
} }
sipCommonCfgProtocolVersion 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 "This object will reflect the version of SIP supported by this
SIP entity. It will follow the same format as SIP version SIP entity. It will follow the same format as SIP version
information contained in the SIP messages generated by this SIP information contained in the SIP messages generated by this SIP
entity. For example, entities supporting SIP version 2 will entity. For example, entities supporting SIP version 2 will
return 'SIP/2.0' as dictated by the standard." return 'SIP/2.0' as dictated by the standard."
REFERENCE REFERENCE
"RFC 3261, Section 7.1" "RFC 3261, Section 7.1"
::= { sipCommonCfgEntry 1 } ::= { sipCommonCfgEntry 1 }
sipCommonCfgServiceOperStatus 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 is up : The application is operating normally and is
processing (receiving and possibly issuing) SIP processing (receiving and possibly issuing) SIP
requests and responses. requests and responses.
down : The application is currently unable to process down : The application is currently unable to process
SIP messages. SIP messages.
congested : The application is operational but no additional congested : The application is operational but no additional
inbound transactions can be accommodated at the inbound transactions can be accommodated at the
moment. moment.
restarting : The application is currently unavailable but it restarting : The application is currently unavailable, but it
is in the process of restarting and will, is in the process of restarting and will
presumably, soon be able to process SIP messages. 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 messages. and MAY not be able to process SIP messages.
The operational status values defined for this object are not The operational status values defined for this object are not
based on any specific information contained in the SIP based on any specific information contained in the SIP
standard." standard."
::= { sipCommonCfgEntry 2 } ::= { sipCommonCfgEntry 2 }
sipCommonCfgServiceStartTime 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 last "The value of sysUpTime at the time the SIP entity was last
started. If started prior to the last re-initialization of the started. If started prior to the last re-initialization of the
local network management subsystem, then this object contains a local network management subsystem, then this object contains a
zero value." zero value."
::= { sipCommonCfgEntry 3 } ::= { sipCommonCfgEntry 3 }
sipCommonCfgServiceLastChange OBJECT-TYPE sipCommonCfgServiceLastChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the SIP entity entered its "The value of sysUpTime at the time the SIP entity entered its
current operational state. If the current state was entered current operational state. If the current state was entered
prior to the last re-initialization of the local network prior to the last re-initialization of the local network
management subsystem, then this object contains a zero value." management subsystem, then this object contains a zero value."
::= { sipCommonCfgEntry 4 } ::= { sipCommonCfgEntry 4 }
sipCommonCfgOrganization 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 entity "This object contains the organization name that the SIP entity
inserts into Organization headers of SIP messages processed by inserts into Organization headers of SIP messages processed by
this system. If the string is empty, no Organization header is this system. If the string is empty, no Organization header is
to be generated." to be generated."
REFERENCE
"RFC 3261, Section 20.25"
::= { sipCommonCfgEntry 5 }
sipCommonCfgMaxTransactions OBJECT-TYPE REFERENCE
SYNTAX Unsigned32 (1..4294967295) "RFC 3261, Section 20.25"
MAX-ACCESS read-only ::= { sipCommonCfgEntry 5 }
STATUS current
DESCRIPTION
"This object indicates the maximum number of simultaneous
transactions per second that the SIP entity can manage. In
general, the value of this object SHOULD reflect a level of
transaction processing per second that is considered high
enough to impact the system's CPU and/or memory resources to
the point of deteriorating SIP call processing but not high
enough to cause catastrophic system failure."
::= { sipCommonCfgEntry 6 }
sipCommonCfgServiceNotifEnable OBJECT-TYPE sipCommonCfgMaxTransactions OBJECT-TYPE
SYNTAX BITS { SYNTAX Unsigned32 (1..4294967295)
sipCommonServiceColdStart(0), MAX-ACCESS read-only
sipCommonServiceWarmStart(1), STATUS current
sipCommonServiceStatusChanged(2) DESCRIPTION
} "This object indicates the maximum number of simultaneous
MAX-ACCESS read-write transactions per second that the SIP entity can manage. In
STATUS current general, the value of this object SHOULD reflect a level of
DESCRIPTION transaction processing per second that is considered high
"This object specifies which SIP service related notifications enough to impact the system's CPU and/or memory resources to
are enabled. Each bit represents a specific notification. If the point of deteriorating SIP call processing but not high
a bit has a value 1, the associated notification is enabled and enough to cause catastrophic system failure."
will be generated by the SIP entity at the appropriate time. ::= { sipCommonCfgEntry 6 }
Support for these notifications is OPTIONAL: either none or all sipCommonCfgServiceNotifEnable OBJECT-TYPE
notification values are supported. If an implementation does SYNTAX BITS {
not support this object, it should return a 'noSuchObject' sipCommonServiceColdStart(0),
exception to an SNMP GET operation. If notifications are sipCommonServiceWarmStart(1),
supported, this object's default value SHOULD reflect sipCommonServiceStatusChanged(2)
sipCommonServiceColdStart and sipCommonServiceWarmStart enabled }
and sipCommonServiceStatusChanged disabled. MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies which SIP service related notifications
are enabled. Each bit represents a specific notification. If
a bit has a value 1, the associated notification is enabled and
will be generated by the SIP entity at the appropriate time.
This object value SHOULD persist across reboots." Support for these notifications is OPTIONAL: either none or all
DEFVAL { { sipCommonServiceColdStart, notification values are supported. If an implementation does
sipCommonServiceWarmStart } } not support this object, it should return a 'noSuchObject'
::= { sipCommonCfgEntry 7 } exception to an SNMP GET operation. If notifications are
supported, this object's default value SHOULD reflect
sipCommonServiceColdStart and sipCommonServiceWarmStart enabled
and sipCommonServiceStatusChanged disabled.
sipCommonCfgEntityType OBJECT-TYPE This object value SHOULD persist across reboots."
SYNTAX SipTCEntityRole DEFVAL { { sipCommonServiceColdStart,
MAX-ACCESS read-only sipCommonServiceWarmStart } }
STATUS current ::= { sipCommonCfgEntry 7 }
DESCRIPTION
"This object identifies the list of SIP entities this row is
related to. It is defined as a bit map. Each bit represents a
type of SIP entity. If a bit has value 1, the SIP entity
represented by this row plays the role of this entity type. If
a bit has value 0, the SIP entity represented by this row does
not act as this entity type Combinations of bits can be set
when the SIP entity plays multiple SIP roles."
::= { sipCommonCfgEntry 8 }
-- sipCommonCfgEntityType OBJECT-TYPE
-- Support for multiple ports SYNTAX SipTCEntityRole
-- MAX-ACCESS read-only
sipCommonPortTable OBJECT-TYPE STATUS current
SYNTAX SEQUENCE OF SipCommonPortEntry DESCRIPTION
MAX-ACCESS not-accessible "This object identifies the list of SIP entities to which this
STATUS current row is related. It is defined as a bit map. Each bit
DESCRIPTION represents a type of SIP entity. If a bit has value 1, the
"This table contains the list of ports that each SIP entity in SIP entity represented by this row plays the role of this
this system is allowed to use. These ports can be advertised entity type. If a bit has value 0, the SIP entity represented
using the Contact header in a REGISTER request or response." by this row does not act as this entity type. Combinations
::= { sipCommonCfgBase 2 } of bits can be set when the SIP entity plays multiple SIP
roles."
::= { sipCommonCfgEntry 8 }
sipCommonPortEntry OBJECT-TYPE --
SYNTAX SipCommonPortEntry -- Support for multiple ports
MAX-ACCESS not-accessible --
STATUS current sipCommonPortTable OBJECT-TYPE
DESCRIPTION SYNTAX SEQUENCE OF SipCommonPortEntry
"Specification of a particular port. MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the list of ports that each SIP entity in
this system is allowed to use. These ports can be advertised
using the Contact header in a REGISTER request or response."
::= { sipCommonCfgBase 2 }
Each row represents those objects for a particular SIP entity sipCommonPortEntry OBJECT-TYPE
present in this system. applIndex is used to uniquely identify SYNTAX SipCommonPortEntry
these instances of SIP entities and correlate them through the MAX-ACCESS not-accessible
common framework of the NETWORK-SERVICES-MIB (RFC 2788)." STATUS current
INDEX { applIndex, sipCommonPort } DESCRIPTION
::= { sipCommonPortTable 1 } "Specification of a particular port.
SipCommonPortEntry ::= SEQUENCE { Each row represents those objects for a particular SIP entity
sipCommonPort InetPortNumber, present in this system. applIndex is used to uniquely identify
sipCommonPortTransportRcv SipTCTransportProtocol these instances of SIP entities and correlate them through
} the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipCommonPort }
::= { sipCommonPortTable 1 }
sipCommonPort OBJECT-TYPE SipCommonPortEntry ::= SEQUENCE {
SYNTAX InetPortNumber (1..65535) sipCommonPort InetPortNumber,
MAX-ACCESS not-accessible sipCommonPortTransportRcv SipTCTransportProtocol
STATUS current }
DESCRIPTION
"This object reflects a particular port that can be used by the
SIP application."
::= { sipCommonPortEntry 1 }
sipCommonPortTransportRcv OBJECT-TYPE sipCommonPort OBJECT-TYPE
SYNTAX SipTCTransportProtocol SYNTAX InetPortNumber (1..65535)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will specify the transport protocol the SIP entity "This object reflects a particular port that can be used by the
will use to receive SIP messages. SIP application."
::= { sipCommonPortEntry 1 }
This object is a bit map. Each bit represents a transport sipCommonPortTransportRcv OBJECT-TYPE
protocol. If a bit has value 1, then that transport protocol SYNTAX SipTCTransportProtocol
is currently being used. If a bit has value 0, then that MAX-ACCESS read-only
transport protocol is currently not being used." STATUS current
::= { sipCommonPortEntry 2 } DESCRIPTION
"This object will specify the transport protocol the SIP entity
will use to receive SIP messages.
-- This object is a bit map. Each bit represents a transport
-- Support for SIP option tags (SIP extensions). protocol. If a bit has value 1, then that transport protocol
-- SIP extensions MAY be supported or required by SIP entities. is currently being used. If a bit has value 0, then that
-- transport protocol is currently not being used."
::= { sipCommonPortEntry 2 }
sipCommonOptionTagTable OBJECT-TYPE --
SYNTAX SEQUENCE OF SipCommonOptionTagEntry -- Support for SIP option tags (SIP extensions).
MAX-ACCESS not-accessible -- SIP extensions MAY be supported or required by SIP entities.
STATUS current --
DESCRIPTION
"This table contains a list of the SIP option tags (SIP
extensions) that either required, supported, or unsupported by
the SIP entity. These option tags are used in the Require,
Proxy-Require, Supported and Unsupported header fields.
Example: if a user agent client supports and requires the sipCommonOptionTagTable OBJECT-TYPE
server to support reliability of provisional responses (IETF SYNTAX SEQUENCE OF SipCommonOptionTagEntry
RFC 3262), this table contains a row with the option tag string MAX-ACCESS not-accessible
'100rel' in sipCommonOptionTag and the OCTET STRING value of STATUS current
'1010 0000' or '0xA0' in sipCommonOptionTagHeaderField. DESCRIPTION
"This table contains a list of the SIP option tags (SIP
extensions) that are either required, supported, or
unsupported by the SIP entity. These option tags are
used in the Require, Proxy-Require, Supported, and
Unsupported header fields.
If a server does not support the required feature (indicated in Example: If a user agent client supports, and requires the
a Require header to a UAS, or in a Proxy-Require to a Proxy server to support, reliability of provisional responses
Server), the server returns a 420 Bad Extension listing the (RFC 3262), this table contains a row with the option tag string
feature in an Unsupported header. '100rel' in sipCommonOptionTag and the OCTET STRING value of
'1010 0000' or '0xA0' in sipCommonOptionTagHeaderField.
Normally the list of such features supported by an entity is If a server does not support the required feature (indicated in
static (i.e. will not change over time)." a Require header to a UAS, or in a Proxy-Require to a Proxy
REFERENCE Server), the server returns a 420 Bad Extension listing the
"RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40" feature in an Unsupported header.
::= { sipCommonCfgBase 3 }
sipCommonOptionTagEntry OBJECT-TYPE Normally, the list of such features supported by an entity is
SYNTAX SipCommonOptionTagEntry static (i.e., will not change over time)."
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A particular SIP option tag (extension) supported or
unsupported by the SIP entity, and which may be supported or
required by a peer.
Each row represents those objects for a particular SIP entity REFERENCE
present in this system. applIndex is used to uniquely identify "RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40"
these instances of SIP entities and correlate them through the ::= { sipCommonCfgBase 3 }
common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipCommonOptionTagIndex }
::= { sipCommonOptionTagTable 1 }
SipCommonOptionTagEntry ::= SEQUENCE { sipCommonOptionTagEntry OBJECT-TYPE
sipCommonOptionTagIndex Unsigned32, SYNTAX SipCommonOptionTagEntry
sipCommonOptionTag SnmpAdminString, MAX-ACCESS not-accessible
sipCommonOptionTagHeaderField SipTCOptionTagHeaders STATUS current
} DESCRIPTION
"A particular SIP option tag (extension) supported or
unsupported by the SIP entity, and which may be supported or
required by a peer.
sipCommonOptionTagIndex OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX Unsigned32 (1..4294967295) present in this system. applIndex is used to uniquely identify
MAX-ACCESS not-accessible these instances of SIP entities and correlate them through the
STATUS current common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION INDEX { applIndex, sipCommonOptionTagIndex }
"This object uniquely identifies a conceptual row in the table." ::= { sipCommonOptionTagTable 1 }
::= { sipCommonOptionTagEntry 1 }
sipCommonOptionTag OBJECT-TYPE SipCommonOptionTagEntry ::= SEQUENCE {
SYNTAX SnmpAdminString sipCommonOptionTagIndex Unsigned32,
MAX-ACCESS read-only sipCommonOptionTag SnmpAdminString,
STATUS current sipCommonOptionTagHeaderField SipTCOptionTagHeaders
DESCRIPTION }
"This object indicates the SIP option tag. The option tag names
are registered with IANA and available at http://www.iana.org."
REFERENCE "RFC 3261, Section 27.1"
::= { sipCommonOptionTagEntry 2 }
sipCommonOptionTagHeaderField OBJECT-TYPE sipCommonOptionTagIndex OBJECT-TYPE
SYNTAX SipTCOptionTagHeaders SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the SIP option tag is supported "This object uniquely identifies a conceptual row in the table."
(Supported header), unsupported (Unsupported header), required ::= { sipCommonOptionTagEntry 1 }
(Require or Proxy-Require header) by the SIP entity. A SIP
option tag may be both supported and required."
::= { sipCommonOptionTagEntry 3 }
-- sipCommonOptionTag OBJECT-TYPE
-- Supported SIP Methods SYNTAX SnmpAdminString
-- MAX-ACCESS read-only
sipCommonMethodSupportedTable OBJECT-TYPE STATUS current
SYNTAX SEQUENCE OF SipCommonMethodSupportedEntry DESCRIPTION
MAX-ACCESS not-accessible "This object indicates the SIP option tag. The option tag names
STATUS current are registered with IANA and available at http://www.iana.org."
DESCRIPTION REFERENCE "RFC 3261, Section 27.1"
"This table contains a list of methods supported by each SIP ::= { sipCommonOptionTagEntry 2 }
entity in this system (see the standard set of SIP methods in
Section 7.1 of RFC 3261). Any additional methods that may be
incorporated into the SIP protocol can be represented by this
table without any requirement to update this MIB module.
The table is informational in nature; conveying to the NMS sipCommonOptionTagHeaderField OBJECT-TYPE
capabilities of the managed system. SYNTAX SipTCOptionTagHeaders
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether the SIP option tag is supported
(Supported header), unsupported (Unsupported header), or
required (Require or Proxy-Require header) by the SIP entity.
A SIP option tag may be both supported and required."
::= { sipCommonOptionTagEntry 3 }
From a protocol point of view, the list of methods advertised --
by the SIP entity in the Allow header (Section 20.5 of RFC -- Supported SIP Methods
3261) MUST be consistent with the methods reflected in this --
table." sipCommonMethodSupportedTable OBJECT-TYPE
::= { sipCommonCfgBase 4 } SYNTAX SEQUENCE OF SipCommonMethodSupportedEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains a list of methods supported by each SIP
entity in this system (see the standard set of SIP methods in
Section 7.1 of RFC 3261). Any additional methods that may be
incorporated into the SIP protocol can be represented by this
table without any requirement to update this MIB module.
sipCommonMethodSupportedEntry OBJECT-TYPE The table is informational in nature and conveys capabilities
SYNTAX SipCommonMethodSupportedEntry of the managed system to the SNMP Manager.
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A particular method supported by the SIP entity.
Each row represents those objects for a particular SIP entity From a protocol point of view, the list of methods advertised
present in this system. applIndex is used to uniquely identify by the SIP entity in the Allow header (Section 20.5 of RFC
these instances of SIP entities and correlate them through the 3261) MUST be consistent with the methods reflected in this
common framework of the NETWORK-SERVICES-MIB (RFC 2788)." table."
INDEX { applIndex, sipCommonMethodSupportedIndex } ::= { sipCommonCfgBase 4 }
::= { sipCommonMethodSupportedTable 1 }
SipCommonMethodSupportedEntry ::= SEQUENCE { sipCommonMethodSupportedEntry OBJECT-TYPE
sipCommonMethodSupportedIndex Unsigned32, SYNTAX SipCommonMethodSupportedEntry
sipCommonMethodSupportedName SipTCMethodName MAX-ACCESS not-accessible
} STATUS current
DESCRIPTION
"A particular method supported by the SIP entity.
sipCommonMethodSupportedIndex OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX Unsigned32 (1..4294967295) present in this system. applIndex is used to uniquely identify
MAX-ACCESS not-accessible these instances of SIP entities and correlate them through
STATUS current the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION INDEX { applIndex, sipCommonMethodSupportedIndex }
"This object uniquely identifies a conceptual row in the table ::= { sipCommonMethodSupportedTable 1 }
and reflects an assigned number used to identifier a specific
SIP method.
This identifier is suitable for referencing the associated SipCommonMethodSupportedEntry ::= SEQUENCE {
method throughout this and other MIBs supported by this managed sipCommonMethodSupportedIndex Unsigned32,
system." sipCommonMethodSupportedName SipTCMethodName
::= { sipCommonMethodSupportedEntry 1 } }
sipCommonMethodSupportedName OBJECT-TYPE sipCommonMethodSupportedIndex OBJECT-TYPE
SYNTAX SipTCMethodName SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the supported method's name. The method "This object uniquely identifies a conceptual row in the table
name MUST be all upper case (e.g, 'INVITE')." and reflects an assigned number used to identify a specific
::= { sipCommonMethodSupportedEntry 2 } SIP method.
-- This identifier is suitable for referencing the associated
-- SIP Timer Configuration method throughout this and other MIBs supported by this managed
-- system."
sipCommonCfgTimerTable OBJECT-TYPE ::= { sipCommonMethodSupportedEntry 1 }
SYNTAX SEQUENCE OF SipCommonCfgTimerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains timer configuration objects applicable to
SIP user agent and SIP stateful Proxy Server entities."
::= { sipCommonCfgTimer 1 }
sipCommonCfgTimerEntry OBJECT-TYPE sipCommonMethodSupportedName OBJECT-TYPE
SYNTAX SipCommonCfgTimerEntry SYNTAX SipTCMethodName
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of timer configuration. "This object reflects the supported method's name. The method
name MUST be all upper case (e.g., 'INVITE')."
::= { sipCommonMethodSupportedEntry 2 }
Each row represents those objects for a particular SIP entity --
present in this system. applIndex is used to uniquely identify -- SIP Timer Configuration
these instances of SIP entities and correlate them through the --
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The sipCommonCfgTimerTable OBJECT-TYPE
objects in this table entry SHOULD be non-volatile and their SYNTAX SEQUENCE OF SipCommonCfgTimerEntry
value SHOULD be kept at reboot." MAX-ACCESS not-accessible
INDEX { applIndex } STATUS current
::= { sipCommonCfgTimerTable 1 } DESCRIPTION
"This table contains timer configuration objects applicable to
SIP user agent and SIP stateful Proxy Server entities."
::= { sipCommonCfgTimer 1 }
SipCommonCfgTimerEntry ::= SEQUENCE { sipCommonCfgTimerEntry OBJECT-TYPE
sipCommonCfgTimerA Unsigned32, SYNTAX SipCommonCfgTimerEntry
sipCommonCfgTimerB Unsigned32, MAX-ACCESS not-accessible
sipCommonCfgTimerC Unsigned32, STATUS current
sipCommonCfgTimerD Unsigned32, DESCRIPTION
sipCommonCfgTimerE Unsigned32, "A row of timer configuration.
sipCommonCfgTimerF Unsigned32,
sipCommonCfgTimerG Unsigned32,
sipCommonCfgTimerH Unsigned32,
sipCommonCfgTimerI Unsigned32,
sipCommonCfgTimerJ Unsigned32,
sipCommonCfgTimerK Unsigned32,
sipCommonCfgTimerT1 Unsigned32,
sipCommonCfgTimerT2 Unsigned32,
sipCommonCfgTimerT4 Unsigned32
}
sipCommonCfgTimerA OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX Unsigned32 (100..1000) present in this system. applIndex is used to uniquely identify
UNITS "milliseconds" these instances of SIP entities and correlate them through
MAX-ACCESS read-only the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
STATUS current The objects in this table entry SHOULD be non-volatile and
DESCRIPTION their value SHOULD be kept at reboot."
"This object reflects the initial value for the retransmit timer
for the INVITE method. The retransmit timer doubles after each
retransmission, ensuring an exponential backoff in network
traffic. This object represents the initial time a SIP entity
will wait to receive a provisional response to an INVITE before
resending the INVITE request."
REFERENCE
"RFC 3261, Section 17.1.1.2"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 1 }
sipCommonCfgTimerB OBJECT-TYPE INDEX { applIndex }
SYNTAX Unsigned32 (32000..300000) ::= { sipCommonCfgTimerTable 1 }
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP entity will wait to
receive a final response to an INVITE. The timer is started
upon transmission of the initial INVITE request."
REFERENCE
"RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 2 }
sipCommonCfgTimerC OBJECT-TYPE SipCommonCfgTimerEntry ::= SEQUENCE {
SYNTAX Unsigned32 (180000..300000) sipCommonCfgTimerA Unsigned32,
UNITS "milliseconds" sipCommonCfgTimerB Unsigned32,
MAX-ACCESS read-only sipCommonCfgTimerC Unsigned32,
STATUS current sipCommonCfgTimerD Unsigned32,
DESCRIPTION sipCommonCfgTimerE Unsigned32,
"This object reflects the maximum time a SIP Proxy Server will sipCommonCfgTimerF Unsigned32,
wait to receive a provisional response to an INVITE. The Timer sipCommonCfgTimerG Unsigned32,
C MUST be set for each client transaction when an INVITE sipCommonCfgTimerH Unsigned32,
request is proxied." sipCommonCfgTimerI Unsigned32,
REFERENCE sipCommonCfgTimerJ Unsigned32,
"RFC 3261, Section 16.6" sipCommonCfgTimerK Unsigned32,
DEFVAL { 180000 } sipCommonCfgTimerT1 Unsigned32,
::= { sipCommonCfgTimerEntry 3 } sipCommonCfgTimerT2 Unsigned32,
sipCommonCfgTimerT4 Unsigned32
}
sipCommonCfgTimerD OBJECT-TYPE sipCommonCfgTimerA OBJECT-TYPE
SYNTAX Unsigned32 (0..300000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the amount of time that the server "This object reflects the initial value for the retransmit timer
transaction can remain in the 'Completed' state when unreliable for the INVITE method. The retransmit timer doubles after each
transports are used. The default value MUST be equal or greater retransmission, ensuring an exponential backoff in network
than 32000 for UDP transport and its value MUST be 0 for traffic. This object represents the initial time a SIP entity
TCP/SCTP transport." will wait to receive a provisional response to an INVITE before
resending the INVITE request."
REFERENCE
"RFC 3261, Section 17.1.1.2"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 1 }
REFERENCE sipCommonCfgTimerB OBJECT-TYPE
"RFC 3261, Section 17.1.1.2" SYNTAX Unsigned32 (32000..300000)
DEFVAL { 32000 } UNITS "milliseconds"
::= { sipCommonCfgTimerEntry 4 } MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP entity will wait to
receive a final response to an INVITE. The timer is started
upon transmission of the initial INVITE request."
REFERENCE
"RFC 3261, Section 17.1.1.2"
sipCommonCfgTimerE OBJECT-TYPE DEFVAL { 32000 }
SYNTAX Unsigned32 (100..1000) ::= { sipCommonCfgTimerEntry 2 }
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the initial value for the retransmit timer
for a non-INVITE method while in 'Trying State'. The
retransmit timer doubles after each retransmission until it
reaches T2 to ensure an exponential backoff in network traffic.
This object represents the initial time a SIP entity will wait
to receive a provisional response to the request before
resending the non-INVITE request."
REFERENCE
"RFC 3261, Section 17.1.2.2"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 5 }
sipCommonCfgTimerF OBJECT-TYPE sipCommonCfgTimerC OBJECT-TYPE
SYNTAX Unsigned32 (32000..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 entity will wait to "This object reflects the maximum time a SIP Proxy Server will
receive a final response to a non-INVITE request. The timer is wait to receive a provisional response to an INVITE. The Timer
started upon transmission of the initial request." C MUST be set for each client transaction when an INVITE
REFERENCE request is proxied."
"RFC 3261, Section 17.1.2.2" REFERENCE
DEFVAL { 32000 } "RFC 3261, Section 16.6"
DEFVAL { 180000 }
::= { sipCommonCfgTimerEntry 3 }
::= { sipCommonCfgTimerEntry 6 } sipCommonCfgTimerD OBJECT-TYPE
SYNTAX Unsigned32 (0..300000)
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the amount of time that the server
transaction can remain in the 'Completed' state when unreliable
transports are used. The default value MUST be equal to or
greater than 32000 for UDP transport, and its value MUST be 0
for TCP/SCTP transport."
REFERENCE
"RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 4 }
sipCommonCfgTimerG OBJECT-TYPE sipCommonCfgTimerE OBJECT-TYPE
SYNTAX Unsigned32 (0..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 timer "This object reflects the initial value for the retransmit timer
for final responses to INVITE requests. If timer G fires, the for a non-INVITE method while in 'Trying' state. The
response is passed to the transport layer once more for retransmit timer doubles after each retransmission until it
retransmission, and timer G is set to fire in MIN(2*T1, T2) reaches T2 to ensure an exponential backoff in network traffic.
seconds. From then on, when timer G fires, the response is This object represents the initial time a SIP entity will wait
passed to the transport again for transmission, and timer G is to receive a provisional response to the request before
reset with a value that doubles, unless that value exceeds T2, resending the non-INVITE request."
in which case it is reset with the value of T2. The default REFERENCE
value MUST be T1 for UDP transport and its value MUST be 0 for "RFC 3261, Section 17.1.2.2"
reliable transport like TCP/SCTP." DEFVAL { 500 }
REFERENCE ::= { sipCommonCfgTimerEntry 5 }
"RFC 3261, Section 17.2.1"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 7 }
sipCommonCfgTimerH 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 server will wait to "This object reflects the maximum time a SIP entity will wait to
receive an ACK before it abandons retransmitting the response. receive a final response to a non-INVITE request. The timer is
The timer is started upon entering the 'Completed' state." started upon transmission of the initial request."
REFERENCE REFERENCE
"RFC 3261, Section 17.2.1" "RFC 3261, Section 17.1.2.2"
DEFVAL { 32000 } DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 8 }
sipCommonCfgTimerI OBJECT-TYPE ::= { sipCommonCfgTimerEntry 6 }
SYNTAX Unsigned32 (0..10000)
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP entity will wait to
receive additional ACK message retransmissions.
The timer is started upon entering the 'Confirmed' state. The sipCommonCfgTimerG OBJECT-TYPE
default value MUST be T4 for UDP transport and its value MUST SYNTAX Unsigned32 (0..1000)
be 0 for reliable transport like TCP/SCTP." UNITS "milliseconds"
REFERENCE MAX-ACCESS read-only
"RFC 3261, Section 17.2.1" STATUS current
DEFVAL { 5000 } DESCRIPTION
::= { sipCommonCfgTimerEntry 9 } "This object reflects the initial value for the retransmit timer
for final responses to INVITE requests. If timer G fires, the
response is passed to the transport layer again for
retransmission, and timer G is set to fire in MIN(2*T1, T2)
seconds. From then on, when timer G fires, the response is
passed to the transport again for transmission, and timer G is
reset with a value that doubles, unless that value exceeds T2,
in which case, it is reset with the value of T2. The default
value MUST be T1 for UDP transport, and its value MUST be 0 for
reliable transport like TCP/SCTP."
REFERENCE
"RFC 3261, Section 17.2.1"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 7 }
sipCommonCfgTimerJ 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 SIP server will wait to "This object reflects the maximum time a server will wait to
receive retransmissions of non-INVITE request. The timer is receive an ACK before it abandons retransmitting the response.
started upon entering the 'Completed' state for non-INVITE
transactions. When timer J fires, the server MUST transition to
the 'Terminated' state."
REFERENCE
"RFC 3261, Section 17.2.2"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 10 }
sipCommonCfgTimerK OBJECT-TYPE The timer is started upon entering the 'Completed' state."
SYNTAX Unsigned32 (0..10000) REFERENCE
UNITS "milliseconds" "RFC 3261, Section 17.2.1"
MAX-ACCESS read-only DEFVAL { 32000 }
STATUS current ::= { sipCommonCfgTimerEntry 8 }
DESCRIPTION
"This object reflects the maximum time a SIP client will wait to
receive retransmissions of responses to non-INVITE requests.
The timer is started upon entering the 'Completed' state for
non-INVITE transactions. When timer K fires, the server MUST
transition to the 'Terminated' state. The default value MUST
be T4 for UDP transport and its value MUST be 0 for reliable
transport like TCP/SCTP."
REFERENCE
"RFC 3261, Section 17.1.2.2"
DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 11 }
sipCommonCfgTimerT1 OBJECT-TYPE sipCommonCfgTimerI OBJECT-TYPE
SYNTAX Unsigned32 (200..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 T1 timer for a SIP entity. T1 is an "This object reflects the maximum time a SIP entity will wait to
estimate of the round-trip time (RTT) between the client and receive additional ACK message retransmissions.
server transactions."
REFERENCE
"RFC 3261, Section 17"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 12 }
sipCommonCfgTimerT2 OBJECT-TYPE The timer is started upon entering the 'Confirmed' state. The
SYNTAX Unsigned32 (200..10000) default value MUST be T4 for UDP transport and its value MUST
UNITS "milliseconds" be 0 for reliable transport like TCP/SCTP."
MAX-ACCESS read-only REFERENCE
STATUS current "RFC 3261, Section 17.2.1"
DESCRIPTION DEFVAL { 5000 }
"This object reflects the T2 timer for a SIP entity. T2 is the ::= { sipCommonCfgTimerEntry 9 }
maximum retransmit interval for non-INVITE requests and INVITE
responses. It's used in various parts of the protocol to reset
other Timer* objects to this value."
REFERENCE
"RFC 3261, Section 17"
DEFVAL { 4000 }
::= { sipCommonCfgTimerEntry 13 }
sipCommonCfgTimerT4 OBJECT-TYPE sipCommonCfgTimerJ OBJECT-TYPE
SYNTAX Unsigned32 (200..10000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the T4 timer for a SIP entity. T4 is the "This object reflects the maximum time a SIP server will wait to
maximum duration a message will remain in the network. It receive retransmissions of non-INVITE requests. The timer is
represents the amount of time the network will take to clear started upon entering the 'Completed' state for non-INVITE
messages between client and server transactions. It's used in transactions. When timer J fires, the server MUST transition to
various parts of the protocol to reset other Timer* objects to the 'Terminated' state."
this value." REFERENCE
REFERENCE "RFC 3261, Section 17.2.2"
"RFC 3261, Section 17" DEFVAL { 32000 }
DEFVAL { 5000 } ::= { sipCommonCfgTimerEntry 10 }
::= { sipCommonCfgTimerEntry 14 }
-- sipCommonCfgTimerK OBJECT-TYPE
-- Common Statistics Objects SYNTAX Unsigned32 (0..10000)
-- UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP client will wait to
receive retransmissions of responses to non-INVITE requests.
The timer is started upon entering the 'Completed' state for
non-INVITE transactions. When timer K fires, the server MUST
transition to the 'Terminated' state. The default value MUST
be T4 for UDP transport, and its value MUST be 0 for reliable
transport like TCP/SCTP."
REFERENCE
"RFC 3261, Section 17.1.2.2"
DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 11 }
-- sipCommonCfgTimerT1 OBJECT-TYPE
-- Summary Statistics SYNTAX Unsigned32 (200..10000)
-- UNITS "milliseconds"
sipCommonSummaryStatsTable OBJECT-TYPE MAX-ACCESS read-only
SYNTAX SEQUENCE OF SipCommonSummaryStatsEntry STATUS current
MAX-ACCESS not-accessible DESCRIPTION
STATUS current "This object reflects the T1 timer for a SIP entity. T1 is an
DESCRIPTION estimate of the round-trip time (RTT) between the client and
"This table contains the summary statistics objects applicable server transactions."
to all SIP entities. Each row represents those objects for a REFERENCE
particular SIP entity present in this system." "RFC 3261, Section 17"
::= { sipCommonSummaryStats 1 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 12 }
sipCommonSummaryStatsEntry OBJECT-TYPE sipCommonCfgTimerT2 OBJECT-TYPE
SYNTAX SipCommonSummaryStatsEntry SYNTAX Unsigned32 (200..10000)
MAX-ACCESS not-accessible UNITS "milliseconds"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"A row of summary statistics. DESCRIPTION
"This object reflects the T2 timer for a SIP entity. T2 is the
maximum retransmit interval for non-INVITE requests and INVITE
responses. It's used in various parts of the protocol to reset
other Timer* objects to this value."
REFERENCE
"RFC 3261, Section 17"
DEFVAL { 4000 }
::= { sipCommonCfgTimerEntry 13 }
Each row represents those objects for a particular SIP entity sipCommonCfgTimerT4 OBJECT-TYPE
present in this system. applIndex is used to uniquely identify SYNTAX Unsigned32 (200..10000)
these instances of SIP entities and correlate them through the UNITS "milliseconds"
common framework of the NETWORK-SERVICES-MIB (RFC 2788)." MAX-ACCESS read-only
INDEX { applIndex } STATUS current
::= { sipCommonSummaryStatsTable 1 } DESCRIPTION
"This object reflects the T4 timer for a SIP entity. T4 is the
maximum duration a message will remain in the network. It
represents the amount of time the network will take to clear
messages between client and server transactions. It's used in
various parts of the protocol to reset other Timer* objects to
this value."
REFERENCE
"RFC 3261, Section 17"
DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 14 }
SipCommonSummaryStatsEntry ::= SEQUENCE { --
sipCommonSummaryInRequests Counter32, -- Common Statistics Objects
sipCommonSummaryOutRequests Counter32, --
sipCommonSummaryInResponses Counter32,
sipCommonSummaryOutResponses Counter32,
sipCommonSummaryTotalTransactions Counter32,
sipCommonSummaryDisconTime TimeStamp
}
sipCommonSummaryInRequests OBJECT-TYPE --
SYNTAX Counter32 -- Summary Statistics
MAX-ACCESS read-only --
STATUS current sipCommonSummaryStatsTable OBJECT-TYPE
DESCRIPTION SYNTAX SEQUENCE OF SipCommonSummaryStatsEntry
"This object indicates the total number of SIP request messages MAX-ACCESS not-accessible
received by the SIP entity including retransmissions. STATUS current
DESCRIPTION
"This table contains the summary statistics objects applicable
to all SIP entities. Each row represents those objects for a
particular SIP entity present in this system."
::= { sipCommonSummaryStats 1 }
Discontinuities in the value of this counter can occur at sipCommonSummaryStatsEntry OBJECT-TYPE
re-initialization of the SIP entity or service. A Management SYNTAX SipCommonSummaryStatsEntry
Station can detect discontinuities in this counter by MAX-ACCESS not-accessible
monitoring the sipCommonSummaryDisconTime object in the same STATUS current
row." DESCRIPTION
::= { sipCommonSummaryStatsEntry 1 } "A row of summary statistics.
sipCommonSummaryOutRequests OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX Counter32 present in this system. applIndex is used to uniquely identify
MAX-ACCESS read-only these instances of SIP entities and correlate them through
STATUS current the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION INDEX { applIndex }
"This object contains the total number of SIP request messages ::= { sipCommonSummaryStatsTable 1 }
sent out (originated and relayed) by the SIP entity. Where a
particular message is sent more than once, for example as a
retransmission, or as a result of forking, each transmission is
counted separately.
Discontinuities in the value of this counter can occur at SipCommonSummaryStatsEntry ::= SEQUENCE {
re-initialization of the SIP entity or service. A Management sipCommonSummaryInRequests Counter32,
Station can detect discontinuities in this counter by sipCommonSummaryOutRequests Counter32,
monitoring the sipCommonSummaryDisconTime object in the same sipCommonSummaryInResponses Counter32,
row." sipCommonSummaryOutResponses Counter32,
::= { sipCommonSummaryStatsEntry 2 } sipCommonSummaryTotalTransactions Counter32,
sipCommonSummaryDisconTime TimeStamp
}
sipCommonSummaryInResponses 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 contains the total number of SIP response messages "This object indicates the total number of SIP request messages
received by the SIP entity including retransmissions. received by the SIP entity, including retransmissions.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same monitoring the sipCommonSummaryDisconTime object in the same
row." row."
::= { sipCommonSummaryStatsEntry 3 } ::= { sipCommonSummaryStatsEntry 1 }
sipCommonSummaryOutResponses OBJECT-TYPE sipCommonSummaryOutRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the total number of SIP response messages "This object contains the total number of SIP request messages
sent (originated and relayed) by the SIP entity including sent out (originated and relayed) by the SIP entity. Where a
retransmissions. particular message is sent more than once, for example as a
retransmission or as a result of forking, each transmission is
counted separately.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same monitoring the sipCommonSummaryDisconTime object in the same
row." row."
::= { sipCommonSummaryStatsEntry 4 } ::= { sipCommonSummaryStatsEntry 2 }
sipCommonSummaryTotalTransactions OBJECT-TYPE sipCommonSummaryInResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of transactions that "This object contains the total number of SIP response messages
are in progress and transactions that have reached the received by the SIP entity, including retransmissions.
terminated state. It is not applicable to stateless SIP Proxy
Servers.
A SIP transaction occurs between a client and a server and Discontinuities in the value of this counter can occur at
comprises all messages from the first request sent from the re-initialization of the SIP entity or service. A Management
client to the server up to a final (non-1xx) response sent from Station can detect discontinuities in this counter by
the server to the client. monitoring the sipCommonSummaryDisconTime object in the same
row."
::= { sipCommonSummaryStatsEntry 3 }
If the request is INVITE and the final response is a non-2xx, sipCommonSummaryOutResponses OBJECT-TYPE
the transaction also include an ACK to the response. The ACK SYNTAX Counter32
for a 2xx response to an INVITE request is a separate MAX-ACCESS read-only
transaction. STATUS current
DESCRIPTION
"This object contains the total number of SIP response messages
sent (originated and relayed) by the SIP entity including
retransmissions.
The branch ID parameter in the Via header field values serves Discontinuities in the value of this counter can occur at
as a transaction identifier. 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 }
A transaction is identified by the CSeq sequence number within sipCommonSummaryTotalTransactions OBJECT-TYPE
a single call leg. The ACK request has the same CSeq number as SYNTAX Counter32
the corresponding INVITE request, but comprises a transaction MAX-ACCESS read-only
of its own. STATUS current
DESCRIPTION
"This object contains a count of the number of transactions that
are in progress and transactions that have reached the
'Terminated' state. It is not applicable to stateless SIP Proxy
Servers.
In the case of a forked request, each branch counts as a single A SIP transaction occurs between a client and a server, and
transaction. comprises all messages from the first request sent from the
client to the server, up to a final (non-1xx) response sent
from the server to the client.
For a transaction stateless Proxy Server, this counter is If the request is INVITE and the final response is a non-2xx,
always 0. the transaction also include an ACK to the response. The ACK
for a 2xx response to an INVITE request is a separate
transaction.
Discontinuities in the value of this counter can occur at The branch ID parameter in the Via header field values serves
re-initialization of the SIP entity or service. A Management as a transaction identifier.
Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same
row."
::= { sipCommonSummaryStatsEntry 5 }
sipCommonSummaryDisconTime OBJECT-TYPE A transaction is identified by the CSeq sequence number within
SYNTAX TimeStamp a single call leg. The ACK request has the same CSeq number as
MAX-ACCESS read-only the corresponding INVITE request, but comprises a transaction
STATUS current of its own.
DESCRIPTION
"The value of the sysUpTime object when the counters for the
summary statistics objects in this row last experienced a
discontinuity."
::= { sipCommonSummaryStatsEntry 6 }
-- In the case of a forked request, each branch counts as a single
-- SIP Method Statistics transaction.
-- Total counts for each SIP method.
--
sipCommonMethodStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonMethodStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the method statistics objects for SIP
entities. Each row represents those objects for a particular
SIP entity present in this system."
::= { sipCommonMethodStats 1 } For a transaction stateless Proxy Server, this counter is
always 0.
sipCommonMethodStatsEntry OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX SipCommonMethodStatsEntry re-initialization of the SIP entity or service. A Management
MAX-ACCESS not-accessible Station can detect discontinuities in this counter by
STATUS current monitoring the sipCommonSummaryDisconTime object in the same
DESCRIPTION row."
"A row of per entity method statistics. ::= { sipCommonSummaryStatsEntry 5 }
Each row represents those objects for a particular SIP entity sipCommonSummaryDisconTime OBJECT-TYPE
present in this system. applIndex is used to uniquely identify SYNTAX TimeStamp
these instances of SIP entities and correlate them through the MAX-ACCESS read-only
common framework of the NETWORK-SERVICES-MIB (RFC 2788)." STATUS current
INDEX { applIndex, sipCommonMethodStatsName } DESCRIPTION
::= { sipCommonMethodStatsTable 1 } "The value of the sysUpTime object when the counters for the
summary statistics objects in this row last experienced a
discontinuity."
::= { sipCommonSummaryStatsEntry 6 }
SipCommonMethodStatsEntry ::= SEQUENCE { --
sipCommonMethodStatsName SipTCMethodName, -- SIP Method Statistics
sipCommonMethodStatsOutbounds Counter32, -- Total counts for each SIP method.
sipCommonMethodStatsInbounds Counter32, --
sipCommonMethodStatsDisconTime TimeStamp sipCommonMethodStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonMethodStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the method statistics objects for SIP
entities. Each row represents those objects for a particular
SIP entity present in this system."
::= { sipCommonMethodStats 1 }
} sipCommonMethodStatsEntry OBJECT-TYPE
SYNTAX SipCommonMethodStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of per entity method statistics.
sipCommonMethodStatsName OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX SipTCMethodName present in this system. applIndex is used to uniquely identify
MAX-ACCESS not-accessible these instances of SIP entities and correlate them through
STATUS current the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION INDEX { applIndex, sipCommonMethodStatsName }
"This object uniquely identifies the SIP method related to the ::= { sipCommonMethodStatsTable 1 }
objects in a particular row."
::= { sipCommonMethodStatsEntry 1 }
sipCommonMethodStatsOutbounds OBJECT-TYPE SipCommonMethodStatsEntry ::= SEQUENCE {
SYNTAX Counter32 sipCommonMethodStatsName SipTCMethodName,
MAX-ACCESS read-only sipCommonMethodStatsOutbounds Counter32,
STATUS current sipCommonMethodStatsInbounds Counter32,
DESCRIPTION sipCommonMethodStatsDisconTime TimeStamp
"This object reflects the total number of requests sent by the
SIP entity, excluding retransmissions. Retransmissions are
counted separately and are not reflected in this counter. A
Management Station can detect discontinuities in this counter
by monitoring the sipCommonMethodStatsDisconTime object in the
same row."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipCommonMethodStatsEntry 2 }
sipCommonMethodStatsInbounds OBJECT-TYPE }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the total number of requests received by
the SIP entity. Retransmissions are counted separately and are
not reflected in this counter. A Management Station can detect
discontinuities in this counter by monitoring the
sipCommonMethodStatsDisconTime object in the same row."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipCommonMethodStatsEntry 3 }
sipCommonMethodStatsDisconTime OBJECT-TYPE sipCommonMethodStatsName OBJECT-TYPE
SYNTAX TimeStamp SYNTAX SipTCMethodName
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the sysUpTime object when the counters for the "This object uniquely identifies the SIP method related to the
method statistics objects in this row last experienced a objects in a particular row."
discontinuity." ::= { sipCommonMethodStatsEntry 1 }
::= { sipCommonMethodStatsEntry 4 }
-- sipCommonMethodStatsOutbounds OBJECT-TYPE
-- Support for specific status codes SYNTAX Counter32
-- MAX-ACCESS read-only
sipCommonStatusCodeTable OBJECT-TYPE STATUS current
SYNTAX SEQUENCE OF SipCommonStatusCodeEntry DESCRIPTION
MAX-ACCESS not-accessible "This object reflects the total number of requests sent by the
STATUS current SIP entity, excluding retransmissions. Retransmissions are
DESCRIPTION counted separately and are not reflected in this counter. A
"This table contains the list of SIP status codes which each SIP Management Station can detect discontinuities in this counter
entity in this system has been requested to monitor. It is the by monitoring the sipCommonMethodStatsDisconTime object in the
mechanism by which specific status codes are monitored. same row."
Entries created in this table must not persist across reboots" REFERENCE
::= { sipCommonStatusCode 1 } "RFC 3261, Section 7.1"
::= { sipCommonMethodStatsEntry 2 }
sipCommonStatusCodeEntry OBJECT-TYPE sipCommonMethodStatsInbounds OBJECT-TYPE
SYNTAX SipCommonStatusCodeEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information on a particular SIP status code "This object reflects the total number of requests received by
that the SIP entity has been requested to monitor. Entries the SIP entity. Retransmissions are counted separately and are
created in this table must not persist across reboots. not reflected in this counter. A Management Station can detect
discontinuities in this counter by monitoring the
sipCommonMethodStatsDisconTime object in the same row."
REFERENCE
"RFC 3261, Section 7.1"
::= { sipCommonMethodStatsEntry 3 }
Each row represents those objects for a particular SIP entity sipCommonMethodStatsDisconTime OBJECT-TYPE
present in this system. applIndex is used to uniquely identify SYNTAX TimeStamp
these instances of SIP entities and correlate them through the MAX-ACCESS read-only
common framework of the NETWORK-SERVICES-MIB (RFC 2788)." STATUS current
INDEX { applIndex, sipCommonStatusCodeMethod, DESCRIPTION
sipCommonStatusCodeValue } "The value of the sysUpTime object when the counters for the
::= { sipCommonStatusCodeTable 1 } method statistics objects in this row last experienced a
discontinuity."
::= { sipCommonMethodStatsEntry 4 }
SipCommonStatusCodeEntry ::= SEQUENCE { --
sipCommonStatusCodeMethod SipTCMethodName, -- Support for specific status codes
sipCommonStatusCodeValue Unsigned32, --
sipCommonStatusCodeIns Counter32, sipCommonStatusCodeTable OBJECT-TYPE
sipCommonStatusCodeOuts Counter32, SYNTAX SEQUENCE OF SipCommonStatusCodeEntry
sipCommonStatusCodeRowStatus RowStatus, MAX-ACCESS not-accessible
sipCommonStatusCodeDisconTime TimeStamp STATUS current
} DESCRIPTION
"This table contains the list of SIP status codes that each SIP
entity in this system has been requested to monitor. It is the
mechanism by which specific status codes are monitored.
Entries created in this table must not persist across reboots."
::= { sipCommonStatusCode 1 }
sipCommonStatusCodeMethod OBJECT-TYPE sipCommonStatusCodeEntry OBJECT-TYPE
SYNTAX SipTCMethodName SYNTAX SipCommonStatusCodeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in the table "This row contains information on a particular SIP status code
and reflects an assigned number used to identify a specific SIP that the SIP entity has been requested to monitor. Entries
method." created in this table must not persist across reboots.
::= { sipCommonStatusCodeEntry 1 }
sipCommonStatusCodeValue OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX Unsigned32 (100..999) present in this system. applIndex is used to uniquely identify
MAX-ACCESS not-accessible these instances of SIP entities and correlate them through
STATUS current the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION INDEX { applIndex, sipCommonStatusCodeMethod,
"This object contains a SIP status code value that the SIP sipCommonStatusCodeValue }
entity has been requested to monitor. All of the other ::= { sipCommonStatusCodeTable 1 }
information in the row is related to this value."
::= { sipCommonStatusCodeEntry 2 }
sipCommonStatusCodeIns OBJECT-TYPE SipCommonStatusCodeEntry ::= SEQUENCE {
SYNTAX Counter32 sipCommonStatusCodeMethod SipTCMethodName,
MAX-ACCESS read-only sipCommonStatusCodeValue Unsigned32,
STATUS current sipCommonStatusCodeIns Counter32,
DESCRIPTION sipCommonStatusCodeOuts Counter32,
"This object reflects the total number of response messages sipCommonStatusCodeRowStatus RowStatus,
received by the SIP entity with the status code value contained sipCommonStatusCodeDisconTime TimeStamp
in the sipCommonStatusCodeValue column. }
Discontinuities in the value of this counter can occur at sipCommonStatusCodeMethod OBJECT-TYPE
re-initialization of the SIP entity or service, or when the SYNTAX SipTCMethodName
monitoring of the Status code is temporarily disabled. A MAX-ACCESS not-accessible
Management Station can detect discontinuities in this counter STATUS current
by monitoring the sipCommonStatusCodeDisconTime object in the DESCRIPTION
same row." "This object uniquely identifies a conceptual row in the
::= { sipCommonStatusCodeEntry 3 } table."
::= { sipCommonStatusCodeEntry 1 }
sipCommonStatusCodeOuts OBJECT-TYPE sipCommonStatusCodeValue OBJECT-TYPE
SYNTAX Counter32 SYNTAX Unsigned32 (100..999)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of response messages sent "This object contains a SIP status code value that the SIP
by the SIP entity with the status code value contained in the entity has been requested to monitor. All of the other
sipCommonStatusCodeValue column. information in the row is related to this value."
::= { sipCommonStatusCodeEntry 2 }
Discontinuities in the value of this counter can occur at sipCommonStatusCodeIns OBJECT-TYPE
re-initialization of the SIP entity or service, or when the SYNTAX Counter32
monitoring of the Status code is temporarily disabled. A MAX-ACCESS read-only
Management Station can detect discontinuities in this counter STATUS current
by monitoring the sipCommonStatusCodeDisconTime object in the DESCRIPTION
same row." "This object reflects the total number of response messages
::= { sipCommonStatusCodeEntry 4 } received by the SIP entity with the status code value contained
in the sipCommonStatusCodeValue column.
sipCommonStatusCodeRowStatus OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX RowStatus re-initialization of the SIP entity or service, or when the
MAX-ACCESS read-create monitoring of the status code is temporarily disabled. A
STATUS current Management Station can detect discontinuities in this counter
DESCRIPTION by monitoring the sipCommonStatusCodeDisconTime object in the
"The row augmentation in sipCommonStatusCodeNotifTable will be same row."
governed by the value of this RowStatus. ::= { sipCommonStatusCodeEntry 3 }
The values 'createAndGo' and 'destroy' are the only valid sipCommonStatusCodeOuts OBJECT-TYPE
values allowed for this object. If a row exists, it will SYNTAX Counter32
reflect a status of 'active' when queried." MAX-ACCESS read-only
::= { sipCommonStatusCodeEntry 5 } STATUS current
DESCRIPTION
"This object reflects the total number of response messages sent
by the SIP entity with the status code value contained in the
sipCommonStatusCodeValue column.
sipCommonStatusCodeDisconTime OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX TimeStamp re-initialization of the SIP entity or service, or when the
MAX-ACCESS read-only monitoring of the Status code is temporarily disabled. A
STATUS current Management Station can detect discontinuities in this counter
DESCRIPTION by monitoring the sipCommonStatusCodeDisconTime object in the
"The value of the sysUpTime object when the counters for the same row."
status code statistic objects in this row last experienced a
discontinuity."
::= { sipCommonStatusCodeEntry 6 }
-- ::= { sipCommonStatusCodeEntry 4 }
-- Support for specific status code notifications
--
sipCommonStatusCodeNotifTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonStatusCodeNotifEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains objects to control notifications related to
particular status codes each SIP entity in this system has been
requested to monitor.
There is an entry in this table corresponding to each entry in sipCommonStatusCodeRowStatus OBJECT-TYPE
sipCommonStatusCodeTable. Therefore, this table augments that SYNTAX RowStatus
table and utilizes the same index methodology. MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The row augmentation in sipCommonStatusCodeNotifTable will be
governed by the value of this RowStatus.
The objects in this table are not included directly in the The values 'createAndGo' and 'destroy' are the only valid
sipCommonStatusCodeTable simply to keep the status code values allowed for this object. If a row exists, it will
notification control objects separate from the actual status reflect a status of 'active' when queried."
code statistics." ::= { sipCommonStatusCodeEntry 5 }
::= { sipCommonStatusCode 2 }
sipCommonStatusCodeNotifEntry OBJECT-TYPE sipCommonStatusCodeDisconTime OBJECT-TYPE
SYNTAX SipCommonStatusCodeNotifEntry SYNTAX TimeStamp
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information controlling notifications for a "The value of the sysUpTime object when the counters for the
particular SIP status code that the SIP entity has been status code statistics objects in this row last experienced
requested to monitor." a discontinuity."
AUGMENTS { sipCommonStatusCodeEntry } ::= { sipCommonStatusCodeEntry 6 }
::= { sipCommonStatusCodeNotifTable 1 }
SipCommonStatusCodeNotifEntry ::= SEQUENCE { --
sipCommonStatusCodeNotifSend TruthValue, -- Support for specific status code notifications
sipCommonStatusCodeNotifEmitMode INTEGER, --
sipCommonStatusCodeNotifThresh Unsigned32,
sipCommonStatusCodeNotifInterval Unsigned32
}
sipCommonStatusCodeNotifSend OBJECT-TYPE sipCommonStatusCodeNotifTable OBJECT-TYPE
SYNTAX TruthValue SYNTAX SEQUENCE OF SipCommonStatusCodeNotifEntry
MAX-ACCESS read-write MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls whether a sipCommonStatusCodeNotif is "This table contains objects to control notifications related to
emitted when the status code value specified in by particular status codes that each SIP entity in this system has
sipCommonStatusCodeValue is sent or received. If the value of been requested to monitor.
this object is 'true', then a notification is sent. If it is
'false', no notification is sent.
Note well, that a notification MAY be emitted for every message There is an entry in this table corresponding to each entry in
sent or received that contains the particular status code. sipCommonStatusCodeTable. Therefore, this table augments
Depending on the status code involved, this can cause a sipCommonStatusCodeTable and utilizes the same index
significant number of notification emissions that could be methodology.
detrimental to network performance. Managers are forewarned to
be prudent in the use of this object to enable notifications.
Look to sipCommonStatusCodeNotifEmitMode for alternative
controls for sipCommonStatusCodeNotif emissions."
DEFVAL { false }
::= { sipCommonStatusCodeNotifEntry 1 }
sipCommonStatusCodeNotifEmitMode OBJECT-TYPE The objects in this table are not included directly in the
SYNTAX INTEGER { sipCommonStatusCodeTable simply to keep the status code
normal(1), notification control objects separate from the actual status
oneShot(2), code statistics."
triggered(3) -- read-only ::= { sipCommonStatusCode 2 }
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The object sipCommonStatusCodeNotifSend MUST be set to 'true'
for the values of this object to have any effect. It is
RECOMMENDED that the desired emit mode be established by this
object prior to setting sipCommonStatusCodeNotifSend to 'true'.
This object and the sipCommonStatusCodeNotifSend object can
obviously be set independently, but their respective values
will have a dependency on each other and the resulting
notifications.
This object specifies the mode for emissions of sipCommonStatusCodeNotifEntry OBJECT-TYPE
sipCommonStatusCodeNotif notifications. SYNTAX SipCommonStatusCodeNotifEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This row contains information controlling notifications for a
particular SIP status code that the SIP entity has been
requested to monitor."
AUGMENTS { sipCommonStatusCodeEntry }
::= { sipCommonStatusCodeNotifTable 1 }
normal : sipCommonStatusCodeNotif notifications will be SipCommonStatusCodeNotifEntry ::= SEQUENCE {
emitted by the system for each SIP response sipCommonStatusCodeNotifSend TruthValue,
messages sent or received that contains the sipCommonStatusCodeNotifEmitMode INTEGER,
desired status code. sipCommonStatusCodeNotifThresh Unsigned32,
sipCommonStatusCodeNotifInterval Unsigned32
}
oneShot : Only one sipCommonStatusCodeNotif notification sipCommonStatusCodeNotifSend OBJECT-TYPE
will be emitted. It will be the next SIP response SYNTAX TruthValue
messages sent or received that contains the MAX-ACCESS read-write
desired status code. STATUS current
DESCRIPTION
"This object controls whether a sipCommonStatusCodeNotif is
emitted when the status code value specified by
sipCommonStatusCodeValue is sent or received. If the value of
this object is 'true', then a notification is sent. If it is
'false', no notification is sent.
Note well that a notification MAY be emitted for every message
sent or received that contains the particular status code.
Depending on the status code involved, this can cause a
significant number of notification emissions that could be
detrimental to network performance. Managers are forewarned to
be prudent in the use of this object to enable notifications.
Look to sipCommonStatusCodeNotifEmitMode for alternative
controls for sipCommonStatusCodeNotif emissions."
DEFVAL { false }
::= { sipCommonStatusCodeNotifEntry 1 }
No more notifications are emitted until this object sipCommonStatusCodeNotifEmitMode OBJECT-TYPE
is set to either 'oneShot' again or 'normal'. This SYNTAX INTEGER {
option is provided as a means of quelling the normal(1),
potential promiscuous behavior that can be oneShot(2),
associated with the sipCommonStatusCodeNotif. triggered(3) -- read-only
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The object sipCommonStatusCodeNotifSend MUST be set to 'true'
for the values of this object to have any effect. It is
RECOMMENDED that the desired emit mode be established by this
object prior to setting sipCommonStatusCodeNotifSend to 'true'.
This object and the sipCommonStatusCodeNotifSend object can
obviously be set independently, but their respective values
will have a dependency on each other and the resulting
notifications.
triggered : This value is only readable and cannot be set. It This object specifies the mode for emissions of
reflects the default value of the object or that sipCommonStatusCodeNotif notifications.
the 'oneShot' case has occurred and indicates the
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 }
sipCommonStatusCodeNotifThresh OBJECT-TYPE normal : sipCommonStatusCodeNotif notifications will be
SYNTAX Unsigned32 emitted by the system for each SIP response
MAX-ACCESS read-write message sent or received that contains the
STATUS current desired status code.
DESCRIPTION
"This object specifies the number of response messages sent or
received by this system that are considered excessive. Based
on crossing that threshold, a
sipCommonStatusCodeThreshExceededInNotif notification or a
sipCommonStatusCodeThreshExceededOutNotif will be sent. The
sipCommonStatusCodeThreshExceededInNotif and
sipCommonStatusCodeThreshExceededOutNotif notifications can be
used as an early warning mechanism in lieu of using
sipCommonStatusCodeNotif.
Note that the configuration applied by this object will be oneShot : Only one sipCommonStatusCodeNotif notification
applied equally to inbound and outbound response messages." will be emitted. It will be the next SIP response
DEFVAL { 500 } message sent or received that contains the
::= { sipCommonStatusCodeNotifEntry 3 } desired status code.
sipCommonStatusCodeNotifInterval OBJECT-TYPE No more notifications are emitted until this
SYNTAX Unsigned32 object is set to 'oneShot' again or set to
UNITS "seconds" 'normal'. This option is provided as a means of
MAX-ACCESS read-write quelling the potential promiscuous behavior that
STATUS current can be associated with the
DESCRIPTION sipCommonStatusCodeNotif.
"This object specifies the time interval over which if
sipCommonStatusCodeThresh is exceeded, with respect to sent or
received messages, a sipCommonStatusCodeThreshExceededInNotif
or sipCommonStatusCodeThreshExceededOutNotif notification will
be sent.
Note that the configuration applied by this object will be triggered : This value is only readable and cannot be set. It
applied equally to inbound and outbound response messages." reflects that the 'oneShot' case has occurred,
DEFVAL { 60 } and indicates that the mode needs to be reset to
::= { sipCommonStatusCodeNotifEntry 4 } get further notifications. The mode is reset by
setting this object to 'oneShot' or 'normal'."
DEFVAL { oneShot }
::= { sipCommonStatusCodeNotifEntry 2 }
-- sipCommonStatusCodeNotifThresh OBJECT-TYPE
-- Transaction Statistics SYNTAX Unsigned32
-- MAX-ACCESS read-write
sipCommonTransCurrentTable OBJECT-TYPE STATUS current
SYNTAX SEQUENCE OF SipCommonTransCurrentEntry DESCRIPTION
MAX-ACCESS not-accessible "This object specifies the number of response messages sent or
STATUS current received by this system that are considered excessive. Based
DESCRIPTION on crossing that threshold, a
"This table contains information on the transactions currently sipCommonStatusCodeThreshExceededInNotif notification or a
awaiting definitive responses by each SIP entity in this sipCommonStatusCodeThreshExceededOutNotif will be sent. The
system. sipCommonStatusCodeThreshExceededInNotif and
sipCommonStatusCodeThreshExceededOutNotif notifications can be
used as an early warning mechanism in lieu of using
sipCommonStatusCodeNotif.
This table does not apply to transaction stateless Proxy Note that the configuration applied by this object will be
Servers." applied equally to inbound and outbound response messages."
::= { sipCommonStatsTrans 1 } DEFVAL { 500 }
::= { sipCommonStatusCodeNotifEntry 3 }
sipCommonTransCurrentEntry OBJECT-TYPE sipCommonStatusCodeNotifInterval OBJECT-TYPE
SYNTAX SipCommonTransCurrentEntry SYNTAX Unsigned32
MAX-ACCESS not-accessible UNITS "seconds"
STATUS current MAX-ACCESS read-write
DESCRIPTION STATUS current
"Information on a particular SIP entity's current transactions. DESCRIPTION
"This object specifies the time interval over which, if
sipCommonStatusCodeThresh is exceeded with respect to sent or
received messages, a sipCommonStatusCodeThreshExceededInNotif
or sipCommonStatusCodeThreshExceededOutNotif notification will
be sent.
Each row represents those objects for a particular SIP entity Note that the configuration applied by this object will be
present in this system. applIndex is used to uniquely identify applied equally to inbound and outbound response messages."
these instances of SIP entities and correlate them through the DEFVAL { 60 }
common framework of the NETWORK-SERVICES-MIB (RFC 2788)." ::= { sipCommonStatusCodeNotifEntry 4 }
INDEX { applIndex }
::= { sipCommonTransCurrentTable 1 }
SipCommonTransCurrentEntry ::= SEQUENCE { --
sipCommonTransCurrentactions Gauge32 -- Transaction Statistics
} --
sipCommonTransCurrentTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonTransCurrentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information on the transactions currently
awaiting definitive responses by each SIP entity in this
system.
sipCommonTransCurrentactions OBJECT-TYPE This table does not apply to transaction stateless Proxy
SYNTAX Gauge32 (0..4294967295) Servers."
MAX-ACCESS read-only ::= { sipCommonStatsTrans 1 }
STATUS current
DESCRIPTION
"This object contains the number of transactions awaiting
definitive (non-1xx) response. In the case of a forked
request, each branch counts as a single transaction
corresponding to the entity identified by applIndex."
::= { sipCommonTransCurrentEntry 1 }
-- sipCommonTransCurrentEntry OBJECT-TYPE
-- SIP Retry Statistics SYNTAX SipCommonTransCurrentEntry
-- MAX-ACCESS not-accessible
-- This group contains various statistic objects about STATUS current
-- retransmission counts. DESCRIPTION
"Information on a particular SIP entity's current transactions.
-- Each row represents those objects for a particular SIP entity
sipCommonStatsRetryTable OBJECT-TYPE present in this system. applIndex is used to uniquely identify
SYNTAX SEQUENCE OF SipCommonStatsRetryEntry these instances of SIP entities and correlate them through
MAX-ACCESS not-accessible the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
STATUS current INDEX { applIndex }
DESCRIPTION ::= { sipCommonTransCurrentTable 1 }
"This table contains retry statistics objects applicable to each
SIP entity in this system."
::= { sipCommonStatsRetry 1 }
sipCommonStatsRetryEntry OBJECT-TYPE SipCommonTransCurrentEntry ::= SEQUENCE {
SYNTAX SipCommonStatsRetryEntry sipCommonTransCurrentactions Gauge32
MAX-ACCESS not-accessible }
STATUS current
DESCRIPTION
"A row of retry statistics.
Each row represents those objects for a particular SIP entity sipCommonTransCurrentactions OBJECT-TYPE
present in this system. applIndex is used to uniquely identify SYNTAX Gauge32 (0..4294967295)
these instances of SIP entities and correlate them through the MAX-ACCESS read-only
common framework of the NETWORK-SERVICES-MIB (RFC 2788)." STATUS current
INDEX { applIndex, sipCommonStatsRetryMethod } DESCRIPTION
::= { sipCommonStatsRetryTable 1 } "This object contains the number of transactions awaiting
definitive (non-1xx) response. In the case of a forked
request, each branch counts as a single transaction
corresponding to the entity identified by applIndex."
::= { sipCommonTransCurrentEntry 1 }
SipCommonStatsRetryEntry ::= SEQUENCE { --
sipCommonStatsRetryMethod SipTCMethodName, -- SIP Retry Statistics
sipCommonStatsRetries Counter32, --
sipCommonStatsRetryFinalResponses Counter32, -- This group contains various statistics objects about
sipCommonStatsRetryNonFinalResponses Counter32, -- retransmission counts.
sipCommonStatsRetryDisconTime TimeStamp --
} sipCommonStatsRetryTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonStatsRetryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains retry statistics objects applicable to each
SIP entity in this system."
::= { sipCommonStatsRetry 1 }
sipCommonStatsRetryMethod OBJECT-TYPE sipCommonStatsRetryEntry OBJECT-TYPE
SYNTAX SipTCMethodName SYNTAX SipCommonStatsRetryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies the SIP method related to the "A row of retry statistics.
objects in a row."
::= { sipCommonStatsRetryEntry 1 }
sipCommonStatsRetries OBJECT-TYPE Each row represents those objects for a particular SIP entity
SYNTAX Counter32 present in this system. applIndex is used to uniquely identify
MAX-ACCESS read-only these instances of SIP entities and correlate them through the
STATUS current common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
DESCRIPTION
"This object reflects the total number of request
retransmissions that have been sent by the SIP entity. Note
that there could be multiple retransmissions per request.
Discontinuities in the value of this counter can occur at INDEX { applIndex, sipCommonStatsRetryMethod }
re-initialization of the SIP entity or service. A Management ::= { sipCommonStatsRetryTable 1 }
Station can detect discontinuities in this counter by
monitoring the sipCommonStatsRetryDisconTime object in the same
row."
::= { sipCommonStatsRetryEntry 2 }
sipCommonStatsRetryFinalResponses OBJECT-TYPE SipCommonStatsRetryEntry ::= SEQUENCE {
SYNTAX Counter32 sipCommonStatsRetryMethod SipTCMethodName,
MAX-ACCESS read-only sipCommonStatsRetries Counter32,
STATUS current sipCommonStatsRetryFinalResponses Counter32,
DESCRIPTION sipCommonStatsRetryNonFinalResponses Counter32,
"This object reflects the total number of Final Response retries sipCommonStatsRetryDisconTime TimeStamp
that have been sent by the SIP entity. Note that there could }
be multiple retransmissions per request.
Discontinuities in the value of this counter can occur at sipCommonStatsRetryMethod OBJECT-TYPE
re-initialization of the SIP entity or service. A Management SYNTAX SipTCMethodName
Station can detect discontinuities in this counter by MAX-ACCESS not-accessible
monitoring the sipCommonStatsRetryDisconTime object in the same STATUS current
row." DESCRIPTION
::= { sipCommonStatsRetryEntry 3 } "This object uniquely identifies the SIP method related to the
objects in a row."
::= { sipCommonStatsRetryEntry 1 }
sipCommonStatsRetryNonFinalResponses 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 non-Final RResponse "This object reflects the total number of request
retries that have been sent by the SIP entity. retransmissions that have been sent by the SIP entity. Note
that there could be multiple retransmissions per request.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by Station can detect discontinuities in this counter by
monitoring the sipCommonStatsRetryDisconTime object in the same monitoring the sipCommonStatsRetryDisconTime object in the same
row." row."
::= { sipCommonStatsRetryEntry 4 } ::= { sipCommonStatsRetryEntry 2 }
sipCommonStatsRetryDisconTime OBJECT-TYPE sipCommonStatsRetryFinalResponses OBJECT-TYPE
SYNTAX TimeStamp SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the sysUpTime object when the counters for the "This object reflects the total number of Final Response retries
retry statistics objects in this row last experienced a that have been sent by the SIP entity. Note that there could
discontinuity." be multiple retransmissions per request.
::= { sipCommonStatsRetryEntry 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 sipCommonStatsRetryDisconTime object in the same
row."
::= { sipCommonStatsRetryEntry 3 }
-- sipCommonStatsRetryNonFinalResponses OBJECT-TYPE
-- Other Common Statistics SYNTAX Counter32
-- MAX-ACCESS read-only
sipCommonOtherStatsTable OBJECT-TYPE STATUS current
SYNTAX SEQUENCE OF SipCommonOtherStatsEntry DESCRIPTION
MAX-ACCESS not-accessible "This object reflects the total number of non-Final Response
STATUS current retries that have been sent by the SIP entity.
DESCRIPTION
"This table contains other common statistics supported by each
SIP entity in this system."
::= { sipCommonOtherStats 1 }
sipCommonOtherStatsEntry OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX SipCommonOtherStatsEntry re-initialization of the SIP entity or service. A Management
MAX-ACCESS not-accessible Station can detect discontinuities in this counter by
STATUS current monitoring the sipCommonStatsRetryDisconTime object in the same
DESCRIPTION row."
"Information on a particular SIP entity's other common ::= { sipCommonStatsRetryEntry 4 }
statistics.
Each row represents those objects for a particular SIP entity sipCommonStatsRetryDisconTime OBJECT-TYPE
present in this system. applIndex is used to uniquely identify SYNTAX TimeStamp
these instances of SIP entities and correlate them through the MAX-ACCESS read-only
common framework of the NETWORK-SERVICES-MIB (RFC 2788)." STATUS current
INDEX { applIndex } DESCRIPTION
::= { sipCommonOtherStatsTable 1 } "The value of the sysUpTime object when the counters for the
retry statistics objects in this row last experienced a
discontinuity."
::= { sipCommonStatsRetryEntry 5 }
SipCommonOtherStatsEntry ::= SEQUENCE { --
sipCommonOtherStatsNumUnsupportedUris Counter32, -- Other Common Statistics
sipCommonOtherStatsNumUnsupportedMethods Counter32, --
sipCommonOtherStatsOtherwiseDiscardedMsgs Counter32, sipCommonOtherStatsTable OBJECT-TYPE
sipCommonOtherStatsDisconTime TimeStamp SYNTAX SEQUENCE OF SipCommonOtherStatsEntry
} MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains other common statistics supported by each
SIP entity in this system."
::= { sipCommonOtherStats 1 }
sipCommonOtherStatsNumUnsupportedUris OBJECT-TYPE sipCommonOtherStatsEntry OBJECT-TYPE
SYNTAX Counter32 SYNTAX SipCommonOtherStatsEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of RequestURIs received with unsupported scheme. A "Information on a particular SIP entity's other common
server normally responds to such requests with a 400 Bad statistics.
Request status code.
Discontinuities in the value of this counter can occur at Each row represents those objects for a particular SIP entity
re-initialization of the SIP entity or service. A Management present in this system. applIndex is used to uniquely identify
Station can detect discontinuities in this counter by these instances of SIP entities and correlate them through
monitoring the sipCommonOtherStatsDisconTime object in the same the common framework of the NETWORK-SERVICES-MIB (RFC 2788)."
row." INDEX { applIndex }
::= { sipCommonOtherStatsEntry 1 } ::= { sipCommonOtherStatsTable 1 }
sipCommonOtherStatsNumUnsupportedMethods OBJECT-TYPE SipCommonOtherStatsEntry ::= SEQUENCE {
SYNTAX Counter32 sipCommonOtherStatsNumUnsupportedUris Counter32,
MAX-ACCESS read-only sipCommonOtherStatsNumUnsupportedMethods Counter32,
STATUS current sipCommonOtherStatsOtherwiseDiscardedMsgs Counter32,
DESCRIPTION sipCommonOtherStatsDisconTime TimeStamp
"Number of SIP requests received with unsupported methods. A }
server normally responds to such requests with a 501 (Not
Implemented) or 405 (Method Not Allowed).
Discontinuities in the value of this counter can occur at sipCommonOtherStatsNumUnsupportedUris OBJECT-TYPE
re-initialization of the SIP entity or service. A Management SYNTAX Counter32
Station can detect discontinuities in this counter by MAX-ACCESS read-only
monitoring the sipCommonOtherStatsDisconTime object in the same STATUS current
row." DESCRIPTION
::= { sipCommonOtherStatsEntry 2 } "Number of RequestURIs received with an unsupported scheme.
A server normally responds to such requests with a 400 Bad
Request status code.
sipCommonOtherStatsOtherwiseDiscardedMsgs OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX Counter32 re-initialization of the SIP entity or service. A Management
MAX-ACCESS read-only Station can detect discontinuities in this counter by
STATUS current monitoring the sipCommonOtherStatsDisconTime object in the same
DESCRIPTION row."
"Number of SIP messages received that for any number of reasons ::= { sipCommonOtherStatsEntry 1 }
was discarded without a response.
Discontinuities in the value of this counter can occur at sipCommonOtherStatsNumUnsupportedMethods OBJECT-TYPE
re-initialization of the SIP entity or service. A Management SYNTAX Counter32
Station can detect discontinuities in this counter by MAX-ACCESS read-only
monitoring the sipCommonOtherStatsDisconTime object in the same STATUS current
row." DESCRIPTION
::= { sipCommonOtherStatsEntry 3 } "Number of SIP requests received with unsupported methods. A
server normally responds to such requests with a 501 (Not
Implemented) or 405 (Method Not Allowed).
sipCommonOtherStatsDisconTime OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX TimeStamp re-initialization of the SIP entity or service. A Management
MAX-ACCESS read-only Station can detect discontinuities in this counter by
STATUS current monitoring the sipCommonOtherStatsDisconTime object in the same
DESCRIPTION row."
"The value of the sysUpTime object when the counters for the ::= { sipCommonOtherStatsEntry 2 }
statistics objects in this row last experienced a
discontinuity."
::= { sipCommonOtherStatsEntry 4 }
-- sipCommonOtherStatsOtherwiseDiscardedMsgs OBJECT-TYPE
-- Notification related objects SYNTAX Counter32
-- MAX-ACCESS read-only
-- STATUS current
-- Status code related notification objects. DESCRIPTION
-- "Number of SIP messages received that, for any number of
sipCommonStatusCodeNotifTo OBJECT-TYPE reasons, was discarded without a response.
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This object contains the value of the To header in the message
containing the status code that caused the notification. The
header name will be part of this object value. For example,
'To: Watson '."
::= { sipCommonNotifObjects 1 }
sipCommonStatusCodeNotifFrom OBJECT-TYPE Discontinuities in the value of this counter can occur at
SYNTAX SnmpAdminString re-initialization of the SIP entity or service. A Management
MAX-ACCESS accessible-for-notify Station can detect discontinuities in this counter by
STATUS current monitoring the sipCommonOtherStatsDisconTime object in the same
DESCRIPTION row."
"This object contains the value of the From header in the ::= { sipCommonOtherStatsEntry 3 }
message containing the status code that caused the
notification. The header name will be part of this object
value. For example, 'From: Watson '."
::= { sipCommonNotifObjects 2 }
sipCommonStatusCodeNotifCallId OBJECT-TYPE sipCommonOtherStatsDisconTime OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX TimeStamp
MAX-ACCESS accessible-for-notify MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the Call-ID in the message "The value of the sysUpTime object when the counters for the
containing the status code that caused the notification. The statistics objects in this row last experienced a
header name will be part of this object value. For example, discontinuity."
'Call-ID: 5551212@example.com'." ::= { sipCommonOtherStatsEntry 4 }
::= { sipCommonNotifObjects 3 }
sipCommonStatusCodeNotifCSeq OBJECT-TYPE --
SYNTAX Unsigned32 -- Notification related objects
MAX-ACCESS accessible-for-notify --
STATUS current
DESCRIPTION
"This object contains the CSeq value in the message containing
the status code that caused the notification. The header name
will be part of this object value. For example, 'CSeq: 1722
INVITE'."
::= { sipCommonNotifObjects 4 }
-- --
-- General notification related objects. -- Status code related notification objects.
-- --
sipCommonNotifApplIndex OBJECT-TYPE sipCommonStatusCodeNotifTo OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the applIndex as described in RFC 2788. "This object contains the value of the To header in the message
This object is created in order to allow a variable binding containing the status code that caused the notification. The
containing a value of applIndex in a notification." header name will be part of this object value. For example,
::= { sipCommonNotifObjects 5 } 'To: Watson '."
::= { sipCommonNotifObjects 1 }
sipCommonNotifSequenceNumber OBJECT-TYPE sipCommonStatusCodeNotifFrom OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a sequence number for each notification "This object contains the value of the From header in the
generated by this SIP entity. Each notification SHOULD have a message containing the status code that caused the
unique sequence number. A network manager can use this notification. The header name will be part of this object
information to determine whether notifications from a value. For example, 'From: Watson '."
particular SIP entity have been missed. The value of this ::= { sipCommonNotifObjects 2 }
object MUST start at 1 and increase by one with each generated
notification. If a system restarts, the sequence number MAY
start again from 1."
::= { sipCommonNotifObjects 6 }
-- sipCommonStatusCodeNotifCallId OBJECT-TYPE
-- Notifications SYNTAX SnmpAdminString
-- MAX-ACCESS accessible-for-notify
sipCommonStatusCodeNotif NOTIFICATION-TYPE STATUS current
OBJECTS { DESCRIPTION
sipCommonNotifSequenceNumber, "This object contains the value of the Call-ID in the message
sipCommonNotifApplIndex, containing the status code that caused the notification. The
sipCommonStatusCodeNotifTo, header name will be part of this object value. For example,
sipCommonStatusCodeNotifFrom, 'Call-ID: 5551212@example.com'."
sipCommonStatusCodeNotifCallId, ::= { sipCommonNotifObjects 3 }
sipCommonStatusCodeNotifCSeq,
sipCommonStatusCodeIns,
sipCommonStatusCodeOuts
}
STATUS current
DESCRIPTION
"Signifies that a specific status code has been sent or received
by the system."
::= { sipCommonMIBNotifications 1 }
sipCommonStatusCodeThreshExceededInNotif NOTIFICATION-TYPE sipCommonStatusCodeNotifCSeq OBJECT-TYPE
OBJECTS { SYNTAX Unsigned32
sipCommonNotifSequenceNumber, MAX-ACCESS accessible-for-notify
sipCommonNotifApplIndex, STATUS current
sipCommonStatusCodeIns DESCRIPTION
} "This object contains the CSeq value in the message containing
STATUS current the status code that caused the notification. The header name
DESCRIPTION will be part of this object value. For example, 'CSeq: 1722
"Signifies that a specific status code was found to have been INVITE'."
received by the system enough to exceed the configured ::= { sipCommonNotifObjects 4 }
threshold. This notification can be used as an early warning
mechanism in lieu of using sipCommonStatusCodeNotif."
::= { sipCommonMIBNotifications 2 }
sipCommonStatusCodeThreshExceededOutNotif NOTIFICATION-TYPE --
OBJECTS { -- General notification related objects.
sipCommonNotifSequenceNumber, --
sipCommonNotifApplIndex, sipCommonNotifApplIndex OBJECT-TYPE
sipCommonStatusCodeOuts SYNTAX Unsigned32 (1..2147483647)
} MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that a specific status code was found to have been "This object contains the applIndex as described in RFC 2788.
sent by the system enough to exceed the configured threshold. This object is created in order to allow a variable binding
This notification can be used as an early warning mechanism in containing a value of applIndex in a notification."
lieu of using sipCommonStatusCodeNotif." ::= { sipCommonNotifObjects 5 }
::= { sipCommonMIBNotifications 3 }
sipCommonServiceColdStart NOTIFICATION-TYPE sipCommonNotifSequenceNumber OBJECT-TYPE
OBJECTS { SYNTAX Unsigned32 (1..2147483647)
sipCommonNotifSequenceNumber, MAX-ACCESS accessible-for-notify
sipCommonNotifApplIndex, STATUS current
sipCommonCfgServiceStartTime DESCRIPTION
} "This object contains a sequence number for each notification
STATUS current generated by this SIP entity. Each notification SHOULD have a
DESCRIPTION unique sequence number. A network manager can use this
"Signifies that the SIP service has reinitialized itself or information to determine whether notifications from a
started for the first time. This SHOULD result from a hard particular SIP entity have been missed. The value of this
'down' to 'up' administrative status change. The configuration object MUST start at 1 and increase by 1 with each generated
or behavior of the service MAY be altered." notification. If a system restarts, the sequence number MAY
::= { sipCommonMIBNotifications 4 } start again from 1."
::= { sipCommonNotifObjects 6 }
sipCommonServiceWarmStart NOTIFICATION-TYPE --
OBJECTS { -- Notifications
sipCommonNotifSequenceNumber, --
sipCommonNotifApplIndex, sipCommonStatusCodeNotif NOTIFICATION-TYPE
sipCommonCfgServiceLastChange OBJECTS {
} sipCommonNotifSequenceNumber,
STATUS current sipCommonNotifApplIndex,
DESCRIPTION sipCommonStatusCodeNotifTo,
"Signifies that the SIP service has reinitialized itself and is sipCommonStatusCodeNotifFrom,
restarting after an administrative 'reset'. The configuration sipCommonStatusCodeNotifCallId,
or behavior of the service MAY be altered." sipCommonStatusCodeNotifCSeq,
::= { sipCommonMIBNotifications 5 } sipCommonStatusCodeIns,
sipCommonStatusCodeOuts
}
STATUS current
DESCRIPTION
"Signifies that a specific status code has been sent or received
by the system."
::= { sipCommonMIBNotifications 1 }
sipCommonServiceStatusChanged NOTIFICATION-TYPE sipCommonStatusCodeThreshExceededInNotif NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipCommonNotifSequenceNumber, sipCommonNotifSequenceNumber,
sipCommonNotifApplIndex, sipCommonNotifApplIndex,
sipCommonCfgServiceLastChange, sipCommonStatusCodeIns
sipCommonCfgServiceOperStatus }
} STATUS current
STATUS current DESCRIPTION
DESCRIPTION "Signifies that a specific status code was found to have been
"Signifies that the SIP service operational status has changed." received by the system frequently enough to exceed the
::= { sipCommonMIBNotifications 6 } configured threshold. This notification can be used as
an early warning mechanism in lieu of using
sipCommonStatusCodeNotif."
::= { sipCommonMIBNotifications 2 }
-- sipCommonStatusCodeThreshExceededOutNotif NOTIFICATION-TYPE
-- Conformance OBJECTS {
-- sipCommonNotifSequenceNumber,
sipCommonMIBCompliances sipCommonNotifApplIndex,
OBJECT IDENTIFIER ::= { sipCommonMIBConformance 1 } sipCommonStatusCodeOuts
sipCommonMIBGroups }
OBJECT IDENTIFIER ::= { sipCommonMIBConformance 2 } STATUS current
DESCRIPTION
"Signifies that a specific status code was found to have been
sent by the system enough to exceed the configured threshold.
This notification can be used as an early warning mechanism in
lieu of using sipCommonStatusCodeNotif."
::= { sipCommonMIBNotifications 3 }
-- sipCommonServiceColdStart NOTIFICATION-TYPE
-- Compliance Statements OBJECTS {
-- sipCommonNotifSequenceNumber,
sipCommonCompliance MODULE-COMPLIANCE sipCommonNotifApplIndex,
STATUS current sipCommonCfgServiceStartTime
DESCRIPTION }
"The compliance statement for SIP entities." STATUS current
DESCRIPTION
"Signifies that the SIP service has reinitialized itself or
started for the first time. This SHOULD result from a hard
'down' to 'up' administrative status change. The configuration
or behavior of the service MAY be altered."
::= { sipCommonMIBNotifications 4 }
MODULE -- this module sipCommonServiceWarmStart NOTIFICATION-TYPE
MANDATORY-GROUPS { sipCommonConfigGroup, OBJECTS {
sipCommonStatsGroup sipCommonNotifSequenceNumber,
} sipCommonNotifApplIndex,
sipCommonCfgServiceLastChange
}
STATUS current
DESCRIPTION
"Signifies that the SIP service has reinitialized itself and is
restarting after an administrative 'reset'. The configuration
or behavior of the service MAY be altered."
::= { sipCommonMIBNotifications 5 }
OBJECT sipCommonStatusCodeRowStatus sipCommonServiceStatusChanged NOTIFICATION-TYPE
SYNTAX RowStatus { active(1) } OBJECTS {
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } sipCommonNotifSequenceNumber,
DESCRIPTION sipCommonNotifApplIndex,
"Support for createAndWait and notInService is not required." sipCommonCfgServiceLastChange,
sipCommonCfgServiceOperStatus
}
STATUS current
DESCRIPTION
"Signifies that the SIP service operational status has changed."
::= { sipCommonMIBNotifications 6 }
OBJECT sipCommonCfgServiceNotifEnable --
MIN-ACCESS not-accessible -- Conformance
DESCRIPTION --
"This object is optional and does not need to be supported." sipCommonMIBCompliances
OBJECT IDENTIFIER ::= { sipCommonMIBConformance 1 }
sipCommonMIBGroups
OBJECT IDENTIFIER ::= { sipCommonMIBConformance 2 }
GROUP sipCommonInformationalGroup --
DESCRIPTION -- Compliance Statements
"This group is OPTIONAL. A SIP entity can elect to not provide --
any support for these objects as they provide optional sipCommonCompliance MODULE-COMPLIANCE
information." STATUS current
DESCRIPTION
"The compliance statement for SIP entities."
GROUP sipCommonConfigTimerGroup MODULE -- this module
DESCRIPTION MANDATORY-GROUPS { sipCommonConfigGroup,
"This group is OPTIONAL. A SIP entity can elect to not provide sipCommonStatsGroup
any timer configuration." }
GROUP sipCommonStatsRetryGroup OBJECT sipCommonStatusCodeRowStatus
DESCRIPTION SYNTAX RowStatus { active(1) }
"This group is OPTIONAL. A SIP entity can elect to not provide WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
any retry statistics." DESCRIPTION
"Support for createAndWait and notInService is not required."
GROUP sipCommonNotifGroup OBJECT sipCommonCfgServiceNotifEnable
DESCRIPTION MIN-ACCESS not-accessible
"This group is OPTIONAL. A SIP entity can elect to not provide DESCRIPTION
any notifications. If implemented, the "This object is optional and does not need to be supported."
sipCommonStatusCodeNotifGroup and sipCommonNotifObjectsGroup
MUST also be implemented."
GROUP sipCommonStatusCodeNotifGroup GROUP sipCommonInformationalGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to not provide "This group is OPTIONAL. A SIP entity can elect to not provide
any notifications. If implemented, the sipCommonNotifGroup and any support for these objects, as they provide optional
sipCommonNotifObjectsGroup MUST also be implemented." information."
GROUP sipCommonNotifObjectsGroup GROUP sipCommonConfigTimerGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to not provide "This group is OPTIONAL. A SIP entity can elect to not provide
any notifications. If implemented, the any timer configuration."
sipCommonStatusCodeNotifGroup and sipCommonNotifGroup MUST also
be implemented."
::= { sipCommonMIBCompliances 1 } GROUP sipCommonStatsRetryGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to not provide
any retry statistics."
-- GROUP sipCommonNotifGroup
-- Units of Conformance DESCRIPTION
-- "This group is OPTIONAL. A SIP entity can elect to not provide
sipCommonConfigGroup OBJECT-GROUP any notifications. If implemented, the
OBJECTS { sipCommonStatusCodeNotifGroup and sipCommonNotifObjectsGroup
sipCommonCfgProtocolVersion, MUST also be implemented."
sipCommonCfgServiceOperStatus,
sipCommonCfgServiceStartTime,
sipCommonCfgServiceLastChange,
sipCommonPortTransportRcv,
sipCommonOptionTag,
sipCommonOptionTagHeaderField,
sipCommonCfgMaxTransactions,
sipCommonCfgServiceNotifEnable,
sipCommonCfgEntityType,
sipCommonMethodSupportedName
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration common to all
SIP entities."
::= { sipCommonMIBGroups 1 }
sipCommonInformationalGroup OBJECT-GROUP GROUP sipCommonStatusCodeNotifGroup
OBJECTS { DESCRIPTION
sipCommonCfgOrganization "This group is OPTIONAL. A SIP entity can elect to not provide
} any notifications. If implemented, the sipCommonNotifGroup and
STATUS current sipCommonNotifObjectsGroup MUST also be implemented."
DESCRIPTION
"A collection of objects providing configuration common to all
SIP entities."
::= { sipCommonMIBGroups 2 }
sipCommonConfigTimerGroup OBJECT-GROUP GROUP sipCommonNotifObjectsGroup
OBJECTS { DESCRIPTION
sipCommonCfgTimerA, "This group is OPTIONAL. A SIP entity can elect to not provide
sipCommonCfgTimerB, any notifications. If implemented, the
sipCommonCfgTimerC, sipCommonStatusCodeNotifGroup and sipCommonNotifGroup MUST also
sipCommonCfgTimerD, be implemented."
sipCommonCfgTimerE,
sipCommonCfgTimerF,
sipCommonCfgTimerG,
sipCommonCfgTimerH,
sipCommonCfgTimerI,
sipCommonCfgTimerJ,
sipCommonCfgTimerK,
sipCommonCfgTimerT1,
sipCommonCfgTimerT2,
sipCommonCfgTimerT4
}
STATUS current
DESCRIPTION
"A collection of objects providing timer configuration common to
all SIP entities."
::= { sipCommonMIBGroups 3 }
sipCommonStatsGroup OBJECT-GROUP ::= { sipCommonMIBCompliances 1 }
OBJECTS {
sipCommonSummaryInRequests,
sipCommonSummaryOutRequests,
sipCommonSummaryInResponses,
sipCommonSummaryOutResponses,
sipCommonSummaryTotalTransactions,
sipCommonSummaryDisconTime,
sipCommonMethodStatsOutbounds,
sipCommonMethodStatsInbounds,
sipCommonMethodStatsDisconTime,
sipCommonStatusCodeIns,
sipCommonStatusCodeOuts,
sipCommonStatusCodeRowStatus,
sipCommonStatusCodeDisconTime,
sipCommonTransCurrentactions,
sipCommonOtherStatsNumUnsupportedUris,
sipCommonOtherStatsNumUnsupportedMethods,
sipCommonOtherStatsOtherwiseDiscardedMsgs,
sipCommonOtherStatsDisconTime
}
STATUS current
DESCRIPTION
"A collection of objects providing statistics common to all SIP
entities."
::= { sipCommonMIBGroups 4 }
sipCommonStatsRetryGroup OBJECT-GROUP --
OBJECTS { -- Units of Conformance
sipCommonStatsRetries, --
sipCommonStatsRetryFinalResponses, sipCommonConfigGroup OBJECT-GROUP
sipCommonStatsRetryNonFinalResponses, OBJECTS {
sipCommonStatsRetryDisconTime sipCommonCfgProtocolVersion,
} sipCommonCfgServiceOperStatus,
STATUS current sipCommonCfgServiceStartTime,
DESCRIPTION sipCommonCfgServiceLastChange,
"A collection of objects providing retry statistics." sipCommonPortTransportRcv,
::= { sipCommonMIBGroups 5 } sipCommonOptionTag,
sipCommonOptionTagHeaderField,
sipCommonCfgMaxTransactions,
sipCommonCfgServiceNotifEnable,
sipCommonCfgEntityType,
sipCommonMethodSupportedName
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration common to all
SIP entities."
::= { sipCommonMIBGroups 1 }
sipCommonNotifGroup NOTIFICATION-GROUP sipCommonInformationalGroup OBJECT-GROUP
NOTIFICATIONS { OBJECTS {
sipCommonStatusCodeNotif, sipCommonCfgOrganization
sipCommonStatusCodeThreshExceededInNotif, }
sipCommonStatusCodeThreshExceededOutNotif, STATUS current
sipCommonServiceColdStart, DESCRIPTION
sipCommonServiceWarmStart, "A collection of objects providing configuration common to all
sipCommonServiceStatusChanged SIP entities."
} ::= { sipCommonMIBGroups 2 }
STATUS current
DESCRIPTION
"A collection of notifications common to all SIP entities."
::= { sipCommonMIBGroups 6 }
sipCommonStatusCodeNotifGroup OBJECT-GROUP sipCommonConfigTimerGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCommonStatusCodeNotifSend, sipCommonCfgTimerA,
sipCommonStatusCodeNotifEmitMode, sipCommonCfgTimerB,
sipCommonStatusCodeNotifThresh, sipCommonCfgTimerC,
sipCommonStatusCodeNotifInterval sipCommonCfgTimerD,
sipCommonCfgTimerE,
sipCommonCfgTimerF,
sipCommonCfgTimerG,
sipCommonCfgTimerH,
sipCommonCfgTimerI,
sipCommonCfgTimerJ,
sipCommonCfgTimerK,
sipCommonCfgTimerT1,
sipCommonCfgTimerT2,
sipCommonCfgTimerT4
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects related to controlling and attribution "A collection of objects providing timer configuration common to
of notifications common to all SIP entities." all SIP entities."
::= { sipCommonMIBGroups 7 } ::= { sipCommonMIBGroups 3 }
sipCommonNotifObjectsGroup OBJECT-GROUP sipCommonStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCommonStatusCodeNotifTo, sipCommonSummaryInRequests,
sipCommonStatusCodeNotifFrom, sipCommonSummaryOutRequests,
sipCommonStatusCodeNotifCallId, sipCommonSummaryInResponses,
sipCommonStatusCodeNotifCSeq, sipCommonSummaryOutResponses,
sipCommonNotifApplIndex, sipCommonSummaryTotalTransactions,
sipCommonNotifSequenceNumber sipCommonSummaryDisconTime,
} sipCommonMethodStatsOutbounds,
STATUS current sipCommonMethodStatsInbounds,
DESCRIPTION sipCommonMethodStatsDisconTime,
"A collection of accessible-for-notify objects related to the sipCommonStatusCodeIns,
notification defined in this MIB module." sipCommonStatusCodeOuts,
::= { sipCommonMIBGroups 8 } sipCommonStatusCodeRowStatus,
sipCommonStatusCodeDisconTime,
sipCommonTransCurrentactions,
sipCommonOtherStatsNumUnsupportedUris,
sipCommonOtherStatsNumUnsupportedMethods,
sipCommonOtherStatsOtherwiseDiscardedMsgs,
sipCommonOtherStatsDisconTime
END }
STATUS current
DESCRIPTION
"A collection of objects providing statistics common to all SIP
entities."
::= { sipCommonMIBGroups 4 }
sipCommonStatsRetryGroup OBJECT-GROUP
OBJECTS {
sipCommonStatsRetries,
sipCommonStatsRetryFinalResponses,
sipCommonStatsRetryNonFinalResponses,
sipCommonStatsRetryDisconTime
}
STATUS current
DESCRIPTION
"A collection of objects providing retry statistics."
::= { sipCommonMIBGroups 5 }
sipCommonNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS {
sipCommonStatusCodeNotif,
sipCommonStatusCodeThreshExceededInNotif,
sipCommonStatusCodeThreshExceededOutNotif,
sipCommonServiceColdStart,
sipCommonServiceWarmStart,
sipCommonServiceStatusChanged
}
STATUS current
DESCRIPTION
"A collection of notifications common to all SIP entities."
::= { sipCommonMIBGroups 6 }
sipCommonStatusCodeNotifGroup OBJECT-GROUP
OBJECTS {
sipCommonStatusCodeNotifSend,
sipCommonStatusCodeNotifEmitMode,
sipCommonStatusCodeNotifThresh,
sipCommonStatusCodeNotifInterval
}
STATUS current
DESCRIPTION
"A collection of objects related to the control and attribution
of notifications common to all SIP entities."
::= { sipCommonMIBGroups 7 }
sipCommonNotifObjectsGroup OBJECT-GROUP
OBJECTS {
sipCommonStatusCodeNotifTo,
sipCommonStatusCodeNotifFrom,
sipCommonStatusCodeNotifCallId,
sipCommonStatusCodeNotifCSeq,
sipCommonNotifApplIndex,
sipCommonNotifSequenceNumber
}
STATUS current
DESCRIPTION
"A collection of accessible-for-notify objects related to the
notification defined in this MIB module."
::= { sipCommonMIBGroups 8 }
END
7.3. SIP User Agent MIB Module 7.3. SIP User Agent MIB Module
SIP-UA-MIB DEFINITIONS ::= BEGIN SIP-UA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Unsigned32, Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
applIndex applIndex
FROM NETWORK-SERVICES-MIB -- RFC 2788 FROM NETWORK-SERVICES-MIB -- RFC 2788
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB -- RFC 4001 FROM INET-ADDRESS-MIB -- RFC 4001
SipTCEntityRole SipTCEntityRole
FROM SIP-TC-MIB; FROM SIP-TC-MIB; -- RFC 4780
sipUAMIB MODULE-IDENTITY sipUAMIB MODULE-IDENTITY
LAST-UPDATED "200609121700Z" LAST-UPDATED "200704200000Z"
ORGANIZATION "IETF Session Initiation Protocol Working Group" ORGANIZATION "IETF Session Initiation Protocol Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 476 2029
Co-editor Joon Maeng Co-editor Joon Maeng
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 858 Coal Creek Circle postal: 858 Coal Creek Circle
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 9100 phone: +1 303 661 9100
Co-editor Dave Walker Co-editor Dave Walker
email: drwalker@rogers.com" email: drwalker@rogers.com"
DESCRIPTION DESCRIPTION
"Session Initiation Protocol (SIP) User Agent (UA) MIB module. "Session Initiation Protocol (SIP) User Agent (UA) MIB module.
SIP is an application-layer signaling protocol for creating, SIP is an application-layer signaling protocol for creating,
modifying and terminating multimedia sessions with one or more modifying, and terminating multimedia sessions with one or more
participants. These sessions include Internet multimedia participants. These sessions include Internet multimedia
conferences and Internet telephone calls. SIP is defined in conferences and Internet telephone calls. SIP is defined in
RFC 3261 (June 2002). RFC 3261 (June 2002).
A User Agent is an application that contains both a User Agent A User Agent is an application that contains both a User Agent
Client (UAC) and a User Agent Server (UAS). A UAC is an Client (UAC) and a User Agent Server (UAS). A UAC is an
application that initiates a SIP request. A UAS is an application that initiates a SIP request. A UAS is an
application that contacts the user when a SIP request is application that contacts the user when a SIP request is
received and that returns a response on behalf of the user. received and that returns a response on behalf of the user.
The response accepts, rejects, or redirects the request. The response accepts, rejects, or redirects the request.
Copyright (C) The Internet Society (2006). This version of Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC XXXX; see the RFC itself for this MIB module is part of RFC 4780; see the RFC itself for
full legal notices." full legal notices."
-- RFC Ed: replace XXXX with actual RFC number and remove this note REVISION "200704200000Z"
REVISION "200609121700Z" DESCRIPTION
DESCRIPTION "Initial version of the IETF SIP-UA-MIB module. This version
"Initial version of the IETF SIP-UA-MIB module. This version published as part of RFC 4780."
published as part of RFC XXXX." ::= { mib-2 150 }
-- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX3 }
-- RFC Ed: replace XXX3 with actual IANA assigned number -- Top-Level Components of this MIB.
-- RFC Ed: and remove these notes sipUAMIBObjects OBJECT IDENTIFIER ::= { sipUAMIB 1 }
sipUAMIBConformance OBJECT IDENTIFIER ::= { sipUAMIB 2 }
-- Top-Level Components of this MIB. --
sipUAMIBObjects OBJECT IDENTIFIER ::= { sipUAMIB 1 } -- This MIB contains objects related to SIP User Agents.
sipUAMIBConformance OBJECT IDENTIFIER ::= { sipUAMIB 2 } --
sipUACfgServer OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 }
-- --
-- This MIB contains objects related to SIP User Agents. -- SIP Server Configuration
-- --
sipUACfgServer OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 } sipUACfgServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUACfgServerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains SIP server configuration objects applicable
to each SIP user agent in this system."
::= { sipUACfgServer 1 }
-- sipUACfgServerEntry OBJECT-TYPE
-- SIP Server Configuration SYNTAX SipUACfgServerEntry
-- MAX-ACCESS not-accessible
sipUACfgServerTable OBJECT-TYPE STATUS current
SYNTAX SEQUENCE OF SipUACfgServerEntry DESCRIPTION
MAX-ACCESS not-accessible "A row of server configuration.
STATUS current
DESCRIPTION
"This table contains SIP server configuration objects applicable
to each SIP user agent in this system."
::= { sipUACfgServer 1 }
sipUACfgServerEntry OBJECT-TYPE Each row represents those objects for a particular SIP user
SYNTAX SipUACfgServerEntry agent present in this system. applIndex is used to uniquely
MAX-ACCESS not-accessible identify these instances of SIP user agents and correlate
STATUS current them through the common framework of the NETWORK-SERVICES-MIB
DESCRIPTION (RFC 2788). The same value of applIndex used in the
"A row of server configuration. corresponding SIP-COMMON-MIB is used here."
INDEX { applIndex, sipUACfgServerIndex }
::= { sipUACfgServerTable 1 }
Each row represents those objects for a particular SIP user SipUACfgServerEntry ::= SEQUENCE {
agent present in this system. applIndex is used to uniquely sipUACfgServerIndex Unsigned32,
identify these instances of SIP user agents and correlate them sipUACfgServerAddressType InetAddressType,
through the common framework of the NETWORK-SERVICES-MIB (RFC sipUACfgServerAddress InetAddress,
2788). The same value of applIndex used in the corresponding sipUACfgServerRole SipTCEntityRole
SIP-COMMON-MIB is used here." }
INDEX { applIndex, sipUACfgServerIndex }
::= { sipUACfgServerTable 1 }
SipUACfgServerEntry ::= SEQUENCE { sipUACfgServerIndex OBJECT-TYPE
sipUACfgServerIndex Unsigned32, SYNTAX Unsigned32 (1..4294967295)
sipUACfgServerAddressType InetAddressType, MAX-ACCESS not-accessible
sipUACfgServerAddress InetAddress, STATUS current
sipUACfgServerRole SipTCEntityRole DESCRIPTION
} "A unique identifier of a server address when multiple addresses
are configured by the SIP entity. If one address isn't
reachable, then another can be tried."
::= { sipUACfgServerEntry 1 }
sipUACfgServerIndex OBJECT-TYPE sipUACfgServerAddressType OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique identifier of a server address when multiple addresses "This object reflects the type of address contained in the
are configured by the SIP entity. If one address isn't associated instance of sipUACfgServerAddress."
reachable, then another can be tried." REFERENCE
::= { sipUACfgServerEntry 1 } "INET-ADDRESS-MIB (RFC 4001)"
::= { sipUACfgServerEntry 2 }
sipUACfgServerAddressType OBJECT-TYPE sipUACfgServerAddress OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the type of address contained in the "This object reflects the address of a SIP server this user
associated instance of sipUACfgServerAddress." agent will use to proxy/redirect calls. The type of this
REFERENCE address is determined by the value of the
"INET-ADDRESS-MIB (RFC 4001)" sipUACfgServerAddressType object."
::= { sipUACfgServerEntry 2 } REFERENCE "INET-ADDRESS-MIB (RFC 4001)"
::= { sipUACfgServerEntry 3 }
sipUACfgServerAddress OBJECT-TYPE sipUACfgServerRole OBJECT-TYPE
SYNTAX InetAddress SYNTAX SipTCEntityRole
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the address of a SIP server this user "This object reflects the function of the SIP server this user
agent will use to proxy/redirect calls. The type of this agent should communicate with: registrar, proxy (outbound
address is determined by the value of the proxy), etc."
sipUACfgServerAddressType object." ::= { sipUACfgServerEntry 4 }
REFERENCE "INET-ADDRESS-MIB (RFC 4001)"
::= { sipUACfgServerEntry 3 }
sipUACfgServerRole OBJECT-TYPE --
SYNTAX SipTCEntityRole -- Conformance
MAX-ACCESS read-only --
STATUS current sipUAMIBCompliances OBJECT IDENTIFIER ::= { sipUAMIBConformance 1 }
DESCRIPTION sipUAMIBGroups OBJECT IDENTIFIER ::= { sipUAMIBConformance 2 }
"This object reflects the function of the SIP server this user
agent should communicate with: registrar, proxy (outbound
proxy), etc."
::= { sipUACfgServerEntry 4 }
-- --
-- Conformance -- Compliance Statements
-- --
sipUAMIBCompliances OBJECT IDENTIFIER ::= { sipUAMIBConformance 1 } sipUACompliance MODULE-COMPLIANCE
sipUAMIBGroups OBJECT IDENTIFIER ::= { sipUAMIBConformance 2 } STATUS current
DESCRIPTION
"The compliance statement for SIP entities that implement the
SIP-UA-MIB module."
MODULE -- this module
MANDATORY-GROUPS { sipUAConfigGroup }
-- ::= { sipUAMIBCompliances 1 }
-- Compliance Statements
--
sipUACompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SIP entities that implement the
SIP-UA-MIB module."
MODULE -- this module
MANDATORY-GROUPS { sipUAConfigGroup }
::= { sipUAMIBCompliances 1 } --
-- Units of Conformance
--
sipUAConfigGroup OBJECT-GROUP
OBJECTS {
sipUACfgServerAddressType,
sipUACfgServerAddress,
sipUACfgServerRole
}
STATUS current
DESCRIPTION
"A collection of objects providing information about the
configuration of SIP User Agents."
::= { sipUAMIBGroups 1 }
-- END
-- Units of Conformance
--
sipUAConfigGroup OBJECT-GROUP
OBJECTS {
sipUACfgServerAddressType,
sipUACfgServerAddress,
sipUACfgServerRole
}
STATUS current
DESCRIPTION
"A collection of objects providing information about the
configuration of SIP User Agents."
::= { sipUAMIBGroups 1 }
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
TruthValue, TruthValue,
TimeStamp, DateAndTime TimeStamp, DateAndTime
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM SNMP-FRAMEWORK-MIB -- RFC 3411
applIndex applIndex
FROM NETWORK-SERVICES-MIB -- RFC 2788 FROM NETWORK-SERVICES-MIB -- RFC 2788
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB; -- RFC 4001 FROM INET-ADDRESS-MIB; -- RFC 4001
sipServerMIB MODULE-IDENTITY sipServerMIB MODULE-IDENTITY
LAST-UPDATED "200609121700Z" LAST-UPDATED "200704200000Z"
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 476 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. SIP is an "Session Initiation Protocol (SIP) Server MIB module. SIP is an
application-layer signaling protocol for creating, modifying application-layer signaling protocol for creating, modifying,
and terminating multimedia sessions with one or more and terminating multimedia sessions with one or more
participants. These sessions include Internet multimedia participants. These sessions include Internet multimedia
conferences and Internet telephone calls. SIP is defined in conferences and Internet telephone calls. SIP is defined in
RFC 3261 (June 2002). RFC 3261 (June 2002).
This MIB is defined for the management of SIP Proxy, Redirect This MIB is defined for the management of SIP Proxy, Redirect,
and Registrar Servers. and Registrar Servers.
A Proxy Server acts as both a client and a server. It accepts A Proxy Server acts as both a client and a server. It accepts
requests from other clients, either responding to them or requests from other clients, either responding to them or
passing them on to other servers, possibly after modification. passing them on to other servers, possibly after modification.
A Redirect Server accepts requests from clients and returns A Redirect Server accepts requests from clients and returns
zero or more addresses to that client. Unlike a User Agent zero or more addresses to that client. Unlike a User Agent
Server it does not accept calls. Server, it does not accept calls.
A Registrar is a server that accepts REGISTER requests. A A Registrar is a server that accepts REGISTER requests. A
Registrar is typically co-located with a Proxy or Redirect Registrar is typically co-located with a Proxy or Redirect
Server. Server.
Copyright (C) The Internet Society (2006). This version of Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC XXXX; see the RFC itself for this MIB module is part of RFC 4780; see the RFC itself for
full legal notices." full legal notices."
-- RFC Ed: replace XXXX with actual RFC number and remove this note REVISION "200704200000Z"
REVISION "200609121700Z" DESCRIPTION
DESCRIPTION "Initial version of the IETF SIP-SERVER-MIB module. This
"Initial version of the IETF SIP-SERVER-MIB module. This version published as part of RFC 4780."
version published as part of RFC XXXX." ::= { mib-2 151 }
-- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX4 }
-- RFC Ed: replace XXX4 with actual IANA assigned number
-- and remove this note
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 } sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 }
sipServerMIBConformance 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 to SIP "This table contains configuration objects applicable 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 SIP server Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the these instances of SIP servers and correlate them through
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
same value of applIndex used in the corresponding The same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here." SIP-COMMON-MIB is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipServerCfgTable 1 } ::= { sipServerCfgTable 1 }
SipServerCfgEntry ::= SipServerCfgEntry ::=
SEQUENCE { SEQUENCE {
sipServerCfgHostAddressType InetAddressType, sipServerCfgHostAddressType InetAddressType,
sipServerCfgHostAddress InetAddress sipServerCfgHostAddress InetAddress
} }
sipServerCfgHostAddressType 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 is "The type of Internet address by which the SIP server is
reachable." reachable."
REFERENCE REFERENCE
"RFC 3261, Section 19.1.1" "RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 1 } ::= { sipServerCfgEntry 1 }
sipServerCfgHostAddress 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 assigned to the "This is the host portion of a SIP URI that is assigned to the
SIP server. It MAY contain a fully qualified domain name, or SIP server. It MAY contain a fully qualified domain name or
an IP address. The length of the value will depend on the type an IP address. The length of the value will depend on the type
of address specified. The type of address given by this object of address specified. The type of address given by this object
is controlled by sipServerCfgHostAddressType." is controlled by sipServerCfgHostAddressType."
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.
-- --
sipServerProxyCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 3 } sipServerProxyCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 3 }
sipServerProxyStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 4 } sipServerProxyStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 4 }
-- --
-- Proxy Server Configuration -- Proxy Server Configuration
-- --
sipServerProxyCfgTable OBJECT-TYPE sipServerProxyCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerProxyCfgEntry SYNTAX SEQUENCE OF SipServerProxyCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable to SIP "This table contains configuration objects applicable to SIP
Proxy Servers." Proxy Servers."
::= { sipServerProxyCfg 1 } ::= { sipServerProxyCfg 1 }
sipServerProxyCfgEntry OBJECT-TYPE sipServerProxyCfgEntry OBJECT-TYPE
SYNTAX SipServerProxyCfgEntry 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 SIP server Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here." SIP-COMMON-MIB is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipServerProxyCfgTable 1 } ::= { sipServerProxyCfgTable 1 }
SipServerProxyCfgEntry ::= SipServerProxyCfgEntry ::=
SEQUENCE { SEQUENCE {
sipServerCfgProxyStatefulness INTEGER, sipServerCfgProxyStatefulness INTEGER,
sipServerCfgProxyRecursion TruthValue, sipServerCfgProxyRecursion TruthValue,
sipServerCfgProxyRecordRoute TruthValue, sipServerCfgProxyRecordRoute TruthValue,
sipServerCfgProxyAuthMethod BITS, sipServerCfgProxyAuthMethod BITS,
sipServerCfgProxyAuthDefaultRealm SnmpAdminString sipServerCfgProxyAuthDefaultRealm SnmpAdminString
} }
sipServerCfgProxyStatefulness 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 for the "This object reflects the default mode of operation for the
Proxy Server entity. Proxy Server entity.
A stateless proxy is a logical entity that does not maintain A stateless proxy is a logical entity that does not maintain
the client or server transaction state machines when it the client or server transaction state machines when it
processes requests. A stateless proxy forwards every request it processes requests. A stateless proxy forwards every request it
receives downstream and every response it receives upstream. If receives downstream and every response it receives upstream. If
the value of this object is stateless(1), the proxy defaults to the value of this object is stateless(1), the proxy defaults to
stateless operations. stateless operations.
A transaction stateful proxy, or simply a 'stateful proxy', is A transaction stateful proxy, or simply a 'stateful proxy', is
a logical entity that maintains the client and server a logical entity that maintains the client and server
transaction state machines during the processing of a request. transaction state machines during the processing of a request.
A (transaction) stateful proxy is not the same as a call A (transaction) stateful proxy is not the same as a call
stateful proxy. If the value if this object is stateful proxy. If the value of this object is
transactionStateful(2), the proxy is stateful on a transaction transactionStateful(2), the proxy is stateful on a transaction
basis. basis.
A call stateful proxy is a logical entity if it retains state A call stateful proxy is a logical entity if it retains state
for a dialog from the initiating INVITE to the terminating BYE for a dialog from the initiating INVITE to the terminating BYE
request. A call stateful proxy is always transaction stateful, request. A call stateful proxy is always transaction stateful,
but the converse is not necessarily true. If the value of this but the converse is not necessarily true. If the value of this
object is callStateful(3), the proxy is call stateful." object is callStateful(3), the proxy is call stateful."
REFERENCE REFERENCE
"RFC 3261, Section 16" "RFC 3261, Section 16"
::= { sipServerProxyCfgEntry 1 } ::= { sipServerProxyCfgEntry 1 }
sipServerCfgProxyRecursion 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 performs "This object reflects whether or not the Proxy performs a
recursive search on the Contacts provided in 3xx redirects. recursive search on the Contacts provided in 3xx redirects.
If the value of this object is 'true', a recursive search is If the value of this object is 'true', a recursive search is
performed. If the value is 'false', no search is performed, performed. If the value is 'false', no search is performed,
the 3xx response is sent upstream towards the source of the and the 3xx response is sent upstream towards the source of
request." the request."
REFERENCE REFERENCE
"RFC 3261 Sections 16.5 and 16.6" "RFC 3261 Sections 16.5 and 16.6"
::= { sipServerProxyCfgEntry 2 } ::= { sipServerProxyCfgEntry 2 }
sipServerCfgProxyRecordRoute 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 itself to "This object reflects whether or not the proxy adds itself to
the Record-Route header as a default action. This header is the Record-Route header as a default action. This header is
used to list the proxies that insist on being in the signaling used to list the proxies that insist on being in the signaling
path for subsequent requests related to the call-leg. path for subsequent requests related to the call leg.
If the value of this object is 'true', the proxy adds itself to If the value of this object is 'true', the proxy adds itself to
the end of the Record-Route header, creating the header if the end of the Record-Route header, creating the header if
required. If the value is 'false', the proxy does not add required. If the value is 'false', the proxy does not add
itself to the Record-Route header." itself to the Record-Route header."
REFERENCE REFERENCE
"RFC 3261, Section 20.30" "RFC 3261, Section 20.30"
::= { sipServerProxyCfgEntry 3 } ::= { sipServerProxyCfgEntry 3 }
-- --
-- Security -- Security
-- --
sipServerCfgProxyAuthMethod 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 MAY be "This object reflects the authentication methods that 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"
::= { sipServerProxyCfgEntry 4 } ::= { sipServerProxyCfgEntry 4 }
sipServerCfgProxyAuthDefaultRealm 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 to be Proxy-Authenticate headers. Note that this MAY need to be
stored per user, in which case, this default value is ignored. stored per user, in which case, this default value is ignored.
" "
REFERENCE REFERENCE
"RFC 3261, Section 22.1" "RFC 3261, Section 22.1"
::= { sipServerProxyCfgEntry 5 } ::= { sipServerProxyCfgEntry 5 }
-- --
-- Proxy Server Statistics -- Proxy Server Statistics
-- --
sipServerProxyStatsTable OBJECT-TYPE sipServerProxyStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerProxyStatsEntry 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 to all "This table contains the statistics objects applicable to all
SIP Proxy Servers in this system." SIP Proxy Servers in this system."
::= { sipServerProxyStats 1 } ::= { sipServerProxyStats 1 }
sipServerProxyStatsEntry OBJECT-TYPE sipServerProxyStatsEntry OBJECT-TYPE
SYNTAX SipServerProxyStatsEntry 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 SIP server Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here." SIP-COMMON-MIB is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipServerProxyStatsTable 1 } ::= { sipServerProxyStatsTable 1 }
SipServerProxyStatsEntry ::= SipServerProxyStatsEntry ::=
SEQUENCE { SEQUENCE {
sipServerProxyStatProxyReqFailures Counter32, sipServerProxyStatProxyReqFailures Counter32,
sipServerProxyStatsDisconTime TimeStamp sipServerProxyStatsDisconTime TimeStamp
} }
sipServerProxyStatProxyReqFailures 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 unsupported "This object contains the number of occurrences of unsupported
options being specified in received Proxy-Require headers. options being specified in received Proxy-Require headers.
Such occurrences result in a 420 Bad Extension status code Such occurrences result in a 420 Bad Extension status code
being returned. being returned.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by Station can detect discontinuities in this counter by
monitoring the sipServerProxyStatsDisconTime object in the same monitoring the sipServerProxyStatsDisconTime object in the same
row." row."
::= { sipServerProxyStatsEntry 1 } ::= { sipServerProxyStatsEntry 1 }
sipServerProxyStatsDisconTime OBJECT-TYPE sipServerProxyStatsDisconTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the sysUpTime object when the counters for the server "The value of the sysUpTime object when the counters for the server
statistics objects in this row last experienced a discontinuity." statistics objects in this row last experienced a discontinuity."
::= { sipServerProxyStatsEntry 2 } ::= { sipServerProxyStatsEntry 2 }
-- --
-- This group contains MIB objects related to SIP Registrars. -- This group contains MIB objects related to SIP Registrars.
-- --
sipServerRegCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 5 } sipServerRegCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 5 }
sipServerRegStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 6 } sipServerRegStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 6 }
-- --
-- Registrar Configuration -- Registrar Configuration
-- --
sipServerRegCfgTable OBJECT-TYPE sipServerRegCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerRegCfgEntry SYNTAX SEQUENCE OF SipServerRegCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable SIP "This table contains configuration objects applicable to SIP
Registrars." Registrars."
::= { sipServerRegCfg 1 } ::= { sipServerRegCfg 1 }
sipServerRegCfgEntry OBJECT-TYPE sipServerRegCfgEntry OBJECT-TYPE
SYNTAX SipServerRegCfgEntry 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 SIP server Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here." SIP-COMMON-MIB is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipServerRegCfgTable 1 } ::= { sipServerRegCfgTable 1 }
SipServerRegCfgEntry ::= SipServerRegCfgEntry ::=
SEQUENCE { SEQUENCE {
sipServerRegMaxContactExpiryDuration Unsigned32, sipServerRegMaxContactExpiryDuration Unsigned32,
sipServerRegMaxUsers Unsigned32, sipServerRegMaxUsers Unsigned32,
sipServerRegCurrentUsers Gauge32, sipServerRegCurrentUsers Gauge32,
sipServerRegDfltRegActiveInterval Unsigned32 sipServerRegDfltRegActiveInterval Unsigned32
} }
sipServerRegMaxContactExpiryDuration 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 requested "This object reflects the maximum expiry that may be requested
by a User Agent for a particular Contact. User Agents can by a User Agent for a particular Contact. User Agents can
specify expiry using either an Expiry header in a REGISTER specify expiry using either an Expiry header in a REGISTER
request, or using an Expires parameter in a Contact header in request, or using an Expires parameter in a Contact header in
a REGISTER request. If the value requested by the User Agent a REGISTER request. If the value requested by the User Agent
is greater than the value of this object, then the contact is greater 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 object, and
that duration is indicated to the User Agent in the response." that duration is indicated to the User Agent in the response."
::= { sipServerRegCfgEntry 1 } ::= { sipServerRegCfgEntry 1 }
sipServerRegMaxUsers OBJECT-TYPE sipServerRegMaxUsers 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 the "This object reflects the maximum number of users that the
Registrar supports. The current number of users is reflected Registrar supports. The current number of users is reflected
by sipServerRegCurrentUsers." by sipServerRegCurrentUsers."
::= { sipServerRegCfgEntry 2 } ::= { sipServerRegCfgEntry 2 }
sipServerRegCurrentUsers 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 registered "This object reflects the number of users currently registered
with the Registrar." with the Registrar."
::= { sipServerRegCfgEntry 3 } ::= { sipServerRegCfgEntry 3 }
sipServerRegDfltRegActiveInterval 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 Registrar "This object reflects the default time interval the Registrar
considers registrations to be active. The value is used to considers registrations to be active. The value is used to
compute the Expires header in the REGISTER response. If a user compute the Expires header in the REGISTER response. If a user
agent requests a time interval shorter than specified by this agent requests a time interval shorter than specified by this
object, the Registrar SHOULD honor that request. If a Contact object, the 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 of the
Expires header field is used instead. If a Contact entry has no Expires header field is used instead. If a Contact entry has no
'expires' parameter and no the Expires header field is present, 'expires' parameter and no Expires header field is present,
the value of this object is used as the default value." the value of this object is used as the default value."
REFERENCE REFERENCE
"RFC 3261, Section 10.2" "RFC 3261, Section 10.2"
::= { sipServerRegCfgEntry 4 } ::= { sipServerRegCfgEntry 4 }
-- --
-- Per User Information -- Per User Information
-- --
sipServerRegUserTable OBJECT-TYPE sipServerRegUserTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerRegUserEntry 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 registered to each "This table contains information on all users registered to each
Registrar in this system." Registrar in this system."
::= { sipServerRegCfg 2 } ::= { sipServerRegCfg 2 }
sipServerRegUserEntry OBJECT-TYPE sipServerRegUserEntry OBJECT-TYPE
SYNTAX SipServerRegUserEntry SYNTAX SipServerRegUserEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single user registered to "This entry contains information for a single user registered to
this Registrar. this Registrar.
Each row represents those objects for a particular SIP server Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here." SIP-COMMON-MIB is used here."
INDEX { applIndex, sipServerRegUserIndex } INDEX { applIndex, sipServerRegUserIndex }
::= { sipServerRegUserTable 1 } ::= { sipServerRegUserTable 1 }
SipServerRegUserEntry ::= SipServerRegUserEntry ::=
SEQUENCE { SEQUENCE {
sipServerRegUserIndex Unsigned32, sipServerRegUserIndex Unsigned32,
sipServerRegUserUri SnmpAdminString, sipServerRegUserUri SnmpAdminString,
sipServerRegUserAuthenticationFailures Counter32, sipServerRegUserAuthenticationFailures Counter32,
sipServerRegUserDisconTime TimeStamp sipServerRegUserDisconTime TimeStamp
} }
sipServerRegUserIndex 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 the table." "This object uniquely identifies a conceptual row in the table."
::= { sipServerRegUserEntry 1 } ::= { sipServerRegUserEntry 1 }
sipServerRegUserUri 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. It is the "This object contains the user's address-of-record. It is the
main form by which the Registrar knows the user. The format is main form by which the Registrar knows the user. The format is
typically 'user@domain'. It is contained in the To header for typically 'user@domain'. It is contained in the To header for
all REGISTER requests." all REGISTER requests."
::= { sipServerRegUserEntry 2 } ::= { sipServerRegUserEntry 2 }
sipServerRegUserAuthenticationFailures 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 the user "This object contains a count of the number of times the user
has failed authentication. has failed authentication.
Discontinuities in the value of this counter can occur due to Discontinuities in the value of this counter can occur due to
successful user authentications, and at re-initialization of successful user authentications and at re-initialization of
the SIP entity or service. A Management Station can detect the SIP entity or service. A Management Station can detect
discontinuities in this counter by monitoring the discontinuities in this counter by monitoring the
sipServerRegUserDisconTime object in the same row." sipServerRegUserDisconTime object in the same row."
::= { sipServerRegUserEntry 3 } ::= { sipServerRegUserEntry 3 }
sipServerRegUserDisconTime OBJECT-TYPE sipServerRegUserDisconTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the sysUpTime object when the counters for the "The value of the sysUpTime object when the counters for the
user registration statistic objects in this row last user registration statistics objects in this row last
experienced a discontinuity." experienced a discontinuity."
::= { sipServerRegUserEntry 4 } ::= { sipServerRegUserEntry 4 }
-- --
-- Per Contact Information -- Per Contact Information
-- --
sipServerRegContactTable OBJECT-TYPE sipServerRegContactTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerRegContactEntry 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 where a "This table contains information on every location where a
registered user (specified by sipServerRegUserIndex) wishes to registered user (specified by sipServerRegUserIndex) wishes to
be found (i.e. the user has provided Contact information to be found (i.e., the user has provided contact information to
each SIP Registrar in this system)." each SIP Registrar in this system)."
::= { sipServerRegCfg 3 } ::= { sipServerRegCfg 3 }
sipServerRegContactEntry OBJECT-TYPE sipServerRegContactEntry OBJECT-TYPE
SYNTAX SipServerRegContactEntry SYNTAX SipServerRegContactEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single Contact. Multiple "This entry contains information for a single Contact. Multiple
contacts may exist for a single user. contacts may exist for a single user.
Each row represents those objects for a particular SIP server Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here." SIP-COMMON-MIB is used here."
INDEX { applIndex, INDEX { applIndex,
sipServerRegUserIndex, sipServerRegUserIndex,
sipServerRegContactIndex sipServerRegContactIndex
} }
::= { sipServerRegContactTable 1 } ::= { sipServerRegContactTable 1 }
SipServerRegContactEntry ::= SipServerRegContactEntry ::=
SEQUENCE { SEQUENCE {
sipServerRegContactIndex Unsigned32, sipServerRegContactIndex Unsigned32,
sipServerRegContactDisplayName SnmpAdminString, sipServerRegContactDisplayName SnmpAdminString,
sipServerRegContactURI SnmpAdminString, sipServerRegContactURI SnmpAdminString,
sipServerRegContactLastUpdated TimeStamp, sipServerRegContactLastUpdated TimeStamp,
sipServerRegContactExpiry DateAndTime, sipServerRegContactExpiry DateAndTime,
sipServerRegContactPreference SnmpAdminString sipServerRegContactPreference SnmpAdminString
} }
sipServerRegContactIndex 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 sipServerRegUserIndex, this object uniquely "Along with the sipServerRegUserIndex, this object uniquely
identifies a conceptual row in the table." identifies a conceptual row in the table."
::= { sipServerRegContactEntry 1 } ::= { sipServerRegContactEntry 1 }
sipServerRegContactDisplayName 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 Contact. For "This object contains the display name for the Contact. For
example, 'Santa at Home', or 'Santa on his Sled', corresponding example, 'Santa at Home', or 'Santa on his Sled', corresponding
to contact URIs of sip:BigGuy@example.com or to contact URIs of sip:BigGuy@example.com or
sip:sclaus817@example.com, respectively." sip:sclaus817@example.com, respectively."
::= { sipServerRegContactEntry 2 } ::= { sipServerRegContactEntry 2 }
sipServerRegContactURI 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 the user can be "This object contains either a SIP URI where the user can be
contacted. This URI is normally returned to a client from a contacted. This URI is normally returned to a client from a
Redirect Server, or is used as the RequestURI in a SIP request Redirect Server, or is used as the RequestURI in a SIP request
line for requests forwarded by a proxy." line for requests forwarded by a proxy."
::= { sipServerRegContactEntry 3 } ::= { sipServerRegContactEntry 3 }
sipServerRegContactLastUpdated 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 information "This object indicates the time when this contact information
was accepted. If the contact information is updated via a was accepted. If the contact information is updated via a
subsequent REGISTER of the same information, this object is subsequent REGISTER of the same information, this object is
also updated." also updated."
::= { sipServerRegContactEntry 4 } ::= { sipServerRegContactEntry 4 }
sipServerRegContactExpiry 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 contact "This object contains the date and time when the contact
information will no longer be valid. Such times may be information will no longer be valid. Such times may be
specified by the user at registration (Expires header or expiry specified by the user at registration (i.e., Expires header or
parameter in the Contact information), or a system default can expiry parameter in the Contact information), or a system
be applied." default can be applied."
::= { sipServerRegContactEntry 5 } ::= { sipServerRegContactEntry 5 }
sipServerRegContactPreference 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 particular "This object indicates a relative preference for the particular
Contact header field value compared to other bindings for this Contact header field value compared to other bindings for this
address-of-record. A registering user may provide this address-of-record. A registering user may provide this
preference as a 'qvalue' parameter in the Contact header. preference as a 'qvalue' parameter in the Contact header.
The format of this item is a decimal number between 0 and 1 The format of this item is a decimal number between 0 and 1
(for example 0.9). Higher values indicate locations preferred (for example 0.9). Higher values indicate 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"
::= { sipServerRegContactEntry 6 } ::= { sipServerRegContactEntry 6 }
-- --
-- Registrar Statistics -- Registrar Statistics
-- --
sipServerRegStatsTable OBJECT-TYPE sipServerRegStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerRegStatsEntry 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 applicable "This table contains the summary statistics objects applicable
to all SIP Registrars in this system." to all SIP Registrars in this system."
::= { sipServerRegStats 1 } ::= { sipServerRegStats 1 }
sipServerRegStatsEntry OBJECT-TYPE sipServerRegStatsEntry OBJECT-TYPE
SYNTAX SipServerRegStatsEntry 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 SIP server Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here." SIP-COMMON-MIB is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipServerRegStatsTable 1 } ::= { sipServerRegStatsTable 1 }
SipServerRegStatsEntry ::= SipServerRegStatsEntry ::=
SEQUENCE { SEQUENCE {
sipServerRegStatsAcceptedRegs Counter32, sipServerRegStatsAcceptedRegs Counter32,
sipServerRegStatsRejectedRegs Counter32, sipServerRegStatsRejectedRegs Counter32,
sipServerRegStatsDisconTime TimeStamp sipServerRegStatsDisconTime TimeStamp
} }
sipServerRegStatsAcceptedRegs 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 REGISTER requests "This object contains a count of the number of REGISTER requests
that have been accepted (status code 200) by the Registrar. that have been accepted (status code 200) by the Registrar.
This includes additions of new contact information, refreshing This includes additions of new contact information, refreshing
contact information, as well as requests for deletion of contact information, as well as requests for deletion of
contact information. contact information.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by Station can detect discontinuities in this counter by
monitoring the sipServerRegStatsDisconTime object in the same monitoring the sipServerRegStatsDisconTime object in the same
row." row."
::= { sipServerRegStatsEntry 1 } ::= { sipServerRegStatsEntry 1 }
sipServerRegStatsRejectedRegs OBJECT-TYPE 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 requests "This object contains a count of the number REGISTER requests
that have been rejected by the Registrar. that have been rejected by the Registrar.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by Station can detect discontinuities in this counter by
monitoring the sipServerRegStatsDisconTime object in the same monitoring the sipServerRegStatsDisconTime object in the same
row." row."
::= { sipServerRegStatsEntry 2 } ::= { sipServerRegStatsEntry 2 }
sipServerRegStatsDisconTime OBJECT-TYPE sipServerRegStatsDisconTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the sysUpTime object when the counters for the "The value of the sysUpTime object when the counters for the
registrar statistic objects in this row last experienced a registrar statistics objects in this row last experienced a
discontinuity." discontinuity."
::= { sipServerRegStatsEntry 3 } ::= { sipServerRegStatsEntry 3 }
-- --
-- Conformance -- Conformance
-- --
sipServerMIBCompliances sipServerMIBCompliances
OBJECT IDENTIFIER ::= { sipServerMIBConformance 1 } OBJECT IDENTIFIER ::= { sipServerMIBConformance 1 }
sipServerMIBGroups
OBJECT IDENTIFIER ::= { sipServerMIBConformance 2 }
-- sipServerMIBGroups
-- Compliance Statements OBJECT IDENTIFIER ::= { sipServerMIBConformance 2 }
--
sipServerProxyServerCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SIP entities acting as Proxy
Servers."
MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup,
sipServerProxyConfigGroup,
sipServerProxyStatsGroup
}
::= { sipServerMIBCompliances 1 }
sipRedirectServerCompliance MODULE-COMPLIANCE --
STATUS current -- Compliance Statements
DESCRIPTION --
"The compliance statement for SIP entities acting as Redirect sipServerProxyServerCompliance MODULE-COMPLIANCE
Servers." STATUS current
MODULE -- this module DESCRIPTION
MANDATORY-GROUPS { sipServerConfigGroup } "The compliance statement for SIP entities acting as Proxy
::= { sipServerMIBCompliances 2 } Servers."
MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup,
sipServerProxyConfigGroup,
sipServerProxyStatsGroup
}
::= { sipServerMIBCompliances 1 }
sipServerRegistrarServerCompliance MODULE-COMPLIANCE sipRedirectServerCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities acting as "The compliance statement for SIP entities acting as Redirect
Registrars." Servers."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipServerConfigGroup, MANDATORY-GROUPS { sipServerConfigGroup }
sipServerRegistrarConfigGroup, ::= { sipServerMIBCompliances 2 }
sipServerRegistrarStatsGroup }
GROUP sipServerRegistrarUsersGroup
DESCRIPTION
"This is an optional group."
::= { sipServerMIBCompliances 3 }
-- sipServerRegistrarServerCompliance MODULE-COMPLIANCE
-- Units of Conformance STATUS current
-- DESCRIPTION
sipServerConfigGroup OBJECT-GROUP "The compliance statement for SIP entities acting as
OBJECTS { Registrars."
sipServerCfgHostAddressType, MODULE -- this module
sipServerCfgHostAddress MANDATORY-GROUPS { sipServerConfigGroup,
} sipServerRegistrarConfigGroup,
STATUS current sipServerRegistrarStatsGroup }
DESCRIPTION GROUP sipServerRegistrarUsersGroup
"A collection of objects providing configuration common to SIP DESCRIPTION
Proxy and Redirect servers." "This is an optional group."
::= { sipServerMIBGroups 1 } ::= { sipServerMIBCompliances 3 }
sipServerProxyConfigGroup OBJECT-GROUP --
OBJECTS { -- Units of Conformance
sipServerCfgProxyStatefulness, --
sipServerCfgProxyRecursion, sipServerConfigGroup OBJECT-GROUP
sipServerCfgProxyRecordRoute, OBJECTS {
sipServerCfgProxyAuthMethod, sipServerCfgHostAddressType,
sipServerCfgProxyAuthDefaultRealm sipServerCfgHostAddress
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration for SIP Proxy
servers."
::= { sipServerMIBGroups 2 }
sipServerProxyStatsGroup OBJECT-GROUP }
OBJECTS { STATUS current
sipServerProxyStatProxyReqFailures, DESCRIPTION
sipServerProxyStatsDisconTime "A collection of objects providing configuration common to SIP
} Proxy and Redirect servers."
STATUS current ::= { sipServerMIBGroups 1 }
DESCRIPTION
"A collection of objects providing statistics for SIP Proxy
servers."
::= { sipServerMIBGroups 3 }
sipServerRegistrarConfigGroup OBJECT-GROUP sipServerProxyConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipServerRegMaxContactExpiryDuration, sipServerCfgProxyStatefulness,
sipServerRegMaxUsers, sipServerCfgProxyRecursion,
sipServerRegCurrentUsers, sipServerCfgProxyRecordRoute,
sipServerRegDfltRegActiveInterval sipServerCfgProxyAuthMethod,
} sipServerCfgProxyAuthDefaultRealm
STATUS current }
DESCRIPTION STATUS current
"A collection of objects providing configuration for SIP DESCRIPTION
Registrars." "A collection of objects providing configuration for SIP Proxy
::= { sipServerMIBGroups 4 } servers."
::= { sipServerMIBGroups 2 }
sipServerRegistrarStatsGroup OBJECT-GROUP sipServerProxyStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipServerRegStatsAcceptedRegs, sipServerProxyStatProxyReqFailures,
sipServerRegStatsRejectedRegs, sipServerProxyStatsDisconTime
sipServerRegStatsDisconTime }
} STATUS current
STATUS current DESCRIPTION
DESCRIPTION "A collection of objects providing statistics for SIP Proxy
"A collection of objects providing statistics for SIP servers."
Registrars." ::= { sipServerMIBGroups 3 }
::= { sipServerMIBGroups 5 }
sipServerRegistrarUsersGroup OBJECT-GROUP sipServerRegistrarConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipServerRegUserUri, sipServerRegMaxContactExpiryDuration,
sipServerRegUserAuthenticationFailures, sipServerRegMaxUsers,
sipServerRegUserDisconTime, sipServerRegCurrentUsers,
sipServerRegContactDisplayName, sipServerRegDfltRegActiveInterval
sipServerRegContactURI, }
sipServerRegContactLastUpdated, STATUS current
sipServerRegContactExpiry, DESCRIPTION
sipServerRegContactPreference "A collection of objects providing configuration for SIP
} Registrars."
STATUS current ::= { sipServerMIBGroups 4 }
DESCRIPTION
"A collection of objects related to registered users."
::= { sipServerMIBGroups 6 }
END sipServerRegistrarStatsGroup OBJECT-GROUP
OBJECTS {
sipServerRegStatsAcceptedRegs,
sipServerRegStatsRejectedRegs,
sipServerRegStatsDisconTime
}
STATUS current
DESCRIPTION
"A collection of objects providing statistics for SIP
Registrars."
::= { sipServerMIBGroups 5 }
sipServerRegistrarUsersGroup OBJECT-GROUP
OBJECTS {
sipServerRegUserUri,
sipServerRegUserAuthenticationFailures,
sipServerRegUserDisconTime,
sipServerRegContactDisplayName,
sipServerRegContactURI,
sipServerRegContactLastUpdated,
sipServerRegContactExpiry,
sipServerRegContactPreference
}
STATUS current
DESCRIPTION
"A collection of objects related to registered users."
::= { sipServerMIBGroups 6 }
END
8. IANA Considerations 8. IANA Considerations
The MIB modules defined in this document use the following IANA- The MIB modules defined in this document use the following IANA-
assigned OBJECT IDENTIFIER values recorded in the SMI Numbers assigned OBJECT IDENTIFIER values recorded in the SMI Numbers
registry: registry:
+--------------+-------------------------+ +--------------+-------------------------+
| Descriptor | OBJECT IDENTIFIER value | | Descriptor | OBJECT IDENTIFIER value |
+--------------+-------------------------+ +--------------+-------------------------+
| sipTC | { mib-2 XXX1 } | | sipTC | { mib-2 148 } |
| sipCommonMIB | { mib-2 XXX2 } | | sipCommonMIB | { mib-2 149 } |
| sipUAMIB | { mib-2 XXX3 } | | sipUAMIB | { mib-2 150 } |
| sipServerMIB | { mib-2 XXX4} | | sipServerMIB | { mib-2 151 } |
+--------------+-------------------------+ +--------------+-------------------------+
-- RFC Ed:(note to be removed prior to publication): the IANA is
requested to assign 4 values in the SMI Numbers registry for "XXX1",
"XXX2", "XXX3", and "XXX4", all under the 'mib-2' sub-tree and to
record the assignments in the SMI Numbers registry. When the
assignments have been made, the RFC Editor is asked to replace "XXX1"
through "XXX4" (here and in the 4 MIB modules) with the corresponding
assigned value and to remove this note.
9. Security Considerations 9. Security Considerations
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 operati