[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:                     acknowledged
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-20 03:28 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".
====================================================================== 

---------------------------------------------------------------------- 
 (0112446) Nick_Lewis (reporter) - 2009-10-20 03:28
 https://issues.asterisk.org/view.php?id=15180#c112446 
---------------------------------------------------------------------- 
There was a consensus that a unique cdr id was needed. A couple of people
did not understand why it could not just be an sql field (but usage reasons
given in the thread). There was a suggestion that the cdrinstance be named
something else such as seq or sequence and there were no objections to
this. There was also a suggestion that the cdrinstance be unique to the
call based linked-id field rather than channel based unique-id field (i.e.
calls that transfer to a different source channel do not reset the
cdrinstance). There was no objection to this.

Therefore I think there is a consensus in support of the approach of Atis
Lezdins. (I do not know if he is planning to work on an implementation.) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-20 03:28 Nick_Lewis     Note Added: 0112446                          
======================================================================