[asterisk-bugs] [Asterisk 0015180]: [patch] No unique identifier for CDR

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15180 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   15180
Category:                   CDR/General
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-22 08:45 CDT
Last Modified:              2009-11-03 10:21 CST
====================================================================== 
Summary:                    [patch] No unique identifier for CDR
Description: 
There is no unique identifier for a CDR. This makes it difficult to
associate other things such as call monitor recordings with a CDR. 
Each call does have a unique identifier which is stored in the CDR as
"uniqueid" but there may be multiple CDRs representing one call. For
example ResetCDR(w) saves a CDR and creates a new one for the call. Both
CDR have the same "uniqueid".
====================================================================== 

---------------------------------------------------------------------- 
 (0113056) mnicholson (administrator) - 2009-11-03 10:21
 https://issues.asterisk.org/view.php?id=15180#c113056 
---------------------------------------------------------------------- 
2. I like that idea.  That is the name I was initially going to use for
that function.  I will make this change.

3. I am not 100% sure how transfers are handled in all cases.  Asterisk
has different code for '#' transfers, channel based transfers, and manager
initiated transfers.  Additionally, this code interacts with the bridging
code in different ways in different cases (e.g. the channel based CDR is
not always reset).  Ideally, this code all needs to be audited and
restructured to have uniform behavior where possible.

In the specific case you cite, you should not need to do ResetCDR(w) as
the bridge CDR should be written for that call.  You may want to do
ResetCDR() without the 'w' flag.  As I said before, this code my have bugs,
so I recommend you test these scenarios yourself.  Please report any bugs
you find. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-03 10:21 mnicholson     Note Added: 0113056                          
======================================================================