Summary:ASTERISK-22074: AddQueueMember Causes AMI Disconnect
Reporter:JoshE (n8ideas)Labels:
Date Opened:2013-07-14 21:44:01Date Closed:2013-08-01 15:28:53
Versions:11.4.0 Frequency of
Description: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:

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.
Comments:By: Rusty Newton (rnewton) 2013-07-16 21:14:48.405-0500

I wasn't able to reproduce this using your example config in either 1.8 or 11.

You'll have to provide more detail on how you are reproducing this.

Please include a minimal, but complete configuration for the channel tech you are using to dial the extensions (sip.conf? iax.conf?), queues.conf and the complete manager.conf file and anything else you find necessary for reproduction.

You might as well go ahead and attach an Asterisk log with VERBOSE and DEBUG turned up to 5 and "manager set debug on" turned on to demonstrate your current reproductions.

By: Rusty Newton (rnewton) 2013-08-01 15:28:42.810-0500

Thank you for the bug report. However I am unable to reproduce this issue. We are now going to close this report - please feel free to reopen when you have more information at hand. You can contact a bug marshal on #asterisk-bugs (irc.freenode.net)