This section lists what E.164 numbers are routed to a specific gateway.
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.
test-gw=02,03:=3,04.:=1
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.
IP[:port]=alias[,alias,...;prefix[:=priority][,prefix[:=priority]]...]
For gateway,
10.0.1.5=Citron;009,008:=2,0.7:=3
For terminal,
10.0.1.10:1720=700
AcceptEndpointIdentifier=1
1
Whether to accept endpointIdentifier specified in a full RRQ.
AcceptGatewayPrefixes=1
1
A gateway can register its prefixes with the gatekeeper by containing supportedPrefixes in the terminalType field of RRQ. This option defines whether to accept the specified prefixes of a gateway.
AcceptMCUPrefixes=1
1
A MCU can register its prefixes with the gatekeeper by containing supportedPrefixes in the terminalType field of RRQ. This option defines whether to accept the specified prefixes of a MCU.
OverwriteEPOnSameAddress=1
0
In some networks an endpoint's IP address may change unexpectedly. This may happen when an endpoint is using a PPP connection (e.g. modem or ADSL). This option defines how to handle a registration request (RRQ) from an IP address which does not match what we have stored. The default action is to reject the request. With this option enabled the conflicting request will cause an unregister request (URQ) to be sent for the existing IP address and the entry to be removed allowing the endpoint to register with the new address.
IRQPollCount=0
1
When the gatekeeper does not receive a keep-alive RRQ from an endpoint within TimeToLive time period, it sends an IRQ message to "poll" the endpoint and check if it is alive. After IRQPollCount messages are sent and no reply is received, the endpoint is unregistered. To disable this feature (and unregister endpoints immediately after TimeToLive timeout), set this variable to 0. IRQ poll interval is 60 seconds.
SupportDynamicIP=1
0
When the IP address of an endpoint changes, the gatekeeper can maintain registration. This will force the EP to fully reregister if the IP Address changes.
AccHTTPLink=https://billing.mysite.com?account=%a&password=%p
N/A
You can assign a URL for clients to access to view billing information. If using PacPhone you can also add wildcards for the client to use so the clients H323ID and password can be used to directly access their account information. %a - H323ID %p - password
AliasTypeFilter=terminal;h323id,dialeddigits
N/A
Where endpoints send multiple H225_AliasAddress and some Aliases are shared across multiple registrations. You can filter out the shared alias types for any given endpoint type. You must had seperate AliasTypeFilter entries for each endpoint type. Valid endpoint types are: gatekeeper,gateway,mcu,terminal Valid filters are: h323id, dialeddigits, url, transport, email, partynumber NOTE: If no alias is found that match the filter than all aliases are registered.
ArjReasonRouteCallToGatekeeper=1
1
If yes, the gatekeeper rejects an answered ARQ without a pre-existing CallRec found in the CallTable by reason routeCallToGatekeeper in routed mode. The endpoint shall release the call immediately and re-send call Setup to the gatekeeper.
RemoveTrailingChar=#
N/A
Specify the trailing character to be removed in destinationInfo. For example, if your endpoint incorrectly contains the termination character like `#' in destinationInfo, you may remove it by this option.
RoundRobinGateways=0
1
Enable/disable round-robin gateway selection, if more than one gateway matches a dialed number. If disabled, the first available gateway will be selected. Otherwise, subsequent calls will be sent to gateways in round-robin fashion.
This allows the assigning of aliases to registering endpoints. This allows endpoints to be assigned fully qualified E164 or URI addresses upon registraton.
[RasSrv::AssignedAlias] 1234=3323465777,me@mysite.com
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)
[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
The gatekeeper can automatically detect whether an endpoint is behind NAT. However, if the detection fails, you can specify it manually in this section.
alias=true,yes,1,...
Specify an endpoint with alias 601 is behind NAT.
601=true