Next Previous Contents

7. RAS Configuration

7.1 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.2 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.

Format:

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

Example:

For gateway,

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

7.3 Section [RasSrv::RRQFeatures]

7.4 Section [RasSrv::ARQFeatures]

7.5 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.6 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.7 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::AssignedGKs]
;; For Endpoint with H323ID starting with 01234
01234=x.x.x.x:1719
;; For Endpoints in the range of 195.71.129.0/24 or 195.71.131.0/24
^195\.71\.(129|131)\.[0-9]+$=x.x.x.x:1719

7.8 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.9 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 an endpoint with alias 601 is behind NAT.

601=true


Next Previous Contents