---
oid: "1.3.6.1.4.1.4935.20.30.1.1.10.15"
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) h323SingleRegLightweightEnable(15)}"
description: "h323SingleRegLightweightEnable 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.15`

```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) h323SingleRegLightweightEnable(15)}
```

### Description

```asn1
h323SingleRegLightweightEnable OBJECT-TYPE
SYNTAX MxEnableState
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates if the lightweight registration functionality is enabled.
disable : the unit does not use the lightweight registration functionality. The
unit does not include the timeToLive field in the registrationRequest
message.
enable : the unit uses the lightweight registration functionality. The unit
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.
- A lightweight registrationRequest message has the keepAlive field set to
true.
When the lightweight registration functionality is enabled, the unit follows
these steps:
step 1 : the unit 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
unit 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 unit 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 unit does not send lightweight registrationRequest messages."
DEFVAL {enable}
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

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