Events & Fields

While CDRs and the Manager are basically both event tracking mechanisms, CEL tries to track only those events that might pertain to billing issues.

See table 11.1 for a list of events raised by CEL and table 11.2 for the list of fields passed for each CEL event.


Table 11.1: List of CEL Events
Event Description
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 conference
CONF_END The time the last person left a conf (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 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.



Table 11.2: List of CEL Event Fields
Field Description
eventtype The name of the event; see the above list; each is prefixed with "EV_".
eventtime The time the event happened
cidname CID name field
cidnum CID number field
cidani CID ANI field
cidrdnis CID RDNIS field
ciddnid CID DNID field
exten The extension in the dialplan
context The context in the dialplan
channame The name assigned to the channel in which the event took place
appname The name of the current application
appdata The arguments that will be handed to that application
amaflags The AMA flags associated with the event; user assignable.
accountcode A user assigned datum (string)
uniqueid Each Channel instance gets a unique ID associated with it.
userfield A user assigned datum (string)
linkedid the per-call id, spans several events, possibly.
peer For bridge or other 2-channel events, this would be the other channel name


lmadsen 2010-10-21