rtpSessionEntry OBJECT-TYPE SYNTAX RtpSessionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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 rue(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)."
INDEX { rtpSessionIndex }
View at oid-info.com
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)'.
Parsed from file rfc2959-Real-Time-Transport-Protocol-RTP.mib.txt
Company: None
Module: RTP-MIB
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)'.
Parsed from file RTP-MIB.mib
Module: RTP-MIB
Automatically extracted from RFC2959
rtpSessionEntry OBJECT-TYPE SYNTAX RtpSessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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)'." INDEX { rtpSessionIndex } ::= { rtpSessionTable 1 }
rtpSessionEntry OBJECT-TYPE SYNTAX RtpSessionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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)'." INDEX { rtpSessionIndex } ::= { rtpSessionTable 1 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.87.1.3.1.1 | rtpSessionIndex | 0 | 0 | The index of the conceptual row which is for SNMP purposes only and has no relation to any protocol value. There is no requireme… |
| 1.3.6.1.2.1.87.1.3.1.2 | rtpSessionDomain | 0 | 0 | The transport-layer protocol used for sending or receiving the stream of RTP data packets on this session. Cannot be changed if r… |
| 1.3.6.1.2.1.87.1.3.1.3 | rtpSessionRemAddr | 0 | 0 | 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 a… |
| 1.3.6.1.2.1.87.1.3.1.4 | rtpSessionLocAddr | 0 | 0 | The local address used by the RTP system. In an IP multicast RTP session, rtpSessionRemAddr will be the same IP multicast addres… |
| 1.3.6.1.2.1.87.1.3.1.5 | rtpSessionIfIndex | 0 | 0 | The ifIndex value is set to the corresponding value from IF-MIB (See RFC 2233, 'The Interfaces Group MIB using SMIv2'). This is … |
| 1.3.6.1.2.1.87.1.3.1.6 | rtpSessionSenderJoins | 0 | 0 | The number of senders that have been observed to have joined the session since this conceptual row was created (rtpSessionStartTi… |
| 1.3.6.1.2.1.87.1.3.1.7 | rtpSessionReceiverJoins | 0 | 0 | The number of receivers that have been been observed to have joined this session since this conceptual row was created (rtpSessio… |
| 1.3.6.1.2.1.87.1.3.1.8 | rtpSessionByes | 0 | 0 | A count of RTCP BYE (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' sec. 6.6) messages received by this en… |
| 1.3.6.1.2.1.87.1.3.1.9 | rtpSessionStartTime | 0 | 0 | The value of SysUpTime at the time that this row was created. |
| 1.3.6.1.2.1.87.1.3.1.10 | rtpSessionMonitor | 0 | 0 | Boolean, Set to 'true(1)' if remote senders or receivers in addition to the local RTP System are to be monitored using RTCP. RTP … |
| 1.3.6.1.2.1.87.1.3.1.11 | rtpSessionRowStatus | 0 | 0 | Value of 'active' when RTP or RTCP messages are being sent or received by an RTP System. A newly-created conceptual row must hav… |