SQLAuth

[Gabriel Georgescu <gaby@xxxxxxxxxxxxxx>]

Hi dear list,

I see in the web manual for [SQLAuth] at specifications for the callquery
that these columns are checked:

1. If there exists a column called 'billingmode', set a billing mode associated with the endpoint (0 - credit,

2. 0 - debit)

3. If there exists a column called 'creditamount', set account balance associated with the endpoint (this is an arbitrary string)

4. If there exists a column called 'credittime', use its integer value to set call duration limit

5. If there exists a column called 'redirectnumber', replace the original destination number with this one

6. If there exists a column called 'redirectip', force the call to be sent to the specified IP

7. If there exists a column called 'proxy', force the gatekeeper to enable/disable (depends on the 'proxy' column value) RTP proxy for this call

I need more details about how gnugk uses these columns to manage the
call.

Here are my questions:
1. The correct answer is 0 - credit and 1 - debit? How will gnugk update
the database knowing this?
2. If there is only a column called 'creditamount' how will gnugk use it
to stop the call?
3. Are there any db updates made during the call? For example if I have
many calls using the same account will the gk cut all calls when the
balance reaches zero? Is there a good mechanism that will cut all calls
exactly at balance zero?

Thank you,
Gabriel