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

Asterisk Bug Tracker noreply at bugs.digium.com
Wed May 27 05:02:15 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
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:                     assigned
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-05-27 05:02 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".
====================================================================== 

---------------------------------------------------------------------- 
 (0105494) Nick_Lewis (reporter) - 2009-05-27 05:02
 https://issues.asterisk.org/view.php?id=15180#c105494 
---------------------------------------------------------------------- 
Tested ok with mysql cdr database and following dialplan macro:

[macro-record-enable]
exten => s,1,GotoIf($["${BLINDTRANSFER}" = ""]?check)
exten => s,n,ResetCDR(w)
exten => s,n,StopMonitor()
exten => s,n(check),AGI(recordingcheck)
exten => s,n,MacroExit()
exten => s,n(record),MixMonitor(${UNIQUEID}i${CDR(cdrinstance)}.wav)

Each transfer of a call creates a new CDR and a corresponding new
callmonitor recording. The callmonitor recording filenames permit them to
be linked unambiguously with the rows of a CDR listing thus permitting
click to play functionality 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-27 05:02 Nick_Lewis     Note Added: 0105494                          
======================================================================




More information about the asterisk-bugs mailing list