similar to: Deadlock of asterisk on app_system

Hello, Has anybody seen that Audiocodes gateway is replying with "486 Busy here" when it's actually not (last call ended ~15 seconds ago). I see this quite often. From other logs i see that previous call ends at 11:13:01, then app_queue tries to dial at 11:13:14 and fails numerous times, before succeeding at 11:14:02 I have attached sample SIP debug log: Any ideas what i could

I am using the AMI to dispatch (2) calls to Local/my_priority at my_context where: [my_context] exten => my_priority,1,Answer() exten => my_priority,n,Dial(${LOCAL_DIAL}) and LOCAL_DIAL has the actual phone number to dial. The first call goes through just fine and I see DAHDI/1/XXXX being called. The second call I see DAHDI/2/XXXX and a message about everyone is busy on congested. I

When I load the asterisk 1.4 gui and log into "/asterisk/static/config/setup/install.html", it tells me "No Analog ports has been detected on your system". I have 2 Wildcard X100P cards that are properly installed. Ztcfg shows no problems. I also get the following message from the asterisk console " app_system.c:105 system_exec_helper: Unable to execute

Dear All, i have following CLI error while try to run this command from Dialplan *TrySystem("DAHDI/45-1", "asterisk -rx "dialplan add extension 1234111,1,Goto(incomingdundi,s,1) into dundilookup"") in new stack WARNING[32626]: app_system.c:81 system_exec_helper: Unable to execute 'asterisk -rx "dialplan add extension 1234111,1,Goto(incomingdundi,s,1) into

I am building a new Asterisk server here at the office, and I'm wondering if there are any downsides to creating my dialplan with AEL. It seems more intuitive (to me), but I'm not sure if there are any pitfalls I need to be aware of first. We use this for internal extensions, 8 pots lines, and our answering service which gets about 500 incoming calls a day down our T1. Also, one more