---
oid: "1.3.6.1.4.1.4935.20.30.1.1.10.5"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 4935 mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegGkDiscoveryMode(5)}"
description: "h323SingleRegGkDiscoveryMode OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2024-09-20"
---

## OID : `1.3.6.1.4.1.4935.20.30.1.1.10.5`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 4935 mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegGkDiscoveryMode(5)}
```

### Description

```asn1
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}
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

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