[asterisk-bugs] [Asterisk 0014844]: Asterisk call file has CDR always set to NO ANSWER

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14844 
====================================================================== 
Reported By:                ruddy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14844
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.22 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-07 09:48 CDT
Last Modified:              2009-06-30 03:46 CDT
====================================================================== 
Summary:                    Asterisk call file has CDR always set to NO ANSWER
Description: 
I'm having a weird behaviour with outgoing calls generated by call file
into /var/spool/asterisk/outgoing

When the callee answers the call, and the call is forward to an extension
where we answer it, we still have 'NO ANSWER' as CDR disposition
====================================================================== 

---------------------------------------------------------------------- 
 (0107221) vmikhnevych (reporter) - 2009-06-30 03:46
 https://issues.asterisk.org/view.php?id=14844#c107221 
---------------------------------------------------------------------- 
We had the same issue on 1.6.1.1. Main problem was billsec=0.
The solution/workaround looks a bit magical, but it worked for us. In
cdr.conf there is a "unanswered=no" default value. We changed it to "yes",
but it didn't help. BUT, then we changed it back to "no", and after that
billsec was correct and calls were marked ANSWERED. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-30 03:46 vmikhnevych    Note Added: 0107221                          
======================================================================