similar to: HDLC Bad FCS (8) on Primary D-channel

Hello, I get an Error every minute on the second card of two installed TE410P Cards in our System. The error is: PRI got event. HDLC Abort (6) on Primary D-channel of span 5(-8) PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 5(-8) Is it possible that there are known problems with 2 cards in one system? I'm running Asterisk/Libpri/zaptel from SVN branch-1.2-16008 I was

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

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

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

Hi, I'll soon replace a Junghanns OctoBRI with a Junghanns QuadBRI. As both use wcb4xxp driver (dahdi 2.3.0, libpri 1.4.10.2 and asterisk 1.6.1), I'm planning to proceed this way : 1. Edit 2 versions of files /etc/dahdi/system.conf and /etc/asterisk/dahdi-channels.conf (one for each card). 2. Link current system.conf and dahdi-channels.conf to QuadBRI files. 3. Power PC off 4. Swap cards

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

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, a few month ago, I tried to install zaptel for my Beronet BN8S0 pci card... I gave up and took hfcmulti/lcr. Now dahdi (2.2.1.1) seems to support the card and I'm very interested to get it to work. But how to get rid of these annoying qozap driver? bishop dahdi # lspci -v -nn -s 01:00.0 01:00.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-8S]

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

Hi, After an upgrade, I discovered yesterday strange things I would like to share here. Basically, I'me comparing platforms: The first one is a 2.6.26 (Debian Lenny) platform, with Asterisk 1.6.1.18, Libpri 1.4.10.2, Dahdi revision 8853 (must be between 2.3 and 2.5, I think). The second one is a 2.6.32 (Debian Squeeze) platform, with Asterisk 10.5.1, Libpri 1.4.12, Dahdi 2.6.1. Both are

Hello, In my system, dmesg outputs : [ 13.039788] wcb4xxp 0000:01:0a.0: probe called for b4xx... [ 13.039788] ACPI: PCI Interrupt 0000:01:0a.0[A] -> GSI 21 (level, low) -> IRQ 21 [ 13.039788] wcb4xxp 0000:01:0a.0: Identified HFC-8S Junghanns.NET octoBRI PCI (controller rev 1) at 0001dfe0, IRQ 21 [ 13.041202] wcb4xxp 0000:01:0a.0: NOTE: hardware echo cancellation has been disabled [

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

Hi, I'm using Asterisk 1.6.1.18 with latest Dahdi Linux and Tools (rev 8854) and libpri 1.4.10.2. During installation, I'm facing this : # dahdi_genconf -v system Default parameters from /etc/dahdi/genconf_parameters Empty configuration -- no spans Of course, I've got span descriptions in /etc/dahdi/genconf_parameters : .... pri_termtype SPAN/1 TE SPAN/2

Hi, Does anyone have any good empirical data suggesting what the maximum number of PRI calls (incoming and outgoing) without hardware echo cancellation can be handled on a single box is? I have a TE410P T1 (1st gen) card and I'm seeing interesting errors of D-Channels going down and then coming back up (See below). I've looked at the number of simultaneous calls at each of these points,

Hi, In my 1.6.1.18 with dahdi 2.2.1.1, I've got : # dahdi_hardware pci:0000:01:0a.0 qozap- 1397:16b8 Junghanns OctoBRI ISDN card Does it mean I should download and use qozap or is it a bug in Dahdi ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100412/de87e46e/attachment.htm

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

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