Home/Catalog/SIP-MIB

SIP-MIB

AI MIB Summary

The SIP-MIB module is intended for monitoring and managing Session Initiation Protocol (SIP) entities, specifically tracking call session states, registration status, and signaling traffic metrics. Although the provided description erroneously references SMDS interfaces, the standard SIP-MIB definition (RFC 3398) exclusively governs SIP-specific objects such as dialog counts, method invocations, and error counters for SIP proxies, user agents, and gateways.

The MIB module to describe SMDS interfaces objects.
Main OID:
sipMIB.1.3.6.1.2.1.36
69
Objects
Active
Status
4
Dependencies

Imported Objects

Objects

69 total
Object Name
sip
OBJECT IDENTIFIER
.1.3.6.1.2.1.10.31
sipL3TableThis table contains SIP L3 parameters and state variables, one entry per SIPL3 interface.
SEQUENCE OF SipL3Entry
.1.3.6.1.2.1.10.31.1
sipL3EntryThis list contains SIP L3 parameters and state variables.
SipL3Entry
.1.3.6.1.2.1.10.31.1.1
sipL3IndexThe value of this object identifies the SIP L3 interface for which this entry contains management information.ro
IfIndex
.1.3.6.1.2.1.10.31.1.1.1
sipL3ReceivedIndividualDAsThe total number of individually addressed SIP Level 3 PDUs received from the remote system across the SNI. The total includes only unerrored L3PDUs.rodeprecated
Counter32
.1.3.6.1.2.1.10.31.1.1.2
sipL3ReceivedGAsThe total number of group addressed SIP Level 3 PDUs received from the remote system across the SNI. The total includes only unerrored L3PDUs.rodeprecated
Counter32
.1.3.6.1.2.1.10.31.1.1.3
sipL3UnrecognizedIndividualDAsThe number of SIP Level 3 PDUs received from the remote system with invalid or unknown individual destination addresses (Destination Address Screening violations are not included). See SMDS Subscription MIB module.rodeprecated
Counter32
.1.3.6.1.2.1.10.31.1.1.4
sipL3UnrecognizedGAsThe number of SIP Level 3 PDUs received from the remote system with invalid or unknown group addresses. (Destination Address Screening violations are not included). See SMDS Subscription MIB module.rodeprecated
Counter32
.1.3.6.1.2.1.10.31.1.1.5
sipL3SentIndividualDAsThe number of individually addressed SIP Level 3 PDUs that have been sent by this system across the SNI.rodeprecated
Counter32
.1.3.6.1.2.1.10.31.1.1.6
sipL3SentGAsThe number of group addressed SIP L3PDUs that have been sent by this system across the SNI.rodeprecated
Counter32
.1.3.6.1.2.1.10.31.1.1.7
sipL3ErrorsThe total number of SIP Level 3 PDUs received from the remote system that were discovered to have errors (including protocol processing and bit errors but excluding addressing-related errors) and were discarded. Includes both group addressed L3PDUs and L3PDUs containing an individual destination address.rodeprecated
Counter32
.1.3.6.1.2.1.10.31.1.1.8
sipL3InvalidSMDSAddressTypesThe number of SIP Level 3 PDUs received from the remote system that had the Source or Destination Address_Type subfields, (the four most significant bits of the 64 bit address field), not equal to the value 1100 or 1110. Also, an error is considered to have occurred if the Address_Type field for a Source Address, the four most significant bits of the 64 bits, is equal to 1110 (a group address).rodeprecated
Counter32
.1.3.6.1.2.1.10.31.1.1.9
sipL3VersionSupportA value which indicates the version(s) of SIP that this interface supports. The value is a sum. This sum initially takes the value zero. For each version, V, that this interface supports, 2 raised to (V - 1) is added to the sum. For example, a port supporting versions 1 and 2 would have a value of (2^(1-1)+2^(2-1))=3. The sipL3VersionSupport is effectively a bit mask with Version 1 equal to the least significant bit (LSB).ro
Integer32
.1.3.6.1.2.1.10.31.1.1.10
sipL2TableThis table contains SIP L2PDU parameters and state variables, one entry per SIP L2 interface.
SEQUENCE OF SipL2Entry
.1.3.6.1.2.1.10.31.2
sipL2EntryThis list contains SIP L2 parameters and state variables.
SipL2Entry
.1.3.6.1.2.1.10.31.2.1
sipL2IndexThe value of this object identifies the SIP interface for which this entry contains management information.ro
IfIndex
.1.3.6.1.2.1.10.31.2.1.1
sipL2ReceivedCountsThe number of SIP Level 2 PDUs received from the remote system across the SNI. The total includes only unerrored L2PDUs.ro
Counter32
.1.3.6.1.2.1.10.31.2.1.2
sipL2SentCountsThe number of SIP Level 2 PDUs that have been sent by this system across the SNI.ro
Counter32
.1.3.6.1.2.1.10.31.2.1.3
sipL2HcsOrCRCErrorsThe number of received SIP Level 2 PDUs that were discovered to have either a Header Check Sequence error or a Payload CRC violation.ro
Counter32
.1.3.6.1.2.1.10.31.2.1.4
sipL2PayloadLengthErrorsThe number of received SIP Level 2 PDUs that had Payload Length errors that fall in the following specifications: - SSM L2_PDU payload length field value less - than 28 octets or greater than 44 octets, - BOM or COM L2_PDU payload length field not - equal to 44 octets, - EOM L2_PDU payload length field value less - than 4 octets or greater than 44 octets.ro
Counter32
.1.3.6.1.2.1.10.31.2.1.5
sipL2SequenceNumberErrorsThe number of received SIP Level 2 PDUs that had a sequence number within the L2PDU not equal to the expected sequence number of the SMDS SS receive process.ro
Counter32
.1.3.6.1.2.1.10.31.2.1.6
sipL2MidCurrentlyActiveErrorsThe number of received SIP Level 2 PDUs that are BOMs for which an active receive process is already started.ro
Counter32
.1.3.6.1.2.1.10.31.2.1.7
sipL2BomOrSSMsMIDErrorsThe number of received SIP Level 2 PDUs that are SSMs with a MID not equal to zero or are BOMs with MIDs equal to zero.ro
Counter32
.1.3.6.1.2.1.10.31.2.1.8
sipL2EomsMIDErrorsThe number of received SIP Level 2 PDUs that are EOMs for which there is no active receive process for the MID (i.e., the receipt of an EOM which does not correspond to a BOM) OR the EOM has a MID equal to zero.ro
Counter32
.1.3.6.1.2.1.10.31.2.1.9
sipPLCP
OBJECT IDENTIFIER
.1.3.6.1.2.1.10.31.3
sipDS1PLCPTableThis table contains SIP DS1 PLCP parameters and state variables, one entry per SIP port.
SEQUENCE OF SipDS1PLCPEntry
.1.3.6.1.2.1.10.31.3.1
sipDS1PLCPEntryThis list contains SIP DS1 PLCP parameters and state variables.
SipDS1PLCPEntry
.1.3.6.1.2.1.10.31.3.1.1
sipDS1PLCPIndexThe value of this object identifies the interface for which this entry contains management information.ro
IfIndex
.1.3.6.1.2.1.10.31.3.1.1.1
sipDS1PLCPSEFSsA DS1 Severely Errored Framing Second (SEFS) is a count of one-second intervals containing one or more SEF events. A Severely Errored Framing (SEF) event is declared when an error in the A1 octet and an error in the A2 octet of a framing octet pair (i.e., errors in both framing octets), or two consecutive invalid and/or nonsequential Path Overhead Identifier octets are detected.ro
Counter32
.1.3.6.1.2.1.10.31.3.1.1.2
sipDS1PLCPAlarmStateThis variable indicates if there is an alarm present for the DS1 PLCP. The value receivedFarEndAlarm means that the DS1 PLCP has received an incoming Yellow Signal, the value incomingLOF means that the DS1 PLCP has declared a loss of frame (LOF) failure condition, and the value noAlarm means that there are no alarms present. See TR-TSV-000773 for a description of alarm states.ro
Enumeration
.1.3.6.1.2.1.10.31.3.1.1.3
sipDS1PLCPUASsThe counter associated with the number of Unavailable Seconds, as defined by TR-TSV-000773, encountered by the PLCP.ro
Counter32
.1.3.6.1.2.1.10.31.3.1.1.4
sipDS3PLCPTableThis table contains SIP DS3 PLCP parameters and state variables, one entry per SIP port.
SEQUENCE OF SipDS3PLCPEntry
.1.3.6.1.2.1.10.31.3.2
sipDS3PLCPEntryThis list contains SIP DS3 PLCP parameters and state variables.
SipDS3PLCPEntry
.1.3.6.1.2.1.10.31.3.2.1
sipDS3PLCPIndexThe value of this object identifies the interface for which this entry contains management information.ro
IfIndex
.1.3.6.1.2.1.10.31.3.2.1.1
sipDS3PLCPSEFSsA DS3 Severely Errored Framing Second (SEFS) is a count of one-second intervals containing one or more SEF events. A Severely Errored Framing (SEF) event is declared when an error in the A1 octet and an error in the A2 octet of a framing octet pair (i.e., errors in both framing octets), or two consecutive invalid and/or nonsequential Path Overhead Identifier octets are detected.ro
Counter32
.1.3.6.1.2.1.10.31.3.2.1.2
sipDS3PLCPAlarmStateThis variable indicates if there is an alarm present for the DS3 PLCP. The value receivedFarEndAlarm means that the DS3 PLCP has received an incoming Yellow Signal, the value incomingLOF means that the DS3 PLCP has declared a loss of frame (LOF) failure condition, and the value noAlarm means that there are no alarms present. See TR-TSV-000773 for a description of alarm states.ro
Enumeration
.1.3.6.1.2.1.10.31.3.2.1.3
sipDS3PLCPUASsThe counter associated with the number of Unavailable Seconds, as defined by TR-TSV-000773, encountered by the PLCP.ro
Counter32
.1.3.6.1.2.1.10.31.3.2.1.4
smdsApplications
OBJECT IDENTIFIER
.1.3.6.1.2.1.10.31.4
ipOverSMDS
OBJECT IDENTIFIER
.1.3.6.1.2.1.10.31.4.1
ipOverSMDSTableThe table of addressing information relevant to this entity's IP addresses.
SEQUENCE OF IpOverSMDSEntry
.1.3.6.1.2.1.10.31.4.1.1
ipOverSMDSEntryThe addressing information for one of this entity's IP addresses.
IpOverSMDSEntry
.1.3.6.1.2.1.10.31.4.1.1.1
ipOverSMDSIndexThe value of this object identifies the interface for which this entry contains management information.ro
IfIndex
.1.3.6.1.2.1.10.31.4.1.1.1.1
ipOverSMDSAddressThe IP address to which this entry's addressing information pertains.ro
IpAddress
.1.3.6.1.2.1.10.31.4.1.1.1.2
ipOverSMDSHAThe SMDS Individual address of the IP station.ro
SMDSAddress
.1.3.6.1.2.1.10.31.4.1.1.1.3
ipOverSMDSLISGAThe SMDS Group Address that has been configured to identify the SMDS Subscriber-Network Interfaces (SNIs) of all members of the Logical IP Subnetwork (LIS) connected to the network supporting SMDS.ro
SMDSAddress
.1.3.6.1.2.1.10.31.4.1.1.1.4
ipOverSMDSARPReqThe SMDS address (individual or group) to which ARP Requests are to be sent.ro
SMDSAddress
.1.3.6.1.2.1.10.31.4.1.1.1.5
smdsCarrierSelection
OBJECT IDENTIFIER
.1.3.6.1.2.1.10.31.5
sipErrorLog
OBJECT IDENTIFIER
.1.3.6.1.2.1.10.31.6
sipL3PDUErrorTableA table that contains the latest occurrence of the following syntactical SIP L3PDU errors: - Destination Address Field Format Error, The following pertains to the 60 least significant bits of the 64 bit address field. The 60 bits contained in the address subfield can be used to represent addresses up to 15 decimal digits. Each decimal digit shall be encoded into four bits using Binary Coded Decimal (BCD), with the most significant digit occurring left-most. If not all 15 digits are required, then the remainder of this field shall be padded on the right with bits set to one. An error is considered to have occurred: a). if the first four bits of the address subfield are not BCD, OR b). if the first four bits of the address subfield are populated with the country code value 0001, AND the 40 bits which follow are not Binary Coded Decimal (BCD) encoded values of the 10 digit addresses, OR the remaining 16 least significant bits are not populated with 1's, OR c). if the address subfield is not correct according to another numbering plan which is dependent upon the carrier assigning the numbers and offering SMDS. - Source Address Field Format Error, The description of this parameter is the same as the description of the Destination Address Field Format Error. - Invalid BAsize Field Value, An error is considered to have occurred when the BAsize field of an SIP L3PDU contains a value less that 32, greater than 9220 octets without the CRC32 field present, greater than 9224 octets with the CRC32 field present, or not equal to a multiple of 4 octets, - Invalid Header Extension Length Field Value, An error is considered to have occurred when the Header Extension Length field value is not equal 3. - Invalid Header Extension - Element Length, An error is considered to have occurred when the Header Extension - Element Length is greater than 12. - Invalid Header Extension - Version Element Position, Length, or Value, An error is considered to have occurred when a Version element with Length=3, Type=0, and Value=1 does not appear first within the Header Extension, or an element Type=0 appears somewhere other than within the first three octets in the Header Extension. - Invalid Header Extension - Carrier Selection Element Position, Length, Value or Format, An error is considered to have occurred when a Carrier Selection element does not appear second within the Header Extension, if the Element Type does not equal 1, the Element Length does not equal 4, 6, or 8, the Element Value field is not four BCD encoded decimal digits used in specifying the Carrier Identification Code (CIC), or the identified CIC code is invalid. - Header Extension PAD Error An error is considered to have occurred when the Header Extension PAD is 9 octets in length, or if the Header Extension PAD is greater than zero octets in length and the Header Extension PAD does not follow all Header Extension elements or does not begin with at least one octet of all zeros. - BEtag Mismatch Error, An error is considered to have occurred when the Beginning-End Tags in the SIP L3PDU header and trailer are not equal. - BAsize Field not equal to Length Field Error, An error is considered to have occurred when the value of the BAsize Field does not equal the value of the Length Field. - Incorrect Length Error, and An error is considered to have occurred when the the Length field value is not equal to the portion of the SIP L3PDU which extends from the Destination Address field up to and including the CRC32 field (if present) or up to and including the PAD field (if the CRC32 field is not present). As an optional check, an error is considered to have occurred when the length of a partially received SIP L3PDU exceeds the BAsize value. - MRI Timeout Error. An error is considered to have occurred when the elapsed time between receipt of BOM and corresponding EOM exceeds the value of the MRI (Message Receive Interval) for a particular transport signal format. An entry is indexed by interface number and error type, and contains Source Address, Destination Address and a timestamp. All these errors are counted in the sipL3Errors counter. When sipL3PDUErrorTimeStamp is equal to zero, the SipL3PDUErrorEntry does not contain any valid information.
SEQUENCE OF SipL3PDUErrorEntry
.1.3.6.1.2.1.10.31.6.1
sipL3PDUErrorEntryAn entry in the service disagreement table.
SipL3PDUErrorEntry
.1.3.6.1.2.1.10.31.6.1.1
sipL3PDUErrorIndexThe value of this object identifies the interface for which this entry contains management information.ro
IfIndex
.1.3.6.1.2.1.10.31.6.1.1.1
sipL3PDUErrorTypeThe type of error.ro
Enumeration
.1.3.6.1.2.1.10.31.6.1.1.2
sipL3PDUErrorSAA rejected SMDS source address.ro
SMDSAddress
.1.3.6.1.2.1.10.31.6.1.1.3
sipL3PDUErrorDAA rejected SMDS destination address.ro
SMDSAddress
.1.3.6.1.2.1.10.31.6.1.1.4
sipL3PDUErrorTimeStampThe timestamp for the service disagreement. The timestamp contains the value of sysUpTime at the latest occurrence of this type of service disagreement. See textual description under sipL3PDUErrorTable for boundary conditions.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.2.1.10.31.6.1.1.5
sipMIBThe MIB module to describe SMDS interfaces objects.
MODULE-IDENTITY
.1.3.6.1.2.1.36
sipMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.2.1.36.1
sipDxiTableThe DXI table.
SEQUENCE OF SipDxiEntry
.1.3.6.1.2.1.36.1.1
sipDxiEntryAn entry in the DXI table.
SipDxiEntry
.1.3.6.1.2.1.36.1.1.1
sipDxiCrcThe value of this object indicates the type of Frame Checksum used by DXI. Current choices include CCITT CRC16 or CRC32.ro
Enumeration
.1.3.6.1.2.1.36.1.1.1.1
sipDxiOutDiscardsThe number of outbound frames discarded because of congestion.ro
Counter32
.1.3.6.1.2.1.36.1.1.1.2
sipDxiInErrorsThe number of inbound frames discarded because of errors such as frame checksum (CRC) violations, non-integral number of octets, address and control field violations, and frame size errors.ro
Counter32
.1.3.6.1.2.1.36.1.1.1.3
sipDxiInAbortsThe number of inbound frames discarded because of an abort bit sequence (1111111) received before closing flag.ro
Counter32
.1.3.6.1.2.1.36.1.1.1.4
sipDxiInTestFramesThe number of unerrored, inbound Test frames received (generally as part of Heart Beat Poll procedure).ro
Counter32
.1.3.6.1.2.1.36.1.1.1.5
sipDxiOutTestFramesThe number of unerrored, outbound Test frames sent (generally as part of Heart Beat Poll procedure).ro
Counter32
.1.3.6.1.2.1.36.1.1.1.6
sipDxiHbpNoAcksThe number of Heart Beat Poll (HBP) No Ack timeouts.ro
Counter32
.1.3.6.1.2.1.36.1.1.1.7
smdsConformance
OBJECT IDENTIFIER
.1.3.6.1.2.1.36.2
smdsGroups
OBJECT IDENTIFIER
.1.3.6.1.2.1.36.2.1
smdsCompliances
OBJECT IDENTIFIER
.1.3.6.1.2.1.36.2.2
SIP-MIB - SNMP MIB Reference | MIBs Explorer