h323GroupMultipleRegLightweightEnable

Indicates if the lightweight registration functionality is enabled.
              
disable : the group does not use the lightweight registration functionality.
          The group does not include the timeToLive field in the
          registrationRequest message.
              
enable  : the group uses the lightweight registration functionality. The group
          includes the timeToLive field in the registrationRequest message.
              
For the lightweight registration functionality, the following RAS message
fields are used:
              
- keepAlive field of the registrationRequest message. The keepAlive field is
  either true or false.
              
- timeToLive field of the registrationRequest and registrationConfirm messages.
  The timeToLive field is a number of seconds.
              
- A full registrationRequest message has the keepAlive field set to false.
              
- lightweight registrationRequest message has the keepAlive field set to true.
              
When the lightweight registration functionality is enabled, the group follows
these steps:
              
step 1 : the group sends a first registrationRequest message to the gatekeeper.
         This registrationRequest message has the keepAlive field set to false
         and contains the timeToLive field. The value of the timeToLive field
         is configurable.
              
step 2 : If the registrationConfirm message contains the timeToLive field, the
         group sends lightweight registrationRequest messages. The interval
         between each lightweight registrationRequest message is one-third of
         the timeToLive value from the gatekeeper (from the registrationConfirm
         message). On a network with heavy traffic, a lightweight
         registrationRequest message could arrive a few seconds late at the
         gatekeeper. Furthermore, since the RAS channel between a group and a
         gatekeeper is unreliable (UDP), a lightweight registrationRequest
         message may never arrive at the gatekeeper. These problems are avoided
         by using an interval equal to one-third the timeToLive value of the
         registrationConfirm message.
              
step 3 : If the registrationConfirm message does not contain the timeToLive
         field, the group does not send lightweight registrationRequest
         messages.

MIB

MX-H323-REGISTRATION-MIB

OID

.1.3.6.1.4.1.4935.20.30.1.1.17.1.20

Type

column

Access

readwrite

Status

current

Parent

h323RegistrationMultipleRegistrationGroupEntry