On Wed, 2007-06-06 at 12:43 +0100, Steve Davies wrote: > On 5/31/07, Carlos Chavez <[EMAIL PROTECTED]> wrote: > > Sometimes I get the following error on the console: > > > > [May 31 11:14:01] ERROR[23502]: cdr_addon_mysql.c:230 mysql_log: > > mysql_cdr: Failed to insert into database: (1062) Duplicate entry > > '1180628004.3214' for key 1 -- Zap/38-1 answered UniCall/11-1 > > > > Why would the UNIQUEID be duplicated? Isn't is supposed to be > > UNIQUE? > > This worries me a bit because the customer is losing calls that will not > > appear in their CDR records for billing. > > > > As far as I know, you can have several CDR records for a single call. > The unique-id is only unique for the call, and is not necessarily > unique in a database context.
I agree. In the stuff I'll be doing, I purposely try to group records involving transfers with the same uniqueid. I can do this for all the call segments involved in a single bridge. You might look at the table definition for MySQL and see if the uniqueid is marked as "UNIQUE", if so, remove that spec from that column... murf > > Steve > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
