Summary:ASTERISK-09790: [branch] Event Based CDR system -- CEL (channel Event Logging)
Reporter:Steve Murphy (murf)Labels:
Date Opened:2007-07-02 09:46:59Date Closed:2008-07-14 15:10:19
Versions:Frequency of
Description:This entry is to request a new CDR system based on Single Events.
I call CEL (Channel Event Logging).
It will be based on the Event system of Russell's; instead of generating
CDR records that would be a direct input to a billing system, it will generate
a series of events that can be linked together into a billing record. It's
a bit lower-level, and has the advantage of the multi-process features of the
event system, the security of logging events to a DB (or file).

Branch is http://svn.digium.com/view/asterisk/team/murf/newcdr/

What's done: the CDR backends; event generation (mostly)
What's needed: Processes to gather event strings into billing records.
              More event tracking for transfers, queues, and meetme's.
Comments:By: snuffy (snuffy) 2007-07-02 17:25:43

sounds good murf..
look forward to testing it

By: Adam Long (worldlink) 2007-11-20 11:43:26.000-0600

I really like this model Murf.. I'm suprised there is not more of a reaction to it.  But i believe it is something that is going to become more and more vital as the complexity of this system grows and features are added.  And i think once it is available alot of users will really like the capabilities.

I was thinking of writing something to use the manager interface to collect events and build CDRs but a built in CDR engine with this is much better.

Way to think ahead!

Let me know if there is anything i can do to help.

Would be nice to have a pluggable framework where CDRs writer modules can extend the framework to allow for easy format modules like CSV, SQL, XML, Radius, etc down the road.

By: Donny Kavanagh (donnyk) 2008-03-12 23:54:09

Murf is it safe to close this given newcdr has been put on hold?

By: Steve Murphy (murf) 2008-05-26 18:12:29

WIth the help/guiding influence of Brian Degenhardt, we are now again, after a pause, putting some effort into the newcdr branch. We have incorporated the "linkedid" channel field, which is updated during bridges and call attempts from one channel to another, the "oldest" linkedid winning if the new channel has an entry. This field then provides the "glue" to tie transfers together. Brian has been doing work to set the linkedid field earlier, make it stickier, and many other improvements. His plan is to write a CEL backend that generates CDR's that apply to "logical calls", a model we both guess most users will find useful.

More to come. Don't touch that channel!

By: Steve Murphy (murf) 2008-07-14 15:08:22

We decided to close this bug; the project isn't going away, but Mantis is
just not the best spot to discuss this. Email is working just fine.
Good progress has been made; the branch nears its time to be merged to trunk.