[asterisk-bugs] [Asterisk 0015180]: [patch] No unique identifier for CDR

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
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:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1-beta1 
Regression:                 No 
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-08-25 01:59 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".
====================================================================== 

---------------------------------------------------------------------- 
 (0109576) tilghman (administrator) - 2009-08-25 01:59
 https://issues.asterisk.org/view.php?id=15180#c109576 
---------------------------------------------------------------------- 
This needs to be discussed on the -dev list prior to implementing this
feature.  Please send a new post to the asterisk-dev list, detailing the
problem you're trying to solve and your proposed solution.  If there is
consensus that your approach is best, this patch will be committed. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-25 01:59 tilghman       Note Added: 0109576                          
2009-08-25 01:59 tilghman       Status                   assigned => feedback
======================================================================