[svn-commits] seanbright: branch group/newcdr r202712 - /team/group/newcdr/configs/
SVN commits to the Digium repositories
svn-commits at lists.digium.com
Tue Jun 23 12:26:13 CDT 2009
Author: seanbright
Date: Tue Jun 23 12:26:10 2009
New Revision: 202712
URL: http://svn.asterisk.org/svn-view/asterisk?view=rev&rev=202712
Log:
First shot at cleaning up cel.conf.sample. I think it is easier to read in this
format.
Modified:
team/group/newcdr/configs/cel.conf.sample
Modified: team/group/newcdr/configs/cel.conf.sample
URL: http://svn.asterisk.org/svn-view/asterisk/team/group/newcdr/configs/cel.conf.sample?view=diff&rev=202712&r1=202711&r2=202712
==============================================================================
--- team/group/newcdr/configs/cel.conf.sample (original)
+++ team/group/newcdr/configs/cel.conf.sample Tue Jun 23 12:26:10 2009
@@ -8,53 +8,91 @@
[general]
-; Define whether or not to use CEL. Default is "no". Setting to "yes"
-; will turn on CEL.
+; CEL Activation
+;
+; Use the 'enable' keyword to turn CEL on or off.
+;
+; Accepted values: yes and no
+; Default value: no
;enable=yes
-; Define the apps you would like to track.
-; You can use the keyword "all"-- If you do, please be aware that a tremendous amount of
-; logging will be done, and asterisk performance may be severely impacted.
+; Application Tracking
+;
+; Use the 'apps' keyword to specify the list of applications for which you want
+; to receive CEL events. This is a comma separated list of Asterisk dialplan
+; applications, such as Dial, Queue, and Park.
+;
+; Accepted values: A comma separated list of Asterisk dialplan applications
+; Default value: none
+;
+; Note: You may also use 'all' which will result in CEL events being reported
+; for all Asterisk applications. This may affect Asterisk's performance
+; significantly.
apps=dial,park
-; Define the events you would like to track.
-; You can use the keyword "all"
-; Possible events:
-; all -- generate entries on all events.
-; CHAN_START -- The time a channel was created
-; CHAN_END -- The time a channel was terminated
-; ANSWER -- The time a channel was answered (ie, phone taken off-hook, etc)
-; HANGUP -- The time at which a hangup occurred.
-; CONF_ENTER -- The time a channel was connected into a conference room
-; CONF_EXIT -- The time a channel was removed from a conference room
-; CONF_START -- The time the first person enters a conf
-; CONF_END -- The time the last person left a conf (and turned out the lights?)
-; APP_START -- The time a tracked app was started
-; APP_END -- the time a tracked app ended.
-; PARK_START -- The time a call was parked
-; PARK_END -- unpark event
-; BRIDGE_START -- The time a bridge is started
-; BRIDGE_END -- The time a bridge is ended
-; 3WAY_START -- When a 3-way conf starts (usually via attended xfer)
-; 3WAY_END -- When one or all exit a 3-way conf
-; BLINDTRANSFER -- When a blind transfer is initiated
-; ATTENDEDTRANSFER -- When an attended transfer is initiated
-; TRANSFER -- Generic transfer initiated; not used yet...?
-; HOOKFLASH -- So far, when a hookflash event occurs on a Zap interface
-; USER_EVENT ; these are triggered from the dialplan, and have a name given by the user.
+; Event Tracking
+;
+; Use the 'events' keyword to specify the list of events which you want to be
+; raised when they occur. This is a comma separated list of the values in the
+; table below.
+;
+; Accepted values: A comma separated list of one or more of the following:
+; ALL -- Generate entries on all events
+; CHAN_START -- The time a channel was created
+; CHAN_END -- The time a channel was terminated
+; ANSWER -- The time a channel was answered (ie, phone taken off-hook)
+; HANGUP -- The time at which a hangup occurred
+; CONF_ENTER -- The time a channel was connected into a conference room
+; CONF_EXIT -- The time a channel was removed from a conference room
+; CONF_START -- The time the first person enters a conference room
+; CONF_END -- The time the last person left a conference room (and
+; turned out the lights?)
+; APP_START -- The time a tracked application was started
+; APP_END -- the time a tracked application ended
+; PARK_START -- The time a call was parked
+; PARK_END -- Unpark event
+; BRIDGE_START -- The time a bridge is started
+; BRIDGE_END -- The time a bridge is ended
+; 3WAY_START -- When a 3-way conference starts (usually via attended xfer)
+; 3WAY_END -- When one or all exit a 3-way conference
+; BLINDTRANSFER -- When a blind transfer is initiated
+; ATTENDEDTRANSFER -- When an attended transfer is initiated
+; TRANSFER -- Generic transfer initiated; not used yet...?
+; HOOKFLASH -- So far, when a hookflash event occurs on a DAHDI
+; interface
+; USER_EVENT -- Triggered from the dialplan, and has a name given by the
+; user
+;
+; Default value: none
+; (Track no events)
-events= APP_START, CHAN_START, CHAN_END, ANSWER,HANGUP, BRIDGE_START, BRIDGE_END
+events=APP_START,CHAN_START,CHAN_END,ANSWER,HANGUP,BRIDGE_START,BRIDGE_END
-; define the date format, by default it is %ld.%06ld,
-; reflect the usual seconds since the epoch, with the
-; number of microseconds
+; Date Format
+;
+; Use the 'dateformat' keyword to specify the date format used when CEL events
+; are raised.
+;
+; Accepted values: A printf-style format string??? REALLY???
+; Default value: %ld.%06ld
+; (Unix time followed by current number of microseconds)
;dateformat = %ld.%06ld
+;
+; Asterisk Manager Interface (AMI) CEL Backend
+;
+
[manager]
-; CEL over AMI - cel_manager.so
-; Set to 'yes' to enable. Disabled by deafult.
-;enabled = yes
+; AMI Backend Activation
+;
+; Use the 'enable' keyword to turn CEL logging to the Asterisk Manager Interface
+; on or off.
+;
+; Accepted values: yes and no
+; Default value: no
+
+;enabled=yes
More information about the svn-commits
mailing list