RTP-MIB

        The managed objects of RTP systems.  The MIB is
structured around three types of information.
1. General information about RTP sessions such
   as the session address.
2. Information about RTP streams being sent to
   an RTP session by a particular sender.
3. Information about RTP streams received on an
   RTP session by a particular receiver from a
   particular sender.
 There are two types of RTP Systems, RTP hosts and
 RTP monitors.  As described below, certain objects
 are unique to a particular type of RTP System.   An
 RTP host may also function as an RTP monitor.
 Refer to RFC 1889, 'RTP: A Transport Protocol for
 Real-Time Applications,' section 3.0, for definitions.
    
Source file
RTP-MIB
Last revised
Identity
rtpMIB
Base OID
1.3.6.1.2.1.87
Imported Objects
IF-MIB InterfaceIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Counter64 Gauge32 Integer32 mib-2 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC RowStatus TAddress TDomain TestAndIncr TimeStamp TruthValue
SYSAPPL-MIB Utf8String
Net-SNMP examples using the rfc MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'RTP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'RTP-MIB::rtpMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'RTP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'RTP-MIB::rtpMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (56)
.1.3.6.1.2.1.87
.1.3.6.1.2.1.87.1
.1.3.6.1.2.1.87.1.1
.1.3.6.1.2.1.87.1.2
.1.3.6.1.2.1.87.1.2.1
.1.3.6.1.2.1.87.1.2.1.1
.1.3.6.1.2.1.87.1.3
.1.3.6.1.2.1.87.1.3.1
Integer32
.1.3.6.1.2.1.87.1.3.1.1
.1.3.6.1.2.1.87.1.3.1.10
.1.3.6.1.2.1.87.1.3.1.11
.1.3.6.1.2.1.87.1.3.1.2
.1.3.6.1.2.1.87.1.3.1.3
.1.3.6.1.2.1.87.1.3.1.4
.1.3.6.1.2.1.87.1.3.1.5
.1.3.6.1.2.1.87.1.3.1.6
.1.3.6.1.2.1.87.1.3.1.7
.1.3.6.1.2.1.87.1.3.1.8
.1.3.6.1.2.1.87.1.3.1.9
.1.3.6.1.2.1.87.1.4
.1.3.6.1.2.1.87.1.4.1
.1.3.6.1.2.1.87.1.4.1.1
.1.3.6.1.2.1.87.1.5
.1.3.6.1.2.1.87.1.5.1
.1.3.6.1.2.1.87.1.5.1.1
.1.3.6.1.2.1.87.1.5.1.10
.1.3.6.1.2.1.87.1.5.1.2
.1.3.6.1.2.1.87.1.5.1.3
.1.3.6.1.2.1.87.1.5.1.4
.1.3.6.1.2.1.87.1.5.1.5
OctetString
.1.3.6.1.2.1.87.1.5.1.6
.1.3.6.1.2.1.87.1.5.1.7
.1.3.6.1.2.1.87.1.5.1.8
Integer32
.1.3.6.1.2.1.87.1.5.1.9
.1.3.6.1.2.1.87.1.6
.1.3.6.1.2.1.87.1.6.1
.1.3.6.1.2.1.87.1.6.1.1
.1.3.6.1.2.1.87.1.7
.1.3.6.1.2.1.87.1.7.1
.1.3.6.1.2.1.87.1.7.1.1
.1.3.6.1.2.1.87.1.7.1.10
Integer32
.1.3.6.1.2.1.87.1.7.1.11
.1.3.6.1.2.1.87.1.7.1.12
.1.3.6.1.2.1.87.1.7.1.13
.1.3.6.1.2.1.87.1.7.1.14
.1.3.6.1.2.1.87.1.7.1.2
.1.3.6.1.2.1.87.1.7.1.3
.1.3.6.1.2.1.87.1.7.1.4
.1.3.6.1.2.1.87.1.7.1.5
.1.3.6.1.2.1.87.1.7.1.6
.1.3.6.1.2.1.87.1.7.1.7
OctetString
.1.3.6.1.2.1.87.1.7.1.8
.1.3.6.1.2.1.87.1.7.1.9
.1.3.6.1.2.1.87.2
.1.3.6.1.2.1.87.2.1
.1.3.6.1.2.1.87.2.2
Dependencies (7) 5 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. IANAifType-MIBrfc
  4. SNMPv2-CONFrfc
  5. SNMPv2-MIBrfc
  6. IF-MIBrfc
  7. SYSAPPL-MIBrfc
  8. RTP-MIBrfcselected
Conformance Groups (4)
Objects available to all RTP Systems.
.1.3.6.1.2.1.87.2.1.1
Objects that are available to RTP Host systems, but may not
be available to RTP Monitor systems.
.1.3.6.1.2.1.87.2.1.2
Objects used to create rows in the RTP Session Table. These
objects are not needed if the system does not create rows.
.1.3.6.1.2.1.87.2.1.3
Objects used in the Inverse Lookup Tables.
.1.3.6.1.2.1.87.2.1.4
Compliance Statements (2)

OID .1.3.6.1.2.1.87.2.2.1
Host implementations MUST comply.
Required groups
mandatory rtpSystemGroup
mandatory rtpHostGroup
optional rtpMonitorGroup Host systems my optionally support row creation and deletion.
This would allow an RTP Host system to act as an RTP Monitor.
optional rtpInverseGroup Multicast RTP Systems SHOULD implement the optional
tables.
Object refinements
ObjectAccessSyntaxDescription
rtpSessionNewIndex noaccess
RTP system implementations support of
row creation and deletion is OPTIONAL so
implementation of this object is OPTIONAL.
rtpSessionDomain readonly
RTP system implementation support of
row creation and deletion is OPTIONAL. When
it is not supported so write access is
OPTIONAL.
rtpSessionRemAddr readonly
Row creation and deletion is OPTIONAL so
read-create access to this object is OPTIONAL.
rtpSessionIfIndex readonly
Row creation and deletion is OPTIONAL so
read-create access to this object is OPTIONAL.
rtpSessionRowStatus noaccess
Row creation and deletion is OPTIONAL so
read-create access to this object is OPTIONAL.
rtpSessionInverseStartTime noaccess
Multicast RTP Systems SHOULD implement the optional
tables.
rtpSenderInverseStartTime noaccess
Multicast RTP Systems SHOULD implement the optional
tables.
rtpRcvrInverseStartTime noaccess
Multicast RTP Systems SHOULD implement the optional
tables.

OID .1.3.6.1.2.1.87.2.2.2
Monitor implementations must comply. RTP Monitors are not
required to support creation or deletion.
Required groups
mandatory rtpSystemGroup
mandatory rtpMonitorGroup
optional rtpHostGroup Monitor implementations may not have access to values in the
rtpHostGroup.
optional rtpInverseGroup Multicast RTP Systems SHOULD implement the optional
tables.
Object refinements
ObjectAccessSyntaxDescription
rtpSessionLocAddr noaccess
RTP monitor sourcing of RTP or RTCP data packets
is OPTIONAL and implementation of this object is
OPTIONAL.
rtpRcvrPT noaccess
RTP monitor systems may not support
retrieval of the RTP Payload Type from the RTP
header (and may receive RTCP messages only). When
queried for the payload type information
rtpSenderPT noaccess
RTP monitor systems may not support
retrieval of the RTP Payload Type from the RTP

header (and may receive RTCP messages only). When
queried for the payload type information.
rtpRcvrOctets noaccess
RTP monitor systems may receive only the RTCP messages
and not the RTP messages that contain the octet count
of the RTP message. Thus implementation of this
object is OPTIONAL
rtpRcvrPackets noaccess
RTP monitor systems may receive only the RTCP messages
and not the RTP messages that contain the octet count
of the RTP message. Thus implementation of this
object is OPTIONAL.
rtpSessionIfIndex readonly
Row creation and deletion is OPTIONAL so
read-create access to this object is OPTIONAL.
rtpSessionInverseStartTime noaccess
Multicast RTP Systems SHOULD implement the optional
tables.
rtpSenderInverseStartTime noaccess
Multicast RTP Systems SHOULD implement the optional
tables.
rtpRcvrInverseStartTime noaccess
Multicast RTP Systems SHOULD implement the optional
tables.