TELDAT-TRAP-NOE-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TELDAT-TRAP-NOE-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

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

Description: Defines Teldat router NOE (Alcatel 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-NOE-MIB?

TELDAT-TRAP-NOE-MIB is a Teldat proprietary, notification-only SNMP MIB that defines the trap varbinds emitted by the router's NOE (Alcatel New Office Environment, an Alcatel-Lucent proprietary VoIP signaling protocol) event subsystem, relevant when a Teldat device interoperates with Alcatel voice infrastructure. It groups numbered event definitions (noe1 through noe6, under noeEventsGroup/noeNotifications) carrying error/warning/info/event strings, a connection identifier, connection state, and, for one event type, expected versus sent sequence numbers. Operationally it is a fault/event monitor for the NOE VoIP signaling path: it lets a management station learn asynchronously about per-connection errors, warnings, or state changes, and specifically about sequence-number mismatches (noe6-expected-seq vs noe6-sent-seq) that indicate signaling desynchronization likely to disrupt call setup or maintenance. As with Teldat's other TRAP-* modules it depends on the standard SNMPv2-SMI/SNMPv2-TC notification conventions and Teldat's private enterprise OID tree, layered on top of the proprietary Alcatel NOE protocol it interoperates with. It is deployed on Teldat routers acting as gateways into Alcatel-based enterprise telephony deployments, where TELDAT-TRAP-NOE-MIB SNMP monitoring alerts operators to NOE signaling errors and sequence mismatches in real time.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-NOE-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 router
  • Teldat gateway to Alcatel VoIP infrastructure

Monitoring Examples

This module defines only notification objects and their varbinds rather than a polled call-state table, so there is no GET-based monitoring scenario; it is trap-only. An SNMP trap receiver would inspect noe4-event/noe4-description together with noe4-connetion-id to identify what happened on a specific NOE connection, and compare noe6-expected-seq against noe6-sent-seq to detect a sequence-number mismatch signaling desynchronization on that connection.

What Can Be Monitored

  • NOE connection error/warning/info events
  • NOE connection state changes
  • NOE sequence-number mismatch events
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

Manages SNMP notifications generated by the NOE event subsystem on Teldat devices.

Start monitoring Teldat gateway to Alcatel VoIP infrastructure (NOE signaling error/sequence-mismatch 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-NOE-MIB