RTP-MIB: View SNMP OID List / Download MIB
VENDOR: INTERNET-STANDARD
| Home | MIB: RTP-MIB | |||
|---|---|---|---|---|
| Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
| Object Name | OID | Type | Access | Info |
| rtpMIB | 1.3.6.1.2.1.87 |
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. |
||
| rtpMIBObjects | 1.3.6.1.2.1.87.1 | |||
| rtpSessionNewIndex | 1.3.6.1.2.1.87.1.1 | testandincr | read-write |
This object is used to assign values to rtpSessionIndex as described in 'Textual Conventions for SMIv2'. For an RTP system that supports the creation of rows, the network manager would read the object, and then write the value back in the Set that creates a new instance of rtpSessionEntry. If the Set fails with the code 'inconsistentValue,' then the process must be repeated; If the Set succeeds, then the object is incremented, and the new instance is created according to the manager's directions. However, if the RTP agent is not acting as a monitor, only the RTP agent may create conceptual rows in the RTP session table. |
| rtpSessionInverseTable | 1.3.6.1.2.1.87.1.2 | no-access |
Maps rtpSessionDomain, rtpSessionRemAddr, and rtpSessionLocAddr TAddress pairs to one or more rtpSessionIndex values, each describing a row in the rtpSessionTable. This makes it possible to retrieve the row(s) in the rtpSessionTable corresponding to a given session without having to walk the entire (potentially large) table. |
|
| 1.3.6.1.2.1.87.1.2.1 | no-access |
Each entry corresponds to exactly one entry in the rtpSessionTable - the entry containing the tuple, rtpSessionDomain, rtpSessionRemAddr, rtpSessionLocAddr and rtpSessionIndex. |
||
| rtpSessionInverseStartTime | 1.3.6.1.2.1.87.1.2.1.1 | timestamp | read-only |
The value of SysUpTime at the time that this row was created. |
| rtpSessionTable | 1.3.6.1.2.1.87.1.3 | no-access |
There's one entry in rtpSessionTable for each RTP session on which packets are being sent, received, and/or monitored. |
|
| 1.3.6.1.2.1.87.1.3.1 | no-access |
Data in rtpSessionTable uniquely identify an RTP session. A host RTP agent MUST create a read-only row for each session to which packets are being sent or received. Rows MUST be created by the RTP Agent at the start of a session when one or more senders or receivers are observed. Rows created by an RTP agent MUST be deleted when the session is over and there are no rtpRcvrEntry and no rtpSenderEntry for this session. An RTP session SHOULD be monitored to create management information on all RTP streams being sent or received when the rtpSessionMonitor has the TruthValue of 'true(1)'. An RTP monitor SHOULD permit row creation with the side effect of causing the RTP System to join the multicast session for the purposes of gathering management information (additional conceptual rows are created in the rtpRcvrTable and rtpSenderTable). Thus, rtpSessionTable rows SHOULD be created for RTP session monitoring purposes. Rows created by a management application SHOULD be deleted via SNMP operations by management applications. Rows created by management operations are deleted by management operations by setting rtpSessionRowStatus to 'destroy(6)'. |
||
| rtpSessionIndex | 1.3.6.1.2.1.87.1.3.1.1 | integer32 | no-access |
The index of the conceptual row which is for SNMP purposes only and has no relation to any protocol value. There is no requirement that these rows are created or maintained sequentially. |
| rtpSessionDomain | 1.3.6.1.2.1.87.1.3.1.2 | tdomain | read-only |
The transport-layer protocol used for sending or receiving the stream of RTP data packets on this session. Cannot be changed if rtpSessionRowStatus is 'active'. |
| rtpSessionRemAddr | 1.3.6.1.2.1.87.1.3.1.3 | taddress | read-only |
The address to which RTP packets are sent by the RTP system. In an IP multicast RTP session, this is the single address used by all senders and receivers of RTP session data. In a unicast RTP session this is the unicast address of the remote RTP system. 'The destination address pair may be common for all participants, as in the case of IP multicast, or may be different for each, as in the case of individual unicast network address pairs.' See RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' sec. 3. The transport service is identified by rtpSessionDomain. For snmpUDPDomain, this is an IP address and even-numbered UDP Port with the RTCP being sent on the next higher odd-numbered port, see RFC 1889, sec. 5. |
| rtpSessionLocAddr | 1.3.6.1.2.1.87.1.3.1.4 | taddress | read-only |
The local address used by the RTP system. In an IP multicast RTP session, rtpSessionRemAddr will be the same IP multicast address as rtpSessionLocAddr. In a unicast RTP session, rtpSessionRemAddr and rtpSessionLocAddr will have different unicast addresses. See RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' sec. 3. The transport service is identified by rtpSessionDomain. For snmpUDPDomain, this is an IP address and even-numbered UDP Port with the RTCP being sent on the next higher odd-numbered port, see RFC 1889, sec. 5. |
| rtpSessionIfIndex | 1.3.6.1.2.1.87.1.3.1.5 | interfaceindex | read-only |
The ifIndex value is set to the corresponding value from IF-MIB (See RFC 2233, 'The Interfaces Group MIB using SMIv2'). This is the interface that the RTP stream is being sent to or received from, or in the case of an RTP Monitor the interface that RTCP packets will be received on. Cannot be changed if rtpSessionRowStatus is 'active'. |
| rtpSessionSenderJoins | 1.3.6.1.2.1.87.1.3.1.6 | counter32 | read-only |
The number of senders that have been observed to have joined the session since this conceptual row was created (rtpSessionStartTime). A sender 'joins' an RTP session by sending to it. Senders that leave and then re-join following an RTCP BYE (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' sec. 6.6) or session timeout may be counted twice. Every time a new RTP sender is detected either using RTP or RTCP, this counter is incremented. |
| rtpSessionReceiverJoins | 1.3.6.1.2.1.87.1.3.1.7 | counter32 | read-only |
The number of receivers that have been been observed to have joined this session since this conceptual row was created (rtpSessionStartTime). A receiver 'joins' an RTP session by sending RTCP Receiver Reports to the session. Receivers that leave and then re-join following an RTCP BYE (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' sec. 6.6) or session timeout may be counted twice. |
| rtpSessionByes | 1.3.6.1.2.1.87.1.3.1.8 | counter32 | read-only |
A count of RTCP BYE (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' sec. 6.6) messages received by this entity. |
| rtpSessionStartTime | 1.3.6.1.2.1.87.1.3.1.9 | timestamp | read-only |
The value of SysUpTime at the time that this row was created. |
| rtpSessionMonitor | 1.3.6.1.2.1.87.1.3.1.10 | truthvalue | read-only |
Boolean, Set to 'true(1)' if remote senders or receivers in addition to the local RTP System are to be monitored using RTCP. RTP Monitors MUST initialize to 'true(1)' and RTP Hosts SHOULD initialize this 'false(2)'. Note that because 'host monitor' systems are receiving RTCP from their remote participants they MUST set this value to 'true(1)'. |
| rtpSessionRowStatus | 1.3.6.1.2.1.87.1.3.1.11 | rowstatus | read-only |
Value of 'active' when RTP or RTCP messages are being sent or received by an RTP System. A newly-created conceptual row must have the all read-create objects initialized before becoming 'active'. A conceptual row that is in the 'notReady' or 'notInService' state MAY be removed after 5 minutes. |
| rtpSenderInverseTable | 1.3.6.1.2.1.87.1.4 | no-access |
Maps rtpSenderAddr, rtpSessionIndex, to the rtpSenderSSRC index of the rtpSenderTable. This table allows management applications to find entries sorted by rtpSenderAddr rather than sorted by rtpSessionIndex. Given the rtpSessionDomain and rtpSenderAddr, a set of rtpSessionIndex and rtpSenderSSRC values can be returned from a tree walk. When rtpSessionIndex is specified in the SNMP Get-Next operations, one or more rtpSenderSSRC values may be returned. |
|
| 1.3.6.1.2.1.87.1.4.1 | no-access |
Each entry corresponds to exactly one entry in the rtpSenderTable - the entry containing the index pair, rtpSessionIndex, rtpSenderSSRC. |
||
| rtpSenderInverseStartTime | 1.3.6.1.2.1.87.1.4.1.1 | timestamp | read-only |
The value of SysUpTime at the time that this row was created. |
| rtpSenderTable | 1.3.6.1.2.1.87.1.5 | no-access |
Table of information about a sender or senders to an RTP Session. RTP sending hosts MUST have an entry in this table for each stream being sent. RTP receiving hosts MAY have an entry in this table for each sending stream being received by this host. RTP monitors MUST create an entry for each observed sender to a multicast RTP Session as a side-effect when a conceptual row in the rtpSessionTable is made 'active' by a manager. |
|
| 1.3.6.1.2.1.87.1.5.1 | no-access |
Each entry contains information from a single RTP Sender Synchronization Source (SSRC, see RFC 1889 'RTP: A Transport Protocol for Real-Time Applications' sec.6). The session is identified to the the SNMP entity by rtpSessionIndex. Rows are removed by the RTP agent when a BYE is received from the sender or when the sender times out (see RFC 1889, Sec. 6.2.1) or when the rtpSessionEntry is deleted. |
||
| rtpSenderSSRC | 1.3.6.1.2.1.87.1.5.1.1 | unsigned32 | no-access |
The RTP SSRC, or synchronization source identifier of the sender. The RTP session address plus an SSRC uniquely identify a sender to an RTP session (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec.3). |
| rtpSenderCNAME | 1.3.6.1.2.1.87.1.5.1.2 | utf8string | read-only |
The RTP canonical name of the sender. |
| rtpSenderAddr | 1.3.6.1.2.1.87.1.5.1.3 | taddress | read-only |
The unicast transport source address of the sender. In the case of an RTP Monitor this address is the address that the sender is using to send its RTCP Sender Reports. |
| rtpSenderPackets | 1.3.6.1.2.1.87.1.5.1.4 | counter64 | read-only |
Count of RTP packets sent by this sender, or observed by an RTP monitor, since rtpSenderStartTime. |
| rtpSenderOctets | 1.3.6.1.2.1.87.1.5.1.5 | counter64 | read-only |
Count of non-header RTP octets sent by this sender, or observed by an RTP monitor, since rtpSenderStartTime. |
| rtpSenderTool | 1.3.6.1.2.1.87.1.5.1.6 | utf8string | read-only |
Name of the application program source of the stream. |
| rtpSenderSRs | 1.3.6.1.2.1.87.1.5.1.7 | counter32 | read-only |
A count of the number of RTCP Sender Reports that have been sent from this sender, or observed if the RTP entity is a monitor, since rtpSenderStartTime. |
| rtpSenderSRTime | 1.3.6.1.2.1.87.1.5.1.8 | timestamp | read-only |
rtpSenderSRTime is the value of SysUpTime at the time that the last SR was received from this sender, in the case of a monitor or receiving host. Or sent by this sender, in the case of a sending host. |
| rtpSenderPT | 1.3.6.1.2.1.87.1.5.1.9 | integer | read-only |
Payload type from the RTP header of the most recently received RTP Packet (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec. 5). |
| rtpSenderStartTime | 1.3.6.1.2.1.87.1.5.1.10 | timestamp | read-only |
The value of SysUpTime at the time that this row was created. |
| rtpRcvrInverseTable | 1.3.6.1.2.1.87.1.6 | no-access |
Maps rtpRcvrAddr and rtpSessionIndex to the rtpRcvrSRCSSRC and rtpRcvrSSRC indexes of the rtpRcvrTable. This table allows management applications to find entries sorted by rtpRcvrAddr rather than by rtpSessionIndex. Given rtpSessionDomain and rtpRcvrAddr, a set of rtpSessionIndex, rtpRcvrSRCSSRC, and rtpRcvrSSRC values can be returned from a tree walk. When rtpSessionIndex is specified in SNMP Get-Next operations, one or more rtpRcvrSRCSSRC and rtpRcvrSSRC pairs may be returned. |
|
| 1.3.6.1.2.1.87.1.6.1 | no-access |
Each entry corresponds to exactly one entry in the rtpRcvrTable - the entry containing the index pair, rtpSessionIndex, rtpRcvrSSRC. |
||
| rtpRcvrInverseStartTime | 1.3.6.1.2.1.87.1.6.1.1 | timestamp | read-only |
The value of SysUpTime at the time that this row was created. |
| rtpRcvrTable | 1.3.6.1.2.1.87.1.7 | no-access |
Table of information about a receiver or receivers of RTP session data. RTP hosts that receive RTP session packets MUST create an entry in this table for that receiver/sender pair. RTP hosts that send RTP session packets MAY create an entry in this table for each receiver to their stream using RTCP feedback from the RTP group. RTP monitors create an entry for each observed RTP session receiver as a side effect when a conceptual row in the rtpSessionTable is made 'active' by a manager. |
|
| 1.3.6.1.2.1.87.1.7.1 | no-access |
Each entry contains information from a single RTP Synchronization Source that is receiving packets from the sender identified by rtpRcvrSRCSSRC (SSRC, see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec.6). The session is identified to the the RTP Agent entity by rtpSessionIndex. Rows are removed by the RTP agent when a BYE is received from the sender or when the sender times out (see RFC 1889, Sec. 6.2.1) or when the rtpSessionEntry is deleted. |
||
| rtpRcvrSRCSSRC | 1.3.6.1.2.1.87.1.7.1.1 | unsigned32 | no-access |
The RTP SSRC, or synchronization source identifier of the sender. The RTP session address plus an SSRC uniquely identify a sender or receiver of an RTP stream (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec.3). |
| rtpRcvrSSRC | 1.3.6.1.2.1.87.1.7.1.2 | unsigned32 | no-access |
The RTP SSRC, or synchronization source identifier of the receiver. The RTP session address plus an SSRC uniquely identify a receiver of an RTP stream (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec.3). |
| rtpRcvrCNAME | 1.3.6.1.2.1.87.1.7.1.3 | utf8string | read-only |
The RTP canonical name of the receiver. |
| rtpRcvrAddr | 1.3.6.1.2.1.87.1.7.1.4 | taddress | read-only |
The unicast transport address on which the receiver is receiving RTP packets and/or RTCP Receiver Reports. |
| rtpRcvrRTT | 1.3.6.1.2.1.87.1.7.1.5 | gauge32 | read-only |
The round trip time measurement taken by the source of the RTP stream based on the algorithm described on sec. 6 of RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications.' This algorithm can produce meaningful results when the RTP agent has the same clock as the stream sender (when the RTP monitor is also the sending host for the particular receiver). Otherwise, the entity should return 'noSuchInstance' in response to queries against rtpRcvrRTT. |
| rtpRcvrLostPackets | 1.3.6.1.2.1.87.1.7.1.6 | counter64 | read-only |
A count of RTP packets lost as observed by this receiver since rtpRcvrStartTime. |
| rtpRcvrJitter | 1.3.6.1.2.1.87.1.7.1.7 | gauge32 | read-only |
An estimate of delay variation as observed by this receiver. (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec.6.3.1 and A.8). |
| rtpRcvrTool | 1.3.6.1.2.1.87.1.7.1.8 | utf8string | read-only |
Name of the application program source of the stream. |
| rtpRcvrRRs | 1.3.6.1.2.1.87.1.7.1.9 | counter32 | read-only |
A count of the number of RTCP Receiver Reports that have been sent from this receiver, or observed if the RTP entity is a monitor, since rtpRcvrStartTime. |
| rtpRcvrRRTime | 1.3.6.1.2.1.87.1.7.1.10 | timestamp | read-only |
rtpRcvrRRTime is the value of SysUpTime at the time that the last RTCP Receiver Report was received from this receiver, in the case of a monitor or RR receiver (the RTP Sender). It is the value of SysUpTime at the time that the last RR was sent by this receiver in the case of an RTP receiver sending the RR. |
| rtpRcvrPT | 1.3.6.1.2.1.87.1.7.1.11 | integer | read-only |
Static or dynamic payload type from the RTP header (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec. 5). |
| rtpRcvrPackets | 1.3.6.1.2.1.87.1.7.1.12 | counter64 | read-only |
Count of RTP packets received by this RTP host receiver since rtpRcvrStartTime. |
| rtpRcvrOctets | 1.3.6.1.2.1.87.1.7.1.13 | counter64 | read-only |
Count of non-header RTP octets received by this receiving RTP host since rtpRcvrStartTime. |
| rtpRcvrStartTime | 1.3.6.1.2.1.87.1.7.1.14 | timestamp | read-only |
The value of SysUpTime at the time that this row was created. |
| rtpConformance | 1.3.6.1.2.1.87.2 | |||
| rtpGroups | 1.3.6.1.2.1.87.2.1 | |||
| rtpSystemGroup | 1.3.6.1.2.1.87.2.1.1 |
Objects available to all RTP Systems. |
||
| rtpHostGroup | 1.3.6.1.2.1.87.2.1.2 |
Objects that are available to RTP Host systems, but may not be available to RTP Monitor systems. |
||
| rtpMonitorGroup | 1.3.6.1.2.1.87.2.1.3 |
Objects used to create rows in the RTP Session Table. These objects are not needed if the system does not create rows. |
||
| rtpInverseGroup | 1.3.6.1.2.1.87.2.1.4 |
Objects used in the Inverse Lookup Tables. |
||
| rtpCompliances | 1.3.6.1.2.1.87.2.2 | |||
| rtpHostCompliance | 1.3.6.1.2.1.87.2.2.1 |
Host implementations MUST comply. |
||
| rtpMonitorCompliance | 1.3.6.1.2.1.87.2.2.2 |
Monitor implementations must comply. RTP Monitors are not required to support creation or deletion. |
||