Status in source: current.
Names: h323SingleRegLightweightEnable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"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",
"}",
"::=",
"{",
"h323RegistrationSingleRegistration",
"15",
"}"
],
"syntax_tree": [
[
"row",
"MxEnableState"
],
null,
[
"MaxAccessPart",
"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."
],
null,
null,
null,
[
"DEFVAL",
"enable"
]
]
}
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: MX-H323-REGISTRATION-MIB
See published definition above
Module imports
{'MX-TC': ['MxIpAddress', 'MxIpPort', 'MxIpDhcpSiteSpecificCode', 'MxEnableState'], 'MX-SMI': ['ipAddressStatus', 'ipAddressConfig'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Unsigned32'], 'MX-H323-MIB': ['h323', 'ipAddressStatusH323', 'ipAddressConfigH323Static', 'ipAddressConfigH323Dhcp'], 'RFC1213-MIB': ['ifIndex'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE'], 'MX-LINE-GROUPING-MIB': ['groupIndex']}
· Download MX-H323-REGISTRATION-MIB
Related source files and packages: