Date: Thu, 04 Jun 1998 22:23:04 +0200 From: Harald Hanche-Olsen <hanche@math.ntnu.no> To: freebsd-isdn@FreeBSD.ORG Subject: Re: idletime disconnect won't work Message-ID: <19980604222304B.hanche@math.ntnu.no> In-Reply-To: Your message of "Sun, 31 May 1998 15:40:54 %2B0200 (CEST)" <m0yg8M2-00024SC@bert.kts.org> References: <m0yg8M2-00024SC@bert.kts.org>
next in thread | previous in thread | raw e-mail | index | archive | help
- hm@kts.org (Hellmuth Michaelis): | > While I am *not* online, I get messages like these in the log. | > | > May 28 23:28:12 thoth /kernel: i4b-L1-isic_isac_irq: CRC error | > May 28 23:28:12 thoth /kernel: i4b-L1-isic_isac_irq: Receive Aborted error | | I suspect this is noise, a wrong cable or a bad cable contact. I've seen | exactly this with a bad cable although others have different opinions on | this. After i cut one of the plugs on the cable and crimped a new one on | that cable this effects disappeared. | | If i were you, i would have a _very_ detailed look at my S0 bus | installation and verify _all_ S0 cables, contacts, wire orders and | bus termination. Um, maybe I'll try that. Except I don't really have the equipment, and I need a good excuse to have the phone company do it for me. 8-) But see below... | > Or is there always some traffic on the S-bus, even when | > nothing interesting is going on? | | Ususally, all traffic stops 10 seconds after the last device using the S0 | bus has stopped communicating. But there are exceptions, it seems that here | in Germany it is possible to get a "constantly active" S0 bus by asking for | it or by accident (Gary has one ;-). | | > Again, how can I find out more about what is happening? | | By debugging at various parts and levels of i4b. Using isdndebug you are | able to trace many events at all layers of the kernel part; using isdntrace | (have a look at the -i flag output) shows what is going on on the S0 bus | for the machine running i4b - using a second machine with 2 passive cards Haven't got a second machine, sorry... But I stopped isdnd and ran isdntrace -b on my one machine, and this appeared: =========== isdntrace controller #0 =========== started Thu Jun 4 22:04:00 1998 -- NT->TE - unit:0 - frame:000001 - time:04.06 22:04:24.58 - length:8 ---------- Dump:000 fe ff 03 0f 00 00 04 ff ........ LAPD: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=127 -- TE->NT - unit:0 - frame:000002 - time:04.06 22:04:24.58 - length:8 ---------- Dump:000 fc ff 03 0f 4d 9c 05 83 ....M... LAPD: SAP=63 (TEI-Management), C, TEI=127, Ri=0x9c4d, IdCheckResp, Ai=65 -- NT->TE - unit:0 - frame:000003 - time:04.06 22:04:56.79 - length:8 ---------- Dump:000 fe ff 03 0f 00 00 04 ff ........ LAPD: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=127 -- TE->NT - unit:0 - frame:000004 - time:04.06 22:04:56.79 - length:8 ---------- Dump:000 fc ff 03 0f d8 59 05 83 .....Y.. LAPD: SAP=63 (TEI-Management), C, TEI=127, Ri=0x59d8, IdCheckResp, Ai=65 -- NT->TE - unit:0 - frame:000005 - time:04.06 22:05:29.01 - length:8 ---------- Dump:000 fe ff 03 0f 00 00 04 ff ........ LAPD: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=127 -- TE->NT - unit:0 - frame:000006 - time:04.06 22:05:29.01 - length:8 ---------- Dump:000 fc ff 03 0f 29 b6 05 83 ....)... LAPD: SAP=63 (TEI-Management), C, TEI=127, Ri=0xb629, IdCheckResp, Ai=65 These messages came in groups of two, one IdCheckReq and one IdCheckResp at the time, and always at the same time log messages like showed above appeared. Seems like my NT box is chattering to my ISDN telephone, asking for an identity and getting a response back, at irregular intervals. Comments? - Harald 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?19980604222304B.hanche>