From owner-freebsd-isdn@FreeBSD.ORG Sun Aug 14 08:28:38 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E80316A41F for ; Sun, 14 Aug 2005 08:28:38 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A588C43D45 for ; Sun, 14 Aug 2005 08:28:37 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from fwd21.aul.t-online.de by mailout06.sul.t-online.com with smtp id 1E4Dr9-0001JZ-00; Sun, 14 Aug 2005 10:28:35 +0200 Received: from fw.reifenberger.com (r1nJcwZvQeDFTdKpfASxLbuDcOyOFdQZgsvIxaw2gWO3BrHO5sYw41@[84.152.84.81]) by fwd21.sul.t-online.de with esmtp id 1E4Dqv-0N3dGi0; Sun, 14 Aug 2005 10:28:21 +0200 Received: from localhost (mike@localhost) by fw.reifenberger.com (8.13.3/8.13.3/Submit) with ESMTP id j7E8RP2Y098562; Sun, 14 Aug 2005 10:27:25 +0200 (CEST) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike owned process doing -bs Date: Sun, 14 Aug 2005 10:27:25 +0200 (CEST) From: Michael Reifenberger To: Hans Petter Selasky In-Reply-To: <200508121816.51020.hselasky@c2i.net> Message-ID: <20050814100345.H98474@fw.reifenberger.com> References: <20050812143625.86D8C1177E@bert.int.kts.org> <200508121816.51020.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ID: r1nJcwZvQeDFTdKpfASxLbuDcOyOFdQZgsvIxaw2gWO3BrHO5sYw41@t-dialin.net X-TOI-MSGID: 46f475a4-d5d6-4f97-8bdd-32299bc855ad Cc: freebsd-isdn@freebsd.org Subject: Re: New ISDN driver X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 08:28:38 -0000 On Fri, 12 Aug 2005, Hans Petter Selasky wrote: > Date: Fri, 12 Aug 2005 18:16:49 +0200 > From: Hans Petter Selasky > To: freebsd-isdn@freebsd.org, hellmuth.michaelis@t-online.de > Subject: Re: New ISDN driver > > On Friday 12 August 2005 16:36, Hellmuth Michaelis wrote: >> Michael Reifenberger wrote: >>> So now we have stock I4B, your I4B and C4B. >>> >>> Has there been any effords to merge the whole lot (at least) into >>> -current? >> >> With regards to Hans Petters ISDN driver: >> >> There are for shure some parts of Hans Petters driver which fix bugs and/or >> enhance i4b and therefore should be integrated into i4b. >> If one compares the current I4B and yours: - Is the new one running GIANT free? - Does it support all current drivers or are some missing? - Is NETGRAPH (i4bing) supported/testet (just necessary for me)? - Is your CAPI implementation integratable with C4B? Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting Comp: Michael.Reifenberger@plaut.de | Priv: Michael@Reifenberger.com http://www.plaut.de | http://www.Reifenberger.com From owner-freebsd-isdn@FreeBSD.ORG Sun Aug 14 15:32:00 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C0D016A41F for ; Sun, 14 Aug 2005 15:32:00 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe16.swip.net [212.247.155.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4584643D49 for ; Sun, 14 Aug 2005 15:31:58 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== Received: from mp-217-233-125.daxnet.no ([193.217.233.125] verified) by mailfe16.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 7246199; Sun, 14 Aug 2005 17:31:55 +0200 From: Hans Petter Selasky To: Michael Reifenberger Date: Sun, 14 Aug 2005 17:32:51 +0200 User-Agent: KMail/1.7 References: <20050812143625.86D8C1177E@bert.int.kts.org> <200508121816.51020.hselasky@c2i.net> <20050814100345.H98474@fw.reifenberger.com> In-Reply-To: <20050814100345.H98474@fw.reifenberger.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200508141732.53167.hselasky@c2i.net> Cc: freebsd-isdn@freebsd.org Subject: Re: New ISDN driver X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 15:32:00 -0000 On Sunday 14 August 2005 10:27, Michael Reifenberger wrote: > On Fri, 12 Aug 2005, Hans Petter Selasky wrote: > > Date: Fri, 12 Aug 2005 18:16:49 +0200 > > From: Hans Petter Selasky > > To: freebsd-isdn@freebsd.org, hellmuth.michaelis@t-online.de > > Subject: Re: New ISDN driver > > > > On Friday 12 August 2005 16:36, Hellmuth Michaelis wrote: > >> Michael Reifenberger wrote: > >>> So now we have stock I4B, your I4B and C4B. > >>> > >>> Has there been any effords to merge the whole lot (at least) into > >>> -current? > >> > >> With regards to Hans Petters ISDN driver: > >> > >> There are for shure some parts of Hans Petters driver which fix bugs > >> and/or enhance i4b and therefore should be integrated into i4b. > > If one compares the current I4B and yours: > - Is the new one running GIANT free? Yes, everything. Currently there is one lock per i4b controller, and I don'= t=20 think it makes sense to have finer granularity than that. > - Does it support all current drivers or are some missing? I found out that NetBSD has some more ISDN drivers than FreeBSD, but if we = are=20 speaking about FreeBSD, everything has been brought into my new system,=20 except what you find in /sys/i4b/layer1/ifpi2 and /sys/i4b/layer1/capi . I= =20 plan to port the ifpi2 driver when I have got some time, but I think that o= ne=20 will be better off buying a new HFC-S PCIA ISDN card or some of the support= ed=20 USB adapters. > - Is NETGRAPH (i4bing) supported/testet (just necessary for me)? i4bing does currently not compile on FreeBSD-7, but it might compile on=20 =46reeBSD 5.4, and I will fix that, hence the Netgraph system has been upda= ted,=20 since I last checked. But the file is there and if you do a one by one line= =20 comparison with the official version, is should not take very long to updat= e=20 it and get it compiling again. But if you just want to set up an IP link,=20 "i4bipr" and "i4bsppp" has been fully tested, and confirmed to work. > - Is your CAPI implementation integratable with C4B? Thomas and I conform to the same CAPI standard, so by putting a layer on to= p=20 of I4B and C4B, that switches messages by controller, it should be possible= =20 to use both systems at the same time. The problem is only that the users wi= ll=20 be confused by all the different controller numbers. So actually it would b= e=20 very nice if C4B could allocate an "i4b controller" and use that controller= =20 number. Here I am referring to my version of I4B. Another thing is the=20 "capi20.h" header files. They are completely different, and maybe someone=20 wants to review which is better, because we cannot have a CAPI system with= =20 two "capi20.h" header files. =46rom what I understand Thomas is not interrested in upgrading I4B or=20 integrating CAPI into I4B, at all. He wants all applications to use CAPI. I= =20 have done a great deal of work to upgrade I4B and I see no problem in=20 extending "i4bcapimgr", which converts CAPI signals into generic I4B signal= s.=20 Then after that, the generic I4B signals are converted into CAPI signals,=20 which means that passive and active cards will follow the same path. Then there is no need for Thomas's kernel CAPI manager. I you want to have= =20 something in the kernel, it is much simpler to write a new B-channel driver= =20 like "/dev/i4btel" than having to implement support for CAPI, register a CA= PI=20 manager and have all those wasted timers and state-machines. I think it will be easier to add new "user interfaces" or "application=20 interfaces", when all signals, no matter where they are coming from, are=20 transformed into some standard signals first, and then sent into the=20 different translators. Currently there are two translators: i4b_capidrv.c a= nd=20 i4b_i4bdrv.c in /sys/i4b/layer4 . Adding a new translator will then be very= =20 easy. I think it is not so smart to design a system to only speak one=20 protocol. Then you get very bound up. From my point of view it is much easi= er=20 to write a protocol translator, than having to port the applications in=20 question. A problem with Thomas' CAPI implementation is that the applications are=20 required to have timers and statemachines to detect missing frames and=20 errors. In my CAPI implementation this is not needed at all. The kernel wil= l=20 keep track of missing signals, and if the system is out of memory, a flag=20 will be set so that error is returned to the application at next read. And= =20 the CAPI library will require that the application is restarted, closing al= l=20 active calls. This flag will only be set if an mbuf used for signalling is= =20 lost. If B-channel mbufs are lost, nothing will happen. The CAPI applicatio= ns=20 I have seen so far does not have any timers checking anything at all and=20 solely rely on the kernel. So therefore I see little use in passing CAPI=20 frames directly from hardware to application. It is best if the kernel does= =20 some processing and checking, and maybe decodes the contents into "struct=20 call_desc" before passing the information to a translator. One thing I have noticed is that some parts of I4B has been copied from Lin= ux.=20 =46or example in the official version of I4B in the file=20 "/sys/i4b/include/i4b_l3l4.h" there is "i4l_driver_bchan_linktab" and=20 "i4l_isdn_bchan_linktab". I am not sure who started I4B, but maybe Hellmuth= =20 can explain why this is like it is? But because it comes from Linux, this i= s=20 no reason we should keep it. So I am actually glad I did such a major=20 rewrite. I have very bad experience copying code, even my own :-) My plan is currently to add E1 support in software and hardware, before=20 Christmas. So maybe we can do some SMP benchmarking then? =2D-HPS From owner-freebsd-isdn@FreeBSD.ORG Sun Aug 14 18:33:33 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB4E216A41F for ; Sun, 14 Aug 2005 18:33:33 +0000 (GMT) (envelope-from hm@kts.org) Received: from mailout08.sul.t-online.com (mailout08.sul.t-online.com [194.25.134.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3381543D45 for ; Sun, 14 Aug 2005 18:33:32 +0000 (GMT) (envelope-from hm@kts.org) Received: from fwd24.aul.t-online.de by mailout08.sul.t-online.com with smtp id 1E4NIY-0005GQ-02; Sun, 14 Aug 2005 20:33:30 +0200 Received: from ernie.int.kts.org (rxH9N2ZlYeQBiBIhszAzGCJhluuemmjXzkO9-Fr9GQ1PmS-dEM-sZz@[84.144.52.14]) by fwd24.sul.t-online.de with esmtp id 1E4NIJ-0B76Yq0; Sun, 14 Aug 2005 20:33:15 +0200 Received: from ernie.int.kts.org ([127.0.0.1]) by localhost (ernie.int.kts.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20335-05; Sun, 14 Aug 2005 20:33:10 +0200 (CEST) Received: from bert.int.kts.org (bert.int.kts.org [172.31.42.2]) by ernie.int.kts.org (Postfix) with ESMTP id BAE65FDAA; Sun, 14 Aug 2005 20:33:08 +0200 (CEST) Received: by bert.int.kts.org (Postfix, from userid 100) id C76FD114D2; Sun, 14 Aug 2005 20:37:38 +0200 (CEST) In-Reply-To: <200508141732.53167.hselasky@c2i.net> To: freebsd-isdn@freebsd.org Date: Sun, 14 Aug 2005 20:37:38 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL119 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20050814183738.C76FD114D2@bert.int.kts.org> From: hm@kts.org (Hellmuth Michaelis) X-Virus-Scanned: by amavisd-new using ClamAV at KTS.ORG X-ID: rxH9N2ZlYeQBiBIhszAzGCJhluuemmjXzkO9-Fr9GQ1PmS-dEM-sZz@t-dialin.net X-TOI-MSGID: 7f405a91-9b88-43d1-b53e-90b158306754 Cc: Subject: Re: New ISDN driver X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hellmuth.michaelis@t-online.de List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 18:33:33 -0000 Hans Petter Selasky wrote: > One thing I have noticed is that some parts of I4B has been copied from Linux. > For example in the official version of I4B in the file > "/sys/i4b/include/i4b_l3l4.h" there is "i4l_driver_bchan_linktab" and > "i4l_isdn_bchan_linktab". I am not sure who started I4B, but maybe Hellmuth > can explain why this is like it is? But because it comes from Linux, this is > no reason we should keep it. So I am actually glad I did such a major > rewrite. I have very bad experience copying code, even my own :-) Just for the record and for the archives: this was my code, this is my code and and this will be my code. The development history is in my code archives. Full stop. Have a nice rest of your life, Hans Petter. It was nice to meet you and an, hmmm, experience for me. hellmuth -- Hellmuth Michaelis mbl +49 (0)160 96455696 secion GmbH fon +49 (0)40 389071-0 Buelowstrasse 20 fax +49 (0)40 389071-19 22763 Hamburg http://www.secion.de/ From owner-freebsd-isdn@FreeBSD.ORG Sun Aug 14 19:24:40 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C670816A41F for ; Sun, 14 Aug 2005 19:24:40 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C5BF43D48 for ; Sun, 14 Aug 2005 19:24:39 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== Received: from mp-217-233-40.daxnet.no ([193.217.233.40] verified) by mailfe08.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 245685910 for freebsd-isdn@freebsd.org; Sun, 14 Aug 2005 21:24:36 +0200 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Sun, 14 Aug 2005 21:25:33 +0200 User-Agent: KMail/1.7 References: <20050812143625.86D8C1177E@bert.int.kts.org> <20050814100345.H98474@fw.reifenberger.com> <200508141732.53167.hselasky@c2i.net> In-Reply-To: <200508141732.53167.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508142125.33718.hselasky@c2i.net> Subject: Re: New ISDN driver X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 19:24:40 -0000 On Sunday 14 August 2005 17:32, Hans Petter Selasky wrote: > On Sunday 14 August 2005 10:27, Michael Reifenberger wrote: > > On Fri, 12 Aug 2005, Hans Petter Selasky wrote: > > > Date: Fri, 12 Aug 2005 18:16:49 +0200 > > > From: Hans Petter Selasky > > > To: freebsd-isdn@freebsd.org, hellmuth.michaelis@t-online.de > > > Subject: Re: New ISDN driver > > > > > > On Friday 12 August 2005 16:36, Hellmuth Michaelis wrote: > > >> Michael Reifenberger wrote: > > >>> So now we have stock I4B, your I4B and C4B. > > >>> > > >>> Has there been any effords to merge the whole lot (at least) into > > >>> -current? > > >> > > >> With regards to Hans Petters ISDN driver: > > >> > > >> There are for shure some parts of Hans Petters driver which fix bugs > > >> and/or enhance i4b and therefore should be integrated into i4b. > > > > If one compares the current I4B and yours: > > - Is the new one running GIANT free? > > Yes, everything. Currently there is one lock per i4b controller, and I > don't think it makes sense to have finer granularity than that. > > > - Does it support all current drivers or are some missing? > > I found out that NetBSD has some more ISDN drivers than FreeBSD, but if we > are speaking about FreeBSD, everything has been brought into my new system, > except what you find in /sys/i4b/layer1/ifpi2 and /sys/i4b/layer1/capi . I > plan to port the ifpi2 driver when I have got some time, but I think that > one will be better off buying a new HFC-S PCIA ISDN card or some of the > supported USB adapters. > > > - Is NETGRAPH (i4bing) supported/testet (just necessary for me)? > > i4bing does currently not compile on FreeBSD-7, but it might compile on > FreeBSD 5.4, and I will fix that, hence the Netgraph system has been > updated, since I last checked. But the file is there and if you do a one by > one line comparison with the official version, is should not take very long > to update it and get it compiling again. But if you just want to set up an > IP link, "i4bipr" and "i4bsppp" has been fully tested, and confirmed to > work. > > > - Is your CAPI implementation integratable with C4B? > > Thomas and I conform to the same CAPI standard, so by putting a layer on > top of I4B and C4B, that switches messages by controller, it should be > possible to use both systems at the same time. The problem is only that the > users will be confused by all the different controller numbers. So actually > it would be very nice if C4B could allocate an "i4b controller" and use > that controller number. Here I am referring to my version of I4B. Another > thing is the "capi20.h" header files. They are completely different, and > maybe someone wants to review which is better, because we cannot have a > CAPI system with two "capi20.h" header files. > > From what I understand Thomas is not interrested in upgrading I4B or > integrating CAPI into I4B, at all. He wants all applications to use CAPI. I > have done a great deal of work to upgrade I4B and I see no problem in > extending "i4bcapimgr", which converts CAPI signals into generic I4B > signals. Then after that, the generic I4B signals are converted into CAPI > signals, which means that passive and active cards will follow the same > path. > > Then there is no need for Thomas's kernel CAPI manager. I you want to have > something in the kernel, it is much simpler to write a new B-channel driver > like "/dev/i4btel" than having to implement support for CAPI, register a > CAPI manager and have all those wasted timers and state-machines. > > I think it will be easier to add new "user interfaces" or "application > interfaces", when all signals, no matter where they are coming from, are > transformed into some standard signals first, and then sent into the > different translators. Currently there are two translators: i4b_capidrv.c > and i4b_i4bdrv.c in /sys/i4b/layer4 . Adding a new translator will then be > very easy. I think it is not so smart to design a system to only speak one > protocol. Then you get very bound up. From my point of view it is much > easier to write a protocol translator, than having to port the applications > in question. > > > A problem with Thomas' CAPI implementation is that the applications are > required to have timers and statemachines to detect missing frames and > errors. In my CAPI implementation this is not needed at all. The kernel > will keep track of missing signals, and if the system is out of memory, a > flag will be set so that error is returned to the application at next read. > And the CAPI library will require that the application is restarted, > closing all active calls. This flag will only be set if an mbuf used for > signalling is lost. If B-channel mbufs are lost, nothing will happen. The > CAPI applications I have seen so far does not have any timers checking > anything at all and solely rely on the kernel. So therefore I see little > use in passing CAPI frames directly from hardware to application. It is > best if the kernel does some processing and checking, and maybe decodes the > contents into "struct call_desc" before passing the information to a > translator. > > > One thing I have noticed is that some parts of I4B has been copied from > Linux. For example in the official version of I4B in the file > "/sys/i4b/include/i4b_l3l4.h" there is "i4l_driver_bchan_linktab" and > "i4l_isdn_bchan_linktab". I am not sure who started I4B, but maybe Hellmuth > can explain why this is like it is? But because it comes from Linux, this > is no reason we should keep it. So I am actually glad I did such a major > rewrite. I have very bad experience copying code, even my own :-) > > > My plan is currently to add E1 support in software and hardware, before > Christmas. So maybe we can do some SMP benchmarking then? I think I have found a serious locking problem in C4B. The function "kcapi_put_message()" uses "sx_xlock()" to protect data. Do you know what that means. This function cannot be called while holding a mutex, neither can it be called from interrupt handlers and timeouts! The reason is that "sx_xlock()" can sleep! And this function is very important, because it is used to receive/transmit all CAPI messages, which is almost everything that is transmitted through "/dev/capi20". This means that one has to create a separate thread that will forward mbufs to "kcapi_put_message()". Simply wasted CPU. Also sx-locks are very depreceated according to "man sx", and "mutexes are inherently more efficient". At the moment there is contention on a "sx" lock, it will sleep, and the kernel is going for a panic or deadlock, if a mutex is held. I suspect there is a reason that Thomas uses an sx-lock, and to change this, maybe the whole of C4B must be redone. Because solving locking problems like this is not very easy. Or is there something I have over-looked ? Any comments ? --HPS From owner-freebsd-isdn@FreeBSD.ORG Sun Aug 14 19:45:04 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2C2D16A41F for ; Sun, 14 Aug 2005 19:45:04 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 342C043D46 for ; Sun, 14 Aug 2005 19:45:03 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== Received: from mp-217-198-105.daxnet.no ([193.217.198.105] verified) by mailfe02.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 429157418 for freebsd-isdn@freebsd.org; Sun, 14 Aug 2005 21:45:01 +0200 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Sun, 14 Aug 2005 21:45:58 +0200 User-Agent: KMail/1.7 References: <20050814183738.C76FD114D2@bert.int.kts.org> In-Reply-To: <20050814183738.C76FD114D2@bert.int.kts.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508142145.59626.hselasky@c2i.net> Subject: Re: New ISDN driver X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 19:45:04 -0000 On Sunday 14 August 2005 20:37, Hellmuth Michaelis wrote: > Hans Petter Selasky wrote: > > One thing I have noticed is that some parts of I4B has been copied from > > Linux. For example in the official version of I4B in the file > > "/sys/i4b/include/i4b_l3l4.h" there is "i4l_driver_bchan_linktab" and > > "i4l_isdn_bchan_linktab". I am not sure who started I4B, but maybe > > Hellmuth can explain why this is like it is? But because it comes from > > Linux, this is no reason we should keep it. So I am actually glad I did > > such a major rewrite. I have very bad experience copying code, even my > > own :-) Well, doesn't "i4l_" indicate that this came from "ISDN4LINUX" ? --HPS From owner-freebsd-isdn@FreeBSD.ORG Sun Aug 14 19:55:53 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C6D116A41F for ; Sun, 14 Aug 2005 19:55:53 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe10.swipnet.se [212.247.155.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4929A43D48 for ; Sun, 14 Aug 2005 19:55:52 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== Received: from mp-217-232-213.daxnet.no ([193.217.232.213] verified) by mailfe10.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 235895016 for freebsd-isdn@freebsd.org; Sun, 14 Aug 2005 21:55:50 +0200 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Sun, 14 Aug 2005 21:56:48 +0200 User-Agent: KMail/1.7 References: <20050814183738.C76FD114D2@bert.int.kts.org> <200508142145.59626.hselasky@c2i.net> In-Reply-To: <200508142145.59626.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508142156.49403.hselasky@c2i.net> Subject: Re: New ISDN driver X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 19:55:53 -0000 On Sunday 14 August 2005 21:45, Hans Petter Selasky wrote: > On Sunday 14 August 2005 20:37, Hellmuth Michaelis wrote: > > Hans Petter Selasky wrote: > > > One thing I have noticed is that some parts of I4B has been copied from > > > Linux. For example in the official version of I4B in the file > > > "/sys/i4b/include/i4b_l3l4.h" there is "i4l_driver_bchan_linktab" and > > > "i4l_isdn_bchan_linktab". I am not sure who started I4B, but maybe > > > Hellmuth can explain why this is like it is? But because it comes from > > > Linux, this is no reason we should keep it. So I am actually glad I did > > > such a major rewrite. I have very bad experience copying code, even my > > > own :-) > > Well, doesn't "i4l_" indicate that this came from "ISDN4LINUX" ? > > > --HPS > _______________________________________________ > freebsd-isdn@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isdn > To unsubscribe, send any mail to "freebsd-isdn-unsubscribe@freebsd.org" From owner-freebsd-isdn@FreeBSD.ORG Mon Aug 15 11:01:51 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0254016A424 for ; Mon, 15 Aug 2005 11:01:51 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADB0E43D55 for ; Mon, 15 Aug 2005 11:01:50 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7FB1oKt007514 for ; Mon, 15 Aug 2005 11:01:50 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7FB1nTw007508 for freebsd-isdn@freebsd.org; Mon, 15 Aug 2005 11:01:49 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 15 Aug 2005 11:01:49 GMT Message-Id: <200508151101.j7FB1nTw007508@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-isdn@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Aug 2005 11:01:51 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/11/16] bin/73988 isdn ISDN - first dial attempt fails o [2005/01/23] kern/76611 isdn [patch] i4b itjc bad enums for PIB cycle o [2005/03/22] kern/79117 isdn iavc(4) for AVM B1 PCI does not attach 3 problems total. From owner-freebsd-isdn@FreeBSD.ORG Tue Aug 16 16:17:19 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14D5D16A420 for ; Tue, 16 Aug 2005 16:17:19 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.swip.net [212.247.155.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4732B43D55 for ; Tue, 16 Aug 2005 16:17:17 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-232-219.daxnet.no ([193.217.232.219] verified) by mailfe11.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 8088614 for freebsd-isdn@freebsd.org; Tue, 16 Aug 2005 18:17:15 +0200 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Tue, 16 Aug 2005 18:18:07 +0200 User-Agent: KMail/1.7 References: <20050814183738.C76FD114D2@bert.int.kts.org> <200508142145.59626.hselasky@c2i.net> In-Reply-To: <200508142145.59626.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508161818.08934.hselasky@c2i.net> Subject: Re: New ISDN driver X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2005 16:17:19 -0000 On Sunday 14 August 2005 21:45, Hans Petter Selasky wrote: > On Sunday 14 August 2005 20:37, Hellmuth Michaelis wrote: > > Hans Petter Selasky wrote: > > > One thing I have noticed is that some parts of I4B has been copied from > > > Linux. For example in the official version of I4B in the file > > > "/sys/i4b/include/i4b_l3l4.h" there is "i4l_driver_bchan_linktab" and > > > "i4l_isdn_bchan_linktab". I am not sure who started I4B, but maybe > > > Hellmuth can explain why this is like it is? But because it comes from > > > Linux, this is no reason we should keep it. So I am actually glad I did > > > such a major rewrite. I have very bad experience copying code, even my > > > own :-) > > Well, doesn't "i4l_" indicate that this came from "ISDN4LINUX" ? If you "cat" all the files in "/sys/i4b" and search for the word "linux" or "Linux" you will get some hits. So I suspect that some parts of the drivers in "/sys/i4b/layer1" are derivatives of Linux. And I have got some hints about that too. So maybe we should just drop support for some hardware, and stick with the chip-drivers I have written from scratch ? Else we might end up getting a bad rumor about stealing code from Linux. Does anyone have any opinion about what is allowed and what is not allowed ? --HPS From owner-freebsd-isdn@FreeBSD.ORG Tue Aug 16 17:16:08 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5CB116A41F for ; Tue, 16 Aug 2005 17:16:08 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 452B943D48 for ; Tue, 16 Aug 2005 17:16:07 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from fwd17.aul.t-online.de by mailout04.sul.t-online.com with smtp id 1E552k-00078t-05; Tue, 16 Aug 2005 19:16:06 +0200 Received: from fw.reifenberger.com (XR2FEmZUZek7i3x0bBDLKl+O-2ROHlInBwPMhqu7Jx9nF5UYHhFi0W@[84.152.117.93]) by fwd17.sul.t-online.de with esmtp id 1E552a-1g0KsS0; Tue, 16 Aug 2005 19:15:56 +0200 Received: from localhost (mike@localhost) by fw.reifenberger.com (8.13.3/8.13.3/Submit) with ESMTP id j7GHExFB009520; Tue, 16 Aug 2005 19:14:59 +0200 (CEST) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike owned process doing -bs Date: Tue, 16 Aug 2005 19:14:59 +0200 (CEST) From: Michael Reifenberger To: Hans Petter Selasky In-Reply-To: <200508161818.08934.hselasky@c2i.net> Message-ID: <20050816190537.E8652@fw.reifenberger.com> References: <20050814183738.C76FD114D2@bert.int.kts.org> <200508142145.59626.hselasky@c2i.net> <200508161818.08934.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ID: XR2FEmZUZek7i3x0bBDLKl+O-2ROHlInBwPMhqu7Jx9nF5UYHhFi0W@t-dialin.net X-TOI-MSGID: 98fc2749-7f97-4256-b6d5-d9b39426c1bd Cc: freebsd-isdn@freebsd.org Subject: Re: New ISDN driver X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2005 17:16:08 -0000 On Tue, 16 Aug 2005, Hans Petter Selasky wrote: ... >> Well, doesn't "i4l_" indicate that this came from "ISDN4LINUX" ? > > If you "cat" all the files in "/sys/i4b" and search for the word "linux" or > "Linux" you will get some hits. > > So I suspect that some parts of the drivers in "/sys/i4b/layer1" are > derivatives of Linux. And I have got some hints about that too. So maybe we > should just drop support for some hardware, and stick with the chip-drivers I > have written from scratch ? Else we might end up getting a bad rumor about > stealing code from Linux. > The occurance of [Ll]inux or l_* doesnt imply that these files are from linux. /sys/compat/linux/* files are stuffed with these letters. Usually they are for compatibility reasons. So its not reasonable to suspect any I4B files to be linux tainted. Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting Comp: Michael.Reifenberger@plaut.de | Priv: Michael@Reifenberger.com http://www.plaut.de | http://www.Reifenberger.com From owner-freebsd-isdn@FreeBSD.ORG Tue Aug 16 18:14:32 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65DC916A41F for ; Tue, 16 Aug 2005 18:14:32 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (Jb873.j.pppool.de [85.74.184.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD9EF43D45 for ; Tue, 16 Aug 2005 18:14:31 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.4/8.11.6) with ESMTP id j7GIESTv010770; Tue, 16 Aug 2005 20:14:28 +0200 (CEST) (envelope-from garyj@jennejohn.org) Message-Id: <200508161814.j7GIESTv010770@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Michael Reifenberger In-reply-to: Your message of "Tue, 16 Aug 2005 19:14:59 +0200." <20050816190537.E8652@fw.reifenberger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Aug 2005 20:14:28 +0200 From: Gary Jennejohn Cc: freebsd-isdn@freebsd.org Subject: Re: New ISDN driver X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gary Jennejohn List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2005 18:14:32 -0000 Michael Reifenberger writes: > On Tue, 16 Aug 2005, Hans Petter Selasky wrote: > ... > >> Well, doesn't "i4l_" indicate that this came from "ISDN4LINUX" ? > > > > If you "cat" all the files in "/sys/i4b" and search for the word "linux" or > > "Linux" you will get some hits. > > > > So I suspect that some parts of the drivers in "/sys/i4b/layer1" are > > derivatives of Linux. And I have got some hints about that too. So maybe we > > should just drop support for some hardware, and stick with the chip-drivers > I > > have written from scratch ? Else we might end up getting a bad rumor about > > stealing code from Linux. > > > > The occurance of [Ll]inux or l_* doesnt imply that these files are from linux > . > /sys/compat/linux/* files are stuffed with these letters. > Usually they are for compatibility reasons. > So its not reasonable to suspect any I4B files to be linux tainted. > Several drivers were developed after examining the Linux code, which in these cases was the only form of documentation available. AVM in particular is very bad about providing documentation to any developer outside the Linux world! Been there, done that. These drivers (some of which I wrote) are NOT clones of the Linux drivers, so don't try to imply that they are, HPS. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-isdn@FreeBSD.ORG Wed Aug 17 00:00:33 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBA6416A41F for ; Wed, 17 Aug 2005 00:00:33 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5333043D45 for ; Wed, 17 Aug 2005 00:00:32 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-198-105.daxnet.no ([193.217.198.105] verified) by mailfe06.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 433903102 for freebsd-isdn@freebsd.org; Wed, 17 Aug 2005 02:00:30 +0200 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Wed, 17 Aug 2005 02:01:27 +0200 User-Agent: KMail/1.7 References: <200508161814.j7GIESTv010770@peedub.jennejohn.org> In-Reply-To: <200508161814.j7GIESTv010770@peedub.jennejohn.org> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200508170201.28540.hselasky@c2i.net> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: New ISDN driver X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 00:00:34 -0000 On Tuesday 16 August 2005 20:14, Gary Jennejohn wrote: > Michael Reifenberger writes: > > On Tue, 16 Aug 2005, Hans Petter Selasky wrote: > > ... > > > > >> Well, doesn't "i4l_" indicate that this came from "ISDN4LINUX" ? > > > > > > If you "cat" all the files in "/sys/i4b" and search for the word > > > "linux" or "Linux" you will get some hits. > > > > > > So I suspect that some parts of the drivers in "/sys/i4b/layer1" are > > > derivatives of Linux. And I have got some hints about that too. So > > > maybe we should just drop support for some hardware, and stick with the > > > chip-drivers > > > > I > > > > > have written from scratch ? Else we might end up getting a bad rumor > > > about stealing code from Linux. > > > > The occurance of [Ll]inux or l_* doesnt imply that these files are from > > linux . > > /sys/compat/linux/* files are stuffed with these letters. > > Usually they are for compatibility reasons. > > So its not reasonable to suspect any I4B files to be linux tainted. > > Several drivers were developed after examining the Linux code, which > in these cases was the only form of documentation available. AVM in > particular is very bad about providing documentation to any developer > outside the Linux world! Been there, done that. They might be afraid that someone will find problems about their products. For example their B-channel FIFO interface ill fits my system, hence you have to pre-write data lengths, which is a bad idea. Because then one has to pre-walk mbuf chains. But it might be interesting to dissassemble that AVM firmware, and see if it is really solid. I think that we won't have much use for those active AVM controllers in the future. Modern passive E1 chips have many useful features. For example DTMF detection, support for telephony conferences, interconnection of channels, and very large buffers. The only thing these chips haven't got, is a modem emulator, which I think is not very difficult to have in software. Detecting sine waves is not very difficult. One simply puts the waves one wants to detect, into a linear equation set, solves it, and finds the unknown amplitudes. This is something like Fast Fourier Transform, though we cannot use FFT, hence these modem frequencies doesn't fit exactly into "n" samples. So it is not very difficult. There also exist other algorithms to demodulate sine waves, but I think one will get best results with linear equation sets? --HPS From owner-freebsd-isdn@FreeBSD.ORG Thu Aug 18 08:17:15 2005 Return-Path: X-Original-To: isdn@freebsd.org Delivered-To: freebsd-isdn@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 167A716A41F for ; Thu, 18 Aug 2005 08:17:15 +0000 (GMT) (envelope-from phk@phk.freebsd.dk) Received: from haven.freebsd.dk (haven.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id B28C943D48 for ; Thu, 18 Aug 2005 08:17:14 +0000 (GMT) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (unknown [192.168.48.2]) by haven.freebsd.dk (Postfix) with ESMTP id 4F4E3BC66 for ; Thu, 18 Aug 2005 08:17:13 +0000 (UTC) To: isdn@freebsd.org From: Poul-Henning Kamp Date: Thu, 18 Aug 2005 10:17:12 +0200 Message-ID: <22583.1124353032@phk.freebsd.dk> Sender: phk@phk.freebsd.dk Cc: Subject: Auerswald 4410 PBX anyone ? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Aug 2005 08:17:15 -0000 My Euracom PBX died and I'm looking for a replacement. Anyone has any experience with the Auerswald 4410 ? The management software is in java and there is a source code USB driver for Linux so in theory it should be possible to manage it from FreeBSD. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-isdn@FreeBSD.ORG Thu Aug 18 08:40:44 2005 Return-Path: X-Original-To: isdn@freebsd.org Delivered-To: freebsd-isdn@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BD0716A41F for ; Thu, 18 Aug 2005 08:40:44 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20A8743D45 for ; Thu, 18 Aug 2005 08:40:43 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from fwd21.aul.t-online.de by mailout05.sul.t-online.com with smtp id 1E5fx4-0005AA-00; Thu, 18 Aug 2005 10:40:42 +0200 Received: from fw.reifenberger.com (Ze5vpEZvoe-SXxtl8cFYH0HFeJoh4eVQeuxutXk+aawWWs5-Ka2eQe@[84.152.84.137]) by fwd21.sul.t-online.de with esmtp id 1E5fwu-26ymKe0; Thu, 18 Aug 2005 10:40:32 +0200 Received: from localhost (mike@localhost) by fw.reifenberger.com (8.13.3/8.13.3/Submit) with ESMTP id j7I8dYVh017638; Thu, 18 Aug 2005 10:39:34 +0200 (CEST) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike owned process doing -bs Date: Thu, 18 Aug 2005 10:39:34 +0200 (CEST) From: Michael Reifenberger To: Poul-Henning Kamp In-Reply-To: <22583.1124353032@phk.freebsd.dk> Message-ID: <20050818103740.M17628@fw.reifenberger.com> References: <22583.1124353032@phk.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ID: Ze5vpEZvoe-SXxtl8cFYH0HFeJoh4eVQeuxutXk+aawWWs5-Ka2eQe@t-dialin.net X-TOI-MSGID: 9d6b638f-639f-4939-b8ef-4e05b8616ebf Cc: isdn@freebsd.org Subject: Re: Auerswald 4410 PBX anyone ? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Aug 2005 08:40:44 -0000 On Thu, 18 Aug 2005, Poul-Henning Kamp wrote: > Date: Thu, 18 Aug 2005 10:17:12 +0200 > From: Poul-Henning Kamp > To: isdn@freebsd.org > Subject: Auerswald 4410 PBX anyone ? > > > My Euracom PBX died and I'm looking for a replacement. > Or use one of your spare machines stuffed with one or two AVM B1's + C4B + Asterisk?... Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting Comp: Michael.Reifenberger@plaut.de | Priv: Michael@Reifenberger.com http://www.plaut.de | http://www.Reifenberger.com From owner-freebsd-isdn@FreeBSD.ORG Thu Aug 18 08:51:45 2005 Return-Path: X-Original-To: isdn@freebsd.org Delivered-To: freebsd-isdn@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB51816A41F for ; Thu, 18 Aug 2005 08:51:45 +0000 (GMT) (envelope-from phk@phk.freebsd.dk) Received: from haven.freebsd.dk (haven.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73C2143D46 for ; Thu, 18 Aug 2005 08:51:45 +0000 (GMT) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (unknown [192.168.48.2]) by haven.freebsd.dk (Postfix) with ESMTP id 05CCCBC66; Thu, 18 Aug 2005 08:51:43 +0000 (UTC) To: Michael Reifenberger From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 18 Aug 2005 10:39:34 +0200." <20050818103740.M17628@fw.reifenberger.com> Date: Thu, 18 Aug 2005 10:51:43 +0200 Message-ID: <22797.1124355103@phk.freebsd.dk> Sender: phk@phk.freebsd.dk Cc: isdn@freebsd.org Subject: Re: Auerswald 4410 PBX anyone ? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Aug 2005 08:51:45 -0000 In message <20050818103740.M17628@fw.reifenberger.com>, Michael Reifenberger writes: >Or use one of your spare machines stuffed with one or two >AVM B1's + C4B + Asterisk?... I've thought about it, but I'm not ready for it yet. I also think the investment in hardware + power usage makes it a bad deal compared to the auerswald. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.