OID reference

h323SingleRegGkDiscoveryMode

1.3.6.1.4.1.4935.20.30.1.1.10.5

Description

The gatekeeper discovery method used by the unit. AUTOMATIC GATEKEEPER DISCOVERY METHOD The unit follows these steps until it registers successfully. step 1 : the unit sends a gatekeeperRequest message on the well-known Discovery Multicast Address. Every gatekeeper on the same network (as the unit) receives the gateke…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.4935.20.30.1.1.10 (h323RegistrationSingleRegistration)
Node code
5
Node name
h323SingleRegGkDiscoveryMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.4935.20.30.1.1.10.5
URN notation
urn:oid:1.3.6.1.4.1.4935.20.30.1.1.10.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

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

Enumerated values

ValueName
0automatic
1manual

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

h323SingleRegGkDiscoveryMode OBJECT-TYPE
            SYNTAX      INTEGER {
                                  automatic(0),
                                  manual(1)
                                }
            MAX-ACCESS  read-write
            STATUS      current
            DESCRIPTION "The gatekeeper discovery method used by the unit.

                         AUTOMATIC GATEKEEPER DISCOVERY METHOD

                         The unit follows these steps until it registers successfully.

                         step 1 : the unit sends a gatekeeperRequest message on the well-known Discovery
                                  Multicast Address. Every gatekeeper on the same network (as the unit)
                                  receives the gatekeeperRequest message.

                         step 2 : a gatekeeper that accepts the gatekeeper request sends a
                                  gatekeeperConfirm message to the unit. The unit then sends a
                                  registrationRequest message to that gatekeeper. The gatekeeper
                                  responds with a registrationConfirm message. The unit is now
                                  registered. If several gatekeepers accept the gatekeeper request, the
                                  unit registers with the first gatekeeper that accepted the gatekeeper
                                  request (i.e. the gatekeeper that sent the first gatekeeperConfirm
                                  message received by the unit).

                         step 3 : a gatekeeper that rejects the gatekeeper request sends a
                                  gatekeeperReject message to the unit. The unit does not initiate any
                                  action upon receipt of a gatekeeperReject message.

                         step 4 : if no gatekeeperConfirm message is received within a time-out, the unit
                                  starts again at step 1. The calculation of the time-out starts as soon
                                  as the first gatekeeperRequest message is sent.

                         note   : after sending a gatekeeperRequest message, the unit only considers the
                                  first answer (the first gatekeeperConfirm message or the first
                                  gatekeeperReject message). If the first answer to be received is a
                                  gatekeeperReject message, the unit sends another gatekeeperRequest
                                  message.

                         MANUAL GATEKEEPER DISCOVERY METHOD

                         The unit is configured with a list of gatekeeper IP addresses.

                         The unit follows these steps until it registers successfully.

                         step 1 : the unit sends a registrationRequest message to the first gatekeeper IP
                                  address of the list.

                         step 2 : if the gatekeeper accepts the registration request, i.e. the
                                  gatekeeper sends a registrationConfirm message to the unit, the unit is
                                  now registered.

                         step 3 : if the gatekeeper rejects the registration request, i.e. the
                                  gatekeeper sends a registrationReject message to the unit, the unit
                                  sends a registrationRequest message to the next gatekeeper IP address
                                  of the list.

                         step 4 : if the registration request times-out, i.e. there is no answer from
                                  the gatekeeper, the unit sends a registrationRequest message to the
                                  next gatekeeper IP address of the list.

                         step 5 : If the unit reaches the end of the list without registering
                                  successfully, the unit waits before starting again at step 1. During
                                  this waiting period, the unit does not send any registrationRequest
                                  message."
            DEFVAL { manual }
            ::=  {  h323RegistrationSingleRegistration 5 }

Meaning

Descriptions

1 unique

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

The gatekeeper discovery method used by the unit. AUTOMATIC GATEKEEPER DISCOVERY METHOD The unit follows these steps until it registers successfully. step 1 : the unit sends a gatekeeperRequest message on the well-known Discovery Multicast Address. Every gatekeeper on the same network (as the unit) receives the gatekeeperRequest message. step 2 : a gatekeeper that accepts the gatekeeper request sends a gatekeeperConfirm message to the unit. The unit then sends a registrationRequest message to that gatekeeper. The gatekeeper responds with a registrationConfirm message. The unit is now registered. If several gatekeepers accept the gatekeeper request, the unit registers with the first gatekeeper that accepted the gatekeeper request (i.e. the gatekeeper that sent the first gatekeeperConfirm message received by the unit). step 3 : a gatekeeper that rejects the gatekeeper request sends a gatekeeperReject message to the unit. The unit does not initiate any action upon receipt of a gatekeeperReject message. step 4 : if no gatekeeperConfirm message is received within a time-out, the unit starts again at step 1. The calculation of the time-out starts as soon as the first gatekeeperRequest message is sent. note : after sending a gatekeeperRequest message, the unit only considers the first answer (the first gatekeeperConfirm message or the first gatekeeperReject message). If the first answer to be received is a gatekeeperReject message, the unit sends another gatekeeperRequest message. MANUAL GATEKEEPER DISCOVERY METHOD The unit is configured with a list of gatekeeper IP addresses. The unit follows these steps until it registers successfully. step 1 : the unit sends a registrationRequest message to the first gatekeeper IP address of the list. step 2 : if the gatekeeper accepts the registration request, i.e. the gatekeeper sends a registrationConfirm message to the unit, the unit is now registered. step 3 : if the gatekeeper rejects the registration request, i.e. the gatekeeper sends a registrationReject message to the unit, the unit sends a registrationRequest message to the next gatekeeper IP address of the list. step 4 : if the registration request times-out, i.e. there is no answer from the gatekeeper, the unit sends a registrationRequest message to the next gatekeeper IP address of the list. step 5 : If the unit reaches the end of the list without registering successfully, the unit waits before starting again at step 1. During this waiting period, the unit does not send any registrationRequest message.

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

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

Status in source: current.

Names: h323SingleRegGkDiscoveryMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h323SingleRegGkDiscoveryMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "automatic",
    "(",
    "0",
    ")",
    ",",
    "manual",
    "(",
    "1",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The gatekeeper discovery method used by the unit. AUTOMATIC GATEKEEPER DISCOVERY METHOD The unit follows these steps until it registers successfully. step 1 : the unit sends a gatekeeperRequest message on the well-known Discovery Multicast Address. Every gatekeeper on the same network (as the unit) receives the gatekeeperRequest message. step 2 : a gatekeeper that accepts the gatekeeper request sends a gatekeeperConfirm message to the unit. The unit then sends a registrationRequest message to that gatekeeper. The gatekeeper responds with a registrationConfirm message. The unit is now registered. If several gatekeepers accept the gatekeeper request, the unit registers with the first gatekeeper that accepted the gatekeeper request (i.e. the gatekeeper that sent the first gatekeeperConfirm message received by the unit). step 3 : a gatekeeper that rejects the gatekeeper request sends a gatekeeperReject message to the unit. The unit does not initiate any action upon receipt of a gatekeeperReject message. step 4 : if no gatekeeperConfirm message is received within a time-out, the unit starts again at step 1. The calculation of the time-out starts as soon as the first gatekeeperRequest message is sent. note : after sending a gatekeeperRequest message, the unit only considers the first answer (the first gatekeeperConfirm message or the first gatekeeperReject message). If the first answer to be received is a gatekeeperReject message, the unit sends another gatekeeperRequest message. MANUAL GATEKEEPER DISCOVERY METHOD The unit is configured with a list of gatekeeper IP addresses. The unit follows these steps until it registers successfully. step 1 : the unit sends a registrationRequest message to the first gatekeeper IP address of the list. step 2 : if the gatekeeper accepts the registration request, i.e. the gatekeeper sends a registrationConfirm message to the unit, the unit is now registered. step 3 : if the gatekeeper rejects the registration request, i.e. the gatekeeper sends a registrationReject message to the unit, the unit sends a registrationRequest message to the next gatekeeper IP address of the list. step 4 : if the registration request times-out, i.e. there is no answer from the gatekeeper, the unit sends a registrationRequest message to the next gatekeeper IP address of the list. step 5 : If the unit reaches the end of the list without registering successfully, the unit waits before starting again at step 1. During this waiting period, the unit does not send any registrationRequest message.\"",
    "DEFVAL",
    "{",
    "manual",
    "}",
    "::=",
    "{",
    "h323RegistrationSingleRegistration",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "automatic",
            0
          ],
          [
            "manual",
            1
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The gatekeeper discovery method used by the unit. AUTOMATIC GATEKEEPER DISCOVERY METHOD The unit follows these steps until it registers successfully. step 1 : the unit sends a gatekeeperRequest message on the well-known Discovery Multicast Address. Every gatekeeper on the same network (as the unit) receives the gatekeeperRequest message. step 2 : a gatekeeper that accepts the gatekeeper request sends a gatekeeperConfirm message to the unit. The unit then sends a registrationRequest message to that gatekeeper. The gatekeeper responds with a registrationConfirm message. The unit is now registered. If several gatekeepers accept the gatekeeper request, the unit registers with the first gatekeeper that accepted the gatekeeper request (i.e. the gatekeeper that sent the first gatekeeperConfirm message received by the unit). step 3 : a gatekeeper that rejects the gatekeeper request sends a gatekeeperReject message to the unit. The unit does not initiate any action upon receipt of a gatekeeperReject message. step 4 : if no gatekeeperConfirm message is received within a time-out, the unit starts again at step 1. The calculation of the time-out starts as soon as the first gatekeeperRequest message is sent. note : after sending a gatekeeperRequest message, the unit only considers the first answer (the first gatekeeperConfirm message or the first gatekeeperReject message). If the first answer to be received is a gatekeeperReject message, the unit sends another gatekeeperRequest message. MANUAL GATEKEEPER DISCOVERY METHOD The unit is configured with a list of gatekeeper IP addresses. The unit follows these steps until it registers successfully. step 1 : the unit sends a registrationRequest message to the first gatekeeper IP address of the list. step 2 : if the gatekeeper accepts the registration request, i.e. the gatekeeper sends a registrationConfirm message to the unit, the unit is now registered. step 3 : if the gatekeeper rejects the registration request, i.e. the gatekeeper sends a registrationReject message to the unit, the unit sends a registrationRequest message to the next gatekeeper IP address of the list. step 4 : if the registration request times-out, i.e. there is no answer from the gatekeeper, the unit sends a registrationRequest message to the next gatekeeper IP address of the list. step 5 : If the unit reaches the end of the list without registering successfully, the unit waits before starting again at step 1. During this waiting period, the unit does not send any registrationRequest message."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "manual"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.4935)

Perron Stephane

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.4935.20.30.1.1.10.10 h323SingleRegRetryTime00
1.3.6.1.4.1.4935.20.30.1.1.10.15 h323SingleRegLightweightEnable00
1.3.6.1.4.1.4935.20.30.1.1.10.20 h323SingleRegLightweightTimeToLive00
1.3.6.1.4.1.4935.20.30.1.1.10.25 h323TermSingleRegAsGateway00
1.3.6.1.4.1.4935.20.30.1.1.10.30 h323SingleRegRasPortSource00
1.3.6.1.4.1.4935.20.30.1.1.10.35 h323SingleRegStaticRasPort00
1.3.6.1.4.1.4935.20.30.1.1.10.40 h323SingleRegCallSignalingPortSource00
1.3.6.1.4.1.4935.20.30.1.1.10.45 h323SingleRegStaticCallSignalingPort00