[asterisk-bugs] [JIRA] (ASTERISK-22074) AddQueueMember Causes AMI Disconnect
JoshE (JIRA)
noreply at issues.asterisk.org
Sun Jul 14 21:44:03 CDT 2013
JoshE created ASTERISK-22074:
--------------------------------
Summary: 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: Blocker
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
More information about the asterisk-bugs
mailing list