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

Tue Aug 26 14:55:29 CDT 2014

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

Rusty Newton edited comment on ASTERISK-24016 at 8/26/14 2:53 PM:
------------------------------------------------------------------

 I tested with the core supported cdr_custom backend. The behavior appears as you describe.

My test was SIP/6001 dialing Dial(SIP/6002&SIp/6004) and letting it timeout to a Hangup

 * CDR written with {{unanswered=yes}}
{noformat}
"""Alice"" <6001>","6001","6999","from-internal","SIP/6001-00000002","SIP/6002-00000003","Dial","SIP/6002&SIP/6004,15","2014-08-26 12:11:45","","2014-08-26 12:12:00","15","0","NO ANSWER","DOCUMENTATION","","1409073105.4","",3
"""Alice"" <6001>","6001","6999","from-internal","SIP/6001-00000002","SIP/6004-00000004","Dial","SIP/6002&SIP/6004,15","2014-08-26 12:11:45","","2014-08-26 12:12:00","15","0","NO ANSWER","DOCUMENTATION","","1409073105.4","",6
"""Alice"" <6001>","6001","6999","from-internal","SIP/6001-00000002","","Hangup","","2014-08-26 12:12:00","","2014-08-26 12:12:00","0","0","NO ANSWER","DOCUMENTATION","","1409073105.4","",7
{noformat}

 * CDR written with {{unanswered=no}}
{noformat}
"""Alice"" <6001>","6001","6999","from-internal","SIP/6001-00000000","SIP/6002-00000001","Dial","SIP/6002&SIP/6004,15","2014-08-26 12:48:31","","2014-08-26 12:48:46","15","0","NO ANSWER","DOCUMENTATION","","1409075311.0","",0
"""Alice"" <6001>","6001","6999","from-internal","SIP/6001-00000000","SIP/6004-00000002","Dial","SIP/6002&SIP/6004,15","2014-08-26 12:48:31","","2014-08-26 12:48:46","15","0","NO ANSWER","DOCUMENTATION","","1409075311.0","",3
{noformat}

So, some CDR output is definitely getting filtered out with {{unanswered=no}}.

The documentation appears to conflict with itself. At least by the way I understand it:

In cdr.conf:
{noformat}
; Define whether or not to log unanswered calls. Setting this to "yes" will
; report every attempt to ring a phone in dialing attempts, when it was not
; answered. For example, if you try to dial 3 extensions, and this option is "yes",
; you will get 3 CDR's, one for each phone that was rung. Default is "no". Some
; find this information horribly useless. Others find it very valuable. Note, in "yes"
; mode, you will see one CDR, with one of the call targets on one side, and the originating
; channel on the other, and then one CDR for each channel attempted. This may seem
; redundant, but cannot be helped.
{noformat}

This makes me think any call as "NO ANSWER" will not be reported when the option is set to "no".

{noformat}
;
; In brief, this option controls the reporting of unanswered calls which only have an A 
; party. Calls which get offered to an outgoing line, but are unanswered, are still 
; logged, and that is the intended behaviour. (It also results in some B side CDRs being
; output, as they have the B side channel as their source channel, and no destination 
; channel.)
{noformat}

This makes me think only "NO ANSWER" calls with only an A party will not be reported with the option is set to "no".

That is, with unanswered=yes, the CDR record with only an A party is reported, and with unanswered=no it is not reported. That is what we see actually happening.

If SIP/A calls SIP/B, even if it is unanswered, there will be an A and B party on the CDR record. It looks like this option is intended to filter out CDRs showing calls between the a device and extensions that don't result in a dial, like the execution of Hangup via SIP/6001 in my test.

I'm thinking the name of the option is ambiguous and the documentation could be reworded for clarity. I'll see if a developer can validate.

was (Author: rnewton):
 I tested with the core supported cdr_custom backend. The behavior appears as you describe.

My test was SIP/6001 dialing Dial(SIP/6002&SIp/6004) and letting it timeout to a Hangup

 * CDR written with {{unanswered=yes}}
{noformat}
"""Alice"" <6001>","6001","6999","from-internal","SIP/6001-00000002","SIP/6002-00000003","Dial","SIP/6002&SIP/6004,15","2014-08-26 12:11:45","","2014-08-26 12:12:00","15","0","NO ANSWER","DOCUMENTATION","","1409073105.4","",3
"""Alice"" <6001>","6001","6999","from-internal","SIP/6001-00000002","SIP/6004-00000004","Dial","SIP/6002&SIP/6004,15","2014-08-26 12:11:45","","2014-08-26 12:12:00","15","0","NO ANSWER","DOCUMENTATION","","1409073105.4","",6
"""Alice"" <6001>","6001","6999","from-internal","SIP/6001-00000002","","Hangup","","2014-08-26 12:12:00","","2014-08-26 12:12:00","0","0","NO ANSWER","DOCUMENTATION","","1409073105.4","",7
{noformat}

 * CDR written with {{unanswered=no}}
{noformat}
"""Alice"" <6001>","6001","6999","from-internal","SIP/6001-00000000","SIP/6002-00000001","Dial","SIP/6002&SIP/6004,15","2014-08-26 12:48:31","","2014-08-26 12:48:46","15","0","NO ANSWER","DOCUMENTATION","","1409075311.0","",0
"""Alice"" <6001>","6001","6999","from-internal","SIP/6001-00000000","SIP/6004-00000002","Dial","SIP/6002&SIP/6004,15","2014-08-26 12:48:31","","2014-08-26 12:48:46","15","0","NO ANSWER","DOCUMENTATION","","1409075311.0","",3
{noformat}

So, some CDR output is definitely getting filtered out with {{unanswered=no}}.

The documentation appears to conflict with itself. At least by the way I understand it:

In cdr.conf:
{noformat}
; Define whether or not to log unanswered calls. Setting this to "yes" will
; report every attempt to ring a phone in dialing attempts, when it was not
; answered. For example, if you try to dial 3 extensions, and this option is "yes",
; you will get 3 CDR's, one for each phone that was rung. Default is "no". Some
; find this information horribly useless. Others find it very valuable. Note, in "yes"
; mode, you will see one CDR, with one of the call targets on one side, and the originating
; channel on the other, and then one CDR for each channel attempted. This may seem
; redundant, but cannot be helped.
{noformat}

This makes me think any call as "NO ANSWER" will not be reported when the option is set to "no".

{noformat}
;
; In brief, this option controls the reporting of unanswered calls which only have an A 
; party. Calls which get offered to an outgoing line, but are unanswered, are still 
; logged, and that is the intended behaviour. (It also results in some B side CDRs being
; output, as they have the B side channel as their source channel, and no destination 
; channel.)
{noformat}

This makes me think only "NO ANSWER" calls with only an A party will not be reported with the option is set to "no".

That is, with unanswered=yes, the CDR record with only an A party is reported, and with unanswered=no it is not reported. That is what we see actually happening.

If SIP/A calls SIP/B, even if it is unanswered, there will be an A and B party on the CDR record. It looks like this option is intended to filter out calls between the phone and "non-endpoint" extensions, like the execution of Hangup via SIP/6001 in my test.

I'm thinking the name of the option is just ambiguous and the documentation could be reworded for clarity. I'll see if a developer can validate.

> 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)