Re: [asterisk-users] Help! channel_find_deadlocked: Avoided initial deadlock for ...
FYI, check the changelog for 1.2.14 to 1.2.25 - IIRC, there are a significant number of deadlock-fixing updates. There is at least one related to the code where that error message is displayed. Regards, Steve On 1/9/08, Douglas Garstang [EMAIL PROTECTED] wrote: Replying to myself. :) I just noticed the deadlock message still displayed on the console at the end of a normal call, so the the deadlock message is not related to the early CANCEL - Original Message From: Douglas Garstang [EMAIL PROTECTED] To: asterisk-users@lists.digium.com Sent: Tuesday, January 8, 2008 5:31:12 PM Subject: [asterisk-users] Help! channel_find_deadlocked: Avoided initial deadlock for ... Hope someone can help. I have a situation where asterisk is sending a SIP CANCEL message before the Dial() timeout has hit. It doesn't always do it. Normally, we send an INVITE to the ITSP. They respond with a 100 Trying, then a 180 Ringing, or 183 Session Progress. It seems to be at this point that Asterisk starts the dial timer. Normally, when no more replies have been received by the dial timeout, Asterisk sends a CANCEL message. That's all fine, and when this happens, this is what appears on the console: -- Called [EMAIL PROTECTED] -- SIP/teleglobe-09879188 is making progress passing it to SIP/teleglobe-09876568 -- Nobody picked up in 4 ms -- Executing PlayTones(SIP/teleglobe-09876568, congestion) in new stack However, when asterisk sends the CANCEL earlier then this, this is what appears on the console: -- SIP/teleglobe-09879188 is making progress passing it to SIP/teleglobe-09876568 == Spawn extension (default, callback, 7) exited non-zero on 'SIP/teleglobe-09876568' Jan 9 01:16:34 WARNING[5719]: channel.c:781 channel_find_locked: Avoided initial deadlock for '0x97f24d8', 10 retries! Does anyone know what the deadlock message is all about? It is ocurring quite frequently. This is Asterisk 1.2.14. Thanks, Doug ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Help! channel_find_deadlocked: Avoided initial deadlock for ...
Replying to myself. :) I just noticed the deadlock message still displayed on the console at the end of a normal call, so the the deadlock message is not related to the early CANCEL - Original Message From: Douglas Garstang [EMAIL PROTECTED] To: asterisk-users@lists.digium.com Sent: Tuesday, January 8, 2008 5:31:12 PM Subject: [asterisk-users] Help! channel_find_deadlocked: Avoided initial deadlock for ... Hope someone can help. I have a situation where asterisk is sending a SIP CANCEL message before the Dial() timeout has hit. It doesn't always do it. Normally, we send an INVITE to the ITSP. They respond with a 100 Trying, then a 180 Ringing, or 183 Session Progress. It seems to be at this point that Asterisk starts the dial timer. Normally, when no more replies have been received by the dial timeout, Asterisk sends a CANCEL message. That's all fine, and when this happens, this is what appears on the console: -- Called [EMAIL PROTECTED] -- SIP/teleglobe-09879188 is making progress passing it to SIP/teleglobe-09876568 -- Nobody picked up in 4 ms -- Executing PlayTones(SIP/teleglobe-09876568, congestion) in new stack However, when asterisk sends the CANCEL earlier then this, this is what appears on the console: -- SIP/teleglobe-09879188 is making progress passing it to SIP/teleglobe-09876568 == Spawn extension (default, callback, 7) exited non-zero on 'SIP/teleglobe-09876568' Jan 9 01:16:34 WARNING[5719]: channel.c:781 channel_find_locked: Avoided initial deadlock for '0x97f24d8', 10 retries! Does anyone know what the deadlock message is all about? It is ocurring quite frequently. This is Asterisk 1.2.14. Thanks, Doug Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Help! channel_find_deadlocked: Avoided initial deadlock for ...
Hope someone can help. I have a situation where asterisk is sending a SIP CANCEL message before the Dial() timeout has hit. It doesn't always do it. Normally, we send an INVITE to the ITSP. They respond with a 100 Trying, then a 180 Ringing, or 183 Session Progress. It seems to be at this point that Asterisk starts the dial timer. Normally, when no more replies have been received by the dial timeout, Asterisk sends a CANCEL message. That's all fine, and when this happens, this is what appears on the console: -- Called [EMAIL PROTECTED] -- SIP/teleglobe-09879188 is making progress passing it to SIP/teleglobe-09876568 -- Nobody picked up in 4 ms -- Executing PlayTones(SIP/teleglobe-09876568, congestion) in new stack However, when asterisk sends the CANCEL earlier then this, this is what appears on the console: -- SIP/teleglobe-09879188 is making progress passing it to SIP/teleglobe-09876568 == Spawn extension (default, callback, 7) exited non-zero on 'SIP/teleglobe-09876568' Jan 9 01:16:34 WARNING[5719]: channel.c:781 channel_find_locked: Avoided initial deadlock for '0x97f24d8', 10 retries! Does anyone know what the deadlock message is all about? It is ocurring quite frequently. This is Asterisk 1.2.14. Thanks, Doug Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
