similar to: Ring requested on channel already in use?

I'm running an E400P. Every now and then Asterisk stops receiving incoming calls. This turns up in the messages log: Nov 25 10:49:12 WARNING[65541]: File chan_zap.c, Line 5793 (pri_dchannel): Ring requested on channel 1 already in use on span 1. Hanging up owner. Nov 25 10:49:15 WARNING[81926]: File chan_zap.c, Line 5793 (pri_dchannel): Ring requested on channel 1 already in use on

Has there been any consideration of having asterisk save to a file the state of which agents are logged in such that after a restart (or crash) all agents don't have to manually re-login (after eventually realizing they're no longer logged in and not receiving calls :) ? ---------------------------------------------------------------------- Jon Lewis | I route Senior

I'm setting up a private enum zone to simplify/centralize dialplans for a number of Asterisk servers. In several dialed number situations, there are a handful of possible destinations for the call, and I'd like to have * try ENUMENTRY1, ENUMENTRY2, .., ENUMENTRYN just in case the first result is temporarily unable to handle the call. In at least some cases, I'd also like the order in

I'm getting exactly the same behavior as was posted about in http://lists.digium.com/pipermail/asterisk-users/2004-March/040380.html I've upgraded (both ends) to CVS stable (CVS-v1-0-06/17/05-13:15:49). Jun 17 13:46:17 NOTICE[15942]: chan_iax2.c:4053 authenticate: No way to send secret to peer 'a.b.c.d' (their methods: 4) Immediately after that, I'll see frames go by with

Hi all, I just posted this question before last week. Meanwhile after upgrading Asterisk 1.0.7-BRIstuffed-0.2.0-RCg to 1.0.8-BRIstuffed-0.2.0-RCh the same problem occurs, but seems to be more seldom. Attached is now the output of "zap show channel" . - I'm running a stable Asterisk on a HP DL380G2 1.4Ghz 0,5GB RAM equipped with 1x TE410P and 2xJunghanns OctoBRI running in NT-mode.

Hi all, I'm running a stable Asterisk on a HP DL380G2 1.4Ghz 0,5GB RAM equipped with 1x TE410P and 2xJunghanns QuadBRI running in NT-mode. Connected to the BRI-Ports are 12 Fax-Modems (Elsa MicroLink ISDN/TL V.34) which are only operating in dial out analog mode to deliver fax messages. After a while of running fine (50-200 dial out connections) on some S0 spans the following message occurs

On Fri, 7 May 1999 jlewis@lewis.org wrote: > # ldd ./ls > /lib/libNoVersion.so.1 => /lib/libNoVersion.so.1 (0x40014000) > libc.so.6 => /lib/libc.so.6 (0x4001c000) > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) > > I''ve never heard of libNoVersion. All the /home/ftp/bin stuff in 6.0 uses > it...but it doesn''t exist.

I receive this error on the asterisk console and it is pretty much ALWAYS coming up. Sometimes there will be a break where it does not display. We had our PRI provider test the lines and they claim that there is no signalling problem. It doesn't matter if there are no calls or if there are 10 calls in progress the error is still displayed. I also get an annoying popping or clicking sound

I have a serious problem that repeats very often, after 30 - 50 calls and I can only solve it by stopped and restarting * :-( After a while, * seems to loose track of something. When an ISDN call from PBX needs to go to the Telco, I get 'Ring requested on unconfigured channel 255/255 span 2' It's always channel 255/255 ??, the 'span' number is random Setup: * between Local

Hi all, as good? I am trying to go up a board TE110P with link E1 ISDN PRI to establish connection with a central office Siemens HiPath 4000. But I am having the following errors: Server1:~ # asterisk -r Asterisk 1.2.10, Copyright (C) 1999 - 2006 Digium, Inc. and others. Created by Mark Spencer <markster@digium.com> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'show warranty'

Hi, I still cant dial out on Zap and I really have no clue why. I'm using Asterisk Asterisk 1.2.6 and Zaptel 1.2.5 with Digium card 4 ports, 31 channels each and able to receive incoming calls and fax perfectly. I've done this in my dial plan. exten => 111,1,Answer() exten => 111,n,Ringing() exten => 111,n,Wait(2) exten => 111,n,AbsoluteTimeout(30) exten =>

I'm not sure if it's the same problem but your error message likely the same. after i additing pridialplan=local in the zapata.conf i'm able to make outboundcalls (located in germany) marcus -----Urspr?ngliche Nachricht----- Von: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] Gesendet: Dienstag, 11. April 2006 16:33 An:

Hi, I am getting this message on the * console on my first pri span. Pri show span show it is down, and I can't make any calls from the span. Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27

System have been working great for weeks, using an average 40 of 120 dahdi channels. But today, I suddenly see scary things like this: -- Moving call from channel 5 to channel 7 [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:10608 pri_fixup_principle: Can't fix up channel from 5 to 7 because 7 is already in use [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:11535 pri_dchannel: Ringing

Hi, For a significant time now (since about 0.2.0-rc8n) the qozap driver has become very verbose if an ISDN line is not connected... I get the messages below every couple of seconds in the asterisk logs. The "flaw" in the messages is the "Alarm cleared" message - The alarm cannot possibly be cleared because there is no physical media connected into that port!!! (BTW - All

Hello all, We have a situation where our 30 lines are maxing out, but no one is on a call. We are currently running CVS head downloaded on 15/8/2005 on a Dell Power Edge 2850. Our office mainly functions on a queue system. At the time this happened all our agents were logged in and no one was taking a call. Does anyone have a similar experience and ideas on how to fix this problem?

hello all, i'm using TE110P and all configuration prosess is done. but after i do the 'modprobe' for zaptel and wcte11xp, follow by ztcfg -vv and asterisk -vvvgc i have this error. *CLI> May 27 14:44:33 WARNING[3059]: chan_zap.c:8534 pri_dchannel: PRI Error: We think we're the network, but they think they're the network, too. May 27 14:44:34 WARNING[3059]: chan_zap.c:8534

What am I doing wrong here? Why is this happening? libpri is version 1.0.7-1 (debian package) asterisk is version 1.0.7.dfsg.1-2 (debian package) zaptel is version 1.0.9.2 -- Executing Dial("SIP/739-5935", "Zap/g1/0916000739") in new stack -- Called g1/0916000739 -- Channel 0/1, span 1 got hangup Oct 10 13:14:45 WARNING[7544]: app_dial.c:412 wait_for_answer:

Greetings to all, I am getting the following error on my PRI-connected Asterisk box, and am just wondering if anyone else has seen this, and if so how they solved it. Jan 18 10:10:23 NOTICE[6070]: chan_zap.c:7428 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Jan 18 10:10:24 NOTICE[6070]: chan_zap.c:7428 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary

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