[asterisk-bugs] [JIRA] (ASTERISK-25203) AMI event QueueCallerLeave not always sent

[Rusty Newton (JIRA)]

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

Rusty Newton edited comment on ASTERISK-25203 at 7/14/15 8:03 PM:
------------------------------------------------------------------

Attached logs from reproduction in Asterisk GIT-13-1aafadf (from today).


was (Author: rnewton):
Attached logs from reproduction.

> AMI event QueueCallerLeave not always sent
> ------------------------------------------
>
>                 Key: ASTERISK-25203
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25203
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: SVN, 13.4.0
>            Reporter: Etienne Lessard
>            Severity: Minor
>         Attachments: ASTERISK-25203_full.txt, ASTERISK-25203-managerlog.txt
>
>
> The AMI Event QueueCallerLeave (generated by app_queue) is not sent when another channel calls the Bridge application with the queue caller's channel.
> For example, if I have the following dialplan:
> {noformat}
> exten = 301,1,NoOp()
> same  =   n,Queue(foo)
> same  =   n,Hangup()
> exten = 302,1,NoOp()
> same  =   n,Bridge(SIP/alice,x)
> same  =   n,Hangup()
> {noformat}
> When Alice (SIP/alice) calls the 301 extension
> And Bob calls the 302 extension
> Then Alice and Bob are bridged together
> But no QueueCallerLeave event was sent
> In asterisk 11, the QueueCallerLeave event was sent in this scenario, which was useful because if you were tracking QueueCallerJoin event, you could just track the QueueCallerLeave event to know "reliably" when a channel calling a queue left a queue (either because it was answered or not).



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