Summary:	ASTERISK-13578: Pickup from features
Reporter:	adria vidal (adriavidal)	Labels:
Date Opened:	2009-02-13 06:08:35.000-0600	Date Closed:	2009-04-13 13:36:58
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Resources/res_features
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Have just updated our Asterisk 1.4.6 to Asterisk 1.4.23.1 and in every attempt to use the feature for pickup make a crash on the Asterisk. Builtin Feature           Default Current ---------------           ------- ------- Pickup                    *8      * If i use the pickup app everything is OK _*[23]XX' =>     1, Pickup(${EXTEN:1})     ****** ADDITIONAL INFORMATION ******    -- Executing [226@desde-usuarios:1] Dial("SIP/212-0826d050", "SIP/226|600|wtWT") in new stack    -- Called 226    -- SIP/226-0826e968 is ringing [Feb 13 12:24:46] NOTICE[3252]: chan_sip.c:14588 handle_request_invite: Nothing to pick up for omlxqcaenrlbjhd@192.168.1.54 [Feb 13 12:24:46] WARNING[3252]: channel.c:1513 ast_hangup: Hard hangup called by thread -1216156752 on SIP/212-0824cf48, while fd is blocked by thread -1244337232 in procedure ast_waitfor_nandfds!  Expect a failure [Feb 13 12:24:46] WARNING[3562]: channel.c:2071 __ast_read: read() failed: Bad file descriptor
Comments:	By: Leif Madsen (lmadsen) 2009-02-13 07:59:22.000-0600 Thank you for your bug report. In order to move your issue forward, we require a backtrace from the core file produced after the crash. Please see the doc/backtrace.txt file in your Asterisk source directory. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then 'make install' after enabling, reproduce the crash, and then execute the instructions in doc/backtrace.txt. When complete, attach that file to this issue report. Thanks! By: Mark Michelson (mmichelson) 2009-02-13 08:59:38.000-0600 I don't want to contradict blitzrage, but I have a feeling that the backtrace that we'd get from this crash would be in the wrong thread, and that by the time the crash occurs, the offending thread would be in a state where a backtrace is not useful. In this particular case, I would recommend describing the situation as accurately as you can, detailing the call flows, uploading relevant dialplan portions, and uploading a *full* console trace. By: Leif Madsen (lmadsen) 2009-02-13 13:12:29.000-0600 No worries putnopvut. It just looked like a crash was occurring, but it appears you have an idea that the backtrace wouldn't be useful. Thanks for catching this so the reporter doesn't waste any time getting us useful information. Thanks! By: adria vidal (adriavidal) 2009-02-16 10:02:53.000-0600 I will have to wait 2 weeks to find time to make the test, the PBX is in production, so i can't make the crash reproduction right now. thanks By: Mark Michelson (mmichelson) 2009-02-16 10:18:16.000-0600 You don't necessarily have to reproduce the crash. In this particular case, I think it would be much better if a developer could reproduce the crash instead. In order to do this, though, we need to know what to do to make the crash occur. We know it involves call pickup, but we don't know what other circumstances are necessary to make the crash occur. That's why it would be a good idea for you to describe, from a high level, what is going on when you have the crash happen. Providing a dialplan which exhibits the behavior would be helpful, too. By: Giorgio Incantalupo (gincantalupo) 2009-02-25 04:52:40.000-0600 I'm using Asterisk 1.4.23 and the pickup feature is not working, even if my Asterisk does not crash. If A calls B and C picks up, A keeps hearing the ringing tone which stops when C hangs up, even if C couldn't catch the call. CLI doesn't show anything unusual but I can post an excerpt if can help. By: Francesco Romano (francesco_r) 2009-02-25 07:34:49.000-0600 I reported the same bug some times ago, but was resolved after the release of 1.4.23. See ASTERISK-13333. So i advice you to upgrade to the latest 1.4SVN and try again. By: Mark Michelson (mmichelson) 2009-03-01 16:20:38.000-0600 As francesco_r has pointed out, call pickup not working properly was a known issue which has been fixed. However, the crash being reported here is one that we had not heard about previously. Unfortunately, there have been no new details posted despite my requests for them. It is clear from tests that I have run that there is some specific scenario that is required for the call pickup to cause a crash. However, the reporter has not told any details regarding how to make the crash occur except that call pickup is involved. Until more details are offered by the reporter, it is nearly impossible to try to get this fixed. By: adria vidal (adriavidal) 2009-03-01 17:23:07.000-0600 sorry for the delay, the PBX is a production system, and have been imposible to deploy the buggy version to try the crash again. Hope in about 3 weeks to have a cut into the system and then test the crash again. By: Mark Michelson (mmichelson) 2009-03-01 17:30:40.000-0600 adriavidal: Please see what I wrote in ~100182. I really don't need for you to reproduce the problem. It may be enough to provide what I asked for in that note. By: Leif Madsen (lmadsen) 2009-03-02 09:57:43.000-0600 adriavidal: please follow up with mmichelson, or else we'll have to close this issue as suspended until you can provide the appropriate details. Thanks! By: Leif Madsen (lmadsen) 2009-04-13 13:36:58 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.