Main page
OID Repository
https://oid-base.com
Display OID:

{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) rtpMIB(87) rtpMIBObjects(1) rtpSessionTable(3) rtpSessionEntry(1)}

rtpSessionEntry(1)

Please enable JS JavaScript to benefit of all features of the OID repository 🚀.
→ Child OIDs with no (direct) grandchild OID described in this OID repository are displayed with hatching (///).
→ Clicking on a slice focuses on the corresponding child OID.
→ Colors are generated randomly each time this page is displayed (except for the first slice).

 
 

OID description



 
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

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}



Classification:

MIB object for network management

 
See classes of OIDs

Information:

Automatically extracted from IETF RFC 2959.


Note to implementers:




 
 
Short link:


Tree display Parent OID: rtpSessionTable(3) First child OID: rtpSessionIndex(1)