Summary:	ASTERISK-26182: A second call into inbound queue causes all calls that came in via the queue to go silent.
Reporter:	Phil Carlson (SlnPhil)	Labels:
Date Opened:	2016-07-07 14:49:48	Date Closed:	2016-07-07 17:37:42
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Applications/app_queue
Versions:	11.22.0	Frequency of Occurrence	Constant
Related Issues:	duplicates ASTERISK-25888 Frequent segfaults in function can_ring_entry() of app_queue.c
Environment:	CentOS release 6.8 (Final), FreePBX, Sangoma AFT-200	Attachments:
Description:	Calls were going silent for no apparent reason. Investigation found a scenario that consistently caused calls to go silent: 1) A remote engineer placed a direct call from a remote asterisk server to the main facility and server over an IAX trunk by direct dialing an extension. 2) The remote engineer placed a call directly to the queue on the main server using an asterisk extension for that purpose. Asterisk routed to the main inbound queue ringing all phones registered in the queue. 3) The main site engineer answered the phone and left the call active. 4) The remote engineer placed a second call to the queue. 5) The phones did not ring. The 2 connected calls both went silent, but did not disconnect and continued to be reported by FreePBX as active calls. 6) The remote engineer then dialed in again (about 5-10 seconds later) on the IAX trunk and was able to connect. 7) We repeated this scenario multiple times with the same results, so it was very repeatable. 8) In one instance we started the asterisk console and turned sip debug on and captured all activity. When the final call was placed the asterisk console aborted and returned us to the linux command prompt. Calls to the main number routed into the queue behaved the same way. Calling directly to the queue (as above) appeared to identify the queue as the source of the problem. So we reconfigured asterisk to use a ring group rather than the queue for the main inbound number and repeated the scenario without problems. That is, multiple inbound calls could be answered and continued to maintain sound. In earlier normal business situations, we have seen similar behavior, but less precisely defined, which prompted this investigation. In one recent situation an engineer called in as a test upon seeing multiple active lines and all active calls went silent. At that time, one call had already been routed from the inbound queue and two other calls had just been answered when the test call was placed. Both calls appeared to come in through the main queue, but this is not confirmed and it is unclear why the second call was able to come in initially. After that, calls were re-established and a few minutes later another call went silent, but one outgoing call remained active and did not go silent.
Comments:	By: Asterisk Team (asteriskteam) 2016-07-07 14:49:49.446-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Phil Carlson (SlnPhil) 2016-07-07 17:26:00.553-0500 I realized asterisk had crashed and found the core file. Attached is the backtrace. Also attached is the capture of the asterisk console with sip debug on from an earlier instance of the same steps. I have multiple other core files including one from the earlier real-world activity. Let me know if you want other backtraces. By: Joshua C. Colp (jcolp) 2016-07-07 17:37:42.251-0500 This has been fixed already and will be released in 11.23.0.