OID reference

rtpConfigBasePort

1.3.6.1.4.1.4935.15.115.5

Description

UDP base port for the RTP/RTCP protocols. The RTP/RTCP ports are allocated starting from this base port. The unit may use two or four RTP/RTCP ports per FXS/FXO interface. It uses 2 ports in case of a standard call, while it uses 4 ports in other types of calls such as a conference call, a call transfer, etc. E.g.: le…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.4935.15.115 (rtpConfig)
Node code
5
Node name
rtpConfigBasePort
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.4935.15.115.5
URN notation
urn:oid:1.3.6.1.4.1.4935.15.115.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 4935 15 115 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixConfig(15) rtpConfig(115) rtpConfigBasePort(5)}
OID-IRI notation
  • /1/3/6/1/4/1/4935/15/115/5
  • /ISO/Identified-Organization/6/1/4/1/4935/15/115/5
  • /ISO/3/6/1/4/1/4935/15/115/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/4935/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/identified-organization/dod/internet/private/enterprise/mediatrix/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/identified-organization/dod/internet/private/enterprises/4935/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/identified-organization/dod/internet/private/enterprises/mediatrix/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/4935/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/mediatrix/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/identified-organization/dod/internet/private/vendor-objects/4935/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/identified-organization/dod/internet/private/vendor-objects/mediatrix/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/org/dod/internet/private/enterprise/4935/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/org/dod/internet/private/enterprise/mediatrix/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/org/dod/internet/private/enterprises/4935/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/org/dod/internet/private/enterprises/mediatrix/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/org/dod/internet/private/ldap-enterprise/4935/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/org/dod/internet/private/ldap-enterprise/mediatrix/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/org/dod/internet/private/vendor-objects/4935/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • /iso/org/dod/internet/private/vendor-objects/mediatrix/mediatrixConfig/rtpConfig/rtpConfigBasePort
  • Additional combinations skipped.

SNMP properties

Value type
Unsigned32
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
5004
Allowed ranges
1025–64535

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.4935.15.115.5.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

rtpConfigBasePort OBJECT-TYPE
            SYNTAX      Unsigned32 (1025..64535)
            MAX-ACCESS  read-write
            STATUS      current
            DESCRIPTION "UDP base port for the RTP/RTCP protocols.

                         The RTP/RTCP ports are allocated starting from this base port.

                         The unit may use two or four RTP/RTCP ports per FXS/FXO interface.

                         It uses 2 ports in case of a standard call, while it uses 4 ports
                         in other types of calls such as a conference call, a call transfer, etc.

                         E.g.: let's say for instance that a unit has two FXS interfaces and the
                         base port is defined on 5004:
                            - if there is currently no ongoing call and FXS connector 1 has an
                              incoming or outgoing call, it will use the RTP/RTCP ports 5004 and 5005.

                            - if there is currently a standard call on FXS connector 1 and FXS
                              connector 2 has a conference call, then FXS connector 2 will use
                              the RTP/RTCP ports 5006, 5007, 5008, and 5009, which are the next
                              available ports.

                         This variable’s semantics are different depending on protocol and/or
                         hardware platforms.
                         Please refer to the documentation shipped with your device for more details."
            DEFVAL { 5004 }
            ::=  {  rtpConfig 5 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

UDP base port for the RTP/RTCP protocols. The RTP/RTCP ports are allocated starting from this base port. The unit may use two or four RTP/RTCP ports per FXS/FXO interface. It uses 2 ports in case of a standard call, while it uses 4 ports in other types of calls such as a conference call, a call transfer, etc. E.g.: let's say for instance that a unit has two FXS interfaces and the base port is defined on 5004: - if there is currently no ongoing call and FXS connector 1 has an incoming or outgoing call, it will use the RTP/RTCP ports 5004 and 5005. - if there is currently a standard call on FXS connector 1 and FXS connector 2 has a conference call, then FXS connector 2 will use the RTP/RTCP ports 5006, 5007, 5008, and 5009, which are the next available ports. This variable’s semantics are different depending on protocol and/or hardware platforms. Please refer to the documentation shipped with your device for more details.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

rtpConfigBasePort · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: rtpConfigBasePort

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rtpConfigBasePort",
    "OBJECT-TYPE",
    "SYNTAX",
    "Unsigned32",
    "(",
    "1025",
    ".",
    ".",
    "64535",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"UDP base port for the RTP/RTCP protocols. The RTP/RTCP ports are allocated starting from this base port. The unit may use two or four RTP/RTCP ports per FXS/FXO interface. It uses 2 ports in case of a standard call, while it uses 4 ports in other types of calls such as a conference call, a call transfer, etc. E.g.: let's say for instance that a unit has two FXS interfaces and the base port is defined on 5004: - if there is currently no ongoing call and FXS connector 1 has an incoming or outgoing call, it will use the RTP/RTCP ports 5004 and 5005. - if there is currently a standard call on FXS connector 1 and FXS connector 2 has a conference call, then FXS connector 2 will use the RTP/RTCP ports 5006, 5007, 5008, and 5009, which are the next available ports. This variable’s semantics are different depending on protocol and/or hardware platforms. Please refer to the documentation shipped with your device for more details.\"",
    "DEFVAL",
    "{",
    "5004",
    "}",
    "::=",
    "{",
    "rtpConfig",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Unsigned32",
      [
        "integerSubType",
        [
          [
            1025,
            64535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "UDP base port for the RTP/RTCP protocols. The RTP/RTCP ports are allocated starting from this base port. The unit may use two or four RTP/RTCP ports per FXS/FXO interface. It uses 2 ports in case of a standard call, while it uses 4 ports in other types of calls such as a conference call, a call transfer, etc. E.g.: let's say for instance that a unit has two FXS interfaces and the base port is defined on 5004: - if there is currently no ongoing call and FXS connector 1 has an incoming or outgoing call, it will use the RTP/RTCP ports 5004 and 5005. - if there is currently a standard call on FXS connector 1 and FXS connector 2 has a conference call, then FXS connector 2 will use the RTP/RTCP ports 5006, 5007, 5008, and 5009, which are the next available ports. This variable’s semantics are different depending on protocol and/or hardware platforms. Please refer to the documentation shipped with your device for more details."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      5004
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.4935)

Perron Stephane