From owner-freebsd-isdn Sun Jan 21 9:23:10 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by hub.freebsd.org (Postfix) with ESMTP id EF00337B400 for ; Sun, 21 Jan 2001 09:22:53 -0800 (PST) Received: from fwd04.sul.t-online.com by mailout05.sul.t-online.com with smtp id 14KOCa-0000nK-04; Sun, 21 Jan 2001 18:22:52 +0100 Received: from night-porter.duskware.de (520038743430-0001@[62.155.250.5]) by fmrl04.sul.t-online.com with esmtp id 14KOCP-0pl2kSC; Sun, 21 Jan 2001 18:22:41 +0100 Received: (from martin@localhost) by night-porter.duskware.de (8.11.2/8.11.0) id f0LHMeP11802; Sun, 21 Jan 2001 18:22:40 +0100 (MET) From: Martin Husemann Message-Id: <200101211722.f0LHMeP11802@night-porter.duskware.de> Subject: Re: turning on isplink via another computer In-Reply-To: <004001c0817e$4c5bc940$0200a8c0@coyote> "from Steven Looman at Jan 18, 2001 07:41:41 pm" To: freebsd-isdn@freebsd.org Date: Sun, 21 Jan 2001 18:22:40 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL78 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Sender: 520038743430-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wrote: > If there is demand I'll make these things available. I've made it available (source and win32 binary) at http://www.duskware.com/isp Enjoy! Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jan 22 7:49:17 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from smtp4.libero.it (smtp4.libero.it [193.70.192.54]) by hub.freebsd.org (Postfix) with ESMTP id 4384B37B6BF for ; Mon, 22 Jan 2001 07:48:56 -0800 (PST) Received: from office (151.21.169.189) by smtp4.libero.it (5.5.015.5) id 3A54738F00B984AD for freebsd-isdn@freebsd.org; Mon, 22 Jan 2001 16:48:53 +0100 Message-ID: <000901c0848a$dfd1dd40$0101a8c0@pyxiscomputers.com> From: "Vittorio Mori" To: Subject: Problems in making a call with i4b ... Date: Mon, 22 Jan 2001 16:48:00 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello out there. I still have big problems in placing a call with i4b, the isdn stack keeps telling me this "invalid number" thing. This happened when I switched to the latest -STABLE. This weekend, I reformatted the whole BSD box to a 4.1.1-RELEASE version, with i4b 0.90.1 but the problem persists. I made many tests, I post here the results, hoping there is a solution for this. Pc used: BSD Box: - Intel PII 266 - Intel Ex chipset PII board - USRobotics Sportster ISA ISDN TA card First, I tested the NT with another PC under Win98, using a cheap PCI ISDN card based on the "cologne" chipset. Worked fine. So the NT is ok, I thought. Then, I used the other partition on the isdn-freebsd box, to set up a temporary win98. I loaded the drivers for the USR ISA TA card, to my greatest surprise (I was convinced that the card was faulty) worked fine (!). I guess now that there is a software problem either in i4b or in 4.2-STABLE .... or something very weird, this configuration has always worked fine for me (7 months), and this ISDN TA has passed trough GOBS of data ... I traced the s0 bus; Here is what I have got when the Win98 Machine (PCI "cologne" chipset card) calls (and connects): =========== isdntrace controller #0 =========== started Mon Jan 22 16:26:38 2001 -- NT->TE - unit:0 - frame:000169 - time:22.01 16:26:48.206721 - length:3 ------ Dump:000 00 d1 73 ..s Q921: SAP=0 (Call Control), R, TEI=104, U-Frame: UA PF 1 -- NT->TE - unit:0 - frame:000170 - time:22.01 16:26:48.266722 - length:4 ------ Dump:000 00 d1 01 02 .... Q921: SAP=0 (Call Control), R, TEI=104, S-Frame: RR N(R) 1 PF 0 -- NT->TE - unit:0 - frame:000171 - time:22.01 16:26:48.326723 - length:11 ----- Dump:000 02 d1 00 02 .... Q921: SAP=0 (Call Control), C, TEI=104, I-Frame: N(S) 0 N(R) 1 P 0 Dump:004 08 01 84 0d 18 01 89 ....... Q931: pd=Q.931/I.451, cr=0x04 (from destination), message=SETUP ACKNOWLEDGE: [channel id: channel=B-1 (exclusive)] -- NT->TE - unit:0 - frame:000172 - time:22.01 16:26:49.116735 - length:12 ----- Dump:000 02 d1 02 02 .... Q921: SAP=0 (Call Control), C, TEI=104, I-Frame: N(S) 1 N(R) 1 P 0 Dump:004 08 01 84 07 4c 02 00 a3 ....L... Q931: pd=Q.931/I.451, cr=0x04 (from destination), message=CONNECT: [connected number (Q.951): (type=unknown, plan=unknown, presentation restricted, screening network provided)] -- NT->TE - unit:0 - frame:000173 - time:22.01 16:26:49.186737 - length:4 ------ Dump:000 00 d1 01 04 .... Q921: SAP=0 (Call Control), R, TEI=104, S-Frame: RR N(R) 2 PF 0 -- NT->TE - unit:0 - frame:000174 - time:22.01 16:26:56.366844 - length:8 ------ Dump:000 02 d1 04 06 .... Q921: SAP=0 (Call Control), C, TEI=104, I-Frame: N(S) 2 N(R) 3 P 0 Dump:004 08 01 84 4d ...M Q931: pd=Q.931/I.451, cr=0x04 (from destination), message=RELEASE: -- NT->TE - unit:0 - frame:000175 - time:22.01 16:26:56.496848 - length:4 ------ Dump:000 00 d1 01 08 .... Q921: SAP=0 (Call Control), R, TEI=104, S-Frame: RR N(R) 4 PF 0 ============================ end =========================== (the RELEASE message it's me hanging up) And here's what I get when I call with the FreeBSD Box, using the USR ISDN TA: =========== isdntrace controller #0 =========== started Mon Jan 22 16:38:43 2001 -- TE->NT - unit:0 - frame:000176 - time:22.01 16:38:56.307707 - length:8 ------ Dump:000 fc ff 03 0f 1e 00 01 ff ........ Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x001e, IdRequest, Ai=127 -- TE->NT - unit:0 - frame:000177 - time:22.01 16:38:58.307735 - length:8 ------ Dump:000 fc ff 03 0f 11 f6 01 ff ........ Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0xf611, IdRequest, Ai=127 -- NT->TE - unit:0 - frame:000178 - time:22.01 16:38:58.327735 - length:8 ------ Dump:000 fe ff 03 0f 11 f6 02 d9 ........ Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0xf611, IdAssign, Ai=108 -- TE->NT - unit:0 - frame:000179 - time:22.01 16:38:58.327735 - length:3 ------ Dump:000 00 d9 7f ... Q921: SAP=0 (Call Control), C, TEI=108, U-Frame: SABME PF 1 -- NT->TE - unit:0 - frame:000180 - time:22.01 16:38:58.337737 - length:3 ------ Dump:000 00 d9 73 ..s Q921: SAP=0 (Call Control), R, TEI=108, U-Frame: UA PF 1 -- TE->NT - unit:0 - frame:000181 - time:22.01 16:38:58.337737 - length:41 ----- Dump:000 00 d9 00 00 .... Q921: SAP=0 (Call Control), C, TEI=108, I-Frame: N(S) 0 N(R) 0 P 0 Dump:004 08 01 3a 05 a1 04 02 88 90 18 01 83 6c 0b 81 30 ..:.........l..0 Dump:020 37 33 33 38 31 37 38 34 33 70 0a 81 38 30 30 31 733817843p..8001 Dump:036 30 31 38 31 38 01818 Q931: pd=Q.931/I.451, cr=0x3a (from origination), message=SETUP: [sending complete] [bearer capability: cap=unrestricted digital information std=CCITT rate=64 kbit/s mode=circuit] [channel id: channel=any channel (preferred)] [calling party number: 0733817843 (type=unknown, plan=ISDN)] [called party number: 800101818 (type=unknown, plan=ISDN)] -- NT->TE - unit:0 - frame:000182 - time:22.01 16:38:58.417737 - length:12 ----- Dump:000 02 d9 00 02 .... Q921: SAP=0 (Call Control), C, TEI=108, I-Frame: N(S) 0 N(R) 1 P 0 Dump:004 08 01 ba 5a 08 02 82 9c ...Z.... Q931: pd=Q.931/I.451, cr=0x3a (from destination), message=RELEASE COMPLETE: [cause: 28: Invalid number format (Q.850) (location=public network serving local user, std=CCITT)] ======================= end =================================== Does anyone have this kind of problems ? It's becoming overwhelmingly frustrating. Bye, Wyk'00 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jan 22 8:55:22 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id C619337B69C for ; Mon, 22 Jan 2001 08:55:04 -0800 (PST) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id DAA505D1E; Mon, 22 Jan 2001 17:54:07 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id 3F43151F; Mon, 22 Jan 2001 18:04:28 +0100 (MET) Subject: Re: Problems in making a call with i4b ... In-Reply-To: <000901c0848a$dfd1dd40$0101a8c0@pyxiscomputers.com> "from Vittorio Mori at Jan 22, 2001 04:48:00 pm" To: Vittorio Mori Date: Mon, 22 Jan 2001 18:04:28 +0100 (MET) Cc: freebsd-isdn@freebsd.org Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010122170428.3F43151F@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Vittorio Mori: > I still have big problems in placing a call with i4b, the isdn stack keeps > telling me this "invalid number" thing. [...] > Dump:020 37 33 33 38 31 37 38 34 33 70 0a 81 38 30 30 31 > 733817843p..8001 > Dump:036 30 31 38 31 38 01818 > Q931: pd=Q.931/I.451, cr=0x3a (from origination), message=SETUP: > [sending complete] > [bearer capability: > cap=unrestricted digital information > std=CCITT > rate=64 kbit/s > mode=circuit] > [channel id: channel=any channel (preferred)] > [calling party number: 0733817843 (type=unknown, plan=ISDN)] > [called party number: 800101818 (type=unknown, plan=ISDN)] > > -- NT->TE - unit:0 - frame:000182 - time:22.01 16:38:58.417737 - > length:12 ----- > Dump:000 02 d9 00 02 .... > Q921: SAP=0 (Call Control), C, TEI=108, I-Frame: N(S) 0 N(R) 1 P 0 > Dump:004 08 01 ba 5a 08 02 82 9c ...Z.... > Q931: pd=Q.931/I.451, cr=0x3a (from destination), message=RELEASE COMPLETE: > [cause: 28: Invalid number format (Q.850) > (location=public network serving local user, std=CCITT)] This all looks like the isdn stack and your card and your machine is in perfect working order. There is nothing wrong. Cause 28 says: Invalid number format (adress incomplete) : this cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete. So the communication from you to the exchange is working and is obviously in a good condition. I would double and triple check the called (800101818) number, this is cause of the problem. Just to try, use a different number (even your own number will do here) and see what happenes. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Jan 24 5:38:15 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hermes.element5.com (hermes.element-5.de [195.185.111.26]) by hub.freebsd.org (Postfix) with SMTP id B628937B402 for ; Wed, 24 Jan 2001 05:37:58 -0800 (PST) Received: (qmail 90792 invoked by uid 1001); 24 Jan 2001 14:37:53 +0100 Message-ID: <20010124133753.90791.qmail@hermes.element5.com> From: glaess@element5.de To: freebsd-isdn@freebsd.org Subject: status of avm b1 driver Date: Wed, 24 Jan 2001 13:37:53 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi is any one there he can tell me the status of the avm b1 driver of the i4b packet na where can i get. thanks holger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Jan 24 6:57:51 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 5940137B69E for ; Wed, 24 Jan 2001 06:57:34 -0800 (PST) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 08E205D28; Wed, 24 Jan 2001 15:56:32 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id 23B2252A; Wed, 24 Jan 2001 16:06:58 +0100 (MET) Subject: Re: status of avm b1 driver In-Reply-To: <20010124133753.90791.qmail@hermes.element5.com> "from glaess@element5.de at Jan 24, 2001 01:37:53 pm" To: glaess@element5.de Date: Wed, 24 Jan 2001 16:06:58 +0100 (MET) Cc: freebsd-isdn@freebsd.org Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010124150658.23B2252A@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of glaess@element5.de: > is any one there he can tell me the status of the avm b1 driver of the > i4b packet na where can i get. The AVM B1 card is not supported and it don't looks like it will ever be supported. In case anyone likes to write a driver for it there are cards for development purposes available. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Jan 24 7:31:42 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from leka.almamedia.fi (leka.yhteys.mtv3.fi [62.236.224.129]) by hub.freebsd.org (Postfix) with SMTP id 466B737B402 for ; Wed, 24 Jan 2001 07:31:22 -0800 (PST) Received: (qmail 4670 invoked from network); 24 Jan 2001 15:31:19 -0000 Received: from dyn-n-039.yhteys.mtv3.fi (HELO snafu.intra.net) (62.236.238.39) by leka.yhteys.mtv3.fi with SMTP; 24 Jan 2001 15:31:19 -0000 Received: from cubical.fi (junkyard.intra.net [192.168.2.2]) by snafu.intra.net (8.11.1/8.9.3) with ESMTP id f0OFW1S10037; Wed, 24 Jan 2001 17:32:27 +0200 (EET) (envelope-from jml@cubical.fi) Message-ID: <3A6EF4F8.A5B48661@cubical.fi> Date: Wed, 24 Jan 2001 17:30:00 +0200 From: Juha-Matti Liukkonen Organization: Cubical Solutions Ltd X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: hm@hcs.de Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: status of avm b1 driver References: <20010124150658.23B2252A@hcswork.hcs.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, FYI, I am in the process of implementing a capi pseudo-device driver which attaches to i4b L4 to support active devices implementing the CAPI 2.0 interface. An underlying hardware driver implements actual hardware communications for the message passing to/from the device. My target is AVM T1 (a PRI device), but the capi layer would conceivably ease supporting other capi based devices as well. The project is currently in-house and made for a specific commercial application, but I see no reason why it could not be made public domain at some point. I am currently waiting for the testing environment to become available, and the implementation is pending final cleanup until then. I am somewhat open to suggestions on possible generalisations of the architecture; for example, the current implementation does not support the userland /dev/capi20 interface specified in the std part III, as we have no need for that, but someone might. - Juha Hellmuth Michaelis wrote: > > >From the keyboard of glaess@element5.de: > > > is any one there he can tell me the status of the avm b1 driver of the > > i4b packet na where can i get. > > The AVM B1 card is not supported and it don't looks like it will ever > be supported. > > In case anyone likes to write a driver for it there are cards for > development purposes available. > > hellmuth > -- > Hellmuth Michaelis Tel +49 40 55 97 47-70 > HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 > Oldesloer Strasse 97-99 Mail hm [at] hcs.de > D-22457 Hamburg WWW http://www.hcs.de > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message -- Juha-Matti Liukkonen, Cubical Solutions Ltd Phone: +358(0)405280142 Email: jml@cubical.fi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Jan 24 7:59:52 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id DD9DF37B401 for ; Wed, 24 Jan 2001 07:59:34 -0800 (PST) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 6F7C05D28; Wed, 24 Jan 2001 16:58:36 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id B827651C; Wed, 24 Jan 2001 17:09:02 +0100 (MET) Subject: Re: status of avm b1 driver In-Reply-To: <3A6EF4F8.A5B48661@cubical.fi> "from Juha-Matti Liukkonen at Jan 24, 2001 05:30:00 pm" To: Juha-Matti Liukkonen Date: Wed, 24 Jan 2001 17:09:02 +0100 (MET) Cc: freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010124160902.B827651C@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Juha-Matti Liukkonen: > FYI, I am in the process of implementing a capi pseudo-device driver > which attaches to i4b L4 to support active devices implementing the CAPI > 2.0 interface. An underlying hardware driver implements actual hardware > communications for the message passing to/from the device. My target is > AVM T1 (a PRI device), but the capi layer would conceivably ease > supporting other capi based devices as well. Hurray! Now this is really good news! hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jan 27 13: 7: 2 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id F1DEB37B69C for ; Sat, 27 Jan 2001 13:06:43 -0800 (PST) Received: from post.rwth-aachen.de (s4m016.dialup.RWTH-Aachen.DE [137.226.8.16]) by nets5.rz.rwth-aachen.de (8.10.1/8.10.1/6) with ESMTP id f0RL6gL03974 for ; Sat, 27 Jan 2001 22:06:42 +0100 (MET) Message-ID: <3A7338BE.FA7EC4B9@post.rwth-aachen.de> Date: Sat, 27 Jan 2001 22:08:14 +0100 From: Gerald Heinig X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-isdn@freebsd.org Subject: Question about FRMR transmit, although docs say not to Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there, I've just been sifting through the Q921 standard and I've come across something weird. It says that upon *reception* of a FRMR (Frame Reject) frame, something should occur. Fine. It does not, however, state anywhere that a FRMR frame should be *transmitted* at any time. In fact, on page 143 it states in a note: "NOTE-An FRMR-response shall not be generated by a data link layer entity; however, on receipt of this frame actions according to E5.8.6 shall be taken". This has me puzzled, since if you don't transmit a certain frame at any time (according to the state machine definition), you can't expect to receive it! The above note is rather contradictory. My only explanation for it is that it's for back-compatibility with an older protocol (1TR6?). Is this correct? I've seen that i4b does in fact *transmit* this frame as well. Is this 1TR6 standard? Cheers, Gerald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jan 27 13:19:11 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from smtp.kdt.de (ns2.kdt.de [195.8.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 9233F37B400 for ; Sat, 27 Jan 2001 13:18:53 -0800 (PST) Received: from beverly.kleinbus.org (line0503.kdt.de [213.240.146.3]) by smtp.kdt.de (8.8.8/8.8.8) with ESMTP id WAA15804; Sat, 27 Jan 2001 22:18:44 +0100 Received: by beverly.kleinbus.org (Postfix, from userid 1501) id CBBB170; Sat, 27 Jan 2001 22:17:37 +0100 (CET) Date: Sat, 27 Jan 2001 22:17:37 +0100 From: Ignatios Souvatzis To: Gerald Heinig Cc: freebsd-isdn@freebsd.org Subject: Re: Question about FRMR transmit, although docs say not to Message-ID: <20010127221737.C1588@beverly.kleinbus.org> References: <3A7338BE.FA7EC4B9@post.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A7338BE.FA7EC4B9@post.rwth-aachen.de>; from Gerald.Heinig@post.rwth-aachen.de on Sat, Jan 27, 2001 at 10:08:14PM +0100 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jan 27, 2001 at 10:08:14PM +0100, Gerald Heinig wrote: > Hi there, > This has me puzzled, since if you don't transmit a certain frame at any time (according to the state machine > definition), you can't expect to receive it! Uhm, wait. - You can expect to have equipment working according to older (or newer) protocol versions - hm, is the protocol symmetric at that level at all? If not, the other side might well be allowed to send that. Regards, -is To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jan 27 15:35:12 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id D602537B400 for ; Sat, 27 Jan 2001 15:34:54 -0800 (PST) Received: from post.rwth-aachen.de (s4m229.dialup.RWTH-Aachen.DE [137.226.8.229]) by nets5.rz.rwth-aachen.de (8.10.1/8.10.1/6) with ESMTP id f0RNYmL19953; Sun, 28 Jan 2001 00:34:48 +0100 (MET) Message-ID: <3A735B6F.D0644868@post.rwth-aachen.de> Date: Sun, 28 Jan 2001 00:36:15 +0100 From: Gerald Heinig X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Ignatios Souvatzis Cc: freebsd-isdn@freebsd.org Subject: Re: Question about FRMR transmit, although docs say not to References: <3A7338BE.FA7EC4B9@post.rwth-aachen.de> <20010127221737.C1588@beverly.kleinbus.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ignatios Souvatzis wrote: > > On Sat, Jan 27, 2001 at 10:08:14PM +0100, Gerald Heinig wrote: > > Hi there, > > This has me puzzled, since if you don't transmit a certain frame at any time (according to the state machine > > definition), you can't expect to receive it! > > Uhm, wait. > > - You can expect to have equipment working according to older (or newer) > protocol versions That's the only reason I could think of that makes sense. > > - hm, is the protocol symmetric at that level at all? If not, the other side > might well be allowed to send that. Quite right. The protocol isn't symmetric, but I was under the impression that Q921 describes TE _and_ NT behaviour. If it only describes TE behaviour, then that would answer the question. However, why does i4b then _transmit_ a FRMR frame? > > Regards, > -is To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jan 27 16:30:22 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from gnu.in-berlin.de (gnu.in-berlin.de [192.109.42.4]) by hub.freebsd.org (Postfix) with ESMTP id C862B37B404 for ; Sat, 27 Jan 2001 16:30:02 -0800 (PST) Received: from hirsch.in-berlin.de (root@hirsch.colt.in-berlin.de [213.61.118.6]) by gnu.in-berlin.de (8.10.1/8.10.1) with ESMTP id f0S0U1B15946 for ; Sun, 28 Jan 2001 01:30:01 +0100 (CET) (envelope-from balu@dva.in-berlin.de) Received: (from uucp@localhost) by hirsch.in-berlin.de (8.11.1/8.11.1/Debian 8.11.0-6) with UUCP id f0S0U1j05006 for freebsd-isdn@freebsd.org; Sun, 28 Jan 2001 01:30:01 +0100 X-Envelope-From: balu@dva.in-berlin.de X-Envelope-To: freebsd-isdn@freebsd.org Received: by dva.in-berlin.de (Postfix, from userid 200) id A494E3FD5; Sun, 28 Jan 2001 01:28:01 +0100 (CET) Date: Sun, 28 Jan 2001 01:28:01 +0100 From: Boris Staeblow To: freebsd-isdn@freebsd.org Subject: ppp dialin didn't work with userland ppp Message-ID: <20010128012801.A5785@dva.in-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I can`t dial into my FreeBSD 4.2-STABLE machine. :-( Setup: FreeBSD 4.2-STABLE, i4b 00.96/Fritz isa, userland-ppp. Client: Windows 98, Fritz/PCI. Any hints? tun0: Phase: PPP Started (direct mode). tun0: Debug: Select changes time: no tun0: Phase: bundle: Establish tun0: Phase: deflink: closed -> opening tun0: Debug: deflink: Input is an i4b version 0.96.0 isdn device (/dev/i4brbch0) tun0: Phase: deflink: Connected! tun0: Phase: deflink: opening -> carrier tun0: Debug: deflink: Using i4b_Timeout [0x8086480] tun0: Debug: Waiting for carrier tun0: Phase: deflink: /dev/i4brbch0: CD detected tun0: Debug: deflink: Entering i4b_Raw tun0: Phase: deflink: carrier -> lcp tun0: Debug: deflink: DescriptorRead: read 27/2048 from 0 tun0: Debug: proto_LayerPull: unknown -> 0xc021 tun0: Debug: link_PullPacket: Despatch proto 0xc021 tun0: Debug: fsm_Output tun0: Debug: 01 01 00 16 01 04 05 dc 05 06 42 fb c2 fa 04 08 ..........B..... tun0: Debug: c0 25 00 00 11 94 .%.... tun0: Debug: proto_LayerPush: Using 0xc021 tun0: Debug: link_PushPacket: Transmit proto 0xc021 tun0: Debug: m_enqueue: len = 1 tun0: Debug: fsm_Output tun0: Debug: 04 01 00 07 0d 03 06 ....... tun0: Debug: proto_LayerPush: Using 0xc021 tun0: Debug: link_PushPacket: Transmit proto 0xc021 tun0: Debug: m_enqueue: len = 2 tun0: Debug: m_dequeue: queue len = 2 tun0: Debug: link_Dequeue: Dequeued from queue 1, containing 1 more packets tun0: Debug: deflink: DescriptorWrite: wrote 26(26) to 0 tun0: Debug: m_dequeue: queue len = 1 tun0: Debug: link_Dequeue: Dequeued from queue 1, containing 0 more packets tun0: Debug: deflink: DescriptorWrite: wrote 11(11) to 0 tun0: Debug: deflink: DescriptorRead: read 16/2048 from 0 tun0: Debug: proto_LayerPull: unknown -> 0xc021 tun0: Debug: link_PullPacket: Despatch proto 0xc021 tun0: Debug: fsm_Output tun0: Debug: 01 02 00 0e 01 04 05 dc 05 06 42 fb c2 fa ..........B... tun0: Debug: proto_LayerPush: Using 0xc021 tun0: Debug: link_PushPacket: Transmit proto 0xc021 tun0: Debug: m_enqueue: len = 1 tun0: Debug: m_dequeue: queue len = 1 tun0: Debug: link_Dequeue: Dequeued from queue 1, containing 0 more packets tun0: Debug: deflink: DescriptorWrite: wrote 18(18) to 0 tun0: Debug: deflink: DescriptorRead: read 24/2048 from 0 tun0: Debug: proto_LayerPull: unknown -> 0xc021 tun0: Debug: link_PullPacket: Despatch proto 0xc021 tun0: Debug: fsm_Output tun0: Debug: 02 02 00 14 02 06 00 0a 00 00 05 06 01 a3 a3 23 ...............# tun0: Debug: 07 02 08 02 .... tun0: Debug: proto_LayerPush: Using 0xc021 tun0: Debug: link_PushPacket: Transmit proto 0xc021 tun0: Debug: m_enqueue: len = 1 tun0: Debug: m_dequeue: queue len = 1 tun0: Debug: link_Dequeue: Dequeued from queue 1, containing 0 more packets tun0: Debug: deflink: DescriptorWrite: wrote 24(24) to 0 tun0: Debug: deflink: DescriptorRead: read 18/2048 from 0 tun0: Debug: proto_LayerPull: unknown -> 0xc021 tun0: Debug: link_PullPacket: Despatch proto 0xc021 tun0: Debug: fsm_Output tun0: Debug: 09 00 00 10 42 fb c2 fa 59 4e 4f 54 00 00 00 00 ....B...YNOT.... tun0: Debug: proto_LayerPush: Using 0xc021 tun0: Debug: link_PushPacket: Transmit proto 0xc021 tun0: Debug: m_enqueue: len = 1 tun0: IPCP: Using trigger address 0.0.0.0 tun0: CCP: FSM: Using "deflink" as a transport tun0: CCP: deflink: State change Initial --> Closed tun0: CCP: deflink: LayerStart. tun0: CCP: MPPE: InitOptsOutput tun0: CCP: MPPE: MasterKey is invalid, MPPE is capable only with CHAP81 authentication tun0: CCP: deflink: SendConfigReq(1) state = Closed tun0: CCP: MPPE[6] value 0x00000000 tun0: Debug: fsm_Output tun0: Debug: 01 01 00 0a 12 06 00 00 00 00 .......... tun0: Debug: proto_LayerPush: Using 0x80fd tun0: Debug: link_PushPacket: Transmit proto 0x80fd tun0: Debug: m_enqueue: len = 2 tun0: CCP: deflink: State change Closed --> Req-Sent tun0: Phase: deflink: lcp -> open tun0: Phase: bundle: Network tun0: IPCP: FSM: Using "deflink" as a transport tun0: IPCP: deflink: State change Initial --> Closed tun0: IPCP: deflink: LayerStart. tun0: IPCP: deflink: SendConfigReq(1) state = Closed tun0: IPCP: IPADDR[6] 0.0.0.0 tun0: IPCP: COMPPROTO[6] 16 VJ slots with slot compression tun0: Debug: fsm_Output tun0: Debug: 01 01 00 10 03 06 00 00 00 00 02 06 00 2d 0f 01 .............-.. tun0: Debug: proto_LayerPush: Using 0x8021 tun0: Debug: link_PushPacket: Transmit proto 0x8021 tun0: Debug: m_enqueue: len = 3 tun0: IPCP: deflink: State change Closed --> Req-Sent tun0: Error: DoLoop: select(): Bad file descriptor tun0: Debug: DoLoop done. tun0: Phase: PPP Terminated (normal). tun0: IPCP: deflink: SendTerminateReq(1) state = Req-Sent tun0: Debug: fsm_Output tun0: Debug: 05 01 00 04 .... tun0: Debug: proto_LayerPush: Using 0x8021 tun0: Debug: m_enqueue: len = 4 Boris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message