[asterisk-bugs] [Asterisk 0015180]: [patch] No unique identifier for CDR
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Oct 27 09:36:35 CDT 2009
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: feedback
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-10-27 09:36 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".
======================================================================
----------------------------------------------------------------------
(0112812) mnicholson (administrator) - 2009-10-27 09:36
https://issues.asterisk.org/view.php?id=15180#c112812
----------------------------------------------------------------------
Something like that would work in theory. Though I like the idea of an
actual uuid.
Issue History
Date Modified Username Field Change
======================================================================
2009-10-27 09:36 mnicholson Note Added: 0112812
======================================================================
More information about the asterisk-bugs
mailing list