[asterisk-bugs] [Asterisk 0012368]: CDR written with incorrect uniqueid

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12368 
====================================================================== 
Reported By:                bcnit
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   12368
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-04-2008 10:54 CDT
Last Modified:              04-09-2008 18:14 CDT
====================================================================== 
Summary:                    CDR written with incorrect uniqueid
Description: 
Under certain circumstances, I am experiencing multiple CDRs with the same
unique ID. This is 100% reproducible.

The situation is this:

SIP device A calls SIP device B, B puts A on hold and on a second line,
dials C. B speaks to C and then transfers C to A by pressing the 'transfer'
button on the phone (or hanging the handset up which performs a transfer
automatically).

The unique ID which is duplicated is the one allocated to the original A
to B call (it is duplicated onto the B to C call).

Dialplan debugging shows that when the call from B to C is made it is
allocated a genuinely unique unique ID, but when this CDR comes to be
written out, the unique ID is empty and is replaced with the unique ID of
the original call (i.e. the first call from A to B).

If CDR logging to MySQL is configured as documented on the voip-info wiki
(with the uniqueID field being the primary key), Asterisk can't write the
duplicate record out to the database.

====================================================================== 

---------------------------------------------------------------------- 
 murf - 04-09-08 18:14  
---------------------------------------------------------------------- 
I hate to say this, but the CDR system is really quite broken in Asterisk,
when it comes to transfers, 3-way confs, and suchlike.

To assume a uniqueID will always be unique in CDR land, is not a good
assumption. If you re-arrange your database to allow this field to be
whatever it wants to be, you'll be better off. You might even be able to
use matching uniqueID's to help sort out xfer situations. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-09-08 18:14  murf           Note Added: 0085263                          
======================================================================