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

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15180 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   15180
Category:                   CDR/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
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:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-05-22 08:45 CDT
Last Modified:              2009-05-22 08:49 CDT
====================================================================== 
Summary:                    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".
====================================================================== 

---------------------------------------------------------------------- 
 (0105295) russell (administrator) - 2009-05-22 08:49
 https://issues.asterisk.org/view.php?id=15180#c105295 
---------------------------------------------------------------------- 
Unfortunately, feature requests without patches are not accepted on the
issue tracker.

If you would like to discuss this idea on the asterisk-dev list, that
would be welcome. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-22 08:49 russell        Note Added: 0105295                          
2009-05-22 08:49 russell        Status                   new => resolved     
2009-05-22 08:49 russell        Resolution               open => won't fix   
2009-05-22 08:49 russell        Assigned To               => russell         
2009-05-22 08:49 russell        Status                   resolved => closed  
======================================================================