---
oid: "1.3.6.1.2.1.87.1.3.1.4"
short-description: "rtpSessionLocAddr OBJECT-TYPE"
last-modified: "2021-02-10"
parent-oid: "1.3.6.1.2.1.87.1.3.1"
---

## OID: `1.3.6.1.2.1.87.1.3.1.4`

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

### Description

```asn1
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."
```

**Classification:** MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 2959](https://www.rfc-editor.org/rfc/rfc2959.html).

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.