rtpSenderTable OBJECT-TYPE SYNTAX SEQUENCE OF RtpSenderEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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."
View at oid-info.com
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.
Parsed from file rfc2959-Real-Time-Transport-Protocol-RTP.mib.txt
Company: None
Module: RTP-MIB
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.
Parsed from file RTP-MIB.mib
Module: RTP-MIB
Automatically extracted from RFC2959
rtpSenderTable OBJECT-TYPE SYNTAX SEQUENCE OF RtpSenderEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { rtpMIBObjects 5 }
rtpSenderTable OBJECT-TYPE SYNTAX SEQUENCE OF RtpSenderEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { rtpMIBObjects 5 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.87.1.5.1 | rtpSenderEntry | 10 | 10 | Each entry contains information from a single RTP Sender Synchronization Source (SSRC, see RFC 1889 'RTP: A Transport Protocol fo… |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.87.1.1 | rtpSessionNewIndex | 1 | 1 | This object is used to assign values to rtpSessionIndex as described in 'Textual Conventions for SMIv2'. For an RTP sys… |
| 1.3.6.1.2.1.87.1.2 | rtpSessionInverseTable | 1 | 2 | Maps rtpSessionDomain, rtpSessionRemAddr, and rtpSessionLocAddr TAddress pairs to one or more rtpSessionIndex values, each descri… |
| 1.3.6.1.2.1.87.1.3 | rtpSessionTable | 1 | 12 | 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.4 | rtpSenderInverseTable | 1 | 2 | Maps rtpSenderAddr, rtpSessionIndex, to the rtpSenderSSRC index of the rtpSenderTable. This table allows management applications… |
| 1.3.6.1.2.1.87.1.6 | rtpRcvrInverseTable | 1 | 2 | Maps rtpRcvrAddr and rtpSessionIndex to the rtpRcvrSRCSSRC and rtpRcvrSSRC indexes of the rtpRcvrTable. This table allows manage… |
| 1.3.6.1.2.1.87.1.7 | rtpRcvrTable | 1 | 15 | Table of information about a receiver or receivers of RTP session data. RTP hosts that receive RTP session packets MUST create an… |