-- Network Working Group K. Lingle
-- Request for Comments: 4780 Cisco Systems, Inc.
-- Category: Standards Track J-F. Mule
-- CableLabs
-- J. Maeng
-- D. Walker
-- April 2007-- Management Information Base for
-- the Session Initiation Protocol (SIP)SIP-TC-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,mib-2
FROM SNMPv2-SMI -- RFC 2578TEXTUAL-CONVENTIONFROM SNMPv2-TC;-- RFC 2579sipTC MODULE-IDENTITYLAST-UPDATED"200704200000Z"ORGANIZATION"IETF Session Initiation Protocol Working Group"CONTACT-INFO"SIP WG email: sip@ietf.org
Co-editor Kevin Lingle
Cisco Systems, Inc.
postal: 7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709
USA
email: klingle@cisco.com
phone: +1 919 476 2029
Co-editor Joon Maeng
email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule
CableLabs
postal: 858 Coal Creek Circle
Louisville, CO 80027
USA
email: jf.mule@cablelabs.com
phone: +1 303 661 9100
Co-editor Dave Walker
email: drwalker@rogers.com"DESCRIPTION"Session Initiation Protocol (SIP) MIB TEXTUAL-CONVENTION
module used by other SIP-related MIB Modules.
Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC 4780; see the RFC itself for
full legal notices."REVISION"200704200000Z"DESCRIPTION"Initial version of the IETF SIP-TC-MIB module. This version
published as part of RFC 4780."::={ mib-2 148}--
-- Textual Conventions
--SipTCTransportProtocol ::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"This convention is a bit map. Each bit represents a transport
protocol. If a bit has value 1, then that selected transport
protocol is in some way dependent on the context of the object
using this convention. If a bit has value 0, then that
transport protocol is not selected. Combinations of bits can
be set when multiple transport protocols are selected.
bit 0: a protocol other than those defined here
bit 1: User Datagram Protocol
bit 2: Transmission Control Protocol
bit 3: Stream Control Transmission Protocol
bit 4: Transport Layer Security Protocol over TCP
bit 5: Transport Layer Security Protocol over SCTP
"REFERENCE"RFC 3261, Section 18 and RFC 4168"SYNTAXBITS{other(0),-- none of the followingudp(1),tcp(2),sctp(3),-- RFC4168tlsTcp(4),tlsSctp(5)-- RFC 4168}SipTCEntityRole ::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"This convention defines the role of a SIP entity. Examples of
SIP entities are proxies, user agents, redirect servers,
registrars, or combinations of the above.
User Agent (UA): A logical entity that can act as both a user
agent client and user agent server.
User Agent Client (UAC): A logical entity that creates a new
request, and then uses the client transaction state machinery
to send it. The role of UAC lasts only for the duration of
that transaction. In other words, if a piece of software
initiates a request, it acts as a UAC for the duration of that
transaction. If it receives a request later, it assumes the
role of a user agent server for the processing of that
transaction.
User Agent Server (UAS): A logical entity that generates a
response to a SIP request. The response accepts, rejects,
or redirects the request. This role lasts only for the
duration of that transaction. In other words, if a piece of
software responds to a request, it acts as a UAS for the
duration of that transaction. If it generates a request
later, it assumes the role of a user agent client for the
processing of that transaction.
Proxy, Proxy Server: An intermediary entity that acts as both
a server and a client for the purpose of making requests on
behalf of other clients. A proxy server primarily plays the
role of routing, which means its job is to ensure that a
request is sent to another entity 'closer' to the targeted
user. Proxies are also useful for enforcing policy. A proxy
interprets and, if necessary, rewrites specific parts of a
request message before forwarding it.
Redirect Server: A redirect server is a user agent server that
generates 3xx responses to requests it receives, directing the
client to contact an alternate set of URIs.
Registrar: A registrar is a server that accepts REGISTER
requests and places the information it receives in those
requests into the location service for the domain it handles."REFERENCE"RFC 3261, Section 6"SYNTAXBITS{other(0),userAgent(1),proxyServer(2),redirectServer(3),registrarServer(4)}SipTCOptionTagHeaders ::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION
"This convention defines the header fields that use the option
tags per Section 19.2 of RFC 3261. These tags are used in
Require (Section 20.32), Proxy-Require (Section 20.29),
Supported (Section 20.37), and Unsupported (Section 20.40)
header fields."REFERENCE"RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40"SYNTAXBITS{require(0),-- Require headerproxyRequire(1),-- Proxy-Require headersupported(2),-- Supported headerunsupported(3)-- Unsupported header}SipTCMethodName ::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"This TEXTUAL-CONVENTION is a string that uniquely identifies a
SIP method. The scope of uniqueness is the context of all
defined SIP methods.
Experimental support of extension methods is acceptable and
expected. Extension methods are those defined in
Internet-Draft documents but not yet allocated and
officially sanctioned by IANA.
To support experimental extension methods, any object using
this TEXTUAL-CONVENTION as syntax MAY return/accept a method
identifier value other than those sanctioned by IANA. That
system MUST ensure no collisions with officially assigned
method names."REFERENCE"RFC 3261, Section 27.4"SYNTAXOCTETSTRING(SIZE(1..100))ENDSIP-COMMON-MIB DEFINITIONS::=BEGIN
IMPORTSMODULE-IDENTITY,OBJECT-TYPE,NOTIFICATION-TYPE,Counter32,Gauge32,TimeTicks,Unsigned32,mib-2
FROM SNMPv2-SMI -- RFC 2578RowStatus,TimeStamp,TruthValueFROM SNMPv2-TC -- RFC 2579MODULE-COMPLIANCE,OBJECT-GROUP,NOTIFICATION-GROUPFROM SNMPv2-CONF -- RFC 2580SnmpAdminStringFROM SNMP-FRAMEWORK-MIB -- RFC 3411
SipTCTransportProtocol,
SipTCMethodName,
SipTCEntityRole,
SipTCOptionTagHeaders
FROM SIP-TC-MIB -- RFC 4780applIndex
FROM NETWORK-SERVICES-MIB -- RFC 2788InetPortNumberFROM INET-ADDRESS-MIB;-- RFC 4001sipCommonMIB MODULE-IDENTITYLAST-UPDATED"200704200000Z"ORGANIZATION"IETF Session Initiation Protocol Working Group"CONTACT-INFO"SIP WG email: sip@ietf.org
Co-editor Kevin Lingle
Cisco Systems, Inc.
postal: 7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709
USA
email: klingle@cisco.com
phone: +1 919 476 2029
Co-editor Joon Maeng
email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule
CableLabs
postal: 858 Coal Creek Circle
Louisville, CO 80027
USA
email: jf.mule@cablelabs.com
phone: +1 303 661 9100
Co-editor Dave Walker
email: drwalker@rogers.com"DESCRIPTION"Session Initiation Protocol (SIP) Common MIB module. This
module defines objects that may be common to all SIP entities.
SIP is an application-layer signaling protocol for creating,
modifying and terminating multimedia sessions with one or more
participants. These sessions include Internet multimedia
conferences and Internet telephone calls. SIP is defined in
RFC 3261 (June 2002).
This MIB is defined for managing objects that are common to
SIP User Agents (UAs), Proxy, Redirect, and Registrar servers.
Objects specific to each of these entities MAY be managed using
entity specific MIBs defined in other modules.
Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC 4780; see the RFC itself for
full legal notices."REVISION"200704200000Z"DESCRIPTION"Initial version of the IETF SIP-COMMON-MIB module. This
version published as part of RFC 4780."::={ mib-2 149}-- Top-Level Components of this MIB.sipCommonMIBNotifications OBJECTIDENTIFIER::={ sipCommonMIB 0}sipCommonMIBObjects OBJECTIDENTIFIER::={ sipCommonMIB 1}sipCommonMIBConformance OBJECTIDENTIFIER::={ sipCommonMIB 2}--
-- This MIB contains objects that are common to all SIP entities.
---- Common basic configurationsipCommonCfgBase OBJECTIDENTIFIER::={ sipCommonMIBObjects 1}
-- Protocol timer configurationsipCommonCfgTimer OBJECTIDENTIFIER::={ sipCommonMIBObjects 2}-- SIP message summary statisticssipCommonSummaryStats OBJECTIDENTIFIER::={ sipCommonMIBObjects 3}-- Per method statisticssipCommonMethodStats OBJECTIDENTIFIER::={ sipCommonMIBObjects 4}-- Per Status code or status code class statisticssipCommonStatusCode OBJECTIDENTIFIER::={ sipCommonMIBObjects 5}-- Transaction statisticssipCommonStatsTrans OBJECTIDENTIFIER::={ sipCommonMIBObjects 6}-- Method retry statisticssipCommonStatsRetry OBJECTIDENTIFIER::={ sipCommonMIBObjects 7}-- Other statisticssipCommonOtherStats OBJECTIDENTIFIER::={ sipCommonMIBObjects 8}-- Accessible-for-notify objectssipCommonNotifObjects OBJECTIDENTIFIER::={ sipCommonMIBObjects 9}--
-- Common Configuration Objects
--sipCommonCfgTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonCfgEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains the common configuration objects applicable
to all SIP entities."::={ sipCommonCfgBase 1}sipCommonCfgEntry OBJECT-TYPESYNTAX SipCommonCfgEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A row of common configuration.
Each row represents objects for a particular SIP entity
instance 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 }::={ sipCommonCfgTable 1}
SipCommonCfgEntry ::=SEQUENCE{
sipCommonCfgProtocolVersion SnmpAdminString,
sipCommonCfgServiceOperStatus INTEGER,
sipCommonCfgServiceStartTime TimeTicks,
sipCommonCfgServiceLastChange TimeTicks,
sipCommonCfgOrganization SnmpAdminString,
sipCommonCfgMaxTransactions Unsigned32,
sipCommonCfgServiceNotifEnable BITS,
sipCommonCfgEntityType SipTCEntityRole
}sipCommonCfgProtocolVersion OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object will reflect the version of SIP supported by this
SIP entity. It will follow the same format as SIP version
information contained in the SIP messages generated by this SIP
entity. For example, entities supporting SIP version 2 will
return 'SIP/2.0' as dictated by the standard."REFERENCE
"RFC 3261, Section 7.1"::={ sipCommonCfgEntry 1}sipCommonCfgServiceOperStatus OBJECT-TYPESYNTAXINTEGER{unknown(1),up(2),down(3),congested(4),restarting(5),quiescing(6),testing(7)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains the current operational state of
the SIP application.
unknown : The operational status cannot be determined
for some reason.
up : The application is operating normally and is
processing (receiving and possibly issuing) SIP
requests and responses.
down : The application is currently unable to process
SIP messages.
congested : The application is operational but no additional
inbound transactions can be accommodated at the
moment.
restarting : The application is currently unavailable, but it
is in the process of restarting and will
presumably, soon be able to process SIP messages.
quiescing : The application is currently operational
but has been administratively put into
quiescence mode. Additional inbound
transactions MAY be rejected.
testing : The application is currently in test mode
and MAY not be able to process SIP messages.
The operational status values defined for this object are not
based on any specific information contained in the SIP
standard."::={ sipCommonCfgEntry 2}sipCommonCfgServiceStartTime OBJECT-TYPESYNTAXTimeTicksMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of sysUpTime at the time the SIP entity was last
started. If started prior to the last re-initialization of the
local network management subsystem, then this object contains a
zero value."::={ sipCommonCfgEntry 3}sipCommonCfgServiceLastChange OBJECT-TYPESYNTAXTimeTicksMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of sysUpTime at the time the SIP entity entered its
current operational state. If the current state was entered
prior to the last re-initialization of the local network
management subsystem, then this object contains a zero value."::={ sipCommonCfgEntry 4}sipCommonCfgOrganization OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains the organization name that the SIP entity
inserts into Organization headers of SIP messages processed by
this system. If the string is empty, no Organization header is
to be generated."REFERENCE"RFC 3261, Section 20.25"::={ sipCommonCfgEntry 5}sipCommonCfgMaxTransactions OBJECT-TYPESYNTAXUnsigned32(1..4294967295)
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object indicates the maximum number of simultaneous
transactions per second that the SIP entity can manage. In
general, the value of this object SHOULD reflect a level of
transaction processing per second that is considered high
enough to impact the system's CPU and/or memory resources to
the point of deteriorating SIP call processing but not high
enough to cause catastrophic system failure."::={ sipCommonCfgEntry 6}sipCommonCfgServiceNotifEnable OBJECT-TYPESYNTAXBITS{sipCommonServiceColdStart(0),sipCommonServiceWarmStart(1),sipCommonServiceStatusChanged(2)}MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object specifies which SIP service related notifications
are enabled. Each bit represents a specific notification. If
a bit has a value 1, the associated notification is enabled and
will be generated by the SIP entity at the appropriate time.
Support for these notifications is OPTIONAL: either none or all
notification values are supported. If an implementation does
not support this object, it should return a 'noSuchObject'
exception to an SNMP GET operation. If notifications are
supported, this object's default value SHOULD reflect
sipCommonServiceColdStart and sipCommonServiceWarmStart enabled
and sipCommonServiceStatusChanged disabled.
This object value SHOULD persist across reboots."DEFVAL{{ sipCommonServiceColdStart,
sipCommonServiceWarmStart }}
::={ sipCommonCfgEntry 7}sipCommonCfgEntityType OBJECT-TYPESYNTAX SipTCEntityRole
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object identifies the list of SIP entities to which this
row is related. It is defined as a bit map. Each bit
represents a type of SIP entity. If a bit has value 1, the
SIP entity represented by this row plays the role of this
entity type. If a bit has value 0, the SIP entity represented
by this row does not act as this entity type. Combinations
of bits can be set when the SIP entity plays multiple SIP
roles."::={ sipCommonCfgEntry 8}--
-- Support for multiple ports
--sipCommonPortTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonPortEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains the list of ports that each SIP entity in
this system is allowed to use. These ports can be advertised
using the Contact header in a REGISTER request or response."::={ sipCommonCfgBase 2}sipCommonPortEntry OBJECT-TYPESYNTAX SipCommonPortEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Specification of a particular port.
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, sipCommonPort }::={ sipCommonPortTable 1}
SipCommonPortEntry ::=SEQUENCE{
sipCommonPort InetPortNumber,
sipCommonPortTransportRcv SipTCTransportProtocol
}sipCommonPort OBJECT-TYPESYNTAXInetPortNumber(1..65535)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This object reflects a particular port that can be used by the
SIP application."::={ sipCommonPortEntry 1}sipCommonPortTransportRcv OBJECT-TYPESYNTAX SipTCTransportProtocol
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object will specify the transport protocol the SIP entity
will use to receive SIP messages.
This object is a bit map. Each bit represents a transport
protocol. If a bit has value 1, then that transport protocol
is currently being used. If a bit has value 0, then that
transport protocol is currently not being used."::={ sipCommonPortEntry 2}--
-- Support for SIP option tags (SIP extensions).
-- SIP extensions MAY be supported or required by SIP entities.
--sipCommonOptionTagTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonOptionTagEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains a list of the SIP option tags (SIP
extensions) that are either required, supported, or
unsupported by the SIP entity. These option tags are
used in the Require, Proxy-Require, Supported, and
Unsupported header fields.
Example: If a user agent client supports, and requires the
server to support, reliability of provisional responses
(RFC 3262), this table contains a row with the option tag string
'100rel' in sipCommonOptionTag and the OCTET STRING value of
'1010 0000' or '0xA0' in sipCommonOptionTagHeaderField.
If a server does not support the required feature (indicated in
a Require header to a UAS, or in a Proxy-Require to a Proxy
Server), the server returns a 420 Bad Extension listing the
feature in an Unsupported header.
Normally, the list of such features supported by an entity is
static (i.e., will not change over time)."REFERENCE"RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40"::={ sipCommonCfgBase 3}sipCommonOptionTagEntry OBJECT-TYPESYNTAX SipCommonOptionTagEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A particular SIP option tag (extension) supported or
unsupported by the SIP entity, and which may be supported or
required by a peer.
Each row represents those objects for a particular SIP entity
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, sipCommonOptionTagIndex }::={ sipCommonOptionTagTable 1}
SipCommonOptionTagEntry ::=SEQUENCE{
sipCommonOptionTagIndex Unsigned32,
sipCommonOptionTag SnmpAdminString,
sipCommonOptionTagHeaderField SipTCOptionTagHeaders
}sipCommonOptionTagIndex OBJECT-TYPESYNTAXUnsigned32(1..4294967295)
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This object uniquely identifies a conceptual row in the table."::={ sipCommonOptionTagEntry 1}sipCommonOptionTag OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object indicates the SIP option tag. The option tag names
are registered with IANA and available at http://www.iana.org."REFERENCE"RFC 3261, Section 27.1"::={ sipCommonOptionTagEntry 2}sipCommonOptionTagHeaderField OBJECT-TYPESYNTAX SipTCOptionTagHeaders
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object indicates whether the SIP option tag is supported
(Supported header), unsupported (Unsupported header), or
required (Require or Proxy-Require header) by the SIP entity.
A SIP option tag may be both supported and required."::={ sipCommonOptionTagEntry 3}--
-- Supported SIP Methods
--sipCommonMethodSupportedTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonMethodSupportedEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains a list of methods supported by each SIP
entity in this system (see the standard set of SIP methods in
Section 7.1 of RFC 3261). Any additional methods that may be
incorporated into the SIP protocol can be represented by this
table without any requirement to update this MIB module.
The table is informational in nature and conveys capabilities
of the managed system to the SNMP Manager.
From a protocol point of view, the list of methods advertised
by the SIP entity in the Allow header (Section 20.5 of RFC
3261) MUST be consistent with the methods reflected in this
table."::={ sipCommonCfgBase 4}sipCommonMethodSupportedEntry OBJECT-TYPESYNTAX SipCommonMethodSupportedEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A particular 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, sipCommonMethodSupportedIndex }::={ sipCommonMethodSupportedTable 1}
SipCommonMethodSupportedEntry ::=SEQUENCE{
sipCommonMethodSupportedIndex Unsigned32,
sipCommonMethodSupportedName SipTCMethodName
}sipCommonMethodSupportedIndex OBJECT-TYPESYNTAXUnsigned32(1..4294967295)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This object uniquely identifies a conceptual row in the table
and reflects an assigned number used to identify a specific
SIP method.
This identifier is suitable for referencing the associated
method throughout this and other MIBs supported by this managed
system."::={ sipCommonMethodSupportedEntry 1}
sipCommonMethodSupportedName OBJECT-TYPESYNTAX SipTCMethodName
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the supported method's name. The method
name MUST be all upper case (e.g., 'INVITE')."::={ sipCommonMethodSupportedEntry 2}--
-- SIP Timer Configuration
--sipCommonCfgTimerTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonCfgTimerEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains timer configuration objects applicable to
SIP user agent and SIP stateful Proxy Server entities."::={ sipCommonCfgTimer 1}sipCommonCfgTimerEntry OBJECT-TYPESYNTAX SipCommonCfgTimerEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A row of timer configuration.
Each row represents those objects for a particular SIP entity
present in this system. applIndex is used to uniquely identify
these instances of SIP entities and correlate them through
the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
The objects in this table entry SHOULD be non-volatile and
their value SHOULD be kept at reboot."INDEX{ applIndex }::={ sipCommonCfgTimerTable 1}
SipCommonCfgTimerEntry ::=SEQUENCE{
sipCommonCfgTimerA Unsigned32,
sipCommonCfgTimerB Unsigned32,
sipCommonCfgTimerC Unsigned32,
sipCommonCfgTimerD Unsigned32,
sipCommonCfgTimerE Unsigned32,
sipCommonCfgTimerF Unsigned32,
sipCommonCfgTimerG Unsigned32,
sipCommonCfgTimerH Unsigned32,
sipCommonCfgTimerI Unsigned32,
sipCommonCfgTimerJ Unsigned32,
sipCommonCfgTimerK Unsigned32,
sipCommonCfgTimerT1 Unsigned32,
sipCommonCfgTimerT2 Unsigned32,
sipCommonCfgTimerT4 Unsigned32}sipCommonCfgTimerA OBJECT-TYPESYNTAXUnsigned32(100..1000)UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the initial value for the retransmit timer
for the INVITE method. The retransmit timer doubles after each
retransmission, ensuring an exponential backoff in network
traffic. This object represents the initial time a SIP entity
will wait to receive a provisional response to an INVITE before
resending the INVITE request."REFERENCE"RFC 3261, Section 17.1.1.2"DEFVAL{500}::={ sipCommonCfgTimerEntry 1}sipCommonCfgTimerB OBJECT-TYPESYNTAXUnsigned32(32000..300000)
UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the maximum time a SIP entity will wait to
receive a final response to an INVITE. The timer is started
upon transmission of the initial INVITE request."REFERENCE"RFC 3261, Section 17.1.1.2"DEFVAL{32000}
::={ sipCommonCfgTimerEntry 2}sipCommonCfgTimerC OBJECT-TYPESYNTAXUnsigned32(180000..300000)UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the maximum time a SIP Proxy Server will
wait to receive a provisional response to an INVITE. The Timer
C MUST be set for each client transaction when an INVITE
request is proxied."REFERENCE"RFC 3261, Section 16.6"DEFVAL{180000}::={ sipCommonCfgTimerEntry 3}sipCommonCfgTimerD OBJECT-TYPESYNTAXUnsigned32(0..300000)UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the amount of time that the server
transaction can remain in the 'Completed' state when unreliable
transports are used. The default value MUST be equal to or
greater than 32000 for UDP transport, and its value MUST be 0
for TCP/SCTP transport."REFERENCE"RFC 3261, Section 17.1.1.2"DEFVAL{32000}::={ sipCommonCfgTimerEntry 4}sipCommonCfgTimerE OBJECT-TYPESYNTAXUnsigned32(100..1000)UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the initial value for the retransmit timer
for a non-INVITE method while in 'Trying' state. The
retransmit timer doubles after each retransmission until it
reaches T2 to ensure an exponential backoff in network traffic.
This object represents the initial time a SIP entity will wait
to receive a provisional response to the request before
resending the non-INVITE request."REFERENCE"RFC 3261, Section 17.1.2.2"DEFVAL{500}::={ sipCommonCfgTimerEntry 5}sipCommonCfgTimerF OBJECT-TYPESYNTAXUnsigned32(32000..300000)UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the maximum time a SIP entity will wait to
receive a final response to a non-INVITE request. The timer is
started upon transmission of the initial request."REFERENCE"RFC 3261, Section 17.1.2.2"DEFVAL{32000}
::={ sipCommonCfgTimerEntry 6}sipCommonCfgTimerG OBJECT-TYPESYNTAXUnsigned32(0..1000)UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the initial value for the retransmit timer
for final responses to INVITE requests. If timer G fires, the
response is passed to the transport layer again for
retransmission, and timer G is set to fire in MIN(2*T1, T2)
seconds. From then on, when timer G fires, the response is
passed to the transport again for transmission, and timer G is
reset with a value that doubles, unless that value exceeds T2,
in which case, it is reset with the value of T2. The default
value MUST be T1 for UDP transport, and its value MUST be 0 for
reliable transport like TCP/SCTP."REFERENCE"RFC 3261, Section 17.2.1"DEFVAL{500}::={ sipCommonCfgTimerEntry 7}sipCommonCfgTimerH OBJECT-TYPESYNTAXUnsigned32(32000..300000)UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects 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}sipCommonCfgTimerI OBJECT-TYPESYNTAXUnsigned32(0..10000)UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the maximum time a SIP entity will wait to
receive additional ACK message retransmissions.
The timer is started upon entering the 'Confirmed' state. The
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}sipCommonCfgTimerJ OBJECT-TYPESYNTAXUnsigned32(32000..300000)UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the maximum time a SIP server will wait to
receive retransmissions of non-INVITE requests. 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}sipCommonCfgTimerK OBJECT-TYPESYNTAXUnsigned32(0..10000)
UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the maximum time a SIP client will wait to
receive retransmissions of responses to non-INVITE requests.
The timer is started upon entering the 'Completed' state for
non-INVITE transactions. When timer K fires, the server MUST
transition to the 'Terminated' state. The default value MUST
be T4 for UDP transport, and its value MUST be 0 for reliable
transport like TCP/SCTP."REFERENCE"RFC 3261, Section 17.1.2.2"DEFVAL{5000}::={ sipCommonCfgTimerEntry 11}sipCommonCfgTimerT1 OBJECT-TYPESYNTAXUnsigned32(200..10000)UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects 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}sipCommonCfgTimerT2 OBJECT-TYPESYNTAXUnsigned32(200..10000)UNITS"milliseconds"MAX-ACCESSread-only
STATUScurrentDESCRIPTION"This object reflects the T2 timer for a SIP entity. T2 is the
maximum retransmit interval for non-INVITE requests and INVITE
responses. It's used in various parts of the protocol to reset
other Timer* objects to this value."REFERENCE"RFC 3261, Section 17"DEFVAL{4000}::={ sipCommonCfgTimerEntry 13}sipCommonCfgTimerT4 OBJECT-TYPESYNTAXUnsigned32(200..10000)UNITS"milliseconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the T4 timer for a SIP entity. T4 is the
maximum duration a message will remain in the network. It
represents the amount of time the network will take to clear
messages between client and server transactions. It's used in
various parts of the protocol to reset other Timer* objects to
this value."REFERENCE"RFC 3261, Section 17"DEFVAL{5000}::={ sipCommonCfgTimerEntry 14}--
-- Common Statistics Objects
----
-- Summary Statistics
--sipCommonSummaryStatsTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonSummaryStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains the summary statistics objects applicable
to all SIP entities. Each row represents those objects for a
particular SIP entity present in this system."
::={ sipCommonSummaryStats 1}sipCommonSummaryStatsEntry OBJECT-TYPESYNTAX SipCommonSummaryStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A row of summary statistics.
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 }::={ sipCommonSummaryStatsTable 1}
SipCommonSummaryStatsEntry ::=SEQUENCE{
sipCommonSummaryInRequests Counter32,
sipCommonSummaryOutRequests Counter32,
sipCommonSummaryInResponses Counter32,
sipCommonSummaryOutResponses Counter32,
sipCommonSummaryTotalTransactions Counter32,
sipCommonSummaryDisconTime TimeStamp}sipCommonSummaryInRequests OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object indicates the total number of SIP request messages
received by the SIP entity, including retransmissions.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same
row."::={ sipCommonSummaryStatsEntry 1}sipCommonSummaryOutRequests OBJECT-TYPE
SYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains the total number of SIP request messages
sent out (originated and relayed) by the SIP entity. Where a
particular message is sent more than once, for example as a
retransmission or as a result of forking, each transmission is
counted separately.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same
row."::={ sipCommonSummaryStatsEntry 2}sipCommonSummaryInResponses OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains the total number of SIP response messages
received by the SIP entity, including retransmissions.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same
row."::={ sipCommonSummaryStatsEntry 3}sipCommonSummaryOutResponses OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains the total number of SIP response messages
sent (originated and relayed) by the SIP entity including
retransmissions.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same
row."::={ sipCommonSummaryStatsEntry 4}sipCommonSummaryTotalTransactions OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains a count of the number of transactions that
are in progress and transactions that have reached the
'Terminated' state. It is not applicable to stateless SIP Proxy
Servers.
A SIP transaction occurs between a client and a server, and
comprises all messages from the first request sent from the
client to the server, up to a final (non-1xx) response sent
from the server to the client.
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 within
a single call leg. The ACK request has the same CSeq number as
the corresponding INVITE request, but comprises a transaction
of its own.
In the case of a forked request, each branch counts as a single
transaction.
For a transaction stateless Proxy Server, this counter is
always 0.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonSummaryDisconTime object in the same
row."::={ sipCommonSummaryStatsEntry 5}sipCommonSummaryDisconTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of the sysUpTime object when the counters for the
summary statistics objects in this row last experienced a
discontinuity."
::={ sipCommonSummaryStatsEntry 6}--
-- SIP Method Statistics
-- Total counts for each SIP method.
--sipCommonMethodStatsTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonMethodStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains the method statistics objects for SIP
entities. Each row represents those objects for a particular
SIP entity present in this system."::={ sipCommonMethodStats 1}sipCommonMethodStatsEntry OBJECT-TYPESYNTAX SipCommonMethodStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A row of per entity method statistics.
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, sipCommonMethodStatsName }::={ sipCommonMethodStatsTable 1}
SipCommonMethodStatsEntry ::=SEQUENCE{
sipCommonMethodStatsName SipTCMethodName,
sipCommonMethodStatsOutbounds Counter32,
sipCommonMethodStatsInbounds Counter32,
sipCommonMethodStatsDisconTime TimeStamp}sipCommonMethodStatsName OBJECT-TYPESYNTAX SipTCMethodName
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION
"This object uniquely identifies the SIP method related to the
objects in a particular row."::={ sipCommonMethodStatsEntry 1}sipCommonMethodStatsOutbounds OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the total number of requests sent by the
SIP entity, excluding retransmissions. Retransmissions are
counted separately and are not reflected in this counter. A
Management Station can detect discontinuities in this counter
by monitoring the sipCommonMethodStatsDisconTime object in the
same row."REFERENCE"RFC 3261, Section 7.1"::={ sipCommonMethodStatsEntry 2}sipCommonMethodStatsInbounds OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the total number of requests received by
the SIP entity. Retransmissions are counted separately and are
not reflected in this counter. A Management Station can detect
discontinuities in this counter by monitoring the
sipCommonMethodStatsDisconTime object in the same row."REFERENCE"RFC 3261, Section 7.1"::={ sipCommonMethodStatsEntry 3}sipCommonMethodStatsDisconTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of the sysUpTime object when the counters for the
method statistics objects in this row last experienced a
discontinuity."::={ sipCommonMethodStatsEntry 4}
--
-- Support for specific status codes
--sipCommonStatusCodeTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonStatusCodeEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains the list of SIP status codes that each SIP
entity in this system has been requested to monitor. It is the
mechanism by which specific status codes are monitored.
Entries created in this table must not persist across reboots."::={ sipCommonStatusCode 1}sipCommonStatusCodeEntry OBJECT-TYPESYNTAX SipCommonStatusCodeEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This row contains information on a particular SIP status code
that the SIP entity has been requested to monitor. Entries
created in this table must not persist across reboots.
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, sipCommonStatusCodeMethod,
sipCommonStatusCodeValue }::={ sipCommonStatusCodeTable 1}
SipCommonStatusCodeEntry ::=SEQUENCE{
sipCommonStatusCodeMethod SipTCMethodName,
sipCommonStatusCodeValue Unsigned32,
sipCommonStatusCodeIns Counter32,
sipCommonStatusCodeOuts Counter32,
sipCommonStatusCodeRowStatus RowStatus,
sipCommonStatusCodeDisconTime TimeStamp}sipCommonStatusCodeMethod OBJECT-TYPESYNTAX SipTCMethodName
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This object uniquely identifies a conceptual row in the
table."::={ sipCommonStatusCodeEntry 1}sipCommonStatusCodeValue OBJECT-TYPESYNTAXUnsigned32(100..999)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This object contains a SIP status code value that the SIP
entity has been requested to monitor. All of the other
information in the row is related to this value."::={ sipCommonStatusCodeEntry 2}sipCommonStatusCodeIns OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the total number of response messages
received by the SIP entity with the status code value contained
in the sipCommonStatusCodeValue column.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service, or when the
monitoring of the status code is temporarily disabled. A
Management Station can detect discontinuities in this counter
by monitoring the sipCommonStatusCodeDisconTime object in the
same row."::={ sipCommonStatusCodeEntry 3}sipCommonStatusCodeOuts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-only
STATUScurrentDESCRIPTION"This object reflects the total number of response messages sent
by the SIP entity with the status code value contained in the
sipCommonStatusCodeValue column.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service, or when the
monitoring of the Status code is temporarily disabled. A
Management Station can detect discontinuities in this counter
by monitoring the sipCommonStatusCodeDisconTime object in the
same row."::={ sipCommonStatusCodeEntry 4}sipCommonStatusCodeRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The row augmentation in sipCommonStatusCodeNotifTable will be
governed by the value of this RowStatus.
The values 'createAndGo' and 'destroy' are the only valid
values allowed for this object. If a row exists, it will
reflect a status of 'active' when queried."::={ sipCommonStatusCodeEntry 5}sipCommonStatusCodeDisconTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of the sysUpTime object when the counters for the
status code statistics objects in this row last experienced
a discontinuity."::={ sipCommonStatusCodeEntry 6}--
-- Support for specific status code notifications
--sipCommonStatusCodeNotifTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonStatusCodeNotifEntry
MAX-ACCESSnot-accessibleSTATUScurrent
DESCRIPTION"This table contains objects to control notifications related to
particular status codes that each SIP entity in this system has
been requested to monitor.
There is an entry in this table corresponding to each entry in
sipCommonStatusCodeTable. Therefore, this table augments
sipCommonStatusCodeTable and utilizes the same index
methodology.
The objects in this table are not included directly in the
sipCommonStatusCodeTable simply to keep the status code
notification control objects separate from the actual status
code statistics."::={ sipCommonStatusCode 2}sipCommonStatusCodeNotifEntry OBJECT-TYPESYNTAX SipCommonStatusCodeNotifEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This row contains information controlling notifications for a
particular SIP status code that the SIP entity has been
requested to monitor."AUGMENTS{ sipCommonStatusCodeEntry }::={ sipCommonStatusCodeNotifTable 1}
SipCommonStatusCodeNotifEntry ::=SEQUENCE{
sipCommonStatusCodeNotifSend TruthValue,
sipCommonStatusCodeNotifEmitMode INTEGER,
sipCommonStatusCodeNotifThresh Unsigned32,
sipCommonStatusCodeNotifInterval Unsigned32}sipCommonStatusCodeNotifSend OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object controls whether a sipCommonStatusCodeNotif is
emitted when the status code value specified by
sipCommonStatusCodeValue is sent or received. If the value of
this object is 'true', then a notification is sent. If it is
'false', no notification is sent.
Note well that a notification MAY be emitted for every message
sent or received that contains the particular status code.
Depending on the status code involved, this can cause a
significant number of notification emissions that could be
detrimental to network performance. Managers are forewarned to
be prudent in the use of this object to enable notifications.
Look to sipCommonStatusCodeNotifEmitMode for alternative
controls for sipCommonStatusCodeNotif emissions."DEFVAL{ false }::={ sipCommonStatusCodeNotifEntry 1}sipCommonStatusCodeNotifEmitMode OBJECT-TYPESYNTAXINTEGER{normal(1),oneShot(2),triggered(3)-- read-only}MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The object sipCommonStatusCodeNotifSend MUST be set to 'true'
for the values of this object to have any effect. It is
RECOMMENDED that the desired emit mode be established by this
object prior to setting sipCommonStatusCodeNotifSend to 'true'.
This object and the sipCommonStatusCodeNotifSend object can
obviously be set independently, but their respective values
will have a dependency on each other and the resulting
notifications.
This object specifies the mode for emissions of
sipCommonStatusCodeNotif notifications.
normal : sipCommonStatusCodeNotif notifications will be
emitted by the system for each SIP response
message sent or received that contains the
desired status code.
oneShot : Only one sipCommonStatusCodeNotif notification
will be emitted. It will be the next SIP response
message sent or received that contains the
desired status code.
No more notifications are emitted until this
object is set to 'oneShot' again or set to
'normal'. This option is provided as a means of
quelling the potential promiscuous behavior that
can be associated with the
sipCommonStatusCodeNotif.
triggered : This value is only readable and cannot be set. It
reflects that the 'oneShot' case has occurred,
and indicates that the mode needs to be reset to
get further notifications. The mode is reset by
setting this object to 'oneShot' or 'normal'."DEFVAL{ oneShot }::={ sipCommonStatusCodeNotifEntry 2}sipCommonStatusCodeNotifThresh OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object specifies the number of response messages sent or
received by this system that are considered excessive. Based
on crossing that threshold, a
sipCommonStatusCodeThreshExceededInNotif notification or a
sipCommonStatusCodeThreshExceededOutNotif will be sent. The
sipCommonStatusCodeThreshExceededInNotif and
sipCommonStatusCodeThreshExceededOutNotif notifications can be
used as an early warning mechanism in lieu of using
sipCommonStatusCodeNotif.
Note that the configuration applied by this object will be
applied equally to inbound and outbound response messages."DEFVAL{500}::={ sipCommonStatusCodeNotifEntry 3}sipCommonStatusCodeNotifInterval OBJECT-TYPESYNTAXUnsigned32UNITS"seconds"MAX-ACCESSread-writeSTATUScurrentDESCRIPTION
"This object specifies the time interval over which, if
sipCommonStatusCodeThresh is exceeded with respect to sent or
received messages, a sipCommonStatusCodeThreshExceededInNotif
or sipCommonStatusCodeThreshExceededOutNotif notification will
be sent.
Note that the configuration applied by this object will be
applied equally to inbound and outbound response messages."DEFVAL{60}::={ sipCommonStatusCodeNotifEntry 4}--
-- Transaction Statistics
--sipCommonTransCurrentTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonTransCurrentEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains information on the transactions currently
awaiting definitive responses by each SIP entity in this
system.
This table does not apply to transaction stateless Proxy
Servers."::={ sipCommonStatsTrans 1}sipCommonTransCurrentEntry OBJECT-TYPESYNTAX SipCommonTransCurrentEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Information on a particular SIP entity's current transactions.
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 }::={ sipCommonTransCurrentTable 1}
SipCommonTransCurrentEntry ::=SEQUENCE{
sipCommonTransCurrentactions Gauge32}sipCommonTransCurrentactions OBJECT-TYPESYNTAXGauge32(0..4294967295)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains the number of transactions awaiting
definitive (non-1xx) response. In the case of a forked
request, each branch counts as a single transaction
corresponding to the entity identified by applIndex."::={ sipCommonTransCurrentEntry 1}--
-- SIP Retry Statistics
--
-- This group contains various statistics objects about
-- retransmission counts.
--sipCommonStatsRetryTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonStatsRetryEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains retry statistics objects applicable to each
SIP entity in this system."::={ sipCommonStatsRetry 1}sipCommonStatsRetryEntry OBJECT-TYPESYNTAX SipCommonStatsRetryEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A row of retry statistics.
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, sipCommonStatsRetryMethod }::={ sipCommonStatsRetryTable 1}
SipCommonStatsRetryEntry ::=SEQUENCE{
sipCommonStatsRetryMethod SipTCMethodName,
sipCommonStatsRetries Counter32,
sipCommonStatsRetryFinalResponses Counter32,
sipCommonStatsRetryNonFinalResponses Counter32,
sipCommonStatsRetryDisconTime TimeStamp}sipCommonStatsRetryMethod OBJECT-TYPESYNTAX SipTCMethodName
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This object uniquely identifies the SIP method related to the
objects in a row."::={ sipCommonStatsRetryEntry 1}sipCommonStatsRetries OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the total number of request
retransmissions that have been sent by the SIP entity. Note
that there could be multiple retransmissions per request.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonStatsRetryDisconTime object in the same
row."::={ sipCommonStatsRetryEntry 2}sipCommonStatsRetryFinalResponses OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the total number of Final Response retries
that have been sent by the SIP entity. Note that there could
be multiple retransmissions per request.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonStatsRetryDisconTime object in the same
row."::={ sipCommonStatsRetryEntry 3}sipCommonStatsRetryNonFinalResponses OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the total number of non-Final Response
retries that have been sent by the SIP entity.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonStatsRetryDisconTime object in the same
row."::={ sipCommonStatsRetryEntry 4}sipCommonStatsRetryDisconTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of the sysUpTime object when the counters for the
retry statistics objects in this row last experienced a
discontinuity."::={ sipCommonStatsRetryEntry 5}--
-- Other Common Statistics
--sipCommonOtherStatsTable OBJECT-TYPESYNTAXSEQUENCEOF SipCommonOtherStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains other common statistics supported by each
SIP entity in this system."::={ sipCommonOtherStats 1}sipCommonOtherStatsEntry OBJECT-TYPESYNTAX SipCommonOtherStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Information on a particular SIP entity's other common
statistics.
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 }::={ sipCommonOtherStatsTable 1}
SipCommonOtherStatsEntry ::=SEQUENCE{
sipCommonOtherStatsNumUnsupportedUris Counter32,
sipCommonOtherStatsNumUnsupportedMethods Counter32,
sipCommonOtherStatsOtherwiseDiscardedMsgs Counter32,
sipCommonOtherStatsDisconTime TimeStamp}sipCommonOtherStatsNumUnsupportedUris OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Number of RequestURIs received with an unsupported scheme.
A server normally responds to such requests with a 400 Bad
Request status code.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonOtherStatsDisconTime object in the same
row."::={ sipCommonOtherStatsEntry 1}sipCommonOtherStatsNumUnsupportedMethods OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Number of SIP requests received with unsupported methods. A
server normally responds to such requests with a 501 (Not
Implemented) or 405 (Method Not Allowed).
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonOtherStatsDisconTime object in the same
row."::={ sipCommonOtherStatsEntry 2}sipCommonOtherStatsOtherwiseDiscardedMsgs OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Number of SIP messages received that, for any number of
reasons, was discarded without a response.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipCommonOtherStatsDisconTime object in the same
row."::={ sipCommonOtherStatsEntry 3}sipCommonOtherStatsDisconTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of the sysUpTime object when the counters for the
statistics objects in this row last experienced a
discontinuity."::={ sipCommonOtherStatsEntry 4}--
-- Notification related objects
----
-- Status code related notification objects.
--sipCommonStatusCodeNotifTo OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"This object contains the value of the To header in the message
containing the status code that caused the notification. The
header name will be part of this object value. For example,
'To: Watson '."::={ sipCommonNotifObjects 1}sipCommonStatusCodeNotifFrom OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"This object contains the value of the From header in the
message containing the status code that caused the
notification. The header name will be part of this object
value. For example, 'From: Watson '."::={ sipCommonNotifObjects 2}sipCommonStatusCodeNotifCallId OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"This object contains the value of the Call-ID in the message
containing the status code that caused the notification. The
header name will be part of this object value. For example,
'Call-ID: 5551212@example.com'."::={ sipCommonNotifObjects 3}sipCommonStatusCodeNotifCSeq OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"This object contains the CSeq value in the message containing
the status code that caused the notification. The header name
will be part of this object value. For example, 'CSeq: 1722
INVITE'."::={ sipCommonNotifObjects 4}--
-- General notification related objects.
--sipCommonNotifApplIndex OBJECT-TYPE
SYNTAXUnsigned32(1..2147483647)MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"This object contains the applIndex as described in RFC 2788.
This object is created in order to allow a variable binding
containing a value of applIndex in a notification."::={ sipCommonNotifObjects 5}sipCommonNotifSequenceNumber OBJECT-TYPESYNTAXUnsigned32(1..2147483647)MAX-ACCESSaccessible-for-notifySTATUScurrentDESCRIPTION"This object contains a sequence number for each notification
generated by this SIP entity. Each notification SHOULD have a
unique sequence number. A network manager can use this
information to determine whether notifications from a
particular SIP entity have been missed. The value of this
object MUST start at 1 and increase by 1 with each generated
notification. If a system restarts, the sequence number MAY
start again from 1."::={ sipCommonNotifObjects 6}--
-- Notifications
--sipCommonStatusCodeNotif NOTIFICATION-TYPEOBJECTS{
sipCommonNotifSequenceNumber,
sipCommonNotifApplIndex,
sipCommonStatusCodeNotifTo,
sipCommonStatusCodeNotifFrom,
sipCommonStatusCodeNotifCallId,
sipCommonStatusCodeNotifCSeq,
sipCommonStatusCodeIns,
sipCommonStatusCodeOuts
}STATUScurrentDESCRIPTION"Signifies that a specific status code has been sent or received
by the system."::={ sipCommonMIBNotifications 1}sipCommonStatusCodeThreshExceededInNotif NOTIFICATION-TYPEOBJECTS{
sipCommonNotifSequenceNumber,
sipCommonNotifApplIndex,
sipCommonStatusCodeIns
}STATUScurrentDESCRIPTION"Signifies that a specific status code was found to have been
received by the system frequently enough to exceed the
configured threshold. This notification can be used as
an early warning mechanism in lieu of using
sipCommonStatusCodeNotif."::={ sipCommonMIBNotifications 2}sipCommonStatusCodeThreshExceededOutNotif NOTIFICATION-TYPEOBJECTS{
sipCommonNotifSequenceNumber,
sipCommonNotifApplIndex,
sipCommonStatusCodeOuts
}STATUScurrentDESCRIPTION"Signifies that a specific status code was found to have been
sent by the system enough to exceed the configured threshold.
This notification can be used as an early warning mechanism in
lieu of using sipCommonStatusCodeNotif."::={ sipCommonMIBNotifications 3}sipCommonServiceColdStart NOTIFICATION-TYPEOBJECTS{
sipCommonNotifSequenceNumber,
sipCommonNotifApplIndex,
sipCommonCfgServiceStartTime
}STATUScurrentDESCRIPTION"Signifies that the SIP service has reinitialized itself or
started for the first time. This SHOULD result from a hard
'down' to 'up' administrative status change. The configuration
or behavior of the service MAY be altered."::={ sipCommonMIBNotifications 4}
sipCommonServiceWarmStart NOTIFICATION-TYPEOBJECTS{
sipCommonNotifSequenceNumber,
sipCommonNotifApplIndex,
sipCommonCfgServiceLastChange
}STATUScurrentDESCRIPTION"Signifies that the SIP service has reinitialized itself and is
restarting after an administrative 'reset'. The configuration
or behavior of the service MAY be altered."::={ sipCommonMIBNotifications 5}sipCommonServiceStatusChanged NOTIFICATION-TYPEOBJECTS{
sipCommonNotifSequenceNumber,
sipCommonNotifApplIndex,
sipCommonCfgServiceLastChange,
sipCommonCfgServiceOperStatus
}STATUScurrentDESCRIPTION"Signifies that the SIP service operational status has changed."::={ sipCommonMIBNotifications 6}--
-- Conformance
--sipCommonMIBCompliances
OBJECTIDENTIFIER::={ sipCommonMIBConformance 1}sipCommonMIBGroups
OBJECTIDENTIFIER::={ sipCommonMIBConformance 2}--
-- Compliance Statements
--sipCommonCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SIP entities."MODULE-- this moduleMANDATORY-GROUPS{ sipCommonConfigGroup,
sipCommonStatsGroup
}OBJECT sipCommonStatusCodeRowStatus
SYNTAXRowStatus{ active(1)}WRITE-SYNTAXRowStatus{ createAndGo(4), destroy(6)}DESCRIPTION"Support for createAndWait and notInService is not required."OBJECT sipCommonCfgServiceNotifEnable
MIN-ACCESSnot-accessibleDESCRIPTION"This object is optional and does not need to be supported."GROUP sipCommonInformationalGroup
DESCRIPTION"This group is OPTIONAL. A SIP entity can elect to not provide
any support for these objects, as they provide optional
information."GROUP sipCommonConfigTimerGroup
DESCRIPTION"This group is OPTIONAL. A SIP entity can elect to not provide
any timer configuration."GROUP sipCommonStatsRetryGroup
DESCRIPTION"This group is OPTIONAL. A SIP entity can elect to not provide
any retry statistics."GROUP sipCommonNotifGroup
DESCRIPTION"This group is OPTIONAL. A SIP entity can elect to not provide
any notifications. If implemented, the
sipCommonStatusCodeNotifGroup and sipCommonNotifObjectsGroup
MUST also be implemented."GROUP sipCommonStatusCodeNotifGroup
DESCRIPTION"This group is OPTIONAL. A SIP entity can elect to not provide
any notifications. If implemented, the sipCommonNotifGroup and
sipCommonNotifObjectsGroup MUST also be implemented."GROUP sipCommonNotifObjectsGroup
DESCRIPTION"This group is OPTIONAL. A SIP entity can elect to not provide
any notifications. If implemented, the
sipCommonStatusCodeNotifGroup and sipCommonNotifGroup MUST also
be implemented."::={ sipCommonMIBCompliances 1}--
-- Units of Conformance
--sipCommonConfigGroup OBJECT-GROUPOBJECTS{
sipCommonCfgProtocolVersion,
sipCommonCfgServiceOperStatus,
sipCommonCfgServiceStartTime,
sipCommonCfgServiceLastChange,
sipCommonPortTransportRcv,
sipCommonOptionTag,
sipCommonOptionTagHeaderField,
sipCommonCfgMaxTransactions,
sipCommonCfgServiceNotifEnable,
sipCommonCfgEntityType,
sipCommonMethodSupportedName
}STATUScurrentDESCRIPTION"A collection of objects providing configuration common to all
SIP entities."::={ sipCommonMIBGroups 1}sipCommonInformationalGroup OBJECT-GROUPOBJECTS{
sipCommonCfgOrganization
}STATUScurrentDESCRIPTION"A collection of objects providing configuration common to all
SIP entities."::={ sipCommonMIBGroups 2}sipCommonConfigTimerGroup OBJECT-GROUPOBJECTS{
sipCommonCfgTimerA,
sipCommonCfgTimerB,
sipCommonCfgTimerC,
sipCommonCfgTimerD,
sipCommonCfgTimerE,
sipCommonCfgTimerF,
sipCommonCfgTimerG,
sipCommonCfgTimerH,
sipCommonCfgTimerI,
sipCommonCfgTimerJ,
sipCommonCfgTimerK,
sipCommonCfgTimerT1,
sipCommonCfgTimerT2,
sipCommonCfgTimerT4
}STATUScurrentDESCRIPTION"A collection of objects providing timer configuration common to
all SIP entities."::={ sipCommonMIBGroups 3}sipCommonStatsGroup OBJECT-GROUPOBJECTS{
sipCommonSummaryInRequests,
sipCommonSummaryOutRequests,
sipCommonSummaryInResponses,
sipCommonSummaryOutResponses,
sipCommonSummaryTotalTransactions,
sipCommonSummaryDisconTime,
sipCommonMethodStatsOutbounds,
sipCommonMethodStatsInbounds,
sipCommonMethodStatsDisconTime,
sipCommonStatusCodeIns,
sipCommonStatusCodeOuts,
sipCommonStatusCodeRowStatus,
sipCommonStatusCodeDisconTime,
sipCommonTransCurrentactions,
sipCommonOtherStatsNumUnsupportedUris,
sipCommonOtherStatsNumUnsupportedMethods,
sipCommonOtherStatsOtherwiseDiscardedMsgs,
sipCommonOtherStatsDisconTime
}STATUScurrentDESCRIPTION"A collection of objects providing statistics common to all SIP
entities."::={ sipCommonMIBGroups 4}sipCommonStatsRetryGroup OBJECT-GROUPOBJECTS{
sipCommonStatsRetries,
sipCommonStatsRetryFinalResponses,
sipCommonStatsRetryNonFinalResponses,
sipCommonStatsRetryDisconTime
}STATUScurrentDESCRIPTION"A collection of objects providing retry statistics."::={ sipCommonMIBGroups 5}sipCommonNotifGroup NOTIFICATION-GROUPNOTIFICATIONS{
sipCommonStatusCodeNotif,
sipCommonStatusCodeThreshExceededInNotif,
sipCommonStatusCodeThreshExceededOutNotif,
sipCommonServiceColdStart,
sipCommonServiceWarmStart,
sipCommonServiceStatusChanged
}STATUScurrentDESCRIPTION"A collection of notifications common to all SIP entities."::={ sipCommonMIBGroups 6}sipCommonStatusCodeNotifGroup OBJECT-GROUPOBJECTS{
sipCommonStatusCodeNotifSend,
sipCommonStatusCodeNotifEmitMode,
sipCommonStatusCodeNotifThresh,
sipCommonStatusCodeNotifInterval
}STATUScurrentDESCRIPTION"A collection of objects related to the control and attribution
of notifications common to all SIP entities."::={ sipCommonMIBGroups 7}sipCommonNotifObjectsGroup OBJECT-GROUPOBJECTS{
sipCommonStatusCodeNotifTo,
sipCommonStatusCodeNotifFrom,
sipCommonStatusCodeNotifCallId,
sipCommonStatusCodeNotifCSeq,
sipCommonNotifApplIndex,
sipCommonNotifSequenceNumber
}STATUScurrent
DESCRIPTION"A collection of accessible-for-notify objects related to the
notification defined in this MIB module."::={ sipCommonMIBGroups 8}ENDSIP-UA-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE,Unsigned32,mib-2
FROM SNMPv2-SMI -- RFC 2578MODULE-COMPLIANCE,OBJECT-GROUPFROM SNMPv2-CONF -- RFC 2580applIndex
FROM NETWORK-SERVICES-MIB -- RFC 2788InetAddressType,InetAddressFROM INET-ADDRESS-MIB -- RFC 4001
SipTCEntityRole
FROM SIP-TC-MIB;-- RFC 4780sipUAMIB MODULE-IDENTITYLAST-UPDATED"200704200000Z"ORGANIZATION"IETF Session Initiation Protocol Working Group"CONTACT-INFO"SIP WG email: sip@ietf.org
Co-editor Kevin Lingle
Cisco Systems, Inc.
postal: 7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709
USA
email: klingle@cisco.com
phone: +1 919 476 2029
Co-editor Joon Maeng
email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule
CableLabs
postal: 858 Coal Creek Circle
Louisville, CO 80027
USA
email: jf.mule@cablelabs.com
phone: +1 303 661 9100
Co-editor Dave Walker
email: drwalker@rogers.com"DESCRIPTION
"Session Initiation Protocol (SIP) User Agent (UA) MIB module.
SIP is an application-layer signaling protocol for creating,
modifying, and terminating multimedia sessions with one or more
participants. These sessions include Internet multimedia
conferences and Internet telephone calls. SIP is defined in
RFC 3261 (June 2002).
A User Agent is an application that contains both a User Agent
Client (UAC) and a User Agent Server (UAS). A UAC is an
application that initiates a SIP request. A UAS is an
application that contacts the user when a SIP request is
received and that returns a response on behalf of the user.
The response accepts, rejects, or redirects the request.
Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC 4780; see the RFC itself for
full legal notices."REVISION"200704200000Z"DESCRIPTION"Initial version of the IETF SIP-UA-MIB module. This version
published as part of RFC 4780."::={ mib-2 150}-- Top-Level Components of this MIB.sipUAMIBObjects OBJECTIDENTIFIER::={ sipUAMIB 1}sipUAMIBConformance OBJECTIDENTIFIER::={ sipUAMIB 2}--
-- This MIB contains objects related to SIP User Agents.
--sipUACfgServer OBJECTIDENTIFIER::={ sipUAMIBObjects 1}--
-- SIP Server Configuration
--sipUACfgServerTable OBJECT-TYPESYNTAXSEQUENCEOF SipUACfgServerEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains SIP server configuration objects applicable
to each SIP user agent in this system."
::={ sipUACfgServer 1}sipUACfgServerEntry OBJECT-TYPESYNTAX SipUACfgServerEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A row of server configuration.
Each row represents those objects for a particular SIP user
agent present in this system. applIndex is used to uniquely
identify these instances of SIP user agents and correlate
them through the common framework of the NETWORK-SERVICES-MIB
(RFC 2788). The same value of applIndex used in the
corresponding SIP-COMMON-MIB is used here."INDEX{ applIndex, sipUACfgServerIndex }::={ sipUACfgServerTable 1}
SipUACfgServerEntry ::=SEQUENCE{
sipUACfgServerIndex Unsigned32,
sipUACfgServerAddressType InetAddressType,
sipUACfgServerAddress InetAddress,
sipUACfgServerRole SipTCEntityRole
}sipUACfgServerIndex OBJECT-TYPESYNTAXUnsigned32(1..4294967295)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A unique identifier of a server address when multiple addresses
are configured by the SIP entity. If one address isn't
reachable, then another can be tried."::={ sipUACfgServerEntry 1}sipUACfgServerAddressType OBJECT-TYPESYNTAXInetAddressTypeMAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"This object reflects the type of address contained in the
associated instance of sipUACfgServerAddress."REFERENCE"INET-ADDRESS-MIB (RFC 4001)"::={ sipUACfgServerEntry 2}sipUACfgServerAddress OBJECT-TYPESYNTAXInetAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the address of a SIP server this user
agent will use to proxy/redirect calls. The type of this
address is determined by the value of the
sipUACfgServerAddressType object."REFERENCE"INET-ADDRESS-MIB (RFC 4001)"::={ sipUACfgServerEntry 3}sipUACfgServerRole OBJECT-TYPESYNTAX SipTCEntityRole
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the function of the SIP server this user
agent should communicate with: registrar, proxy (outbound
proxy), etc."::={ sipUACfgServerEntry 4}--
-- Conformance
--sipUAMIBCompliances OBJECTIDENTIFIER::={ sipUAMIBConformance 1}sipUAMIBGroups OBJECTIDENTIFIER::={ sipUAMIBConformance 2}--
-- Compliance Statements
--sipUACompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SIP entities that implement the
SIP-UA-MIB module."MODULE-- this moduleMANDATORY-GROUPS{ sipUAConfigGroup }::={ sipUAMIBCompliances 1}--
-- Units of Conformance
--sipUAConfigGroup OBJECT-GROUPOBJECTS{
sipUACfgServerAddressType,
sipUACfgServerAddress,
sipUACfgServerRole
}STATUScurrentDESCRIPTION"A collection of objects providing information about the
configuration of SIP User Agents."::={ sipUAMIBGroups 1}ENDSIP-SERVER-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE,Counter32,Unsigned32,Gauge32,mib-2
FROM SNMPv2-SMI -- RFC 2578TruthValue,TimeStamp,DateAndTimeFROM SNMPv2-TC -- RFC 2579MODULE-COMPLIANCE,OBJECT-GROUPFROM SNMPv2-CONF -- RFC 2580SnmpAdminStringFROM SNMP-FRAMEWORK-MIB -- RFC 3411applIndex
FROM NETWORK-SERVICES-MIB -- RFC 2788InetAddressType,InetAddressFROM INET-ADDRESS-MIB;-- RFC 4001
sipServerMIB MODULE-IDENTITYLAST-UPDATED"200704200000Z"ORGANIZATION"IETF Session Initiation Protocol
Working Group"CONTACT-INFO"SIP WG email: sip@ietf.org
Co-editor: Kevin Lingle
Cisco Systems, Inc.
postal: 7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709
USA
email: klingle@cisco.com
phone: +1 919 476 2029
Co-editor: Joon Maeng
email: jmaeng@austin.rr.com
Co-editor: Jean-Francois Mule
CableLabs
postal: 858 Coal Creek Circle
Louisville, CO 80027
USA
email: jf.mule@cablelabs.com
phone: +1 303 661 9100
Co-editor: Dave Walker
email: drwalker@rogers.com
"DESCRIPTION"Session Initiation Protocol (SIP) Server MIB module. SIP is an
application-layer signaling protocol for creating, modifying,
and terminating multimedia sessions with one or more
participants. These sessions include Internet multimedia
conferences and Internet telephone calls. SIP is defined in
RFC 3261 (June 2002).
This MIB is defined for the management of SIP Proxy, Redirect,
and Registrar Servers.
A Proxy Server acts as both a client and a server. It accepts
requests from other clients, either responding to them or
passing them on to other servers, possibly after modification.
A Redirect Server accepts requests from clients and returns
zero or more addresses to that client. Unlike a User Agent
Server, it does not accept calls.
A Registrar is a server that accepts REGISTER requests. A
Registrar is typically co-located with a Proxy or Redirect
Server.
Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC 4780; see the RFC itself for
full legal notices."REVISION"200704200000Z"DESCRIPTION"Initial version of the IETF SIP-SERVER-MIB module. This
version published as part of RFC 4780."::={ mib-2 151}
-- Top-Level Components of this MIB.sipServerMIBObjects OBJECTIDENTIFIER::={ sipServerMIB 1}sipServerMIBConformance OBJECTIDENTIFIER::={ sipServerMIB 2}--
-- These groups contain objects common to all SIP servers.
--sipServerCfg OBJECTIDENTIFIER::={ sipServerMIBObjects 1}--
-- Common Server Configuration Objects
--sipServerCfgTable OBJECT-TYPESYNTAXSEQUENCEOF SipServerCfgEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains configuration objects applicable to SIP
Redirect and Proxy Servers."::={ sipServerCfg 1}sipServerCfgEntry OBJECT-TYPESYNTAX SipServerCfgEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A row of common configuration.
Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through
the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
The same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."INDEX{ applIndex }::={ sipServerCfgTable 1}
SipServerCfgEntry ::=SEQUENCE{
sipServerCfgHostAddressType InetAddressType,
sipServerCfgHostAddress InetAddress}sipServerCfgHostAddressType OBJECT-TYPESYNTAXInetAddressTypeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The type of Internet address by which the SIP server is
reachable."REFERENCE"RFC 3261, Section 19.1.1"::={ sipServerCfgEntry 1}sipServerCfgHostAddress OBJECT-TYPESYNTAXInetAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This is the host portion of a SIP URI that is assigned to the
SIP server. It MAY contain a fully qualified domain name or
an IP address. The length of the value will depend on the type
of address specified. The type of address given by this object
is controlled by sipServerCfgHostAddressType."REFERENCE"RFC 3261, Section 19.1.1"::={ sipServerCfgEntry 2}--
-- This group contains MIB objects
-- related to SIP Proxy Servers.
--sipServerProxyCfg OBJECTIDENTIFIER::={ sipServerMIBObjects 3}sipServerProxyStats OBJECTIDENTIFIER::={ sipServerMIBObjects 4}--
-- Proxy Server Configuration
--sipServerProxyCfgTable OBJECT-TYPESYNTAXSEQUENCEOF SipServerProxyCfgEntry
MAX-ACCESSnot-accessibleSTATUScurrent
DESCRIPTION"This table contains configuration objects applicable to SIP
Proxy Servers."::={ sipServerProxyCfg 1}sipServerProxyCfgEntry OBJECT-TYPESYNTAX SipServerProxyCfgEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A row of common proxy configuration.
Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."INDEX{ applIndex }::={ sipServerProxyCfgTable 1}
SipServerProxyCfgEntry ::=SEQUENCE{
sipServerCfgProxyStatefulness INTEGER,
sipServerCfgProxyRecursion TruthValue,
sipServerCfgProxyRecordRoute TruthValue,
sipServerCfgProxyAuthMethod BITS,
sipServerCfgProxyAuthDefaultRealm SnmpAdminString}sipServerCfgProxyStatefulness OBJECT-TYPESYNTAXINTEGER{stateless(1),transactionStateful(2),callStateful(3)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION
"This object reflects the default mode of operation for the
Proxy Server entity.
A stateless proxy is a logical entity that does not maintain
the client or server transaction state machines when it
processes requests. A stateless proxy forwards every request it
receives downstream and every response it receives upstream. If
the value of this object is stateless(1), the proxy defaults to
stateless operations.
A transaction stateful proxy, or simply a 'stateful proxy', is
a logical entity that maintains the client and server
transaction state machines during the processing of a request.
A (transaction) stateful proxy is not the same as a call
stateful proxy. If the value of this object is
transactionStateful(2), the proxy is stateful on a transaction
basis.
A call stateful proxy is a logical entity if it retains state
for a dialog from the initiating INVITE to the terminating BYE
request. A call stateful proxy is always transaction stateful,
but the converse is not necessarily true. If the value of this
object is callStateful(3), the proxy is call stateful."REFERENCE"RFC 3261, Section 16"::={ sipServerProxyCfgEntry 1}sipServerCfgProxyRecursion OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects whether or not the Proxy performs a
recursive search on the Contacts provided in 3xx redirects.
If the value of this object is 'true', a recursive search is
performed. If the value is 'false', no search is performed,
and the 3xx response is sent upstream towards the source of
the request."REFERENCE"RFC 3261 Sections 16.5 and 16.6"::={ sipServerProxyCfgEntry 2}sipServerCfgProxyRecordRoute OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"This object reflects whether or not the proxy adds itself to
the Record-Route header as a default action. This header is
used to list the proxies that insist on being in the signaling
path for subsequent requests related to the call leg.
If the value of this object is 'true', the proxy adds itself to
the end of the Record-Route header, creating the header if
required. If the value is 'false', the proxy does not add
itself to the Record-Route header."REFERENCE"RFC 3261, Section 20.30"::={ sipServerProxyCfgEntry 3}--
-- Security
--sipServerCfgProxyAuthMethod OBJECT-TYPESYNTAXBITS{none(0),tls(1),digest(2)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the authentication methods that MAY be
used to authenticate request originators.
bit 0 no authentication is performed
bit 1 TLS is used
bit 2 HTTP Digest is used."REFERENCE"RFC 3261 Sections 22, 23, 26, 26.2.3"::={ sipServerProxyCfgEntry 4}sipServerCfgProxyAuthDefaultRealm OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the default realm value used in
Proxy-Authenticate headers. Note that this MAY need to be
stored per user, in which case, this default value is ignored.
"REFERENCE"RFC 3261, Section 22.1"::={ sipServerProxyCfgEntry 5}--
-- Proxy Server Statistics
--sipServerProxyStatsTable OBJECT-TYPESYNTAXSEQUENCEOF SipServerProxyStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains the statistics objects applicable to all
SIP Proxy Servers in this system."::={ sipServerProxyStats 1}sipServerProxyStatsEntry OBJECT-TYPESYNTAX SipServerProxyStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A row of summary statistics.
Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."INDEX{ applIndex }::={ sipServerProxyStatsTable 1}
SipServerProxyStatsEntry ::=SEQUENCE{
sipServerProxyStatProxyReqFailures Counter32,
sipServerProxyStatsDisconTime TimeStamp}sipServerProxyStatProxyReqFailures OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains the number of occurrences of unsupported
options being specified in received Proxy-Require headers.
Such occurrences result in a 420 Bad Extension status code
being returned.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipServerProxyStatsDisconTime object in the same
row."::={ sipServerProxyStatsEntry 1}sipServerProxyStatsDisconTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of the sysUpTime object when the counters for the server
statistics objects in this row last experienced a discontinuity."::={ sipServerProxyStatsEntry 2}--
-- This group contains MIB objects related to SIP Registrars.
--sipServerRegCfg OBJECTIDENTIFIER::={ sipServerMIBObjects 5}sipServerRegStats OBJECTIDENTIFIER::={ sipServerMIBObjects 6}--
-- Registrar Configuration
--sipServerRegCfgTable OBJECT-TYPESYNTAXSEQUENCEOF SipServerRegCfgEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains configuration objects applicable to SIP
Registrars."::={ sipServerRegCfg 1}sipServerRegCfgEntry OBJECT-TYPESYNTAX SipServerRegCfgEntry
MAX-ACCESSnot-accessibleSTATUScurrent
DESCRIPTION"A row of common Registrar configuration.
Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."INDEX{ applIndex }::={ sipServerRegCfgTable 1}
SipServerRegCfgEntry ::=SEQUENCE{
sipServerRegMaxContactExpiryDuration Unsigned32,
sipServerRegMaxUsers Unsigned32,
sipServerRegCurrentUsers Gauge32,
sipServerRegDfltRegActiveInterval Unsigned32}sipServerRegMaxContactExpiryDuration OBJECT-TYPESYNTAXUnsigned32(0..4294967295)UNITS"seconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the maximum expiry that may be requested
by a User Agent for a particular Contact. User Agents can
specify expiry using either an Expiry header in a REGISTER
request, or using an Expires parameter in a Contact header in
a REGISTER request. If the value requested by the User Agent
is greater than the value of this object, then the contact
information is given the duration specified by this object, and
that duration is indicated to the User Agent in the response."::={ sipServerRegCfgEntry 1}sipServerRegMaxUsers OBJECT-TYPESYNTAXUnsigned32(1..4294967295)
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the maximum number of users that the
Registrar supports. The current number of users is reflected
by sipServerRegCurrentUsers."::={ sipServerRegCfgEntry 2}sipServerRegCurrentUsers OBJECT-TYPESYNTAXGauge32(0..4294967295)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the number of users currently registered
with the Registrar."::={ sipServerRegCfgEntry 3}sipServerRegDfltRegActiveInterval OBJECT-TYPESYNTAXUnsigned32(1..4294967295)UNITS"seconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object reflects the default time interval the Registrar
considers registrations to be active. The value is used to
compute the Expires header in the REGISTER response. If a user
agent requests a time interval shorter than specified by this
object, the Registrar SHOULD honor that request. If a Contact
entry does not have an 'expires' parameter, the value of the
Expires header field is used instead. If a Contact entry has no
'expires' parameter and no Expires header field is present,
the value of this object is used as the default value."REFERENCE"RFC 3261, Section 10.2"::={ sipServerRegCfgEntry 4}
--
-- Per User Information
--sipServerRegUserTable OBJECT-TYPESYNTAXSEQUENCEOF SipServerRegUserEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains information on all users registered to each
Registrar in this system."::={ sipServerRegCfg 2}sipServerRegUserEntry OBJECT-TYPESYNTAX SipServerRegUserEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This entry contains information for a single user registered to
this Registrar.
Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."INDEX{ applIndex, sipServerRegUserIndex }::={ sipServerRegUserTable 1}
SipServerRegUserEntry ::=SEQUENCE{
sipServerRegUserIndex Unsigned32,
sipServerRegUserUri SnmpAdminString,
sipServerRegUserAuthenticationFailures Counter32,
sipServerRegUserDisconTime TimeStamp}sipServerRegUserIndex OBJECT-TYPESYNTAXUnsigned32(1..4294967295)MAX-ACCESSnot-accessible
STATUScurrentDESCRIPTION"This object uniquely identifies a conceptual row in the table."::={ sipServerRegUserEntry 1}sipServerRegUserUri OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains the user's address-of-record. It is 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."::={ sipServerRegUserEntry 2}sipServerRegUserAuthenticationFailures OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains a count of the number of times the user
has failed authentication.
Discontinuities in the value of this counter can occur due to
successful user authentications and at re-initialization of
the SIP entity or service. A Management Station can detect
discontinuities in this counter by monitoring the
sipServerRegUserDisconTime object in the same row."::={ sipServerRegUserEntry 3}sipServerRegUserDisconTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of the sysUpTime object when the counters for the
user registration statistics objects in this row last
experienced a discontinuity."::={ sipServerRegUserEntry 4}
--
-- Per Contact Information
--sipServerRegContactTable OBJECT-TYPESYNTAXSEQUENCEOF SipServerRegContactEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains information on every location where a
registered user (specified by sipServerRegUserIndex) wishes to
be found (i.e., the user has provided contact information to
each SIP Registrar in this system)."::={ sipServerRegCfg 3}sipServerRegContactEntry OBJECT-TYPESYNTAX SipServerRegContactEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This entry contains information for a single Contact. Multiple
contacts may exist for a single user.
Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."INDEX{ applIndex,
sipServerRegUserIndex,
sipServerRegContactIndex
}::={ sipServerRegContactTable 1}
SipServerRegContactEntry ::=SEQUENCE{
sipServerRegContactIndex Unsigned32,
sipServerRegContactDisplayName SnmpAdminString,
sipServerRegContactURI SnmpAdminString,
sipServerRegContactLastUpdated TimeStamp,
sipServerRegContactExpiry DateAndTime,
sipServerRegContactPreference SnmpAdminString}sipServerRegContactIndex OBJECT-TYPESYNTAXUnsigned32(1..4294967295)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Along with the sipServerRegUserIndex, this object uniquely
identifies a conceptual row in the table."::={ sipServerRegContactEntry 1}sipServerRegContactDisplayName OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains the display name for the Contact. For
example, 'Santa at Home', or 'Santa on his Sled', corresponding
to contact URIs of sip:BigGuy@example.com or
sip:sclaus817@example.com, respectively."::={ sipServerRegContactEntry 2}sipServerRegContactURI OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains either a SIP URI where the user can be
contacted. This URI is normally returned to a client from a
Redirect Server, or is used as the RequestURI in a SIP request
line for requests forwarded by a proxy."::={ sipServerRegContactEntry 3}sipServerRegContactLastUpdated OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION
"This object indicates the time when this contact information
was accepted. If the contact information is updated via a
subsequent REGISTER of the same information, this object is
also updated."::={ sipServerRegContactEntry 4}sipServerRegContactExpiry OBJECT-TYPESYNTAXDateAndTimeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains the date and time when the contact
information will no longer be valid. Such times may be
specified by the user at registration (i.e., Expires header or
expiry parameter in the Contact information), or a system
default can be applied."::={ sipServerRegContactEntry 5}sipServerRegContactPreference OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object indicates a relative preference for the particular
Contact header field value compared to other bindings for this
address-of-record. A registering user may provide this
preference as a 'qvalue' parameter in the Contact header.
The format of this item is a decimal number between 0 and 1
(for example 0.9). Higher values indicate locations preferred
by the user."REFERENCE"RFC 3261, Section 10.2.1.2, 16.6, and 20.10"::={ sipServerRegContactEntry 6}--
-- Registrar Statistics
--sipServerRegStatsTable OBJECT-TYPESYNTAXSEQUENCEOF SipServerRegStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains the summary statistics objects applicable
to all SIP Registrars in this system."::={ sipServerRegStats 1}sipServerRegStatsEntry OBJECT-TYPESYNTAX SipServerRegStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A row of summary statistics.
Each row represents those objects for a particular SIP server
present in this system. applIndex is used to uniquely identify
these instances of SIP servers and correlate them through the
common framework of the NETWORK-SERVICES-MIB (RFC 2788). The
same value of applIndex used in the corresponding
SIP-COMMON-MIB is used here."INDEX{ applIndex }::={ sipServerRegStatsTable 1}
SipServerRegStatsEntry ::=SEQUENCE{
sipServerRegStatsAcceptedRegs Counter32,
sipServerRegStatsRejectedRegs Counter32,
sipServerRegStatsDisconTime TimeStamp}sipServerRegStatsAcceptedRegs OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains a count of the number of REGISTER requests
that have been accepted (status code 200) by the Registrar.
This includes additions of new contact information, refreshing
contact information, as well as requests for deletion of
contact information.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipServerRegStatsDisconTime object in the same
row."::={ sipServerRegStatsEntry 1}
sipServerRegStatsRejectedRegs OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object contains a count of the number REGISTER requests
that have been rejected by the Registrar.
Discontinuities in the value of this counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter by
monitoring the sipServerRegStatsDisconTime object in the same
row."::={ sipServerRegStatsEntry 2}sipServerRegStatsDisconTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value of the sysUpTime object when the counters for the
registrar statistics objects in this row last experienced a
discontinuity."::={ sipServerRegStatsEntry 3}--
-- Conformance
--sipServerMIBCompliances
OBJECTIDENTIFIER::={ sipServerMIBConformance 1}sipServerMIBGroups
OBJECTIDENTIFIER::={ sipServerMIBConformance 2}--
-- Compliance Statements
--sipServerProxyServerCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SIP entities acting as Proxy
Servers."MODULE-- this moduleMANDATORY-GROUPS{ sipServerConfigGroup,
sipServerProxyConfigGroup,
sipServerProxyStatsGroup
}::={ sipServerMIBCompliances 1}sipRedirectServerCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SIP entities acting as Redirect
Servers."MODULE-- this moduleMANDATORY-GROUPS{ sipServerConfigGroup }::={ sipServerMIBCompliances 2}sipServerRegistrarServerCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SIP entities acting as
Registrars."MODULE-- this moduleMANDATORY-GROUPS{ sipServerConfigGroup,
sipServerRegistrarConfigGroup,
sipServerRegistrarStatsGroup }GROUP sipServerRegistrarUsersGroup
DESCRIPTION"This is an optional group."::={ sipServerMIBCompliances 3}--
-- Units of Conformance
--sipServerConfigGroup OBJECT-GROUPOBJECTS{
sipServerCfgHostAddressType,
sipServerCfgHostAddress
}STATUScurrentDESCRIPTION"A collection of objects providing configuration common to SIP
Proxy and Redirect servers."::={ sipServerMIBGroups 1}sipServerProxyConfigGroup OBJECT-GROUPOBJECTS{
sipServerCfgProxyStatefulness,
sipServerCfgProxyRecursion,
sipServerCfgProxyRecordRoute,
sipServerCfgProxyAuthMethod,
sipServerCfgProxyAuthDefaultRealm
}STATUScurrentDESCRIPTION"A collection of objects providing configuration for SIP Proxy
servers."::={ sipServerMIBGroups 2}sipServerProxyStatsGroup OBJECT-GROUPOBJECTS{
sipServerProxyStatProxyReqFailures,
sipServerProxyStatsDisconTime
}STATUScurrentDESCRIPTION"A collection of objects providing statistics for SIP Proxy
servers."::={ sipServerMIBGroups 3}sipServerRegistrarConfigGroup OBJECT-GROUPOBJECTS{
sipServerRegMaxContactExpiryDuration,
sipServerRegMaxUsers,
sipServerRegCurrentUsers,
sipServerRegDfltRegActiveInterval
}STATUScurrentDESCRIPTION"A collection of objects providing configuration for SIP
Registrars."::={ sipServerMIBGroups 4}sipServerRegistrarStatsGroup OBJECT-GROUPOBJECTS{
sipServerRegStatsAcceptedRegs,
sipServerRegStatsRejectedRegs,
sipServerRegStatsDisconTime
}STATUScurrentDESCRIPTION"A collection of objects providing statistics for SIP
Registrars."::={ sipServerMIBGroups 5}
sipServerRegistrarUsersGroup OBJECT-GROUPOBJECTS{
sipServerRegUserUri,
sipServerRegUserAuthenticationFailures,
sipServerRegUserDisconTime,
sipServerRegContactDisplayName,
sipServerRegContactURI,
sipServerRegContactLastUpdated,
sipServerRegContactExpiry,
sipServerRegContactPreference
}STATUScurrentDESCRIPTION"A collection of objects related to registered users."::={ sipServerMIBGroups 6}END