[asterisk-bugs] [JIRA] (ASTERISK-22074) AddQueueMember Causes AMI Disconnect

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-22074:
-----------------------------------

    Severity: Critical  (was: Blocker)
    
> AddQueueMember Causes AMI Disconnect
> ------------------------------------
>
>                 Key: ASTERISK-22074
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22074
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 11.4.0
>            Reporter: JoshE
>            Severity: Critical
>
> Very simple dialplan:
> exten => *30,1,NoOp(Logging Into Queue)
> same => n,AddQueueMember(sales)
> same => n,Playback(goodbye)
> same => n,Hangup
> exten => *34,1,NoOp(Logging Out Of Queue)
> same => n,RemoveQueueMember(sales)
> same => n,Playback(goodbye)
> same => n,Hangup
> With this manager connected via a REMOTE TCP connection:
> [manager]
> secret=1234
> permit=0.0.0.0/0.0.0.0
> read = all
> When running *30 and *34 to trigger login / logout of queue, the AMI connection will be dropped.  This initially looked to be 100% reproducible for the AddQueueMember event.  After a few tests and Asterisk version changes on 11 branch, it now looks like it happens about 50% of the time on both events.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira