[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-27 10:50 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".
====================================================================== 

---------------------------------------------------------------------- 
 (0112816) Nick_Lewis (reporter) - 2009-10-27 10:50
 https://issues.asterisk.org/view.php?id=15180#c112816 
---------------------------------------------------------------------- 
Be it call sequence or uuid, I think there is a broader question regarding
linkedid. This or a similar structure to represent the call would still be
useful. It seems crazy holding cdr info against the channel and then having
to duplicate it all every time a call transfer causes the channel to
change. Couldnt channels just have references to the call they are
currently part of and the new call structure then reference the individual
call detail records (ast_cdr). Wouldnt this prevent a lot of faffing about
during transfers etc 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-27 10:50 Nick_Lewis     Note Added: 0112816                          
======================================================================