|
|
This is the manual for GNU Gatekeeper 2.3.2.
A manual for your version is in your GnuGk download archive.
Chapters:
Contents ·
Introduction ·
Installation ·
Getting started ·
Basic Config ·
Routed Mode & Proxy ·
Routing ·
RAS Config ·
Authentication ·
Accounting ·
Neighbors ·
Per Endpoint Config ·
Advanced Config ·
Monitoring
If the destination of an ARQ is unknown, the gatekeeper sends LRQs to
its neighbors to ask if they have the destination endpoint.
A neighbor is selected if one of its prefixes matches the destination
or it has the ``*'' prefix. More than one prefix may be specified.
You can use special characters ``.'' to do wildcard
matching and ``!'' to disable a specific prefix.
Conversely, the gatekeeper will only reply to LRQs sent from neighbors
defined in this section.
If you specify an empty prefix, no LRQ will be sent to that neighbor,
but the gatekeeper will accept LRQs from it. The empty prefix is denoted
by a single semicolon appended to the neighbor entry. Example:
GK1=192.168.0.5;
If you skip the semicolon, LRQs will be always sent to this neighbor.
The password field is used to authenticate LRQs from that neighbor.
See section
[Gatekeeper::Auth] for details.
Whether a call is accepted from a neighbor also depends on the AcceptNeighborsCalls switch in the
[RoutedMode] section.
The gatekeeper types have the following characteristics:
GnuGk
When in doubt, use the
GnuGk gatekeeper type. This also activates H.460.23 / H.460.24.
CiscoGk
GnuGk will pretend to be a Cisco gatekeeper and send fake manufacturer data.
ClarentGk
Clarent gatekeeper can't decode nonStandardData in LRQs, so GnuGk will filter it out.
GlonetGk
Limited support for LRQ forwarding.
GKID="GnuGk" | "CiscoGk" | "ClarentGk" | "GlonetGk"
- Example:
[RasSrv::Neighbors]
GK1=CiscoGk
GK2=GnuGk
[Neighbor::GK1]
GatekeeperIdentifier=GK1
Host=192.168.1.1
SendPrefixes=02
AcceptPrefixes=*
ForwardLRQ=always
[Neighbor::GK2]
GatekeeperIdentifier=GK2
Host=192.168.1.2
SendPrefixes=03,0048
AcceptPrefixes=0049,001
ForwardHopCount=2
ForwardLRQ=depends
The [RasSrv::Neighbors] section is only used to specify the gatekeeper type. The configuration for each neighbor is placed in a separate section.
Defines some features of LRQ and LCF.
NeighborTimeout=1
Default: 2
Timeout value in seconds to wait for responses from neighbors.
If no neighbor responds before the timeout, the gatekeeper will
reply with an ARJ to the endpoint sending the ARQ.
SendRetries=4
Default: 2
Number of tries to send LRQ to neighbors.
If there is no response from neighbors after retries timeout, the gatekeeper will
reply with a LRJ to the endpoint sending the LRQ.
ForwardHopCount=2
Default: N/A
If the gatekeeper receives a LRQ that the destination is unknown
it may forward this message to its neighbors.
When the gatekeeper receives a LRQ and decides that the message
should be forwarded on to another gatekeeper, it first decrements
hopCount field of the LRQ.
If hopCount has reached 0, the gatekeeper shall not forward the message.
This option defines the number of gatekeepers through which a LRQ
may propagate. Note that it only affects the sender of LRQ, not the forwarder.
This setting can be overridden via the configuration section for a particular neighbor.
AcceptForwardedLRQ=1
Default: 1
Whether to accept an LRQ forwarded from neighbors.
This setting can be overridden with configuration
of a particular neighbor.
ForwardResponse=0
Default: 0
If the gatekeeper forwards a received LRQ message it can decide either
to receive the LCF response or to let it travel back directly to the LRQ
originator. Set this option to 1 if the gatekeeper needs to receive LCF
messages for forwarded LRQs. This setting can be overridden with configuration
of a particular neighbor.
ForwardLRQ=always | never | depends
Default: depends
This settings determines whether the received LRQ should be forwarded
or not. always forwards LRQ unconditionally, never blocks LRQ
forwarding, depends tells the gatekeeper to forward LRQ only if its
hop count is greater than 1. This setting can be overridden with configuration
of a particular neighbor.
AcceptNonNeighborLRQ=1
Default: 0
Whether to accept a LRQ forwarded from parties not defined as Neighbors.
This can be used with SRV routing policy to place calls to third party gatekeepers.
This should be used in conjunction with a LRQ Authentication policy.
AcceptNonNeighborLCF=1
Default: 0
This setting disables matching of the LRQ responder's IP address and
specified neighbor IP addresses in order to accept LCF message responses
from any IP address. This has primary importance when a
multiple level gatekeeper hierarchy is used without routed Q.931 signaling.
As a minimal security, only LRQ/LCF sequence numbers will be checked accordingly. This feature is required by the
national gatekeepers connected to the Global Dialing Scheme (GDS), see
http://www.vide.net/help/gdsintro.shtml
for more information.
WARNING: Enabling receiving LCF from other than the LRQ destination IP is a significant security risk.
Use this setting with extreme caution.
Sections starting with [Neighbor:: are specific for one neighbor. If
you define a [Neighbor::...] section, the default values of all
settings in
[RasSrv::LRQFeatures] will be applied to
this neighbor. You may override the global defaults through configuration options in
each neighbor-specific section.
GatekeeperIdentifier=GKID
Default: N/A
Gatekeeper identifier for this neighbor. If this option is not specified,
the identifier is taken from the second part of the Neighbor:: section name.
Host=192.168.1.1
Default: N/A
An IP address for this neighbor.
Password=secret
Default: N/A
A password to be used to validate crypto tokens received from incoming LRQs.
Not yet implemented, yet.
Dynamic=0
Default: 0
1 means that the IP address for this neighbor can change.
SendPrefixes=004,002:=1,001:=2
Default: N/A
A list of prefixes that this neighbor expects to receive LRQs for.
If '*' is specified, LRQs will always be sent to this neighbor.
A priority can be given to each prefix for each neighbor (using := syntax),
so in case of multiple LCF received from multiple neighbor, the one
with the highest priority will be selected to route the call.
One can also direct the gatekeeper to send LRQ to this neighbor
based on an alias type:
SendPrefixes=h323_ID,dialedDigits,001
AcceptPrefixes=*
Default: *
A list of prefixes that GnuGk will accept in LRQs received
from this neighbor. If '*' is specified, all LRQs will be accepted from this neighbor.
One can also direct the gatekeeper to accept LRQ from this neighbor
based on an alias type:
AcceptPrefixes=dialedDigits
ForwardHopCount=2
Default: N/A
If the gatekeeper receives an LRQ that the destination is either unknown,
it may forward this message to its neighbors.
When the gatekeeper receives an LRQ and decides that the message
should be forwarded on to another gatekeeper, it first decrements
hopCount field of the LRQ.
If hopCount has reached 0, the gatekeeper shall not forward the message.
This options defines the number of gatekeepers through which an LRQ
may propagate. Note it only affects the sender of LRQ, not the forwarder.
AcceptForwardedLRQ=1
Default: 1
Whether to accept an LRQ forwarded from this neighbor.
ForwardResponse=0
Default: 0
If the gatekeeper forwards received LRQ message it can decide either
to receive the LCF response or to let it travel back directly to the LRQ
originator. Set this option to "1" if the gatekeeper needs to receive LCF
messages for forwarded LRQs.
ForwardLRQ=always | never | depends
Default: depends
This settings determines whether the received LRQ should be forwarded
or not. always forwards LRQ unconditionally, never blocks LRQ
forwarding, depends tells the gatekeeper to forward LRQ only if its
hop count is greater than 1.
UseH46018=1
Default: 0
Enable H.460.18 keep-alive messages to this neighbor. Set this switch only on the H.460.18
client side that is supposed to send the keep-alive ServiceControlIndication (SCI) messages.
SendPassword=secret
Default: N/A
EXPERIMENTAL: The password to send to the neighbor (right now only used for H.460.18 SCI).
Next
Previous
Contents
Chapters:
Contents ·
Introduction ·
Installation ·
Getting started ·
Basic Config ·
Routed Mode & Proxy ·
Routing ·
RAS Config ·
Authentication ·
Accounting ·
Neighbors ·
Per Endpoint Config ·
Advanced Config ·
Monitoring
|
