[asterisk-bugs] [Asterisk 0013665]: Wrong CDR is posted if call files or Manager API Originate is used

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13665 
====================================================================== 
Reported By:                corruptor
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   13665
Category:                   CDR/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.22 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-10 09:07 CDT
Last Modified:              2008-10-30 13:48 CDT
====================================================================== 
Summary:                    Wrong CDR is posted if call files or Manager API
Originate is used
Description: 
This has changed between 1.4.21 and 1.4.22.
If we use call files and call has been answered asterisk sets DIALSTATUS
variable to ANSWER but disposition field of the CDR is NO ANSWER.
====================================================================== 

---------------------------------------------------------------------- 
 (0094427) davidw (reporter) - 2008-10-30 13:48
 http://bugs.digium.com/view.php?id=13665#c94427 
---------------------------------------------------------------------- 
This may or may not be the same underlying problem, but on 1.6.0, if you
AMI Redirect an answered call and CDRReset(av) in the new extension, you
get a proper CDR for the original Dial, output during the reset, but the
CDR for an answered Dial, in the new extension, shows a good start, end and
answer time, for the new segment, but shows a NO ANSWER status.

(Incidentally, I resorted to just using ResetCDR because ForkCDR didn't
seem helpful and ResetCDR effectively forks the CDR, anyway.) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-30 13:48 davidw         Note Added: 0094427                          
======================================================================