All MIBs › TELDAT-TRAP-SCCP-MIB
Organization: Teldat, S.A.
Last Updated: 2014-01-20
Category: Teldat Router Management, Teldat Trap Notifications, VoIP and Telephony
Description: Defines Teldat router SCCP (Skinny Client Control Protocol) 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-SCCP-MIB?
TELDAT-TRAP-SCCP-MIB is a vendor-specific MIB from Teldat defining SNMP trap notifications from the router's SCCP (Skinny Client Control Protocol, used in Cisco-style IP telephony signaling) event subsystem. It is a notifications-only module exposing trap variable bindings such as connection state, IP address, port, and a human-readable message/description. Its monitoring purpose is software/VoIP signaling event visibility: it alerts a management station in real time about SCCP session state changes or messages, helping operators detect issues affecting IP telephony endpoints or gateways handled by the router. It depends on the SCCP protocol as implemented within Teldat router VoIP-related software features. It is typically deployed on Teldat routers acting as VoIP gateways or SCCP proxies in enterprise telephony deployments. Engineers can download the TELDAT-TRAP-SCCP-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-SCCP-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 enterprise/carrier routers used as VoIP gateways
Monitoring Examples
A monitoring system would receive a trap carrying sccp1_state, sccp1_ip, and sccp1_port to learn that an SCCP session with a given endpoint changed state, and traps with sccp2_message/sccp3_message alongside their respective sccp2_ip/sccp2_port or sccp3_ip/sccp3_port fields to get descriptive detail about what occurred on a specific connection. A trap with sccp4_description, sccp4_ip, and sccp4_port would provide a free-text explanation tied to a particular IP telephony endpoint, useful for diagnosing call-signaling problems.
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
RFC description
Manages SNMP notifications from SCCP event subsystem for Teldat devices.
Start monitoring Teldat enterprise/carrier routers used as VoIP gateways (SCCP session state 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.