OID reference

h323AliasesConfigured

1.3.6.1.4.1.4935.20.30.15.1.5.1.10

Description

The aliases that uniquely identify the line. These are the configured aliases. This variable only applies to unit of type terminal. Each line must be configured with unique aliases. A line can be configured with zero, one or two aliases. A line can be configured with two aliases of the same type or two aliases of diff…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.4935.20.30.15.1.5.1 (h323AliasesIfAliasesEntry)
Node code
10
Node name
h323AliasesConfigured
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.4935.20.30.15.1.5.1.10
URN notation
urn:oid:1.3.6.1.4.1.4935.20.30.15.1.5.1.10
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 4935 20 30 15 1 5 1 10}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323AliasesMIB(15) h323AliasesMIBObjects(1) h323AliasesIfAliasesTable(5) h323AliasesIfAliasesEntry(1) h323AliasesConfigured(10)}
OID-IRI notation
  • /1/3/6/1/4/1/4935/20/30/15/1/5/1/10
  • /ISO/Identified-Organization/6/1/4/1/4935/20/30/15/1/5/1/10
  • /ISO/3/6/1/4/1/4935/20/30/15/1/5/1/10
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/4935/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/identified-organization/dod/internet/private/enterprise/mediatrix/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/identified-organization/dod/internet/private/enterprises/4935/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/identified-organization/dod/internet/private/enterprises/mediatrix/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/4935/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/mediatrix/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/identified-organization/dod/internet/private/vendor-objects/4935/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/identified-organization/dod/internet/private/vendor-objects/mediatrix/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/org/dod/internet/private/enterprise/4935/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/org/dod/internet/private/enterprise/mediatrix/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/org/dod/internet/private/enterprises/4935/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/org/dod/internet/private/enterprises/mediatrix/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/org/dod/internet/private/ldap-enterprise/4935/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/org/dod/internet/private/ldap-enterprise/mediatrix/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/org/dod/internet/private/vendor-objects/4935/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • /iso/org/dod/internet/private/vendor-objects/mediatrix/mediatrixIpTelephonySignaling/h323/h323AliasesMIB/h323AliasesMIBObjects/h323AliasesIfAliasesTable/h323AliasesIfAliasesEntry/h323AliasesConfigured
  • Additional combinations skipped.

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
""
Allowed size (octets)
0–63

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: ifIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.4935.20.30.15.1.5.1.10

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.

h323AliasesConfigured OBJECT-TYPE
            SYNTAX      OCTET STRING (SIZE (0..63))
            MAX-ACCESS  read-write
            STATUS      current
            DESCRIPTION "The aliases that uniquely identify the line. These are the configured aliases.
                         This variable only applies to unit of type terminal.

                         Each line must be configured with unique aliases.

                         A line can be configured with zero, one or two aliases. A line can be
                         configured with two aliases of the same type or two aliases of different types.

                         A line can be configured with E.164 aliases, H.323 ID aliases and party number
                         aliases. Transport ID aliases (IP addresses) are not allowed. The local IP
                         address of the unit is configured through ipAddressConfigLocalHost.

                         The configured aliases are included in the terminalAlias field of the
                         gatekeeperRequest and registrationRequest messages.

                         As an example, a line is configured with two aliases, '3460707' as E.164 alias
                         and 'user1' as H.323 ID alias. The following string is used to describe these
                         aliases:

                            E164=3460707;H323ID=user1

                         Each line must have at least one current alias (either configured or
                         confirmed). If a line has no alias, the unit locks this line. When a line is
                         locked, no call can be made/received from/to this line.

                         Refer to the administrator documentation for the description of the aliases
                         syntax.

                         Refer to the administrator documentation for the description of the configured,
                         confirmed and current aliases."
            DEFVAL { "" }
            ::=  {  h323AliasesIfAliasesEntry 10 }

Meaning

Descriptions

1 unique

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

The aliases that uniquely identify the line. These are the configured aliases. This variable only applies to unit of type terminal. Each line must be configured with unique aliases. A line can be configured with zero, one or two aliases. A line can be configured with two aliases of the same type or two aliases of different types. A line can be configured with E.164 aliases, H.323 ID aliases and party number aliases. Transport ID aliases (IP addresses) are not allowed. The local IP address of the unit is configured through ipAddressConfigLocalHost. The configured aliases are included in the terminalAlias field of the gatekeeperRequest and registrationRequest messages. As an example, a line is configured with two aliases, '3460707' as E.164 alias and 'user1' as H.323 ID alias. The following string is used to describe these aliases: E164=3460707;H323ID=user1 Each line must have at least one current alias (either configured or confirmed). If a line has no alias, the unit locks this line. When a line is locked, no call can be made/received from/to this line. Refer to the administrator documentation for the description of the aliases syntax. Refer to the administrator documentation for the description of the configured, confirmed and current aliases.

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

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

Status in source: current.

Names: h323AliasesConfigured

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h323AliasesConfigured",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "(",
    "SIZE",
    "(",
    "0",
    ".",
    ".",
    "63",
    ")",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The aliases that uniquely identify the line. These are the configured aliases. This variable only applies to unit of type terminal. Each line must be configured with unique aliases. A line can be configured with zero, one or two aliases. A line can be configured with two aliases of the same type or two aliases of different types. A line can be configured with E.164 aliases, H.323 ID aliases and party number aliases. Transport ID aliases (IP addresses) are not allowed. The local IP address of the unit is configured through ipAddressConfigLocalHost. The configured aliases are included in the terminalAlias field of the gatekeeperRequest and registrationRequest messages. As an example, a line is configured with two aliases, '3460707' as E.164 alias and 'user1' as H.323 ID alias. The following string is used to describe these aliases: E164=3460707;H323ID=user1 Each line must have at least one current alias (either configured or confirmed). If a line has no alias, the unit locks this line. When a line is locked, no call can be made/received from/to this line. Refer to the administrator documentation for the description of the aliases syntax. Refer to the administrator documentation for the description of the configured, confirmed and current aliases.\"",
    "DEFVAL",
    "{",
    [
      "literal",
      "2222"
    ],
    "}",
    "::=",
    "{",
    "h323AliasesIfAliasesEntry",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING",
      [
        "octetStringSubType",
        [
          [
            0,
            63
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The aliases that uniquely identify the line. These are the configured aliases. This variable only applies to unit of type terminal. Each line must be configured with unique aliases. A line can be configured with zero, one or two aliases. A line can be configured with two aliases of the same type or two aliases of different types. A line can be configured with E.164 aliases, H.323 ID aliases and party number aliases. Transport ID aliases (IP addresses) are not allowed. The local IP address of the unit is configured through ipAddressConfigLocalHost. The configured aliases are included in the terminalAlias field of the gatekeeperRequest and registrationRequest messages. As an example, a line is configured with two aliases, '3460707' as E.164 alias and 'user1' as H.323 ID alias. The following string is used to describe these aliases: E164=3460707;H323ID=user1 Each line must have at least one current alias (either configured or confirmed). If a line has no alias, the unit locks this line. When a line is locked, no call can be made/received from/to this line. Refer to the administrator documentation for the description of the aliases syntax. Refer to the administrator documentation for the description of the configured, confirmed and current aliases."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "\"\""
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.4935)

Perron Stephane

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.4935.20.30.15.1.5.1.5 h323AliasesGroupIndex00
1.3.6.1.4.1.4935.20.30.15.1.5.1.15 h323AliasesCurrent00