[asterisk-bugs] [JIRA] (ASTERISK-25399) app_queue: AgentComplete event has wrong reason

Kevin Harwell (JIRA) noreply at issues.asterisk.org
Tue Sep 29 16:42:35 CDT 2015


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

Kevin Harwell updated ASTERISK-25399:
-------------------------------------

    Target Release Version/s: 13.6.0

> app_queue: AgentComplete event has wrong reason
> -----------------------------------------------
>
>                 Key: ASTERISK-25399
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25399
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 13.5.0
>            Reporter: Kevin Harwell
>            Assignee: Kevin Harwell
>      Target Release: 13.6.0
>
>
> When a queued caller transfers an agent to another extension sometimes the raised AgentComplete event has a reason of "caller" and sometimes "transfer". Since a transfer has taken place this should always be transfer.
> Steps to reproduce (may take several times for it to happen):
> 1. alice gets queued and then bridged with member bob.
> 2. alice then does an attended transfer of bob to charlie.
> 3. observe the AgentComplete event's reason
> This occurs because sometimes the stasis hangup event arrives before the transfer event thus writing a different reason out.



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



More information about the asterisk-bugs mailing list