|Summary:||ASTERISK-17967: Asterisk locks on transfer|
|Date Opened:||2011-06-06 06:59:52||Date Closed:||2012-09-05 08:20:05|
|Environment:||Debian Squeeze Linux version 2.6.32-5-686 (Debian 2.6.32-31) (email@example.com) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Mar 8 21:36:00 UTC 2011||Attachments:||( 0) lock-backtrace.txt|
( 1) transfer-lock.txt
|Description:||A calls B|
B tries to do attended transfer via dtmf sequence.
|Comments:||By: Gregory Hinton Nietsky (irroot) 2011-06-06 08:54:11.367-0500|
This is not a "deadlock" but there is a block happening in autoservice_stop
/* Wait while autoservice thread rebuilds its list. */
the lock is held in autoservice thread and it seems it cannot continue to rebuild list.
unlocking and locking the channle in the while loop will allow this to proceed.
By: jamhed (jamhed) 2011-06-06 09:59:22.186-0500
> unlocking and locking the channle in the while loop will allow this to proceed.
How can I do that? :)
By: Gregory Hinton Nietsky (irroot) 2011-06-06 12:10:10.484-0500
This is the best idea i have not sure its right.
By: Gregory Hinton Nietsky (irroot) 2011-09-17 05:41:43.938-0500
Dont use that patch it will introduce further problems.
By: Gregory Hinton Nietsky (irroot) 2011-09-17 06:29:41.967-0500
Spent more time and this issue is gone please try 1.8.7-rc1 for best results
the fix was added by commit 315447
r315446 | russell | 2011-04-26 12:40:23 -0500 (Tue, 26 Apr 2011) | 14 lines
chan_local: resolve a deadlock.
This patch resolves a fairly complex deadlock that can occur with the
combination of chan_local and a dialplan switch, such as dynamic realtime
extensions, which pulls autoservice into the picture when doing a dialplan
(closes issue #18818)
Reported by: nic
issue18818.patch uploaded by jthurman (license 614)
18818.v1.txt uploaded by russell (license 2)
Tested by: nic, jthurman, kterzi, steve-howes, sysreq, IshMalik
By: Matt Jordan (mjordan) 2012-09-05 08:20:05.742-0500
Closing out as a duplicate of ASTERISK-17414. If you find that you still have this problem in later versions of Asterisk 1.8, please contact a bug marshal in #asterisk-bugs and we will reopen this issue. Thanks!