11.4 Section [SQLAcct]
This accounting module stores accounting information directly to a SQL database. Many configuration settings are common with other SQL modules.


Driver=MySQL | PostgreSQL | Firebird | ODBC | SQLite
Default: N/A

SQL database driver to use. Currently, MySQL, PostgreSQL, Firebird, ODBC and SQLite drivers are implemented.


Host=DNS[:PORT] | IP[:PORT]
Default: localhost

SQL server host address. Can be in the form of DNS[:PORT] or IP[:PORT]. Examples: sql.mycompany.com or sql.mycompany.com:3306 or 192.168.3.100.


Database=billing
Default: N/A

The database name to connect to.


Username=gnugk

The username used to connect to the database.


Password=secret

The password used to connect to the database. If the password is not specified, a database connection attempt without any password will be made. If EncryptAllPasswords is enabled, or a KeyFilled variable is defined in this section, the password is in an encrypted form and should be created using the addpasswd utility.


StartQuery=INSERT ...
Default: N/A

Defines SQL query used to insert a new call record to the database. The query is parametrized - that means parameter replacement is made before each query is executed. Parameter placeholders are denoted by % character and can be one letter (like %u) or whole strings (like %{src-info}). Specify %% to embed a percent character inside the query string (like %%). For SQLAcct the following parameters are defined:

%g - gatekeeper name
%n - call number (not unique after gatekeeper restart)
%d - call duration (seconds)
%t - total call duration (from Setup to Release Complete)
%c - Q.931 disconnect cause (hexadecimal integer)
%r - who disconnected the call (-1 - unknown, 0 - the gatekeeper, 1 - the caller, 2 - the callee)
%p - PDD (Post Dial Delay) in seconds
%s - unique (for this gatekeeper) call (Acct-Session-Id)
%u - H.323 ID of the calling party
%{gkip} - IP address of the gatekeeper
%{CallId} - H.323 call identifier (16 hex 8-bit digits)
%{ConfId} - H.323 conference identifier (16 hex 8-bit digits)
%{setup-time} - timestamp string for Q.931 Setup message
%{alerting-time} - timestamp string for Q.931 Alerting message
%{connect-time} - timestamp string for a call connected event
%{disconnect-time} - timestamp string for a call disconnect event
%{ring-time} - time a remote phone was ringing for (from Alerting till Connect or Release Complete)
%{caller-ip} - signaling IP address of the caller
%{caller-port} - signaling port of the caller
%{callee-ip} - signaling IP address of the called party
%{callee-port} - signaling port of the called party
%{src-info} - a colon separated list of source aliases
%{dest-info} - a colon separated list of destination aliases
%{Calling-Station-Id} - calling party number
%{Called-Station-Id} - called party number (rewritten Dialed-Number)
%{Dialed-Number} - dialed number (as received from the calling party)
%{caller-epid} - endpoint identifier of the calling party
%{callee-epid} - endpoint identifier of the called party
%{call-attempts} - number of attempts to establish the calls (with failover this can be > 1)
%{last-cdr} - is this the last CDR for this call ? (0 / 1) only when using failover this can be 0
%{media-oip} - caller's RTP media IP (only for H.245 routed/tunneled calls)
%{codec} - audio codec used during the call (only for H.245 routed/tunneled calls)
%{bandwidth} - bandwidth for this call
%{client-auth-id} - an ID provided to GnuGk when authenticating the call (through SqlAuth)
Sample query string:

INSERT INTO call (gkname, sessid, username, calling, called)
VALUES ('%g', '%s', '%u', '%{Calling-Station-Id}', '%{Called-Station-Id}')


StartQueryAlt=INSERT ...
Default: N/A

Defines a SQL query used to insert a new call record to the database in case the StartQuery failed for some reason (the call already exists, for example). The syntax and parameters are the same as for StartQuery.


UpdateQuery=UPDATE ...
Default: N/A

Defines a SQL query used to update a call record in the database with the current call state. The syntax and parameters are the same as for StartQuery.

Sample query string:

UPDATE call SET duration = %d WHERE gkname = '%g' AND sessid = '%s'


StopQuery=UPDATE ...
Default: N/A

Defines SQL query used to update a call record in the database when the call is finished (disconnected). The syntax and parameters are the same as for StartQuery.

Sample query string:

UPDATE call SET duration = %d, dtime = '%{disconnect-time}' WHERE gkname = '%g' AND sessid = '%s'


StopQueryAlt=INSERT ...
Default: N/A

Defines a SQL query used to update call record in the database when the call is finished (disconnected) in case the regular StopQuery failed (because the call record does not yet exist, for example). The syntax and parameters are the same as for StartQuery.

Sample query string:

INSERT INTO call (gkname, sessid, username, calling, called, duration)
VALUES ('%g', '%s', '%u', '%{Calling-Station-Id}', '%{Called-Station-Id}', %d)


TimestampFormat=MySQL
Default: N/A

Format of timestamp strings used in queries. If this setting is not specified, the global one from the main gatekeeper section is used.


MinPoolSize=5
Default: 1

Number of concurrent SQL connections in the pool. The first available connection in the pool is used to store accounting data.


A Sample MySQL Schema
The SQLAcct module is designed to adapt to whatever database structure you already have. You can define all queries so they fit your existing tables. Here is an example of what those tables might look like in MySQL and which you can use as a starting point.

Create a new database; here we use the name 'GNUGK':


create database GNUGK;

Then create a table in this database to store you accounting data; we call the table 'CDR'.


create table GNUGK.CDR (
gatekeeper_name varchar(255),
call_number int zerofill,
call_duration mediumint unsigned zerofill,
index duration_idx (call_duration),
disconnect_cause smallint unsigned zerofill,
index dcc_idx (disconnect_cause),
acct_session_id varchar(255),
h323_id varchar(255),
gkip varchar(15),
CallId varchar(255),
ConfID varchar(255),
setup_time datetime,
connect_time datetime,
disconnect_time datetime,
caller_ip varchar(15),
index srcip_idx (caller_ip),
caller_port smallint unsigned zerofill,
callee_ip varchar(15),
index destip_idx (callee_ip),
callee_port smallint unsigned zerofill,
src_info varchar(255),
dest_info varchar(255),
Calling_Station_Id varchar(255),
Called_Station_Id varchar(255),
index dialednumber_idx (Called_Station_Id (20)),
Dialed_Number varchar(255)
);

Then you need to create a username for accessing the data.


mysql> GRANT delete,insert,select,update ON GNUGK.* TO 'YourDesiredUsername'@'localhost' IDENTIFIED BY 'APassword';
mysql> flush privileges;

With this command you will permit access to the data only from the local server. If you need to access the data from any other computer then you have to set the proper security options.

For example, to permit access from the 192.168.1.0/24 network:


mysql> GRANT delete,insert,select,update ON GNUGK.* TO 'YourDesiredUsername'@'192.168.1.%' IDENTIFIED BY 'APassword';
mysql> flush privileges;

Then you can add the following settings into your gnugk.ini file to insert and update the history of the calls into your database.


[Gatekeeper::Acct]
SQLAcct=optional;start,stop,update
FileAcct=sufficient;stop

[FileAcct]
DetailFile=Add your desire path here something like /var/log/cdr.log
StandardCDRFormat=0
CDRString=%g|%n|%d|%c|%s|%u|%{gkip}|%{CallId}|%{ConfId}|%{setup-time}|%{connect-time}|%{disconnect-time}|%{caller-ip}|%{caller-port}|%{callee-ip}|%{callee-port}|%{src-info}|%{dest-info}|%{Calling-Station-Id}|%{Called-Station-Id}|%{Dialed-Number}
Rotate=daily
RotateTime=23:59

[SQLAcct]
Driver=MySQL
Database=GNUGK
Username=YourDesiredUsername
Password=APassword
StartQuery= insert into CDR (gatekeeper_name, call_number, call_duration, disconnect_cause, acct_session_id, h323_id, gkip, CallId, ConfId, setup_time, connect_time, disconnect_time, caller_ip, caller_port, callee_ip, callee_port, src_info, dest_info, Calling_Station_Id, Called_Station_Id, Dialed_Number) values ('%g', '%n', %d, %c, '%s', '%u', '%{gkip}', '%{CallId}', '%{ConfId}', '%{setup-time}', '%{connect-time}', '%{disconnect-time}', '%{caller-ip}', '%{caller-port}', '%{callee-ip}', '%{callee-port}', '%{src-info}', '%{dest-info}', '%{Calling-Station-Id}', '%{Called-Station-Id}', '%{Dialed-Number}')

StartQueryAlt= insert into CDR (gatekeeper_name, call_number, call_duration, disconnect_cause, acct_session_id, h323_id, gkip, CallId, ConfID, setup_time, connect_time, disconnect_time, caller_ip, caller_port, callee_ip, callee_port, src_info, dest_info, Calling_Station_Id, Called_Station_Id, Dialed_Number) values ('%g', '%n', %d, %c, '%s', '%u', '%{gkip}', '%{CallId}', '%{ConfID}', '%{setup-time}', '%{connect-time}', '%{disconnect-time}', '%{caller-ip}', '%{caller-port}', '%{callee-ip}', '%{callee-port}', '%{src-info}', '%{dest-info}', '%{Calling-Station-Id}', '%{Called-Station-Id}', '%{Dialed-Number}')

UpdateQuery= update CDR set call_duration=%d where gatekeeper_name='%g' and acct_session_id='%s'

StopQuery= update CDR set call_duration=%d, disconnect_cause=%c, disconnect_time='%{disconnect-time}' where gatekeeper_name='%g' and acct_session_id='%s'

StopQueryAlt= insert into CDR (gatekeeper_name, call_number, call_duration, disconnect_cause, acct_session_id, h323_id, gkip, CallId, ConfID, setup_time, connect_time, disconnect_time, caller_ip, caller_port, callee_ip, callee_port, src_info, dest_info, Calling_Station_Id, Called_Station_Id, Dialed_Number) values ('%g STOP Alt', '%n', %d, %c, '%s', '%u', '%{gkip}', '%{CallId}', '%{ConfID}', '%{setup-time}', '%{connect-time}', '%{disconnect-time}', '%{caller-ip}', '%{caller-port}', '%{callee-ip}', '%{callee-port}', '%{src-info}', '%{dest-info}', '%{Calling-Station-Id}', '%{Called-Station-Id}', '%{Dialed-Number}')

TimestampFormat=MySQL

11.5 Section [StatusAcct]
This accounting module sends all accounting information to the status port where it can be used to interface to external systems in real time.


StartEvent=CALL|Start|%{CallId}
Default: CALL|Start|%{caller-ip}:%{caller-port}|%{callee-ip}:%{callee-port}|%{CallId}

Defines the event to display for a new call. The string is parametrized with the same variables as the other accounting modules (See [SQLAcct]).


StopEvent=CALL|Stop|%{CallId}
Default: CALL|Stop|%{caller-ip}:%{caller-port}|%{callee-ip}:%{callee-port}|%{CallId}

Defines the event when a call is finished (disconnected). The syntax and parameters are the same as for StartEvent. This event is equivalent to the old status port CDR event, but more flexible.


UpdateEvent=CALL|Update|%{CallId}
Default: CALL|Update|%{caller-ip}:%{caller-port}|%{callee-ip}:%{callee-port}|%{CallId}

Defines event used to update the current call state. The syntax and parameters are the same as for StartEvent.


ConnectEvent=CALL|Connect|%{CallId}
Default: CALL|Connect|%{caller-ip}:%{caller-port}|%{callee-ip}:%{callee-port}|%{CallId}

Defines the event when a call is connected. The syntax and parameters are the same as for StartEvent.


TimestampFormat=MySQL
Default: N/A

Format of timestamp strings used in events. If this setting is not specified, the global one from the main gatekeeper section is used.

11.6 Section [SyslogAcct]
This accounting module sends accounting information to the Unix syslog and is not available on Windows. The local syslog daemon will then route the messages according to its configuration, generally specified in /etc/syslog.conf.


SyslogFacility=LOG_LOCAL1
Default: LOG_USER

Set the syslog facility to one of LOG_USER, LOG_DAEMON, LOG_AUTH, LOG_LOCAL0, LOG_LOCAL1, LOG_LOCAL2, LOG_LOCAL3, LOG_LOCAL4, LOG_LOCAL5, LOG_LOCAL6, LOG_LOCAL7.


SyslogLevel=LOG_NOTICE
Default: LOG_INFO

Set the syslog level to LOG_EMERG, LOG_ALERT, LOG_CRIT, LOG_ERR, LOG_WARNING, LOG_NOTICE, LOG_INFO or LOG_DEBUG.


StartEvent=CALL|Start|%{CallId}
Default: CALL|Start|%{caller-ip}:%{caller-port}|%{callee-ip}:%{callee-port}|%{CallId}

Defines the event to display for a new call. The string is parametrized with the same variables as the other accounting modules (See [SQLAacct]).


StopEvent=CALL|Stop|%{CallId}
Default: CALL|Stop|%{caller-ip}:%{caller-port}|%{callee-ip}:%{callee-port}|%{CallId}

Defines the event when a call is finished (disconnected). The syntax and parameters are the same as for StartEvent. This event is equivalent to the old status port CDR event, but more flexible.


UpdateEvent=CALL|Update|%{CallId}
Default: CALL|Update|%{caller-ip}:%{caller-port}|%{callee-ip}:%{callee-port}|%{CallId}

Defines event used to update the current call state. The syntax and parameters are the same as for StartEvent.


ConnectEvent=CALL|Connect|%{CallId}
Default: CALL|Connect|%{caller-ip}:%{caller-port}|%{callee-ip}:%{callee-port}|%{CallId}

Defines the event when a call is connected. The syntax and parameters are the same as for StartEvent.


TimestampFormat=MySQL
Default: N/A

Format of timestamp strings used in events. If this setting is not specified, the global one from the main gatekeeper section is used.

12. Neighbor Configuration

12.1 Section [RasSrv::Neighbors]
If the destination of an ARQ is unknown, the gatekeeper sends LRQs to its neighbors to ask if they have the destination endpoint. A neighbor is selected if one of its prefixes matches the destination or it has the ``*'' prefix. More than one prefix may be specified. You can use special characters ``.'' to do wildcard matching and ``!'' to disable a specific prefix.

Conversely, the gatekeeper will only reply to LRQs sent from neighbors defined in this section. If you specify an empty prefix, no LRQ will be sent to that neighbor, but the gatekeeper will accept LRQs from it. The empty prefix is denoted by a single semicolon appended to the neighbor entry. Example:

GK1=192.168.0.5;

If you skip the semicolon, LRQs will be always sent to this neighbor.

The password field is used to authenticate LRQs from that neighbor. See section [Gatekeeper::Auth] for details.

Whether a call is accepted from a neighbor also depends on the AcceptNeighborsCalls switch in the [RoutedMode] section.

The gatekeeper types have the following characteristics:

GnuGk
When in doubt, use this gatekeeper type. This also activates H.460.23 / H.460.24.
CiscoGk
GnuGk will pretend to be a Cisco gatekeeper and send fake manufacturer data.
ClarentGk
Clarent gatekeeper can't decode nonStandardData in LRQs, so GnuGk will filter it out.
GlonetGk
Limited support for LRQ forwarding.

GKID="GnuGk" | "CiscoGk" | "ClarentGk" | "GlonetGk"


Example:
[RasSrv::Neighbors]
GK1=CiscoGk
GK2=GnuGk

[Neighbor::GK1]
GatekeeperIdentifier=GK1
Host=192.168.1.1
SendPrefixes=02
AcceptPrefixes=*
ForwardLRQ=always

[Neighbor::GK2]
GatekeeperIdentifier=GK2
Host=192.168.1.2
SendPrefixes=03,0048
AcceptPrefixes=0049,001
ForwardHopCount=2
ForwardLRQ=depends



The [RasSrv::Neighbors] section is only used to specify the gatekeeper type. The configuration for each neighbor is placed in a separate section

12.2 Section [RasSrv::LRQFeatures]
Defines some features of LRQ and LCF.

NeighborTimeout=1
Default: 2

Timeout value in seconds to wait for responses from neighbors. If no neighbor responds before the timeout, the gatekeeper will reply with an ARJ to the endpoint sending the ARQ.



SendRetries=4
Default: 2

Number of tries to send LRQ to neighbors. If there is no response from neighbors after retries timeout, the gatekeeper will reply with a LRJ to the endpoint sending the LRQ.


ForwardHopCount=2
Default: N/A

If the gatekeeper receives a LRQ that the destination is unknown it may forward this message to its neighbors.

When the gatekeeper receives a LRQ and decides that the message should be forwarded on to another gatekeeper, it first decrements hopCount field of the LRQ. If hopCount has reached 0, the gatekeeper shall not forward the message. This option defines the number of gatekeepers through which a LRQ may propagate. Note that it only affects the sender of LRQ, not the forwarder. This setting can be overridden via the configuration section for a particular neighbor.


AcceptForwardedLRQ=1
Default: 1

Whether to accept an LRQ forwarded from neighbors. This setting can be overridden with configuration of a particular neighbor.


ForwardResponse=0
Default: 0

If the gatekeeper forwards a received LRQ message it can decide either to receive the LCF response or to let it travel back directly to the LRQ originator. Set this option to 1 if the gatekeeper needs to receive LCF messages for forwarded LRQs. This setting can be overridden with configuration of a particular neighbor.


ForwardLRQ=always | never | depends
Default: depends

This settings determines whether the received LRQ should be forwarded or not. always forwards LRQ unconditionally, never blocks LRQ forwarding, depends tells the gatekeeper to forward LRQ only if its hop count is greater than 1. This setting can be overridden with configuration of a particular neighbor.


AcceptNonNeighborLRQ=1
Default: 0

Whether to accept a LRQ forwarded from parties not defined as Neighbors. This can be used with SRV routing policy to place calls to third party gatekeepers. This should be used in conjunction with a LRQ Authentication policy.


AcceptNonNeighborLCF=1
Default: 0

This setting disables matching of the LRQ responder's IP address and specified neighbor IP addresses in order to accept LCF message responses from any IP address. This has primary importance when a multiple level gatekeeper hierarchy is used without routed Q.931 signaling. As a minimal security, only LRQ/LCF sequence numbers will be checked accordingly. This feature is required by the national gatekeepers connected to the Global Dialing Scheme (GDS), see http://www.vide.net/help/gdsintro.shtml for more information. WARNING: Enabling receiving LCF from other than the LRQ destination IP is a significant security risk. Use this setting with extreme caution.

12.3 Section [Neighbor::...]
Sections starting with [Neighbor:: are specific for one neighbor. If you define a [Neighbor::...] section, the default values of all settings in [RasSrv::LRQFeatures] will be applied to this neighbor. You may override the global defaults through configuration options in each neighbor-specific section.


GatekeeperIdentifier=GKID
Default: N/A

Gatekeeper identifier for this neighbor. If this option is not specified, the identifier is taken from the second part of the Neighbor:: section name.


Host=192.168.1.1
Default: N/A

An IP address for this neighbor.


Password=secret
Default: N/A

A password to be used to validate crypto tokens received from incoming LRQs. Not yet implemented, yet.


Dynamic=0
Default: 0

1 means that the IP address for this neighbor can change.


SendPrefixes=004,002:=1,001:=2
Default: N/A

A list of prefixes that this neighbor expects to receive LRQs for. If '*' is specified, LRQs will always be sent to this neighbor. A priority can be given to each prefix for each neighbor (using := syntax), so in case of multiple LCF received from multiple neighbor, the one with the highest priority will be selected to route the call. One can also direct the gatekeeper to send LRQ to this neighbor based on an alias type:
SendPrefixes=h323_ID,dialedDigits,001



AcceptPrefixes=*
Default: *

A list of prefixes that GnuGk will accept in LRQs received from this neighbor. If '*' is specified, all LRQs will be accepted from this neighbor. One can also direct the gatekeeper to accept LRQ from this neighbor based on an alias type:
AcceptPrefixes=dialedDigits



ForwardHopCount=2
Default: N/A

If the gatekeeper receives an LRQ that the destination is either unknown, it may forward this message to its neighbors. When the gatekeeper receives an LRQ and decides that the message should be forwarded on to another gatekeeper, it first decrements hopCount field of the LRQ. If hopCount has reached 0, the gatekeeper shall not forward the message. This options defines the number of gatekeepers through which an LRQ may propagate. Note it only affects the sender of LRQ, not the forwarder.


AcceptForwardedLRQ=1
Default: 1

Whether to accept an LRQ forwarded from this neighbor.


ForwardResponse=0
Default: 0

If the gatekeeper forwards received LRQ message it can decide either to receive the LCF response or to let it travel back directly to the LRQ originator. Set this option to "1" if the gatekeeper needs to receive LCF messages for forwarded LRQs.


ForwardLRQ=always | never | depends
Default: depends

This settings determines whether the received LRQ should be forwarded or not. always forwards LRQ unconditionally, never blocks LRQ forwarding, depends tells the gatekeeper to forward LRQ only if its hop count is greater than 1.


UseH46018=1
Default: 0

Enable H.460.18 keep-alive messages to this neighbor. Set this switch only on the H.460.18 client side that is supposed to send the keep-alive ServiceControlIndication (SCI) messages.


SendPassword=secret
Default: N/A



EXPERIMENTAL: The password to send to the neighbor (right now only used for H.460.18 SCI).

13. Per-Endpoint Configuration
In addition to the standard configuration file options, per-endpoint configuration settings can be specified in the config file. The syntax is as follows:

13.1 Section [EP::...]

[EP::ALIAS]
Key Name=Value String

ALIAS should be replaced with the actual alias for the endpoint the settings should apply to. Currently, the following options are recognized:


Capacity=10
Default: -1

Call capacity for an endpoint. No more than Capacity concurrent calls will be sent to this endpoint. In case of gateways, if more than one gateway matches a dialed number, a call will be sent to the first available gateway which has available capacity.


PrefixCapacities=^0049:=10,^(0044|0045):=20
Default: N/A

Limit the capacity for certain prefixes. Regular expressions can be used to specify the prefix and specify a combined capacity for a group of prefixes. For a gateway to be considered available a.) the prefix must have capacity left and b.) the total gateway capacity (see above) must not be exceeded.


GatewayPriority=1
Default: 1

Applicable only to gateways. Allows priority based routing when more than one gateway matches a dialed number. Lower values indicate a higher gateway priority. A call is routed to the first available gateway (that has available capacity) with the highest priority (the lowest GatewayPriority values). In case the gateway priority contradicts prefix priority (see section [RasSrv::GWPrefixes]) for details), prefix priority will take precedence.


GatewayPrefixes=0048,0049:=2,0044
Default: N/A

Additional prefixes for this gateway. Applies only to gateways. Special characters . and ! can be used to match any digit or to disable the prefix. You may use the := syntax to set a prefix priority in the same manner as in [RasSrv::GWPrefixes] section. If no priority is explicitly configured for a prefix, then the gateway priority is used.



CalledTypeOfNumber=1
Default: N/A

Sets Called-Party-Number type of number to the specified value for calls sent to this endpoint (0 - UnknownType, 1 - InternationalType, 2 - NationalType, 3 - NetworkSpecificType, 4 - SubscriberType, 6 - AbbreviatedType, 7 - ReservedType).


CallingTypeOfNumber=1
Default: N/A

Sets Calling-Party-Number type of number to the specified value for calls sent to this endpoint (0 - UnknownType, 1 - InternationalType, 2 - NationalType, 3 - NetworkSpecificType, 4 - SubscriberType, 6 - AbbreviatedType, 7 - ReservedType).


CalledPlanOfNumber=1
Default: N/A

Sets Called-Numbering-Plan of number to the specified value for calls sent to this endpoint (0 - UnknownType, 1 - ISDN, 3 - X.121 numbering, 4 - Telex, 8 - National standard, 9 - private numbering).


CallingPlanOfNumber=1
Default: N/A

Sets Calling-Numbering-Plan of number to the specified value for calls sent to this endpoint (0 - UnknownType, 1 - ISDN, 3 - X.121 numbering, 4 - Telex, 8 - National standard, 9 - private numbering).


Proxy=1
Default: 0

Enables/disables proxying calls sent to this endpoint (0 - do not change global proxy settings, 1 - force proxy mode, 2 - disable proxy mode).


TranslateReceivedQ931Cause=17:=34
Default: N/A

Translate received cause codes in ReleaseComplete messages from this endpoint. In the above example code 17 (User busy) will be translated into cause code 34 (No circuit/channel available).


TranslateSentQ931Cause=21:=34,27:=34
Default: N/A

Translate cause codes in ReleaseComplete messages sent out to this endpoint. In the above example code 21 and 27 will be translated into cause code 34, because this particular gateway might deal with error code 34 better than with others.


DisableH46018=1
Default: 0

Disable H.460.18/.19 for this endpoint.


Example:


[RasSrv::PermanentEndpoints]
192.168.1.1=gw1;48
192.168.1.2=gw2;48,!4850,!4860,!4869,!4888

[EP::gw1]
Capacity=60
GatewayPriority=1

[EP::gw2]
Capacity=30
GatewayPriority=2

In this example, calls will be sent to the gateway gw1 until its capacity is fully utilized (60 concurrent calls) and then to the gateway gw2.

14. Advanced Configuration

14.1 Section [CallTable]

GenerateNBCDR=0
Default: 1

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 debugging purposes.


GenerateUCCDR=0
Default: 0

Generate CDRs for calls that are unconnected. This is usually used for debugging purposes. Note that 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.


DefaultCallDurationLimit=3600
Default: 0

Default maximum call duration limit (seconds). Set it to 0 to disable this feature and not limit call duration.


AcctUpdateInterval=60
Default: 0

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 [Gatekeeper::Acct]). In general, the accounting update is to provide back-end services with incrementing call duration for connected calls. The default value "0" disables accounting updates. Please note that setting this to a short interval may decrease gatekeeper performance.


TimestampFormat=Cisco
Default: RFC822

Format of timestamp strings printed inside CDRs. You can use the same list of formats as specified in the [Gatekeeper::Main] section.


IRRFrequency=60
Default: 120

Set the irrFrequency in ACF messages. 0 turns it off.


IRRCheck=TRUE
Default: FALSE

Check if both endpoints in a call send the requested IRRs. A call will be terminated if one of the endpoints didn't send an IRR after 2 * irrFrequency.


SingleFailoverCDR=FALSE
Default: TRUE

When failover is active, more than one gateway may be tried to establish a call. This switch defines if one or multiple CDRs are generated for such a call.


DisabledCodecs=g711Alaw64k;g711Ulaw64k;h263VideoCapability;
Default: N/A

Filter out certain codecs. Please note the trailing semicolon. Calls must be H.245 routed or proxied for codec filtering to work. This setting can be overridden on a per-call basis by using the Radius attribute 'disable-codec'.

14.2 Section [H225toQ931]
When converting between H.225 reasons and Q.931 cause codes, GnuGk uses a conversion table. Using this section you can change this mapping.


[H225toQ931]
;0=34 # noBandwidth
;1=47 # gatekeeperResources
2=34 # unreachableDestination => NoCircuitChannelAvailable (default 3)
;3=16 # destinationRejection
;4=88 # invalidRevision
;5=111 # noPermission
;6=38 # unreachableGatekeeper
;7=42 # gatewayResources
;8=28 # badFormatAddress
;9=41 # adaptiveBusy
;10=17 # inConf
;11=31 # undefinedReason
;12=16 # facilityCallDeflection
;13=31 # securityDenied
14=34 # calledPartyNotRegistered => NoCircuitChannelAvailable (default 20)
;15=31 # callerNotRegistered
;16=47 # newConnectionNeeded
;17=127 # nonStandardReason
;18=31 # replaceWithConferenceInvite
;19=31 # genericDataReason
;20=31 # neededFeatureNotSupported
;21=127 # tunnelledSignallingRejected

14.3 Section [GkQoSMonitor]
Use H.460.9 to collect quality of service information from endpoints. Endpoints must support H.460.9 for this service to function.


Enable=1
Default: 0

Defines whether to enable or disable the feature. If enabled, this function with respond to supportedFeature requests from clients so clients know to send QoS statistics to the gatekeeper.


CallEndOnly=0
Default: 1

Define whether to collect the information via IRR messages or to only collect QoS information at the end of a call.


DefaultFile=qos.txt
Default: N/A

Define the output file for QoS logs. If a file is not defined the QoS information is output as an item in the Trace File at trace level 4