[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-02 10:33 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".
====================================================================== 

---------------------------------------------------------------------- 
 (0112969) mnicholson (administrator) - 2009-11-02 10:33
 https://issues.asterisk.org/view.php?id=15180#c112969 
---------------------------------------------------------------------- 
I did some testing for this patch, and while it does accomplish the task of
generating a way to uniquely identify a CDR record, but I found an issue
that may limit the usefulness of this issue for some.

In short, the CDR sequence number written to disk is different than the
sequence number the dialplan sees (although it is the same as the sequence
number on the 'h' exten).  Fixing that issue is going to be complicated
because of the way asterisk generates CDRs for bridges. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-02 10:33 mnicholson     Note Added: 0112969                          
======================================================================