similar to: Help - Lost All Calls

Hey all, I had a user complaining of calls which were dropping mid-conversation. I looked into the time of one of the calls, and saw the following: Apr 4 12:13:03 WARNING[6670] chan_zap.c: No D-channels available! Using Primary channel 28 as D-channel anyway! Apr 4 12:13:05 WARNING[6660] channel.c: Avoided initial deadlock for '0x82b8430', 10 retries! Apr 4 12:13:05 WARNING[6660]

We've experienced the same problem twice now in the past month. The asterisk pid stops responding. We aren't able to connect to the CLI and all calls are dropped. The lots are pretty bare as well. This is the message log: Oct 24 09:12:35 WARNING[20711] channel.c: Avoided initial deadlock for '0x8444a70', 10 retries! Oct 24 09:12:35 WARNING[20711] channel.c: Avoided initial

Hi What causes deadlock? Apr 5 14:02:43 WARNING[2413] channel.c: Avoided initial deadlock for '0x82acb10', 10 retries! Apr 5 14:02:43 WARNING[2413] channel.c: Avoided initial deadlock for '0x8298160', 10 retries! Here is the portion of the log: Apr 5 14:02:42 NOTICE[23363] chan_zap.c: Got event 18 (Ring Begin)... Apr 5 14:02:42 VERBOSE[23363] logger.c: -- Executing

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

Greetings, I've been having a large number of deadlock issues lately on chan_sip occurring only on VIA EPIA ML6000 boards. I'm curious if anyone else is having similar issues. My Config (have multiple systems all running the same hardware with the same problem) VIA EPIA ML6000 1GB RAM 80GB HDD Various Digium Cards (T1 and TDM cards) Trixbox 1.2.2 (though running stock asterisk code)

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

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',

Hi, We have integrated an Asterisk system (built from CVS HEAD) with an Avaya IP Office switch running Q.SIG on an E1 interface, using a Digium Wildcard TE110P. The system is being used for handling both inbound and outbound call traffic to a set of Asterisk agents who are connected via extensions on the IP Office - there is a maximum of 15 agents at any one time, allowing at least another

hi, i am recieving deadlocks frequently and its calls are getting hanged . Aug 11 13:13:53 WARNING[6367] channel.c: Avoided initial deadlock for '0xb6692258', 10 retries! Aug 11 13:13:54 WARNING[6367] channel.c: Avoided initial deadlock for '0xb6692258', 10 retries! Aug 11 13:13:54 WARNING[6367] channel.c: Avoided initial deadlock for '0xb78e5be8', 10 retries! Aug 11

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

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

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

Hello all, I'm running Asterisk 1.2.35 with chan_mgcp activated. The process host around 2,4K users. Along the day I've got some debug reports like : Feb 24 22:25:42 DEBUG[28546] channel.c: Avoiding deadlock for 'MGCP/aaln/1 at 028421223635-1' Feb 24 22:29:04 DEBUG[28670] channel.c: Avoiding initial deadlock for 'MGCP/aaln/1 at 028421223635-1' Then, at

I thought this problem with PRI and channels getting out of sync was fixed in the 1.2.x release of Asterisk. Here are the errors: Jan 5 13:59:05 WARNING[1253]: chan_zap.c:8360 pri_dchannel: Ring requested on channel 0/2 already in use on span 1. Hanging up owner. Jan 5 13:59:11 WARNING[1253]: chan_zap.c:8360 pri_dchannel: Ring requested on channel 0/2 already in use on span 1. Hanging up

Hi all, I am getting some warnnings in Asterisk's logs. I am not familiar with this error, could anyone please tell me what is this error, is it danger..? Jan 4 17:58:35 WARNING[30665] channel.c: Avoided initial deadlock for '0x9106ef8', 10 retries! Jan 4 17:58:40 WARNING[5478] channel.c: Avoided initial deadlock for '0x9106ef8', 10 retries! Jan 4 17:58:41 WARNING[30665]

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

Hi, Gere are some messages that sometimes show up in my Asterisk logs... If you help me out to solve them, I could make a list of all know warning messages so that we can publish in the wiki or somewhere else! - "res_features.c: Did not read data." - on Google, the only reference to this was in Russian :( - "Asked to transmit frame type 64, while native formats is 256 (read/write

Ok so it seg faults when I try to dial out through IAX(voiptalk.org), ofcourse it doesn't if I remove allow=speex :P ---- (gdb) run -c Starting program: /usr/sbin/asterisk -c [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 28283)] [New Thread 32769 (LWP 28285)] [New Thread 16386 (LWP 28286)] [Thread 16386 (LWP 28286) exited] [New Thread 32771 (LWP 28287)] Asterisk

Hi I have 3FXO trunks called ZAP-25,ZAP-26 and ZAP-28 and T1 Channnel bank I get this deadlock problem when 2 incoming call from FXO(Here ZAP-28 and then ZAP-26) wants to dial same channel (Here ZAP-1). In this senario ZAP-1 first answer ZAP-28 and thne ZAP-26 wants to call ZAP-1 but it time out and goto voicemail after that ZAP-1 try to reach ZAP-26 call by puting ZAP-28 on HOLD During

An Asterisk box at customer site shows these messages pretty regularly. This causes one way voice, the called party cannot hear the calling party. Apr 7 11:59:44 WARNING[18406] channel.c: Avoided initial deadlock for '0x817b790', 10 retries! Apr 7 14:47:46 WARNING[18406] channel.c: Avoided initial deadlock for '0x81a4380', 10 retries! Apr 7 14:58:53 WARNING[18406] channel.c: