Debugging Line Errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



hi:
Please cat /proc/interrupts, show the IRQ?

Best regards,
James.zhu
Doing asterisk/PRI/ss7/dahdi, linux, asterisk cards, gateway(fxs/fxo/pri<->SIP).
website: www.voipviews.com 


From: mitul@xxxxxxxxxxx
Date: Sat, 30 Jul 2011 14:44:08 +0530
To: asterisk-ss7 at lists.digium.com
Subject: Re: Debugging Line Errors

Looks like you have connected more E1 Channels then what your Server CPU can handle, or the Wire that connects the E1 and the modem has errors (this is not very likely, but the prev one could be the case)
Regards,

Mitul Limbani
On Sat, Jul 30, 2011 at 2:23 PM, Nyamul Hassan <nyamul at gmail.com> wrote:


Hi,
We are getting the following errors from time to time:
NOTICE[29077]: chan_dahdi.c:3312 my_handle_link_exception: SS7 got event: HDLC Bad FCS(8) on span 1/0



WARNING[32196]: app_dial.c:1328 wait_for_answer: Unable to write frametype: 2NOTICE[29077]: chan_dahdi.c:3312 my_handle_link_exception: SS7 got event: HDLC Bad FCS(8) on span 1/0



NOTICE[29077]: chan_dahdi.c:3312 my_handle_link_exception: SS7 got event: HDLC Bad FCS(8) on span 1/0WARNING[32261]: app_dial.c:1328 wait_for_answer: Unable to write frametype: 2



NOTICE[29077]: chan_dahdi.c:3312 my_handle_link_exception: SS7 got event: HDLC Bad FCS(8) on span 1/0NOTICE[29077]: chan_dahdi.c:3312 my_handle_link_exception: SS7 got event: HDLC Bad FCS(8) on span 1/0



NOTICE[29077]: chan_dahdi.c:3312 my_handle_link_exception: SS7 got event: HDLC Bad FCS(8) on span 1/0NOTICE[29077]: chan_dahdi.c:3312 my_handle_link_exception: SS7 got event: HDLC Abort(6) on span 1/0



NOTICE[29077]: chan_dahdi.c:3312 my_handle_link_exception: SS7 got event: HDLC Abort(6) on span 1/0NOTICE[29077]: chan_dahdi.c:3312 my_handle_link_exception: SS7 got event: HDLC Bad FCS(8) on span 1/0



NOTICE[29077]: chan_dahdi.c:3312 my_handle_link_exception: SS7 got event: HDLC Abort(6) on span 1/0WARNING[32264]: app_dial.c:1328 wait_for_answer: Unable to write frametype: 2





What I've read over this mailing list and elsewhere, it is mostly due to a hardware error.
Is there a way to check the hardware errors?  Like, to see the line error, bit error, crc error of the E1 line?  That would help us in debugging transmission related issue.





RegardsHASSAN


--

_____________________________________________________________________

-- Bandwidth and Colocation Provided by http://www.api-digital.com --



asterisk-ss7 mailing list

To UNSUBSCRIBE or update options visit:

   http://lists.digium.com/mailman/listinfo/asterisk-ss7



--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-ss7 mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-ss7 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-ss7/attachments/20110801/81071df5/attachment.htm>


[Index of Archives]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite Backpacking]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]

  Powered by Linux