similar to: Channels being lost/disconnected using Q.SIG

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'

---------- Forwarded message ---------- From: Jan Prunk <janprunk at gmail.com> Date: Sep 13, 2007 3:35 PM Subject: Bad FCS error To: asterisk-users at lists.digium.com Hello ! I am getting the following error in asterisk logs: Sep 11 17:33:30 NOTICE[2187] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Sep 11 21:45:08 NOTICE[2187] chan_zap.c: PRI got event:

hello everyone, Last week I installed asterisk 1.2.24 with digium TE220B card. I have a problem with our PRI and Asterisk: the call be interrupted.It happens either PSTN-to-SIP or SIP-to-SIP,almost every call. After spending several days searching on internet, I found a lot of discussion about this issue and I have tried many, but it still.I am totally new to Asterisk environment and suspect I

I just upgraded my asterisk install from january 2005 CVS HEAD to current CVS HEAD : * zaptel * libpri * asterisk My asterisk have one TE405P with one span (the clock source) pluged into a telco PRI E1, a second span is a PRI E1 to another PBX and the third one is a T1 to a rhino channel bank. Everything went smoothly except that the two PRI span restart every ten seconds after some HDLC

Hi everyone, I have been having some problems lately with our PRI and Asterisk, or maybe it is just me. It happens once maybe twice a day, but when some of our customers are calling in, the phone just drops on them. I pulled the information below from the log from one that happened. I notice why it is happening, but I can't seem to figure out a way to stop it from happening. I also

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been seeing some strange issues recently as it relates to our Asterisk phone system. Let me give a little background on things: We have a T1 provided by Knology. We recently had an outage of Internet and phones. The following problems (except for the log messages) seemed to have cropped up after the outage. I was prompted by a friend of mine

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

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

Hello, All! It is a Piece of my log At the moment of a call: Jan 9 09:50:21 NOTICE[10902]: chan_zap.c:8194 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 3 -- Accepting call from '' to '0033444' on channel 1/1, span 1 -- Executing Dial("Zap/1-1", "SIP/3444|60|rgT") in new stack -- Called 3444 -- SIP/3444-0823e6b0 is

I'm running asterisk 1.0.3 and seeing occasional messages on the asterisk console that say: Dec 18 09:09:55 NOTICE[26411]: chan_zap.c:7381 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 or Dec 18 09:25:46 NOTICE[26411]: chan_zap.c:7381 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 They don't see to have a noticeable impact

Hi!, this issue makes me crazy. I read a lot of docs, also * mailling list and I try a lot of things without success. Any help will be appreciated. Here is the info: Hardware: -------------------------------------------- Supermicro Server with motherboard X7DB8, chipset Intel 5000P, Xeon 5050 Digium TE110P Software --------------------------------------------- Asterisk version 1.2.12.1

I hope someone can help me out with this issue. It has been dogging me for months and I can't seem to get it to go away. I have a Rhino Ceros box running Asterisk 1.4.21.2 connected via eth0 (nVidia MCP61 Ethernet) to a RedFone FoneBRIDGE2 dual-port with EC. The FB is the latest hardware rev and the latest firmware. I'm running the latest fonulator version and I'm running Zap-1.4.11

Hi friends, Where can I get some information to understand messages like the following ones? *NOTICE[6455] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1* *NOTICE[6455] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1* * ERROR[6455] chan_zap.c: !! Got S-frame while link down* *ERROR[6458] chan_zap.c: !! Got reject for frame 27, retransmitting

Can anyone help and point me in a useful direction. I'm using * 1.2.4 with Zaptel 1.2.4. I have a TE110P card and it's a Supermicro P8SCT mobo. If I run the PRI card in the PCI-X slot it shares an interupt with eth0 but I don't get problems. I've been trying to move it onto it's own IRQ, by moving the card to a regular PCI slot but I now get the errors Mar 2 08:43:09

Hi fellow asterisk users, I am running Asterisk 1.4.29 with an Digium TE121 card (wcte12xp kernel module) an approx. 100 snom320. The whole installation is running without issues since 5 months. Without having changed anything on the asterisk server for at least 2 months, i noticed "clicking sounds" at external calls over the PRI. Asterisk constantly throws the following messages: ...

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 Team I have installed the new DL580 and used the new TE420B to add capacity on our ivr. Before I put new E1?s I decided to first move the old e1 from the old system to this new one but it has errors which not only affect the audio quality, but also cause the asterisk to refuse any call after sometime even though the channels seems up and active {seems d-channel fails}.. When processing

fact I'm surprised that's changed (FreePBX's DAHDI module created the current config -- i.e. the one I posted in my original email). I'll change that back and see if that makes a difference, but I'm pretty sure I used the above configuration in a previous attempt with the same results. Also, I have indeed received the following messages prior to the interface going down and

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