All MIBs › TRIP-TC
Organization: IETF IPTel Working Group. Mailing list: iptel@lists.bell-labs.com
Last Updated: 2004-02-05
Description: Textual conventions module for the IETF Telephony Routing Over IP (TRIP) protocol MIB, used by IP telephony routing systems
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 TRIP-TC?
TRIP-TC is an IETF standards-track textual-conventions MIB module supporting the Telephony Routing over IP (TRIP) protocol, used by IP telephony gateways and location servers to exchange routing information about how to reach telephone-number destinations across IP networks. This module itself does not define runtime data objects, hardware/software status objects, or notifications; it only defines shared textual conventions (data types) that other TRIP-related MIB modules import and reuse for consistent representation of TRIP-specific values (such as route attributes or gateway identifiers). Because it is purely a type-definitions module, it is not directly used to monitor hardware or software status; any monitoring capability comes from companion TRIP MIB modules that actually import these conventions to define pollable objects. As an IETF module it is foundational to, and required by, other TRIP MIB modules for consistent syntax. It would be deployed as a supporting type-library module wherever IP telephony gateways or Internet Telephony Administrative Domains (ITADs) are managed via SNMP using TRIP-based routing. Engineers implementing or auditing this functionality typically reference the TRIP-TC RFC/standard documentation for the authoritative specification.
IPNetwork Monitor allows you to monitor SNMP objects defined in TRIP-TC. 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 IETF MIB, not tied to a specific manufacturer
- IP telephony gateways and location servers implementing TRIP
Monitoring Examples
TRIP-TC is a textual-conventions-only module with no data objects, tables, or notifications of its own — sample_objects is empty, and by design a TC module exists solely to be imported by other MIBs. There is no honest monitoring scenario to construct for this module in isolation; any actual polling would occur against a companion TRIP MIB module that imports these type definitions to expose real gateway/routing data.
Imported Objects
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| Unsigned32 | |
| mib-2 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
OIDs
RFC description
Telephony Routing Over IP (TRIP) textual conventions and initial MIB definitions.
Start monitoring vendor-neutral, standards-based IETF MIB, IP telephony gateways and location servers implementing TRIP (shared textual conventions, no data objects) 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.