From owner-freebsd-isdn@FreeBSD.ORG Thu Feb 14 23:27:26 2008 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12A6116A419 for ; Thu, 14 Feb 2008 23:27:26 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.swipnet.se [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id A79F913C4D1 for ; Thu, 14 Feb 2008 23:27:24 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [85.19.218.18] (account mc467741@c2i.net [85.19.218.18] verified) by mailfe11.swip.net (CommuniGate Pro SMTP 5.1.13) with ESMTPA id 636314132 for freebsd-isdn@freebsd.org; Fri, 15 Feb 2008 00:27:23 +0100 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org User-Agent: KMail/1.9.7 References: <474EE92C.3000406@merlin-home.dtdns.net> <4753132E.1060800@ovb.ch> <200712030046.19953.hm@kts.org> In-Reply-To: <200712030046.19953.hm@kts.org> MIME-Version: 1.0 Content-Disposition: inline Date: Fri, 15 Feb 2008 00:28:19 +0100 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200802150028.20411.hselasky@c2i.net> Subject: Re: Support of ISDN Subsystem under Freebsd 6.x/7.x - amd64 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, 14 Feb 2008 23:27:26 -0000 Hi, > Maybe we should continue this discussion after Christmas? I have been thinking a little bit and I believe that ISDN4BSD will become more IP-based in the future. ISDN4BSD already puts all data into so called "mbufs" which are used to hold IP-packets. Internally ISDN4BSD could possibly use the IP stack when briding a call, because then it will become possible that the sound can be routed directly to the physical piece of hardware that is handling a call, instead of routing everything into userland, through Asterisk for example, and then back again into the kernel. Of course this might mean that we have to put some voice codecs into the kernel, but I think that support for A-law and u-law will be sufficent for a while. Maybe each ISDN adapter should allocate a network adapter for itself and then feed all D-channel and B-channel data into the kernel through IPv4 or IPv6 UDP frames to a programable IP-address. Then if you have a firewall loaded in the kernel, routing those IP-packets somewhere else can be a piece of cake. This also brings up some interesting questions like that the DSS1 protocol becomes a UDP client in the kernel. Then you can actually run the DSS1 protocol on a different machine than the one where the ISDN cable is physically connected. Any comments ? --HPS