[asterisk-bugs] [JIRA] (ASTERISK-29199) app_queue: Calls not connected

EDV O-TON (JIRA) noreply at issues.asterisk.org
Wed Dec 9 05:11:16 CST 2020


     [ https://issues.asterisk.org/jira/browse/ASTERISK-29199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

EDV O-TON updated ASTERISK-29199:
---------------------------------

    Attachment: debuglog.txt

Here is the debug log of the whole scenario:

- phone 744 calls phone 742 to get a busy state
- phone 741 calls queue 666
- agent 742 is paused in the queue 666
- phone 742 ends the call
- phone 744 calls queue 667
- the bug effect
- phone 741 ends call
- phone 742 gets the queue 667 call
- phone 742 ends call

> app_queue: Calls not connected
> ------------------------------
>
>                 Key: ASTERISK-29199
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29199
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 16.15.0, 18.1.0
>         Environment: Ubuntu 20.04, Ubuntu 18.04 both with latest patches
>            Reporter: EDV O-TON
>            Assignee: EDV O-TON
>            Severity: Minor
>         Attachments: debuglog.txt
>
>
> Agent has two queues A and B
> Queue A has a higher weight ( e.g. 66) than queue B (e.g. 65).
> The queue A gets a call while the agent is on call. The agent is manually paused in Queue A but not in Queue B. After the agent hangup his active call another call for queue B gets in. This one isn't transferred to the agent until the call in queue A is connected to another agent or the caller quits.
> A test with weights vice versa worked as expected and the call ist immediately connected to the agent



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



More information about the asterisk-bugs mailing list