Summary:	ASTERISK-11185: soft hangup is not working
Reporter:	Private Name (falves11)	Labels:
Date Opened:	2008-01-10 10:37:47.000-0600	Date Closed:	2008-04-02 17:02:43
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I have a shell script that requests a soft hangup for any calls that are longer than one hour, and Asterisk responds like below, but the calls actually never close. They keep accumulating. The problem is that the calls actually did clos, for I can see that the 'h' section of the dialplan executed in show channels concise, but if that is so why the calls show still in "core show channels concise". In the 'h' handler I execute a func_odbc funtion, and also I applied the patch so func_odbc would use direct_execute (issue  10723). Maybe these issues are related?? Requested Hangup on channel 'SIP/66.28.147.100-b51ef000' Requested Hangup on channel 'SIP/66.28.147.100-b4b922d0' Requested Hangup on channel 'SIP/66.28.147.100-b4f0d590' Requested Hangup on channel 'SIP/66.28.147.100-b4e83300' Requested Hangup on channel 'SIP/66.28.147.100-b5379840' Requested Hangup on channel 'SIP/66.28.147.100-b537dab0' Requested Hangup on channel 'SIP/66.28.147.100-b4f80650' Requested Hangup on channel 'SIP/66.28.147.100-b50f2350' Requested Hangup on channel 'SIP/66.28.147.100-b49b0710' Requested Hangup on channel 'SIP/66.28.147.100-b498e4c0' Requested Hangup on channel 'SIP/66.28.147.100-b4a6e9a0' Requested Hangup on channel 'SIP/66.28.147.100-b4e01d90' Requested Hangup on channel 'SIP/66.28.147.100-b4ba55f0' Requested Hangup on channel 'SIP/66.28.147.100-b4e7ea60' Requested Hangup on channel 'SIP/66.28.147.100-013792a0' Requested Hangup on channel 'SIP/66.28.147.100-01d6c7a0' Requested Hangup on channel 'SIP/66.28.147.100-b44f9ff0' Requested Hangup on channel 'SIP/66.28.147.100-b43a35c0' Requested Hangup on channel 'SIP/66.28.147.100-0121a610' Requested Hangup on channel 'SIP/66.28.147.100-00d6bb70' Requested Hangup on channel 'SIP/66.28.147.100-00b70e80' Requested Hangup on channel 'SIP/66.28.147.100-008d8f80'
Comments:	By: Joshua C. Colp (jcolp) 2008-01-14 15:47:43.000-0600 Please provide a sip history for call legs that exhibit this issue and a core show channel. By: Private Name (falves11) 2008-01-14 15:53:08.000-0600 Question: How do I capture a sip history to a file?? By: Joshua C. Colp (jcolp) 2008-01-14 15:55:55.000-0600 You can't capture sip history to a file. It gets stored in memory. By: jmls (jmls) 2008-02-17 12:52:30.000-0600 falves11, can you provide a sip history ? By: Private Name (falves11) 2008-02-17 13:00:00.000-0600 I cannot, since my Asterisk are always over 200 calls each and it would take my business down. It seems that some calls get stuck and it is impossible to close them with soft hangup, because they already went through the hangup process. Maybe we need a command to forcefully kill an active call, or maybe we need to make a better soft hangup. By: Tilghman Lesher (tilghman) 2008-02-18 16:19:32.000-0600 falves11:  then you need to decide which is the bigger problem for your business:  crashes over the long term or the short period of time that you'd need to devote to provide the requested debugging.  We cannot figure out a problem unless you're willing to provide the necessary information. By: Private Name (falves11) 2008-02-18 16:30:42.000-0600 I already provided the valgrind traces for another case, 0011940, where my asterisk crashes and nobody has made a comment yet. That is an important case, because all calls get dropped in a crash. I suggest that we wait a little to see if somebody can interprete those traces, and then we move on to this problem. This problem has not happenned lately, so maybe it is gone, or not. Please help me with the case 0011940 meanwhile. I already lost two hours of production when the valgrind-enabled asterisk went down and I had to get out of bed to bring it up. I am not the owner of this business, just the technology partner. I can not risk outages or I will soon looking for a job. By: Jason Parker (jparker) 2008-04-02 16:10:08 Issue ASTERISK-11391 has been closed.  Can you provide a sip history now? By: Private Name (falves11) 2008-04-02 17:01:31 Please close the case. The issue vanished. By: Jason Parker (jparker) 2008-04-02 17:02:25 Closed per reporter.