This is working perfect for me since I applied the patch.<br><br><br><br><div><span class="gmail_quote">On 6/19/06, <b class="gmail_sendername">Juan Pablo Abuyeres</b> <<a href="mailto:jpabuyer@tecnoera.com">jpabuyer@tecnoera.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I tried JBenden's patch posted on <a href="http://bugs.digium.com/view.php">
http://bugs.digium.com/view.php</a>?<br>id=7274 and it works very well. No CDRs are lost since the patch is<br>applied. I'm reporting this here as requested by vechers.<br><br><br>On Thu, 2006-06-01 at 17:50 -0400, Joseph Benden wrote:
<br>> Hello,<br>><br>> This conversation was dropped in the past as someone felt the spooling<br>> native to 1.2.x would handle the situation. However; the opposite is<br>> true. The code in cdr_addon_mysql will not report back to any calling
<br>> code as to whether the database operation happened successfully. Thus<br>> losing CDRs is a true reality. Personally, I've been using my<br>> original patch whereby I spool the records to a file. This change was
<br>> not accepted for CVS HEAD at that time.<br>><br>> The way to tell if you are losing records is to run the Perl CSV (in<br>> the bug id) import tool, taking a count before hand, and afterwords.<br>> If you've got more records, then you lost some. However, getting the
<br>> records that fell out would require more work. However the major<br>> reason for CDR loss stems from the database disappearing.<br>><br>> I have never researched the other real-time cdr modules. Thus I can
<br>> not speak for the other ones.<br>><br>> -Joe<br>> Thralling Penguin LLC<br>><br>><br>> On Thu, 2006-06-01 at 23:29 +0200, Matt Riddell (IT) wrote:<br>> > Juan Pablo Abuyeres wrote:<br>> > > Hi,
<br>> > ><br>> > > I am losing CDR records on my MySQL backend. I just compared CSV records<br>> > > with MySQL's and I was surprised with the difference. Searching a bit, I<br>> > > hit this bug:
<a href="http://bugs.digium.com/view.php?id=4953">http://bugs.digium.com/view.php?id=4953</a><br>> > ><br>> > > Questions:<br>> > ><br>> > > 1.- kpfleming says "The spooling issue will continue to be a problem for
<br>> > > v1-0 users, but HEAD (and v1-2) users can use the built-in spooling in<br>> > > the CDR engine.". That "built-in spooling" has to be enabled somewhere<br>> > > or is it automatic?
<br>> > ><br>> > > 2.- If there is a built-in spooling into CDR itself and there is no<br>> > > spooling in cdr_addon_mysql, when the mysql server is down, crashed,<br>> > > full, unwired, firewalled, or whatever.. is built-in spooling in CDR
<br>> > > itself supposed to handle that??<br>> > ><br>> > > I'm using asterisk-1.2.7.1 and asterisk-addons-1.2.2<br>> ><br>> > Is there any way that we can tell which cdr records have been lost? Is
<br>> > there an error in the console? Does this apply to all realtime cdr<br>> > operations i.e. postgres, odbc etc or just MySQL?<br>> ><br>> _______________________________________________<br>> --Bandwidth and Colocation provided by
<a href="http://Easynews.com">Easynews.com</a> --<br>><br>> asterisk-dev mailing list<br>> To UNSUBSCRIBE or update options visit:<br>> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev
</a><br><br>_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:
<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br></blockquote></div><br>