Posted: Sat Jul 16, 2005 12:03 am Post subject: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary, D
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 my kernel (also enabling my motherboard chipset in the kernel). After doing this I got 20x the Hard Drive write speed, no interrupts are shared, and the error is gone.
span=1,0,0,esf,b8zs
Message: 1
Date: Wed, 29 Jun 2005 07:13:29 -0600
From: "Michael Blood" <Michael@Matraex.com>
Subject: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary
D-channel of span 1
To: <asterisk-users@lists.digium.com>
Message-ID: <018a01c57cac$5a6959c0$0f00a8c0@cyprus>
Content-Type: text/plain; charset="us-ascii"
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 but that doesn't always
correspond with this error coming up so it is likely a separate issue.
I have loaded all modules by hand like below as someone suggested in a
search for HDLC errors on the list.
insmod zaptel
insmod wct1xxp
Jun 29 07:09:07 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got
event: HDLC Abort (6) on Primary D-channel of span 1
Jun 29 07:09:07 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got
event: HDLC Abort (6) on Primary D-channel of span 1
Jun 29 07:09:07 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got
event: HDLC Abort (6) on Primary D-channel of span 1
Posted: Sat Jul 16, 2005 1:04 pm Post subject: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary, D
Hey Kevin,
I managed to resolve this error after a week of pulling out my hair. Here is what I did to resolve the error and a link below for further assistance.
1 - If you are not using 2.6 kernel, upgrade.
2 - Check your span line in your zaptel.conf. You should be receiving timing, not giving it, when using a PRI (generally). Change the second number from 1 to 0. Save and restart asterisk. (span=1,0,0,esf,b8zs)
3 - I had a SATA RAID ARRAY setup (RAID 5) because I thought, hey, I can have redundency so that I don't loose voicemail if a drive crashes. Sadly if you run anything other than an IDE Drive you cannot use DMA and the Digium cards rely heavily on DMA. So I was forced to take out my RAID Controller and SATA drives and install a nice high end 120 Gig IDE Drive.
4 - In you BIOS disable any on board devices that you can (i.e. scsi controllers, usb controllers, serial controllers, etc...). If your BIOS supports/has an APIC(Advanced Processor Interrupt Controller) (which most modern motherboards do) go into your IRQ settings and set them all to the default AUTO type option. (you'll see why further below).
5 - In your 2.6 kernel enable these options:
PROCESSOR TYPE AND FEATURES --->
[*] Local APIC support on uniprocessors [*] IO-APIC support on uniprocessors
DEVICE DRIVERS --->
ATA/ATAPI/MFM/RLL support --->
[*] Generic PCI bus-master DMA support
[*] Use PCI DMA by default when available
<*> VIA82CXXX chipset support
----- I CHOSE THE VIA82CXXX CHIPSET SUPPORT FOR MY MOTHERBOARD, CHOSE THE APPROPRIATE ONE FOR YOUR MOTHERBOARD, THIS IS IMPORTANT IN USING DMA. THE APIC IS GOING TO ASSIGN IRQS AND PREVENT SHARING, ALSO FREES UP MORE THAN 16 IRQ LIMIT. SAVE THE CHANGES AND RECOMPILE YOUR KERNEL.
6 - run these commands to enable dma if it is not already on and enable irq unmask
linux# hdparm -d1 /dev/hda
/dev/hda:
setting using_dma to 1 (on)
using_dma = 1 (on)
linux# hdparm -u1 /dev/hda
/dev/hda:
setting unmaskirq to 1 (on)
unmaskirq = 1 (on)
* signifies the current active mode
YOU CAN SEE ABOVE THAT UDMA5 MODE IS ACTIVE BY THE * NEXT TO IT.
7 - you can run hdparm -tT /dev/hda to get some benchmarks on your drive, mine is running at:
/dev/hda:
Timing cached reads: 956 MB in 2.00 seconds = 477.59 MB/sec
Timing buffered disk reads: 126 MB in 3.03 seconds = 41.62 MB/sec
Which is literally 20 times faster than before I ran through these steps.
8 - Make absolutly positive that you are using the current most stable version of asterisk.
9 - Lastly, if you are running any services that you can put on another machine (i.e. TFTP, NTP) do so. Move them to another machine and try not to run any services but what is absolutely necessary and asterisk.
This should take care of you but if you need more try the link below. When all else fails, go to the digium supported hardware and change out your motherboard.
Message: 6
Date: Fri, 15 Jul 2005 20:13:48 -0400
From: "Kevin " <Asterisk@gtcus.com>
Subject: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary
D-channel of span 1
To: "'Asterisk Users Mailing List - Non-Commercial Discussion'"
<asterisk-users@lists.digium.com>
Message-ID: <036801c5899b$3e4877c0$2c02a8c0@gtcp4>
Content-Type: text/plain; charset="us-ascii"
I am getting an error in the log on the PRI span. The error is :
PRI got event: HDLC Abort (6) on Primary D-channel of span 1
I thought the problem was an interrupt conflict with the T110P card, so
I changed out the server to one that will dedicate the interrupt to the
T110P card. I still have the problem.
It's a dell 800 server with an SATA drive.
Can anyone offer and suggestions as any probable cause?
Posted: Wed Jul 20, 2005 9:21 pm Post subject: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary, D
Quote:
2 - Check your span line in your zaptel.conf. You should be receiving
timing, not giving it, when using a PRI (generally). Change the second
number from 1 to 0. Save and restart asterisk. (span=1,0,0,esf,b8zs)
I think you've got this cocked-up. A 0 in the second position tells zaptel to
internally-clock the circuit, and ingnore the clocking information from the
provider.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
