[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-11-20 11:17 CST
====================================================================== 
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.
====================================================================== 

---------------------------------------------------------------------- 
 (0095192) murf (administrator) - 2008-11-20 11:17
 http://bugs.digium.com/view.php?id=13665#c95192 
---------------------------------------------------------------------- 
I **tried** the manager interface, but while the call files work fine,
something is amiss with my manager config, I guess. I don't want to waste
more time on it. I'll clear up the manager stuff later.
When I say: 

Action: Originate
Channel: Dahdi/1
Exten: 102
Context: extension
Priority: 1
Timeout: 10
CallerID: d1a
Account: ManPlacedCall

Dahdi/1 gets called and then is immediately hung up. No explanation,
even if I turn up verbose to 40 and Debug to 20. I'll figure it out
later.

riksta: This bug is posted against 1.4; 1.6.0 is feature frozen, and not
all bug fixes get posted against it. Try 1.6.1, and see if it's having the
same problem. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-20 11:17 murf           Note Added: 0095192                          
======================================================================