[asterisk-bugs] [JIRA] (ASTERISK-24016) CDR logs multiple unanswered devices despite unanswered=no

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222443#comment-222443 ] 

Matt Jordan commented on ASTERISK-24016:
----------------------------------------

What you are seeing is the intended behaviour in Asterisk 12+. This is a documentation issue - the  {{unanswered}} documentation in the sample config file clearly conflicts a bit, and the documentation in the CDR specification on this facet is pretty lacking. We'll get that cleaned up.

Why did this behaviour change?

In Asterisk 12+, from the perspective of the CDR engine, dialling is now a common operation between all applications. If FollowMe, or Dial, or Queue, or anyone else performs a dial operation, the CDR engine views that as the same operation. This solved a large class of problems where certain dial operations created the wrong CDR in previous versions of Asterisk when initiated by a particular application (such as Queue). However, it also means that the logic for handling dial operations is the same, regardless of who initiated it.

In Queues, the default behaviour was to always log all agents that were dialled, regardless of the presence of the unanswered flag. In Dial, that was not the case. The philosophy taken in Asterisk 12 was: *Do not drop information*. Because we can't tell the difference between a "Queue" dial and a "Dial" dial, we output the information when there is both a Party A and a Party B.

Does that mean you have to post-process your records? Yes. To quote from the Asterisk 12 CDR spec:

{quote}
In Asterisk 12, changes in the bridging architecture necessitated a substantial upgrade to CDR behavior. The largest changes are:
* Individual components in Asterisk no longer modify CDRs directly. CDRs are produced based on the state of the channels and bridges within Asterisk. As a result, there is a much greater degree of consistency in CDRs throughout Asterisk, regardless of the application channels happen to be executing in.
* The behavior of CDRs between multiple parties is now defined.
* Depending on how channels are dialed and bridged, multiple CDRs will be created for a given call. Post-processing of these records will be required to determine the overall statistics of the call.
{quote}

> CDR logs multiple unanswered devices despite unanswered=no
> ----------------------------------------------------------
>
>                 Key: ASTERISK-24016
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24016
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/General
>    Affects Versions: 12.3.2
>            Reporter: S C
>            Assignee: Rusty Newton
>            Severity: Minor
>
> Every available device in a Dial command get a cdr record when unanswered (both by hangup or dial timeout).  Setting "unanswered" in cdr.conf to yes or no does not affect behavior.



--
This message was sent by Atlassian JIRA
(v6.2#6252)