System information

With this configuration in place, CEL events will appear as events on the manager
interface. To generate example manager events, we will use the following dialplan
example:
exten => 111,1,Answer()
same => n,CELGenUserEvent(Custom Event,Whiskey Tango Foxtrot)
same => n,Hangup()
This is the command used to execute this extension and generate sample CEL events:
*CLI> console dial 111@testing
Finally, this is one of the example manager events produced as a result of this test call:
Event: CEL
Privilege: call,all
EventName: CHAN_START
AccountCode:
CallerIDnum:
CallerIDname:
CallerIDani:
CallerIDrdnis:
CallerIDdnid:
Exten: 111
Context: testing
Channel: Console/dsp
Application:
AppData:
EventTime: 2010-08-23 08:14:51
AMAFlags: NONE
UniqueID: 1282569291.1
LinkedID: 1282569291.1
Userfield:
Peer:
cel_pgsql
This module allows posting of CEL events to a PostgreSQL database. We recommend
that new installations use cel_odbc instead.
cel_radius
The cel_radius backend allows posting of CEL events to a RADIUS server. When using
this module, each CEL event is reported to the RADIUS server as a single stop event.
This module is configured in the /etc/asterisk/cel.conf file. The options for this module,
listed in Table 24-14, are placed in a section called [radius].
Table 24-14. Available options in the cel.conf [radius] section
Option Value/Example Notes
usegmtime no Logs timestamps using GMT instead of local time. The default is yes.
radiuscfg /etc/radiusclient-ng/
radiusclient.conf
Sets the location of the radiusclient-ng configuration file. The
default is /etc/radiusclient-ng/radiusclient.conf.
CEL (Channel Event Logging) | 545