similar to: Avoided deadlock for '0x864e70', 10 retries!

Hi i have 20 people calling agents calling when ever they calling i get this below error May 30 00:46:57 WARNING[2840]: channel.c:785 channel_find_locked: Avoided deadlock for '0x8b2f50', 10 retries! and the voice go choppy, and voice breakages iam using Latest SVN, any suggestion to come over this problem ram -------------- next part -------------- An HTML attachment was scrubbed...

Hello! I clear remarks in Makefile: DEBUG_THREADS = -DDEBUG_THREADS -DDETECT_DEADLOCKS But same things in CLI: Aug 30 18:16:31 WARNING[22292]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x82f2fe0', 9 retries! -- Zap/32-1 is proceeding passing it to Zap/31-1 -- Zap/32-1 is ringing -- Accepting call from '2177' to '7141278' on channel

What are these? Nov 22 09:35:23 WARNING[7127]: channel.c:787 channel_find_locked: Avoided deadlock for '0xf6c06778', 10 retries! Nov 22 09:35:24 WARNING[7127]: channel.c:787 channel_find_locked: Avoided deadlock for '0xf6c06778', 10 retries! Nov 22 09:35:24 WARNING[7127]: channel.c:787 channel_find_locked: Avoided deadlock for '0xf6c06778', 10 retries! Nov 22 09:35:25

My Asterisk is Asterisk 1.2.30.2 currently running on viciserver the problem is : Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided deadlock for '0x861f6d8', 9 retries! Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided deadlock for '0x85a6420', 9 retries! Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided

Dear users, Couple of days ago I have updated my * to 1.2.4 with ZAP 1.2.3 Since the upgrade I am having these problems: Feb 7 16:21:18 WARNING[387] channel.c: Avoided deadlock for '0x91a8b20', 10 retries!$ Feb 7 16:23:16 WARNING[16176] channel.c: Avoided deadlock for '0x91a8b20', 10 retries!$ Feb 7 16:23:28 WARNING[16176] channel.c: Avoided deadlock for '0x91a8b20',

In asterisk 1.2 branch SVN 51363 zaptel svn 1980 libpri svn 393 addons svn 332 My equipment is a Via EPIA minit-itx CN10000 1.2ghz, 1gb ram and a tdm400p (4fxo). A call comes from zap, a SIP ulaw receives the call, talks for a while and when SIP users tries to park the call, then dozens of... WARNING[3853]: channel.c:781 channel_find_locked: Avoided initial deadlock for '0x91bb840', 10

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

I never so this error. I am using H323 with Asterisk 1.2.6 Any idea what can be the problem? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060401/2e8ad498/attachment.htm

I have thousands if this messages in the logs: Dec 4 10:53:43 NOTICE[26310]: app_queue.c:1980 wait_for_answer: No one is answering queue 'COMMERCIAL-WT' (2/0/0) Dec 4 10:53:43 WARNING[5602]: channel.c:889 channel_find_locked: Warning: Avoided contention wait for '0xb77482c8', 10 retries! RETURN = NULL Dec 4 10:53:43 WARNING[5602]: channel.c:889 channel_find_locked: Warning:

Hi All. I have many days reading and research about asterisk and vicidial. I thing this issue is about asterisk and doesnt about vicidial. Isn't it? I have a problem with theses application (I already ask for help in vicidial forums), but I can not fix it. I have debian 5 with asterisk 1.2.24 and vicidial 2.0.4. This server has a IAX tunnel with another asterisk server B which connect to

Hi! We have an Asterisk Bussines Edition ABE-A.1-6 on a PowerEdge 2850 with 4Gb RAM. It was working 24/7 without any for a month, but for not related causes I rebooted it a week ago. Yesterday the machine suddenly stop working, with a kernel panic. We was watching logs, and found in /var/log/asterisk just before the machine hung the messages posted avobe(is the first time we see it). Anyone

I am running 1.2.34 (also tried on 1.2.32) and whenever I launch an AGI, I get the "avoided deadlock" message below. *CLI> == Spawn extension (CONTEXT3, 6080, 8) exited non-zero on 'SIP/3211-1-081c40a8' -- Executing NoOp("SIP/3211-1-081c40a8", "") in new stack -- Executing AGI("SIP/3211-1-081c40a8", "diallocal.agi") in new

All out of the blue I get these errors? Any Ideas why Please help May 26 09:54:28 WARNING[3964]: channel.c:507 ast_channel_walk_locked: Avoided initial deadlock for 'SIP/301-b9d0', 10 retries! May 26 09:54:30 WARNING[3964]: channel.c:507 ast_channel_walk_locked: Avoided initial deadlock for 'SIP/301-b9d0', 10 retries! May 26 09:54:33 WARNING[3964]: channel.c:507

Running the current cvs head, I have a serious problem with a channel lock. It seems to be directly related to the queue sending calls to agents. The queue attempts to call the available agents, and it is in this process that the channels seem to get locked. Aug 2 18:02:14 WARNING[24985]: channel.c:709 channel_find_locked: Avoided initial deadlock for '0xb7b0a168', 10 retries! Aug

Hi, sometimes on by Asterisk 1.2.10 box I get these errors, there are about 50 active SIP channels so I dont know if calls are getting dropped or not. Should I be worried? 2006-10-18 09:33:59 WARNING[4375]: channel.c:787 channel_find_locked: Avoided deadlock for '0xb7341470', 10 retries! -- Executing GotoIf("SIP/sipCSC-b737f9e8", "0 ? 15") in new stack

Hi, sometimes on my Asterisk 1.2.10 box I get these errors, there are about 50 active SIP channels so I dont know if calls are getting dropped or not. Should I be worried? 2006-10-18 09:33:59 WARNING[4375]: channel.c:787 channel_find_locked: Avoided deadlock for '0xb7341470', 10 retries! -- Executing GotoIf("SIP/sipCSC-b737f9e8", "0 ? 15") in new stack

I have a major problem with SIP redirects, or maybe just do not understand how they are supposed to work. We are using Cisco 7940s and 7960s with SIP version 6.3. Asterisk 1.2.5. A call come in to extension 944 over the IAX trunk. Extension 944 has forward all to extension 904 set on the phone. According to the dialplan. extension 904 should ring for 90 seconds, then ring another extension, and

Anyone have any idea what's causing this or how to debug it? I'm pretty sure the root cause is with chan_sccp.so, but not sure how to prove it. I recently upgraded from CVS-head to 1.2.1 and the chan_sccp from 12-17-2005. Now, once or twice a week, I get this on the console: Jan 31 10:39:08 WARNING[10586]: channel.c:784 channel_find_locked: Avoided deadlock for '0xbf1013e0',

Hello! After upgrading my production machine to 1.2.1(used to be 1.2.0) on friday i experienced strange behaviour yesterday, i received deadlock-avoided-messages and channels refusing to hangup on span1(used for inbound calls), both messages in all cases paired: Jan 9 17:40:01 WARNING[30003] chan_zap.c: Ring requested on channel 0/17 already in use on span 1. Hanging up owner. Jan 9 17:40:01

Dec 1 12:08:43 WARNING[6189]: channel.c:495 ast_channel_walk_locked: Avoided deadlock for 'SIP/2502-6303', 10 retries! Dec 1 12:08:44 WARNING[6189]: channel.c:495 ast_channel_walk_locked: Avoided deadlock for 'SIP/2502-6303', 10 retries! Dec 1 12:08:44 WARNING[6189]: channel.c:495 ast_channel_walk_locked: Avoided deadlock for 'SIP/2502-6303', 10 retries! what does this