MTP2 CRC errors resulting in flapping link

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

 



On Mon, 2006-07-03 at 13:57 +0200, Kai Militzer wrote:
> Hello list,
> 
> I have a really big problem with the loss of my MTP-link because of CRC 
> errors. I constantly see messages like:
> 
> Jul  3 13:46:06 NOTICE[18867]: mtp.c:1496 mtp_thread_main: Full Zaptel 
> input buffer detected, incoming packets may have been lost on link 'l1'.
> Jul  3 13:46:06 NOTICE[18867]: mtp.c:1543 mtp_thread_main: Empty Zaptel 
> output buffer detected, outgoing packets may have been lost on link 'l1'.
> Jul  3 13:46:06 NOTICE[18867]: mtp.c:1227 mtp2_read_su: MTP2 CRC error 
> (CRC=0xba93 != 0xf0b8) on link 'l1'.
> Jul  3 13:46:06 NOTICE[18867]: mtp.c:1442 mtp_thread_main: Excessive 
> poll delay 57756!
> Jul  3 13:46:06 NOTICE[18867]: mtp.c:1496 mtp_thread_main: Full Zaptel 
> input buffer detected, incoming packets may have been lost on link 'l1'.
> Jul  3 13:46:06 NOTICE[18867]: mtp.c:1543 mtp_thread_main: Empty Zaptel 
> output buffer detected, outgoing packets may have been lost on link 'l1'.
> Jul  3 13:46:06 NOTICE[18867]: mtp.c:1227 mtp2_read_su: MTP2 CRC error 
> (CRC=0x9b7c != 0xf0b8) on link 'l1'.
> 
> And on the other side of the SS7 link on an Alcatel switch there are 
> CRC16 messages logged. I also see
 ^^^^^^

Don't know if it's of any help but afaik the only CRC setting that the
zaptel drivers know about is CRC4. CRC16, by name, seems different.
Perhaps you could try disabling CRC checking on both sides and see if
the problem goes away or, if possible, activate CRC4 (not CRC16)
checking on the Alcatel switch & your Asterisk box.

Regards,
Patrick


[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