<br><br><div class="gmail_quote">On Tue, Sep 7, 2010 at 5:36 PM, Fabiano Carlos Heringer <span dir="ltr"><<a href="mailto:bigu@grupoheringer.com.br" target="_blank">bigu@grupoheringer.com.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Em 07/09/2010 17:15, Miguel Molina escreveu:
<div><div></div><div><blockquote type="cite">
El 07/09/10 14:49, Fabiano Carlos Heringer escribió:
<blockquote type="cite">
<font face="Arial">Is there a way to solve the mess on CDR
caused by
CDR Transfer? anyway, by paid support, no paid, or another
way... Im
going crazy about this. My boss is really furious because he
don´t
understand nothing on the CDR.<br>
<br>
I tried the 1.6.2.11, Asterisk 1.8 beta, and everything still
the same.<br>
<br>
Any solution?<br>
<br>
Thanks!<br>
<br>
</font> </blockquote>
Hi<br>
<br>
Some quick measures:<br>
<br>
1. Enable unanswered=yes on cdr.conf and try to see if it helps
you
with the CDR.<br>
2. Try using CEL (Channel Event Logging) in 1.8-beta and try to
see if
that helps in a definite way.<br>
<br>
Cheers,<br>
<pre cols="72">--
Ing. Miguel Molina
Grupo de Tecnología
Millenium Phone Center
</pre>
</blockquote>
</div></div><font face="Arial">Hi, will make this change on my cdr.conf<br>
<br>
About CEL on asterisk 1.8 i tried some test on my test server, he
really logs each event on log, but i did not understood how he
will work on a user view (most simple). It´s possible to log this
events on a database such mysql?<br>
<br>
Thanks!<br></font></div></blockquote><div><br>Sorry for the delay, things have been busy here. <br><br>Yes, there are problems with the existing CDR interface, mostly historical, because as Asterisk<br>grew, the CDR system became obsolete. There were attempts to make it work, but structurally<br>
and architecturally, it was just not going to work.<br><br>CEL was my answer, built on the channel event goodness that Russell. It's now in 1.8; but it<br>lacks a converter to CDRs. You *could* just use the string of events coming out of CEL, but...<br>
I'd love to see your SQL statements to pull things together!<br><br>
I had begun writing a CEL->CDR converter, but got laid off before I could finish it.<br>
It makes a good start toward a finished package. Long ago (what, almost 2 years now?)<br>
I proposed two methods of generating CDR's. One was 'simple', the other 'Complex", or "Leg Based".<br>
<br>
Since then, I refined the doc to just 'Simple', and outlined with some examples how it would/should work.<br>
The doc still needs to be cleaned up, but you may make sense of it.<br>
<br>
The trouble with CDRs is that no two shops can agree on a CDR standard that involves transfers, parks, etc.<br>
Beyond the "start", "answer", and "end" times, and some fundamental data about the call (source, dest, <br>
responsible party, etc.) There isn't much unity about what timepoints need to be represented, etc. And I'd seen<br>
so few implementations, I couldn't judge a good way to generalize the CDR converter. <br>
<br>
So, I challenge everyone to look at my simple CDR definition, and see it would possible for you to adapt it<br>
(perhaps via a mapping from it to your desired conflagration/configuration.<br><br>To look at the doc, do "svn co <a href="http://svn.digium.com/svn/team/murf/asterisk-RFCs">http://svn.digium.com/svn/team/murf/asterisk-RFCs</a> and look at the <br>
document in there (I have a few different formats, the .docx is the source).<br><br>It's been in flux. Just the first few examples are accurate. Let me know what you think.<br><br>murf<br><br clear="all"><br></div></div>
<br>-- <br>Steve Murphy<br>ParseTree Corp<br>
<br>