[asterisk-bugs] [Asterisk 0016222]: [patch] CDR always set disposition as NO ANSWER with .call files
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Apr 22 16:58:05 CDT 2010
The following issue has been RESOLVED.
======================================================================
https://issues.asterisk.org/view.php?id=16222
======================================================================
Reported By: telles
Assigned To: mnicholson
======================================================================
Project: Asterisk
Issue ID: 16222
Category: CDR/General
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Asterisk Version: 1.6.1.9
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2009-11-11 08:38 CST
Last Modified: 2010-04-22 16:58 CDT
======================================================================
Summary: [patch] CDR always set disposition as NO ANSWER with
.call files
Description:
CDR always set disposition as NO ANSWER with .call files.
If you set "unanswered=no" at cdr.conf you won't get any CDR record.
It works fine with any 1.4.X asterisk version.
All 1.6 releases has the same problem.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
duplicate of 0014167 [patch] CDR does not get produced with ...
has duplicate 0016227 Call files produces "NO ANSWER&quo...
related to 0016797 Originating a call from within the dial...
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-04-22 16:58 svnbot Status assigned => resolved
2010-04-22 16:58 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list