Sophie: gnugk-2.3.1-1mdv2010.1 x86

gnugk-2.3.1-1mdv2010.1.x86_64.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
 <TITLE>The GNU Gatekeeper: RAS Configuration</TITLE>
 <LINK HREF="manual-8.html" REL=next>
 <LINK HREF="manual-6.html" REL=previous>
 <LINK HREF="manual.html#toc7" REL=contents>
</HEAD>
<BODY>
<A HREF="manual-8.html">Next</A>
<A HREF="manual-6.html">Previous</A>
<A HREF="manual.html#toc7">Contents</A>
<HR>
<H2><A NAME="s7">7.</A> <A HREF="manual.html#toc7">RAS Configuration</A></H2>


<H2><A NAME="gwprefixes"></A> <A NAME="ss7.1">7.1</A> <A HREF="manual.html#toc7.1">Section [RasSrv::GWPrefixes]</A>
</H2>

<P>This section configures how dialed E.164 numbers are routed to a specific gateway.</P>
<P>
<DL>
<DT><B>Format:</B><DD><P><CODE>gw-alias=prefix[:=priority][,prefix[:=priority],...]</CODE></P>
<P>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 <CODE>.</CODE> and <CODE>!</CODE>
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 
<A HREF="manual-11.html#epconfig">[EP::...]</A>), the prefix priority will be preferred.</P>
<P>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.</P>

<DT><B>Example:</B><DD><P><CODE>test-gw=02,03:=3,04:=1</CODE></P>
</DL>
</P>

<H2><A NAME="ss7.2">7.2</A> <A HREF="manual.html#toc7.2">Section [RasSrv::PermanentEndpoints]</A>
</H2>

<P>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 <CODE>.</CODE> and <CODE>!</CODE>
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 
<A HREF="#gwprefixes">[RasSrv::GWPrefixes]</A> section.
<DL>
<DT><B>Format:</B><DD><P><CODE>IP[:port]=alias[,alias,...;prefix[:=priority][,prefix[:=priority]]...]</CODE></P>
<DT><B>Example:</B><DD><P>For gateway,
<BLOCKQUOTE>
<CODE>10.0.1.5=MyGW;009,008:=2,0.7:=3</CODE>
</BLOCKQUOTE>

For terminal,
<BLOCKQUOTE>
<CODE>10.0.1.10:1720=700</CODE>
</BLOCKQUOTE>
</P>
</DL>
</P>


<H2><A NAME="ss7.3">7.3</A> <A HREF="manual.html#toc7.3">Section [RasSrv::RRQFeatures]</A>
</H2>

<P>
<UL>
<LI><CODE>AcceptEndpointIdentifier=1</CODE><BR>
Default: <CODE>1</CODE><BR>
<P>Whether to accept <B>endpointIdentifier</B> specified in a full RRQ.</P>

</LI>
<LI><CODE>AcceptGatewayPrefixes=1</CODE><BR>
Default: <CODE>1</CODE><BR>
<P>A gateway can register its prefixes with the gatekeeper by sending
<B>supportedPrefixes</B> in the <B>terminalType</B> field of the RRQ.
This option defines whether to accept the specified prefixes of a gateway.</P>

</LI>
<LI><CODE>AcceptMCUPrefixes=1</CODE><BR>
Default: <CODE>1</CODE><BR>
<P>A MCU can register its prefixes with the gatekeeper by sending 
<B>supportedPrefixes</B> in the <B>terminalType</B> field of the RRQ.
This option defines whether to accept the specified prefixes of a MCU.</P>


</LI>
<LI><CODE>OverwriteEPOnSameAddress=1</CODE><BR>
Default: <CODE>0</CODE><BR>
<P>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.</P>

</LI>
<LI><CODE>IRQPollCount=0</CODE><BR>
Default: <CODE>1</CODE><BR>
<P>When the gatekeeper does not receive a keep-alive RRQ from an endpoint
within the 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.</P>

</LI>
<LI><CODE>SupportDynamicIP=1</CODE><BR>
Default: <CODE>0</CODE><BR>
<P>When the IP address of an endpoint changes, the gatekeeper can maintain registration. 
This will force the EP to fully re-register if its IP address changes. </P>

</LI>
<LI><CODE>AccHTTPLink=https://billing.mysite.com?account=%a&amp;password=%p</CODE><BR>
Default: <CODE>N/A</CODE><BR>
<P>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 </P>

</LI>
<LI><CODE>AliasTypeFilter=terminal;h323id,dialeddigits</CODE><BR>
Default: <CODE>N/A</CODE><BR>
<P>Use this setting 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. The registrations will keep all alias types listed in the
filter setting and remove all others.
You must have separate AliasTypeFilter entries for each endpoint type.
Valid endpoint types are: gatekeeper, gateway, mcu and terminal.
Valid filters are: h323id, dialeddigits, url, transport, email and partynumber.
NOTE: If no alias is found that match the filter then all aliases are registered.</P>
</LI>
</UL>
</P>


<H2><A NAME="ss7.4">7.4</A> <A HREF="manual.html#toc7.4">Section [RasSrv::ARQFeatures]</A>
</H2>

<P>
<UL>
<LI><CODE>ArjReasonRouteCallToGatekeeper=1</CODE><BR>
Default: <CODE>1</CODE><BR>
<P>If enabled, the gatekeeper rejects an answered ARQ without a pre-existing
CallRec found in the CallTable by reason <B>routeCallToGatekeeper</B>
in routed mode.
The endpoint shall release the call immediately and re-send call Setup
to the gatekeeper.</P>

</LI>
<LI><CODE>RemoveTrailingChar=#</CODE><BR>
Default: <CODE>N/A</CODE><BR>
<P>Specify the trailing character to be removed in <B>destinationInfo</B>.
For example, if your endpoint incorrectly contains a termination character
such as `#' in <B>destinationInfo</B> you may remove it with this option.</P>

</LI>
<LI><CODE>RoundRobinGateways=0</CODE><BR>
Default: <CODE>1</CODE><BR>
<P>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.</P>

</LI>
</UL>
</P>

<H2><A NAME="ss7.5">7.5</A> <A HREF="manual.html#toc7.5">Section [RasSrv::AssignedAlias]</A>
</H2>

<P>This allows the assigning of aliases to endpoints as they register, allowing them to 
set their fully qualified E.164 or URI addresses.</P>
<P>
<DL>
<DT><B>Example:</B><DD><P>
<PRE>
[RasSrv::AssignedAlias]
1234=3323465777,me@mysite.com 
</PRE>
</P>
</DL>
</P>

<H2><A NAME="ss7.6">7.6</A> <A HREF="manual.html#toc7.6">Section [AssignedAliases::SQL]</A>
</H2>

<P>This section configures GnuGk to read the assigned aliases from a database.
You can use the same database parameters as defined in 
<A HREF="manual-8.html#sqlpasswordauth">[SQLPasswordAuth]</A>.</P>
<P>
<UL>
<LI><CODE>Query=SELECT ...</CODE><BR>
Default: <CODE>N/A</CODE><BR>
<P>Defines the SQL query used to retrieve the assigned aliases from the database.</P>
<P>One parameter is defined:
<UL>
<LI><CODE>%u</CODE> - endpoint alias</LI>
</UL>
</P>
<P>Sample query string:
<BLOCKQUOTE><CODE>
<PRE>
SELECT assignedalias FROM users WHERE alias = '%u' AND active
</PRE>
</CODE></BLOCKQUOTE>
</P>

</LI>
</UL>
</P>

<H2><A NAME="ss7.7">7.7</A> <A HREF="manual.html#toc7.7">Section [RasSrv::AssignedGatekeeper]</A>
</H2>

<P>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)</P>
<P>
<DL>
<DT><B>Examples:</B><DD><P>
<PRE>
[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
</PRE>
</P>
</DL>
</P>


<H2><A NAME="ss7.8">7.8</A> <A HREF="manual.html#toc7.8">Section [AssignedGatekeepers::SQL]</A>
</H2>

<P>This section allows GnuGk to read the assigned gatekeepers from a database.
You can use the same database parameters as defined in 
<A HREF="manual-8.html#sqlpasswordauth">[SQLPasswordAuth]</A>.</P>
<P>
<UL>
<LI><CODE>Query=SELECT ...</CODE><BR>
Default: <CODE>N/A</CODE><BR>
<P>Defines the SQL query used to retrieve the assigned gatekeepers from the database.</P>
<P>Two parameters are defined:
<UL>
<LI><CODE>%u</CODE> - endpoint alias</LI>
<LI><CODE>%i</CODE> - endpoint IP</LI>
</UL>
</P>
<P>Sample query string:
<BLOCKQUOTE><CODE>
<PRE>
SELECT assignedgatekeeper FROM users WHERE alias = '%u' AND active
</PRE>
</CODE></BLOCKQUOTE>
</P>

</LI>
</UL>
</P>


<H2><A NAME="ss7.9">7.9</A> <A HREF="manual.html#toc7.9">Section [NATedEndpoints]</A>
</H2>

<P>The gatekeeper can automatically detect whether an endpoint is behind NAT.
However, if the detection fails, you can specify it manually in this section.</P>
<P>
<DL>
<DT><B>Format:</B><DD><P><CODE>alias=true,yes,1,...</CODE></P>
<DT><B>Example:</B><DD><P>Specify an endpoint with alias 601 is behind NAT.
<BLOCKQUOTE>
<CODE>601=true</CODE>
</BLOCKQUOTE>
</P>
</DL>
</P>

<HR>
<A HREF="manual-8.html">Next</A>
<A HREF="manual-6.html">Previous</A>
<A HREF="manual.html#toc7">Contents</A>
</BODY>
</HTML>