similar to: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span

On Wed, Aug 03, 2005 at 11:28:19AM -0500, asterisk-users-request@lists.digium.com wrote: > 10. Inter-Tel AXXESS failure: HDLC Bad FCS (8) on Primary > D-channel of span 1 (Gavin Hamill) > Date: Wed, 3 Aug 2005 15:32:48 +0100 > From: Gavin Hamill <gdh@laterooms.com> > Subject: [Asterisk-Users] Inter-Tel AXXESS failure: HDLC Bad FCS (8) > on Primary D-channel of span

hello my friends, when i make a genzaptelconf i get this message ******************** CAS signalling on span 2 conflicts with HDLC with FCS check on channel ******************* Any idea Please? I m installing zaptel 1.4 i checked in "http://bugs.digium.com/view.php?id=7860" that it's a bug but beacause i m a newbie in asterisk i can't undrestand what exactly mean Thank You

Yep, another list posting on this topic :) All the messages I've read on this are from people experiencing these errors in quiet times - I get them as soon as I plug a port on our TE410P to an Inter-Tel AXXESS PBX.. and I get them continuously... I'm just sticking an * box in between ISDN30e (we're in the UK so euroisdn) and the PBX.. and whilst the telco ISDN30e side works like

Hello, I've got a running system in which logs are full of messages such as: [Jun 10 07:24:14] NOTICE[2414] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2 The strange thing is those messages are coming from a single span. My setup is : Asterisk 1.6.1.18 Junghanns OctoBRI with wcb4xxp driver libpri 1.4.10.2 dahdi 2.3.0 3 BRI lines in PtMP mode What does this

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 also experienced this problem and the first thing that really helped out was changing the timing in the span line of the zaptel.conf. Change it to look like this (see below) and see if it helps out. I got the error much less after doing this and eventually got rid of the error completely by removing my raid drives, installing an IDE drive, enabling DMA mode on the Hard Drive, enabling APCI in

I have 2 servers, configured identically. Each has a TE405P and 2 PRIs. One server was experiencing crackly audio on one circuit, accompanied by HDLC bad FCS messages. The telco recabled and moved me to another port on the DMS-100. The audio is better, but there are still bad FCS problems on the span. I have moved the PRI in question to the other server, and the problem does indeed move with the

On Wednesday 03 August 2005 17:33, Jens von B?low wrote: > Gavin, > > >> Any ideas/advice would be warmly received right now! > > You are not going to like my response... Erk :) > The only way I could get this to work (luckily I had 2 identical sites and > was busy with the upgrade to the gen2 card) was to downgrade to zaptel > 1.0.7. Alas no - just moved down to

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 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 all, After running fine for a few months now asterisk seems to hang frequently , still functioning but the DAHDI channels seem busy (users report a busy signal when calling or being called) A reboot will allow it to run for another day or maybe 2 or 3 till the problem occurs again. running stock Asterisk 1.6.2.9-2+squeeze2 on Debian with stock kernel 2.6.32-5-686 i get the following

Dear All, we have installed a TE410P card on a Dell Poweredge 1750 running a slackware 10 with 2.4.26 Kernel. Then we have made two loops on the card and we have configurated all the 120 channels. Our goals was to perform some stess tests even if in this scenario we used the same box as generator and target. The stress test comprised to generate up to 60 calls at the same time by placing a file

Hi all, So, we reverted the LibPRI version and tested it, and then tried with the latest version of everything. Still no changes. The BRI line is in PTMP. If we set the configs to PTMP in the genconf_parameters and try it, we get the following: [Jan 21 17:32:20] ERROR[20341]: chan_dahdi.c:12645 dahdi_pri_error: Unable to receive TEI from network! If we set it to PTP (which it is not) we

Dear All, I'm integrating avaya commuication manager difinity ver 1.0 with asterisk using B2B E1. following are the details of my H/W, zaptel configs and software installed. Digium TE110p asterisk 1.2.19 cent OS 4.4 zaptel 1.2.18 libpri 1.2.4 etc/zaptel.conf span=1,0,0,cas,hdb3 bchan=1-15,17-31 dchan=16 when i ztcfg -vvv im having this error message and the E1 is not getting up. "cas

Hi Related to this message: http://lists.digium.com/pipermail/asterisk-users/2005-February/090205.html After having a lot of trouble with abort and breakdown of the PRI connection I finally figured out what was wrong: The kernel was compiled for generic ide chipsets which doesn't support DMA. When our daily backup created some load for the disks the interrupts for the digium card

Hi, We currently have an Asterisk box (P4 2.4 Ghz, 512Mb RAM, 1 T100P, Zhone Channel Bank and 1 E100P) connected to an ISDN running without any problems. That machine is working for about 1 year. Two days ago, we decided to switch that machine for two PowerEdge 600SC (HA) and we got some problems. The running machine (P4 2.4Ghz) has an Intel motherboard with four 32-bit 3.3v PCI slots,

---------- 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:

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

Hi, After upgrading to DAHDI 2.4.0 from Zaptel, I noticed a lot of HDLC errors on my console: [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 These errors prevented calls from being made and received on my PRI spans. This seems

I have an * box connected to a Nortel SL100 through a PRI (US) using the Digium TE410P (quad-span T1 card). I don't have access to the SL100 - it is handled by another group. The span comes up OK (timing, framing fine). However, as soon as the D channel comes up, I get endless "HDLC Bad FCS" errors. I modified logger.conf to get rid of the messages (so I could see what else was