From 98a672123c7872f6b9b75a9a2b6bb3aea504de6a Mon Sep 17 00:00:00 2001 From: David Leutgeb Date: Tue, 5 Dec 2023 12:25:34 +0100 Subject: Initial commit --- MIBS/audiocodes/RTP-MIB | 1021 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 MIBS/audiocodes/RTP-MIB (limited to 'MIBS/audiocodes/RTP-MIB') diff --git a/MIBS/audiocodes/RTP-MIB b/MIBS/audiocodes/RTP-MIB new file mode 100644 index 0000000..698aa94 --- /dev/null +++ b/MIBS/audiocodes/RTP-MIB @@ -0,0 +1,1021 @@ +RTP-MIB + +DEFINITIONS ::= BEGIN +IMPORTS + Counter32, Counter64, Gauge32, mib-2, Integer32, + MODULE-IDENTITY, + OBJECT-TYPE, Unsigned32 FROM SNMPv2-SMI + RowStatus, TAddress, + TDomain, TestAndIncr, + TimeStamp, TruthValue FROM SNMPv2-TC + OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF; + +rtpMIB MODULE-IDENTITY + LAST-UPDATED "200010020000Z" -- 2 October 2000 + ORGANIZATION + "IETF AVT Working Group + Email: rem-conf@es.net" + CONTACT-INFO + "Mark Baugher + Postal: Intel Corporation + 2111 NE 25th Avenue + Hillsboro, OR 97124 + + United States + Tel: +1 503 466 8406 + Email: mbaugher@passedge.com + + Bill Strahm + Postal: Intel Corporation + 2111 NE 25th Avenue + Hillsboro, OR 97124 + United States + Tel: +1 503 264 4632 + Email: bill.strahm@intel.com + + Irina Suconick + Postal: Ennovate Networks + 60 Codman Hill Rd., + Boxboro, Ma 01719 + Tel: +1 781-505-2155 + Email: irina@ennovatenetworks.com" + + DESCRIPTION + "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." + REVISION "200010020000Z" -- 2 October 2000 + DESCRIPTION "Initial version of this MIB. + Published as RFC 2959." + +::= { mib-2 87 } + + +InterfaceIndex ::= TEXTUAL-CONVENTION + DISPLAY-HINT "d" + STATUS current + DESCRIPTION + "A unique value, greater than zero, for each interface + or interface sub-layer in the managed system. It is + recommended that values are assigned contiguously + starting from 1. The value for each interface sub- + layer must remain constant at least from one re- + initialization of the entity's network management + system to the next re-initialization." + SYNTAX Integer32 + + +Utf8String ::= TEXTUAL-CONVENTION + DISPLAY-HINT "1024a" + STATUS current + DESCRIPTION + "To facilitate internationalization, this TC + represents information taken from the ISO/IEC IS + 10646-1 character set, encoded as an octet string + using the UTF-8 character encoding scheme described + in RFC 2044 [10]. For strings in 7-bit US-ASCII, + there is no impact since the UTF-8 representation + is identical to the US-ASCII encoding." + SYNTAX OCTET STRING (SIZE (0..1024)) + + + +-- +-- OBJECTS +-- +rtpMIBObjects OBJECT IDENTIFIER ::= { rtpMIB 1 } +rtpConformance OBJECT IDENTIFIER ::= { rtpMIB 2 } + +-- + +-- SESSION NEW INDEX +-- +rtpSessionNewIndex OBJECT-TYPE + SYNTAX TestAndIncr + MAX-ACCESS read-write + STATUS current + DESCRIPTION + "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." + ::= { rtpMIBObjects 1 } + +-- +-- SESSION INVERSE TABLE +-- +rtpSessionInverseTable OBJECT-TYPE + SYNTAX SEQUENCE OF RtpSessionInverseEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "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." + ::= { rtpMIBObjects 2 } + +rtpSessionInverseEntry OBJECT-TYPE + SYNTAX RtpSessionInverseEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Each entry corresponds to exactly one entry in the + rtpSessionTable - the entry containing the tuple, + rtpSessionDomain, rtpSessionRemAddr, rtpSessionLocAddr + and rtpSessionIndex." + INDEX { rtpSessionDomain, rtpSessionRemAddr, rtpSessionLocAddr, + rtpSessionIndex } + ::= { rtpSessionInverseTable 1 } + +RtpSessionInverseEntry ::= SEQUENCE { + rtpSessionInverseStartTime TimeStamp + } + +rtpSessionInverseStartTime OBJECT-TYPE + SYNTAX TimeStamp + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The value of SysUpTime at the time that this row was + created." + ::= { rtpSessionInverseEntry 1 } + +-- +-- SESSION TABLE +-- +rtpSessionTable OBJECT-TYPE + SYNTAX SEQUENCE OF RtpSessionEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "There's one entry in rtpSessionTable for each RTP session + on which packets are being sent, received, and/or + monitored." + ::= { rtpMIBObjects 3 } + +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 ::= SEQUENCE { + rtpSessionIndex Integer32, + rtpSessionDomain TDomain, + rtpSessionRemAddr TAddress, + rtpSessionLocAddr TAddress, + rtpSessionIfIndex InterfaceIndex, + rtpSessionSenderJoins Counter32, + rtpSessionReceiverJoins Counter32, + rtpSessionByes Counter32, + rtpSessionStartTime TimeStamp, + rtpSessionMonitor TruthValue, + rtpSessionRowStatus RowStatus + } + +rtpSessionIndex OBJECT-TYPE + SYNTAX Integer32 (1..2147483647) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "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." + ::= { rtpSessionEntry 1 } + +rtpSessionDomain OBJECT-TYPE + SYNTAX TDomain + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "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'." + ::= { rtpSessionEntry 2 } + +rtpSessionRemAddr OBJECT-TYPE + SYNTAX TAddress + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "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." + ::= { rtpSessionEntry 3 } + +rtpSessionLocAddr OBJECT-TYPE + SYNTAX TAddress + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "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." + ::= { rtpSessionEntry 4 } + +rtpSessionIfIndex OBJECT-TYPE + SYNTAX InterfaceIndex + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "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'." + ::= { rtpSessionEntry 5 } + +rtpSessionSenderJoins OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "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." + ::= { rtpSessionEntry 6 } + +rtpSessionReceiverJoins OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "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." + ::= { rtpSessionEntry 7 } + +rtpSessionByes OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "A count of RTCP BYE (see RFC 1889, 'RTP: A Transport + Protocol for Real-Time Applications,' sec. 6.6) messages + received by this entity." + ::= { rtpSessionEntry 8 } + +rtpSessionStartTime OBJECT-TYPE + SYNTAX TimeStamp + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The value of SysUpTime at the time that this row was + created." + ::= { rtpSessionEntry 9 } + +rtpSessionMonitor OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION + + "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)'." + ::= { rtpSessionEntry 10 } + +rtpSessionRowStatus OBJECT-TYPE + SYNTAX RowStatus + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "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." + ::= { rtpSessionEntry 11 } + +-- +-- SENDER INVERSE TABLE +-- +rtpSenderInverseTable OBJECT-TYPE + SYNTAX SEQUENCE OF RtpSenderInverseEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "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." + ::= { rtpMIBObjects 4 } + +rtpSenderInverseEntry OBJECT-TYPE + SYNTAX RtpSenderInverseEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Each entry corresponds to exactly one entry in the + rtpSenderTable - the entry containing the index pair, + rtpSessionIndex, rtpSenderSSRC." + INDEX { rtpSessionDomain, rtpSenderAddr, rtpSessionIndex, + + rtpSenderSSRC } + ::= { rtpSenderInverseTable 1 } + +RtpSenderInverseEntry ::= SEQUENCE { + rtpSenderInverseStartTime TimeStamp + } + +rtpSenderInverseStartTime OBJECT-TYPE + SYNTAX TimeStamp + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The value of SysUpTime at the time that this row was + created." + ::= { rtpSenderInverseEntry 1 } + +-- +-- SENDERS TABLE +-- +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 } + +rtpSenderEntry OBJECT-TYPE + SYNTAX RtpSenderEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "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." + INDEX { rtpSessionIndex, rtpSenderSSRC } + ::= { rtpSenderTable 1 } + +RtpSenderEntry ::= SEQUENCE { + rtpSenderSSRC Unsigned32, + rtpSenderCNAME Utf8String, + rtpSenderAddr TAddress, + rtpSenderPackets Counter64, + rtpSenderOctets Counter64, + rtpSenderTool Utf8String, + rtpSenderSRs Counter32, + rtpSenderSRTime TimeStamp, + rtpSenderPT INTEGER, + rtpSenderStartTime TimeStamp + } + +rtpSenderSSRC OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "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)." + ::= { rtpSenderEntry 1 } + +rtpSenderCNAME OBJECT-TYPE + SYNTAX Utf8String + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The RTP canonical name of the sender." + ::= { rtpSenderEntry 2 } + +rtpSenderAddr OBJECT-TYPE + SYNTAX TAddress + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "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." + ::= { rtpSenderEntry 3 } + +rtpSenderPackets OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Count of RTP packets sent by this sender, or observed by + + an RTP monitor, since rtpSenderStartTime." + ::= { rtpSenderEntry 4 } + +rtpSenderOctets OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Count of non-header RTP octets sent by this sender, or observed + by an RTP monitor, since rtpSenderStartTime." + ::= { rtpSenderEntry 5 } + +rtpSenderTool OBJECT-TYPE + SYNTAX Utf8String (SIZE(0..127)) + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Name of the application program source of the stream." + ::= { rtpSenderEntry 6 } + +rtpSenderSRs OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "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." + ::= { rtpSenderEntry 7 } + +rtpSenderSRTime OBJECT-TYPE + SYNTAX TimeStamp + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "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." + ::= { rtpSenderEntry 8 } + +rtpSenderPT OBJECT-TYPE + SYNTAX INTEGER (0..127) + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "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)." + ::= { rtpSenderEntry 9 } + +rtpSenderStartTime OBJECT-TYPE + SYNTAX TimeStamp + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The value of SysUpTime at the time that this row was + created." + ::= { rtpSenderEntry 10 } + +-- +-- RECEIVER INVERSE TABLE +-- +rtpRcvrInverseTable OBJECT-TYPE + SYNTAX SEQUENCE OF RtpRcvrInverseEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "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." + ::= { rtpMIBObjects 6 } + +rtpRcvrInverseEntry OBJECT-TYPE + SYNTAX RtpRcvrInverseEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Each entry corresponds to exactly one entry in the + rtpRcvrTable - the entry containing the index pair, + rtpSessionIndex, rtpRcvrSSRC." + INDEX { rtpSessionDomain, rtpRcvrAddr, rtpSessionIndex, + rtpRcvrSRCSSRC, rtpRcvrSSRC } + ::= { rtpRcvrInverseTable 1 } + +RtpRcvrInverseEntry ::= SEQUENCE { + rtpRcvrInverseStartTime TimeStamp + } + +rtpRcvrInverseStartTime OBJECT-TYPE + SYNTAX TimeStamp + + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The value of SysUpTime at the time that this row was + created." + ::= { rtpRcvrInverseEntry 1 } + +-- +-- RECEIVERS TABLE +-- +rtpRcvrTable OBJECT-TYPE + SYNTAX SEQUENCE OF RtpRcvrEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "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." + ::= { rtpMIBObjects 7 } + +rtpRcvrEntry OBJECT-TYPE + SYNTAX RtpRcvrEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "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." + INDEX { rtpSessionIndex, rtpRcvrSRCSSRC, rtpRcvrSSRC } + ::= { rtpRcvrTable 1 } + +RtpRcvrEntry ::= SEQUENCE { + rtpRcvrSRCSSRC Unsigned32, + rtpRcvrSSRC Unsigned32, + rtpRcvrCNAME Utf8String, + rtpRcvrAddr TAddress, + + rtpRcvrRTT Gauge32, + rtpRcvrLostPackets Counter64, + rtpRcvrJitter Gauge32, + rtpRcvrTool Utf8String, + rtpRcvrRRs Counter32, + rtpRcvrRRTime TimeStamp, + rtpRcvrPT INTEGER, + rtpRcvrPackets Counter64, + rtpRcvrOctets Counter64, + rtpRcvrStartTime TimeStamp + } + +rtpRcvrSRCSSRC OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "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)." + ::= { rtpRcvrEntry 1 } + +rtpRcvrSSRC OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "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)." + ::= { rtpRcvrEntry 2 } + +rtpRcvrCNAME OBJECT-TYPE + SYNTAX Utf8String + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The RTP canonical name of the receiver." + ::= { rtpRcvrEntry 3 } + +rtpRcvrAddr OBJECT-TYPE + SYNTAX TAddress + MAX-ACCESS read-only + STATUS current + DESCRIPTION + + "The unicast transport address on which the receiver is + receiving RTP packets and/or RTCP Receiver Reports." + ::= { rtpRcvrEntry 4 } + +rtpRcvrRTT OBJECT-TYPE + SYNTAX Gauge32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "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." + ::= { rtpRcvrEntry 5 } + +rtpRcvrLostPackets OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "A count of RTP packets lost as observed by this receiver + since rtpRcvrStartTime." + ::= { rtpRcvrEntry 6 } + +rtpRcvrJitter OBJECT-TYPE + SYNTAX Gauge32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "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)." + ::= { rtpRcvrEntry 7 } + +rtpRcvrTool OBJECT-TYPE + SYNTAX Utf8String (SIZE(0..127)) + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Name of the application program source of the stream." + ::= { rtpRcvrEntry 8 } + +rtpRcvrRRs OBJECT-TYPE + SYNTAX Counter32 + + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "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." + ::= { rtpRcvrEntry 9 } + +rtpRcvrRRTime OBJECT-TYPE + SYNTAX TimeStamp + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "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." + ::= { rtpRcvrEntry 10 } + +rtpRcvrPT OBJECT-TYPE + SYNTAX INTEGER (0..127) + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Static or dynamic payload type from the RTP header (see + RFC 1889, 'RTP: A Transport Protocol for Real-Time + Applications' sec. 5)." + ::= { rtpRcvrEntry 11 } + +rtpRcvrPackets OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Count of RTP packets received by this RTP host receiver + since rtpRcvrStartTime." + ::= { rtpRcvrEntry 12 } + +rtpRcvrOctets OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Count of non-header RTP octets received by this receiving RTP + host since rtpRcvrStartTime." + ::= { rtpRcvrEntry 13 } + +rtpRcvrStartTime OBJECT-TYPE + SYNTAX TimeStamp + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The value of SysUpTime at the time that this row was + created." + ::= { rtpRcvrEntry 14 } + +-- +-- MODULE GROUPS +-- +-- +-- There are two types of RTP Systems, RTP hosts and RTP Monitors. +-- Thus there are three kinds of objects: 1) Objects common to both +-- kinds of systems, 2) Objects unique to RTP Hosts and 3) Objects +-- unique to RTP Monitors. There is a fourth group, 4) Objects that +-- SHOULD be implemented by Multicast hosts and RTP Monitors + +rtpGroups OBJECT IDENTIFIER ::= { rtpConformance 1 } +rtpSystemGroup OBJECT-GROUP + OBJECTS { + rtpSessionDomain, + rtpSessionRemAddr, + rtpSessionIfIndex, + rtpSessionSenderJoins, + rtpSessionReceiverJoins, + rtpSessionStartTime, + rtpSessionByes, + rtpSessionMonitor, + rtpSenderCNAME, + rtpSenderAddr, + rtpSenderPackets, + rtpSenderOctets, + rtpSenderTool, + rtpSenderSRs, + rtpSenderSRTime, + rtpSenderStartTime, + rtpRcvrCNAME, + rtpRcvrAddr, + rtpRcvrLostPackets, + rtpRcvrJitter, + rtpRcvrTool, + rtpRcvrRRs, + rtpRcvrRRTime, + rtpRcvrStartTime + } + STATUS current + + DESCRIPTION + "Objects available to all RTP Systems." + ::= { rtpGroups 1 } + +rtpHostGroup OBJECT-GROUP + OBJECTS { + rtpSessionLocAddr, + rtpSenderPT, + rtpRcvrPT, + rtpRcvrRTT, + rtpRcvrOctets, + rtpRcvrPackets + } + STATUS current + DESCRIPTION + "Objects that are available to RTP Host systems, but may not + be available to RTP Monitor systems." + ::= { rtpGroups 2 } + +rtpMonitorGroup OBJECT-GROUP + OBJECTS { + rtpSessionNewIndex, + rtpSessionRowStatus + } + STATUS current + DESCRIPTION + "Objects used to create rows in the RTP Session Table. These + objects are not needed if the system does not create rows." + ::= { rtpGroups 3 } + +rtpInverseGroup OBJECT-GROUP + OBJECTS { + rtpSessionInverseStartTime, + rtpSenderInverseStartTime, + rtpRcvrInverseStartTime + } + STATUS current + DESCRIPTION + "Objects used in the Inverse Lookup Tables." + ::= { rtpGroups 4 } + +-- +-- Compliance +-- +rtpCompliances OBJECT IDENTIFIER ::= { rtpConformance 2 } + +rtpHostCompliance MODULE-COMPLIANCE + STATUS current + + DESCRIPTION + "Host implementations MUST comply." + MODULE RTP-MIB + MANDATORY-GROUPS { + rtpSystemGroup, + rtpHostGroup + } + GROUP rtpMonitorGroup + DESCRIPTION + "Host systems my optionally support row creation and deletion. + This would allow an RTP Host system to act as an RTP Monitor." + GROUP rtpInverseGroup + DESCRIPTION + "Multicast RTP Systems SHOULD implement the optional + tables." + OBJECT rtpSessionNewIndex + MIN-ACCESS not-accessible + DESCRIPTION + "RTP system implementations support of + row creation and deletion is OPTIONAL so + implementation of this object is OPTIONAL." + OBJECT rtpSessionDomain + MIN-ACCESS read-only + DESCRIPTION + "RTP system implementation support of + row creation and deletion is OPTIONAL. When + it is not supported so write access is + OPTIONAL." + OBJECT rtpSessionRemAddr + MIN-ACCESS read-only + DESCRIPTION + "Row creation and deletion is OPTIONAL so + read-create access to this object is OPTIONAL." + OBJECT rtpSessionIfIndex + MIN-ACCESS read-only + DESCRIPTION + "Row creation and deletion is OPTIONAL so + read-create access to this object is OPTIONAL." + OBJECT rtpSessionRowStatus + MIN-ACCESS not-accessible + DESCRIPTION + "Row creation and deletion is OPTIONAL so + read-create access to this object is OPTIONAL." + OBJECT rtpSessionInverseStartTime + MIN-ACCESS not-accessible + DESCRIPTION + "Multicast RTP Systems SHOULD implement the optional + tables." + + OBJECT rtpSenderInverseStartTime + MIN-ACCESS not-accessible + DESCRIPTION + "Multicast RTP Systems SHOULD implement the optional + tables." + OBJECT rtpRcvrInverseStartTime + MIN-ACCESS not-accessible + DESCRIPTION + "Multicast RTP Systems SHOULD implement the optional + tables." + ::= { rtpCompliances 1 } + +rtpMonitorCompliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "Monitor implementations must comply. RTP Monitors are not + required to support creation or deletion." + MODULE RTP-MIB + MANDATORY-GROUPS { + rtpSystemGroup, + rtpMonitorGroup + } + GROUP rtpHostGroup + DESCRIPTION + "Monitor implementations may not have access to values in the + rtpHostGroup." + GROUP rtpInverseGroup + DESCRIPTION + "Multicast RTP Systems SHOULD implement the optional + tables." + OBJECT rtpSessionLocAddr + MIN-ACCESS not-accessible + DESCRIPTION + "RTP monitor sourcing of RTP or RTCP data packets + is OPTIONAL and implementation of this object is + OPTIONAL." + OBJECT rtpRcvrPT + MIN-ACCESS not-accessible + DESCRIPTION + "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" + OBJECT rtpSenderPT + MIN-ACCESS not-accessible + DESCRIPTION + "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." + OBJECT rtpRcvrOctets + MIN-ACCESS not-accessible + DESCRIPTION + "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" + OBJECT rtpRcvrPackets + MIN-ACCESS not-accessible + DESCRIPTION + "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." + OBJECT rtpSessionIfIndex + MIN-ACCESS read-only + DESCRIPTION + "Row creation and deletion is OPTIONAL so + read-create access to this object is OPTIONAL." + OBJECT rtpSessionInverseStartTime + MIN-ACCESS not-accessible + DESCRIPTION + "Multicast RTP Systems SHOULD implement the optional + tables." + OBJECT rtpSenderInverseStartTime + MIN-ACCESS not-accessible + DESCRIPTION + "Multicast RTP Systems SHOULD implement the optional + tables." + OBJECT rtpRcvrInverseStartTime + MIN-ACCESS not-accessible + DESCRIPTION + "Multicast RTP Systems SHOULD implement the optional + tables." + ::= { rtpCompliances 2 } +END -- cgit v1.2.3