[asterisk-bugs] [JIRA] Closed: (ASTERISK-20332) Missing CDR rows on Abandon queue event
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Thu Sep 6 10:13:07 CDT 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan closed ASTERISK-20332.
----------------------------------
Resolution: Won't Fix
With unanswered=no, CDR records are only written if a party B is also involved in the call. With unanswered=yes, calls that do not have a party B are also recorded.
If a caller abandons a queue and no one has answered, then the expected behavior is that nothing will get written to the CDR unless you have unanswered=yes.
Note that there are other bugs regarding CDRs in queues; those may or may not get fixed in a new version of Asterisk. However, to not perturb existing systems, the behavior is not going to be modified in current release branches.
> Missing CDR rows on Abandon queue event
> ---------------------------------------
>
> Key: ASTERISK-20332
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20332
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: CDR/General
> Environment: Unix Centos
> Reporter: Mario
> Severity: Critical
>
> Sometime when a caller abandon a queue, CDR does not write the row. If I put the "unanswered = yes" option on cdr.conf, it works, but I've (obviously) more than a row per call (# of row= # of busy agents on the queue, and this is correct).
> I've read that this bug affected also previous version of Asterisk. Is there a patch?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list