draft-ietf-sip-mib-03.txt   draft-ietf-sip-mib-04.txt 
Internet Engineering Task Force K. Lingle Internet Engineering Task Force K. Lingle
Internet Draft Cisco Systems Internet Draft Cisco Systems
Document: draft-ietf-sip-mib-03.txt J. Maeng Document: draft-ietf-sip-mib-04.txt J. Maeng
June 2001 ipDialog, Inc. February 2002 ipDialog, Inc.
Expires: December 2001 J-F. Mule Expires: August 2002 J-F. Mule
Clarent Corp. CableLabs
D. Walker D. Walker
SS8 Networks, Inc. SS8 Networks, Inc.
Management Information Base Management Information Base
for Session Initiation Protocol for Session Initiation Protocol
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
skipping to change at page 2, line 7 skipping to change at page 2, line 7
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that are used In particular, it describes a set of managed objects that are used
to manage Session Initiation Protocol (SIP) entities, which include to manage Session Initiation Protocol (SIP) entities, which include
User Agents, Proxy servers, Redirect servers and Registrars. User Agents, Proxy servers, Redirect servers and Registrars.
Table of Contents Table of Contents
Abstract..........................................................1 Abstract...........................................................1
1. Introduction...................................................2 1. Introduction...................................................2
2. The SNMP Management Framework..................................2 2. The SNMP Management Framework..................................2
3. Overview.......................................................3 3. Overview.......................................................3
4. Structure of SIP MIB...........................................3 4. Structure of SIP MIB...........................................3
4.1. Textual Conventions..........................................4 4.1. Textual Conventions..........................................4
4.2. Relationship to Other MIB....................................5 4.2. Relationship to Other MIBs...................................5
5. Definitions....................................................8 5. Definitions....................................................8
5.1. SIP Textual Conventions......................................8 5.1. SIP Textual Conventions......................................8
5.2. SIP Common...................................................9 5.2. SIP Common...................................................9
5.3. SIP User Agent..............................................57 5.3. SIP User Agent..............................................61
5.4. SIP Server (Registrar, Redirect & Proxy Server).............61 5.4. SIP Server (Registrar, Redirect & Proxy Server).............65
6. Changes from previous drafts..................................80 6. Changes from previous drafts..................................84
7. Security Considerations.......................................81 7. Security Considerations.......................................89
8. Intellectual Property.........................................81 8. Intellectual Property.........................................89
9. Full Copyright Statement......................................82 9. Full Copyright Statement......................................90
10. References..................................................83 10. References..................................................91
11. Author's Addresses..........................................84 11. Author's Addresses..........................................92
1. 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 In particular, it describes a set of managed objects that are used
to schedule management operations periodically or at specified dates to manage Session Initiation Protocol (SIP) entities, which include
and times. User Agents, Proxy servers, Redirect servers and Registrars.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [16]. document are to be interpreted as described in RFC 2119 [16].
2. The SNMP Management Framework 2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
skipping to change at page 3, line 29 skipping to change at page 3, line 29
A more detailed introduction to the current SNMP Management A more detailed introduction to the current SNMP Management
Framework can be found in RFC 2570 [20]. Framework can be found in RFC 2570 [20].
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. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB MUST be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine-readable translation is possible (use of Counter64). Some machine-readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine- SMIv1 during the translation process. However, this loss of machine-
readable information is not considered to change the semantics of readable information is not considered to change the semantics of
the MIB. the MIB.
3. Overview 3. Overview
The Session Initiation Protocol (SIP) [17] is an application-layer The Session Initiation Protocol (SIP) [17] is an application-layer
skipping to change at page 3, line 53 skipping to change at page 3, line 53
server and Registrar. It is provided as a base for the work within server and Registrar. It is provided as a base for the work within
the working group to define a MIB. the working group to define a MIB.
This MIB is intended to provide management of the basic SIP This MIB is intended to provide management of the basic SIP
entities. It provides for monitoring of status and protocol entities. It provides for monitoring of status and protocol
statistics, as well as for configuration of SIP entities. It also statistics, as well as for configuration of SIP entities. It also
includes objects for the SIP INFO method [19]. includes objects for the SIP INFO method [19].
4. Structure of SIP MIB 4. Structure of SIP MIB
This memo specifies five MIB modules. They are SIP-MIB-SMI, SIP- This memo specifies four MIB modules. They are SIP-COMMON-MIB, SIP-
COMMON-MIB, SIP-SERVER-MIB, SIP-UA-MIB and SIP-TC. SIP-MIB-SMI SERVER-MIB, SIP-UA-MIB and SIP-TC. SIP-COMMON-MIB contains common
indicates the root OID of SIP MIB modules. SIP-COMMON-MIB contains objects used in all the SIP entities. SIP-SERVER-MIB contains
common objects used in all the SIP entities such as Registrars, objects specific to Registrars, Proxies and Redirect servers, and
Proxy Servers, Redirect Servers and User Agents. SIP-SERVER-MIB and SIP-UA-MIB includes objects specific to User Agents. SIP-TC defines
SIP-UA-MIB includes objects defined for Registrars, Proxy Redirect the textual conventions used throughout MIB modules.
servers and User Agents, respectively. SIP-TC defines the textual
conventions used throughout MIB modules.
Each MIB Module contains following groups of objects: The MIB Modules contain following groups of objects:
-- SIP-COMMON-MIB: Common to all the SIP entities -- SIP-COMMON-MIB: Common to all the SIP entities
sipCommonConfigGroup, sipCommonConfigGroup,
sipCommonStatsGroup, sipCommonStatsGroup,
sipCommonConfigTimerGroup, sipCommonConfigTimerGroup,
sipCommonConfigTimerExtMethodGroup, sipCommonConfigTimerExtMethodGroup,
sipCommonConfigRetryGroup, sipCommonConfigRetryGroup,
sipCommonConfigRetryExtMethodGroup, sipCommonConfigRetryExtMethodGroup,
sipCommonStatsRetryGroup, sipCommonStatsRetryGroup,
sipCommonStatsRetryExtMethodsGroup, sipCommonStatsRetryExtMethodsGroup,
skipping to change at page 4, line 36 skipping to change at page 4, line 34
-- Redirect Servers -- Redirect Servers
sipServerConfigGroup, sipServerConfigGroup,
sipProxyConfigGroup, sipProxyConfigGroup,
sipProxyStatsGroup, sipProxyStatsGroup,
sipRegistrarConfigGroup, sipRegistrarConfigGroup,
sipRegistrarStatsGroup. sipRegistrarStatsGroup.
-- SIP-UA-MIB: Groups of objects for User Agents -- SIP-UA-MIB: Groups of objects for User Agents
sipUAConfigGroup sipUAConfigGroup
It is required to implement SIP-COMMON-MIB together with its own MIB To conform with this specification, an SNMP agent MUST implement
module in Registrars, Proxy Servers, Redirect Servers and User SIP-TC, plus one instance of SIP-COMMON-MIB and one instance of the
Agents. For instance, a SIP Registrar will need four MIB modules, SIP entity-type-specific MIB (SIP-SERVER-MIB or SIP-UA-MIB) as
SIP-MIB-SMI, SIP-COMMON-MIB, SIP-SERVER-MIB, and SIP-TC in order to applicable for each instance of a SIP entity being managed. If a
provide a complete set of objects. If a device has more than one sip device has more than one sip entity or multiple instances of the
entity or multiple instances of the same entity, it should implement same entity, it SHOULD implement multiple SIP modules. Section 4.2
multiple SIP modules. Section 4.2 describes handling of multiple describes handling of multiple instances in detail.
instances in detail.
4.1. Textual Conventions 4.1. Textual Conventions
The data type SipTransportProtocol is used as textual conventions in The data type SipTransportProtocol is used as textual conventions in
this document. These textual conventions have NO effect on either this document. These textual conventions have NO effect on either
the syntax or the semantics of any managed object. Objects defined the syntax or the semantics of any managed object. Objects defined
using these conventions are always encoded by means of the rules using these conventions are always encoded by means of the rules
that define their primitive type. Hence, no changes to the SMI or that define their primitive type. Hence, no changes to the SMI or
the SNMP are necessary to accommodate these textual conventions, the SNMP are necessary to accommodate these textual conventions,
which are adopted merely for the convenience of readers. which are adopted merely for the convenience of readers.
4.2. Relationship to Other MIB 4.2. Relationship to Other MIBs
There is a requirement to be able to support multiple instances of There is a requirement to be able to support multiple instances of
SIP MIB modules in the context of a single system having a single various SIP MIB modules in the context of a single system having a
SNMP agent. single SNMP agent.
It is also possible to have multiple instances of a particular type
of SIP entity running on the same system. For example, there may be
Registrars for different domains with completely different
behaviors.
While there are separate MIB modules defined for SIP User Agents and
SIP servers, there is also a "common" MIB module expected to be
supported by every SIP entity. Further, all SIP entities are either
acting as a UAC, UAS or perhaps both. So a SIP Proxy Server must
support the SIP-SERVER-MIB and SIP-COMMON-MIB modules. Likewise,
the Registrar must support the SIP-SERVER-MIB and SIP-COMMON-MIB
modules. Here we have the requirement for supporting multiple
instances of a particular MIB module in one system.
This requirement is solved by using the framework provided by the This requirement is solved by using the framework provided by the
NETWORK-SERVICES-MIB, RFC 2788 [18]. A device implementing the SIP NETWORK-SERVICES-MIB, RFC 2788 [18]. A device implementing the SIP
MIB MUST support the NETWORK-SERVICES-MIB and, at a minimum, it MUST MIB MUST support the NETWORK-SERVICES-MIB and, at a minimum, it MUST
support the applIndex and applName objects in applTable. The support the applIndex and applName objects in applTable. The
following applName conventions will be adopted: following applName conventions will be adopted:
o for a SIP Proxy entity, applName must be equal to "sip_proxy" o for a SIP Proxy entity, applName MUST be equal to "sip_proxy"
o for a SIP Redirect entity, applName must be equal to o for a SIP Redirect entity, applName MUST be equal to
"sip_redirect" "sip_redirect"
o for a SIP Registrar entity, applName must be equal to o for a SIP Registrar entity, applName MUST be equal to
"sip_registrar" "sip_registrar"
o for a SIP User Agent entity, applName must be equal to o for a SIP User Agent entity, applName MUST be equal to
"sip_ua" "sip_ua"
o for a SIP entity acting in any combination of Proxy, Redirect, o for any combination of Proxy, Registrar, or Redirect Server
or Registrar, AND wishing to support only a single instance of being managed as a single aggregate entity, the applName for
the SIP-COMMON-MIB, the applName for the combined server the combined server entity MUST reflect the appropriate
entity must reflect the appropriate combination. For example, combination. For example, "sip_proxy_redirect" or
"sip_proxy_redirect" or "sip_proxy_registrar". "sip_proxy_registrar".
Additionally, the following objects may be supported in applTable. The SNMP agent MAY support any combination of the other attributes
If they are, the object values SHOULD be populated as follows: in applTable. If the following objects are supported, the object
values SHOULD be populated as follows:
o applVersion: version of the SIP application; if the SIP o applVersion: version of the SIP application; if the SIP
protocol version is used, the value MUST be as defined in SIP protocol version is used, the value MUST be as defined in SIP
[17], section 4.3.1. [17], section 4.3.1.
o applUptime: value must be identical to sipServiceStartTime o applUptime: value MUST be identical to sipServiceStartTime
defined in the SIP-COMMON module, defined in the SIP-COMMON-MIB module,
o applOperStatus: value should reflect the operational status o applOperStatus: value SHOULD reflect the operational status
defined in sipServiceOperStatus, at least by means of a defined in sipServiceOperStatus, at least by means of a
mapping, mapping,
o applLastChange: value must be identical to o applLastChange: value MUST be identical to
sipServiceLastChange defined in the SIP-COMMON module. sipServiceLastChange defined in the SIP-COMMON module.
Note: There are a number of other objects in the applTable. They Note: There are a number of other objects in the applTable. They
are not included for the sake of brevity and for the fact that they are not included for the sake of brevity and for the fact that they
do not enhance the concept being presented. do not enhance the concept being presented.
Example 1: The table below illustrates how it would conceptually Example 1:
appear in a system acting as both, a Proxy and Registrar server and
wishing to maintain separate SIP-COMMON-MIB instances.
The NETWORK-SERVICES-MIB applTable would 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 applIndex | applName | applDescription
----------+-----------------+------------------------------ ----------+-----------------+------------------------------
1 | "sip_proxy" | "ACME SIP Proxy" 1 | "sip_proxy" | "ACME SIP Proxy"
----------+-----------------+------------------------------ ----------+-----------------+------------------------------
2 | "sip_registrar" | "ACME SIP Registrar" 2 | "sip_registrar" | "ACME SIP Registrar"
----------+-----------------+------------------------------ ----------+-----------------+------------------------------
The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for
the 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 The SIP-SERVER-MIB tables would, however, only be populated with one
row indexed by applIndex=1 and applIndex=2 respectively if the row indexed by applIndex=1 and applIndex=2 respectively if the
server provides either proxy or registrar. server provides either proxy or registrar.
SIP-COMMON-MIB sipCommonCfgTable might be populated as: SIP-COMMON-MIB sipCommonCfgTable might be populated as:
applIndex | sipProtocolVersion | sipServiceOperStatus | ... applIndex | sipProtocolVersion | sipServiceOperStatus | ...
----------+--------------------+----------------------+---- ----------+--------------------+----------------------+----
1 | "SIP/2.0" | up(1) | 1 | "SIP/2.0" | up(1) |
----------+--------------------+----------------------+---- ----------+--------------------+----------------------+----
2 | "SIP/2.0" | restarting(6) | 2 | "SIP/2.0" | restarting(4) |
----------+--------------------+----------------------+---- ----------+--------------------+----------------------+----
while sipProxyCfgTable in SIP-SERVER-MIB is populated as: while sipProxyCfgTable in SIP-SERVER-MIB might be populated as:
applIndex | sipRequestMaxExpires | sipProxyStateful | ... applIndex | sipRequestMaxExpires | sipProxyStatefulness | ...
----------+----------------------+------------------+---- ----------+----------------------+----------------------+----
1 | 3600 | false | 1 | 3600 | stateless(1) |
----------+----------------------+------------------+---- ----------+----------------------+----------------------+----
and sipRegUserTable in SIP-SERVER-MIB is populated as: and sipRegUserTable in SIP-SERVER-MIB might be populated as:
applIndex | sipUserIndex | sipUserUri | ... applIndex | sipUserIndex | sipUserUri | ...
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 1 | drwalker@ss8.com | 2 | 1 | drwalker@ss8.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 2 | jmaeng@ipdialog.com | 2 | 2 | jmaeng@ipdialog.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 3 | klingle@cisco.com | 2 | 3 | klingle@cisco.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 4 | jfm@clarent.com | 2 | 4 | jf.mule@cablelabs.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
Example 2: The next table illustrates how it would conceptually
appear in a system acting as both, a Proxy and Registrar server and
wishing to share a single instance of SIP-COMMON-MIB.
The NETWORK-SERVICES-MIB applTable would be populated as follows: Example 2:
This example illustrates how to represent a system acting as both
Proxy and Registrar server, where the two entities share a single
instance of SIP-COMMON-MIB.
The NETWORK-SERVICES-MIB applTable might be populated as follows:
applIndex | applName | applDescription applIndex | applName | applDescription
----------+----------------------+--------------------------- ----------+----------------------+---------------------------
1 | "sip_proxy_registrar"| "ACME SIP Proxy&Registrar" 1 | "sip_proxy_registrar"| "ACME SIP Proxy&Registrar"
----------+----------------------+--------------------------- ----------+----------------------+---------------------------
The SIP-COMMON-MIB sipCommonCfgTable would have only one row to The SIP-COMMON-MIB sipCommonCfgTable would have only one row to
cover both the proxy and the registrar. cover both the proxy and the registrar.
SIP-COMMON-MIB sipCommonCfgTable might be populated as: SIP-COMMON-MIB sipCommonCfgTable might be populated as:
applIndex | sipProtocolVersion | sipServiceOperStatus | ... applIndex | sipProtocolVersion | sipServiceOperStatus | ...
----------+--------------------+----------------------+---- ----------+--------------------+----------------------+----
1 | "SIP/2.0" | up(1) | 1 | "SIP/2.0" | up(1) |
----------+--------------------+----------------------+---- ----------+--------------------+----------------------+----
skipping to change at page 7, line 27 skipping to change at page 7, line 16
SIP-COMMON-MIB sipCommonCfgTable might be populated as: SIP-COMMON-MIB sipCommonCfgTable might be populated as:
applIndex | sipProtocolVersion | sipServiceOperStatus | ... applIndex | sipProtocolVersion | sipServiceOperStatus | ...
----------+--------------------+----------------------+---- ----------+--------------------+----------------------+----
1 | "SIP/2.0" | up(1) | 1 | "SIP/2.0" | up(1) |
----------+--------------------+----------------------+---- ----------+--------------------+----------------------+----
while sipProxyCfgTable in SIP-SERVER-MIB is populated as: while sipProxyCfgTable in SIP-SERVER-MIB is populated as:
applIndex | sipRequestMaxExpires | sipProxyStateful | ... applIndex | sipRequestMaxExpires | sipProxyStatefulness | ...
----------+----------------------+------------------+---- ----------+----------------------+----------------------+----
1 | 3600 | false | 1 | 3600 | stateless(1) |
----------+----------------------+------------------+---- ----------+----------------------+----------------------+----
and sipRegUserTable in SIP-SERVER-MIB is populated as: and sipRegUserTable in SIP-SERVER-MIB might be populated as:
applIndex | sipUserIndex | sipUserUri | ... applIndex | sipUserIndex | sipUserUri | ...
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
1 | 1 | drwalker@ss8networks.com | 1 | 1 | drwalker@ss8networks.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
1 | 2 | jmaeng@ipdialog.com | 1 | 2 | jmaeng@ipdialog.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
1 | 3 | klingle@cisco.com | 1 | 3 | klingle@cisco.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
1 | 4 | jfm@clarent.com | 1 | 4 | jf.mule@cablelabs.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
The NETWORK-SERVICES-MIB assocTable is not considered a requirement The NETWORK-SERVICES-MIB assocTable is not considered a requirement
for SIP systems. It is not a mandatory group for NETWORK-SERVICES- for SIP systems. It is not a mandatory group for NETWORK-SERVICES-
MIB compliance. MIB compliance.
5. Definitions 5. Definitions
5.1. SIP Textual Conventions 5.1. SIP Textual Conventions
skipping to change at page 8, line 20 skipping to change at page 8, line 20
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
sipTC MODULE-IDENTITY sipTC MODULE-IDENTITY
LAST-UPDATED "200106060000Z" LAST-UPDATED "200202040000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO CONTACT-INFO
"SIP MIB Team email: sip-mib@yahoogroups.com "SIP MIB email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
skipping to change at page 8, line 51 skipping to change at page 8, line 51
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
postal: 495 March Road postal: 495 March Road
Kanata, ON K2K 3G1 Kanata, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: drwalker@ss8.com
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
Clarent Corporation CableLabs
700 Chesapeake Drive postal: 400 Centennial Parkway
Redwood City, CA 94063 Louisville, CO 80027
USA USA
email: jfm@clarent.com email: jf.mule@cablelabs.com
phone: +1 650 481 2835" phone: +1 303 661 3708 "
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Initial version of Session Initiation Protocol (SIP)
MIB Textual Conventions module used by other MIB Textual Conventions module used by other
SIP-related MIB Modules." SIP-related MIB Modules."
::= { mib-2 9992 } -- to be assigned by IANA ::= { mib-2 9992 } -- to be assigned by IANA
-- --
-- Textual Conventions -- Textual Conventions
-- --
SipTransportProtocol ::= TEXTUAL-CONVENTION SipTransportProtocol ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention is a bit map. Each bit represents a "This convention is a bit map. Each bit represents a
transport protocol. If a bit has value 1, then that transport protocol. If a bit has value 1, then that
transport protocol selected in some way dependent on selected transport protocol is in some way dependent
the context of the object using this convention. on the context of the object using this convention.
If a bit has value 0, then that transport protocol If a bit has value 0, then that transport protocol
is not selected. Combinations of bits can be is not selected. Combinations of bits can be
set when multiple transport protocols are selected. set when multiple transport protocols are selected.
bit 0 : a protocol other than those defined here. bit 0 : a protocol other than those defined here.
bit 1 : User Datagram Protocol. bit 1 : User Datagram Protocol.
bit 2 : Transmission Control Protocol. bit 2 : Transmission Control Protocol.
bit 3 : Stream Control Transmission Protocol. bit 3 : Stream Control Transmission Protocol.
bit 4 : Transport Layer Security Protocol." bit 4 : Transport Layer Security Protocol."
SYNTAX BITS { SYNTAX BITS {
skipping to change at page 10, line 20 skipping to change at page 10, line 20
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
SipTransportProtocol SipTransportProtocol
FROM SIP-TC FROM SIP-TC
applIndex applIndex
FROM NETWORK-SERVICES-MIB; FROM NETWORK-SERVICES-MIB;
sipCommonMIB MODULE-IDENTITY sipCommonMIB MODULE-IDENTITY
LAST-UPDATED "200106060000Z" LAST-UPDATED "200202040000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO CONTACT-INFO
"SIP MIB Team email: sip-mib@yahoogroups.com "SIP MIB email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
skipping to change at page 10, line 51 skipping to change at page 10, line 51
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
postal: 495 March Road postal: 495 March Road
Kanata, ON K2K 3G1 Kanata, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: drwalker@ss8.com
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
Clarent Corporation CableLabs
700 Chesapeake Drive postal: 400 Centennial Parkway
Redwood City, CA 94063 Louisville, CO 80027
USA USA
email: jfm@clarent.com email: jf.mule@cablelabs.com
phone: +1 650 481 2835" phone: +1 303 661 3708 "
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Initial version of Session Initiation Protocol (SIP)
Common MIB module. This module defines objects which Common MIB module. This module defines objects which
may be common to all SIP entities. may be common to all SIP entities.
SIP is an application-layer signalling protocol for SIP is an application-layer signalling protocol for
creating, modifying and terminating multimedia creating, modifying and terminating multimedia
sessions with one or more participants. These sessions sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 2543 (March telephone calls. SIP is defined in RFC 2543 (March
1999). 1999).
This MIB is defined for the managing objects which are This MIB is defined for managing objects which are
common to SIP User Agents (UAs), Proxy and Redirect common to SIP User Agents (UAs), Proxy and Redirect
Servers, and Registrars. Objects specific to each of Servers, and Registrars. Objects specific to each of
these entities may be managed using entity specific these entities may be managed using entity specific
MIBs defined in other modules. MIBs defined in other modules.
A User Agent is an application that contains both a A User Agent is an application that contains both a
User Agent Client (UAC) and a User Agent Server (UAS). User Agent Client (UAC) and a User Agent Server (UAS).
A UAC is an application that initiates a SIP request. A UAC is an application that initiates a SIP request.
A UAS is an application that contacts the user when a A UAS is an application that contacts the user when a
SIP request is received and that returns a response on SIP request is received and that returns a response on
skipping to change at page 11, line 53 skipping to change at page 11, line 53
sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 } sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 }
sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 } sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
sipCommonMIBConform OBJECT IDENTIFIER ::= { sipCommonMIB 2 } sipCommonMIBConform OBJECT IDENTIFIER ::= { sipCommonMIB 2 }
-- --
-- This MIB contains objects that are common to all SIP entities. -- This MIB contains objects that are common to all SIP entities.
-- --
sipCommonCfgBase OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 } sipCommonCfgBase OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 }
sipCommonCfgTimer OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 } sipCommonCfgTimer OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 }
sipCommonCfgRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 } sipCommonCfgRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 3 }
sipCommonStatsSummary OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 } sipCommonCfgExpires OBJECT IDENTIFIER ::= { sipCommonMIBObjects 4 }
sipCommonStatsMethod OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 } sipCommonStatsSummary OBJECT IDENTIFIER ::= { sipCommonMIBObjects 5 }
sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 } sipCommonStatsMethod OBJECT IDENTIFIER ::= { sipCommonMIBObjects 6 }
sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 } sipCommonStatusCode OBJECT IDENTIFIER ::= { sipCommonMIBObjects 7 }
sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 } sipCommonStatsTrans OBJECT IDENTIFIER ::= { sipCommonMIBObjects 8 }
sipCommonStatsOther OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 } sipCommonStatsRetry OBJECT IDENTIFIER ::= { sipCommonMIBObjects 9 }
sipCommonStatsOther OBJECT IDENTIFIER ::= { sipCommonMIBObjects 10 }
-- --
-- Common Configuration Objects -- Common Configuration Objects
-- --
sipCommonCfgTable OBJECT-TYPE sipCommonCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgEntry SYNTAX SEQUENCE OF SipCommonCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the common configuration objects "This table contains the common configuration objects
applicable to all SIP entities." applicable 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 those objects for a particular SIP Each row represents objects for a particular SIP
entity present in this system. applIndex is used to entity instance present in this system. applIndex
uniquely identify these instances of SIP entities and is used to uniquely identify these instances of SIP
correlate them through the common framework of the entities and correlate them through the common
NETWORK-SERVICES-MIB (RFC 2788)." framework of the NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipCommonCfgTable 1 } ::= { sipCommonCfgTable 1 }
SipCommonCfgEntry ::= SipCommonCfgEntry ::=
SEQUENCE { SEQUENCE {
sipProtocolVersion SnmpAdminString, sipProtocolVersion SnmpAdminString,
sipServiceOperStatus INTEGER, sipServiceOperStatus INTEGER,
sipServiceAdminStatus INTEGER, sipServiceAdminStatus INTEGER,
sipServiceStartTime TimeTicks, sipServiceStartTime TimeTicks,
sipServiceLastChange TimeTicks, sipServiceLastChange TimeTicks,
sipOrganization SnmpAdminString, sipOrganization SnmpAdminString,
sipMaxSessions Unsigned32, sipMaxSessions Unsigned32,
sipInviteTimeout Unsigned32,
sipRequestUriHostMatching TruthValue sipRequestUriHostMatching TruthValue
} }
sipProtocolVersion OBJECT-TYPE sipProtocolVersion OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will reflect the version of SIP supported by "This object will reflect the version of SIP supported by
this SIP entity. It will follow the same format as SIP this SIP entity. It will follow the same format as SIP
skipping to change at page 12, line 55 skipping to change at page 13, line 4
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object will reflect the version of SIP supported by "This object will reflect the version of SIP supported by
this SIP entity. It will follow the same format as SIP this SIP entity. It will follow the same format as SIP
version information contained in the SIP messages version information contained in the SIP messages
generated by this SIP entity. For example, entities generated by this SIP entity. For example, entities
supporting SIP version 2 will return 'SIP/2.0' as dictated supporting SIP version 2 will return 'SIP/2.0' as dictated
by RFC 2543." by RFC 2543."
::= { sipCommonCfgEntry 1 } ::= { sipCommonCfgEntry 1 }
sipServiceOperStatus OBJECT-TYPE sipServiceOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), up(1),
down(2), down(2),
testing(3), congested(3),
restarting(4),
unknown(4), quiescing(5),
halted(5), testing(6),
restarting(6) unknown(7)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the current operational state of the "This object contains the current operational state of the
SIP application. SIP application.
up(1) : The application is operating normally, and up(1) : The application is operating normally, and
is processing (receiving and possibly is processing (receiving and possibly
issuing) SIP requests and responses. issuing) SIP requests and responses.
down(2) : The application is currently unable to down(2) : The application is currently unable to
process SIP messages. process SIP messages.
testing(3) : The application is currently in test mode congested(3) : The application is operational but no
and may not be able to process SIP additional inbound transactions can be
messages. accomodated at the moment.
unknown(4) : The operational status of the application restarting(4) : The application is currently unavailable
cannot be determined for some reason. but it is in the process of restarting and
halted(5) : The application has been manually will, presumably, soon be able to process
prevented from processing SIP messages. SIP messages.
restarting(6) : The application is booting and will soon quiescing(5) : The application is currently operational
be able to process SIP messages." but has been administratively put into
quiese mode. Additional inbound transactions
may be rejected.
testing(6) : The application is currently in test mode
and may not be able to process SIP messages.
unknown(7) : The operational status cannot be determined
for some reason."
::= { sipCommonCfgEntry 2 } ::= { sipCommonCfgEntry 2 }
sipServiceAdminStatus OBJECT-TYPE sipServiceAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
shutdown(1), noop(1),
reset(2), up(2),
restart(3), down(3),
stop(4), reset(4),
rts(5) quieseSessions(5),
quieseApplication(6)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to affect the overall operational "This object is used to affect the overall operational
state of the SIP server application. state of the SIP application. When read, this object
always return a value of noop(1) since sipServiceOperStatus
reflects the actual operational status.
shutdown(1) : Immediately kill the application, don't noop(1) : Setting this object to a noop value
restart. has no effect; when read, this value
reset(2) : Restart application, reinitialize data, is always returned.
requires rts. up(2) : Enable the application.
restart(3) : Restart application, no data loss, requires down(3) : Abrupt shutdown. Immediately terminate.
rts. reset(4) : Restart application, reinitialize data.
stop(4) : Stop processing new requests, requires rts. quieseSessions(5) : Enable quiescence mode. Stop accepting
rts(5) : Return to service." any new SIP sessions. Stop processing
new transactions except for transactions
associated with an existing session or
call.
quieseApplications(6): Enable quiescence mode. Stop processing
new SIP transactions except for
transactions associated with existing
applications. The exact application
behavior should be specified by the
implementation."
::= { sipCommonCfgEntry 3 } ::= { sipCommonCfgEntry 3 }
sipServiceStartTime OBJECT-TYPE sipServiceStartTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the SIP entity was last "The value of sysUpTime at the time the SIP entity was last
started. If the current state was entered prior to the started. If started prior to the last re-initialization of
the local network management subsystem, then this object
last re-initialization of the local network management contains a zero value."
subsystem, then this object contains a zero value."
::= { sipCommonCfgEntry 4 } ::= { sipCommonCfgEntry 4 }
sipServiceLastChange OBJECT-TYPE sipServiceLastChange OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the SIP entity entered "The value of sysUpTime at the time the SIP entity entered
its current operational state. If the current state was its current operational state. If the current state was
entered prior to the last re-initialization of the local entered prior to the last re-initialization of the local
network management subsystem, then this object contains a network management subsystem, then this object contains a
zero value." zero value."
::= { sipCommonCfgEntry 5 } ::= { sipCommonCfgEntry 5 }
sipOrganization OBJECT-TYPE sipOrganization OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the name of the organization issuing "This object contains the organization name which the SIP
the request or response. It may also be inserted by a entity inserts into Organization headers of SIP messages
proxy at a boundary of an organization. If the object processed by this system. If the sting is empty, no
exists, it is inserted into requests and responses." Organization header is to be generated."
REFERENCE REFERENCE
"RFC 2543, Section 6.24" "RFC 2543, Section 6.24"
::= { sipCommonCfgEntry 6 } ::= { sipCommonCfgEntry 6 }
sipMaxSessions OBJECT-TYPE sipMaxSessions OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum number of simultaneous "This object indicates the maximum number of simultaneous
sessions that the SIP entity can manage." sessions that the SIP entity can manage."
::= { sipCommonCfgEntry 7 } ::= { sipCommonCfgEntry 7 }
sipInviteTimeout OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"For user agent clients, this value is inserted into the
Expires header.
For proxy servers, if a received request contained an
Expires header, then the value in the header takes
precedence. The server returns a 408 Request Timeout if
no response is received before
expiration of the request timer."
::= { sipCommonCfgEntry 8 }
sipRequestUriHostMatching OBJECT-TYPE sipRequestUriHostMatching OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the host in "This object specifies whether or not the host in
RequestURI must match server's host name. RequestURI must match server's host name.
If the value of this object is TRUE, then the server If the value of this object is ĉtrueĈ, then the server
requires a match, and if the RequestURI doesn't match the requires a match, and if the RequestURI doesn't match the
server's host name, a 404 Not Found status code is server's host name, a 404 Not Found status code is
returned by the server. returned by the server.
If the value is FALSE, then no match is required." If the value is ĉfalseĈ, then no match is required."
REFERENCE REFERENCE
"RFC 2543, Section 4.3" "RFC 2543, Section 4.3"
::= { sipCommonCfgEntry 9 } ::= { sipCommonCfgEntry 8 }
-- --
-- Support for multiple ports -- Support for multiple ports
-- --
sipPortTable OBJECT-TYPE sipPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipPortEntry SYNTAX SEQUENCE OF SipPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the list of ports that each SIP entity "This table contains the list of ports that each SIP entity
skipping to change at page 16, line 50 skipping to change at page 16, line 57
::= { sipPortEntry 3 } ::= { sipPortEntry 3 }
sipPortStatus OBJECT-TYPE sipPortStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row status of the entry. This object is required to "The row status of the entry. This object is required to
create or delete rows remotely by a manager. The row create or delete rows remotely by a manager. The row
associated with port 5060 need not be created and cannot associated with port 5060 need not be created and cannot
be deleted. It is always present in the table." be deleted. It is always present in the table. It is
implementation specific as to whether objects in this table
can be set while a row is 'active'."
::= { sipPortEntry 4 } ::= { sipPortEntry 4 }
-- --
-- Support for multiple non-SIP URI schemes -- Support for multiple non-SIP URI schemes
-- --
sipUriSupportedTable OBJECT-TYPE sipUriSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUriSupportedEntry SYNTAX SEQUENCE OF SipUriSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of URI schemes supported by each "This table contains a list of URI schemes supported by each
SIP entity in this system. These are in addition to the SIP SIP entity in this system. These are in addition to the SIP
skipping to change at page 17, line 14 skipping to change at page 17, line 22
"This table contains a list of URI schemes supported by each "This table contains a list of URI schemes supported by each
SIP entity in this system. These are in addition to the SIP SIP entity in this system. These are in addition to the SIP
URL which must necessarily be supported. Normally the URL which must necessarily be supported. Normally the
list of URI schemes supported by an entity is static list of URI schemes supported by an entity is static
(i.e. will not change over time). (i.e. will not change over time).
A URI is a Uniform Resource Identifier (as defined in RFC A URI is a Uniform Resource Identifier (as defined in RFC
2396). 2396).
URI schemes could, for example, contain URLs for phones, fax, URI schemes could, for example, contain URLs for phones, fax,
or irc if they were defined) or a mailto: (RFC 2368) URL." or irc (if they were defined) or a mailto: (RFC 2368) URL."
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
::= { sipCommonCfgBase 3 } ::= { sipCommonCfgBase 3 }
sipUriSupportedEntry OBJECT-TYPE sipUriSupportedEntry OBJECT-TYPE
SYNTAX SipUriSupportedEntry SYNTAX SipUriSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular non-SIP URI supported by the SIP entity. "A particular non-SIP URI supported by the SIP entity.
skipping to change at page 18, line 15 skipping to change at page 18, line 24
-- --
-- Support for features which may be requested in Proxy-Require -- Support for features which may be requested in Proxy-Require
-- and Require headers -- and Require headers
-- --
sipFtrSupportedTable OBJECT-TYPE sipFtrSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipFtrSupportedEntry SYNTAX SEQUENCE OF SipFtrSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of the non-standard features "This table contains a list of the features
supported by each SIP entity in this system, and which supported by each SIP entity in this system, and which
may be required by a peer. Definition of such features is may be required by a peer. Definition of non-standard
features is outside the scope of SIP, which only provides
outside the scope of SIP, which only provides mechanisms mechanisms whereby support for specific features may be
whereby support for specific features may be signalled or signalled or requested.
requested.
For example, a user agent client may require that a server As and example of a non-standard feature, a user agent
support the 'com.example.billing' feature, which it would client may require that a server support the
'com.example.billing' feature, which it would
indicate in a Require header. Such a client would have indicate in a Require header. Such a client would have
a row in its sipFtrSupportedTable containing the string a row in its sipFtrSupportedTable containing the string
'com.example.billing'. Similarly, a server which is 'com.example.billing'. Similarly, a server which is
capable of handling requests for such features would list capable of handling requests for such features would list
the string in its sipFtrSupportedTable. the string in its sipFtrSupportedTable.
If a server does not support the required feature If a server does not support the required feature
(indicated in a Require header to a UAS, or in a Proxy- (indicated in a Require header to a UAS, or in a Proxy-
Require to a proxy server), the server returns a 420 Bad Require to a proxy server), the server returns a 420 Bad
Extension listing the feature in an Unsupported header. Extension listing the feature in an Unsupported header.
For IETF standardized features, the complete path
(eg, org.ietf.sip.xxx) should be reflected in this table.
Normally the list of such features supported by an entity Normally the list of such features supported by an entity
is static (i.e. will not change over time)." is static (i.e. will not change over time)."
REFERENCE REFERENCE
"RFC 2543, Sections 6.28, 6.30, and 6.38" "RFC 2543, Sections 6.28, 6.30, and 6.38"
::= { sipCommonCfgBase 4 } ::= { sipCommonCfgBase 4 }
sipFtrSupportedEntry OBJECT-TYPE sipFtrSupportedEntry OBJECT-TYPE
SYNTAX SipFtrSupportedEntry SYNTAX SipFtrSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular non-standard feature supported by the SIP "A particular feature supported by the SIP
entity, and which may be required by a peer. entity, and which may be required by a peer.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and uniquely identify these instances of SIP entities and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipFtrSupportedIndex } INDEX { applIndex, sipFtrSupportedIndex }
::= { sipFtrSupportedTable 1 } ::= { sipFtrSupportedTable 1 }
skipping to change at page 19, line 20 skipping to change at page 19, line 32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in the "This object uniquely identifies a conceptual row in the
table." table."
::= { sipFtrSupportedEntry 1 } ::= { sipFtrSupportedEntry 1 }
sipFtrSupported OBJECT-TYPE sipFtrSupported OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates a particular non-standard feature "This object indicates a particular feature
which is supported by the SIP entity." which is supported by the SIP entity."
::= { sipFtrSupportedEntry 2 } ::= { sipFtrSupportedEntry 2 }
-- --
-- SIP Timer Configuration -- SIP Timer Configuration
-- --
sipCommonCfgTimerTable OBJECT-TYPE sipCommonCfgTimerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgTimerEntry SYNTAX SEQUENCE OF SipCommonCfgTimerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 22, line 24 skipping to change at page 22, line 30
-- Initial Timers Extensions: support for extension methods -- Initial Timers Extensions: support for extension methods
-- --
sipCommonCfgTimerExtMethodTable OBJECT-TYPE sipCommonCfgTimerExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgTimerExtMethodEntry SYNTAX SEQUENCE OF SipCommonCfgTimerExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains retransmit timers for each SIP "This table contains retransmit timers for each SIP
extension method this entity supports. extension method this entity supports.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788).
The applicable T2 timer value for timers configured The applicable T2 timer value for timers configured
in this table is that of the sipCfgTimerT2 object in this table is that of the sipCfgTimerT2 object
with the same applIndex value." with the same applIndex value."
::= { sipCommonCfgTimer 2 } ::= { sipCommonCfgTimer 2 }
sipCommonCfgTimerExtMethodEntry OBJECT-TYPE sipCommonCfgTimerExtMethodEntry OBJECT-TYPE
SYNTAX SipCommonCfgTimerExtMethodEntry SYNTAX SipCommonCfgTimerExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains timer value information for "This row contains timer value information for
a particular extension method." a particular extension method.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipCfgTimerExtMethodIndex } INDEX { applIndex, sipCfgTimerExtMethodIndex }
::= { sipCommonCfgTimerExtMethodTable 1 } ::= { sipCommonCfgTimerExtMethodTable 1 }
SipCommonCfgTimerExtMethodEntry ::= SipCommonCfgTimerExtMethodEntry ::=
SEQUENCE { SEQUENCE {
sipCfgTimerExtMethodIndex Unsigned32, sipCfgTimerExtMethodIndex Unsigned32,
sipCfgTimerExtMethodName SnmpAdminString, sipCfgTimerExtMethodName SnmpAdminString,
sipCfgTimerExtMethodTimer Unsigned32, sipCfgTimerExtMethodTimer Unsigned32,
sipCfgTimerExtMethodStatus RowStatus sipCfgTimerExtMethodStatus RowStatus
} }
skipping to change at page 23, line 21 skipping to change at page 23, line 27
DESCRIPTION DESCRIPTION
"This object contains the name of the particular extension "This object contains the name of the particular extension
method the SIP entity supports. For example, it may method the SIP entity supports. For example, it may
contain the string 'REFER' if the REFER method is supported. contain the string 'REFER' if the REFER method is supported.
It is an error for any of the methods contained in RFC 2543 It is an error for any of the methods contained in RFC 2543
to be requested." to be requested."
::= { sipCommonCfgTimerExtMethodEntry 2 } ::= { sipCommonCfgTimerExtMethodEntry 2 }
sipCfgTimerExtMethodTimer OBJECT-TYPE sipCfgTimerExtMethodTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the time a SIP entity will wait "This object specifies the time a SIP entity will wait
for a response to the extension method request before for a response to the extension method request before
retransmitting. The retransmit timer doubles after retransmitting. The retransmit timer doubles after
each retransmission, ensuring an exponential backoff each retransmission, ensuring an exponential backoff
in network traffic." in network traffic."
DEFVAL { 500 }
::= { sipCommonCfgTimerExtMethodEntry 3 } ::= { sipCommonCfgTimerExtMethodEntry 3 }
sipCfgTimerExtMethodStatus OBJECT-TYPE sipCfgTimerExtMethodStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row status of the entry. This object is required "The row status of the entry. This object is required
to create or delete rows remotely by a manager. to create or delete rows remotely by a manager.
A value for sipCfgTimerExtMethodName must be set A value for sipCfgTimerExtMethodName and
sipCfgTimerExtMethodTimer must be set
for row creation to be successful. If that method for row creation to be successful. If that method
already exists for a particular applIndex, the row already exists for a particular applIndex, the row
create operation will fail." create operation will fail."
::= { sipCommonCfgTimerExtMethodEntry 4 } ::= { sipCommonCfgTimerExtMethodEntry 4 }
-- --
-- SIP Retry Configuration -- SIP Retry Configuration
-- --
sipCommonCfgRetryTable OBJECT-TYPE sipCommonCfgRetryTable OBJECT-TYPE
skipping to change at page 26, line 14 skipping to change at page 26, line 22
-- --
-- Retry Extensions: support for extension methods -- Retry Extensions: support for extension methods
-- --
sipCommonCfgRetryExtMethodTable OBJECT-TYPE sipCommonCfgRetryExtMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgRetryExtMethodEntry SYNTAX SEQUENCE OF SipCommonCfgRetryExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains retry configuration for each SIP "This table contains retry configuration for each SIP
extension method this entity supports." extension method this entity supports."
::= { sipCommonCfgTimer 3 } ::= { sipCommonCfgRetry 2 }
sipCommonCfgRetryExtMethodEntry OBJECT-TYPE sipCommonCfgRetryExtMethodEntry OBJECT-TYPE
SYNTAX SipCommonCfgRetryExtMethodEntry SYNTAX SipCommonCfgRetryExtMethodEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains retry configuration information for "This row contains retry configuration information for
a particular extension method. a particular extension method.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
skipping to change at page 27, line 14 skipping to change at page 27, line 22
::= { sipCommonCfgRetryExtMethodEntry 2 } ::= { sipCommonCfgRetryExtMethodEntry 2 }
sipCfgRetryExtMethodRetry OBJECT-TYPE sipCfgRetryExtMethodRetry OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the number of times a SIP entity "This object specifies the number of times a SIP entity
will retry sending its request for this particular will retry sending its request for this particular
extension method." extension method."
DEFVAL { 6 }
::= { sipCommonCfgRetryExtMethodEntry 3 } ::= { sipCommonCfgRetryExtMethodEntry 3 }
sipCfgRetryExtMethodStatus OBJECT-TYPE sipCfgRetryExtMethodStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row status of the entry. This object is required "The row status of the entry. This object is required
to create or delete rows remotely by a manager. to create or delete rows remotely by a manager.
A value for sipCfgRetryExtMethodName must be set A value for sipCfgRetryExtMethodName and
sipCfgRetryExtMethodRetry must be set
for row creation to be successful. If that method for row creation to be successful. If that method
already exists for a particular applIndex, the row already exists for a particular applIndex, the row
create operation will fail." create operation will fail."
::= { sipCommonCfgRetryExtMethodEntry 4 } ::= { sipCommonCfgRetryExtMethodEntry 4 }
-- --
-- Per Method Expires Configuration
--
sipCommonCfgExpiresMethodTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgExpiresMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains Expires header value configuration
objects applicable to SIP user agent and SIP stateful
proxy entities."
::= { sipCommonCfgExpires 1 }
sipCommonCfgExpiresMethodEntry OBJECT-TYPE
SYNTAX SipCommonCfgExpiresMethodEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row of Expires header configuration for SIP Methods.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex }
::= { sipCommonCfgExpiresMethodTable 1 }
SipCommonCfgExpiresMethodEntry ::=
SEQUENCE {
sipCfgExpiresInvite Unsigned32,
sipCfgExpiresRegister Unsigned32,
sipCfgExpiresHeaderMethod BITS
}
sipCfgExpiresInvite OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"For user agent clients, this value is inserted into the
Expires header.
For proxy servers, if a received request contained an
Expires header, then the value in the header takes
precedence."
::= { sipCommonCfgExpiresMethodEntry 1 }
sipCfgExpiresRegister OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"For user agent clients, this value is inserted into the
Expires header.
For registrar servers, if a received request contained an
Expires header, then the value in the header takes
precedence."
::= { sipCommonCfgExpiresMethodEntry 2 }
sipCfgExpiresHeaderMethod OBJECT-TYPE
SYNTAX BITS {
invite(0),
register(1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This convention is a bit map. Each bit represents a
sip method where the Expires header line must be present.
If a bit has value 1, then that messages corresponding
to that SIP method must include an Expires header line.
If a bit has value 0, then the Expires header line is
not present.
Combinations of bits can be set when the Expires header
line is required in multiple SIP methods.
bit 0 : INVITE method.
bit 1 : REGISTER Method."
::= { sipCommonCfgExpiresMethodEntry 3 }
sipCommonCfgExpiresStatusCodeTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgExpiresStatusCodeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the Expires header configuration
objects for the SIP responses."
::= { sipCommonCfgExpires 2 }
sipCommonCfgExpiresStatusCodeEntry OBJECT-TYPE
SYNTAX SipCommonCfgExpiresStatusCodeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This row contains information on the configuration of
the Expires header value for a particular SIP status
code. Examples of SIP responses that may include an
Expires header are 302 and 504.
Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and
correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex, sipCfgExpiresStatusCodeValue }
::= { sipCommonCfgExpiresStatusCodeTable 1 }
SipCommonCfgExpiresStatusCodeEntry ::=
SEQUENCE {
sipCfgExpiresStatusCodeValue INTEGER,
sipCfgExpiresHeaderValue Unsigned32,
sipCfgExpiresStatusCodeStatus RowStatus
}
sipCfgExpiresStatusCodeValue OBJECT-TYPE
SYNTAX INTEGER (100..999)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object contains a SIP status code value for which
the Expires header value is configured. All of the other
information in the row is related to this value."
::= { sipCommonCfgExpiresStatusCodeEntry 1 }
sipCfgExpiresHeaderValue OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value is inserted into the Expires header for the
specific status code."
::= { sipCommonCfgExpiresStatusCodeEntry 2 }
sipCfgExpiresStatusCodeStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is required to create or delete rows remotely
by a manager.
A value for sipCfgExpiresHeaderValue must be specified when
creating rows by setting this row status to 'createAndGo'.
The row will automatically transition to 'active'.
The configuration specified by an entry will be made
active when this object is set to 'active'."
::= { sipCommonCfgExpiresStatusCodeEntry 3 }
--
-- Common Statistics Objects -- Common Statistics Objects
-- --
-- --
-- Summary Statistics -- Summary Statistics
-- --
sipSummaryStatsTable OBJECT-TYPE sipSummaryStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipSummaryStatsEntry SYNTAX SEQUENCE OF SipSummaryStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 29, line 4 skipping to change at page 31, line 51
sipSummaryOutResponses OBJECT-TYPE sipSummaryOutResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the total number of SIP response "This object contains the total number of SIP response
messages sent (originated and relayed) by the SIP entity messages sent (originated and relayed) by the SIP entity
including retransmissions." including retransmissions."
::= { sipSummaryStatsEntry 4 } ::= { sipSummaryStatsEntry 4 }
sipSummaryTotalTransactions OBJECT-TYPE sipSummaryTotalTransactions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of transactions "This object contains a count of the number of transactions
completed or in progress. completed and in progress. It is not applicable to stateless
SIP proxy servers.
A SIP transaction occurs between a client and a server and A SIP transaction occurs between a client and a server and
comprises all messages from the first request sent from comprises all messages from the first request sent from
the client to the server up to a final (non-1xx) response the client to the server up to a final (non-1xx) response
sent from the server to the client. sent from the server to the client.
A transaction is identified by the CSeq sequence number A transaction is identified by the CSeq sequence number
within a single call leg. The ACK request has the same within a single call leg. The ACK request has the same
CSeq number as the corresponding INVITE request, but CSeq number as the corresponding INVITE request, but
comprises a transaction of its own. comprises a transaction of its own.
In the case of a forked request, all branches count as a In the case of a forked request, all branches count as a
single transaction." single transaction.
For a transaction stateless proxy, this counter is always 0."
::= { sipSummaryStatsEntry 5 } ::= { sipSummaryStatsEntry 5 }
-- --
-- SIP Method Statistics -- SIP Method Statistics
-- Total counts for each SIP method. -- Total counts for each SIP method.
-- --
sipMethodStatsTable OBJECT-TYPE sipMethodStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipMethodStatsEntry SYNTAX SEQUENCE OF SipMethodStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the per method statistics objects "This table contains the per method statistics objects
applicable to all SIP entities. Each row represents applicable to all SIP entities. Each row represents
skipping to change at page 34, line 38 skipping to change at page 37, line 38
the sipStatsExtMethodName column including retransmissions the sipStatsExtMethodName column including retransmissions
if appropriate for the method." if appropriate for the method."
::= { sipStatsExtMethodEntry 4 } ::= { sipStatsExtMethodEntry 4 }
sipStatsExtMethodStatus OBJECT-TYPE sipStatsExtMethodStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The row status of the entry. This object is required "The row status of the entry. This object is required
to create or delete rows remotely by a manager." to create or delete rows remotely by a manager.
If set to 'notInService', all counters values may be
reset to zero and any associated notifications will be
disabled. Associated notifications are specified in the
sipCommonStatusCodeNotifTable.
The configuration specified by an entry will be made
active when this object is set to 'active'."
::= { sipStatsExtMethodEntry 5 } ::= { sipStatsExtMethodEntry 5 }
-- --
-- SIP Response Status Codes -- SIP Response Status Codes
-- --
sipStatusCodesTable OBJECT-TYPE sipStatusCodesTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipStatusCodesEntry SYNTAX SEQUENCE OF SipStatusCodesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 35, line 26 skipping to change at page 38, line 35
sipStatsInfoClassOuts Counter32, sipStatsInfoClassOuts Counter32,
sipStatsSuccessClassIns Counter32, sipStatsSuccessClassIns Counter32,
sipStatsSuccessClassOuts Counter32, sipStatsSuccessClassOuts Counter32,
sipStatsRedirClassIns Counter32, sipStatsRedirClassIns Counter32,
sipStatsRedirClassOuts Counter32, sipStatsRedirClassOuts Counter32,
sipStatsReqFailClassIns Counter32, sipStatsReqFailClassIns Counter32,
sipStatsReqFailClassOuts Counter32, sipStatsReqFailClassOuts Counter32,
sipStatsServerFailClassIns Counter32, sipStatsServerFailClassIns Counter32,
sipStatsServerFailClassOuts Counter32, sipStatsServerFailClassOuts Counter32,
sipStatsGlobalFailClassIns Counter32, sipStatsGlobalFailClassIns Counter32,
sipStatsGlobalFailClassOuts Counter32 sipStatsGlobalFailClassOuts Counter32,
sipStatsOtherClassesIns Counter32,
sipStatsOtherClassesOuts Counter32
} }
sipStatsInfoClassIns OBJECT-TYPE sipStatsInfoClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of 1xx class "This object reflects the number of 1xx class
SIP responses received by the SIP entity. SIP responses received by the SIP entity.
This class of responses relates to providing some This class of responses relates to providing some
skipping to change at page 36, line 33 skipping to change at page 39, line 44
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.2" "RFC 2543, Sections 5.1.1 & 7.2"
::= { sipStatusCodesEntry 4 } ::= { sipStatusCodesEntry 4 }
sipStatsRedirClassIns OBJECT-TYPE sipStatsRedirClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of 3xx class SIP "This object reflects the number of 3xx class SIP
responses received by the SIP entity. This class of responses received by the SIP entity."
responses relate to call redirection actions taken
by a Redirect Server."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.3" "RFC 2543, Sections 5.1.1 & 7.3"
::= { sipStatusCodesEntry 5 } ::= { sipStatusCodesEntry 5 }
sipStatsRedirClassOuts OBJECT-TYPE sipStatsRedirClassOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of 3xx class SIP "This object reflects the number of 3xx class SIP
responses sent by the SIP entity. This class of responses sent by the SIP entity."
responses relate to call redirection actions taken
by a Redirect Server."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.3" "RFC 2543, Sections 5.1.1 & 7.3"
::= { sipStatusCodesEntry 6 } ::= { sipStatusCodesEntry 6 }
sipStatsReqFailClassIns OBJECT-TYPE sipStatsReqFailClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of 4xx class SIP "This object reflects the number of 4xx class SIP
responses received by the SIP entity. This class of responses received by the SIP entity. This class of
responses reflect request failure by a SIP entity responses reflect request failure by a SIP entity
providing a client function." providing a client function."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.4" "RFC 2543, Sections 5.1.1 & 7.4"
::= { sipStatusCodesEntry 7 } ::= { sipStatusCodesEntry 7 }
sipStatsReqFailClassOuts OBJECT-TYPE sipStatsReqFailClassOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 37, line 31 skipping to change at page 40, line 39
::= { sipStatusCodesEntry 8 } ::= { sipStatusCodesEntry 8 }
sipStatsServerFailClassIns OBJECT-TYPE sipStatsServerFailClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of 5xx class SIP "This object reflects the number of 5xx class SIP
responses received by the SIP entity. This class of responses received by the SIP entity. This class of
responses reflect failure responses received by a responses reflect failure responses received by a
SIP entity providing a client function. These SIP entity providing a client function."
responses are not definite failures and must not
terminate a search if other possible locations remain
untried."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5" "RFC 2543, Sections 5.1.1 & 7.5"
::= { sipStatusCodesEntry 9 } ::= { sipStatusCodesEntry 9 }
sipStatsServerFailClassOuts OBJECT-TYPE sipStatsServerFailClassOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of 5xx class SIP "This object reflects the number of 5xx class SIP
responses sent by the SIP entity. This class of responses sent by the SIP entity. This class of
responses reflect failure responses sent by a SIP responses reflect failure responses sent by a SIP
entity providing a server function. These entity providing a server function."
responses are not definite failures and must not
terminate a search if other possible locations remain
untried."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.5" "RFC 2543, Sections 5.1.1 & 7.5"
::= { sipStatusCodesEntry 10 } ::= { sipStatusCodesEntry 10 }
sipStatsGlobalFailClassIns OBJECT-TYPE sipStatsGlobalFailClassIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of 6xx class SIP "This object reflects the number of 6xx class SIP
responses received by the SIP entity. This class of responses received by the SIP entity. This class of
skipping to change at page 38, line 12 skipping to change at page 41, line 14
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of 6xx class SIP "This object reflects the number of 6xx class SIP
responses received by the SIP entity. This class of responses received by the SIP entity. This class of
responses reflect failure responses received by a responses reflect failure responses received by a
SIP entity providing a client function. SIP entity providing a client function.
The responses generally indicate that a server has The responses generally indicate that a server has
definitive information about a particular called party, definitive information about a particular called party,
not just the particular instance indicated in the not just the particular instance indicated in the
Request-URI. All further searches for this user are Request-URI."
doomed to failure and pending searches should be
terminated."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.6" "RFC 2543, Sections 5.1.1 & 7.6"
::= { sipStatusCodesEntry 11 } ::= { sipStatusCodesEntry 11 }
sipStatsGlobalFailClassOuts OBJECT-TYPE sipStatsGlobalFailClassOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of 6xx class SIP "This object reflects the number of 6xx class SIP
responses sent by the SIP entity. This class of responses sent by the SIP entity. This class of
responses reflect failure responses sent by a SIP responses reflect failure responses sent by a SIP
entity providing a server function. entity providing a server function.
The responses generally indicate that a server has The responses generally indicate that a server has
definitive information about a particular called party, definitive information about a particular called party,
not just the particular instance indicated in the not just the particular instance indicated in the
Request-URI. All further searches for this user are Request-URI."
doomed to failure and pending searches should be
terminated."
REFERENCE REFERENCE
"RFC 2543, Sections 5.1.1 & 7.6" "RFC 2543, Sections 5.1.1 & 7.6"
::= { sipStatusCodesEntry 12 } ::= { sipStatusCodesEntry 12 }
sipStatsOtherClassesIns OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of SIP responses
received by the SIP entity for status code response
classes other than 1xx, 2xx, 3xx, 4xx, 5xx, or 6xx."
::= { sipStatusCodesEntry 13 }
sipStatsOtherClassesOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the number of SIP responses
sent by the SIP entity for status code response
classes other than 1xx, 2xx, 3xx, 4xx, 5xx, or 6xx."
::= { sipStatusCodesEntry 14 }
-- --
-- support for specific status codes -- support for specific status codes
-- --
sipCommonStatusCodeTable OBJECT-TYPE sipCommonStatusCodeTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonStatusCodeEntry SYNTAX SEQUENCE OF SipCommonStatusCodeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the list of SIP status codes which "This table contains the list of SIP status codes which
each SIP entity in this system has been requested to each SIP entity in this system has been requested to
skipping to change at page 40, line 42 skipping to change at page 44, line 4
sipCommonStatusCodeNotifEntry OBJECT-TYPE sipCommonStatusCodeNotifEntry OBJECT-TYPE
SYNTAX SipCommonStatusCodeNotifEntry SYNTAX SipCommonStatusCodeNotifEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information controlling notifications "This row contains information controlling notifications
for a particular SIP status code that the SIP entity has for a particular SIP status code that the SIP entity has
been requested to monitor." been requested to monitor."
AUGMENTS { sipCommonStatusCodeEntry } AUGMENTS { sipCommonStatusCodeEntry }
::= { sipCommonStatusCodeNotifTable 1 } ::= { sipCommonStatusCodeNotifTable 1 }
SipCommonStatusCodeNotifEntry ::= SipCommonStatusCodeNotifEntry ::=
SEQUENCE { SEQUENCE {
sipCommonStatusCodeNotifSend TruthValue, sipCommonStatusCodeNotifSend TruthValue,
sipCommonStatusCodeNotifEmitMode INTEGER, sipCommonStatusCodeNotifEmitMode INTEGER,
sipCommonStatusCodeNotifThresh Unsigned32, sipCommonStatusCodeNotifThresh Unsigned32,
sipCommonStatusCodeNotifInterval TimeTicks sipCommonStatusCodeNotifInterval Unsigned32
} }
sipCommonStatusCodeNotifSend OBJECT-TYPE sipCommonStatusCodeNotifSend OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls whether a sipStatusCodeNotif "This object controls whether a sipStatusCodeNotif
is emitted when the status code value specified in is emitted when the status code value specified in
by sipCommonStatusCodeValue is sent or received. by sipCommonStatusCodeValue is sent or received.
If the value of this object is TRUE, then a notification If the value of this object is ĉtrueĈ, then a notification
is sent. If it is FALSE, no notification is sent. is sent. If it is ĉfalseĈ, no notification is sent.
Note well, that a notification may be emitted for Note well, that a notification may be emitted for
every msg sent or received that contains the particular every msg sent or received that contains the particular
status code. Depending on the status code involved, status code. Depending on the status code involved,
this can cause a significant number of notification this can cause a significant number of notification
emissions that could be detrimental to network performance. emissions that could be detrimental to network performance.
Managers are forewarned to be prudent in the use of Managers are forewarned to be prudent in the use of
this object to enable notifications. Look to this object to enable notifications. Look to
sipCommonStatusCodeNotifEmitMode for alternative sipCommonStatusCodeNotifEmitMode for alternative
controls for sipStatusCodeNotif emissions." controls for sipStatusCodeNotif emissions."
DEFVAL { false } DEFVAL { false }
skipping to change at page 41, line 27 skipping to change at page 44, line 44
sipCommonStatusCodeNotifEmitMode OBJECT-TYPE sipCommonStatusCodeNotifEmitMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
normal(1), normal(1),
oneShot(2), oneShot(2),
triggered(3) -- read-only triggered(3) -- read-only
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object sipCommonStatusCodeNotifSend must be set "The object sipCommonStatusCodeNotifSend must be set
to TRUE for the values of this object to have any to ĉtrueĈ for the values of this object to have any
effect. It is recommended that the desired emit mode effect. It is recommended that the desired emit mode
be established by this object prior to setting be established by this object prior to setting
sipCommonStatusCodeNotifSend to TRUE. sipCommonStatusCodeNotifSend to ĉtrueĈ.
This object specifies the mode for emissions of This object specifies the mode for emissions of
sipStatusCodeNotif notifications. sipStatusCodeNotif notifications.
normal : sipStatusCodeNotif notifications will normal : sipStatusCodeNotif notifications will
be emitted by the system for each be emitted by the system for each
SIP response messages sent or received SIP response messages sent or received
that contains the desired status code. that contains the desired status code.
oneShot : Only one sipStatusCodeNotif notification oneShot : Only one sipStatusCodeNotif notification
will be emitted. It will be the next will be emitted. It will be the next
skipping to change at page 42, line 17 skipping to change at page 45, line 36
"This object specifies the number of response messages "This object specifies the number of response messages
sent or received by this system that are considered sent or received by this system that are considered
excessive. Based on crossing that threshold, a excessive. Based on crossing that threshold, a
sipStatusCodeExceededNotif notification will be sent. sipStatusCodeExceededNotif notification will be sent.
The sipStatusCodeExceededNotif can be used as an The sipStatusCodeExceededNotif can be used as an
early warning mechanism in lieu of using sipStatusCodeNotif." early warning mechanism in lieu of using sipStatusCodeNotif."
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonStatusCodeNotifEntry 3 } ::= { sipCommonStatusCodeNotifEntry 3 }
sipCommonStatusCodeNotifInterval OBJECT-TYPE sipCommonStatusCodeNotifInterval OBJECT-TYPE
SYNTAX TimeTicks SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the time interval over which "This object specifies the time interval over which
if sipCommonStatusCodeThresh is exceeded a if sipCommonStatusCodeThresh is exceeded a
sipCommonStatusCodeThresh notification will be sent." sipCommonStatusCodeThresh notification will be sent."
DEFVAL { 6000 } -- 60 seconds DEFVAL { 60 }
::= { sipCommonStatusCodeNotifEntry 4 } ::= { sipCommonStatusCodeNotifEntry 4 }
-- --
-- support for status code notification attributes. -- support for status code notification attributes.
-- --
sipStatusCodeNotifTo OBJECT-TYPE sipStatusCodeNotifTo OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the To header in the "This object contains the value of the To header in the
message containing the status code that caused the message containing the status code that caused the
notification." notification. The header name will be part of
this object value.
For example, 'To: Watson ."
::= { sipCommonStatusCode 4 } ::= { sipCommonStatusCode 4 }
sipStatusCodeNotifFrom OBJECT-TYPE sipStatusCodeNotifFrom OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the From header in the "This object contains the value of the From header in the
message containing the status code that caused the message containing the status code that caused the
notification." notification. The header name will be part of
this object value.
For example, 'From: Watson '."
::= { sipCommonStatusCode 5 } ::= { sipCommonStatusCode 5 }
sipStatusCodeNotifCallId OBJECT-TYPE sipStatusCodeNotifCallId OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the CallId in the "This object contains the value of the CallId in the
message containing the status code that caused the message containing the status code that caused the
notification." notification. The header name will be part of
this object value.
For example, 'Call-ID: 5551212@information.com'."
::= { sipCommonStatusCode 6 } ::= { sipCommonStatusCode 6 }
sipStatusCodeNotifCSeq OBJECT-TYPE
sipStatusCodeNotifCSeq OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the CSeq value in the message "This object contains the CSeq value in the message
containing the status code that caused the notification." containing the status code that caused the notification.
The header name will be part of this object value.
For example, 'CSeq: 1722 INVITE'."
::= { sipCommonStatusCode 7 } ::= { sipCommonStatusCode 7 }
-- --
-- Transaction Statistics -- Transaction Statistics
-- --
sipCurrentTransTable OBJECT-TYPE sipCurrentTransTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCurrentTransEntry SYNTAX SEQUENCE OF SipCurrentTransEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on the transactions "This table contains information on the transactions
currently awaiting definitive responses by each SIP currently awaiting definitive responses by each SIP
entity in this system." entity in this system.
This table does not apply to transaction stateless
proxy servers."
::= { sipCommonStatsTrans 1 } ::= { sipCommonStatsTrans 1 }
sipCurrentTransEntry OBJECT-TYPE sipCurrentTransEntry OBJECT-TYPE
SYNTAX SipCurrentTransEntry SYNTAX SipCurrentTransEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular SIP entities' current "Information on a particular SIP entity's current
transactions. transactions.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and uniquely identify these instances of SIP entities and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipCurrentTransTable 1 } ::= { sipCurrentTransTable 1 }
skipping to change at page 44, line 4 skipping to change at page 47, line 31
SYNTAX Gauge32 (0..4294967295) SYNTAX Gauge32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the number of transactions awaiting "This object contains the number of transactions awaiting
definitive (non-1xx) response. In the case of a forked definitive (non-1xx) response. In the case of a forked
request, all branches count as a single transaction. The request, all branches count as a single transaction. The
value of this object will reflect the number of rows in value of this object will reflect the number of rows in
sipTransactionTable." sipTransactionTable."
::= { sipCurrentTransEntry 1 } ::= { sipCurrentTransEntry 1 }
sipTransactionTable OBJECT-TYPE sipTransactionTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipTransactionEntry SYNTAX SEQUENCE OF SipTransactionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on all of the transactions "This table contains information on all of the transactions
currently being processed (the count of such transactions currently being processed (the count of such transactions
is maintained in the sipCurrentTransactions object) by a is maintained in the sipCurrentTransactions object) by a
particular SIP entity in this system." particular SIP entity in this system.
This table does not apply to transaction stateless
proxy servers."
::= { sipCommonStatsTrans 2 } ::= { sipCommonStatsTrans 2 }
sipTransactionEntry OBJECT-TYPE sipTransactionEntry OBJECT-TYPE
SYNTAX SipTransactionEntry SYNTAX SipTransactionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular current transaction. "Information on a particular current transaction.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
skipping to change at page 44, line 41 skipping to change at page 48, line 14
SipTransactionEntry ::= SipTransactionEntry ::=
SEQUENCE { SEQUENCE {
sipTransIndex Unsigned32, sipTransIndex Unsigned32,
sipTransTo SnmpAdminString, sipTransTo SnmpAdminString,
sipTransFrom SnmpAdminString, sipTransFrom SnmpAdminString,
sipTransCallId SnmpAdminString, sipTransCallId SnmpAdminString,
sipTransCSeq Unsigned32, sipTransCSeq Unsigned32,
sipTransState INTEGER, sipTransState INTEGER,
sipTransNumOutstandingBranches Integer32, sipTransNumOutstandingBranches Integer32,
sipTransExpiry DateAndTime, sipTransExpiry DateAndTime,
sipTransCallingPartyContentType SnmpAdminString, sipTransMethod SnmpAdminString,
sipTransCalledPartyContentType SnmpAdminString sipTransActivityInfo SnmpAdminString
} }
sipTransIndex OBJECT-TYPE sipTransIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in the "This object uniquely identifies a conceptual row in the
table." table."
::= { sipTransactionEntry 1 } ::= { sipTransactionEntry 1 }
sipTransTo OBJECT-TYPE sipTransTo OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the To header in request "This object contains the value of the To header in request
message." message. The header name will be part of this object value.
For example, 'To: Watson ."
::= { sipTransactionEntry 2 } ::= { sipTransactionEntry 2 }
sipTransFrom OBJECT-TYPE sipTransFrom OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the From header in the "This object contains the value of the From header in the
request message." request message. The header name will be part of this
object value.
For example, 'From: Watson '."
::= { sipTransactionEntry 3 } ::= { sipTransactionEntry 3 }
sipTransCallId OBJECT-TYPE sipTransCallId OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the CallId value in the "This object contains the value of the CallId value in the
request message." request message. The header name will be part of this
object value.
For example, 'Call-ID: 5551212@information.com'."
::= { sipTransactionEntry 4 } ::= { sipTransactionEntry 4 }
sipTransCSeq OBJECT-TYPE sipTransCSeq OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the CSeq value for the current "This object contains the CSeq value for the current
transaction." transaction. The header name will be part of this
object value. For example, 'CSeq: 1722 INVITE'."
::= { sipTransactionEntry 5 } ::= { sipTransactionEntry 5 }
sipTransState OBJECT-TYPE sipTransState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
null(1), null(1),
initial(2), initial(2),
calling(3), calling(3),
ringing(4), ringing(4),
completed(5), completed(5),
callProceeding(6), callProceeding(6),
failure(7), failure(7),
success(8), success(8),
confirmed(9) confirmed(9)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the current state of the SIP "This object contains the current state of the SIP
transaction. transaction. Note that some of the object values
may only be applicable to some transaction types
(for example, INVITE and non-INVITE transaction
states differ).
null(1) : The SIP entity is not active. null(1) : The SIP entity is not active.
initial(2) : Prior to sending or receiving any initial(2) : Prior to sending or receiving any
request. request.
calling(3) : After sending the request and prior to calling(3) : After sending the request and prior to
receiving any response. receiving any response.
ringing(4) : After receiving one or more ringing(4) : After receiving one or more
informational (1xx) responses. informational (1xx) responses.
completed(5) : After ACK has been sent following completed(5) : After ACK has been sent following
reception of definitive response. reception of definitive response.
skipping to change at page 46, line 39 skipping to change at page 50, line 19
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an indication of when the transaction "This object contains an indication of when the transaction
will be considered to have timed out. This value is based will be considered to have timed out. This value is based
on the value in the Expires header, or the value of the on the value in the Expires header, or the value of the
sipInviteTimeout object if no Expires value was sipInviteTimeout object if no Expires value was
specified in the original request." specified in the original request."
::= { sipTransactionEntry 8 } ::= { sipTransactionEntry 8 }
sipTransCallingPartyContentType OBJECT-TYPE sipTransMethod OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the content type of the transaction, "This object reflects the SIP method which initiated
including parameters, as indicated by the session the transaction."
initiator. All optional white space is removed from
subfields in the media-type specification. It may
indicate mime multipart, in which case the multiple
entries are separated by spaces."
REFERENCE
"RFC 2543, Section 6.16 and RFC 2068 section 3.7"
::= { sipTransactionEntry 9 } ::= { sipTransactionEntry 9 }
sipTransCalledPartyContentType OBJECT-TYPE sipTransActivityInfo OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the content type of the transaction, "This object contains an informational string about the
including parameters, as indicated by the session latest activity on this transaction. The string is made
respondant. All optional white space is removed from up of 2 elements separated by a space character: the first
subfields in the media-type specification. It may element indicates the direction of the latest message
indicate mime multipart, in which case the multiple (received or sent) and the second element is the SIP request
entries are separated by spaces." name or SIP response code.
REFERENCE Examples of valid strings are:
"RFC 2543, Section 6.16 and RFC 2068, Section 3.7" sent 100
received INVITE
sent BYE
received 200"
::= { sipTransactionEntry 10 } ::= { sipTransactionEntry 10 }
-- --
-- SIP Retry Statistics -- SIP Retry Statistics
-- --
-- The counter objects in this group correspond directly to the -- The counter objects in this group correspond directly to the
-- retry timers supported in sipCommonCfgRetry group. applIndex can -- retry timers supported in sipCommonCfgRetry group. applIndex can
-- be used to correlate the two groups. -- be used to correlate the two groups.
-- --
skipping to change at page 51, line 15 skipping to change at page 54, line 46
DESCRIPTION DESCRIPTION
"This table contains other common statistics supported by "This table contains other common statistics supported by
each SIP entity in this system." each SIP entity in this system."
::= { sipCommonStatsOther 1 } ::= { sipCommonStatsOther 1 }
sipOtherStatsEntry OBJECT-TYPE sipOtherStatsEntry OBJECT-TYPE
SYNTAX SipOtherStatsEntry SYNTAX SipOtherStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular SIP entities' other common "Information on a particular SIP entity's other common
statistics. statistics.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
entity present in this system. applIndex is used to entity present in this system. applIndex is used to
uniquely identify these instances of SIP entities and uniquely identify these instances of SIP entities and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788)."
INDEX { applIndex } INDEX { applIndex }
::= { sipOtherStatsTable 1 } ::= { sipOtherStatsTable 1 }
skipping to change at page 52, line 4 skipping to change at page 55, line 33
in RFC 2788. It is used to bind this notification in RFC 2788. It is used to bind this notification
with a specific instance of SIP entity." with a specific instance of SIP entity."
::= { sipCommonMIBNotifs 1 } ::= { sipCommonMIBNotifs 1 }
sipStatusCodeNotif NOTIFICATION-TYPE sipStatusCodeNotif NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifApplIndex, sipNotifApplIndex,
sipStatusCodeNotifTo, sipStatusCodeNotifTo,
sipStatusCodeNotifFrom, sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId, sipStatusCodeNotifCallId,
sipStatusCodeNotifCSeq sipStatusCodeNotifCSeq,
sipCommonStatusCodeIns,
sipCommonStatusCodeOuts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that a specific status code has been sent "Signifies that a specific status code has been sent
or received by the system." or received by the system."
::= { sipCommonMIBNotifs 2 } ::= { sipCommonMIBNotifs 2 }
sipStatusCodeThreshExceededNotif NOTIFICATION-TYPE sipStatusCodeThreshExceededNotif NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifApplIndex, sipNotifApplIndex,
skipping to change at page 53, line 39 skipping to change at page 57, line 15
"This group is optional. A SIP entity can elect to "This group is optional. A SIP entity can elect to
not provide any notifications. If implemented, the not provide any notifications. If implemented, the
sipCommonStatusCodeNotifGroup must also be implemented." sipCommonStatusCodeNotifGroup must also be implemented."
GROUP sipCommonStatusCodeNotifGroup GROUP sipCommonStatusCodeNotifGroup
DESCRIPTION DESCRIPTION
"This group is optional. A SIP entity can elect to "This group is optional. A SIP entity can elect to
not provide any notifications. If implemented, the not provide any notifications. If implemented, the
sipCommonNotifGroup must also be implemented." sipCommonNotifGroup must also be implemented."
GROUP sipCommonConfigExpiresGroup
DESCRIPTION
"This group is optional. A SIP entity can elect to
not provide any Expires header configuration."
::= { sipCommonMIBCompliances 1 } ::= { sipCommonMIBCompliances 1 }
-- --
-- Units of Conformance -- Units of Conformance
-- --
sipCommonConfigGroup OBJECT-GROUP sipCommonConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipProtocolVersion, sipProtocolVersion,
sipServiceOperStatus, sipServiceOperStatus,
sipServiceAdminStatus, sipServiceAdminStatus,
sipServiceStartTime, sipServiceStartTime,
sipServiceLastChange, sipServiceLastChange,
sipTransportRcv, sipTransportRcv,
sipTransportSnd, sipTransportSnd,
sipPortStatus, sipPortStatus,
sipUriSupported, sipUriSupported,
sipFtrSupported, sipFtrSupported,
sipOrganization, sipOrganization,
sipMaxSessions, sipMaxSessions,
sipInviteTimeout,
sipRequestUriHostMatching sipRequestUriHostMatching
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration common "A collection of objects providing configuration common
to all SIP enities." to all SIP enities."
::= { sipCommonMIBGroups 1 } ::= { sipCommonMIBGroups 1 }
sipCommonConfigTimerGroup OBJECT-GROUP sipCommonConfigTimerGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgInitialTimerInvite, sipCfgInitialTimerInvite,
sipCfgTimerProv, sipCfgTimerProv,
skipping to change at page 55, line 49 skipping to change at page 59, line 30
sipStatsSuccessClassIns, sipStatsSuccessClassIns,
sipStatsSuccessClassOuts, sipStatsSuccessClassOuts,
sipStatsRedirClassIns, sipStatsRedirClassIns,
sipStatsRedirClassOuts, sipStatsRedirClassOuts,
sipStatsReqFailClassIns, sipStatsReqFailClassIns,
sipStatsReqFailClassOuts, sipStatsReqFailClassOuts,
sipStatsServerFailClassIns, sipStatsServerFailClassIns,
sipStatsServerFailClassOuts, sipStatsServerFailClassOuts,
sipStatsGlobalFailClassIns, sipStatsGlobalFailClassIns,
sipStatsGlobalFailClassOuts, sipStatsGlobalFailClassOuts,
sipStatsOtherClassesIns,
sipStatsOtherClassesOuts,
sipCommonStatusCodeIns, sipCommonStatusCodeIns,
sipCommonStatusCodeOuts, sipCommonStatusCodeOuts,
sipCommonStatusCodeStatus, sipCommonStatusCodeStatus,
sipCurrentTransactions, sipCurrentTransactions,
sipTransTo, sipTransTo,
sipTransFrom, sipTransFrom,
sipTransCallId, sipTransCallId,
sipTransCSeq, sipTransCSeq,
sipTransState, sipTransState,
sipTransNumOutstandingBranches, sipTransNumOutstandingBranches,
sipTransExpiry, sipTransExpiry,
sipTransCallingPartyContentType, sipTransMethod,
sipTransCalledPartyContentType, sipTransActivityInfo,
sipNumUnsupportedUris sipNumUnsupportedUris
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics common "A collection of objects providing statistics common
toall SIP entities." toall SIP entities."
::= { sipCommonMIBGroups 6 } ::= { sipCommonMIBGroups 6 }
sipCommonStatsRetryGroup OBJECT-GROUP sipCommonStatsRetryGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 57, line 13 skipping to change at page 60, line 53
sipStatusCodeNotifCallId, sipStatusCodeNotifCallId,
sipStatusCodeNotifCSeq, sipStatusCodeNotifCSeq,
sipNotifApplIndex sipNotifApplIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects related to controlling and attribution "A collection of objects related to controlling and attribution
of notifications common to all SIP entities." of notifications common to all SIP entities."
::= { sipCommonMIBGroups 10 } ::= { sipCommonMIBGroups 10 }
sipCommonConfigExpiresGroup OBJECT-GROUP
OBJECTS {
sipCfgExpiresInvite,
sipCfgExpiresRegister,
sipCfgExpiresHeaderMethod,
sipCfgExpiresHeaderValue,
sipCfgExpiresStatusCodeStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration
related to Expires header."
::= { sipCommonMIBGroups 11 }
END END
5.3. SIP User Agent 5.3. SIP User Agent
SIP-UA-MIB DEFINITIONS ::= BEGIN SIP-UA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Unsigned32, Unsigned32,
skipping to change at page 57, line 41 skipping to change at page 61, line 38
FROM SNMPv2-TC FROM SNMPv2-TC
applIndex applIndex
FROM NETWORK-SERVICES-MIB FROM NETWORK-SERVICES-MIB
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
sipUAMIB MODULE-IDENTITY sipUAMIB MODULE-IDENTITY
LAST-UPDATED "200106060000Z" LAST-UPDATED "200202040000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO CONTACT-INFO
"SIP MIB Team email: sip-mib@yahoogroups.com "SIP MIB email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
skipping to change at page 58, line 7 skipping to change at page 62, line 4
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
Co-editor Joon Maeng Co-editor Joon Maeng
ipDialog, Inc. ipDialog, Inc.
postal: 7701 N. Lamar Blvd., Suite 304 postal: 7701 N. Lamar Blvd., Suite 304
Austin, TX 78752-1023 Austin, TX 78752-1023
USA USA
email: jmaeng@ipdialog.com email: jmaeng@ipdialog.com
phone: +1 512 371 1770 phone: +1 512 371 1770
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
postal: 495 March Road postal: 495 March Road
Kanata, ON K2K 3G1 Kanata, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: drwalker@ss8.com
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
Clarent Corporation CableLabs
700 Chesapeake Drive postal: 400 Centennial Parkway
Redwood City, CA 94063 Louisville, CO 80027
USA USA
email: jfm@clarent.com email: jf.mule@cablelabs.com
phone: +1 650 481 2835" phone: +1 303 661 3708 "
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Initial version of Session Initiation Protocol (SIP)
User Agent (UA) MIB module. User Agent (UA) MIB module.
SIP is an application-layer signalling protocol for SIP is an application-layer signalling protocol for
creating, modifying and terminating multimedia creating, modifying and terminating multimedia
sessions with one or more participants. These sessions sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 2543 (March telephone calls. SIP is defined in RFC 2543 (March
1999). 1999).
skipping to change at page 58, line 44 skipping to change at page 62, line 40
A User Agent is an application that contains both a A User Agent is an application that contains both a
User Agent Client (UAC) and a User Agent Server (UAS). User Agent Client (UAC) and a User Agent Server (UAS).
A UAC is an application that initiates a SIP request. A UAC is an application that initiates a SIP request.
A UAS is an application that contacts the user when a A UAS is an application that contacts the user when a
SIP request is received and that returns a response on SIP request is received and that returns a response on
behalf of the user. The response accepts, rejects, or behalf of the user. The response accepts, rejects, or
redirects the request." redirects the request."
::= { mib-2 9992 } -- to be assigned by IANA ::= { mib-2 9992 } -- to be assigned by IANA
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipUAMIBNotifs OBJECT IDENTIFIER ::= { sipUAMIB 0 }
sipUAMIBObjects OBJECT IDENTIFIER ::= { sipUAMIB 1 } sipUAMIBObjects OBJECT IDENTIFIER ::= { sipUAMIB 1 }
sipUAMIBConform OBJECT IDENTIFIER ::= { sipUAMIB 2 } sipUAMIBConform OBJECT IDENTIFIER ::= { sipUAMIB 2 }
-- --
-- This MIB contains objects related to SIP User Agents. -- This MIB contains objects related to SIP User Agents.
-- --
sipUACfgSipServer OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 } sipUACfgSipServer OBJECT IDENTIFIER ::= { sipUAMIBObjects 1 }
sipUAStats OBJECT IDENTIFIER ::= { sipUAMIBObjects 2 }
-- --
-- SIP Server Configuration -- SIP Server Configuration
-- --
sipUACfgSipServerTable OBJECT-TYPE sipUACfgSipServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipUACfgSipServerEntry SYNTAX SEQUENCE OF SipUACfgSipServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains SIP server configuration objects "This table contains SIP server configuration objects
skipping to change at page 59, line 20 skipping to change at page 63, line 15
SYNTAX SipUACfgSipServerEntry SYNTAX SipUACfgSipServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of server configuration. "A row of server configuration.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
user agent present in this system. applIndex is used to user agent present in this system. applIndex is used to
uniquely identify these instances of SIP user agents and uniquely identify these instances of SIP user agents and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788). The same value of
applIndex used in the corresponding SIP-COMMON-MIB is
used here."
INDEX { applIndex, sipUACfgSipServerAddrIndex } INDEX { applIndex, sipUACfgSipServerAddrIndex }
::= { sipUACfgSipServerTable 1 } ::= { sipUACfgSipServerTable 1 }
SipUACfgSipServerEntry ::= SipUACfgSipServerEntry ::=
SEQUENCE { SEQUENCE {
sipUACfgSipServerAddrIndex Unsigned32, sipUACfgSipServerAddrIndex Unsigned32,
sipUACfgSipServerAddrType InetAddressType, sipUACfgSipServerAddrType InetAddressType,
sipUACfgSipServerAddr InetAddress, sipUACfgSipServerAddr InetAddress,
sipUACfgSipServerAddrStatus RowStatus sipUACfgSipServerAddrStatus RowStatus
} }
skipping to change at page 60, line 18 skipping to change at page 64, line 16
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to control rows in this table. "This object is used to control rows in this table.
'active' : the row's information is completely 'active' : the row's information is completely
populated and that information is populated and that information is
being used by the user agent. being used by the user agent.
'notInService' : the row's address is not being used 'notInService' : the row's address is not being used
by the user agent, but will remain in the table. by the user agent, but will remain in
the table.
'notReady' : key information is missing thus, preventing 'notReady' : key information is missing thus,
the row from being made 'active' (eg, no preventing the row from being made
address specified). 'active' (eg, no address specified).
'createAndGo' : only allowed if the manager also provides 'createAndGo' : only allowed if the manager also
a varbind for sipUACfgSipServerAddr object provides a varbind for
in the same set operation. sipUACfgSipServerAddr object in the
same set operation.
'createAndWait' : not applicable. 'createAndWait' : not applicable.
'destroy' : the row's address will no longer be used 'destroy' : the row's address will no longer be used
by the user agent and the row will be by the user agent and the row will be
removed from the table." removed from the table."
::= { sipUACfgSipServerEntry 4 } ::= { sipUACfgSipServerEntry 4 }
-- --
-- Conformance -- Conformance
skipping to change at page 61, line 48 skipping to change at page 65, line 48
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
applIndex applIndex
FROM NETWORK-SERVICES-MIB FROM NETWORK-SERVICES-MIB
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
sipServerMIB MODULE-IDENTITY sipServerMIB MODULE-IDENTITY
LAST-UPDATED "200106060000Z" LAST-UPDATED "200202040000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO CONTACT-INFO
"SIP MIB Team email: sip-mib@yahoogroups.com "SIP MIB email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
skipping to change at page 62, line 24 skipping to change at page 66, line 26
Co-editor Dave Walker Co-editor Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
postal: 495 March Road postal: 495 March Road
Kanata, ON K2K 3G1 Kanata, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: drwalker@ss8.com
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
Clarent Corporation CableLabs
700 Chesapeake Drive postal: 400 Centennial Parkway
Redwood City, CA 94063 Louisville, CO 80027
USA USA
email: jfm@clarent.com email: jf.mule@cablelabs.com
phone: +1 650 481 2835" phone: +1 303 661 3708 "
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Initial version of Session Initiation Protocol (SIP)
Server MIB module. Server MIB module.
SIP is an application-layer signalling protocol for SIP is an application-layer signalling protocol for
creating, modifying and terminating multimedia creating, modifying and terminating multimedia
sessions with one or more participants. These sessions sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 2543 (March telephone calls. SIP is defined in RFC 2543 (March
1999). 1999).
This MIB is defined for the management of SIP Proxy, This MIB is defined for the management of SIP Proxy,
Redirect, and Registrar Servers. Redirect, and Registrar Servers.
A Proxy Server acts as both a client and a server. A Proxy Server acts as both a client and a server.
It accepts requests from other clients, either It accepts requests from other clients, either
responding to them or passing them on to other responding to them or passing them on to other
servers, possibly after modification. servers, possibly after modification.
A Redirect Server accepts requests from clients and A Redirect Server accepts requests from clients and
returns zero or more addresses to that client. Unlike returns zero or more addresses to that client.
a Proxy server it does not initiate requests. Unlike Unlike a User Agent Server it does not accept calls.
a User Agent Server it does not accept calls.
A Registrar is a server that accepts REGISTER A Registrar is a server that accepts REGISTER
requests. A Registrar is typically co-located with a requests. A Registrar is typically co-located with a
Proxy or Redirect Server." Proxy or Redirect Server."
::= { mib-2 9991 } -- to be assigned by IANA ::= { mib-2 9991 } -- to be assigned by IANA
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipServerMIBNotifs OBJECT IDENTIFIER ::= { sipServerMIB 0 }
sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 } sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 }
sipServerMIBConform OBJECT IDENTIFIER ::= { sipServerMIB 2 } sipServerMIBConform OBJECT IDENTIFIER ::= { sipServerMIB 2 }
-- --
-- These groups contains objects common to all SIP servers. -- These groups contains objects common to all SIP servers.
-- --
sipServerCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 1 } sipServerCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 1 }
sipServerStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 2 } sipServerStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 2 }
-- --
skipping to change at page 63, line 38 skipping to change at page 67, line 37
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 Each row represents those objects for a particular SIP
server present in this system. applIndex is used to server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and uniquely identify these instances of SIP servers and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788). The same value of
applIndex used in the corresponding SIP-COMMON-MIB
is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipServerCfgTable 1 } ::= { sipServerCfgTable 1 }
SipServerCfgEntry ::= SipServerCfgEntry ::=
SEQUENCE { SEQUENCE {
sipServerHostAddrType InetAddressType, sipServerHostAddrType InetAddressType,
sipServerHostAddr InetAddress, sipServerHostAddr InetAddress,
sipPgpVersion SnmpAdminString, sipPgpVersion SnmpAdminString,
sipServerContactDfltAction INTEGER, sipServerContactDfltAction INTEGER,
sipServerRespectUAAction TruthValue sipServerRespectUAAction TruthValue
skipping to change at page 65, line 42 skipping to change at page 69, line 43
SYNTAX SipProxyCfgEntry SYNTAX SipProxyCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common proxy configuration. "A row of common proxy configuration.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
server present in this system. applIndex is used to server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and uniquely identify these instances of SIP servers and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788). The same value of
applIndex used in the corresponding SIP-COMMON-MIB
is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipProxyCfgTable 1 } ::= { sipProxyCfgTable 1 }
SipProxyCfgEntry ::= SipProxyCfgEntry ::=
SEQUENCE { SEQUENCE {
sipRequestMaxExpires Unsigned32, sipRequestMaxExpires Unsigned32,
sipProxyStatefulness INTEGER, sipProxyStatefulness INTEGER,
sipProxySendsCancel TruthValue, sipProxySendsCancel TruthValue,
sipProxyForwardAll1xx TruthValue, sipProxyForwardAll1xx TruthValue,
sipProxyRecursion TruthValue, sipProxyRecursion TruthValue,
skipping to change at page 66, line 35 skipping to change at page 70, line 38
DESCRIPTION DESCRIPTION
"This object specifies the default mode of operation for "This object specifies the default mode of operation for
the proxy server entity. the proxy server entity.
A stateless proxy entity does not maintain state A stateless proxy entity does not maintain state
for a SIP transaction. A stateless proxy forwards every for a SIP transaction. A stateless proxy forwards every
request it receives downstream and every response it request it receives downstream and every response it
receives upstream. If the value of this object is receives upstream. If the value of this object is
stateless(1), the proxy defaults to stateless operations. stateless(1), the proxy defaults to stateless operations.
A transaction stateful proxy does maintain state A transaction stateful proxy, or simply a 'stateful
information for the duration of a SIP transaction. Also proxy', maintains state information for the duration of
known as a stateful proxy. If the value if this object a SIP transaction. If the value if this object is
is transactionStateful(2), the proxy is stateful on a transactionStateful(2), the proxy is stateful on a
transaction basis. transaction basis.
A call stateful proxy does retain state that persists A call stateful proxy does retain state that persists
for the duration of a call initiated through it. To for the duration of a call initiated through it. To
properly manage that state, the proxy will normally properly manage that state, the proxy will normally
need to receive the BYE requests that terminate the call. need to receive the BYE requests that terminate the call.
If the value of this object is callStateful(3), the If the value of this object is callStateful(3), the
proxy is call stateful." proxy is call stateful."
REFERENCE REFERENCE
"RFC 2543, Section 12.3" "RFC 2543, Section 12.3"
skipping to change at page 66, line 60 skipping to change at page 71, line 6
sipProxySendsCancel OBJECT-TYPE sipProxySendsCancel OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not a forking proxy sends "This object specifies whether or not a forking proxy sends
CANCEL on outstanding branch requests after receiving a CANCEL on outstanding branch requests after receiving a
2xx or 6xx, or after the request times-out. 2xx or 6xx, or after the request times-out.
If the value of this object is TRUE, the server sends a If the value of this object is ĉtrueĈ, the server sends a
CANCELs on branches where no definitive response has been CANCELs on branches where no definitive response has been
received. If FALSE, the proxy does not send CANCELs." received. If ĉfalseĈ, the proxy does not send CANCELs."
REFERENCE REFERENCE
"RFC 2543, Section 12.4" "RFC 2543, Section 12.4"
::= { sipProxyCfgEntry 3 } ::= { sipProxyCfgEntry 3 }
sipProxyForwardAll1xx OBJECT-TYPE sipProxyForwardAll1xx OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the proxy forwards "This object specifies whether or not the proxy forwards
all 1xx responses, except the 100 Trying response, all 1xx responses, except the 100 Trying response,
upstream towards the source of the request. upstream towards the source of the request.
If the value of this object is TRUE, the 1xx responses are If the value of this object is ĉtrueĈ, the 1xx responses are
sent. If the value is FALSE, duplicate 1xx responses are sent. If the value is ĉfalseĈ, duplicate 1xx responses are
not sent upstream." not sent upstream."
::= { sipProxyCfgEntry 4 } ::= { sipProxyCfgEntry 4 }
sipProxyRecursion OBJECT-TYPE sipProxyRecursion OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Proxy performs "This object specifies whether or not the Proxy performs
recursive search on the Contacts provided in 3xx recursive search on the Contacts provided in 3xx
redirects. redirects.
If the value of this object is TRUE, a recursive search 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 3xx response is sent upstream towards the source of
the request." the request."
::= { sipProxyCfgEntry 5 } ::= { sipProxyCfgEntry 5 }
sipProxyProvideAlternatives OBJECT-TYPE sipProxyProvideAlternatives OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object specifies whether or not the Server provides "The object specifies whether or not the Server provides
alternative Contacts in 3xx and 485 responses. alternative Contacts in 3xx and 485 responses.
If the value of this object is TRUE, the server inserts a If the value of this object is ĉtrueĈ, the server inserts a
list of alternative URLs into a Contact header where the list of alternative URLs into a Contact header where the
request Originator may possibly find the desired called request Originator may possibly find the desired called
party. If the value is FALSE, the server doesn't add party. If the value is ĉfalseĈ, the server doesn't add
Contact information to 3xx and 485 responses. Contact information to 3xx and 485 responses.
Note that the policies of a server may limit the Note that the policies of a server may limit the
particular alternatives that are returned when this object particular alternatives that are returned when this object
is TRUE." is set to ĉtrueĈ."
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
DEFVAL { false } DEFVAL { false }
::= { sipProxyCfgEntry 6 } ::= { sipProxyCfgEntry 6 }
sipProxyRecordRoute OBJECT-TYPE sipProxyRecordRoute OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the proxy adds itself "This object specifies whether or not the proxy adds itself
to the Record-Route header as a default action. This to the Record-Route header as a default action. This
header is used to list the proxies that insist on being in header is used to list the proxies that insist on being in
the signalling path for subsequent requests related to the the signalling path for subsequent requests related to the
skipping to change at page 68, line 16 skipping to change at page 72, line 20
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the proxy adds itself "This object specifies whether or not the proxy adds itself
to the Record-Route header as a default action. This to the Record-Route header as a default action. This
header is used to list the proxies that insist on being in header is used to list the proxies that insist on being in
the signalling path for subsequent requests related to the the signalling path for subsequent requests related to the
call-leg. call-leg.
If the value of this object is TRUE, the proxy adds itself If the value of this object is ĉtrueĈ, the proxy adds itself
to the end of the Record-Route header, creating the header to the end of the Record-Route header, creating the header
if required. If the value is FALSE, the proxy doesn't add if required. If the value is ĉfalseĈ, the proxy doesn't add
itself to the Record-Route header." itself to the Record-Route header."
REFERENCE REFERENCE
"RFC 2543, Section 6.29" "RFC 2543, Section 6.29"
::= { sipProxyCfgEntry 7 } ::= { sipProxyCfgEntry 7 }
sipProxyStateTimeout OBJECT-TYPE sipProxyStateTimeout OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the duration after reception of the "This object specifies the duration after reception of the
first INVITE response that a stateful proxy retains state first INVITE response that a stateful proxy retains state
in order to handle possible retransmissions of the response." in order to handle possible retransmissions of the
response."
REFERENCE REFERENCE
"RFC 2543, Section 12.3.6" "RFC 2543, Section 12.3.6"
::= { sipProxyCfgEntry 8 } ::= { sipProxyCfgEntry 8 }
-- --
-- Security -- Security
-- --
sipProxyAuthMethod OBJECT-TYPE sipProxyAuthMethod OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
none(0), none(0),
skipping to change at page 70, line 21 skipping to change at page 74, line 27
SYNTAX SipProxyStatsEntry SYNTAX SipProxyStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics. "A row of summary statistics.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
server present in this system. applIndex is used to server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and uniquely identify these instances of SIP servers and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788). The same value of
applIndex used in the corresponding SIP-COMMON-MIB
is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipProxyStatsTable 1 } ::= { sipProxyStatsTable 1 }
SipProxyStatsEntry ::= SipProxyStatsEntry ::=
SEQUENCE { SEQUENCE {
sipNumProxyRequireFailures Counter32 sipNumProxyRequireFailures Counter32
} }
sipNumProxyRequireFailures OBJECT-TYPE sipNumProxyRequireFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at page 70, line 45 skipping to change at page 74, line 53
"This object contains the number of occurrences of "This object contains the number of occurrences of
unsupported options being specified in received Proxy- unsupported options being specified in received Proxy-
Require headers. Such occurrences result in a 420 Bad Require headers. Such occurrences result in a 420 Bad
Extension status code being Extension status code being
returned." returned."
::= { sipProxyStatsEntry 1 } ::= { sipProxyStatsEntry 1 }
-- --
-- This group contains MIB objects related to SIP Redirect Servers. -- This group contains MIB objects related to SIP Redirect Servers.
-- --
sipRedirCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 5 } sipRedirCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 5
sipRedirStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 6 } }
sipRedirStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 6
}
-- none at this time -- none at this time
-- --
-- This group contains MIB objects related to SIP Registrars. -- This group contains MIB objects related to SIP Registrars.
-- --
sipRegCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 7 } sipRegCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 7
sipRegStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 8 } }
sipRegStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 8
}
-- --
-- Registrar Configuration -- Registrar Configuration
-- --
sipRegCfgTable OBJECT-TYPE sipRegCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegCfgEntry SYNTAX SEQUENCE OF SipRegCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable "This table contains configuration objects applicable
skipping to change at page 71, line 22 skipping to change at page 75, line 34
SYNTAX SipRegCfgEntry SYNTAX SipRegCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of common registrar configuration. "A row of common registrar configuration.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
server present in this system. applIndex is used to server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and uniquely identify these instances of SIP servers and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788). The same value of
applIndex used in the corresponding SIP-COMMON-MIB
is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipRegCfgTable 1 } ::= { sipRegCfgTable 1 }
SipRegCfgEntry ::= SipRegCfgEntry ::=
SEQUENCE { SEQUENCE {
sipRegAllowThirdParty TruthValue, sipRegAllowThirdParty TruthValue,
sipRegMaxContactExpiryDate Unsigned32, sipRegMaxContactExpiryDate Unsigned32,
sipRegMaxUsers Unsigned32, sipRegMaxUsers Unsigned32,
sipRegCurrentUsers Gauge32, sipRegCurrentUsers Gauge32,
sipRegDfltRegActiveInterval Unsigned32 sipRegDfltRegActiveInterval Unsigned32
skipping to change at page 71, line 44 skipping to change at page 75, line 58
sipRegAllowThirdParty OBJECT-TYPE sipRegAllowThirdParty OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Registrar should "This object specifies whether or not the Registrar should
allows third party registrations. In third-party allows third party registrations. In third-party
registration, the entity issuing the request (in the From registration, the entity issuing the request (in the From
header) is different from the entity being registered (in header) is different from the entity being registered (in
the To header) to whom the the To header) to whom the provided Contact information
provided Contact information applies. applies.
If the value of this object is TRUE, the Registrar allows If the value of this object is ĉtrueĈ, the Registrar allows
third party registrations. If the value is FALSE, third third party registrations. If the value is ĉfalseĈ, third
party registrations are rejected: a 403 Forbidden status party registrations are rejected: a 403 Forbidden status
code is returned to the requestor." code is returned to the requestor."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.6" "RFC 2543, Section 4.2.6"
::= { sipRegCfgEntry 1 } ::= { sipRegCfgEntry 1 }
sipRegMaxContactExpiryDate OBJECT-TYPE sipRegMaxContactExpiryDate OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 73, line 19 skipping to change at page 77, line 33
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single user "This entry contains information for a single user
registered to this Registrar. registered to this Registrar.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
server present in this system. applIndex is used to server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and uniquely identify these instances of SIP servers and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788). The same value of
applIndex used in the corresponding SIP-COMMON-MIB
is used here."
INDEX { applIndex, sipUserIndex } INDEX { applIndex, sipUserIndex }
::= { sipRegUserTable 1 } ::= { sipRegUserTable 1 }
SipRegUserEntry ::= SipRegUserEntry ::=
SEQUENCE { SEQUENCE {
sipUserIndex Unsigned32, sipUserIndex Unsigned32,
sipUserUri SnmpAdminString, sipUserUri SnmpAdminString,
sipUserAuthenticationFailures Counter32, sipUserAuthenticationFailures Counter32,
sipUserTableRowStatus RowStatus sipUserTableRowStatus RowStatus
} }
skipping to change at page 74, line 38 skipping to change at page 78, line 54
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single Contact. "This entry contains information for a single Contact.
Multiple contacts may exist for a single user. Multiple contacts may exist for a single user.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
server present in this system. applIndex is used to server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and uniquely identify these instances of SIP servers and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788). The same value of
applIndex used in the corresponding SIP-COMMON-MIB
is used here."
INDEX { applIndex, sipUserIndex, sipContactIndex } INDEX { applIndex, sipUserIndex, sipContactIndex }
::= { sipContactTable 1 } ::= { sipContactTable 1 }
SipContactEntry ::= SipContactEntry ::=
SEQUENCE { SEQUENCE {
sipContactIndex Unsigned32, sipContactIndex Unsigned32,
sipContactDisplayName SnmpAdminString, sipContactDisplayName SnmpAdminString,
sipContactURI SnmpAdminString, sipContactURI SnmpAdminString,
sipContactLastUpdated TimeStamp, sipContactLastUpdated TimeStamp,
sipContactExpiry DateAndTime, sipContactExpiry DateAndTime,
sipContactPreference OCTET STRING, sipContactPreference SnmpAdminString,
sipContactAction INTEGER, sipContactAction INTEGER,
sipContactRetryAfter DateAndTime sipContactRetryAfter DateAndTime
} }
sipContactIndex OBJECT-TYPE sipContactIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Along with the sipUserIndex, this object uniquely "Along with the sipUserIndex, this object uniquely
skipping to change at page 75, line 56 skipping to change at page 80, line 17
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 specified by the user at registration (Expires header or
expiry parameter in the Contact information), or a system expiry parameter in the Contact information), or a system
default can be applied." default can be applied."
::= { sipContactEntry 5 } ::= { sipContactEntry 5 }
sipContactPreference OBJECT-TYPE sipContactPreference OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..255)) SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the preference for this contact "This object specifies the preference for this contact
relative to all other active contacts for same user. A relative to all other active contacts for same user. A
registering user may provide this preference as a 'qvalue' registering user may provide this preference as a 'qvalue'
parameter in the Contact header. parameter in the Contact header.
The format of this item is a decimal number between 0 The format of this item is a decimal number between 0
and 1 (for example 0.9). Higher values indicate locations and 1 (for example 0.9). Higher values indicate locations
skipping to change at page 77, line 12 skipping to change at page 81, line 27
SYNTAX SipRegStatsEntry SYNTAX SipRegStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row of summary statistics. "A row of summary statistics.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
server present in this system. applIndex is used to server present in this system. applIndex is used to
uniquely identify these instances of SIP servers and uniquely identify these instances of SIP servers and
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788)." NETWORK-SERVICES-MIB (RFC 2788). The same value of
applIndex used in the corresponding SIP-COMMON-MIB
is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipRegStatsTable 1 } ::= { sipRegStatsTable 1 }
SipRegStatsEntry ::= SipRegStatsEntry ::=
SEQUENCE { SEQUENCE {
sipRegAcceptedRegistrations Counter32, sipRegAcceptedRegistrations Counter32,
sipRegRejectedRegistrations Counter32 sipRegRejectedRegistrations Counter32
} }
sipRegAcceptedRegistrations OBJECT-TYPE sipRegAcceptedRegistrations OBJECT-TYPE
skipping to change at page 80, line 6 skipping to change at page 84, line 20
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics for "A collection of objects providing statistics for
SIP Registrars." SIP Registrars."
::= { sipServerMIBGroups 5 } ::= { sipServerMIBGroups 5 }
END END
6. Changes from previous drafts 6. Changes from previous drafts
o Changes from draft-ietf-sip-mib-02.txt
o Changes from draft-ietf-sip-mib-03
These are the specific draft-ietf-sip-mib-04 changes to the MIB
modules based on what they looked like for draft-ietf-sip-mib-03.
Front paper/Back paper
o Rewrote parts of section 4.2
o Fixed minor editorial nits
SIP-COMMON-MIB
o CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
o sipInviteTimeout was removed from the MIB. See below regarding new
sipCommonCfgExpires objects. They provide equivalent functionality
with extensibility beyond INVITE.
o sipCommonCfgExpires OID subtree added. Per method Expires
configuration objects were added there.
This new high-level OID was placed under the existing
sipCommonCfgRetry OID and therefore, caused the OIDs for the
subsequent groups to change (incrementing by one).
o Objects from tables under sipCommonCfgExpires were added to a new
OBJECT-GROUP sipCommonConfigExpiresGroup, and that group was listed
as optional in sipCommonCompliance.
o Minor DESCRIPTION change for sipCommonCfgEntry. No behavior
change.
o sipServiceOperStatus SYNTAX changed.
New values added: congested & quiescing
Old values removed: halted
The order of the enumeration was altered as well.
o sipServiceAdminStatus SYNTAX changed.
New values added: noop, up, down, quieseSessions, and
quieseApplications
Old values removed: shutdown, restart, stop, rts.
These changes were made based on comments from last call reviewer
and general known ambiguities in the previous design of the object.
o Clarifying changes to the DESCRIPTION of sipServiceStartTime.
o Clarifying changes to the DESCRIPTION of sipOrganization.
o Clarification of behavior for sipPortStatus while row is
'active'.
o Clarifying changes to the DESCRIPTION of sipUriSupportedTable
o Clarifying changes to the DESCRIPTIONs of sipFtrSupportedTable,
sipFtrSupportedEntry, and sipFtrSupported.
Specifically, IETF standard features and non-standard features are
now represented by this table. Only non-standard features were
mentioned in prior revisions of the draft.
o Reference to usage of RFC 2788 applIndex moved from
sipCommonCfgTimerExtMethodTable to sipCommonCfgTimerExtMethodEntry.
This was the convention for other table/entry definitions in
the MIB, so these objects were previously unconventional.
o DEFVAL removed from sipCfgTimerExtMethodTimer. The generic nature
of the "extension" object does not lend itself to being able to
specify a particular default value.
o Since the removal of the DEFVAL clause from
sipCfgTimerExtMethodTimer,
a value for that object must be specified when creating a
sipCommonCfgTimerExtMethodEntry. The description of
sipCfgTimerExtMethodStatus was updated to reflect this.
o sipCommonCfgRetryExtMethodTable is now properly defined under
sipCommonCfgRetry OID space instead of under sipCommonCfgTimer
OID space.
o DEFVAL removed from sipCfgRetryExtMethodRetry. The generic nature
of the "extension" object does not lend itself to being able to
specify a particular default value.
o Since the removal of the DEFVAL clause from
sipCfgRetryExtMethodRetry,
a value for that object must be specified when creating a
sipCommonCfgRetryExtMethodEntry. The description of
sipCfgRetryExtMethodStatus was updated to reflect this.
o Clarifying changes to the DESCRIPTION of
sipSummaryTotalTransactions.
Specifically, the object is not applicable to stateless SIP proxy
servers and the object should always return a value of 0 if
implemented by a stateless proxy.
o Clarifying changes to the DESCRIPTION of sipStatsExtMethodStatus.
o sipStatsOtherClassesIns and sipStatsOtherClassesOuts counter
objects were added to sipStatusCodesTable to handle possible
future classes of response status codes.
o Text referring specifically to Redirect Server in
sipStatsRedirClassIns and sipStatsRedirClassOuts was removed.
o Text defining protocol behavior in sipStatsServerFailClassIns,
sipStatsServerFailClassOuts, sipStatsGlobalFailClassIns, and
sipStatsGlobalFailClassOuts was removed.
o sipCommonStatusCodeNotifInterval SYNTAX changed from TimeTicks
to Unsigned32 w/ a UNITS of "seconds" added to the definition.
DEFVAL clause changed accordingly.
o sipStatusCodeNotifTo, sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId,
and sipStatusCodeNotifCSeq all had clarifying changes to their
DESCRIPTIONs. Specifically, the header name will be part of the
object value and example values were given.
o Clarifying changes to the DESCRIPTION of sipCurrentTransTable
and sipTransactionTable. Specifically, these tables are not
applicable to transaction stateless SIP proxy servers.
o Minor gramatical change to the DESCRIPTION of sipCurrentTransEntry.
o sipTransMethod and sipTransActivityInfo objects were added to
sipTransactionTable while sipTransCallingPartyContentType and
sipTransCalledPartyContentType were removed.
o Clarifying changes to the DESCRIPTION of sipTransState.
Specifically, noting that not all values of the object
are applicable to all transaction types.
o sipTransTo, sipTransFrom, sipTransCallId, and sipTransCSeq
all had clarifying changes to their DESCRIPTIONs.
Specifically, the header name will be part of the object
value and example values were given.
o Minor gramatical change to the DESCRIPTION of sipOtherStatsEntry.
o sipCommonStatusCodeIns and sipCommonStatusCodeOuts objects were
added to the varbind of sipStatusCodeNotif.
o Appropriate changes were made to sipCommonStatsGroup OBJECT-GROUP
based on objects being added and/or removed from the MIB.
SIP-SERVER-MIB
o CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
o The statement "Unlike a Proxy server it does not initiate
requests." was removed from where a Redirect Server is
defined in the MIB's DESCRIPTION.
o sipServerMIBNotifs OID removed. No notifications were
ever defined under this subtree.
o Clarifying text added to all of the Table DESCRIPTIONS
stating that the value of applIndex used in this MIB
corresponds to the value of applIndex used in the
SIP-COMMON-MIB.
o Clarifying changes to the DESCRIPTION of sipProxyStatefulness.
o sipContactPreference SYNTAX changed from OCTET STRING to
SnmpAdminString.
SIP-UA-MIB
o CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
o sipUAMIBNotifs OID removed. No notifications were
ever defined under this subtree.
o sipUAStats OID removed. No notifications were
ever defined under this subtree.
o Clarifying text added to all of the Table DESCRIPTIONS
stating that the value of applIndex used in this MIB
corresponds to the value of applIndex used in the
SIP-COMMON-MIB.
SIP-TC
o CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
o Changes from draft-ietf-sip-mib-02
The following changes were made based on review comments to the The following changes were made based on review comments to the
previous version of the draft. previous version of the draft.
In general In general
o Eliminated the SIP-MIB-SMI modules. Each MIB module will now o Eliminated the SIP-MIB-SMI modules. Each MIB module will now
get it's own IANA OID. get it's own IANA OID.
o Top-level OID subtrees restructured in each MIB. o Top-level OID subtrees restructured in each MIB.
o General cleanup/removal of "placeholder" OID subtrees o General cleanup/removal of "placeholder" OID subtrees
for object groups and notifications that never materialized. for object groups and notifications that never materialized.
skipping to change at page 81, line 33 skipping to change at page 89, line 25
collectively, they allow tracing and influencing of connections in collectively, they allow tracing and influencing of connections in
SIP entities and provide information of their connection SIP entities and provide information of their connection
characteristics. characteristics.
It is thus important to control even GET access to these objects and It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these objects when sending possibly to even encrypt the values of these objects when sending
them over the network via SNMP. Not all versions of SNMP provide them over the network via SNMP. Not all versions of SNMP provide
features for such a secure environment. features for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is itself is secure (for example by using IPSec), there is no control
no control as to who on the secure network is allowed to access and as to who on the secure network is allowed to access and GET/SET
GET/SET (read/change/create/delete) the objects in this MIB. (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2574 [12] and the View-based of the User-based Security Model RFC 2574 [12] and the View-based
Access Control Model RFC 2575 [15] is recommended. Access Control Model RFC 2575 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
8. Intellectual Property 8. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
skipping to change at page 82, line 18 skipping to change at page 90, line 9
can be obtained from the IETF Secretariat. can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
9. Full Copyright Statement 9. Full Copyright Statement
Copyright(C) The Internet Society (2001). All Rights Reserved. This Copyright (C) The Internet Society (2002). All Rights Reserved.
document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
skipping to change at page 84, line 12 skipping to change at page 92, line 12
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
2573, April 1999. 2573, April 1999.
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999. (SNMP)", RFC 2575, April 1999.
[16] Bradner, S., "Key words for use in RFCs to Indicate Requirement [16] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[17] M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg, [17] Handley, M., Schulzrinne, H., Schooler, E., and J. Rosenberg,
"SIP: Session Initiation Protocol", RFC 2543, March 1999. "SIP: Session Initiation Protocol", RFC 2543, March 1999.
[18] N. Freed, and S, Killle, ôNetwork Services Monitor MIBö, RFC [18] Freed, N. and S. Kille, "Network Services Monitor MIB", RFC
2788, March 2000 2788, March 2000
[19] S. Donavan, "The SIP INFO Method", RFC 2976, October 2000 [19] Donavan, S., "The SIP INFO Method", RFC 2976, October 2000
[20] Case, J., Mundy, R., Partain, D. and B. Stewart, [20] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network "Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999. Management Framework", RFC 2570, April 1999.
11. Author's Addresses 11. Author's Addresses
Kevin Lingle Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Road 7025 Kit Creek Road
skipping to change at page 84, line 41 skipping to change at page 92, line 41
USA USA
email: klingle@cisco.com email: klingle@cisco.com
phone: +1 919 392 2029 phone: +1 919 392 2029
Joon Maeng Joon Maeng
ipDialog, Inc. ipDialog, Inc.
7701 N. Lamar Blvd., Suite 304 7701 N. Lamar Blvd., Suite 304
Austin, TX 78752-1023 Austin, TX 78752-1023
USA USA
email: jmaeng@ipdialog.com email: jmaeng@ipdialog.com
phone: +1 512-371-1770 phone: +1 512 371 1770
Jean-Francois MuleĈ Jean-Francois MuleĈ
Clarent Corporation CableLabs
700 Chesapeake Drive, MS 101 400 Centennial Parkway
Redwood City, CA 94063 Louisville, CO 80027
USA USA
email: jfm@clarent.com email: jf.mule@cablelabs.com
phone: +1 650 481 2835 phone: +1 303 661 3708
Dave Walker Dave Walker
SS8 Networks, Inc. SS8 Networks, Inc.
495 March Road 495 March Road
Kanata, ON K2K 3G1 Kanata, ON K2K 3G1
Canada Canada
email: drwalker@ss8.com email: drwalker@ss8.com
phone: +1 613 592 2100 phone: +1 613 592 2100
 End of changes. 

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