Next Previous Contents

7. RAS Configuration

7.1 Section [RasSrv::GWPrefixes]

This section lists what E.164 numbers are routed to a specific gateway.

Format:

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

Note you have to specify the alias of the gateway. If a gateway registered with the alias, all numbers beginning with the prefixes are routed to this gateway. Special characters . and ! can be used here to match any digit and disable the prefix. A priority can be given to each prefix for each gateway (using := syntax), so in case of 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 call will be routed to all selected gateways in order of the prefix priority). The smaller value corresponds to the higher priority. Default value is 1. In case when prefix priority intersectes with GatewayPriority (see section [EP::...]) prefix one is preferred.

Example:

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

7.2 Section [RasSrv::PermanentEndpoints]

In this section you can put endpoints that don't have RAS support or that you don't want to be expired. The records will always keep in registration table of the gatekeeper. However, You can still unregister it via 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=Citron;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 registering endpoints. This allows endpoints to be assigned fully qualified E164 or URI addresses upon registraton.

Example:

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

7.6 Section [RasSrv::AssignedGatekeeper]

This allows the assigning of a gatekeeper based apon 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 gatekeeper is then advised in the GCF to register with that gatekeeper. You may have multiple gatekeepers for a specific prefix the first is assigned the assigned and the others are assigned alternates. (requires H.323v6)

Examples:

[RasSrv::AssignedGKs]
;; For Endpoint with H323ID starting with 01234
01234=x.x.x.x:1719
;; For Endpoint in the range of 195.71.129.0/24 to 195.71.131.0/24
^195\.71\.(129|131)\.[0-9]+$=x.x.x.x:1719

7.7 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