Asterisk Guru

AsteriskGuru Archives
Mailing List Archives

FAQ

Memberlist

Usergroups

Profile

[Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-

AsteriskGuru Archives Forum Index -> Asterisk-Users

View previous topic :: View next topic

Author

Message

Asterisk at gtcus.com (Ke
Guest

Posted: Fri Jul 15, 2005 4:12 pm Post subject: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-

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

adam at emplifyhr.com (Ad
Guest

Posted: Fri Jul 15, 2005 8:37 pm Post subject: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-

try removing asterisk modules you are not using, and non-asterisk
services running on the machine, especially ones with high disk or
network usage.

Kevin wrote:

Quote:

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?

Thanks

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

pabelanger at codeslinger
Guest

Posted: Wed Jul 20, 2005 7:01 pm Post subject: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-

Evening all, Just got my first PRI got event: HDLC Abort (6) on Primary D-channel of span 1 error message. Our production box has been up for ~2 month. We are Asterisk 1.0.9 with Slackware 10.1. Now I have search the lists from this message and hear all the problem. Everything from asterisk and IRQ's to telco issue. I hear to night, to say.. I'm pretty sure mine is a telco issue. Reason I think this, check out how soon after my HDLC Abort (6) error I get Red Alarms. Right away. Most of the other issue, HDLC Abort (6) repeats many times. Jul 20 18:27:50 NOTICE[2650]: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 1: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 1 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 2: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 2 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 3: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 3 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 4: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 4 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 5: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 5 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 6: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 6 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 7: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 7 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 8: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 8 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 9: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 9 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 10: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 10 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 11: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 11 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 12: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 12 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 13: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 13 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 14: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 14 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 15: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 15 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 16: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 16 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 17: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 17 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 18: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 18 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 19: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 19 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 20: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 20 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 21: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 21 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 22: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 22 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 23: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 23 Jul 20 18:27:50 NOTICE[2650]: PRI got event: Alarm (4) on Primary D-channel of span 1 Jul 20 18:27:50 WARNING[2650]: No D-channels available! Using Primary on channel anyway 24! Jul 20 18:27:59 WARNING[2650]: No D-channels available! Using Primary on channel anyway 24! But just to me safe, please check out my /procs and let me know if you see anything. Once again, I strongly believe this is a telco issue not Asterisk. [pabelanger@pts/0] # cat /proc/interrupts CPU0 0: 90839 XT-PIC timer 1: 2 XT-PIC keyboard 2: 0 XT-PIC cascade 10: 898130 XT-PIC t4xxp 12: 879 XT-PIC eth0 14: 2155 XT-PIC ide0 NMI: 0 ERR: 0 Any to back my clams that asterisk is fine, I'm using the TE405P, with a different telco in my second span and it operates fine!! PB

psvasterisk at psv.nu (Pe
Guest

Posted: Wed Jul 20, 2005 9:40 pm Post subject: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-

On Wed, 20 Jul 2005, Paul Belanger wrote:

Quote:

Any to back my clams that asterisk is fine, I'm using the TE405P, with a
different telco in my second span and it operates fine!!

What span is your clock source? A TE405P card can only operate in one
clock domain at a time. I.e. the same clock will be used on all of them.
If both providers are connected to the same TE405P card you will most
likely have a problem with one of them unless they in turn have their
clocks locked to a common source.

Two differently clocked sources wil manifest themselves as the occasional
bit slip. I am not sure if a bit slip can cause the problems on the D
channel you are seeing.

Peter

Display posts from previous:

AsteriskGuru Archives Forum Index -> Asterisk-Users	All times are GMT
Page 1 of 1

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