In order for the Gatekeeper to determine if an endpoint is turned off,
or has otherwise entered a failure mode, the Gatekeeper may use the Information
Request (IRQ) to poll the endpoints at the certain interval (in seconds).
THE IRQ INTERVAL controls the frequency the gk sends IRQ messages.
This message is sent to all on-line endpoints registered as dynamic in order
to verify they are really on-line. This is done to detect terminals that
shut off without sending the required URQ message that notifies the gk that
they are no longer on-line.
Endpoints failing to respond too many times have their dynamic properties
unregistered. Choosing the desired interval should take into account the
following factors :
IRQ messages add to the traffic already present over the network and the
shorter the interval the more IRQ messages will be sent. On the other hand the
longer the delay the longer it will take for the gk to detect dynamic
registrations that have ceased to actually be on-line. Note that the
IRQ interval relates to each endpoint and the actual number of the IRQ messages
the gk will create should be multiplied by the number of endpoints
registered dynamically.
Parsed from file Rad0485.MIB.txt
Company: None
Module: OPTIMUX-MIB
In order for the Gatekeeper to determine if an endpoint is turned off,
or has otherwise entered a failure mode, the Gatekeeper may use the Information
Request (IRQ) to poll the endpoints at the certain interval (in seconds).
THE IRQ INTERVAL controls the frequency the gk sends IRQ messages.
This message is sent to all on-line endpoints registered as dynamic in order
to verify they are really on-line. This is done to detect terminals that
shut off without sending the required URQ message that notifies the gk that
they are no longer on-line.
Endpoints failing to respond too many times have their dynamic properties
unregistered. Choosing the desired interval should take into account the
following factors :
IRQ messages add to the traffic already present over the network and the
shorter the interval the more IRQ messages will be sent. On the other hand the
longer the delay the longer it will take for the gk to detect dynamic
registrations that have ceased to actually be on-line. Note that the
IRQ interval relates to each endpoint and the actual number of the IRQ messages
the gk will create should be multiplied by the number of endpoints
registered dynamically.
Parsed from file OPTIMUX-MIB.mib
Module: OPTIMUX-MIB
gkGenIrqInterval OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "In order for the Gatekeeper to determine if an endpoint is turned off, or has otherwise entered a failure mode, the Gatekeeper may use the Information Request (IRQ) to poll the endpoints at the certain interval (in seconds). THE IRQ INTERVAL controls the frequency the gk sends IRQ messages. This message is sent to all on-line endpoints registered as dynamic in order to verify they are really on-line. This is done to detect terminals that shut off without sending the required URQ message that notifies the gk that they are no longer on-line. Endpoints failing to respond too many times have their dynamic properties unregistered. Choosing the desired interval should take into account the following factors : IRQ messages add to the traffic already present over the network and the shorter the interval the more IRQ messages will be sent. On the other hand the longer the delay the longer it will take for the gk to detect dynamic registrations that have ceased to actually be on-line. Note that the IRQ interval relates to each endpoint and the actual number of the IRQ messages the gk will create should be multiplied by the number of endpoints registered dynamically." ::= {gkGenEntry 6}
gkGenIrqInterval OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "In order for the Gatekeeper to determine if an endpoint is turned off, or has otherwise entered a failure mode, the Gatekeeper may use the Information Request (IRQ) to poll the endpoints at the certain interval (in seconds). THE IRQ INTERVAL controls the frequency the gk sends IRQ messages. This message is sent to all on-line endpoints registered as dynamic in order to verify they are really on-line. This is done to detect terminals that shut off without sending the required URQ message that notifies the gk that they are no longer on-line. Endpoints failing to respond too many times have their dynamic properties unregistered. Choosing the desired interval should take into account the following factors : IRQ messages add to the traffic already present over the network and the shorter the interval the more IRQ messages will be sent. On the other hand the longer the delay the longer it will take for the gk to detect dynamic registrations that have ceased to actually be on-line. Note that the IRQ interval relates to each endpoint and the actual number of the IRQ messages the gk will create should be multiplied by the number of endpoints registered dynamically." ::= {gkGenEntry 6}
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.164.3.1.7.2.1.1 | gkGenCallMode | 0 | 0 | This parameters shows whether the calls will go through the GK (routed) or whether the calls will be direct from Endpoint to End… |
1.3.6.1.4.1.164.3.1.7.2.1.2 | gkGenMaxConnections | 0 | 0 | MAX no. of connections enabled by the GK to take place simultaneously. If the MAX no. of calls is exceeded, a busy signal will b… |
1.3.6.1.4.1.164.3.1.7.2.1.3 | gkGenDefaultDistance | 0 | 0 | The Distance allowed for endpoints that are registered dynamically. |
1.3.6.1.4.1.164.3.1.7.2.1.4 | gkGenOutOfZoneDist | 0 | 0 | The Distance allowed for an out of zone endpoint that is making a call through the gatekeeper. |
1.3.6.1.4.1.164.3.1.7.2.1.5 | gkGenCallAcceptPolicy | 0 | 0 | Defines the policy concerning the incoming phone calls. The importance of this parameter is for bidding and security matters. Acc… |
1.3.6.1.4.1.164.3.1.7.2.1.7 | gkGenQ931Port | 0 | 0 | Q.931 Port no. |
1.3.6.1.4.1.164.3.1.7.2.1.8 | gkGenRasPort | 0 | 0 | RAS Port no. |
1.3.6.1.4.1.164.3.1.7.2.1.9 | gkGenRegPolicy | 0 | 0 | Policy of dynamic registrations in the Gatekeeper. The GK will act according to the following policies: Accept All - The GK … |
1.3.6.1.4.1.164.3.1.7.2.1.10 | gkGenZoneId | 0 | 0 | Zone Identifier: 1 or 2 digits, (0-9)(1-9). |