[asterisk-dev] Please reopen bug #13409

[Venefax]

I think that for one call we can have several cdr records with the same
uniqueid. That is normal. I have up to 10 some times. That is not a bug in
itself, it is a misdesign of the database model. Please make sure that you
don't change the way it works now. It will break all versions in production.
What we should not have, and maybe that's what is happening, is the same
exact record stored twice, I mean, a single Dial attempt being recorded
twice, that would be fatal and it would generate chaos. Every Dial attempt
should generate a single CDR record.

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Steve Murphy
Sent: Thursday, September 04, 2008 8:34 PM
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] Please reopen bug #13409

On Thu, 2008-09-04 at 18:36 -0300, Daniel Ferrer wrote:
> I tested today 1.4.22-rc3, as I see it includes patch for issue #13409.
> 
> This patch is causing me CDR problems, I use cdr_mysql (from addons
> package) as backend, and in a normal call A->B, this patch causes to 
> post the CDR twice, giving me a constraint key violation (uniqueid is 
> primary key in cdr table).
> 
> Can you reopen this? I've a slighty modified patch that calls also 
> ast_cdr_detach but doesn't post a new cdr. I cannot post it or write a 
> note to this issue because it is in 'fixed' state.
> 

Daniel--

I'll be looking into this. I realized that calling cdr_detach() to free the
cdr before destroying the channel might be a rash thing to do, but saw no
doubles in my testing, so thought that the single-channel filter might be
taking care of this situation. Evidently not.

The bug has been re-opened, so please attach your fix and I'll see what I
can do.

murf

> thanks
> bye
> 
--
Steve Murphy
Software Developer
Digium