Summary:	ASTERISK-20918: Asterisk fails to CANCEL all calls that it initiated via AGI
Reporter:	David Cunningham (dcunningham)	Labels:
Date Opened:	2013-01-10 23:19:26.000-0600	Date Closed:	2015-03-13 20:32:37
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/General
Versions:	1.8.11.1	Frequency of Occurrence	Frequent
Related Issues:
Environment:	CentOS release 6.3 (Final) Linux hostname 2.6.32-279.14.1.el6.x86_64 #1 SMP Tue Nov 6 23:43:09 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux	Attachments:	( 0) full.12.3.gz
Description:	When Asterisk does a Dial() to multiple destinations and one of those destinations answers, it only sends a CANCEL to some, but not all, of the other destinations. Attached is an Asterisk trace showing a call an AGI which implements a hunt group. On line 3804 it Dial()s the destinations, which launches a new AGI for each destination. Each destination AGI then dials the phone. You can see that phone 6326821 is sent an INVITE at line 10048. At line 46774 phone 6326838 answers the call. Then CANCELs are sent to many phones, but not to phone 6326821. Thanks.
Comments:	By: David Cunningham (dcunningham) 2013-01-10 23:19:46.564-0600 Trace attached. By: Freddi Hansen (freddi_fonet) 2013-01-17 05:10:04.226-0600 I have tried forking 10 calls via local channel to sip-phones and get the same. ( on 1.8.20 ) If I take a wireshark of all calls then I can see that the number of CANCEL's sent is ok but some of the calls get multiple CANCEL's while other don't get any. This setup has another sideeffect. If I answer one of the 10 phones dialed i parallel then it will be disconnected after 30 seconds in 10-20% of calls. I am not an "Asterisk locking wizard" that can solve this I just wanted to confirm that I se the same issue. By: Rusty Newton (rnewton) 2013-01-17 09:25:08.543-0600 Freddi, can you post your pcap and an Asterisk full log with it. Be sure DEBUG and VERBOSE messages are turned on (and set to level 5 or above) for your full log in logger.conf, plus "agi set debug on" and a "logger reload" before you reproduce the issue for the log. This will help a dev to confirm its the same issue and hopefully give them some additional clues. By: Freddi Hansen (freddi_fonet) 2013-01-18 04:56:06.891-0600 I will create this setup on a testserver with a simplified dialplan, hopefully within a day or two. By: David Cunningham (dcunningham) 2013-01-28 20:18:59.583-0600 Would there be any update on this please? By: Tilghman Lesher (tilghman) 2013-01-31 11:25:14.820-0600 Is it always the first channel in the huntgroup (first channel argument in the Dial) which fails to be cancelled correctly? By: Michael L. Young (elguero) 2013-01-31 13:34:19.013-0600 Is this the same setup as in ASTERISK-20902? By: Freddi Hansen (freddi_fonet) 2013-01-31 18:14:11.892-0600 I have my testserver working with a simplified dialplan on asterisk 1.8-r380696M but I can't get to fail now. I will try to get more functions from production servers copied over, maybe it's only when they are used. I keep trying to narrow what needed as minimum to get it to fail. One production server that fails is using 1.8-r378663M but I will try to upgrade and see if it changes anything. To answer Tilghman: it's random which channel(s) that aren't cancelled.   By: David Cunningham (dcunningham) 2013-02-04 19:47:20.382-0600 Michael, yes it is running the same code. I am not sure if it's the same problem. By: Matt Jordan (mjordan) 2013-02-18 22:23:20.535-0600 David: Did this problem get resolved when ASTERISK-20902 got resolved, or is it still an issue? By: David Cunningham (dcunningham) 2013-02-18 22:34:21.169-0600 The problem was not resolved by the fix in 20902. However upgrading to Asterisk 11 does seem to have solved it. By: Joshua C. Colp (jcolp) 2015-03-13 20:32:37.789-0500 Per reporter this was fixed in Asterisk 11.