Summary:	ASTERISK-05833: Attempting to place a call from a queue into a parking extension crashes asterisk (chan-sccp)
Reporter:	Steve Hanselman (shanselman)	Labels:
Date Opened:	2005-12-13 10:28:02.000-0600	Date Closed:	2011-06-07 14:00:45
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Platform: Asterisk latest SVN (SVN-trunk-r7457M) Lastest chan-sccp (1209) Not sure if this is a core asterisk issue or is related to the chansccp (this is the not asterisk one, but the one from berlios.de). ****** STEPS TO REPRODUCE ****** Caller enters queue. Agent answers call on an SCCP phone (7940, latest firmware). Agent transfers call to parking extension, hears announcement of parked extension, hits transfer to confirm and asterisk crashes. ****** ADDITIONAL INFORMATION ****** This is the bt: (gdb) bt #0  __pthread_mutex_trylock (mutex=0xcc) at mutex.c:64 #1  0x0806537a in ast_queue_hangup (chan=0x81e06f8) at include/asterisk/lock.h:589 #2  0x409af75e in sccp_channel_transfer (c=0x40a087fc) at sccp_channel.c:702 #3  0x409ba21e in sccp_sk_transfer (d=0x81a1f60, l=0x81a2b90, c=0x0) at sccp_softkeys.c:86 #4  0x409ad11d in sccp_handle_soft_key_event (s=0x813a0f8, r=0x0) at sccp_actions.c:1183 ASTERISK-1  0x409a54b0 in sccp_handle_message (r=0x81d6c80, s=0x813a0f8) at chan_sccp.c:578 ASTERISK-2  0x409bb66f in sccp_socket_thread (ignore=0x0) at sccp_socket.c:304 ASTERISK-3  0x4003cc3f in pthread_start_thread (arg=0x40a08be0) at manager.c:284 (gdb)
Comments:	By: Kevin P. Fleming (kpfleming) 2005-12-13 10:31:25.000-0600 We can't provide support for modules not in the main Asterisk distribution. This backtrace shows that the SCCP channel driver operations where running (apparently) in a thread where they did not belong. In the future, please use the 'version number' field for putting the version you are running, instead of putting it into the bug description. By: Steve Hanselman (shanselman) 2005-12-14 11:20:39.000-0600 (These notes are being added in case anybody else gets this issue, can you re-close this issue) The bug is reproducible and is down to having old modules in the asterisk modules directory, remove them, start asterisk, no issues.  Drop them back in, start asterisk and this is reproducible 100% of the time. ls -lt /usr/lib/asterisk/modules/ By: Jason Parker (jparker) 2005-12-14 12:04:26.000-0600 Re-closing, per posters request.