Debugging Line Errors

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

 



Thanks Bipin.  Is there a way to check the line / bit / crc error codes?
 Usually routers have a means of seeing that.  Even Sangoma exposes such
information through wanpipe tools.  So, I was searching for something
similar from Digium.  Are there any?

Regards
HASSAN


On Fri, Aug 5, 2011 at 15:09, bipin singh <bipinraghuvanshi at gmail.com>wrote:

> Hi ,
>                     May be CRC4 issue check it .
>
> 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: 2
>> NOTICE[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/0
>> WARNING[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/0
>> NOTICE[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/0
>> NOTICE[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/0
>> NOTICE[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/0
>> WARNING[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.
>>
>> Regards
>> HASSAN
>>
>>
>> --
>> _____________________________________________________________________
>> -- 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
>>
>
>
>
> --
> BIPIN RAGHUVANSHI
> OPERATION HEAD
> ASTERISK (DEVELOPMENT AND RESEARCH)
> WWW.EHORIZONS.IN
> 011-32323262
> 011-46334633
>
> --
> _____________________________________________________________________
> -- 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/20110805/ce07eff9/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