similar to: PRI dchannel in use?

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

Using CVS-HEAD libpri, CVS-HEAD zaptel, CVS-STABLE asterisk. Everything compiled fine. No problems loading chan_zap.so. Incomming calls to PRI work fine. Outbound is a different story: -- Executing Dial("SIP/64.72.107.4-4122fb40", "ZAP/R1d/18005551212|60") in new stack -- Called R1d/18005551212 -- Channel 0/23, span 1 got hangup Mar 13 13:19:29 WARNING[28835]:

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

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:

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 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 have problem using Asterisk.I have isdn-pri and openvox d110p card in my computer.They are connected with RJ-45 (1,2,4,5 pins to the card and all pins to the isdn done by telco workers). I got green led on isdn which is sign that isdn is working and that is connected to openvox, right ? I compiled newest versions of libpri zaptel and asterisk and had no problems during that. When I started

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

I've read as much as I can on this error and still can't seem to figure out what's causing this error: Jun 23 20:54:58 NOTICE[7483]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 23 20:55:03 NOTICE[7483]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 23 20:55:03 NOTICE[7483]:

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 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 everyone, I have a PRI conection on an * system running Asterisk 1.0.9, libpri 1.0.9 and zaptel 1.0.9.2 connected to an AXE 10 (APZ 21220 System 64) in the network side. I know the system and the wildcard I´m using are ok because I´ve used them before with other PRI connections (to a Siemens EWSD) without any problem. First the PRI didn´t work (I got the TE110P alarmed with red). After

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.

Hello all, I've got an intermittent issue with my asterisk set-up, and I'm pulling my hair out! Mostly everything works fine, but I get an error once every few days that sometimes (but not always) causes asterisk to stop accepting new calls and also stop responding to commands on the console (asterisk -r). The usual errors look something like this: [Feb 19 13:09:52] ERROR[18728]

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

I can't build it, errors: chan_zap.c:61: #error "You need newer libpri" chan_zap.c: In function `zt_call': chan_zap.c:1806: warning: implicit declaration of function `pri_sr_set_redirecting' chan_zap.c: In function `pri_dchannel': chan_zap.c:7776: structure has no member named `redirectingreason' chan_zap.c:7778: structure has no member named `redirectingreason'

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

I have been messing with Asterisk for months and got it working well with a SIP connection, but this is the first time I have set it up with TDM cards. The cards are configured, working and the T-1's (configured for PRI/DCHAN) and I can even call into it if I add the DNIS as an extension to default context. That is the oddity. I can find nowhere in the documentation that says anything about