[asterisk-bugs] [Asterisk 0017762]: CDR user fields not updated and CDR() returns invalid data when using Queue with "c" flag
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Aug 6 18:08:59 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17762
======================================================================
Reported By: kkm
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17762
Category: CDR/General
Reproducibility: have not tried
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: 1.6.2.10
JIRA: SWP-1992
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-07-29 19:52 CDT
Last Modified: 2010-08-06 18:08 CDT
======================================================================
Summary: CDR user fields not updated and CDR() returns
invalid data when using Queue with "c" flag
Description:
When Queue() is called with the "c" flag (continue dialplan after agent
hangup):
1. assignments made to CDR(...) values from the h extension are not
written to the database; these are the userfield and all additional custom
fields (used with adaptive_odbc).
2. CDR() fields are reset to defaults. These are CDR(billsec),
CDR(duration), CDR(disposition) -- possibly more.
======================================================================
----------------------------------------------------------------------
(0125674) kkm (reporter) - 2010-08-06 18:08
https://issues.asterisk.org/view.php?id=17762#c125674
----------------------------------------------------------------------
“Well the thing with CDRs is that we're trying not to change them
anymore. Everytime we "fix" something for one person, we break CDRs for
someone else.”
Amen to that! I've seen some subtle changes in the past with upgrades.
And internally, in our software we have couple of such poisonous features
as well. :-)
Issue History
Date Modified Username Field Change
======================================================================
2010-08-06 18:08 kkm Note Added: 0125674
======================================================================
More information about the asterisk-bugs
mailing list