h323GroupMultipleRegGkDiscoveryMode

MX-H323-REGISTRATION-MIB · .1.3.6.1.4.1.4935.20.30.1.1.17.1.10

Object

column r/w Enumeration
The gatekeeper discovery method used by the group of lines.
              
AUTOMATIC GATEKEEPER DISCOVERY METHOD
              
The group follows these steps until it registers successfully.
              
step 1 : the group 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 group. The group then sends a
         registrationRequest message to that gatekeeper. The gatekeeper
         responds with a registrationConfirm message. The group is now
         registered. If several gatekeepers accept the gatekeeper request, the
         group registers with the first gatekeeper that accepted the gatekeeper
         request (i.e. the gatekeeper that sent the first gatekeeperConfirm
         message received by the group).
              
step 3 : a gatekeeper that rejects the gatekeeper request sends a
         gatekeeperReject message to the group. The group does not initiate any
         action upon receipt of a gatekeeperReject message.
              
step 4 : if no gatekeeperConfirm message is received within a time-out, the
         group 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 group 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 group sends another gatekeeperRequest
         message.
              
MANUAL GATEKEEPER DISCOVERY METHOD
              
The unit is configured with a list of gatekeeper IP addresses. Each group uses
the same list of gatekeeper IP addresses.
              
The group follows these steps as long as it does not register successfully.
              
step 1 : the group 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 group, the group
         is now registered.
              
step 3 : if the gatekeeper rejects the registration request, i.e. the
         gatekeeper sends a registrationReject message to the group, the group
         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 group sends a registrationRequest message to the
         next gatekeeper IP address of the list.
              
step 5 : If the group the end of the list without registering successfully,
         the group waits before starting again at step 1. During this waiting
         period, the group does not send any registrationRequest message.

Context

MIB
MX-H323-REGISTRATION-MIB
OID
.1.3.6.1.4.1.4935.20.30.1.1.17.1.10
Type
column
Access
readwrite
Status
current
Parent
h323RegistrationMultipleRegistrationGroupEntry
Table
h323RegistrationMultipleRegistrationGroupTable
Siblings
8

Syntax

Enumeration

Values & Constraints

Enumerated Values
0automatic
1manual

Related Objects

Sibling Objects