OID reference

h323SingleRegLightweightEnable

1.3.6.1.4.1.4935.20.30.1.1.10.15

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 tim…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.4935.20.30.1.1.10 (h323RegistrationSingleRegistration)
Node code
15
Node name
h323SingleRegLightweightEnable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.4935.20.30.1.1.10.15
URN notation
urn:oid:1.3.6.1.4.1.4935.20.30.1.1.10.15
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 4935 20 30 1 1 10 15}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) mediatrix(4935) mediatrixIpTelephonySignaling(20) h323(30) h323RegistrationMIB(1) h323RegistrationMIBObjects(1) h323RegistrationSingleRegistration(10) h323SingleRegLightweightEnable(15)}
OID-IRI notation
  • /1/3/6/1/4/1/4935/20/30/1/1/10/15
  • /ISO/Identified-Organization/6/1/4/1/4935/20/30/1/1/10/15
  • /ISO/3/6/1/4/1/4935/20/30/1/1/10/15
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/4935/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/identified-organization/dod/internet/private/enterprise/mediatrix/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/identified-organization/dod/internet/private/enterprises/4935/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/identified-organization/dod/internet/private/enterprises/mediatrix/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/4935/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/mediatrix/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/identified-organization/dod/internet/private/vendor-objects/4935/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/identified-organization/dod/internet/private/vendor-objects/mediatrix/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/org/dod/internet/private/enterprise/4935/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/org/dod/internet/private/enterprise/mediatrix/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/org/dod/internet/private/enterprises/4935/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/org/dod/internet/private/enterprises/mediatrix/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/org/dod/internet/private/ldap-enterprise/4935/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/org/dod/internet/private/ldap-enterprise/mediatrix/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/org/dod/internet/private/vendor-objects/4935/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • /iso/org/dod/internet/private/vendor-objects/mediatrix/mediatrixIpTelephonySignaling/h323/h323RegistrationMIB/h323RegistrationMIBObjects/h323RegistrationSingleRegistration/h323SingleRegLightweightEnable
  • Additional combinations skipped.

SNMP properties

Value type
MxEnableState
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
enable

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

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 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

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.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

h323SingleRegLightweightEnable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

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"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.4935)

Perron Stephane

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.4935.20.30.1.1.10.5 h323SingleRegGkDiscoveryMode00
1.3.6.1.4.1.4935.20.30.1.1.10.10 h323SingleRegRetryTime00
1.3.6.1.4.1.4935.20.30.1.1.10.20 h323SingleRegLightweightTimeToLive00
1.3.6.1.4.1.4935.20.30.1.1.10.25 h323TermSingleRegAsGateway00
1.3.6.1.4.1.4935.20.30.1.1.10.30 h323SingleRegRasPortSource00
1.3.6.1.4.1.4935.20.30.1.1.10.35 h323SingleRegStaticRasPort00
1.3.6.1.4.1.4935.20.30.1.1.10.40 h323SingleRegCallSignalingPortSource00
1.3.6.1.4.1.4935.20.30.1.1.10.45 h323SingleRegStaticCallSignalingPort00