System information

cel_sqlite3_custom
This CEL backend inserts CEL events into a SQLite database using SQLite version 3.
The database created by this module lives at /var/log/asterisk/master.db. The configu-
ration file for this module, /etc/asterisk/cel_sqlite3_custom.conf, identifies the table
name, as well as customizes which CEL variables will be inserted into the database. It
looks like this:
[master]
table = cel
;
; List the column names to use when inserting CEL events.
;
columns => eventtype, eventtime, cidname, cidnum, cidani, cidrdnis, ciddnid,
context, exten, channame, appname, appdata, amaflags, accountcode, uniqueid,
userfield, peer
;
; Map CEL event contents to the previously specified columns.
;
values => '${eventtype}','${eventtime}','${CALLERID(name)}','${CALLERID(num)}',
'${CALLERID(ANI)}','${CALLERID(RDNIS)}','${CALLERID(DNID)}',
'${CHANNEL(context)}','${CHANNEL(exten)}','${CHANNEL(channame)}',
'${CHANNEL(appname)}','${CHANNEL(appdata)}','${CHANNEL(amaflags)}',
'${CHANNEL(accountcode)}','${CHANNEL(uniqueid)}','${CHANNEL(userfield)}',
'${CHANNEL(peer)}'
In the cel_sqlite3_custom.conf file, the contents of the columns and val
ues options must appear on a single line.
cel_tds
The cel_tds module uses the FreeTDS library to post CEL events to a Microsoft SQL
Server or Sybase database. It is possible to use FreeTDS with unixODBC, so we rec-
ommend using cel_odbc instead of this module.
Example Channel Events
Now we will show you some example sets of call events from the CEL system. The
cel_custom module will be used for its simplicity. The configuration used for /etc/as-
terisk/cel_custom.conf is the same as shown in “cel_custom” on page 543. Additionally,
the following configuration was used for /etc/asterisk/cel.conf:
[general]
enable = yes
546 | Chapter 24: System Monitoring and Logging