TELDAT-TRAP-VOIP-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TELDAT-TRAP-VOIP-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications, VoIP and Telephony

Description: Defines Teldat router VoIP event trap notifications.

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-TRAP-VOIP-MIB?

TELDAT-TRAP-VOIP-MIB is a Teldat router MIB that defines SNMP trap notifications generated by the VoIP event subsystem on Teldat routers. It exposes purely event/fault data -- a series of VoIP-related trap definitions (numbered voip1 through voip5-style events) carrying details like text description, associated interface, line, event type, and reason code -- rather than polled performance counters. Its monitoring value is entirely fault/event-oriented: it lets an NMS receive real-time alerts about VoIP subsystem conditions such as call failures, interface issues, or line-level problems, functioning as a software/service-status alerting mechanism for the router's embedded VoIP functionality. It depends on the underlying Teldat VoIP subsystem and the SNMPv2 notification framework rather than external IETF VoIP MIBs. It is typically deployed on Teldat routers with integrated VoIP gateway capability, where operators want proactive alerting on voice service issues. Network engineers evaluating or troubleshooting this functionality can download the TELDAT-TRAP-VOIP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-VOIP-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 with integrated VoIP gateway functionality

Monitoring Examples

An NMS would subscribe to voipNotifications to catch events such as those carrying voip3-Event and voip3-parameter on a given voip3-interface and voip3-line, or voip5-Type/voip5-Reason codes, to determine why a VoIP call or line failed. The voip1-text and voip2-text objects would supply human-readable descriptions accompanying simpler trap variants, letting an operator quickly understand a VoIP fault (e.g., line down, codec negotiation failure) without needing to correlate raw codes manually.

What Can Be Monitored

  • VoIP event traps by interface/line
  • VoIP event type and reason codes
  • VoIP fault descriptive text
Imported Objects

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

From TELDAT-MIB

telEventTrapsOBJECT-IDENTITY
OIDs

RFC description

Teldat VoIP event notifications and traps for voice over IP system monitoring.

Start monitoring Teldat routers with integrated VoIP gateway functionality (call/line-level event traps) 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 TELDAT-TRAP-VOIP-MIB