[asterisk-dev] CDR fixes--- Wait a minute!! (LONG)
kkovachev at varna.net
Sat Jun 9 00:20:44 MST 2007
On Fri, 08 Jun 2007 18:25:34 -0600, Steve Murphy wrote
> 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 think
> > > strangely!
> > I couldn't care less about transfers, ForkCDR, I just want to be able to save
> > more data with a CDR and to be able to prove a call lasted at least for an X
> > amount of time. If I have a call that apparently lasted for 24 hours it would
> > be great to have 24 (or 12 or 240) CDRs to prove that, yes, asterisk really
> > thought we had a call all that time.
> > But then. I don't use Asterisk in an office/home environment, even our
> > diallingplan is totally different from what most people here have....
> The CDR stuff is built to just generate data about a closed call.
> There's no mechanisms available to 'interrupt' and generate state about
> channels, or to split up CDRs into hour or 10-minute chunks. Such stuff
> 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).
You may want to take a look at http://bugs.digium.com/view.php?id=6335
> Steve Murphy
> Software Developer
More information about the asterisk-dev