asterisk 1.8.7.0 DAHDI Version: 2.4.1.2 libss7-1.0.2 rhino-linux-0.99.4rc1 and a longer log [Nov 22 16:23:13] WARNING[29195] sig_ss7.c: MTP2 link down (SLC 0) [Nov 22 16:23:18] NOTICE[29195] chan_dahdi.c: SS7 got event: HDLC Abort(6) on span 1/0 [Nov 22 16:23:34] NOTICE[29195] chan_dahdi.c: SS7 got event: HDLC Bad FCS(8) on span 1/0 [Dec 1 18:40:38] NOTICE[29195] chan_dahdi.c: SS7 got event: HDLC Abort(6) on span 1/0 [Dec 5 16:41:12] WARNING[29195] sig_ss7.c: MTP2 link down (SLC 0) [Dec 5 16:41:17] NOTICE[29195] chan_dahdi.c: SS7 got event: HDLC Abort(6) on span 1/0 [Dec 5 16:41:37] NOTICE[29195] chan_dahdi.c: SS7 got event: HDLC Abort(6) on span 1/0 [Dec 5 16:41:50] WARNING[29195] sig_ss7.c: MTP2 link down (SLC 0) [Dec 13 22:31:47] WARNING[29195] sig_ss7.c: MTP2 link down (SLC 0) [Dec 19 13:59:37] WARNING[18949] chan_skinny.c: read() returned error: Connection reset by peer [Dec 20 17:44:12] WARNING[19945] app_dial.c: Unable to write frametype: 2 [Dec 20 17:59:59] WARNING[19950] app_dial.c: Unable to forward frametype: 2 [Dec 21 08:19:06] WARNING[20446] app_dial.c: Unable to write frametype: 2 [Dec 21 10:44:14] WARNING[20631] app_dial.c: Unable to write frametype: 2 [Dec 21 12:07:46] WARNING[20660] app_dial.c: Unable to write frametype: 2 [Dec 22 07:42:53] WARNING[21484] app_dial.c: Unable to write frametype: 2 [Dec 23 10:40:36] WARNING[29195] sig_ss7.c: REL on channel (CIC 77) without owner! [Dec 24 06:01:23] ERROR[29195] chan_dahdi.c: [1] !! Unable to handle message of type 0xd on CIC 24 [Dec 24 09:10:27] WARNING[23033] app_dial.c: Unable to write frametype: 2 [Dec 24 12:31:56] WARNING[23124] app_dial.c: Unable to write frametype: 2 [Dec 25 07:02:26] WARNING[23798] app_dial.c: Unable to write frametype: 2 [Dec 25 15:28:22] WARNING[24049] app_dial.c: Unable to write frametype: 2 [Dec 25 16:03:32] WARNING[24072] app_dial.c: Unable to write frametype: 2 [Dec 25 19:04:03] WARNING[29195] sig_ss7.c: MTP2 link down (SLC 0) [Dec 25 19:04:08] NOTICE[29195] chan_dahdi.c: SS7 got event: HDLC Abort(6) on span 1/0 [Dec 25 23:29:32] WARNING[24235] app_dial.c: Unable to write frametype: 2 [Dec 26 04:52:23] WARNING[24417] app_dial.c: Unable to write frametype: 2 [Dec 27 06:13:02] ERROR[29195] chan_dahdi.c: [1] !! Unable to handle message of type 0xd on CIC 24 [Dec 28 11:30:07] WARNING[26424] app_dial.c: Unable to forward frametype: 2 [Dec 30 05:53:19] ERROR[29195] chan_dahdi.c: [1] !! Unable to handle message of type 0xd on CIC 24 [Dec 30 05:53:20] ERROR[29195] chan_dahdi.c: [1] !! Unable to handle message of type 0xe on CIC 24 [Dec 30 08:13:01] NOTICE[29208] chan_iax2.c: Auto-congesting call due to slow response [Dec 30 08:13:33] NOTICE[29204] chan_iax2.c: Auto-congesting call due to slow response [Dec 31 06:27:12] WARNING[29289] app_dial.c: Unable to write frametype: 2 [Dec 31 06:44:33] WARNING[29402] app_dial.c: Unable to write frametype: 2 [Dec 31 21:00:36] WARNING[29195] sig_ss7.c: MTP2 link down (SLC 0) [Dec 31 21:00:41] NOTICE[29195] chan_dahdi.c: SS7 got event: HDLC Abort(6) on span 1/0 [Dec 31 21:00:56] NOTICE[29195] chan_dahdi.c: SS7 got event: HDLC Bad FCS(8) on span 1/0 [Jan 1 22:21:48] WARNING[29195] sig_ss7.c: REL on channel (CIC 24) without owner! [Jan 2 16:13:40] WARNING[31144] app_dial.c: Unable to write frametype: 2 [Jan 3 05:12:46] WARNING[31497] app_dial.c: Unable to forward frametype: 2 [Jan 4 11:17:11] WARNING[32667] app_dial.c: Unable to write frametype: 2 -----Original Message----- From: asterisk-ss7-bounces@xxxxxxxxxxxxxxxx [mailto:asterisk-ss7-bounces at lists.digium.com] On Behalf Of Jakub Klausa Sent: Wednesday, January 04, 2012 11:04 AM To: asterisk-ss7 at lists.digium.com Subject: Re: Unable to forward frametype: 2 On 4 sty 2012, at 19:30, Ryan Crowder wrote: > > Can someone help me with these frametype 2 errors? They occasionally cause a CHANUNAVAIL and failed call. Thanks! > > [Dec 30 05:53:19] ERROR[29195] chan_dahdi.c: [1] !! Unable to handle > message of type 0xd on CIC 24 [Dec 30 05:53:20] ERROR[29195] > chan_dahdi.c: [1] !! Unable to handle message of type 0xe on CIC 24 You haven't provide enough information to identify the problem to the point, but your problems begin here, and for now you can just simply ignore the forwarding of frametype 2, as your problem are related to the signaling itself here - i think 0xd is SUS which as the error message clearly states was not handled properly. > > [Dec 31 21:00:36] WARNING[29195] sig_ss7.c: MTP2 link down (SLC 0) > [Dec 31 21:00:41] NOTICE[29195] chan_dahdi.c: SS7 got event: HDLC > Abort(6) on span 1/0 [Dec 31 21:00:56] NOTICE[29195] chan_dahdi.c: SS7 > got event: HDLC Bad FCS(8) on span 1/0 [Jan 1 22:21:48] WARNING[29195] sig_ss7.c: REL on channel (CIC 24) without owner! Is that a call that lasted for several days, since the dates would suggest it. Anyway, the HDLC errors and MTP problems may be your bigger worries then the forwarding of frametype 2 at the moment. If you'd provide informations about your setup (especially software versions you're using) and more consistent logs, it should be easier to try to help you out. -- Jakub Klausa | +48 509 032 888 | j.klausa at ss7.pl | http://www.ss7.pl/ Dane rejestrowe -> http://kontakt.ss7.pl -- _____________________________________________________________________ -- 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 ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4722 - Release Date: 01/04/12 CONFIDENTIALITY / PRIVILEGE NOTICE: This transmission and any attachments are intended solely for the addressee. This transmission is covered by the Electronic Communications Privacy Act, 18 U.S.C ?? 2510-2521. The information contained in this transmission is confidential in nature and protected from further use or disclosure under U.S. Pub. L. 106-102, 113 U.S. Stat. 1338 (1999), and may be subject to attorney-client or other legal privilege. Your use or disclosure of this information for any purpose other than that intended by its transmittal is strictly prohibited, and may subject you to fines and/or penalties under federal and state law. If you are not the intended recipient of this transmission, please DESTROY ALL COPIES RECEIVED and confirm destruction to the sender via return transmittal.
|