TELDAT-TRAP-R2-MIB

All MIBs › TELDAT-TRAP-R2-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Remote Access and Serial WAN, Teldat Router Management, Teldat Trap Notifications, VoIP and Telephony

Description: Defines Teldat router R2 (R2 signaling) 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-R2-MIB?

The TELDAT-TRAP-R2-MIB is a vendor-specific SNMP notification module for Teldat routers' R2 channel-associated signaling subsystem, used on E1/T1 telephony trunks employing the R2 signaling standard. It exposes per-event objects for the signaling message/command, the interface, and the specific channel (timeslot) involved. Its monitoring purpose is tracking the software/protocol status of R2 signaling on voice trunks — surfacing signaling messages, commands, and events per channel — essential for diagnosing call setup or signaling failures on E1 voice gateways. It relates conceptually to standard telephony signaling MIBs but is implemented as Teldat's own enterprise event set. It is deployed on Teldat routers/gateways carrying E1 R2-signaled voice trunks, typically in legacy PSTN interconnection scenarios. Engineers can download the TELDAT-TRAP-R2-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-R2-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/gateway (E1 R2 signaling voice trunk)

Monitoring Examples

A trap with r22_message, r22_interface, and r22_channel identifies exactly which signaling message occurred on which E1 channel/timeslot of a given interface, useful for tracing a failed call setup back to a specific R2 signaling exchange. r24_command together with r24_interface and r24_channel shows a signaling command issued on a particular channel, letting an operator correlate signaling anomalies with specific voice circuits.

What Can Be Monitored

R2 signaling message/event
signaling command
affected interface
affected channel/timeslot

Imported Objects

From SNMPv2-SMI

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

From SNMPv2-TC

DisplayString

From TELDAT-MIB

telEventTraps

OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
r2TrapsMIB	1.3.6.1.4.1.2007.1.4.100			This Module Information Base file is defined for managing received SNMP notifications generated by the R2 event subsystem.
r2EventsGroup	1.3.6.1.4.1.2007.1.4.100.1
r2EventObjects1	1.3.6.1.4.1.2007.1.4.100.1.1			Event R2.1 Message generated for each event received on the state machine that shows the effect produced.
STR r21Event	1.3.6.1.4.1.2007.1.4.100.1.1.1	DisplayString	accessible-for-notify	Parameter 'event' in event R2.1
STR r21Interface	1.3.6.1.4.1.2007.1.4.100.1.1.2	DisplayString	accessible-for-notify	Parameter 'interface' in event R2.1
I32 r21Channel	1.3.6.1.4.1.2007.1.4.100.1.1.3	Integer32	accessible-for-notify	Parameter 'channel' in event R2.1
r2EventObjects2	1.3.6.1.4.1.2007.1.4.100.1.2			Event R2.2 Message generated for each change on multiframe alignment detection.
STR r22Message	1.3.6.1.4.1.2007.1.4.100.1.2.1	DisplayString	accessible-for-notify	Parameter 'message' in event R2.2
STR r22Interface	1.3.6.1.4.1.2007.1.4.100.1.2.2	DisplayString	accessible-for-notify	Parameter 'interface' in event R2.2
I32 r22Channel	1.3.6.1.4.1.2007.1.4.100.1.2.3	Integer32	accessible-for-notify	Parameter 'channel' in event R2.2
r2EventObjects3	1.3.6.1.4.1.2007.1.4.100.1.3			Event R2.3 Message generated for each change on the alarm bit.
STR r23Message	1.3.6.1.4.1.2007.1.4.100.1.3.1	DisplayString	accessible-for-notify	Parameter 'message' in event R2.3
STR r23Interface	1.3.6.1.4.1.2007.1.4.100.1.3.2	DisplayString	accessible-for-notify	Parameter 'interface' in event R2.3
I32 r23Channel	1.3.6.1.4.1.2007.1.4.100.1.3.3	Integer32	accessible-for-notify	Parameter 'channel' in event R2.3
r2EventObjects4	1.3.6.1.4.1.2007.1.4.100.1.4			Event R2.4 Command sent to the r2 api
STR r24Command	1.3.6.1.4.1.2007.1.4.100.1.4.1	DisplayString	accessible-for-notify	Parameter 'command' in event R2.4
STR r24Interface	1.3.6.1.4.1.2007.1.4.100.1.4.2	DisplayString	accessible-for-notify	Parameter 'interface' in event R2.4
I32 r24Channel	1.3.6.1.4.1.2007.1.4.100.1.4.3	Integer32	accessible-for-notify	Parameter 'channel' in event R2.4
r2EventObjects5	1.3.6.1.4.1.2007.1.4.100.1.5			Event R2.5 Error in r2 channel
STR r25Error	1.3.6.1.4.1.2007.1.4.100.1.5.1	DisplayString	accessible-for-notify	Parameter 'error' in event R2.5
STR r25Context	1.3.6.1.4.1.2007.1.4.100.1.5.2	DisplayString	accessible-for-notify	Parameter 'context' in event R2.5
STR r25Interface	1.3.6.1.4.1.2007.1.4.100.1.5.3	DisplayString	accessible-for-notify	Parameter 'interface' in event R2.5
I32 r25Channel	1.3.6.1.4.1.2007.1.4.100.1.5.4	Integer32	accessible-for-notify	Parameter 'channel' in event R2.5
r2EventObjects6	1.3.6.1.4.1.2007.1.4.100.1.6			Event R2.6 Phase changed in mfc r2 protocol
STR r26OldState	1.3.6.1.4.1.2007.1.4.100.1.6.1	DisplayString	accessible-for-notify	Parameter 'oldState' in event R2.6
STR r26NewState	1.3.6.1.4.1.2007.1.4.100.1.6.2	DisplayString	accessible-for-notify	Parameter 'newState' in event R2.6
STR r26Interface	1.3.6.1.4.1.2007.1.4.100.1.6.3	DisplayString	accessible-for-notify	Parameter 'interface' in event R2.6
I32 r26Channel	1.3.6.1.4.1.2007.1.4.100.1.6.4	Integer32	accessible-for-notify	Parameter 'channel' in event R2.6
r2EventObjects7	1.3.6.1.4.1.2007.1.4.100.1.7			Event R2.7 Phase changed in mfc r2 protocol
STR r27OldState	1.3.6.1.4.1.2007.1.4.100.1.7.1	DisplayString	accessible-for-notify	Parameter 'oldState' in event R2.7
STR r27NewState	1.3.6.1.4.1.2007.1.4.100.1.7.2	DisplayString	accessible-for-notify	Parameter 'newState' in event R2.7
STR r27Interface	1.3.6.1.4.1.2007.1.4.100.1.7.3	DisplayString	accessible-for-notify	Parameter 'interface' in event R2.7
I32 r27Channel	1.3.6.1.4.1.2007.1.4.100.1.7.4	Integer32	accessible-for-notify	Parameter 'channel' in event R2.7
r2EventObjects8	1.3.6.1.4.1.2007.1.4.100.1.8			Event R2.8 MFC signal sent or received
I32 r28Signal	1.3.6.1.4.1.2007.1.4.100.1.8.1	Integer32	accessible-for-notify	Parameter 'signal' in event R2.8
STR r28Received	1.3.6.1.4.1.2007.1.4.100.1.8.2	DisplayString	accessible-for-notify	Parameter 'received' in event R2.8
STR r28Interface	1.3.6.1.4.1.2007.1.4.100.1.8.3	DisplayString	accessible-for-notify	Parameter 'interface' in event R2.8
I32 r28Channel	1.3.6.1.4.1.2007.1.4.100.1.8.4	Integer32	accessible-for-notify	Parameter 'channel' in event R2.8
r2EventObjects9	1.3.6.1.4.1.2007.1.4.100.1.9			Event R2.9 MFC signal sent or received
STR r29Received	1.3.6.1.4.1.2007.1.4.100.1.9.1	DisplayString	accessible-for-notify	Parameter 'received' in event R2.9
STR r29A	1.3.6.1.4.1.2007.1.4.100.1.9.2	DisplayString	accessible-for-notify	Parameter 'a' in event R2.9
STR r29B	1.3.6.1.4.1.2007.1.4.100.1.9.3	DisplayString	accessible-for-notify	Parameter 'b' in event R2.9
STR r29C	1.3.6.1.4.1.2007.1.4.100.1.9.4	DisplayString	accessible-for-notify	Parameter 'c' in event R2.9
STR r29D	1.3.6.1.4.1.2007.1.4.100.1.9.5	DisplayString	accessible-for-notify	Parameter 'd' in event R2.9
STR r29Interface	1.3.6.1.4.1.2007.1.4.100.1.9.6	DisplayString	accessible-for-notify	Parameter 'interface' in event R2.9
I32 r29Channel	1.3.6.1.4.1.2007.1.4.100.1.9.7	Integer32	accessible-for-notify	Parameter 'channel' in event R2.9
r2Notifications	1.3.6.1.4.1.2007.1.4.100.2
r2NotificationsPrefix	1.3.6.1.4.1.2007.1.4.100.2.0
NTF r2Notification1	1.3.6.1.4.1.2007.1.4.100.2.0.1			Notification of Event R2.1 Message: 'Event received on state machine: $1 on $2$3' Parameters list: $1: r21Event $2: r21Interface $3: r21Channel Message generated for each event received on the state machine that shows the effect produced.
NTF r2Notification2	1.3.6.1.4.1.2007.1.4.100.2.0.2			Notification of Event R2.2 Message: 'Multiframe alignment change detected: $1 on $2:$3' Parameters list: $1: r22Message $2: r22Interface $3: r22Channel Message generated for each change on multiframe alignment detection.
NTF r2Notification3	1.3.6.1.4.1.2007.1.4.100.2.0.3			Notification of Event R2.3 Message: 'Alarm: $1 on $2:$3' Parameters list: $1: r23Message $2: r23Interface $3: r23Channel Message generated for each change on the alarm bit.
NTF r2Notification4	1.3.6.1.4.1.2007.1.4.100.2.0.4			Notification of Event R2.4 Message: 'Command: $1 sent to $2:$3' Parameters list: $1: r24Command $2: r24Interface $3: r24Channel Command sent to the r2 api
NTF r2Notification5	1.3.6.1.4.1.2007.1.4.100.2.0.5			Notification of Event R2.5 Message: 'Error $1 context $2 on $3:$4' Parameters list: $1: r25Error $2: r25Context $3: r25Interface $4: r25Channel Error in r2 channel
NTF r2Notification6	1.3.6.1.4.1.2007.1.4.100.2.0.6			Notification of Event R2.6 Message: 'MFC phase change $1->$2 on $3:$4' Parameters list: $1: r26OldState $2: r26NewState $3: r26Interface $4: r26Channel Phase changed in mfc r2 protocol
NTF r2Notification7	1.3.6.1.4.1.2007.1.4.100.2.0.7			Notification of Event R2.7 Message: 'MFC state change $1->$2 on $3:$4' Parameters list: $1: r27OldState $2: r27NewState $3: r27Interface $4: r27Channel Phase changed in mfc r2 protocol
NTF r2Notification8	1.3.6.1.4.1.2007.1.4.100.2.0.8			Notification of Event R2.8 Message: 'MFC $1 signal $2 on $3:$4' Parameters list: $1: r28Signal $2: r28Received $3: r28Interface $4: r28Channel MFC signal sent or received
NTF r2Notification9	1.3.6.1.4.1.2007.1.4.100.2.0.9			Notification of Event R2.9 Message: 'ABCD signal $1 $2$3$4$5 on $6:$7' Parameters list: $1: r29Received $2: r29A $3: r29B $4: r29C $5: r29D $6: r29Interface $7: r29Channel MFC signal sent or received

RFC description

Manages SNMP notifications generated by Teldat R2 event subsystem for handling received event traps and state machine events.

Start monitoring Teldat router/gateway, E1 R2 signaling voice trunk (channel-associated signaling 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-R2-MIB

What Is TELDAT-TRAP-R2-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description