[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:                     feedback
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-10-26 15:48 CDT
====================================================================== 
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".
====================================================================== 

---------------------------------------------------------------------- 
 (0112781) sum (reporter) - 2009-10-26 15:48
 https://issues.asterisk.org/view.php?id=15180#c112781 
---------------------------------------------------------------------- 
what about have a UUID in the CDR table? this could be generated when the
call start and be avaiable at the dialplan, also you don't have to worry
about what is on the cdr table. this is the way I found easier to link a
cdr record with a recorded file, I just have an app that generates the UUID
and I set it to the channel variables each time I have a new call. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-26 15:48 sum            Note Added: 0112781                          
======================================================================