[asterisk-bugs] [Asterisk 0016180]: [patch] CDR dispositions BUSY and FAILED are reported as NO ANSWER

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16180 
====================================================================== 
Reported By:                aatef
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   16180
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Target Version:             1.4.29
Asterisk Version:           SVN 
JIRA:                       SWP-362 
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-11-04 13:04 CST
Last Modified:              2009-12-14 15:08 CST
====================================================================== 
Summary:                    [patch] CDR dispositions BUSY and FAILED are
reported as NO ANSWER
Description: 
Asterisk 1.4.26.2 and I think all Asterisk versions after 1.4.20 all report
the calls with Disposition BUSY and FAILED as NO ANSWER calls.
So in the CDR there are only 2 DISPOSITIONS available ANSWER and NO ANSWER
only


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012946 [patch] ResetCDR does not work on non-a...
====================================================================== 

---------------------------------------------------------------------- 
 (0115219) jpeeler (administrator) - 2009-12-14 15:08
 https://issues.asterisk.org/view.php?id=16180#c115219 
---------------------------------------------------------------------- 
This patch solves the issue here, so the concern is making sure none of the
other CDR records are adversely affected. Can the reporter please test some
common scenarios? I will continue my testing as well. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-14 15:08 jpeeler        Note Added: 0115219                          
======================================================================