SIP-DS2-MIB

AI MIB Summary

The SIP-DS2-MIB module facilitates the monitoring and management of Session Initiation Protocol (SIP) entities, specifically tracking DS2 (Digital Signal 2) interface statistics and SIP session states for telecommunications infrastructure. It provides granular visibility into call setup failures, trunk utilization, and protocol-level error counters essential for maintaining VoIP service reliability.

The MIB module for entities implementing the xxxx protocol.

Main OID:

sipDS2.1.3.6.1.4.1.1751.1.1198.5.2

Objects

Active

Status

Dependencies

Imported Objects

Objects

15 total

Object Name	Syntax	OID
lucent OBJECT IDENTIFIER `.1.3.6.1.4.1.1751`	OBJECT IDENTIFIER	`.1.3.6.1.4.1.1751`
RFC1155-SMI Unknown `.1.3.6.1.4.1.1751`	Unknown	`.1.3.6.1.4.1.1751`
products OBJECT IDENTIFIER `.1.3.6.1.4.1.1751.1`	OBJECT IDENTIFIER	`.1.3.6.1.4.1.1751.1`
softSwitch OBJECT IDENTIFIER `.1.3.6.1.4.1.1751.1.1198`	OBJECT IDENTIFIER	`.1.3.6.1.4.1.1751.1.1198`
sipDeviceServer OBJECT IDENTIFIER `.1.3.6.1.4.1.1751.1.1198.5`	OBJECT IDENTIFIER	`.1.3.6.1.4.1.1751.1.1198.5`
sipDS2The MIB module for entities implementing the xxxx protocol. MODULE-IDENTITY `.1.3.6.1.4.1.1751.1.1198.5.2`	MODULE-IDENTITY	`.1.3.6.1.4.1.1751.1.1198.5.2`
sipSystem OBJECT IDENTIFIER `.1.3.6.1.4.1.1751.1.1198.5.2.1`	OBJECT IDENTIFIER	`.1.3.6.1.4.1.1751.1.1198.5.2.1`
dsInfoDevice Server information. This value should include the full name and version identification and/or manufacturer information. It is mandatory that this contains only printable ASCII charactersro DisplayString `.1.3.6.1.4.1.1751.1.1198.5.2.1.1`	DisplayString	`.1.3.6.1.4.1.1751.1.1198.5.2.1.1`
dsProtocolInfoDevice Server H323/SIP stack information. This value should include the full name and version identification and/or manufacturer information of the H323/SIP Stack used in the device server implementation. It is mandatory that this contains only printable ASCII charactersro DisplayString `.1.3.6.1.4.1.1751.1.1198.5.2.1.2`	DisplayString	`.1.3.6.1.4.1.1751.1.1198.5.2.1.2`
logLevelDevice Server Log Level. A minimum logging level is always set for the device servers, which logs errors and warnings. If still more verbosity is required, that can be done by setting this parameter to a required level. 1. Error 2. Warning 3. Inforw INTEGER ( 1..3 ) `.1.3.6.1.4.1.1751.1.1198.5.2.1.3`	INTEGER ( 1..3 )	`.1.3.6.1.4.1.1751.1.1198.5.2.1.3`
succeededCallsTotal number of calls successfully made since the last uptime of this device server.ro INTEGER ( 0..65535 ) `.1.3.6.1.4.1.1751.1.1198.5.2.1.4`	INTEGER ( 0..65535 )	`.1.3.6.1.4.1.1751.1.1198.5.2.1.4`
activeCallsNumber of calls which are still progressing at this time by this device serverro INTEGER ( 0..65535 ) `.1.3.6.1.4.1.1751.1.1198.5.2.1.5`	INTEGER ( 0..65535 )	`.1.3.6.1.4.1.1751.1.1198.5.2.1.5`
failedCallsTotal Number of calls failed since the last uptime of this device serverro INTEGER ( 0..65535 ) `.1.3.6.1.4.1.1751.1.1198.5.2.1.6`	INTEGER ( 0..65535 )	`.1.3.6.1.4.1.1751.1.1198.5.2.1.6`
reloadConfigThis is to tell the device server to load it's configuration again. This is done when some configuration parameters need to be updated in the systemrw INTEGER ( 0..1 ) `.1.3.6.1.4.1.1751.1.1198.5.2.1.7`	INTEGER ( 0..1 )	`.1.3.6.1.4.1.1751.1.1198.5.2.1.7`
resetLogTo discard previous log and to start logging afresh resetLog would be usedrw INTEGER ( 0..1 ) `.1.3.6.1.4.1.1751.1.1198.5.2.1.8`	INTEGER ( 0..1 )	`.1.3.6.1.4.1.1751.1.1198.5.2.1.8`