HDLC Abort errors are usually caused lost or corrupted data from the T-1.
If you configured the span as PRI in Asterisk and it's not a PRI, I can
imagine you might get this message.
Also, if there is a problem with the line itself, I can imagine you
might get this message.
However, in my experience, HDLC Abort errors are usually caused by some
device in your system locking interrupts for a long time -- long enough
to miss a few bits in the stream coming from the card to the PCI bus.
Some devices that commonly do this are SATA controllers, IDE
controllers, RAID, Gig Ethernet, Video cards. There is very little you
can do about it, other than disable the offending device. Of course, not
all brands/makes/models of the above device types cause problems, only
some of them do, but I don't know of any "problem list".
Anthony Rodgers wrote:
Looks like a timing problem - zaptel.conf and zapata.conf, please.....
A.
On Apr 25, 2006, at 3:05 AM, Nico Giefing wrote:
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 running Debian Stable with Kernel 2.4.25
Since Yesterday i'm running Kernel 2.6.8
The Interrupte of the cards are: 16 and 28
Do anybody have any idea how i can solve this Problem?
--
Now accepting new clients in Birmingham, Atlanta, Huntsville,
Chattanooga, and Montgomery.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
