[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-03 10:08 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".
====================================================================== 

---------------------------------------------------------------------- 
 (0113054) Nick_Lewis (reporter) - 2009-11-03 10:08
 https://issues.asterisk.org/view.php?id=15180#c113054 
---------------------------------------------------------------------- 
1. Yes I see linkedid+sequence it is then (I still have a preference for a
call/linkedid structure to hold a sequence per call rather than a global
sequence shared by all calls but I accept that this adds complexity for
little gain)

2. Ok but could the function names be a bit more informative. 
ast_cdr_dup_unique_swap() may be better than ast_cdr_dup_unique2()

3. At the moment my dialplan does a Reset(w) if it sees the BLINDTRANSFER
flag but it sounds as if this may not be necessary if the old cdr is posted
and the new cdr produced as part of a transfer process. Does this also
apply to channel tech specific transfers? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-03 10:08 Nick_Lewis     Note Added: 0113054                          
======================================================================