[asterisk-bugs] [JIRA] (ASTERISK-25665) Duplicate logging in queue log for EXITEMPTY events

[Friendly Automation (JIRA)]

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

Friendly Automation commented on ASTERISK-25665:
------------------------------------------------

Change 14811 merged by Friendly Automation:
app_queue: Fix leave-empty not recording a call as abandoned

[https://gerrit.asterisk.org/c/asterisk/+/14811|https://gerrit.asterisk.org/c/asterisk/+/14811]

> Duplicate logging in queue log for EXITEMPTY events
> ---------------------------------------------------
>
>                 Key: ASTERISK-25665
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25665
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 1.8.32.3, 13.6.0
>            Reporter: Ove Aursand
>            Severity: Minor
>      Target Release: 13.16.0, 13.17.0, 14.5.0, 14.6.0, 15.0.0
>
>
> How to reproduce:
> Create a queue without members and place a call in the queue. The queue needs "leavewhenempty" set to yes.
> Generates something like this in the log:
> {noformat}
> 1452163740|1452163738.3|que0120550|NONE|ENTERQUEUE||+4721074800|1
> 1452163740|1452163738.3|que0120550|NONE|EXITEMPTY|1|1|0
> 1452163740|1452163738.3|que0120550|NONE|EXITEMPTY|1|1|0
> {noformat}
> ast_log for EXITEMPTY is called in queue_exec and also wait_our_turn. To me it looks like it's the same issue in the source code for 13.6.0 as well, but I haven't tested on that version.
> Removing the ast_log line in wait_our_turn fixed the issue for me.



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