TRIP-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsTRIP-MIB

Organization: IETF IPTel Working Group. Mailing list: iptel@lists.bell-labs.com

Last Updated: 2004-09-02

Category: IP and Core Protocols, Routing Protocols, Telephony and VoIP

Description: Defines managed objects for managing Telephony Routing over IP (TRIP) location servers, including peer configuration and routing tables.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring TRIP-MIB with a free 30-day trial of IPNetwork Monitor.

What Is TRIP-MIB?

TRIP-MIB is an IETF standards-track MIB, published as RFC 3872, that models Telephony Routing over IP (TRIP), a policy-driven inter-domain protocol used between Location Servers (LS) to advertise reachability of telephony destinations and the attributes of routes to them. Its central tripCfgTable, indexed by applIndex, exposes per-LS-instance configuration and state: tripCfgProtocolVersion, tripCfgItad (the LS's Internet Telephony Administrative Domain), tripCfgIdentifier, tripCfgAdminStatus/tripCfgOperStatus (up/down/faulty), the LS's listening address and port (tripCfgAddr, tripCfgPort), and timing/policy parameters such as tripCfgMinItadOriginationInterval, tripCfgMinRouteAdvertisementInterval, tripCfgMaxPurgeTime, and tripCfgDisableTime. Monitoring these objects reveals whether a TRIP LS instance is administratively and operationally up, and how it is tuned to originate and re-advertise telephony routes, which matters for diagnosing call-routing failures in VoIP peering networks. It depends on NETWORK-SERVICES-MIB for applIndex, INET-ADDRESS-MIB for address typing, and TRIP-TC-MIB for TRIP-specific textual conventions. It is deployed on VoIP gateways and softswitches acting as TRIP location servers, and administrators researching the TRIP-MIB RFC (3872) definition can use these objects to confirm an LS instance is healthy.

IPNetwork Monitor allows you to monitor SNMP objects defined in TRIP-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 (RFC 3872), not tied to a specific manufacturer — applies to VoIP gateways/softswitches acting as TRIP Location Servers

Monitoring Examples

An operator polls tripCfgOperStatus for a given applIndex to confirm the TRIP location server instance is up, and checks tripCfgMinRouteAdvertisementInterval against expected peering configuration; an operational status of faulty or down while tripCfgAdminStatus reads up would indicate the LS failed to start despite being administratively enabled, blocking telephony route exchange with peers.

What Can Be Monitored

  • TRIP LS admin/operational status
  • ITAD and LS identifier configuration
  • listening address and port
  • route origination and advertisement interval tuning
  • route purge and disable timers
Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressType
InetPortNumber

From NETWORK-SERVICES-MIB

applIndexOBJECT-TYPE
applRFC2788GroupOBJECT-GROUP

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32
mib-2

From SNMPv2-TC

DateAndTime
RowStatus
StorageType
TimeInterval
TimeStamp
TruthValue

From TRIP-TC-MIB

TripAddressFamily
TripAppProtocol
TripCommunityId
TripId
TripItad
TripProtocolVersion
TripSendReceiveMode

How to Use in IPNetwork Monitor

Example using tripPeerInUpdates OID:

Select a device implementing TRIP-MIB as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type tripPeerInUpdates into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of TRIP update messages received from this remote peer since the last restart of this location server. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Telephony Routing over IP (TRIP) policy-driven protocol for reachability advertisement between location servers in voice networks.

Start monitoring vendor-neutral, standards-based IETF MIB (RFC 3872), VoIP gateway/softswitch acting as TRIP Location Server (admin/oper 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.

Download TRIP-MIB