[asterisk-bugs] [JIRA] (ASTERISK-28060) Queue answered out of order

[Richard Mudgett (JIRA)]

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

Richard Mudgett edited comment on ASTERISK-28060 at 9/19/18 3:23 PM:
---------------------------------------------------------------------

Added note: here is my queue.log file (only a very basic relevant snippet)
{noformat}
1537375673|pbx3-1537375673.977560|test-hardcoded|NONE|ENTERQUEUE||705|1
1537375676|pbx3-1537375676.977563|test-hardcoded|NONE|ENTERQUEUE||200|1
1537375683|pbx3-1537375673.977560|test-hardcoded|SIP/AGENTA|RINGNOANSWER|10000
1537375693|pbx3-1537375676.977563|test-hardcoded|SIP/AGENTA|RINGNOANSWER|10000
1537375699|pbx3-1537375676.977563|test-hardcoded|NONE|ABANDON|1|1|23
1537375701|pbx3-1537375673.977560|test-hardcoded|NONE|ABANDON|1|1|28
{noformat}

What to look at: call pbx3-1537375676.977563 has a RINGNOANSWER to AGENTA, but it really shouldnt since its the second call coming in and the first call wasnt answered before.


was (Author: bluefox):
Added note: here is my queue.log file (only a very basic relevant snippet)
1537375673|pbx3-1537375673.977560|test-hardcoded|NONE|ENTERQUEUE||705|1
1537375676|pbx3-1537375676.977563|test-hardcoded|NONE|ENTERQUEUE||200|1
1537375683|pbx3-1537375673.977560|test-hardcoded|SIP/AGENTA|RINGNOANSWER|10000
1537375693|pbx3-1537375676.977563|test-hardcoded|SIP/AGENTA|RINGNOANSWER|10000
1537375699|pbx3-1537375676.977563|test-hardcoded|NONE|ABANDON|1|1|23
1537375701|pbx3-1537375673.977560|test-hardcoded|NONE|ABANDON|1|1|28

What to look at: call pbx3-1537375676.977563 has a RINGNOANSWER to AGENTA, but it really shouldnt since its the second call coming in and the first call wasnt answered before.

> Queue answered out of order
> ---------------------------
>
>                 Key: ASTERISK-28060
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28060
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 13.22.0
>         Environment: Centos7 kept updated
> Using certified-13.21-cert2 - but that wasnt in the dropdown of choices
>            Reporter: Michael Gaudette
>            Assignee: Unassigned
>            Severity: Minor
>
> not quite 100% reproducible, but happens often. might be a feature not a bug but I can't find any documentation on feature if it is one. If feature, please point out documentation on how to disable (or any info)
> The queue system seems to remember old calls, and takes this into account when deciding who to serve first.
> Way to reproduce*:
> Call a queue from phone A first - wait a few seconds
> Call same queue from Phone B
> While both calls are waiting, hangup phone A - phone B becomes "longuest waiting"
> Call back from phone A
> "queue-show" CLI command shows phone B as longuest waiting
> Have an agent answer queue call - phone A is served first, not phone B as would be expected
> *to reproduce, make sure to "clear" memory of older calls by first using both phones to make a queue call and answer them normally.



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