JUNIPER-SIP-COMMON-MIB

All MIBs › JUNIPER-SIP-COMMON-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2009-02-09

Category: Domain: VoIP/Telephony, Vendor: Juniper

Description: Juniper Networks MIB for monitoring SIP (Session Initiation Protocol) call statistics on Juniper mobile gateway platforms.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is JUNIPER-SIP-COMMON-MIB?

JUNIPER-SIP-COMMON-MIB is a Juniper Networks enterprise MIB defining objects common to all SIP (Session Initiation Protocol) entities on Juniper mobile-gateway and session platforms. It exposes SIP service configuration, such as protocol version, organization, and max transactions, and operational status objects shared across SIP application instances, along with port-level configuration. Its monitoring value centers on software/service status, service operational status, start time, and last-change timestamp, which together behave like an uptime/availability indicator for the SIP signaling service, complementing call-statistics MIBs. It is Juniper's enterprise implementation building on general SIP entity concepts rather than a direct IETF standard. Typical deployment is Juniper mobile/session gateways handling SIP-based voice/video signaling in service-provider or enterprise VoIP networks. Engineers can download the JUNIPER-SIP-COMMON-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-SIP-COMMON-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Juniper Networks mobile/session gateways
Juniper SIP-capable security/routing platforms

Monitoring Examples

An admin would poll jnxSipCommonCfgTable/jnxSipCommonCfgEntry for jnxSipCommonCfgServiceOperStatus and jnxSipCommonCfgServiceStartTime to confirm the SIP service is up and compute effective uptime, while jnxSipCommonCfgServiceLastChange flags recent restarts. jnxSipCommonPortTable/jnxSipCommonPortEntry would be checked to verify the SIP service is still listening on its configured ports, and jnxSipCommonCfgMaxTransactions helps confirm the instance hasn't hit its configured transaction ceiling.

What Can Be Monitored

SIP service operational status
service start time / uptime
service last-change time
max concurrent transactions
configured SIP listening ports
SIP protocol version/organization

Imported Objects

From INET-ADDRESS-MIB

InetPortNumber

From JUNIPER-JS-SMI

jnxVoip

OBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
TimeTicks
Unsigned32

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using jnxSipCommonCfgServiceOperStatus OID:

Select a Juniper Networks mobile/session gateway (SIP entity common objects) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type jnxSipCommonCfgServiceOperStatus into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The current operational state of the SIP application — unknown, up (processing SIP requests normally), or down. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'up', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxSip	1.3.6.1.4.1.2636.3.39.1.15.2
jnxSipCommonMIB	1.3.6.1.4.1.2636.3.39.1.15.2.1			This is Juniper Networks' implementation of enterprise specific MIB for SIP. This module defines objects which may be common to all SIP entities.
jnxSipCommonMIBObjects	1.3.6.1.4.1.2636.3.39.1.15.2.1.1
jnxSipCommonCfgTable	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.1		not-accessible	This table contains the common configuration objects applicable to all SIP entities.
jnxSipCommonCfgEntry	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.1.1		not-accessible	A row of common configuration. Each row represents objects for a particular SIP entity instance present in this system.
STR jnxSipCfgApplName	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.1.1.1	DisplayString	not-accessible	The name of the network application which uniquely identifies the application to which this entry is applicable.
STR jnxSipCommonCfgProtocolVersion	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.1.1.2	SnmpAdminString	read-only	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.
INT jnxSipCommonCfgServiceOperStatusEx	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.1.1.3	INTEGER	read-only	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.
TIK jnxSipCommonCfgServiceStartTime	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.1.1.4	TimeTicks	read-only	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.
TIK jnxSipCommonCfgServiceLastChange	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.1.1.5	TimeTicks	read-only	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.
STR jnxSipCommonCfgOrganization	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.1.1.6	SnmpAdminString	read-only	This object contains the organization name which 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.
U32 jnxSipCommonCfgMaxTransactions	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.1.1.7	Unsigned32	read-only	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.
BIT jnxSipCommonCfgEntityType	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.1.1.8	Bits	read-only	This object identifies the list of SIP entities this row is related to. It is defined as a bit map. Each bit represents a type of SIP entity. If a bit has value 1, the SIP entity represented by this row plays the role of this entity type. If a bit has value 0, the SIP entity represented by this row does not act as this entity type Combinations of bits can be set when the SIP entity plays multiple SIP roles.
jnxSipCommonPortTable	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.2		not-accessible	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.
jnxSipCommonPortEntry	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.2.1		not-accessible	Specification of a particular port. Each row represents those objects for a particular SIP entity present in this system.
STR jnxSipPortApplName	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.2.1.1	DisplayString	not-accessible	The name of the network application which uniquely identifies the application to which this entry is applicable.
INE jnxSipCommonPort	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.2.1.2	InetPortNumber	not-accessible	This object reflects a particular port that can be used by the SIP application.
BIT jnxSipCommonPortTransportRcv	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.2.1.3	Bits	read-only	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.
jnxSipCommonOptionTagTable	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.3		not-accessible	This table contains a list of the SIP option tags (SIP extensions) that either required, supported, or unsupported by the SIP entity. These option tags are used in the Require, Proxy-Require, Supported and Unsupported header fields. Example: if a user agent client supports and requires the server to support reliability of provisional responses (IETF RFC 3262), this table contains a row with the option tag string '100rel' in jnxSipCommonOptionTag and the OCTET STRING value of '1010 0000' or '0xA0' in jnxSipCommonOptionTagHeaderField. 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).
jnxSipCommonOptionTagEntry	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.3.1		not-accessible	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.
STR jnxSipOptionTagApplName	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.3.1.1	DisplayString	not-accessible	The name of the network application which uniquely identifies the application to which this entry is applicable.
U32 jnxSipCommonOptionTagIndex	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.3.1.2	Unsigned32	not-accessible	This object uniquely identifies a conceptual row in the table.
STR jnxSipCommonOptionTag	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.3.1.3	SnmpAdminString	read-only	This object indicates the SIP option tag. The option tag names are registered with IANA and available at http://www.iana.org/.
BIT jnxSipCommonOptionTagHeaderField	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.3.1.4	Bits	read-only	This object indicates whether the SIP option tag is supported (Supported header), unsupported (Unsupported header), required (Require or Proxy-Require header) by the SIP entity. A SIP option tag may be both supported and required.
jnxSipCommonMethodSupportedTable	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.4		not-accessible	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; conveying to the NMS capabilities of the managed system.
jnxSipCommonMethodSupportedEntry	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.4.1		not-accessible	A particular method supported by the SIP entity. Each row represents those objects for a particular SIP entity present in this system.
STR jnxSipMethodSupportedApplName	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.4.1.1	DisplayString	not-accessible	The name of the network application which uniquely identifies the application to which this entry is applicable.
U32 jnxSipCommonMethodSupportedIndex	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.4.1.2	Unsigned32	not-accessible	This object uniquely identifies a conceptual row in the table for a specific SIP method.
OCT jnxSipCommonMethodSupportedName	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.4.1.3	OCTET STRING	read-only	This object reflects the supported method's name. The method name MUST be all upper case (e.g, 'INVITE').
jnxSipCommonCfgTimerTable	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5		not-accessible	This table contains timer configuration objects applicable to SIP user agent and SIP stateful Proxy Server entities.
jnxSipCommonCfgTimerEntry	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1		not-accessible	A row of timer configuration. Each row represents those objects for a particular SIP entity present in this system.
STR jnxSipCfgTimerApplName	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.1	DisplayString	not-accessible	The name of the network application which uniquely identifies the application to which this entry is applicable.
U32 jnxSipCommonCfgTimerA	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.2	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerB	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.3	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerC	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.4	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerD	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.5	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerE	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.6	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerF	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.7	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerG	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.8	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerH	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.9	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerI	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.10	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerJ	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.11	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerK	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.12	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerT1	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.13	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerT2	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.14	Unsigned32	read-only	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.
U32 jnxSipCommonCfgTimerT4	1.3.6.1.4.1.2636.3.39.1.15.2.1.1.5.1.15	Unsigned32	read-only	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.

RFC description

Manages common Session Initiation Protocol (SIP) configuration and status across Juniper Networks VoIP entities.

Start monitoring Juniper Networks mobile/session gateway (SIP entity common objects) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download JUNIPER-SIP-COMMON-MIB