[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-21 13:54 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".
====================================================================== 

---------------------------------------------------------------------- 
 (0112576) mnicholson (administrator) - 2009-10-21 13:54
 https://issues.asterisk.org/view.php?id=15180#c112576 
---------------------------------------------------------------------- 
I have reviewed the mailing list threads and given this some though.  Right
now, I am thinking of implementing a 'sequence' field that will be
incremented each time a CDR is created.  This way the value will be
available in the dialplan.  The disadvantage of this approach is that the
sequence value will not always be sequential.

The alternative is to generate the sequence value when the CDR is posted,
but the sequence value would not be available in the dialplan with this
approach.

I would like some feedback on this before I spend time working on an
implementation. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-21 13:54 mnicholson     Note Added: 0112576                          
======================================================================