System information

Here is the CDR that was logged to Master.csv as a result of this call:
"""Console"" <2565551212>","2565551212","101","LocalSets","Console/dsp",
"SIP/0000FFFF0002-00000000","Dial","SIP/0000FFFF0002","2010-08-16 01:16:10",
"2010-08-16 01:16:16","2010-08-16 01:16:29","19","13","ANSWERED",
"DOCUMENTATION","","1281935770.2","",2
Caveats
The CDR system in Asterisk works very well for fairly simple call scenarios. However,
as call scenarios get more complicated, involving calls to multiple parties, transfers,
parking, and other such features, the CDR system starts to fall short. Many users report
that the records do not show all of the information that they expect. Many bug fixes
have been made to address some of the issues, but the cost of regressions or changes
in behavior when making changes in this area is very high since these records are used
for billing.
As a result, the Asterisk development team has become increasingly resistant to making
additional changes to the CDR system. Instead, a new system, channel event logging
(CEL), has been developed that is intended to help address logging of more complex
call scenarios. Bear in mind that call detail records are simpler and easier to consume,
though, so we still recommend using CDRs if they suit your needs.
CEL (Channel Event Logging)
Channel event logging (CEL) is a new system that was created to provide a more flexible
means of logging the details of complex call scenarios. Instead of collapsing a call down
to a single log entry, a series of events are logged for the call. This provides a more
accurate picture of what has happened to the call, at the expense of a more complex log.
Channel Event Types
Each CEL record represents an event that occurred for a channel in the Asterisk system.
Table 24-7 lists the events that are generated by Asterisk as calls are processed.
Table 24-7. CEL event types
CEL event type Description
CHAN_START A channel has been created.
CHAN_END A channel has been destroyed.
LINKEDID_END The last channel with a given linkedid has been destroyed.
ANSWER A channel has been answered. On a channel created for an outbound call, this event will be generated
when the remote end answers.
HANGUP A channel has hung up. Generally, this event will be followed very shortly by a CHAN_END event.
The difference is that this event occurs as soon as a hangup request is received, whereas
CEL (Channel Event Logging) | 537