[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 11:39 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".
====================================================================== 

---------------------------------------------------------------------- 
 (0112982) Nick_Lewis (reporter) - 2009-11-02 11:39
 https://issues.asterisk.org/view.php?id=15180#c112982 
---------------------------------------------------------------------- 
For call monitoring I need the ability to start a new CDR (with new
sequence) at any time of my choosing. This is not just for when the parties
to a call change (e.g. transfers) but also when a party starts or stops
monitoring a call so that the CDR reflects the actual duration of the
recording. I believe that ResetCDR(w) is the correct way to accomplish this
in the dialplan so I think ResetCDR(w) should change the sequence number.

The sequence number size looks a bit small now that it is global rather
than per channel or per call/linkedid. Would a uuid be better if there are
asterisk restarts? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-02 11:39 Nick_Lewis     Note Added: 0112982                          
======================================================================