[asterisk-bugs] [Asterisk 0017762]: CDR user fields not updated and CDR() returns invalid data when using Queue with "c" flag

[Asterisk Bug Tracker]

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:                     feedback
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 13:48 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0125650) lmadsen (administrator) - 2010-08-06 13:48
 https://issues.asterisk.org/view.php?id=17762#c125650 
---------------------------------------------------------------------- 
The resolution to this issue, at a minimum, is to provide some sort of
documentation to explain why this can't be resolved as-is, and to explain
why you can't expect CDRs to work as might be expected.

We need to make sure that when these types of issues come up, we document
and explain why CDRs are not designed for this type of call flow instead of
just closing them.

Bottom line: don't close this issue unless you've provided documentation
to the Asterisk source tree explaining why this can't be done ;) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-06 13:48 lmadsen        Note Added: 0125650                          
======================================================================