[asterisk-dev] CDR fixes--- Wait a minute!! (LONG)
murf at digium.com
Fri Jun 8 17:25:34 MST 2007
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).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3227 bytes
Desc: not available
Url : http://lists.digium.com/pipermail/asterisk-dev/attachments/20070608/ad82ce41/smime.bin
More information about the asterisk-dev