<br><br><div class="gmail_quote">On Thu, Mar 12, 2009 at 1:13 PM, Matt Riddell <span dir="ltr"><<a href="mailto:lists@venturevoip.com" target="_blank">lists@venturevoip.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On 13/03/2009 8:02 a.m., nik600 wrote:<br>
> Hi to all.<br>
><br>
> What can i do if a customer needs to log in the CDR all the dialpan<br>
> actions related to a call?<br>
> I mean, not only the lastapp e the lastdata but all the dialpan actions!<br>
><br>
> I know that the actual CDR system store one record for each call (and<br>
> for billing purposes this can be correct) but in some cases the<br>
> approach needed is something similar to the queue_log.<br>
><br>
> I know that exists ResetCDR and ForkCDR but they don't do what i need,<br>
> expecially because they fill-in lastdata and lastapp with "ResetCDR"<br>
><br>
> So, what can i do?<br>
<br>
</div>Use the Asterisk Manager with UserEvent?</blockquote><div><br>I think Matt's approach is more practical; Really, you can't just use the <br>CDR logs, because that's what isn't enough for you. Some folks have reported<br>
getting by with a mix of CDR's and manager events, but ooohhhh, it's ugly!<br>It can be done, tho.<br><br>But you could read my proposed CDR doc by checking it out of SVN:<br><br>svn co <a href="http://svn.digium.com/svn/asterisk/team/murf/RFCs" target="_blank">http://svn.digium.com/svn/asterisk/team/murf/RFCs</a><br>
<br>and reading the pdf in the dir that will be created, and letting me know<br>what you think of it. The Leg-based approach with your own splits might<br>be the ticket you are interested in.<br><br>Now, I might add this: surely you are jesting about *every* dialplan command!<br>
Most dialplan apps that get used are things like "gotoIf" and such, that take<br>some number of microseconds to execute. It'd be silly timing such, as the<br>CDR records are currently rounded off to whole seconds. My current thinking<br>
is to specify exactly which app invocations you want to track; those involved<br>with dialing would be automatically tracked. Or time groups of invocations via<br>forcing a leg-split via a simple dialplan application call...<br>
<br>again, read the doc, and let me know what you think.<br><br>murf<br></div></div><br><br clear="all">
<br>-- <br>Steve Murphy<br>ParseTree Corp<br><br>