[asterisk-dev] CDR fixes--- Wait a minute!! (LONG)
stotaro at asteriskhelpdesk.com
Fri Jun 8 19:42:02 CDT 2007
> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-
> bounces at lists.digium.com] On Behalf Of Steve Murphy
> Sent: Friday, June 08, 2007 8:26 PM
> To: Asterisk Developers Mailing List
> Subject: Re: [asterisk-dev] CDR fixes--- Wait a minute!! (LONG)
> On Fri, 2007-06-08 at 22:49 +0200, Andreas Sikkema wrote:
> > On Friday 08 June 2007 19:16:56 Steve Murphy wrote:
> > > Share your thoughts, or I'll do your thinking for you! Warning! I
> > > strangely!
> > I couldn't care less about transfers, ForkCDR, I just want to be
> > more data with a CDR and to be able to prove a call lasted at least
> an X
> > amount of time. If I have a call that apparently lasted for 24 hours
> > be great to have 24 (or 12 or 240) CDRs to prove that, yes, asterisk
> > thought we had a call all that time.
> > But then. I don't use Asterisk in an office/home environment, even
> > diallingplan is totally different from what most people here
> The CDR stuff is built to just generate data about a closed call.
> There's no mechanisms available to 'interrupt' and generate state
> channels, or to split up CDRs into hour or 10-minute chunks. Such
> would eat up a lot of CPU cycles. If a call takes like a week to
> complete, you'll have to PRAY that asterisk stays alive that long, so
> you get the CDR.
> You might be able to invent a neat little program to attach to the
> asterisk manager interface, and monitor the calls going on, making
> regular reports about 'long calls' (say, more than an hour).
> Steve Murphy
> Software Developer
Use an application like queuemetrics on var/log/asterisk/full, or use
queues for everything and actually use queuemetrics.
Just off the top of my head, maybe not too practical.
More information about the asterisk-dev