All MIBs › TRIP-TC-MIB
Organization: IETF IPTel Working Group. Mailing list: iptel@lists.bell-labs.com
Last Updated: 2004-09-02
Category: Routing Protocols, Telephony and VoIP, Textual Conventions and Registries
Description: Supplies the textual conventions used by MIB modules for Telephony Routing over IP (TRIP).
IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring TRIP-TC-MIB with a free 30-day trial of IPNetwork Monitor.
What Is TRIP-TC-MIB?
TRIP-TC-MIB is a vendor-neutral IETF standards MIB (RFC 3872) that defines shared textual conventions used by other Telephony Routing over IP (TRIP) MIB modules rather than exposing any managed objects of its own. TRIP is a protocol for exchanging telephony routing information between IP telephony gateways and gateway location servers, similar in spirit to BGP for VoIP call routing. This module itself carries no monitorable data — no interfaces, environment, counters, or fault objects — since it is purely a type-definition library consumed by companion TRIP MIBs (such as a TRIP peer or route table MIB) that would provide the actual protocol state, session, and route status objects. Because it only supplies textual conventions, it has an inherent dependency relationship with the actual TRIP protocol MIB modules that import it. It is deployed wherever TRIP-capable ITAD (Internet Telephony Administrative Domain) gateways or route servers implement SNMP instrumentation for VoIP call routing infrastructure. Engineers implementing or auditing this functionality typically reference the TRIP-TC-MIB RFC/standard documentation for the authoritative specification.
IPNetwork Monitor allows you to monitor SNMP objects defined in TRIP-TC-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
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer
- VoIP/IP telephony gateway or TRIP route server
Monitoring Examples
Since TRIP-TC-MIB defines only textual conventions (data types) and has no sample objects of its own, there is nothing to poll directly in this module; a monitoring tool would instead see these types reused as the SYNTAX of objects in a companion TRIP MIB, such as a peer state or route-table entry. For example, a TC defined here might constrain the value of a TRIP session state object elsewhere, so a management station observing that dependent object relies on this module purely for type-safety and consistent value semantics across TRIP implementations. There is no independent fault, performance, or configuration table to monitor in TRIP-TC-MIB itself.
What Can Be Monitored
- textual convention definitions only (no direct monitorable objects)
- supports type consistency for companion TRIP MIB modules
- no interface, environment, or fault objects of its own
Imported Objects
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| Unsigned32 | |
| mib-2 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
OIDs
RFC description
Defines textual conventions for Telephony Routing over IP (TRIP) MIB modules.
Start monitoring VoIP telephony gateways and TRIP route servers 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.