Next Previous Contents

7. RAS Configuration

7.1 Section [ReplyToRasAddress]

Some messages from endpoints to the gatekeeper (GatekeeperRequest, RegistrationRequest and InfoRequestResponse) contain an element rasAddress where the endpoint tells the gatekeeper where to send the response to these messages. By default GnuGk will ignore this address and respond to the IP and port where it has received the request from. It does so, because some endpoints rely on this behavior and in case where eg. a NAT is used, the response may not reach the sender if it is sent to another IP and port. Usually endpoints will send the RAS messages from their RAS port anyway, so it doesn't make a difference.

This section allows you to define when GnuGk should use the rasAddress inside the message it has received instead of the address where it has received the message from.

Syntax:

network=True|False

The network is specified by an IP plus optional CIDR, eg. 192.168.1.0/24. The network specifies the IP where the RAS message is received from, the setting specifies whether to use the rasAddress. The default is not to use it. The rule for the network with the longest netmask is used (the most specific).

Example:

In this example messages from the 192.168.0.0/18 will use the rasAddress, except for messages coming from the 192.168.4.0/24 network.

[ReplyToRasAddress]
192.168.0.0/18=True
192.168.4.0/24=False

7.2 Section [RasSrv::GWPrefixes]

This section configures how dialed E.164 numbers are routed to a specific gateway.

Format:

gw-alias=prefix[:=priority][,prefix[:=priority],...]

Note that you must specify the alias of the gateway. If a gateway has registered with the specified alias, all numbers beginning with the prefixes are routed to that gateway. Special characters . and ! can be used here to match any digit or to disable the prefix. A priority can be given to each prefix for each gateway (using := syntax), so that if several gateways match the dialed number, the one with the highest prefix priority will be selected to route the call (when the ActivateFailover switch is ON, the call will be routed to all selected gateways in order of the prefix priority). A smaller value corresponds to a higher priority. Default value is 1. If the prefix priority and overlaps the GatewayPriority (see section [EP::...]), the prefix priority will be preferred.

In the following example, the gateway "test-gw" will be responsible for prefixes "02" and "03" with a priority of 3, and for "04" with a priority of 1.

Example:

test-gw=02,03:=3,04:=1

7.3 Section [RasSrv::PermanentEndpoints]

In this section you may configure endpoints that don't have RAS support or that you don't want to be expired. Their records will always remain in the registration table of the gatekeeper. However, you can still unregister it via the status port. Special characters . and ! can be used with prefixes here to match any digit and disable the prefix. You may use := syntax to set a prefix priority in the same manner as in [RasSrv::GWPrefixes] section.

Make sure you add at least one prefix for all gateways, even if you assign the prefixes elsewhere (eg. in the [EP::...] section), otherwise the endpoint won't be considered a gateway and those settings won't apply!

Gateway entries may also optionally include vendor information which is stored with the gateway record

Format:

IP[:port]=alias[,alias,...;prefix[:=priority][,prefix[:=priority]]...;[vendor,product]

Example:

For gateway,

10.0.1.5=MyGW;009,008:=2,0.7:=3
10.0.1.5=MyGW;009,008:=2,0.7:=3;yate,4.1.0
For terminal,
10.0.1.10:1720=700

7.4 Section [RasSrv::RRQFeatures]

7.5 Section [RasSrv::ARQFeatures]

7.6 Section [RasSrv::AssignedAlias]

This allows the assigning of aliases to endpoints as they register, allowing them to set their fully qualified E.164 or URI addresses.

Example:

[RasSrv::AssignedAlias]
1234=3323465777,me@mysite.com 

7.7 Section [AssignedAliases::SQL]

This section configures GnuGk to read the assigned aliases from a database. You can use the same database parameters as defined in [SQLPasswordAuth].

7.8 Section [RasSrv::AlternateGatekeeper]

This section allows you to override the global definition of AlternateGKs from the [Gatekeeper::Main] section for certain IPs or IP ranges. See there for a detailed definition of the config options.

The network is specified by an IP plus optional CIDR, eg. 192.168.1.0/24. The rule for the network with the longest netmask is used (the most specific).

Example:

In this example, 192.168.1.10 gets assigned GnuGk10 as alternate gatekeeper, while the rest of the 192.168.0.0/18 network will use GnuGk4. Endpoints in all other networks will use the globally defined alternate gatekeeper.

[RasSrv::AlternateGatekeeper]
192.168.0.0/18=1.2.3.4;1719;true;120;GnuGk4
192.168.1.10=1.2.3.10;1719;true;120;GnuGk10

7.9 Section [RasSrv::AssignedGatekeeper]

This allows the assigning of a gatekeeper based upon the H323ID or the apparent source IP address of the registering endpoint. The received H323ID in the GRQ is checked to see if it has a prefix for an assigned gatekeeper or the IP is in a range of an assigned gatekeeper. The endpoint is then advised in the GCF to register with that gatekeeper. You may have multiple gatekeepers for a specific prefix. The first is assigned as the primary and others are then the alternates. (requires H.323v6)

Examples:

[RasSrv::AssignedGatekeeper]
;; for endpoint with alias starting with 01234
01234=192.168.1.100:1719
;; for endpoint with alias starting with 999
999=[2a01:4f8:61:2243::99]:1719
;; for endpoints in the range of 195.71.129.0/24 or 195.71.131.0/24
^195\.71\.(129|131)\.[0-9]+$=10.10.0.5:1719
;; for endpoints tarting with ^2a01:
^2a01:=[2a01:4f8:61:2243::199]:1719

7.10 Section [AssignedGatekeepers::SQL]

This section allows GnuGk to read the assigned gatekeepers from a database. You can use the same database parameters as defined in [SQLPasswordAuth].

7.11 Section [AlternateGatekeepers::SQL]

This section allows GnuGk to read the alternate gatekeepers from a database. You can use the same database parameters as defined in [SQLPasswordAuth].

7.12 Section [AssignedLanguage::SQL]

This section configures GnuGk to read the assigned Languages from a database. You can use the same database parameters as defined in [SQLPasswordAuth].

7.13 Section [NATedEndpoints]

The gatekeeper can automatically detect whether an endpoint is behind NAT. However, if the detection fails, you can specify it manually in this section.

Format:

alias=true | yes | 1

Example:

Specify that the endpoint with alias 601 is behind NAT.

601=true

7.14 Section [GkPresence::SQL]

H323 SQL Presence system : Highly Experimental Use the common database configuration options to define your database connection for this module.


Next Previous Contents