System information

cdr_sqlite
This module allows posting of CDRs to a SQLite database using SQLite version 2.
Unless you have a specific need for SQLite version 2 as opposed to version 3, we rec-
ommend that all new installations use cdr_sqlite3_custom.
This module requires no configuration to work. If the module has been compiled and
loaded into Asterisk, it will insert CDRs into a table called cdr in a database located
at /var/log/asterisk/cdr.db.
cdr_sqlite3_custom
This CDR backend inserts CDRs into a SQLite database using SQLite version 3. The
database created by this module lives at /var/log/asterisk/master.db. This module re-
quires a configuration file, /etc/asterisk/cdr_sqlite3_custom.conf. The configuration file
identifies the table name, as well as customizes which CDR variables will be inserted
into the database:
[master]
table = cdr
;
; List the column names to use when inserting CDRs.
;
columns => calldate, clid, dcontext, channel, dstchannel, lastapp, lastdata,
duration, billsec, disposition, amaflags, accountcode, uniqueid, userfield,
test
;
; Map CDR contents to the previously specified columns.
;
values => '${CDR(start)}','${CDR(clid)}','${CDR(dcontext)}','${CDR(channel)}',
'${CDR(dstchannel)}','${CDR(lastapp)}','${CDR(lastdata)}','${CDR(duration)}',
'${CDR(billsec)}','${CDR(disposition)}','${CDR(amaflags)}',
'${CDR(accountcode)}','${CDR(uniqueid)}','${CDR(userfield)}','${CDR(test)}'
In the cdr_sqlite3_custom.conf file, the contents of the columns and val
ues options must each be on a single line.
cdr_syslog
This module allows logging of CDRs using syslog. To enable this, first add an entry to
the system’s syslog configuration file, /etc/syslog.conf. For example:
local4.* /var/log/asterisk/asterisk-cdr.log
Call Detail Records | 535