misc.sgml

H.323网守实现

<sect>Advanced Configuration
<p>
<sect1>Section &lsqb;CallTable&rsqb;
<label id="calltable">
<p>
<itemize>
<item><tt/GenerateNBCDR=0/<newline>
Default: <tt/1/
<p>
Generate CDRs for calls from neighbor zones.
The IP and endpoint ID of the calling party is printed as empty.
This is usually used for debug purpose.

<item><tt/GenerateUCCDR=0/<newline>
Default: <tt/0/
<p>
Generate CDRs for calls that are unconnected. This is usually
used for debug purpose. Note a call is considered unconnected
only if the gatekeeper uses routed mode and a Q.931 Connect message is not
received by the gatekeeper. In direct mode, a call is always considered
connected.

<item><tt/DefaultCallDurationLimit=3600/<newline>
Default: <tt/0/
<p>
Default maximum call duration limit (seconds).
Set it to <tt/0/ to disable this feature and not limit
calls duration.

<item><tt/AcctUpdateInterval=60/<newline>
Default: <tt/0/
<p>
A time interval (seconds) for accounting updates to be logged
for each call in progress. The exact details of the accounting updates
depend on accounting logger modules selected (see section
<ref id="gkacct" name="[Gatekeeper::Acct]">). In general, the accounting
update is to provide backend services with incrementing call duration
for connected calls.
The default value 0 tells the gatkeeper to not send accounting updates
at all. Please note that setting short periods may decrease GK performance.

<item><tt/TimestampFormat=Cisco/<newline>
Default: <tt/RFC822/
<p>
Format of timestamp strings printed inside CDRs.

</itemize>


<sect1>Section &lsqb;Endpoint&rsqb;
<p>
The gatekeeper can work as an endpoint by registering with another gatekeeper.
With this feature, you can easily build gatekeeper hierarchies.
The section defines the endpoint features for the gatekeeper.

<itemize>
<item><tt/Gatekeeper=10.0.1.1/<newline>
Default: <tt/no/
<p>
Define a parent gatekeeper for the endpoint(gatekeeper) to register with.
Don't try to register with yourself, unless you want to be confusing.
To disable this feature, set the field to be <tt/no/.

<item><tt/Type=Gateway/<newline>
Default: <tt/Gateway/
<p>
Define the terminal type for the endpoint.
The valid values are <tt/Gateway/ or <tt/Terminal/.

<item><tt/H323ID=CitronProxy/<newline>
Default: <tt>&lt;Name&gt;</tt>
<p>
Specify the H.323 ID aliases for the endpoint.
Multiple aliases can be separated by comma.

<item><tt/E164=18888600000,18888700000/<newline>
Default: <tt>N/A</tt>
<p>
Define the E.164 (dialedDigits) aliases for the endpoint.
Multiple aliases can be separated by comma.

<item><tt/Password=123456/<newline>
Default: <tt>N/A</tt>
<p>
Specify a password to be sent to the parent gatekeeper.
All RAS requests will contain the password in the <bf/cryptoTokens/ field
(MD5 & HMAC-SHA1-96) and the <bf/tokens/ field (CAT).
To send RAS requests without both <bf/cryptoTokens/ and <bf/tokens/ fields,
set the password to be empty.
If <tt/EncryptAllPasswords/ is enabled, or a <tt/KeyFilled/ variable is defined
in this section, the password is in encrypted form and should be created using
the <tt/addpasswd/ utility.
<p>
Besides, the password is also used in LRQs sent to neighbor gatekeepers.

<item><tt/Prefix=188886,188887/<newline>
Default: <tt>N/A</tt>
<p>
Register the specified prefixes with the parent gatekeeper.
Only takes effect when the Type is <tt/Gateway/.

<item><tt/TimeToLive=900/<newline>
Default: <tt>60</tt>
<p>
Suggest a time-to-live value in seconds for the registration.
Note that the real time-to-live timer is assigned by the parent
gatekeeper in the RCF replied to the RRQ.

<item><tt/RRQRetryInterval=10/<newline>
Default: <tt/3/
<p>
Define a retry interval in seconds for resending an RRQ if no response 
is received from the parent gatekeeper. This interval is doubled with each
failure, up to a maximum RRQRetryInterval * 128 timeout.

<item><tt/ARQTimeout=2/<newline>
Default: <tt/2/
<p>
Define the timeout value in second for ARQs.

<item><tt/UnregisterOnReload=1/<newline>
Default: <tt/0/
<p>
Defines whether the child gatekeeper unregisters and re-registers with
it's parent when receiving a Reload command.

<item><tt/NATRetryInterval=60/<newline>
Default: <tt/60/
<p>
How long to wait before trying to reconnect TCP NAT signalling socket (seconds).
This can happen when either the connection cannot be established or it has
been broken.

<item><tt/NATKeepaliveInterval=86400/<newline>
Default: <tt/86400/
<p>
Define how often the TCP NAT signalling connection with a parent gatekeeper
is refreshed. As NAT boxes usually keep TCP mappings for a definite time only,
it is good to set this to some value a bit shorter than NAT box mapping timeout.
Refreshing is done by sending a special Q.931 IncomingCallProceeding message.
If you NAT performs TCP port translation, you may need to set it to a values
as short as 60 seconds.

<item><tt/Discovery=0/<newline>
Default: <tt/1/
<p>
Decide whether to discover the parent gatekeeper by sending GRQ first.

<item><tt/UseAlternateGK=0/<newline>
Default: <tt/1/
<p>
Enable alternate gatekeepers feature. If GRJ/GCF/RFC messages received 
from a parent gatekeeper contain a list of alternate gatekeepers, this
information is stored and can be used to reregister with another gatekeeper
in case of any failure. If you don't want to use this feature, set this
variable to <tt/0/.

<item><tt/GatekeeperIdentifier=ParentGK/<newline>
Default: <tt/Not set/
<p>
Define it if you want to accept only such parent gatekeepers that match
this gatekeeper identifier. Useful with GRQ discovery and can prevent 
an accidental gatekeeper match. Do not set this variable, if you do not
care about gatekeeper identifiers or you use alternate gatekeepers that
can have different gatekeeper indentifiers set.

<item><tt/EndpointIdentifier=OpenH323GK/<newline>
Default: <tt/Not set/
<p>
Set this if you want to use a specific endpoint identifier for this child
gatekeeper. If this option is not set (default), the identifier is assigned
by a parent gatekeeper in a GCF/RCF message.

</itemize>


<sect1>Section &lsqb;CTI::Agents&rsqb;
<p>
This section allows the configuration of a so called virtual queues to
allow inbound call distribution by an external application via the
status port.
A virtual queue has an H.323 alias that can be called like an endpoint.

Upon arrival of an ARQ on a virtual queue, the gatekeeper signals
a RouteRequest on the status port and waits for an external application
to respond with either a RouteReject (then the ARQ will be rejected)
or with RouteToAlias/RouteToGateway which leads to the ARQ being rewritten so the call
will be routed to the alias (eg. call center agent) specified by
the external application.

If no answer is received after a timeout period, the call is terminated.

You can specify virtual queues in three ways:
<itemize>
<item><tt/exact alias name/ - a list of aliases is given. If an ARQ destination
  alias matches one these names, the virtual queue is activated,
<item><tt/prefix/ - a list of prefixes is given. If an ARQ destination alias
  starts with one these prefixes, the virtual queue is activated,
<item><tt/regular expression/ - a regular expression is given. If an ARQ destination
  alias matches the expression, the virtual queue is activated.
</itemize>

See the monitoring section for details on the messages and responses.

<itemize>
<item>
<tt/VirtualQueueAliases/<newline>
Default: none
<p>
This defines a list of H.323 aliases for the virtual queues (used with the vqueue RoutingPolicy).

<descrip>
<tag/Example:/
<quote/<tt/VirtualQueueAliases=sales,support//