[Asterisk-Dev] dev conf topic: better CDRs

[C. Maj]

On Tue, 22 Feb 2005, Kevin P. Fleming waxed:

> Matthew Boehm wrote:
> > There are many Asterisk users out there than need better/more detailed CDRs.
> > Our class 4/5 switch spits out over 80 different columns for each call that
> > passes thru. Most notably are the differences between "true" number and
> > "translated" number.
>
> I have some code in the works that will likely solve this issue... but
> in a very different way.
>
> My CDR system (not in place yet, only prototyped) actually uses a
> two-level CDR: the master record looks much like the existing one, and
> is created when the call arrives in Asterisk. Nothing is updated in that
> record except for the endtime and duration fields when the call ends.
>
> In addition, that master record has "child" records that are created as
> the call moves through Asterisk; every Goto (implicit or explicit)
> generates a record, apps can add entries for "events" that occurred
> (app_voicemail could record an entry for "voicemail left", etc.),
> extensions entered by the caller at an IVR menu (or any other place)
> generate records, Dial generates records for dialed targets and the one
> that answers, etc.

Does it rely on parsing the manager "Newexten" events ?  It
seems like this would be a route that can co-exist with the
current CDR system.  I think those events spit out Unique
IDs with everything.

Just curious.

--Chris


-- 
Chris Maj, Rochester
cmaj_at_freedomcorpse_dot_com
Pronunciation Guide: Maj == May