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

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Aug 5 12:28:24 CDT 2009


The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=14844 
====================================================================== 
Reported By:                ruddy
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14844
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.22 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-04-07 09:48 CDT
Last Modified:              2009-08-05 12:28 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
====================================================================== 

---------------------------------------------------------------------- 
 (0108666) lmadsen (administrator) - 2009-08-05 12:28
 https://issues.asterisk.org/view.php?id=14844#c108666 
---------------------------------------------------------------------- 
As mnicholson has tried several times to reproduce this issue and cannot,
I'm closing this as "unable to reproduce". If the reporter can find myself
or mnicholson on IRC in #asterisk-bugs (irc.freenode.net), then we can
perhaps figure out why you're seeing this issue, but he cannot.

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-05 12:28 lmadsen        Note Added: 0108666                          
2009-08-05 12:28 lmadsen        Status                   feedback => closed  
======================================================================




More information about the asterisk-bugs mailing list