Looking for some help any way I can. I've been closely following digium's troubleshooting steps and seem to be okay there. I am connecting, via PRI, to a Definity system. When I release the board on the Definity side I get this in Asterisk: *CLI> Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 I've spent about 30 hours so far troubleshooting this problem to no avail with Digium and Avaya. I followed the wiki instruction to start with and have been tweaking and recompiling since then. I tried direct wiring and also using the csu from Avaya. Started with the latest from CVS and have cleaned up and gone back to the stable cvs release. Any advice would be much appreciated! The avaya side says the d-channel is out of service. Configs: /etc/zaptel.conf Loadzone=us defaultzone=us span=1,1,0,d4,b8zs bchan=1-4 #number of channels (Yes I'm only using 4 channels for now) dchan=24 #dchannel /etc/asterisk/zapata.conf [channels] context=default signalling=pri_net switchtype=national ;echocancel=yes ;echocancelwhenbridged=yes ;echotraining=400 callerid=asreceived group=1 channel=>1-4 overlapdial=yes
> -----Original Message----- > From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users- > bounces@lists.digium.com] On Behalf Of Matt Loretitsch > Sent: Thursday, April 07, 2005 9:16 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: [Asterisk-Users] PRI Advice... > > Looking for some help any way I can. I've been closely following > digium's troubleshooting steps and seem to be okay there. I am > connecting, via PRI, to a Definity system. When I release the boardon> the Definity side I get this in Asterisk: > > *CLI> Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI > got event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:48 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI got > event: HDLC Abort (6) on Primary D-channel of span 1 > > I've spent about 30 hours so far troubleshooting this problem to no > avail with Digium and Avaya. I followed the wiki instruction to start > with and have been tweaking and recompiling since then. I trieddirect> wiring and also using the csu from Avaya. Started with the latestfrom> CVS and have cleaned up and gone back to the stable cvs release. Any > advice would be much appreciated! The avaya side says the d-channelis> out of service. > > Configs: > /etc/zaptel.conf > Loadzone=us > defaultzone=us > span=1,1,0,d4,b8zs > bchan=1-4 #number of channels (Yes I'm only using 4 channels fornow)> dchan=24 #dchannel > > /etc/asterisk/zapata.conf > [channels] > context=default > signalling=pri_net > switchtype=national > ;echocancel=yes > ;echocancelwhenbridged=yes > ;echotraining=400 > callerid=asreceived > group=1 > channel=>1-4 > overlapdial=yesSearch www.voip-info.org (wiki) I remember seeing a config posted where * and a definity were connected.
Matt Loretitsch wrote:> Looking for some help any way I can. I've been closely following > digium's troubleshooting steps and seem to be okay there. I am > connecting, via PRI, to a Definity system. When I release the board on > the Definity side I get this in Asterisk: > > *CLI> Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI > got event: HDLC Abort (6) on Primary D-channel of span 1 > Apr 7 10:17:23 NOTICE[13099]: chan_zap.c:7395 pri_dchannel: PRI gotThis appears to be a problem with some specific motherboard. What motherboard (brand AND model) are you using? -- Always do right. This will gratify some people and astonish the rest. Mark Twain
I am using a Dell Optiplex G1. Unable to ascertain who made the motherboard for them at that time. It doesn't look familiar internally. Maybe I'll switch PCI ports and see what comes of it. Mine doesn't appear the share any interrupts either. The zttest gives me 99.999% for a 5 minute average, well above their minimum spec. At least I'm not alone on this. -Matt -----Original Message----- From: Michael Crozier [mailto:crozierm@conducivetech.com] Sent: Friday, April 08, 2005 2:13 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] PRI Advice...> This appears to be a problem with some specific motherboard. ?What > motherboard (brand AND model) are you using?I seem to be having a similar problem, where my asterisk machine appears to lose sync with the PRI/T1. This causes the entire T1 (initially coming through an Adtran 600R to separate the data/voice channels) to be reset, including the data channels. The problems occurs often. NOTICE[3646]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 NOTICE[3646]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 NOTICE[3646]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 I am using an TE110P on a Intel SE7210TP1-E motherboard loaded with Debian testing, but a stock 2.6.11.6 kernel version. The TE110P appears to be on it's own interrupt. The Zaptel and Asterisk code is from stable/1.0.7 CVS. The zaptel drivers are proving quite unstable with this combination. If I attempt to rmmod the zap drivers, the machine hangs and is unresponsive to keyboard input, ping, or sysreq. Additionally, I attempted to bypass the Adtran unit using the TE110's to separate the data channels into an HDLC interface. I wasn't succesfull, as the HDLC interface triggered similar "hanging" problems and I never succeeded in getting packets of the data channels. I'm looking for advice on likely causes of this problem or suggestions for how I might further diagnose it. I welcome any advice regarding my network, software, or hardware configuration. Pointers to helpful documentation or archived discussions would also be quite helpful. Thanks, Michael _______________________________________________ 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