Displaying 20 results from an estimated 10000 matches similar to: "HDLC Bad FCS / HDLC Abort solution"
2005 Jan 04
1
HDLC Bad FCS (8) HDLC Abort on TE410P
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
2005 Jul 04
1
HDLC bad FCS
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
2010 Jun 11
1
HDLC Bad FCS (8) on Primary D-channel
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
2006 Apr 25
1
PRI got event: HDLC Bad FCS (8) on Primary D-channel of span
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
2005 Aug 20
0
Re: Inter-Tel AXXESS failure: HDLC Bad FCS (8) on Primary D-channel of span 1
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
2004 Dec 18
0
PRI got event: HDLC Bad FCS
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
2004 Dec 22
1
PRI error (HDLC Bad FCS)
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,
2005 Aug 03
0
Inter-Tel AXXESS failure: HDLC Bad FCS (8) on Primary D-channel of span 1
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
2005 Aug 03
0
Inter-Tel AXXESS failure: HDLC Bad FCS (8) onPrimary D-channel of span 1
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
2010 May 31
1
Suddenly "HDLC Bad FCS (8)" errors on ISDN-PRI, changed nothing
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:
...
2007 Feb 14
1
CAS signalling on span 2 conflicts with HDLC with FCS check on channel 20
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
2011 Jun 01
10
busy hangup HDLC Bad FCS (8) on Primary D-channel
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
2005 Aug 26
0
CVS HEAD HDLC Abort on a TE405P PRI
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
2007 Sep 13
2
Fwd: Bad FCS error
---------- 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:
2007 Jan 09
0
Bad FCS & hangup
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
2005 Sep 26
1
Bad FCS nightmare to Nortel SL100 with TE410P
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
2005 Jun 29
4
PRI got event: HDLC Abort (6) on Primary D-channel of span 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
2005 Jun 23
1
HDLC abort 6 error
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]:
2011 Jan 24
1
B410P: DAHDI BRI PTMP HDLC Abort (6) on Primary D-channel of span 1 (TEI Errors)
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
2005 Feb 03
0
zttool user's manual & HDLC Abort errors
Hello all,
Does anyone know where I can get an explanation of how to use zttool?
I am running a PRI between to asterisk servers for testing and on one
end of the PRI (the pri_cpe side), I see
Tx/Rx Levels: 0/ 3
On all other PRIs, I see 0/0. Can anyone tell me what this means?
The real problem is that I get HDLC Abort errors every couple of
minutes on this PRI and I am trying to figure