OID reference

sipOutboundProxyConfig

1.3.6.1.4.1.4935.99.10.1.30

Description

This variable provisions the type of routing that the configured outbound proxy does. looseRouter : This is the most current method for SIP routing, as per RFC3261, and will become the standard behavior once RFC3261 compliance is achieved. See sipOutboundProxyHost in the SIP MIB for a description. strictRouter : Pre-R…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.4935.99.10.1 (sipExperimentalMIBObjects)
Node code
30
Node name
sipOutboundProxyConfig
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.4935.99.10.1.30
URN notation
urn:oid:1.3.6.1.4.1.4935.99.10.1.30
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 4935 99 10 1 30}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixExperimental(99) sipExperimentalMIB(10) sipExperimentalMIBObjects(1) sipOutboundProxyConfig(30)}
OID-IRI notation
  • /1/3/6/1/4/1/4935/99/10/1/30
  • /ISO/Identified-Organization/6/1/4/1/4935/99/10/1/30
  • /ISO/3/6/1/4/1/4935/99/10/1/30
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/4935/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/identified-organization/dod/internet/private/enterprise/mediatrix/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/identified-organization/dod/internet/private/enterprises/4935/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/identified-organization/dod/internet/private/enterprises/mediatrix/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/4935/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/mediatrix/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/identified-organization/dod/internet/private/vendor-objects/4935/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/identified-organization/dod/internet/private/vendor-objects/mediatrix/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/org/dod/internet/private/enterprise/4935/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/org/dod/internet/private/enterprise/mediatrix/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/org/dod/internet/private/enterprises/4935/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/org/dod/internet/private/enterprises/mediatrix/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/org/dod/internet/private/ldap-enterprise/4935/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/org/dod/internet/private/ldap-enterprise/mediatrix/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/org/dod/internet/private/vendor-objects/4935/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • /iso/org/dod/internet/private/vendor-objects/mediatrix/mediatrixExperimental/sipExperimentalMIB/sipExperimentalMIBObjects/sipOutboundProxyConfig
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
looseRouter

Enumerated values

ValueName
0looseRouter
1strictRouter

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.99.10.1.30.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.

sipOutboundProxyConfig OBJECT-TYPE
        SYNTAX      INTEGER {
                             looseRouter(0),
                             strictRouter(1)
                            }
        MAX-ACCESS  read-write
        STATUS      current
        DESCRIPTION "This variable provisions the type of routing that the configured outbound proxy
                     does.

                     looseRouter :
                        This is the most current method for SIP routing, as per RFC3261, and will
                        become the standard behavior once RFC3261 compliance is achieved.

                        See sipOutboundProxyHost in the SIP MIB for a description.

                     strictRouter :
                        Pre-RFC3261, RFC2543 compatible SIP routing.

                        The initial route for all SIP requests will contain the home domain proxy
                        address (the Request-URI). Requests will be directed to the outbound proxy.

                        In other words, the Request-URI is constructed as usual, using the home domain
                        proxy and the username, but is used in the route set. The Request-URI is filled
                        by the outbound proxy address.


                     Also see sipHomeDomainProxyHost."
        DEFVAL { looseRouter }
        ::=  { sipExperimentalMIBObjects 30 }

Meaning

Descriptions

1 unique

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

This variable provisions the type of routing that the configured outbound proxy does. looseRouter : This is the most current method for SIP routing, as per RFC3261, and will become the standard behavior once RFC3261 compliance is achieved. See sipOutboundProxyHost in the SIP MIB for a description. strictRouter : Pre-RFC3261, RFC2543 compatible SIP routing. The initial route for all SIP requests will contain the home domain proxy address (the Request-URI). Requests will be directed to the outbound proxy. In other words, the Request-URI is constructed as usual, using the home domain proxy and the username, but is used in the route set. The Request-URI is filled by the outbound proxy address. Also see sipHomeDomainProxyHost.

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

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

Status in source: current.

Names: sipOutboundProxyConfig

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "sipOutboundProxyConfig",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "looseRouter",
    "(",
    "0",
    ")",
    ",",
    "strictRouter",
    "(",
    "1",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This variable provisions the type of routing that the configured outbound proxy does. looseRouter : This is the most current method for SIP routing, as per RFC3261, and will become the standard behavior once RFC3261 compliance is achieved. See sipOutboundProxyHost in the SIP MIB for a description. strictRouter : Pre-RFC3261, RFC2543 compatible SIP routing. The initial route for all SIP requests will contain the home domain proxy address (the Request-URI). Requests will be directed to the outbound proxy. In other words, the Request-URI is constructed as usual, using the home domain proxy and the username, but is used in the route set. The Request-URI is filled by the outbound proxy address. Also see sipHomeDomainProxyHost.\"",
    "DEFVAL",
    "{",
    "looseRouter",
    "}",
    "::=",
    "{",
    "sipExperimentalMIBObjects",
    "30",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "looseRouter",
            0
          ],
          [
            "strictRouter",
            1
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This variable provisions the type of routing that the configured outbound proxy does. looseRouter : This is the most current method for SIP routing, as per RFC3261, and will become the standard behavior once RFC3261 compliance is achieved. See sipOutboundProxyHost in the SIP MIB for a description. strictRouter : Pre-RFC3261, RFC2543 compatible SIP routing. The initial route for all SIP requests will contain the home domain proxy address (the Request-URI). Requests will be directed to the outbound proxy. In other words, the Request-URI is constructed as usual, using the home domain proxy and the username, but is used in the route set. The Request-URI is filled by the outbound proxy address. Also see sipHomeDomainProxyHost."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "looseRouter"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.4935)

Perron Stephane

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.4935.99.10.1.5 sipNatCustom22
1.3.6.1.4.1.4935.99.10.1.25 sipUnregisteredPortBehavior00
1.3.6.1.4.1.4935.99.10.1.80 sipEnforceOfferAnswerModel00
1.3.6.1.4.1.4935.99.10.1.85 sipAllowMediaReactivationInAnswerEnable00
1.3.6.1.4.1.4935.99.10.1.90 sipAllowAudioAndImageNegotiationEnable00
1.3.6.1.4.1.4935.99.10.1.95 sipCodecOrderInAnswer00
1.3.6.1.4.1.4935.99.10.1.130 sipRtpUdpChecksumEnable00