SIP
Click on the red underlined text to get to the source
... managed objects that are used to
manage Session Initiation Protocol (SIP) entities, which include User
Agents, and Proxy, Redirect and Registrar servers. The managed
objects ...
... User
Agents, and Proxy, Redirect and Registrar servers. The managed
objects defined in this document are intended to provide basic SIP
protocol management for SIP entities ...
... Registrar servers. It is intended to provide management of the basic
SIP entities. It provides for monitoring of status and protocol
statistics, as well as for configuration of SIP entities.
...
... SIP entities. It provides for monitoring of status and protocol
statistics, as well as for configuration of SIP entities.
...
... MIB contains common MIB objects
used in all the SIP entities. SIP-SERVER-MIB contains objects
...
... * sipCommonCfgBase: This object group defines configuration
objects common to all SIP entities, including the SIP protocol
version ...
... group defines configuration
objects common to all SIP entities, including the SIP protocol
version, the type of SIP entity ...
... UA, proxy, redirect, registrar
servers), the operational and administrative status, the SIP
organization name, the maximum number of SIP transactions ...
... servers), the operational and administrative status, the SIP
organization name, the maximum number of SIP transactions an
entity ...
... group defines timer
configuration objects applicable to SIP user agent and stateful
SIP proxy ...
... * sipCommonSummaryStats: This object group defines a table
containing the summary statistics objects applicable to all SIP
entities, including the total number of all SIP requests and
responses in/out and the total number of transactions ...
... group defines a table
containing the summary statistics objects applicable to all SIP
entities, including the total number of all SIP requests and
responses in/out and the total number of transactions.
...
... * sipCommonMethodStats: This object group defines a table
containing the SIP method statistics objects applicable to all
SIP entities ...
... SIP method statistics objects applicable to all
SIP entities, including the number of outbound and inbound
requests on a per method basis. Retransmissions ...
... * sipCommonStatusCode: This object group defines a table
indicating the number of SIP responses (in and out) that the
SIP entity has been requested to monitor on a per-method ...
... indicating the number of SIP responses (in and out) that the
SIP entity has been requested to monitor on a per-method basis
(100, 200, 302, etc.).
...
... containing a gauge reflecting the number of transactions
currently awaiting definitive responses by the managed SIP
entity.
* sipCommonStatsRetry: This object group ...
... * sipCommonOtherStats: This object group defines additional
statistics objects including the number of SIP requests
received with unsupported URIs, the number of requests received
...
... received with unsupported URIs, the number of requests received
with unsupported SIP methods, and the number of discarded
messages.
...
... * sipServerCfg: This object group defines common server
configuration objects including the SIP server host address.
...
... * sipServerProxyCfg: This object group defines configuration
objects for SIP Proxy Servers including the proxy mode of
operation (stateless ...
... * sipServerProxyStats: This object group defines a table
containing the statistics objects applicable to SIP Proxy
Servers. It includes the number of occurrences of unsupported
options being specified in received Proxy-Require headers ...
... * sipServerRegCfg: This object group defines common configuration
objects for SIP Registrar servers, including the ability to
accept third-party registrations ...
... * sipServerRegStats: This object group contains summary
statistics objects for SIP Registrar servers. Precisely, it
contains the number of REGISTER requests that have been
...
...
* sipUACfgServer: This object group specifies SIP server
configuration objects applicable to SIP user agents including
...
... group specifies SIP server
configuration objects applicable to SIP user agents including
the Internet address of the SIP ...
... To conform with this specification, an SNMP agent MUST implement the
SIP-TC-MIB module, plus the SIP-COMMON-MIB module ...
... SIP-TC-MIB module, plus the SIP-COMMON-MIB module and one of the SIP
entity-type-specific MIB modules ...
... MIB module, plus the SIP-COMMON-MIB module and one of the SIP
entity-type-specific MIB modules (SIP-SERVER-MIB ...
... UA-MIB) as
applicable for each instance of a SIP entity being managed. If a
device has more than one SIP entity or multiple instances of the same
...
... applicable for each instance of a SIP entity being managed. If a
device has more than one SIP entity or multiple instances of the same
entity type, it MUST implement multiple SIP ...
... SIP entity or multiple instances of the same
entity type, it MUST implement multiple SIP modules. Section 5.2
describes handling of multiple instances in detail.
...
...
The data types SipTCTransportProtocol, SipTCEntityRole,
SipTCOptionTagHeaders, and SipTCMethodName are defined in the SIP-
TC-MIB module and used as Textual Conventions ...
... MIB, the authors considered the following
requirement: the SIP MIB must allow a single system with a single
SNMP agent ...
... MIB must allow a single system with a single
SNMP agent to support multiple instances of various SIP MIB modules.
This requirement ...
... MIB and, at a minimum, MUST support the index and name objects
(applIndex and applName) in the application table (applTable). In
order to allow each instance of a SIP entity to be managed as a
separate network service application, a naming convention SHOULD be
...
... network service application, a naming convention SHOULD be
used to make the application name unique. For example, if a system
is running 2 SIP UAs that need to be managed as 2 separate SIP
entities, by convention, the application names used in the Network
Services Monitoring ...
... is running 2 SIP UAs that need to be managed as 2 separate SIP
entities, by convention, the application names used in the Network
Services Monitoring MIB application table should be "sip_ua1" and
...
... "sip_proxy17".
o for a SIP Registrar entity, the applName value SHOULD be equal to
a character string starting ...
... "sip_registrar1", "sip_registrar2".
o for a SIP User Agent entity, the applName value SHOULD be equal to
a character string starting ...
... system administrator or configuration files of the
SIP entity). This note is illustrated in the first example
provided below.
...
...
o applVersion: version of the SIP application.
o applUptime: the value of applUptime MUST be identical to the value
...
...
o applUptime: the value of applUptime MUST be identical to the value
of sipCommonCfgServiceStartTime defined in the SIP-COMMON-MIB
module.
...
...
o applLastChange: the value of applLastChange MUST be identical to
the value of sipCommonCfgServiceLastChange defined in the SIP-
COMMON module.
...
... The tables below illustrate how a system acting as both Proxy and
Registrar server might be configured to maintain separate SIP-
COMMON-MIB instances.
...
... | applIndex | applName | applDescription |
+-----------+-------------------+----------------------+
| 1 | "sip_proxy10" | "ACME SIP Proxy" |
| 2 | "sip_registrar17" | "ACME SIP Registrar ...
... SIP Proxy" |
| 2 | "sip_registrar17" | "ACME SIP Registrar" |
+-----------+-------------------+----------------------+
...
... +-----------+-------------------+----------------------+
The SIP-COMMON-MIB sipCommonCfgTable would have two rows: one for the
proxy ...
... proxy (applIndex=1) and one for the registrar (applIndex=2). The
SIP-SERVER-MIB tables would, however, only be populated with one row
...
... Version | Status | |
+---------+------------------------+--------------------------+-----+
| 1 | "SIP/2.0" | up(1) | |
| 2 | "SIP/2.0" | restarting ...
... | 1 | "SIP/2.0" | up(1) | |
| 2 | "SIP/2.0" | restarting(4) | |
+---------+------------------------+--------------------------+-----+
...
... +---------+------------------------+--------------------------+-----+
while the sipServerProxyCfgTable in SIP-SERVER-MIB might be populated
as:
...
... +-----------+-------------------------------+-----+
and the sipServerRegUserTable in SIP-SERVER-MIB might be populated
as:
...
... Proxy and Registrar server, where the two entities share a single
instance of SIP-COMMON-MIB.
...
... +-----------+------------------------+------------------------------+
| 1 | "sip_proxy_registrar1" | "ACME SIP Proxy and |
| | | Registrar" |
...
... +-----------+------------------------+------------------------------+
The SIP-COMMON-MIB sipCommonCfgTable would have only one row to cover
...
... |applIndex |sipCommonCfgProtocolVersion|sipCommonCfgServiceOperStatus|
+----------+---------------------------+-----------------------------+
| 1 | "SIP/2.0" | up(1) |
+----------+---------------------------+-----------------------------+
...
... +----------+---------------------------+-----------------------------+
while the sipServerRegUserTable in SIP-SERVER-MIB might be populated
as:
...
... MIB assocTable is not considered a requirement
for SIP systems. It is not a mandatory group for compliance with the
NETWORK ...
...
The SIP MIB modules defined in this document IMPORT definitions
normatively from the following MIB modules ...
... This MIB module also includes REFERENCE clauses that normatively
refer to SIP [RFC3261] and INET-ADDRESS-MIB ...
... in some of the examples described in the DESCRIPTION clauses,
including Reliability of Provisional Responses in SIP [RFC3262] and
SIP ...
... methods may be defined. In order to avoid having to update the SIP-
COMMON-MIB module to accommodate these extension methods ...
... method identifier name (SipTCMethodName TEXTUAL-CONVENTION) to
represent all SIP methods registered with IANA.
...
...
For example, the sipCommonMethodSupportedTable is the main table for
listing all of the SIP methods supported by a system, including the
SIP ...
... SIP methods supported by a system, including the
SIP methods defined in RFC 3261prop [RFC3261 ...
... RFC3261], Section 27.4) establishes
the sub-registries for SIP Methods and Response Codes under
...
... http://www.iana.org/assignments/sip-parameters. This document uses
the existing sub-registry for the names of registered SIP methods.
...
... methods.
For example, in the sipCommonMethodSupportedTable of SIP-COMMON-MIB,
the sipCommonMethodSupportedName values can be represented as
...
... SIP Textual Conventions ...
...
SIP-TC-MIB DEFINITIONS ::= BEGIN
...
... DESCRIPTION
"Session Initiation Protocol (SIP) MIB TEXTUAL-CONVENTION
module used by other SIP ...
... DESCRIPTION
"This convention defines the role of a SIP entity. Examples of
SIP entities are proxies ...
... 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
...
... DESCRIPTION
"This TEXTUAL-CONVENTION is a string that uniquely identifies a
SIP method. The scope of uniqueness is the context of all
...
... SIP Common MIB Module ...
...
SIP-COMMON-MIB DEFINITIONS ::= BEGIN
...
... DESCRIPTION
"Session Initiation Protocol (SIP) Common MIB module. This
module defines objects that may be common to all SIP entities ...
... SIP) Common MIB module. This
module defines objects that may be common to all SIP entities.
SIP ...
... This MIB is defined for managing objects that are common to
SIP User Agents (UAs), Proxy, Redirect, and Registrar servers.
...
... --
-- This MIB contains objects that are common to all SIP entities.
--
...
... OBJECT IDENTIFIER ::= { sipCommonMIBObjects 2 }
-- SIP message summary statistics
sipCommonSummaryStats OBJECT IDENTIFIER ...
... DESCRIPTION
"This table contains the common configuration objects applicable
to all SIP entities."
::= { sipCommonCfgBase 1 }
...
...
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 ...
... 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 ...
... DESCRIPTION
"This object will reflect the version of SIP supported by this
SIP entity. It will follow the same format as SIP ...
... version of SIP supported by this
SIP entity. It will follow the same format as SIP version
information contained in the SIP messages ...
... 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 ...
... 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 ...
... SIP version
information contained in the SIP messages generated by this SIP
entity. For example, entities supporting SIP version 2 will
...
... version
information contained in the SIP messages generated by this SIP
entity. For example, entities supporting SIP version 2 will
return 'SIP ...
... "This object contains the current operational state of
the SIP application.
unknown : The operational status cannot be determined
...
... 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 ...
... SIP
requests and responses.
down : The application is currently unable to process
SIP messages.
congested : The application is operational but no additional
...
... 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
...
... 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
...
...
The operational status values defined for this object are not
based on any specific information contained in the SIP
standard."
::= { sipCommonCfgEntry 2 }
...
... DESCRIPTION
"The value of sysUpTime at the time the SIP entity was last
started. If started prior to the last re-initialization of the
...
... DESCRIPTION
"The value of sysUpTime at the time the SIP entity entered its
current operational state. If the current state ...
... STATUS current
DESCRIPTION
"This object contains the organization name that the SIP entity
inserts into Organization headers of SIP messages ...
... SIP entity
inserts into Organization headers of SIP messages processed by
this system. If the string is empty, no Organization header is
...
... transactions per second that the SIP entity can manage. In
general, the value of this object SHOULD reflect a level of
transaction ...
... 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 ...
... 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 ...
... STATUS current
DESCRIPTION
"This object identifies the list of SIP entities to which this
row is related. It is defined as a bit ...
... 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 ...
... DESCRIPTION
"This table contains the list of ports that each SIP entity in
this system is allowed to use. These ports can be advertised
...
...
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 ...
... 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 ...
... "This object reflects a particular port that can be used by the
SIP application."
::= { sipCommonPortEntry 1 }
...
... DESCRIPTION
"This object will specify the transport protocol the SIP entity
will use to receive SIP messages.
...
... -- Support for SIP option tags (SIP extensions).
-- SIP extensions MAY be supported or required by SIP entities ...
... option tags (SIP extensions).
-- SIP extensions MAY be supported or required by SIP entities.
--
...
... "This table contains a list of the SIP option tags (SIP
extensions) that are either required, supported, or
unsupported by the SIP entity ...
... SIP
extensions) that are either required, supported, or
unsupported by the SIP entity. These option tags are
used in the Require, Proxy ...
... STATUS current
DESCRIPTION
"A particular SIP option tag (extension) supported or
unsupported by the SIP entity ...
... 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 ...
... 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 ...
...
DESCRIPTION
"This object indicates whether the SIP option tag is supported
(Supported header ...
... header) by the SIP entity.
A SIP option tag may be both supported and required."
::= { sipCommonOptionTagEntry 3 }
...
... DESCRIPTION
"This table contains a list of methods supported by each SIP
entity in this system (see the standard set of SIP methods in
...
... "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 3261prop ...
... 3261prop). Any additional methods that may be
incorporated into the SIP protocol can be represented by this
table without any requirement to update ...
... From a protocol point of view, the list of methods advertised
by the SIP entity in the Allow header (Section 20.5 of RFC
3261prop ...
...
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 ...
... 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 ...
... "This table contains timer configuration objects applicable to
SIP user agent and SIP stateful Proxy Server entities."
...
... timer configuration objects applicable to
SIP user agent and SIP stateful Proxy Server entities."
::= { sipCommonCfgTimer 1 }
...
...
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 ...
... 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 ...
... 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
...
... STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP entity will wait to
receive a final response to an INVITE. The timer ...
... STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP Proxy Server will
wait to receive a provisional response to an INVITE. The Timer ...
... 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 ...
... STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP entity will wait to
receive a final response to a non-INVITE request. The timer ...
... STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP entity will wait to
receive additional ACK message retransmissions ...
... STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP server will wait to
receive retransmissions of non-INVITE requests ...
... STATUS current
DESCRIPTION
"This object reflects the maximum time a SIP client will wait to
receive retransmissions ...
... "This object reflects the T1 timer for a SIP entity. T1 is an
estimate of the round-trip time ...
... "This object reflects the T2 timer for a SIP entity. T2 is the
maximum retransmit interval for non-INVITE requests ...
... "This object reflects the T4 timer for a SIP entity. T4 is the
maximum duration a message will remain in the network ...
... DESCRIPTION
"This table contains the summary statistics objects applicable
to all SIP entities. Each row represents those objects for a
particular SIP entity ...
... SIP entities. Each row represents those objects for a
particular SIP entity present in this system."
::= { sipCommonSummaryStats 1 }
...
...
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 ...
... 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 ...
... STATUS current
DESCRIPTION
"This object indicates the total number of SIP request messages
received by the SIP entity, including retransmissions ...
... "This object indicates the total number of SIP request messages
received by the SIP entity, including retransmissions.
...
... counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter ...
... STATUS current
DESCRIPTION
"This object contains the total number of SIP request messages
sent out (originated and relayed) by the SIP entity. Where a
...
... "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 ...
... counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter ...
... STATUS current
DESCRIPTION
"This object contains the total number of SIP response messages
received by the SIP entity, including retransmissions ...
... "This object contains the total number of SIP response messages
received by the SIP entity, including retransmissions.
...
... counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter ...
... STATUS current
DESCRIPTION
"This object contains the total number of SIP response messages
sent (originated and relayed) by the SIP entity including
...
... "This object contains the total number of SIP response messages
sent (originated and relayed) by the SIP entity including
retransmissions.
...
... counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter ...
... counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter ...
... DESCRIPTION
"This table contains the method statistics objects for SIP
entities. Each row represents those objects for a particular
SIP entity ...
... SIP
entities. Each row represents those objects for a particular
SIP entity present in this system."
::= { sipCommonMethodStats 1 }
...
...
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 ...
... 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 ...
... STATUS current
DESCRIPTION
"This object uniquely identifies the SIP method related to the
objects in a particular row ...
... DESCRIPTION
"This object reflects the total number of requests sent by the
SIP entity, excluding retransmissions. Retransmissions are
...
... DESCRIPTION
"This object reflects the total number of requests received by
the SIP entity. Retransmissions are counted separately and are
not reflected in this counter ...
... STATUS current
DESCRIPTION
"This table contains the list of SIP status codes that each SIP
entity in this system has been requested to monitor. It is the
...
... "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.
...
... DESCRIPTION
"This row contains information on a particular SIP status code
that the SIP entity has been requested to monitor. Entries
...
... 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 ...
... 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 ...
... STATUS current
DESCRIPTION
"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 ...
... DESCRIPTION
"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."
...
... DESCRIPTION
"This object reflects the total number of response messages
received by the SIP entity with the status code value contained
in the sipCommonStatusCodeValue column.
...
... counter can occur at
re-initialization of the SIP entity or service, or when the
monitoring of the status code ...
... DESCRIPTION
"This object reflects the total number of response messages sent
by the SIP entity with the status code value contained in the
sipCommonStatusCodeValue column.
...
... counter can occur at
re-initialization of the SIP entity or service, or when the
monitoring of the Status code ...
... notifications related to
particular status codes that each SIP entity in this system has
been requested to monitor.
...
... row contains information controlling notifications for a
particular SIP status code that the SIP entity has been
requested to monitor."
...
... notifications for a
particular SIP status code that the SIP entity has been
requested to monitor."
AUGMENTS { sipCommonStatusCodeEntry }
...
... 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 ...
... "This table contains information on the transactions currently
awaiting definitive responses by each SIP entity in this
system.
...
... STATUS current
DESCRIPTION
"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 ...
... 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 ...
... DESCRIPTION
"This table contains retry statistics objects applicable to each
SIP entity in this system."
::= { sipCommonStatsRetry 1 }
...
...
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 ...
... 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 ...
... STATUS current
DESCRIPTION
"This object uniquely identifies the SIP method related to the
objects in a row ...
... "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.
...
... counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter ...
... DESCRIPTION
"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.
...
... counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter ...
... DESCRIPTION
"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 ...
... counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter ...
... DESCRIPTION
"This table contains other common statistics supported by each
SIP entity in this system."
::= { sipCommonOtherStats 1 }
...
... STATUS current
DESCRIPTION
"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 ...
... 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 ...
... counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter ...
... STATUS current
DESCRIPTION
"Number of SIP requests received with unsupported methods. A
server normally responds to such requests with a 501 (Not
...
... counter can occur at
re-initialization of the SIP entity or service. A Management
Station can detect discontinuities in this counter ...
... STATUS current
DESCRIPTION
"Number of SIP messages received that, for any number of
reasons, was discarded without a response.
...
... counter can occur at
re-