All MIBs › TELDAT-MON-PROTOCOL-SIP-MIB
Organization: Teldat, S.A.
Last Updated: 2006-05-18
Category: Teldat Router Management, VoIP and Telephony
Description: Monitors Teldat router SIP protocol registration state, active dialog counts, and VoIP call signaling statistics.
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 TELDAT-MON-PROTOCOL-SIP-MIB?
TELDAT-MON-PROTOCOL-SIP-MIB is a Teldat proprietary MIB module for monitoring the Session Initiation Protocol (SIP) signaling stack on Teldat routers and VoIP gateways, covering call setup and registration for voice-over-IP services. It exposes data on active SIP proxy status, locally registered peers and phones, and detailed transaction statistics such as requests/responses parsed and sent, plus API invocation counts. This is squarely a performance-and-fault monitoring MIB: it lets an operator confirm the SIP process/service is running (active proxy), track registration health (peers/phones registered), and detect protocol-level problems via memory and network error counters, which reflect software-level health of the VoIP signaling stack. It appears largely self-contained around Teldat's own SIP implementation, with only conceptual (not object-level) ties to the IETF SIP specification (RFC 3261). It is deployed on Teldat routers and VoIP gateways used for enterprise or carrier voice signaling. Engineers can download the TELDAT-MON-PROTOCOL-SIP-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-MON-PROTOCOL-SIP-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
- Teldat routers and VoIP gateways
Monitoring Examples
An administrator would poll teldatSipActiveProxy to confirm the SIP proxy service is up, and walk teldatSipLocPeerRegTable/teldatSipLocPeerRegEntry (indexed by teldatSipLocPeerRegIndex, with teldatSipLocPeerRegUser, teldatSipLocPeerRegLocation, teldatSipLocPeerRegExpiration) to verify which SIP peers are currently registered and when their registrations expire. Similarly, teldatSipPhoneLocRegTable would show which local phones are registered. A sudden drop in registered peer/phone counts, or rising counters under teldatSipTransStatsObject for memory or network errors, would indicate a SIP registration or signaling failure needing investigation.
What Can Be Monitored
- active SIP proxy status
- locally registered SIP peers
- locally registered phones and expiration times
- SIP transaction statistics (requests/responses parsed and sent)
- SIP memory errors
- SIP network errors
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| DisplayString | |
| TEXTUAL-CONVENTION |
| telProdNpMonProtocols | OBJECT-IDENTITY |
OIDs
RFC description
Teldat MIB for Session Initiation Protocol (SIP) monitoring, tracking VoIP call signaling statistics, transactions, and user agent metrics.
Start monitoring Teldat routers and VoIP gateways (SIP proxy/registration/transaction 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.