rtpSessionLocAddr
RTP-MIB ·
.1.3.6.1.2.1.87.1.3.1.4
Object
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.
Context
- MIB
- RTP-MIB
- OID
.1.3.6.1.2.1.87.1.3.1.4- Type
- column
- Access
- readonly
- Status
- current
- Parent
- rtpSessionEntry
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workWalk the column to discover its indexed instances, or supply every index to read one instance.
Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'RTP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'RTP-MIB::rtpSessionLocAddr'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'RTP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'RTP-MIB::rtpSessionLocAddr.<rtpSessionIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'RTP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'RTP-MIB::rtpSessionLocAddr'
Syntax
Type Description
Denotes a transport service address.
A TAddress value is always interpreted within the context of a
TDomain value. Thus, each definition of a TDomain value must
be accompanied by a definition of a textual convention for use
with that TDomain. Some possible textual conventions, such as
SnmpUDPAddress for snmpUDPDomain, are defined in the SNMPv2-TM
MIB module. Other possible textual conventions are defined in
other MIB modules.
Values & Constraints
Type Constraints
range: 1..255
Conformance
Member of
Compliance refinements
rtpMonitorCompliance
noaccess
RTP monitor sourcing of RTP or RTCP data packets
is OPTIONAL and implementation of this object is
OPTIONAL.
is OPTIONAL and implementation of this object is
OPTIONAL.