draft-ietf-sip-mib-04.txt   draft-ietf-sip-mib-05.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-04.txt J. Maeng Document: draft-ietf-sip-mib-05.txt J. Maeng
February 2002 ipDialog, Inc. March 2003 ipDialog, Inc.
Expires: August 2002 J-F. Mule Expires: August 2003 J-F. Mule
CableLabs 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 [RFC2026].
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
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 Internet-Standard 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 MIBs...................................5 4.2. Relationship to Other MIBs......................4
5. Definitions....................................................8 5. Definitions...................................................7
5.1. SIP Textual Conventions......................................8 5.1. SIP Textual Conventions.........................7
5.2. SIP Common...................................................9 5.2. SIP Common......................................9
5.3. SIP User Agent..............................................61 5.3. SIP User Agent.................................63
5.4. SIP Server (Registrar, Redirect & Proxy Server).............65 5.4. SIP Server (Registrar, Redirect & Proxy Server)67
6. Changes from previous drafts..................................84 6. Changes from previous drafts.................................89
7. Security Considerations.......................................89 7. Security Considerations......................................93
8. Intellectual Property.........................................89 8. Intellectual Property........................................94
9. Full Copyright Statement......................................90 9. Full Copyright Statement.....................................94
10. References..................................................91 10. Normative References.......................................96
11. Author's Addresses..........................................92 11. Informative References.....................................96
12. Acknowledgments............................................96
13. Author's Addresses.........................................96
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 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.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [16]. document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119].
2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
second version, called SMIv2, is described in STD 58, RFC 2578
[5], RFC 2579 [6] and RFC 2580 [7].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3 and
described in RFC 2572 [11] and RFC 2574 [12].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [8]. A second set of protocol
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14] and 2. The Internet-Standard Management Framework
the view-based access control mechanism described in RFC 2575
[15].
A more detailed introduction to the current SNMP Management For a detailed overview of the documents that describe the current
Framework can be found in RFC 2570 [20]. Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. MIB objects are generally
defined using the mechanisms defined in the SMI. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
This memo specifies a MIB module that is compliant to the SMIv2. A Structure of Management Information (SMI). This memo specifies a
MIB conforming to the SMIv1 can be produced through the appropriate MIB module that is compliant to the SMIv2, which is described in STD
translations. The resulting translated MIB MUST be semantically 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
equivalent, except where objects or events are omitted because no 2580 [RFC2580].
translation is possible (use of Counter64). Some machine-readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine-
readable information is not considered to change the semantics of
the MIB.
3. Overview 3. Overview
The Session Initiation Protocol (SIP) [17] is an application-layer The Session Initiation Protocol (SIP) [1] is an application-layer
control protocol that can establish, modify and terminate multimedia control (signaling) protocol for creating, modifying, and
sessions or calls. This MIB provides some managed objects for SIP terminating sessions with one or more participants. These sessions
entities defined in RFC 2543 - User Agent, Proxy server, Redirect include Internet telephone calls, multimedia distribution, and
server and Registrar. It is provided as a base for the work within multimedia conferences. This MIB provides some managed objects for
the working group to define a MIB. SIP entities defined in RFC 3261 - User Agent, Proxy server,
Redirect server and Registrar. It is provided as a base for the work
within 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 [3].
4. Structure of SIP MIB 4. Structure of SIP MIB
This memo specifies four MIB modules. They are SIP-COMMON-MIB, SIP- This memo specifies four MIB modules. They are SIP-COMMON-MIB, SIP-
SERVER-MIB, SIP-UA-MIB and SIP-TC. SIP-COMMON-MIB contains common SERVER-MIB, SIP-UA-MIB and SIP-TC. SIP-COMMON-MIB contains common
objects used in all the SIP entities. SIP-SERVER-MIB contains objects used in all the SIP entities. SIP-SERVER-MIB contains
objects specific to Registrars, Proxies and Redirect servers, and objects specific to Registrars, Proxies and Redirect servers, and
SIP-UA-MIB includes objects specific to User Agents. SIP-TC defines SIP-UA-MIB includes objects specific to User Agents. SIP-TC defines
the textual conventions used throughout MIB modules. the textual conventions used throughout MIB modules.
skipping to change at page 5, line 12 skipping to change at page 4, line 31
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 MIBs 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
various SIP MIB modules in the context of a single system having a various SIP MIB modules in the context of a single system having a
single SNMP agent. single SNMP agent.
This requirement is solved by using the framework provided by the This requirement is solved by using the framework provided by the
NETWORK-SERVICES-MIB, RFC 2788 [18]. A device implementing the SIP NETWORK-SERVICES-MIB, RFC 2788 [2]. 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
skipping to change at page 5, line 36 skipping to change at page 4, line 55
the combined server entity MUST reflect the appropriate the combined server entity MUST reflect the appropriate
combination. For example, "sip_proxy_redirect" or combination. For example, "sip_proxy_redirect" or
"sip_proxy_registrar". "sip_proxy_registrar".
The SNMP agent MAY support any combination of the other attributes The SNMP agent MAY support any combination of the other attributes
in applTable. If the following objects are supported, the object in applTable. If the following objects are supported, the object
values SHOULD be populated as follows: 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. [1], section 7.1.
o applUptime: value MUST be identical to sipServiceStartTime o applUptime: value MUST be identical to sipServiceStartTime
defined in the SIP-COMMON-MIB 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
skipping to change at page 6, line 37 skipping to change at page 6, line 4
while sipProxyCfgTable in SIP-SERVER-MIB might be populated as: while sipProxyCfgTable in SIP-SERVER-MIB might be populated as:
applIndex | sipRequestMaxExpires | sipProxyStatefulness | ... applIndex | sipRequestMaxExpires | sipProxyStatefulness | ...
----------+----------------------+----------------------+---- ----------+----------------------+----------------------+----
1 | 3600 | stateless(1) | 1 | 3600 | stateless(1) |
----------+----------------------+----------------------+---- ----------+----------------------+----------------------+----
and sipRegUserTable in SIP-SERVER-MIB might be populated as: and sipRegUserTable in SIP-SERVER-MIB might be populated as:
applIndex | sipUserIndex | sipUserUri | ... applIndex | sipUserIndex | sipUserUri | ...
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 1 | drwalker@ss8.com | 2 | 1 | drwalker@ss8.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 2 | jmaeng@ipdialog.com | 2 | 2 | jmaeng@ipdialog.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 3 | klingle@cisco.com | 2 | 3 | klingle@cisco.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
2 | 4 | jf.mule@cablelabs.com | 2 | 4 | jfm@cablelabs.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
Example 2: Example 2:
This example illustrates how to represent a system acting as both This example illustrates how to represent a system acting as both
Proxy and Registrar server, where the two entities share a single Proxy and Registrar server, where the two entities share a single
instance of SIP-COMMON-MIB. instance of SIP-COMMON-MIB.
The NETWORK-SERVICES-MIB applTable might be populated as follows: The NETWORK-SERVICES-MIB applTable might be populated as follows:
applIndex | applName | applDescription applIndex | applName | applDescription
skipping to change at page 7, line 31 skipping to change at page 6, line 54
and sipRegUserTable in SIP-SERVER-MIB might be populated as: and sipRegUserTable in SIP-SERVER-MIB might be populated as:
applIndex | sipUserIndex | sipUserUri | ... applIndex | sipUserIndex | sipUserUri | ...
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
1 | 1 | drwalker@ss8networks.com | 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 | jf.mule@cablelabs.com | 1 | 4 | jfm@cablelabs.com |
----------+--------------+--------------------------+---- ----------+--------------+--------------------------+----
The NETWORK-SERVICES-MIB assocTable is not considered a requirement The NETWORK-SERVICES-MIB assocTable is not considered a requirement
for SIP systems. It is not a mandatory group for NETWORK-SERVICES- for SIP systems. It is not a mandatory group for NETWORK-SERVICES-
MIB compliance. MIB compliance.
5. Definitions 5. Definitions
5.1. SIP Textual Conventions 5.1. SIP Textual Conventions
SIP-TC DEFINITIONS ::= BEGIN SIP-TC DEFINITIONS ::= BEGIN
skipping to change at page 8, line 20 skipping to change at page 7, line 23
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 "200202040000Z" LAST-UPDATED "200302250000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO CONTACT-INFO
"SIP MIB email: sip@ietf.org "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
skipping to change at page 8, line 58 skipping to change at page 8, line 17
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 400 Centennial Parkway postal: 400 Centennial Parkway
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 3708 " phone: +1 303 661 3708 "
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Session Initiation Protocol (SIP) MIB Textual
MIB Textual Conventions module used by other Conventions module used by other SIP-related
SIP-related MIB Modules." MIB Modules.
::= { mib-2 9992 } -- to be assigned by IANA
Copyright (C) The Internet Society (2003). This version
of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices."
REVISION "200302250000Z"
DESCRIPTION
"Initial version of the IETF SIP-TC module.
This version published as part of RFC XXXX."
::= { mib-2 xx } -- xx 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
selected transport protocol is in some way dependent selected transport protocol is in some way dependent
skipping to change at page 10, line 17 skipping to change at page 9, line 38
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
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
InetPortNumber
FROM INET-ADDRESS-MIB;
sipCommonMIB MODULE-IDENTITY sipCommonMIB MODULE-IDENTITY
LAST-UPDATED "200202040000Z" LAST-UPDATED "200302250000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO CONTACT-INFO
"SIP MIB email: sip@ietf.org "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
skipping to change at page 10, line 58 skipping to change at page 10, line 25
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 400 Centennial Parkway postal: 400 Centennial Parkway
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 3708 " phone: +1 303 661 3708 "
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Session Initiation Protocol (SIP) Common MIB module.
Common MIB module. This module defines objects which This module defines objects which may be common to all
may be common to all SIP entities. 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 3261 (June
1999). 2002).
This MIB is defined for 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.
skipping to change at page 11, line 39 skipping to change at page 11, line 5
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. Unlike
a Proxy server it does not initiate requests. Unlike a Proxy server it does not initiate requests. Unlike
a User Agent Server it does not accept calls. a User Agent Server it does not accept calls.
A Registrar 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 9990 } -- to be assigned by IANA
Copyright (C) The Internet Society (2003). This version
of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices."
REVISION "200302250000Z"
DESCRIPTION
"Initial version of the IETF SIP-COMMON-MIB module.
This version published as part of RFC XXXX."
::= { mib-2 xx } -- xx to be assigned by IANA
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 } sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 }
sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 } sipCommonMIBObjects OBJECT IDENTIFIER ::= { sipCommonMIB 1 }
sipCommonMIBConform OBJECT IDENTIFIER ::= { sipCommonMIB 2 } sipCommonMIBConform OBJECT IDENTIFIER ::= { sipCommonMIB 2 }
-- --
-- This MIB contains objects that are common to all SIP entities. -- This MIB contains objects that are common to all SIP entities.
-- --
sipCommonCfgBase OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 } sipCommonCfgBase OBJECT IDENTIFIER ::= { sipCommonMIBObjects 1 }
skipping to change at page 13, line 20 skipping to change at page 12, line 45
quiescing(5), quiescing(5),
testing(6), testing(6),
unknown(7) 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 : 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 : The application is currently unable to
process SIP messages. process SIP messages.
congested(3) : The application is operational but no congested : The application is operational but no
additional inbound transactions can be additional inbound transactions can be
accomodated at the moment. accommodated at the moment.
restarting(4) : The application is currently unavailable restarting : The application is currently unavailable
but it is in the process of restarting and but it is in the process of restarting and
will, presumably, soon be able to process will, presumably, soon be able to process
SIP messages. SIP messages.
quiescing(5) : The application is currently operational quiescing : The application is currently operational
but has been administratively put into but has been administratively put into
quiese mode. Additional inbound transactions quiesce mode. Additional inbound transactions
may be rejected. may be rejected.
testing(6) : The application is currently in test mode testing : The application is currently in test mode
and may not be able to process SIP messages. and may not be able to process SIP messages.
unknown(7) : The operational status cannot be determined unknown : The operational status cannot be determined
for some reason." for some reason."
::= { sipCommonCfgEntry 2 } ::= { sipCommonCfgEntry 2 }
sipServiceAdminStatus OBJECT-TYPE sipServiceAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noop(1), noop(1),
up(2), up(2),
down(3), down(3),
reset(4), reset(4),
quieseSessions(5), quiesceSessions(5),
quieseApplication(6) quiesceApplication(6)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to affect the overall operational "This object is used to affect the overall operational
state of the SIP application. When read, this object state of the SIP application. When read, this object
always return a value of noop(1) since sipServiceOperStatus always return a value of noop(1) since sipServiceOperStatus
reflects the actual operational status. reflects the actual operational status.
noop(1) : Setting this object to a noop value noop : Setting this object to a noop value
has no effect; when read, this value has no effect; when read, this value
is always returned. is always returned.
up(2) : Enable the application. up : Enable the application.
down(3) : Abrupt shutdown. Immediately terminate. down : Abrupt shutdown. Immediately terminate.
reset(4) : Restart application, reinitialize data. reset : Restart application, reinitialize data.
quieseSessions(5) : Enable quiescence mode. Stop accepting quiesceSessions : Enable quiescence mode. Stop accepting
any new SIP sessions. Stop processing any new SIP sessions. Stop processing
new transactions except for transactions new transactions except for transactions
associated with an existing session or associated with an existing session or
call. call.
quieseApplications(6): Enable quiescence mode. Stop processing quiesceApplications : Enable quiescence mode. Stop processing
new SIP transactions except for new SIP transactions except for
transactions associated with existing transactions associated with existing
applications. The exact application applications. The exact application
behavior should be specified by the behavior should be specified by the
implementation." implementation."
::= { sipCommonCfgEntry 3 } ::= { sipCommonCfgEntry 3 }
sipServiceStartTime OBJECT-TYPE sipServiceStartTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 14, line 57 skipping to change at page 14, line 23
sipOrganization OBJECT-TYPE sipOrganization OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the organization name which the SIP "This object contains the organization name which the SIP
entity inserts into Organization headers of SIP messages entity inserts into Organization headers of SIP messages
processed by this system. If the sting is empty, no processed by this system. If the sting is empty, no
Organization header is to be generated." Organization header is to be generated."
REFERENCE REFERENCE
"RFC 2543, Section 6.24" "RFC 3261, Section 20.25"
::= { sipCommonCfgEntry 6 } ::= { sipCommonCfgEntry 6 }
sipMaxSessions OBJECT-TYPE sipMaxSessions OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum number of 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 }
sipRequestUriHostMatching OBJECT-TYPE sipRequestUriHostMatching OBJECT-TYPE
skipping to change at page 15, line 16 skipping to change at page 14, line 38
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 }
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 Location Service may be used to
returned by the server. obtain information about a callee's possible location(s)
If the value is ĉfalseĈ, then no match is required." or a 404 Not Found status code is returned by the server.
If the value is 'false', then no match is required."
REFERENCE REFERENCE
"RFC 2543, Section 4.3" "RFC 3261, Section 8.1.1.1"
::= { sipCommonCfgEntry 8 } ::= { 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
skipping to change at page 16, line 4 skipping to change at page 15, line 25
DESCRIPTION DESCRIPTION
"Specification of a particular port. "Specification of a particular port.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
entity 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, sipPort } INDEX { applIndex, sipPort }
::= { sipPortTable 1 } ::= { sipPortTable 1 }
SipPortEntry ::= SipPortEntry ::=
SEQUENCE { SEQUENCE {
sipPort INTEGER, sipPort InetPortNumber,
sipTransportRcv SipTransportProtocol, sipTransportRcv SipTransportProtocol,
sipTransportSnd SipTransportProtocol, sipTransportSnd SipTransportProtocol,
sipPortStatus RowStatus sipPortStatus RowStatus
} }
sipPort OBJECT-TYPE sipPort OBJECT-TYPE
SYNTAX INTEGER (1..65535) SYNTAX InetPortNumber
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects a particular port that can be used by "This object reflects a particular port that can be used by
the SIP application." the SIP application."
::= { sipPortEntry 1 } ::= { sipPortEntry 1 }
sipTransportRcv OBJECT-TYPE sipTransportRcv OBJECT-TYPE
SYNTAX SipTransportProtocol SYNTAX SipTransportProtocol
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 17, line 24 skipping to change at page 16, line 47
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 3261, Section 20.10"
::= { sipCommonCfgBase 3 } ::= { sipCommonCfgBase 3 }
sipUriSupportedEntry OBJECT-TYPE sipUriSupportedEntry OBJECT-TYPE
SYNTAX SipUriSupportedEntry SYNTAX SipUriSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular non-SIP URI supported by the SIP entity. "A particular non-SIP URI supported by the SIP entity.
Each row represents those objects for a particular SIP Each row represents those objects for a particular SIP
skipping to change at page 18, line 45 skipping to change at page 18, line 12
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 3261, Section 19.2"
::= { sipCommonCfgBase 4 } ::= { sipCommonCfgBase 4 }
sipFtrSupportedEntry OBJECT-TYPE sipFtrSupportedEntry OBJECT-TYPE
SYNTAX SipFtrSupportedEntry SYNTAX SipFtrSupportedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A particular feature supported by the SIP "A particular feature supported by the SIP
entity, and which may be required by a peer. entity, and which may be required by a peer.
skipping to change at page 19, line 38 skipping to change at page 18, line 59
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 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 }
-- --
-- Support for extension methods
--
sipExtMethodSupportedTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipExtMethodSupportedEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains a list of extension methods supported
by each SIP entity in this system. These are in addition
to the standard set of SIP methods discussed in Section
7.1 of RFC 3261. Any additional methods that may be
incorporated into the SIP protocol should be represented
by this table without any requirement to update this MIB.
The table is informational in nature; conveying to the NMS
capabilities of the managed system."
::= { sipCommonCfgBase 5 }
sipExtMethodSupportedEntry OBJECT-TYPE
SYNTAX SipExtMethodSupportedEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A particular extension method supported by the SIP entity.
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, sipExtMethodSupportedIndex }
::= { sipExtMethodSupportedTable 1 }
SipExtMethodSupportedEntry ::=
SEQUENCE {
sipExtMethodSupportedIndex Unsigned32,
sipExtMethodName SnmpAdminString
}
sipExtMethodSupportedIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object uniquely identifies a conceptual row
in the table."
::= { sipExtMethodSupportedEntry 1 }
sipExtMethodName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the supported extension method's name."
::= { sipExtMethodSupportedEntry 2 }
--
-- SIP Timer Configuration -- SIP Timer Configuration
-- --
sipCommonCfgTimerTable OBJECT-TYPE sipCommonCfgTimerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgTimerEntry SYNTAX SEQUENCE OF SipCommonCfgTimerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains timer configuration objects applicable "This table contains timer configuration objects applicable
to SIP user agent and SIP stateful proxy entities." to SIP user agent and SIP stateful proxy entities."
::= { sipCommonCfgTimer 1 } ::= { sipCommonCfgTimer 1 }
skipping to change at page 20, line 10 skipping to change at page 20, line 31
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 }
::= { sipCommonCfgTimerTable 1 } ::= { sipCommonCfgTimerTable 1 }
SipCommonCfgTimerEntry ::= SipCommonCfgTimerEntry ::=
SEQUENCE { SEQUENCE {
sipCfgInitialTimerInvite Unsigned32, sipCfgTimerA Unsigned32,
sipCfgTimerProv Unsigned32, sipCfgTimerB Unsigned32,
sipCfgInitialTimerBye Unsigned32, sipCfgTimerC Unsigned32,
sipCfgTimerD Unsigned32,
sipCfgInitialTimerRegister Unsigned32, sipCfgTimerE Unsigned32,
sipCfgInitialTimerOptions Unsigned32, sipCfgTimerF Unsigned32,
sipCfgInitialTimerInfo Unsigned32, sipCfgTimerG Unsigned32,
sipCfgInitialTimerRsp Unsigned32, sipCfgTimerH Unsigned32,
sipCfgTimerT2 Unsigned32 sipCfgTimerI Unsigned32,
sipCfgTimerJ Unsigned32,
sipCfgTimerK Unsigned32,
sipCfgTimerT1 Unsigned32,
sipCfgTimerT2 Unsigned32,
sipCfgTimerT4 Unsigned32
} }
sipCfgInitialTimerInvite OBJECT-TYPE sipCfgTimerA OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the initial value for the retransmit
timer for the INVITE method. The retransmit timer doubles timer for the INVITE method. The retransmit timer doubles
after each retransmission, ensuring an exponential backoff after each retransmission, ensuring an exponential backoff
in network traffic. This object represents the initial time in network traffic. This object represents the initial time
a SIP entity will wait to receive a provisional response to a SIP entity will wait to receive a provisional response to
an INVITE before resending the INVITE request." an INVITE before resending the INVITE request."
REFERENCE
"RFC 3261, Section 17.1.1.2"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 1 } ::= { sipCommonCfgTimerEntry 1 }
sipCfgTimerProv OBJECT-TYPE sipCfgTimerB OBJECT-TYPE
SYNTAX Unsigned32 (60000..300000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum time a SIP entity will wait "This object specifies the maximum time a SIP entity will
to receive a final response to an INVITE. The timer is started wait to receive a final response to an INVITE. The
upon receipt of a provisional response." timer is started upon transmission of the initial INVITE
DEFVAL { 60000 } request."
REFERENCE
"RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 2 } ::= { sipCommonCfgTimerEntry 2 }
sipCfgInitialTimerBye OBJECT-TYPE sipCfgTimerC OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (180000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the maximum time a SIP proxy will
timer for the BYE method. The retransmit timer doubles wait to receive a provisional response to an INVITE.
after each retransmission, ensuring an exponential backoff The Timer C MUST be set for each client transaction when
in network traffic. This object represents the initial time an INVITE request is proxied. The timer MUST be larger
a SIP entity will wait to receive a response to a BYE request." than 3 minutes."
DEFVAL { 500 } REFERENCE
"RFC 3261, Section 16.6"
DEFVAL { 180000 }
::= { sipCommonCfgTimerEntry 3 } ::= { sipCommonCfgTimerEntry 3 }
sipCfgInitialTimerRegister OBJECT-TYPE sipCfgTimerD OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (0..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the amount of time that the server
timer for the REGISTER method. The retransmit timer doubles transaction can remain in the 'Completed' state when
after each retransmission, ensuring an exponential backoff unreliable transports are used. The default value must be
in network traffic. This object represents the initial time greater than 32000 for UDP transport and its value must
a SIP entity will wait to receive a response to a REGISTER be 0 for TCP/SCTP transport."
request." REFERENCE
DEFVAL { 500 } "RFC 3261, Section 17.1.1.2"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 4 } ::= { sipCommonCfgTimerEntry 4 }
sipCfgInitialTimerOptions OBJECT-TYPE sipCfgTimerE OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (100..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the initial value for the retransmit
timer for the OPTIONS method. The retransmit timer doubles timer for a non-INVITE method while in 'Trying State'.
after each retransmission, ensuring an exponential backoff The retransmit timer doubles after each retransmission
until it reaches T2 to ensure an exponential backoff
in network traffic. This object represents the initial time in network traffic. This object represents the initial time
a SIP entity will wait to receive a response to an OPTIONS a SIP entity will wait to receive a provisional response to
request." the request before resending the non-INVITE request."
REFERENCE
"RFC 3261, Section 17.1.2.2"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 5 } ::= { sipCommonCfgTimerEntry 5 }
sipCfgInitialTimerInfo OBJECT-TYPE sipCfgTimerF OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the maximum time a SIP entity will
timer for the INFO method. The retransmit timer doubles wait to receive a final response to a non-INVITE request.
after each retransmission, ensuring an exponential backoff The timer is started upon transmission of the
in network traffic. This object represents the initial time initial request."
a SIP entity will wait to receive a response to a INFO request." REFERENCE
DEFVAL { 500 } "RFC 3261, Section 17.1.2.2"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 6 } ::= { sipCommonCfgTimerEntry 6 }
sipCfgInitialTimerRsp OBJECT-TYPE sipCfgTimerG OBJECT-TYPE
SYNTAX Unsigned32 (100..1000) SYNTAX Unsigned32 (0..1000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the initial value for the retransmit "This object specifies the initial value for the retransmit
timer for final responses. The retransmit timer doubles timer for final responses to INVITE requests.
after each retransmission, ensuring an exponential backoff If timer G fires, the response is passed to the transport
in network traffic. This object represents the initial time layer once more for retransmission, and timer G is set
a SIP entity will wait to retransmit a final response." to fire in MIN(2*T1, T2) seconds. From then on, when
REFERENCE "Section 10.5.1 RFC2543" timer G fires, the response is passed to the transport
again for transmission, and timer G is reset with a value
that doubles, unless that value exceeds T2, in which case
it is reset with the value of T2.
The default value must be T1 for UDP transport and its value
must be 0 for reliable transport like TCP/SCTP."
REFERENCE
"RFC 3261, Section 17.2.1"
DEFVAL { 500 } DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 7 } ::= { sipCommonCfgTimerEntry 7 }
sipCfgTimerH OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the maximum time a server will wait
to receive an ACK before it abandons retransmitting the
response. The timer is started upon entering the
'Completed' state."
REFERENCE
"RFC 3261, Section 17.2.1"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 8 }
sipCfgTimerI OBJECT-TYPE
SYNTAX Unsigned32 (0..10000)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the maximum time a SIP entity will
wait to receive additional ACK message retransmissions.
The timer is started upon entering the 'Confirmed' state.
The default value must be T4 for UDP transport and its value
must be 0 for reliable transport like TCP/SCTP."
REFERENCE
"RFC 3261, Section 17.2.1"
DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 9 }
sipCfgTimerJ OBJECT-TYPE
SYNTAX Unsigned32 (32000..300000)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the maximum time a SIP server will
wait to receive retransmissions of non-INVITE request.
The timer is started upon entering the 'Completed' state
for non-INVITE transactions. When timer J fires, the server
must transition to the 'Terminated' state."
REFERENCE "RFC 3261, Section 17.2.2"
DEFVAL { 32000 }
::= { sipCommonCfgTimerEntry 10 }
sipCfgTimerK OBJECT-TYPE
SYNTAX Unsigned32 (0..10000)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the maximum time a SIP client will
wait to receive retransmissions of responses to non-INVITE
requests.
The timer is started upon entering the 'Completed' state
for non-INVITE transactions. When timer K fires, the server
must transition to the 'Terminated' state.
The default value must be T4 for UDP transport and its value
must be 0 for reliable transport like TCP/SCTP."
REFERENCE
"RFC 3261, Section 17.1.2.2"
DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 11 }
sipCfgTimerT1 OBJECT-TYPE
SYNTAX Unsigned32 (200..10000)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the T1 timer for a SIP entity. T1
is an estimate of the round-trip time (RTT) between the
client and server transactions."
REFERENCE "RFC 3261, Section 17"
DEFVAL { 500 }
::= { sipCommonCfgTimerEntry 12 }
sipCfgTimerT2 OBJECT-TYPE sipCfgTimerT2 OBJECT-TYPE
SYNTAX Unsigned32 (200..10000) SYNTAX Unsigned32 (200..10000)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the T2 timer for a SIP entity." "This object specifies the T2 timer for a SIP entity."
REFERENCE "Section 10.4 and 10.5 RFC2543" REFERENCE "RFC 3261, Section 17"
DEFVAL { 4000 } DEFVAL { 4000 }
::= { sipCommonCfgTimerEntry 8 } ::= { sipCommonCfgTimerEntry 13 }
sipCfgTimerT4 OBJECT-TYPE
SYNTAX Unsigned32 (200..10000)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the T4 timer for a SIP entity."
REFERENCE "RFC 3261, Section 17"
DEFVAL { 5000 }
::= { sipCommonCfgTimerEntry 14 }
-- --
-- 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
skipping to change at page 23, line 20 skipping to change at page 25, line 42
table." table."
::= { sipCommonCfgTimerExtMethodEntry 1 } ::= { sipCommonCfgTimerExtMethodEntry 1 }
sipCfgTimerExtMethodName OBJECT-TYPE sipCfgTimerExtMethodName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
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
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
skipping to change at page 27, line 8 skipping to change at page 29, line 26
table." table."
::= { sipCommonCfgRetryExtMethodEntry 1 } ::= { sipCommonCfgRetryExtMethodEntry 1 }
sipCfgRetryExtMethodName OBJECT-TYPE sipCfgRetryExtMethodName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
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
to be requested."
::= { 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."
skipping to change at page 28, line 53 skipping to change at page 31, line 10
sipCfgExpiresHeaderMethod OBJECT-TYPE sipCfgExpiresHeaderMethod OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
invite(0), invite(0),
register(1) register(1)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention is a bit map. Each bit represents a "This convention is a bit map. Each bit represents a
sip method where the Expires header line must be present. SIP method where the Expires header should be included.
If a bit has value 1, then that messages corresponding If a bit has value 1, then the requests corresponding
to that SIP method must include an Expires header line. to that SIP method must include an Expires header line.
If a bit has value 0, then the Expires header line is If a bit has value 0, then the Expires header line will
not present. not be added.
Combinations of bits can be set when the Expires header Combinations of bits can be set when the Expires header
line is required in multiple SIP methods. line is required in multiple SIP methods.
bit 0 : INVITE method. bit 0 : INVITE method.
bit 1 : REGISTER Method." bit 1 : REGISTER Method."
::= { sipCommonCfgExpiresMethodEntry 3 } ::= { sipCommonCfgExpiresMethodEntry 3 }
sipCommonCfgExpiresStatusCodeTable OBJECT-TYPE sipCommonCfgExpiresStatusCodeTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgExpiresStatusCodeEntry SYNTAX SEQUENCE OF SipCommonCfgExpiresStatusCodeEntry
skipping to change at page 31, line 58 skipping to change at page 34, line 15
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 and in progress. It is not applicable to stateless that are in progress and transactions that have reached the
terminated state. It is not applicable to stateless
SIP proxy servers. 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.
If the request is INVITE and the final response is a non-2xx,
the transaction also include an ACK to the response. The ACK
for a 2xx response to an INVITE request is a separate
transaction.
The branch ID parameter in the Via header field values
serves as a transaction identifier.
A transaction is identified by the CSeq sequence number A transaction is identified by the CSeq sequence number
within a single call leg. The ACK request has the same within a single call leg. The ACK request has the same
CSeq number as the corresponding INVITE request, but CSeq number as the corresponding INVITE request, but
comprises a transaction of its own. comprises a transaction of its own.
In the case of a forked request, all branches count as 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." For a transaction stateless proxy, this counter is always 0."
::= { sipSummaryStatsEntry 5 } ::= { sipSummaryStatsEntry 5 }
skipping to change at page 33, line 20 skipping to change at page 35, line 43
} }
sipStatsInviteIns OBJECT-TYPE sipStatsInviteIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE requests "This object reflects the total number of INVITE requests
received by the SIP entity including retransmissions." received by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 1 } ::= { sipMethodStatsEntry 1 }
sipStatsInviteOuts OBJECT-TYPE sipStatsInviteOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INVITE requests "This object reflects the total number of INVITE requests
sent by the SIP entity including retransmissions." sent by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.1" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 2 } ::= { sipMethodStatsEntry 2 }
sipStatsAckIns OBJECT-TYPE sipStatsAckIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of ACK requests "This object reflects the total number of ACK requests
received by the SIP entity." received by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.2" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 3 } ::= { sipMethodStatsEntry 3 }
sipStatsAckOuts OBJECT-TYPE sipStatsAckOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of ACK requests sent "This object reflects the total number of ACK requests sent
by the SIP entity." by the SIP entity."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.2" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 4 } ::= { sipMethodStatsEntry 4 }
sipStatsByeIns OBJECT-TYPE sipStatsByeIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of BYE requests "This object reflects the total number of BYE requests
received by the SIP entity including retransmissions." received by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.4" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 5 } ::= { sipMethodStatsEntry 5 }
sipStatsByeOuts OBJECT-TYPE sipStatsByeOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of BYE requests sent "This object reflects the total number of BYE requests sent
by the SIP entity including retransmissions." by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.4" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 6 } ::= { sipMethodStatsEntry 6 }
sipStatsCancelIns OBJECT-TYPE sipStatsCancelIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of CANCEL requests "This object reflects the total number of CANCEL requests
received by the SIP entity including retransmissions." received by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.5" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 7 } ::= { sipMethodStatsEntry 7 }
sipStatsCancelOuts OBJECT-TYPE sipStatsCancelOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of CANCEL requests "This object reflects the total number of CANCEL requests
sent by the SIP entity including retransmissions." sent by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.5" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 8 } ::= { sipMethodStatsEntry 8 }
sipStatsOptionsIns OBJECT-TYPE sipStatsOptionsIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of OPTIONS requests "This object reflects the total number of OPTIONS requests
received by the SIP entity including retransmissions." received by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.3" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 9 } ::= { sipMethodStatsEntry 9 }
sipStatsOptionsOuts OBJECT-TYPE sipStatsOptionsOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of OPTIONS requests "This object reflects the total number of OPTIONS requests
sent by the SIP entity including retransmissions." sent by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.3" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 10 } ::= { sipMethodStatsEntry 10 }
sipStatsRegisterIns OBJECT-TYPE sipStatsRegisterIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of REGISTER requests "This object reflects the total number of REGISTER requests
received by the SIP entity including retransmissions." received by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.6" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 11 } ::= { sipMethodStatsEntry 11 }
sipStatsRegisterOuts OBJECT-TYPE sipStatsRegisterOuts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of REGISTER requests "This object reflects the total number of REGISTER requests
sent by the SIP entity including retransmissions." sent by the SIP entity including retransmissions."
REFERENCE REFERENCE
"RFC 2543, Section 4.2.6" "RFC 3261, Section 7.1"
::= { sipMethodStatsEntry 12 } ::= { sipMethodStatsEntry 12 }
sipStatsInfoIns OBJECT-TYPE sipStatsInfoIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of INFO requests "This object reflects the total number of INFO requests
received by the SIP entity including retransmissions." received by the SIP entity including retransmissions."
REFERENCE REFERENCE
skipping to change at page 37, line 6 skipping to change at page 39, line 21
sipStatsExtMethodName OBJECT-TYPE sipStatsExtMethodName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the name of the particular extension "This object contains the name of the particular extension
method that the SIP entity has been requested to monitor. method that the SIP entity has been requested to monitor.
For example, it may contain the string 'REFER' if the For example, it may contain the string 'REFER' if the
network management station has requested that the SIP network management station has requested that the SIP
entity count the number of messages sent an received entity count the number of messages sent an received
which containing a REFER method. It is an error for any which containing a REFER method."
of the methods contained in RFC 2543 to be requested."
::= { sipStatsExtMethodEntry 2 } ::= { sipStatsExtMethodEntry 2 }
sipStatsExtMethodIns OBJECT-TYPE sipStatsExtMethodIns OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the total number of requests received "This object reflects the total number of requests received
by the SIP entity which requested the method contained in by the SIP entity which requested the method contained in
the sipStatsExtMethodName column including retransmissions the sipStatsExtMethodName column including retransmissions
skipping to change at page 37, line 40 skipping to change at page 39, line 54
::= { 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 If set to 'notInService', all counters will cease to
reset to zero and any associated notifications will be increment and retain their last known value.
disabled. Associated notifications are specified in the If subsequently set to 'active' the counters will begin
sipCommonStatusCodeNotifTable. to increment again."
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
DESCRIPTION DESCRIPTION
"This table contains statistics on response status code "This table contains statistics on response status code
classes for each SIP entity in this system." classes for each SIP entity in this system."
::= { sipCommonStatusCode 1 } ::= { sipCommonStatusCode 1 }
skipping to change at page 44, line 20 skipping to change at page 46, line 24
} }
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 message 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 }
::= { sipCommonStatusCodeNotifEntry 1 } ::= { sipCommonStatusCodeNotifEntry 1 }
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
SIP response messages sent or received SIP response messages sent or received
that contains the desired status code. that contains the desired status code.
No more notifs are emitted until this No more notifications are emitted until this
object is set to either 'oneShot' again object is set to either 'oneShot' again
or 'normal'. This option is provided or 'normal'. This option is provided
as a means of quelling the potential as a means of quelling the potential
promiscuous behavior that can be associated promiscuous behavior that can be associated
with the sipStatusCodeNotif. with the sipStatusCodeNotif.
triggered : This value is only readable and cannot be triggered : This value is only readable and cannot be
set. It reflects when the 'oneShot' has set. It reflects when the 'oneShot' has
occurred and indicates the mode needs to occurred and indicates the mode needs to
be reset to get further notifications. be reset to get further notifications.
skipping to change at page 48, line 15 skipping to change at page 50, line 19
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,
sipTransMethod SnmpAdminString, sipTransMethod SnmpAdminString,
sipTransActivityInfo SnmpAdminString sipTransActivityInfo SnmpAdminString,
sipTransBranchID 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 }
skipping to change at page 49, line 33 skipping to change at page 51, line 40
} }
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. Note that some of the object values transaction. Note that some of the object values
may only be applicable to some transaction types may only be applicable to some transaction types
(for example, INVITE and non-INVITE transaction (for example, INVITE and non-INVITE transaction
states differ). states differ).
null(1) : The SIP entity is not active. null : The SIP entity is not active.
initial(2) : Prior to sending or receiving any initial : Prior to sending or receiving any
request. request.
calling(3) : After sending the request and prior to calling : After sending the request and prior to
receiving any response. receiving any response.
ringing(4) : After receiving one or more ringing : After receiving one or more
informational (1xx) responses. informational (1xx) responses.
completed(5) : After ACK has been sent following completed : After ACK has been sent following
reception of definitive response. reception of definitive response.
callProceeding(6) : Entered on reception of an INVITE. callProceeding : Entered on reception of an INVITE.
failure(7) : Entered when call fails(send status failure : Entered when call fails(send status
code>=300). code>=300).
success(8) : Entered when user answers(send status success : Entered when user answers(send status
code=200). code=200).
confirmed(9) : Entered on reception of an ACK in confirmed : Entered on reception of an ACK in
failure or success states." failure or success states."
REFERENCE REFERENCE
"RFC 2543, Figures 12 and 13" "RFC 2543, Figures 12 and 13"
::= { sipTransactionEntry 6 } ::= { sipTransactionEntry 6 }
sipTransNumOutstandingBranches OBJECT-TYPE sipTransNumOutstandingBranches OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of branches "This object contains a count of the number of branches
awaiting a final response. Only a forking proxy will have awaiting a final response. Only a forking proxy will have
a value greater than one." a value greater than one."
::= { sipTransactionEntry 7 } ::= { sipTransactionEntry 7 }
sipTransExpiry OBJECT-TYPE sipTransExpiry OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
skipping to change at page 50, line 46 skipping to change at page 52, line 52
element indicates the direction of the latest message element indicates the direction of the latest message
(received or sent) and the second element is the SIP request (received or sent) and the second element is the SIP request
name or SIP response code. name or SIP response code.
Examples of valid strings are: Examples of valid strings are:
sent 100 sent 100
received INVITE received INVITE
sent BYE sent BYE
received 200" received 200"
::= { sipTransactionEntry 10 } ::= { sipTransactionEntry 10 }
sipTransBranchID OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the value of the branch parameter
in the top Via header of the current transaction. This value
uniquely identifies a transaction. The parameter name will
be part of this object value.
For example, 'branch=z9hG4bK77ef4c2312983.1"
::= { sipTransactionEntry 11 }
-- --
-- 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.
--
-- --
sipCommonStatsRetryTable OBJECT-TYPE sipCommonStatsRetryTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonStatsRetryEntry SYNTAX SEQUENCE OF SipCommonStatsRetryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains retry statistics objects applicable "This table contains retry statistics objects applicable
to each SIP entity in this system." to each SIP entity in this system."
::= { sipCommonStatsRetry 1 } ::= { sipCommonStatsRetry 1 }
skipping to change at page 57, line 37 skipping to change at page 59, line 51
sipProtocolVersion, sipProtocolVersion,
sipServiceOperStatus, sipServiceOperStatus,
sipServiceAdminStatus, sipServiceAdminStatus,
sipServiceStartTime, sipServiceStartTime,
sipServiceLastChange, sipServiceLastChange,
sipTransportRcv, sipTransportRcv,
sipTransportSnd, sipTransportSnd,
sipPortStatus, sipPortStatus,
sipUriSupported, sipUriSupported,
sipFtrSupported, sipFtrSupported,
sipExtMethodName,
sipOrganization, sipOrganization,
sipMaxSessions, sipMaxSessions,
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, sipCfgTimerA,
sipCfgTimerProv, sipCfgTimerB,
sipCfgInitialTimerBye, sipCfgTimerC,
sipCfgInitialTimerRegister, sipCfgTimerD,
sipCfgInitialTimerOptions, sipCfgTimerE,
sipCfgInitialTimerInfo, sipCfgTimerF,
sipCfgInitialTimerRsp, sipCfgTimerG,
sipCfgTimerT2 sipCfgTimerH,
sipCfgTimerI,
sipCfgTimerJ,
sipCfgTimerK,
sipCfgTimerT1,
sipCfgTimerT2,
sipCfgTimerT4
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing timer configuration "A collection of objects providing timer configuration
common to all SIP enities." common to all SIP enities."
::= { sipCommonMIBGroups 2 } ::= { sipCommonMIBGroups 2 }
sipCommonConfigTimerExtMethodGroup OBJECT-GROUP sipCommonConfigTimerExtMethodGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgTimerExtMethodName, sipCfgTimerExtMethodName,
skipping to change at page 59, line 45 skipping to change at page 62, line 7
sipCurrentTransactions, sipCurrentTransactions,
sipTransTo, sipTransTo,
sipTransFrom, sipTransFrom,
sipTransCallId, sipTransCallId,
sipTransCSeq, sipTransCSeq,
sipTransState, sipTransState,
sipTransNumOutstandingBranches, sipTransNumOutstandingBranches,
sipTransExpiry, sipTransExpiry,
sipTransMethod, sipTransMethod,
sipTransActivityInfo, sipTransActivityInfo,
sipTransBranchID,
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 61, line 38 skipping to change at page 63, line 57
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 "200202040000Z" LAST-UPDATED "200302250000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO CONTACT-INFO
"SIP MIB email: sip@ietf.org "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
skipping to change at page 62, line 20 skipping to change at page 64, line 40
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 400 Centennial Parkway postal: 400 Centennial Parkway
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 3708 " phone: +1 303 661 3708 "
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Session Initiation Protocol (SIP) User Agent (UA)
User Agent (UA) MIB module. 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).
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
Copyright (C) The Internet Society (2003). This version
of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices."
REVISION "200302250000Z"
DESCRIPTION
"Initial version of the IETF SIP-UA-MIB module.
This version published as part of RFC XXXX."
::= { mib-2 xx } -- xx to be assigned by IANA
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipUAMIBObjects OBJECT IDENTIFIER ::= { sipUAMIB 1 } sipUAMIBObjects OBJECT IDENTIFIER ::= { sipUAMIB 1 }
sipUAMIBConform OBJECT IDENTIFIER ::= { sipUAMIB 2 } 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 }
skipping to change at page 63, line 47 skipping to change at page 66, line 20
be tried." be tried."
::= { sipUACfgSipServerEntry 1 } ::= { sipUACfgSipServerEntry 1 }
sipUACfgSipServerAddrType OBJECT-TYPE sipUACfgSipServerAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the type of address contained "This object specifies the type of address contained
in the associated instance of sipUACfgSipServerAddr." in the associated instance of sipUACfgSipServerAddr."
REFERENCE "INET-ADDRESS-MIB (RFC 2851)" REFERENCE "INET-ADDRESS-MIB (RFC 3291)"
DEFVAL { ipv4 } DEFVAL { ipv4 }
::= { sipUACfgSipServerEntry 2 } ::= { sipUACfgSipServerEntry 2 }
sipUACfgSipServerAddr OBJECT-TYPE sipUACfgSipServerAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the address of a SIP server "This object specifies the address of a SIP server
this user agent will use to proxy/redirect calls." this user agent will use to proxy/redirect calls."
skipping to change at page 65, line 48 skipping to change at page 68, line 21
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 "200202040000Z" LAST-UPDATED "200302250000Z"
ORGANIZATION "IETF SIP Working Group, SIP MIB Team" ORGANIZATION "IETF SIP Working Group, SIP MIB Team"
CONTACT-INFO CONTACT-INFO
"SIP MIB email: sip@ietf.org "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
skipping to change at page 66, line 33 skipping to change at page 69, line 5
phone: +1 613 592 2100 phone: +1 613 592 2100
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 400 Centennial Parkway postal: 400 Centennial Parkway
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 3708 " phone: +1 303 661 3708 "
DESCRIPTION DESCRIPTION
"Initial version of Session Initiation Protocol (SIP) "Session Initiation Protocol (SIP) Server MIB module.
Server MIB module.
SIP is an application-layer signalling protocol for SIP is an application-layer signaling protocol for
creating, modifying and terminating multimedia creating, modifying and terminating multimedia
sessions with one or more participants. These sessions 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. returns zero or more addresses to that client.
Unlike a User Agent Server it does not accept calls. Unlike 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
Copyright (C) The Internet Society (2003). This
version
of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices."
REVISION "200302250000Z"
DESCRIPTION
"Initial version of the IETF SIP-SERVER-MIB module.
This version published as part of RFC XXXX."
::= { mib-2 xx } -- xx to be assigned by IANA
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 } sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 }
sipServerMIBConform OBJECT IDENTIFIER ::= { sipServerMIB 2 } sipServerMIBConform OBJECT IDENTIFIER ::= { sipServerMIB 2 }
-- --
-- These groups 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
sipServerStats OBJECT IDENTIFIER ::= { sipServerMIBObjects 2 } 1 }
sipServerStats OBJECT IDENTIFIER ::= { sipServerMIBObjects
2 }
-- --
-- Common Server Configuration Objects -- Common Server Configuration Objects
-- --
sipServerCfgTable OBJECT-TYPE sipServerCfgTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipServerCfgEntry SYNTAX SEQUENCE OF SipServerCfgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains configuration objects applicable "This table contains configuration objects applicable
skipping to change at page 68, line 47 skipping to change at page 71, line 35
-- Additional Server Configuration -- Additional Server Configuration
-- --
sipServerContactDfltAction OBJECT-TYPE sipServerContactDfltAction OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
redirect(1), redirect(1),
proxy(2) proxy(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether the default contact action "This object specifies whether the default contact
action
of the server is to be a proxy or a redirect server. A of the server is to be a proxy or a redirect server. A
User Agent may indicate a preference upon registration of User Agent may indicate a preference upon registration
Contact information. The value of this object is used in of
Contact information. The value of this object is used
in
the absence of such an indication." the absence of such an indication."
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
::= { sipServerCfgEntry 4 } ::= { sipServerCfgEntry 4 }
sipServerRespectUAAction OBJECT-TYPE sipServerRespectUAAction OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether the server should respect "This object specifies whether the server should respect
the wishes of a User Agent when the UA specifies a server the wishes of a User Agent when the UA specifies a
server
action (proxy or redirect) for certain Contact action (proxy or redirect) for certain Contact
information. If the value of this object is false, then information. If the value of this object is false,
then
the value contained in the sipServerContactDfltAction the value contained in the sipServerContactDfltAction
is used." is used."
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
::= { sipServerCfgEntry 5 } ::= { sipServerCfgEntry 5 }
-- --
-- This group contains MIB objects related to SIP Proxy Servers. -- This group contains MIB objects related to SIP Proxy Servers.
-- --
sipProxyCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 3 } sipProxyCfg OBJECT IDENTIFIER ::= { sipServerMIBObjects 3 }
skipping to change at page 70, line 36 skipping to change at page 73, line 35
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
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, or simply a 'stateful A transaction stateful proxy, or simply a 'stateful
proxy', maintains state information for the duration of proxy', maintains state information for the duration of
a SIP transaction. If the value if this object is a SIP transaction. If the value if this object 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"
::= { sipProxyCfgEntry 2 } ::= { sipProxyCfgEntry 2 }
sipProxySendsCancel OBJECT-TYPE sipProxySendsCancel OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not a forking proxy 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
CANCELs on branches where no definitive response has been a CANCELs on branches where no definitive response has
received. If ĉfalseĈ, the proxy does not send CANCELs." been
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
sent. If the value is ĉfalseĈ, duplicate 1xx responses are responses
not sent upstream." are sent. If the value is 'false', duplicate 1xx
responses are not sent upstream."
::= { sipProxyCfgEntry 4 } ::= { sipProxyCfgEntry 4 }
sipProxyRecursion OBJECT-TYPE sipProxyRecursion OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Proxy 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
performed. If the value is ĉfalseĈ, no search is performed, search
the 3xx response is sent upstream towards the source of is performed. If the value is 'false', no search is
the request." performed, the 3xx response is sent upstream towards
the source
of 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
list of alternative URLs into a Contact header where the inserts a
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
is set to ĉtrueĈ." object
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
the signalling path for subsequent requests related to the in
the signaling 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
to the end of the Record-Route header, creating the header itself
if required. If the value is ĉfalseĈ, the proxy doesn't add to the end of the Record-Route header, creating the
header
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
first INVITE response that a stateful proxy retains state the
first INVITE response that a stateful proxy retains
state
in order to handle possible retransmissions of the in order to handle possible retransmissions of the
response." 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
skipping to change at page 73, line 12 skipping to change at page 76, line 39
bit 1 HTTP basic is used bit 1 HTTP basic is used
bit 2 HTTP digest is used bit 2 HTTP digest is used
bit 3 PGP (Pretty Good Privacy) is used." bit 3 PGP (Pretty Good Privacy) is used."
::= { sipProxyCfgEntry 9 } ::= { sipProxyCfgEntry 9 }
sipProxyAuthPgpAlgorithm OBJECT-TYPE sipProxyAuthPgpAlgorithm OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
md5(2), md5(2),
sha1(3) sha1(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the PGP algorithm the proxy uses." "This object specifies the PGP algorithm the proxy
uses."
::= { sipProxyCfgEntry 10 } ::= { sipProxyCfgEntry 10 }
sipProxyAuthRealm OBJECT-TYPE sipProxyAuthRealm OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the realm used in Proxy-Authenticate "This object specifies the realm used in Proxy-
headers. Note that this may need to be stored per user." Authenticate
headers. Note that this may need to be stored per
user."
::= { sipProxyCfgEntry 11 } ::= { sipProxyCfgEntry 11 }
sipProxyNonceLifeTime OBJECT-TYPE sipProxyNonceLifeTime OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the life-time of a given nonce. A "This object specifies the life-time of a given nonce.
A
nonce is a server specified value whose contents are nonce is a server specified value whose contents are
opaque to the entity being authenticated and which is used opaque to the entity being authenticated and which is
in calculating authentication data. If this object has a used
in calculating authentication data. If this object has
a
value of zero, then value of zero, then
nonces are not reused." nonces are not reused."
::= { sipProxyCfgEntry 12 } ::= { sipProxyCfgEntry 12 }
-- --
-- Proxy-Authenticate received by this server -- Proxy-Authenticate received by this server
-- (i.e. this server is being authenticated by a peer) -- (i.e. this server is being authenticated by a peer)
-- --
sipPgpPrivateKey OBJECT-TYPE sipPgpPrivateKey OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..255)) SYNTAX OCTET STRING(SIZE(0..255))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object is the server's private PGP key, "The value of this object is the server's private PGP
key,
used for both PGP authentication of this server and for used for both PGP authentication of this server and for
PGP-based PGP-based
encryption." encryption."
::= { sipProxyCfgEntry 13 } ::= { sipProxyCfgEntry 13 }
-- --
-- Proxy Server Statistics -- Proxy Server Statistics
-- --
sipProxyStatsTable OBJECT-TYPE sipProxyStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipProxyStatsEntry SYNTAX SEQUENCE OF SipProxyStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the statistics objects applicable "This table contains the statistics objects applicable
to all SIP Proxy Servers in this system." to all SIP Proxy Servers in this system."
skipping to change at page 74, line 51 skipping to change at page 78, line 31
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the number of occurrences of "This object contains the number of occurrences of
unsupported options being specified in received 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 75, line 54 skipping to change at page 79, line 34
sipRegMaxUsers Unsigned32, sipRegMaxUsers Unsigned32,
sipRegCurrentUsers Gauge32, sipRegCurrentUsers Gauge32,
sipRegDfltRegActiveInterval Unsigned32 sipRegDfltRegActiveInterval Unsigned32
} }
sipRegAllowThirdParty OBJECT-TYPE sipRegAllowThirdParty OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies whether or not the Registrar 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
header) is different from the entity being registered (in From
header) is different from the entity being registered
(in
the To header) to whom the provided Contact information the To header) to whom the 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
third party registrations. If the value is ĉfalseĈ, third allows
party registrations are rejected: a 403 Forbidden status third party registrations. If the value is 'false',
code is returned to the requestor." third
party registrations are rejected: a 403 Forbidden
status
code is returned to the requester."
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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum expiry that may be "This object specifies the maximum expiry that may be
requested by a User Agent for a particular Contact. User requested by a User Agent for a particular Contact.
Agents can specify expiry using either an Expiry header in User
Agents can specify expiry using either an Expiry header
in
a REGISTER request, or using an Expires parameter in a a REGISTER request, or using an Expires parameter in a
Contact header in a REGISTER request. If the value Contact header in a REGISTER request. If the value
requested by the User Agent is greater than the value of requested by the User Agent is greater than the value
of
this object, then the contact information is given the this object, then the contact information is given the
duration specified by this object, and that duration duration specified by this object, and that duration
is indicated to the User Agent in the response." is indicated to the User Agent in the response."
DEFVAL { 4294967295 } DEFVAL { 4294967295 }
::= { sipRegCfgEntry 2 } ::= { sipRegCfgEntry 2 }
sipRegMaxUsers OBJECT-TYPE sipRegMaxUsers OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the maximum number of users that the "This object specifies the maximum number of users that
the
registrar supports. The current number of users is registrar supports. The current number of users is
reflected by sipRegCurrentUsers." reflected by sipRegCurrentUsers."
::= { sipRegCfgEntry 3 } ::= { sipRegCfgEntry 3 }
sipRegCurrentUsers OBJECT-TYPE sipRegCurrentUsers OBJECT-TYPE
SYNTAX Gauge32 (0..4294967295) SYNTAX Gauge32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the number of users currently "This object specifies the number of users currently
skipping to change at page 77, line 8 skipping to change at page 81, line 4
"This object specifies the default time interval the "This object specifies the default time interval the
Registrar considers registrations to be active. The Registrar considers registrations to be active. The
value is used to compute the Expires header in the value is used to compute the Expires header in the
REGISTER response. If a user agent requests a time REGISTER response. If a user agent requests a time
interval shorter than specified by this object, the interval shorter than specified by this object, the
Registrar should honor that request. If a Contact Registrar should honor that request. If a Contact
entry does not have an 'expires' parameter, this entry does not have an 'expires' parameter, this
object is used as the default value." object is used as the default value."
REFERENCE "Expires header, section 6.20 RFC2543" REFERENCE "Expires header, section 6.20 RFC2543"
::= { sipRegCfgEntry 5 } ::= { sipRegCfgEntry 5 }
-- --
-- Per User Information -- Per User Information
-- --
sipRegUserTable OBJECT-TYPE sipRegUserTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegUserEntry SYNTAX SEQUENCE OF SipRegUserEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on all users registered to "This table contains information on all users registered
to
each Registrar in this system." each Registrar in this system."
::= { sipRegCfg 2 } ::= { sipRegCfg 2 }
sipRegUserEntry OBJECT-TYPE sipRegUserEntry OBJECT-TYPE
SYNTAX SipRegUserEntry SYNTAX SipRegUserEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single user "This entry contains information for a single user
registered to this Registrar. registered to this Registrar.
skipping to change at page 77, line 42 skipping to change at page 81, line 38
correlate them through the common framework of the correlate them through the common framework of the
NETWORK-SERVICES-MIB (RFC 2788). The same value of NETWORK-SERVICES-MIB (RFC 2788). The same value of
applIndex used in the corresponding SIP-COMMON-MIB applIndex used in the corresponding SIP-COMMON-MIB
is used here." is used here."
INDEX { applIndex, sipUserIndex } INDEX { applIndex, sipUserIndex }
::= { sipRegUserTable 1 } ::= { sipRegUserTable 1 }
SipRegUserEntry ::= SipRegUserEntry ::=
SEQUENCE { SEQUENCE {
sipUserIndex Unsigned32, sipUserIndex Unsigned32,
sipUserUri SnmpAdminString, sipUserUri
SnmpAdminString,
sipUserAuthenticationFailures Counter32, sipUserAuthenticationFailures Counter32,
sipUserTableRowStatus RowStatus sipUserTableRowStatus RowStatus
} }
sipUserIndex OBJECT-TYPE sipUserIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object uniquely identifies a conceptual row in the "This object uniquely identifies a conceptual row in the
table." table."
::= { sipRegUserEntry 1 } ::= { sipRegUserEntry 1 }
sipUserUri OBJECT-TYPE sipUserUri OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the user's address-of-record. It is "This object contains the user's address-of-record. It
the main form by which the registrar knows the user. The is
format is typically 'user@domain'. It is contained in the the main form by which the registrar knows the user.
The
format is typically 'user@domain'. It is contained in
the
To header for all REGISTER requests." To header for all REGISTER requests."
::= { sipRegUserEntry 2 } ::= { sipRegUserEntry 2 }
sipUserAuthenticationFailures OBJECT-TYPE sipUserAuthenticationFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of times the "This object contains a count of the number of times the
user has failed authentication." user has failed authentication."
skipping to change at page 78, line 36 skipping to change at page 82, line 40
::= { sipRegUserEntry 4 } ::= { sipRegUserEntry 4 }
-- --
-- Per Contact Information -- Per Contact Information
-- --
sipContactTable OBJECT-TYPE sipContactTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipContactEntry SYNTAX SEQUENCE OF SipContactEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on every location where a "This table contains information on every location where
registered user (specified by sipUserIndex) wishes to be a
found (i.e. the user has provided Contact information to registered user (specified by sipUserIndex) wishes to
be
found (i.e. the user has provided Contact information
to
each SIP Registrar in this system)." each SIP Registrar in this system)."
::= { sipRegCfg 3 } ::= { sipRegCfg 3 }
sipContactEntry OBJECT-TYPE sipContactEntry OBJECT-TYPE
SYNTAX SipContactEntry SYNTAX SipContactEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains information for a single 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.
skipping to change at page 79, line 42 skipping to change at page 83, line 51
corresponding to contact URLs of corresponding to contact URLs of
sip:BigGuy@sip.northpole.ca or sip:BigGuy@sip.northpole.ca or
sip:sclaus817@sip.mobile.com, respectively." sip:sclaus817@sip.mobile.com, respectively."
::= { sipContactEntry 2 } ::= { sipContactEntry 2 }
sipContactURI OBJECT-TYPE sipContactURI OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains either a SIP URL or a URI where the "This object contains either a SIP URL or a URI where
user can be contacted. This URI is normally returned to a the
user can be contacted. This URI is normally returned
to a
client from a redirect server, or is used as the client from a redirect server, or is used as the
RequestURI in a SIP request line for requests forwarded by RequestURI in a SIP request line for requests forwarded
by
a proxy." a proxy."
::= { sipContactEntry 3 } ::= { sipContactEntry 3 }
sipContactLastUpdated OBJECT-TYPE sipContactLastUpdated OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the time when this contact "This object indicates the time when this contact
information was accepted. If the contact information is information was accepted. If the contact information
updated via a subsequent REGISTER of the same information, is
updated via a subsequent REGISTER of the same
information,
this object is also updated." this object is also updated."
::= { sipContactEntry 4 } ::= { sipContactEntry 4 }
sipContactExpiry OBJECT-TYPE sipContactExpiry OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the date and time when the 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
expiry parameter in the Contact information), or a system or
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 SnmpAdminString 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
preferred by the user." preferred by the user."
REFERENCE REFERENCE
"RFC 2543, Section 6.13" "RFC 2543, Section 6.13"
::= { sipContactEntry 6 } ::= { sipContactEntry 6 }
sipContactAction OBJECT-TYPE sipContactAction OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
redirect(1), redirect(1),
proxy(2) proxy(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the user wanted the server "This object indicates whether the user wanted the
to act as a redirect server or as a proxy server. It is server
to act as a redirect server or as a proxy server. It
is
specified by the optional 'action' parameter in the specified by the optional 'action' parameter in the
Contact header." Contact header."
::= { sipContactEntry 7 } ::= { sipContactEntry 7 }
sipContactRetryAfter OBJECT-TYPE sipContactRetryAfter OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates that the contact information is "This object indicates that the contact information is
currently inactive, and that it should only be activated currently inactive, and that it should only be
activated
after the date and time specified by the object. This after the date and time specified by the object. This
value is provided by a user when deleting contact value is provided by a user when deleting contact
information using a REGISTER request containing a Retry- information using a REGISTER request containing a
Retry-
After header." After header."
REFERENCE REFERENCE
"RFC 2543, Section 6.32" "RFC 2543, Section 6.32"
::= { sipContactEntry 8 } ::= { sipContactEntry 8 }
-- --
-- Registrar Statistics -- Registrar Statistics
-- --
sipRegStatsTable OBJECT-TYPE sipRegStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegStatsEntry SYNTAX SEQUENCE OF SipRegStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the summary statistics objects "This table contains the summary statistics objects
applicable to all SIP Registrars in this system." applicable to all SIP Registrars in this system."
skipping to change at page 81, line 45 skipping to change at page 86, line 21
sipRegAcceptedRegistrations Counter32, sipRegAcceptedRegistrations Counter32,
sipRegRejectedRegistrations Counter32 sipRegRejectedRegistrations Counter32
} }
sipRegAcceptedRegistrations OBJECT-TYPE sipRegAcceptedRegistrations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a count of the number of REGISTER "This object contains a count of the number of REGISTER
requests that have been accepted (status code 200) by the requests that have been accepted (status code 200) by
the
Registrar. This includes additions of new contact Registrar. This includes additions of new contact
information, refreshing contact information, as well as information, refreshing contact information, as well as
requests for deletion of contact information." requests for deletion of contact information."
::= { sipRegStatsEntry 1 } ::= { sipRegStatsEntry 1 }
sipRegRejectedRegistrations OBJECT-TYPE sipRegRejectedRegistrations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 84, line 21 skipping to change at page 89, line 7
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-04
Started realignment with SIP RFC3261.
o Changes from draft-ietf-sip-mib-03 o Changes from draft-ietf-sip-mib-03
These are the specific draft-ietf-sip-mib-04 changes to the MIB 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. modules based on what they looked like for draft-ietf-sip-mib-03.
Front paper/Back paper Front paper/Back paper
o Rewrote parts of section 4.2 o Rewrote parts of section 4.2
o Fixed minor editorial nits o Fixed minor editorial nits
SIP-COMMON-MIB SIP-COMMON-MIB
o CONTACT-INFO "SIP MIB email" changed to sip@ietf.org o CONTACT-INFO "SIP MIB email" changed to sip@ietf.org
o sipInviteTimeout was removed from the MIB. See below regarding new o sipInviteTimeout was removed from the MIB. See below regarding
sipCommonCfgExpires objects. They provide equivalent functionality new sipCommonCfgExpires objects. They provide equivalent
with extensibility beyond INVITE. functionality with extensibility beyond INVITE.
o sipCommonCfgExpires OID subtree added. Per method Expires o sipCommonCfgExpires OID subtree added. Per method Expires
configuration objects were added there. configuration objects were added there.
This new high-level OID was placed under the existing This new high-level OID was placed under the existing
sipCommonCfgRetry OID and therefore, caused the OIDs for the sipCommonCfgRetry OID and therefore, caused the OIDs for the
subsequent groups to change (incrementing by one). subsequent groups to change (incrementing by one).
o Objects from tables under sipCommonCfgExpires were added to a new o Objects from tables under sipCommonCfgExpires were added to a new
OBJECT-GROUP sipCommonConfigExpiresGroup, and that group was listed OBJECT-GROUP sipCommonConfigExpiresGroup, and that group was listed
as optional in sipCommonCompliance. as optional in sipCommonCompliance.
skipping to change at page 85, line 28 skipping to change at page 90, line 15
o Clarifying changes to the DESCRIPTION of sipUriSupportedTable o Clarifying changes to the DESCRIPTION of sipUriSupportedTable
o Clarifying changes to the DESCRIPTIONs of sipFtrSupportedTable, o Clarifying changes to the DESCRIPTIONs of sipFtrSupportedTable,
sipFtrSupportedEntry, and sipFtrSupported. sipFtrSupportedEntry, and sipFtrSupported.
Specifically, IETF standard features and non-standard features are Specifically, IETF standard features and non-standard features are
now represented by this table. Only non-standard features were now represented by this table. Only non-standard features were
mentioned in prior revisions of the draft. mentioned in prior revisions of the draft.
o Reference to usage of RFC 2788 applIndex moved from o Reference to usage of RFC 2788 applIndex moved from
sipCommonCfgTimerExtMethodTable to sipCommonCfgTimerExtMethodEntry. sipCommonCfgTimerExtMethodTable to
sipCommonCfgTimerExtMethodEntry.
This was the convention for other table/entry definitions in This was the convention for other table/entry definitions in
the MIB, so these objects were previously unconventional. the MIB, so these objects were previously unconventional.
o DEFVAL removed from sipCfgTimerExtMethodTimer. The generic nature o DEFVAL removed from sipCfgTimerExtMethodTimer. The generic nature
of the "extension" object does not lend itself to being able to of the "extension" object does not lend itself to being able to
specify a particular default value. specify a particular default value.
o Since the removal of the DEFVAL clause from o Since the removal of the DEFVAL clause from
sipCfgTimerExtMethodTimer, sipCfgTimerExtMethodTimer,
a value for that object must be specified when creating a a value for that object must be specified when creating a
skipping to change at page 86, line 36 skipping to change at page 91, line 23
o sipStatusCodeNotifTo, sipStatusCodeNotifFrom, o sipStatusCodeNotifTo, sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId, sipStatusCodeNotifCallId,
and sipStatusCodeNotifCSeq all had clarifying changes to their and sipStatusCodeNotifCSeq all had clarifying changes to their
DESCRIPTIONs. Specifically, the header name will be part of the DESCRIPTIONs. Specifically, the header name will be part of the
object value and example values were given. object value and example values were given.
o Clarifying changes to the DESCRIPTION of sipCurrentTransTable o Clarifying changes to the DESCRIPTION of sipCurrentTransTable
and sipTransactionTable. Specifically, these tables are not and sipTransactionTable. Specifically, these tables are not
applicable to transaction stateless SIP proxy servers. applicable to transaction stateless SIP proxy servers.
o Minor gramatical change to the DESCRIPTION of sipCurrentTransEntry. o Minor gramatical change to the DESCRIPTION of
sipCurrentTransEntry.
o sipTransMethod and sipTransActivityInfo objects were added to o sipTransMethod and sipTransActivityInfo objects were added to
sipTransactionTable while sipTransCallingPartyContentType and sipTransactionTable while sipTransCallingPartyContentType and
sipTransCalledPartyContentType were removed. sipTransCalledPartyContentType were removed.
o Clarifying changes to the DESCRIPTION of sipTransState. o Clarifying changes to the DESCRIPTION of sipTransState.
Specifically, noting that not all values of the object Specifically, noting that not all values of the object
are applicable to all transaction types. are applicable to all transaction types.
o sipTransTo, sipTransFrom, sipTransCallId, and sipTransCSeq o sipTransTo, sipTransFrom, sipTransCallId, and sipTransCSeq
skipping to change at page 89, line 31 skipping to change at page 94, line 19
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), there is no control itself is secure (for example by using IPSec), there is no control
as to who on the secure network is allowed to access and GET/SET as to who on the secure network is allowed to access and 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 [RFC2574] and the View-
Access Control Model RFC 2575 [15] is recommended. based Access Control Model RFC 2575 [RFC2575] 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
skipping to change at page 90, line 9 skipping to change at page 94, line 52
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 (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are 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
skipping to change at page 91, line 5 skipping to change at page 96, line 5
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
10. References 10. Normative References
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2571, April 1999.
[2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990.
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.
[4] Rose, M., "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M. and S. Waldbusser, "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M. and S. Waldbusser, "Conformance Statements for SMIv2", STD
58, RFC 2580, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990.
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, [RFC2026] Bradner, S., "The Internet Standards Process - - Revision
"Introduction to Community-based SNMPv2", RFC 1901, January 3", BCP 9, RFC 2026, October 1996.
1996.
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
"Transport Mappings for Version 2 of the Simple Network Rose, M. and S. Waldbusser, "Structure of Management
Management Protocol (SNMPv2)", RFC 1906, January 1996. Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Processing and Dispatching for the Simple Network Management Rose, M. and S. Waldbusser, "Textual Conventions for
Protocol (SNMP)", RFC 2572, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
for version 3 of the Simple Network Management Protocol Rose, M. and S. Waldbusser, "Conformance Statements for
(SNMPv3)", RFC 2574, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, [1] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
"Protocol Operations for Version 2 of the Simple Network Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:
Management Protocol (SNMPv2)", RFC 1905, January 1996. Session Initiation Protocol", RFC 3261, June 2002.
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC [2] Freed, N. and S. Kille, "Network Services Monitor MIB",
2573, April 1999. RFC 2788, March 2000
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access [3] Donavan, S., "The SIP INFO Method", RFC 2976, October 2000
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999.
[16] Bradner, S., "Key words for use in RFCs to Indicate Requirement 11. Informative References
Levels", BCP 14, RFC 2119, March 1997.
[17] Handley, M., Schulzrinne, H., Schooler, E., and J. Rosenberg, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"SIP: Session Initiation Protocol", RFC 2543, March 1999. "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[18] Freed, N. and S. Kille, "Network Services Monitor MIB", RFC [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
2788, March 2000 Requirement Levels", BCP 14, RFC 2119, March 1997.
[19] Donavan, S., "The SIP INFO Method", RFC 2976, October 2000 12. Acknowledgments
[20] Case, J., Mundy, R., Partain, D. and B. Stewart, We wish to thank the members of the IETF SIP & SIPPING WGs & the SIP-
"Introduction to Version 3 of the Internet-standard Network MIB Design team for their comments and suggestions. Detailed comments
Management Framework", RFC 2570, April 1999. were provided by Tom Taylor and Kavitha Patchayappan.
11. Author's Addresses 13. Author's Addresses
Kevin Lingle Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Road 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 92, line 48 skipping to change at page 97, line 19
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Ĉ
CableLabs CableLabs
400 Centennial Parkway 400 Centennial Parkway
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jfm@cablelabs.com
phone: +1 303 661 3708 mibs@cablelabs.com
phone: +1 303 661 9100
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/