From owner-freebsd-isdn@FreeBSD.ORG Wed Oct 26 15:16:42 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 25DFC16A41F for ; Wed, 26 Oct 2005 15:16:42 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 938C943D5F for ; Wed, 26 Oct 2005 15:16:40 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-36-246.daxnet.no ([193.217.36.246] verified) by mailfe05.swip.net (CommuniGate Pro SMTP 4.3.8) with ESMTP id 11008859; Wed, 26 Oct 2005 17:16:38 +0200 From: Hans Petter Selasky To: Cian Hughes Date: Wed, 26 Oct 2005 17:17:43 +0200 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200510261717.44769.hselasky@c2i.net> Cc: freebsd-isdn@freebsd.org Subject: Re: ISDN Drivers on FreeBSD 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, 26 Oct 2005 15:16:42 -0000 On Monday 24 October 2005 10:06, Cian Hughes wrote: > Hey, to be bluntly honest I'm confused as to what to use next with > regards to ISDN drivers for my AVM B1 PCI v4, basically, I currently > use C4B and it works well with Asterisk, however I'm building a new 7- > Current Box at the moment, which I will move the card into when I'm > finished, which set of drivers, system, whatever is: > being most actively developed? > most mature? > least processor intensive? I think I can say that my implementation of CAPI 2.0, and the so called "CMSG" structure, is at least 50% faster, with regard to zeroing of memory, than the "liblinuxcapi" implementation. "liblinuxcapi" is required by C4B when one is using "chan_capi" and Asterisk. "liblinuxcapi" will zero some 300 bytes per message, while I zero around 170. I have optimized this to 0 bytes for certain messages, like DATA_B3_IND/REQ. > > If I use this new I4B fork, will I in effect go from CAPI to I4b > internals and back through a CAPI emulation layer to asterisk, or is > it smarter than that? My ISDN driver does not yet support active CAPI controllers. But the idea is that all signals are decoded into a set of common signals, that are then decoded to I4B and CAPI 2.0. This makes adding more application interfaces easier. +---- /dev/i4b [D-channel] ---- > [common signals] --+ +---- /dev/capi20 So you might have to buy a new "HFC-S PCI A ISDN" card to be able to use my ISDN driver, or some other passive ISDN device that is supported. --HPS