similar to: PRI deadlock problem is 1.2.1

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

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

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

We are currently using Asterisk 1.0.8 and noticing a rather odd problem that occurs roughly during the middle of the day sometimes. It seems that Asterisk and Bellsouth are getting out of sync somehow on the the status of the PRI channels. I get warnings messages like: Jul 18 10:50:24 WARNING[744]: chan_zap.c:7585 pri_dchannel: Ring requested on channel 0/1 already in use on span 1.

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

Today is the first time I've had any show stopping errors with asterisk since I started using it over 8 months ago... While I wait on the telco to check the circuit I thought I would post this here. Not sure yet but I thinks my 4-port PRI card is gone!!! I made a call and right when the person answered - BOOM. This is only a little better than it not working at all.

I am trying to test out my PRI configuration on a server by conection another asterisk server to it. I have the T-1 cards up and both set to bchan=1-23 and dchan=24 in zaptel.conf I am getting lost on the signalling in zapata.conf. using pri_cpe makes sense for my target box, but I am getting the following errors on my source box if I use pri_net or pri_cpe signalling. May 31 17:15:06

Hi, I got a problem with PRI that I'm not sure how to solve. Asterisk sits between PABX and PRI. PRI is span 1 and PABX is span 2. After every single call (no matter in what direction) I get "pri_fixup_principle: Call specified, but not found?" and "pri_dchannel: Hangup on bad channel" messages and the channel in question is restarted. As far as I can see, all

I am getting a TON of these errors on the console. I Googled and wikied and greped found the error in the source but cannot understand why it is happening. The system works fine, no dropped calls, no echo, it will even run for weeks with this error. But it just scrolls and scrolls on the console. Temporary fix was to turn off the console monitor! :-) Any ideas. Apr 16 10:40:12

Hi all, I have 1 Card Digium TE412P and 2PRI E1. I have more problems with drops lines. The asterisk log is this: May 16 10:52:26 NOTICE[4465]: chan_zap.c:8194 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 1 May 16 10:52:26 WARNING[4465]: chan_zap.c:2287 pri_find_dchan: No D-channels available! Using Primary channel 16 as D-channel anyway! May 16 10:52:26 NOTICE[4465]:

Just throwing out this question. integrating with Altiware server. PRI appears to be okay. It keeps trying to move my call to a different channel...usually channel 1. This is the deal here: Moving call from channel 23 to channel 1 Then the following errors after no audio then hanging up manually: Mar 24 17:46:17 WARNING[1315]: chan_zap.c:7792 pri_fixup_principle: Call specified, but not

I am trying to connect two machines to each other with an T1 crossover cable. The first machine has two TE120P cards - one connecting to the telco on an ISDN PRI. The second to a crossover T1 cable to a second machine which has one TE120P card. Telco <-cA-> Machine1 <-cB-> Machine2 Machine1: Two TE120P cards Machine2: One TE120P card cA: Standard T1 Cable cB: Crossover T1

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?

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

Hi guys, I've been trying to get my ISDN-10 line up for the past few days, but its been going up and down. I am using OpenVox D110P card on asterisk version 1.4.21. It seems to me like a cable problem. I tried using Ethernet straight cable (12, 45, 36, 78) and also a "straight" cable where the twisted pairs are on 12, 34, 56 and 78. The problem remains the same.

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'

I just started getting this error today (I've gotten this error befor) and its preventing me from having any incoming calls: chan_zap.c:7542 pri_dchannel: Ring requested on channel 0/2 already in use on span 1. Hanging up owner. PRI has been working fine. I didn't know anything was wrong until someone came and said their DID wasn't working. You call their DID, asterisk shows the

Hey, I wrote yesterday about PRI dropping, which turned out to just be a regular reset of unused B-channels. This time there's a real issue. As noted earlier I have an ISDN-30 connection, a Digium TE-121 with VPMADT032 echo cancellation. These are my configurations files: == /etc/zaptel.conf loadzone=dk defaultzone=dk span=1,1,0,css,hdb3,crc4 bchan=1-15 dchan=16 bchan=17-31 == ==

We've had a recurring issue on one of our servers where one or more zap channels from a PRI will get "stuck" causing incoming calls to fail. I happened to have a CLI session when it happened this morning. The start of the problem looked like: -- Channel 0/3, span 1 got hangup -- Channel 0/3, span 1 got hangup Jul 18 08:34:54 WARNING[20343]: chan_zap.c:7585 pri_dchannel: Ring

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.