Date: Mon, 20 Sep 1999 14:00:41 +0200 From: Luke Roberts <luke@roberts.nl> To: Freebsd-isdn@FreeBSD.ORG Subject: 14b L2 and L3 errors Message-ID: <4.2.0.58.19990920140034.009b61d0@pop.roberts.nl>
next in thread | raw e-mail | index | archive | help
Hi, I'mn running i4b version 00.82.0 on FreeBSD 3.2-release on a 300 MHz K6-2 machine with 64 MB SDRAM and a Teles 16.3 ISA non plug n play card. Unfortunatly i4b very often stops working correctly, sometimes after one dialup session and sometimes after a few days. But i never get an i4b uptime of more than 2 days :-( I suspected something was wrong with our ISDN line so I asked the phonecompany to come and check the line. After a lot of tests at the local ISDN switch and at my office they can detect nothing wrong with our ISDN connection. Also the wiring from the FreeBSD machine to the NT1 ISDN box is in order. The FreeBSD machine gives the following error codes: 14b-L2-i4b_T200_timeout: unit 0, RC = 0 Sep 20 10:49:53 dilis /kernel: 14b-L2-i4b_T200_timeout: unit 0, RC = 0 Sep 20 10:49:53 dilis /kernel: 14b-L2-i4b_T200_timeout: unit 0, RC = 0 14b-L3-T305_timeout: DISC not answered, cr = 80 Sep 20 10:50:24 dilis /kernel: 14b-L3-T305_timeout: DISC not answered, cr = 80 Sep 20 10:50:24 dilis /kernel: 14b-L3-T305_timeout: DISC not answered, cr = 80 14b-L3-T308_timeout: REL not answered, cr = 80 Sep 20 10:50:28 dilis /kernel: 14b-L3-T308_timeout: REL not answered, cr = 80 Sep 20 10:50:28 dilis /kernel: 14b-L3-T308_timeout: REL not answered, cr = 80 14b-L3-T303_timeout: SETUP not answered, cr = 94 14b-L3-T303_next_l3state: FSM illegal sate, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! Sep 20 10:50:35 dilis /kernel: 14b-L3-T303_timeout: SETUP not answered, cr = 94 Sep 20 10:50:35 dilis /kernel: 14b-L3-T303_timeout: SETUP not answered, cr = 94 Sep 20 10:50:35 dilis /kernel: 14b-L3-T303_next_l3state: FSM illegal sate, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! Sep 20 10:50:35 dilis /kernel: 14b-L3-T303_next_l3state: FSM illegal sate, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! During these errors the i4b full screen version will display that i4b is "dialing out" but the "outgoing call proceeding" message which is followed with the "outgoing call active" is never switched to state 3 :-(. Sometimes when this error occurs the "outgoing call proceeding" isn't even reached. Has anybody had this problem or can anybody explain what's up? It's realy a pitty this is happening becuase i4b is a great piece of software! Also I heard that some of you leave the machines rinning for months without having to restart i4b. wow if only ;-)..... Also a question? Is anybody working on multichannel ppp? Thanks, Luke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.2.0.58.19990920140034.009b61d0>