From owner-freebsd-isdn@FreeBSD.ORG Sun Jun 5 19:54:50 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 A6BF016A41C for ; Sun, 5 Jun 2005 19:54:50 +0000 (GMT) (envelope-from Thomas.Wintergerst@nord-com.net) Received: from mail3.ewetel.de (mail3.ewetel.de [212.6.122.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EBC643D48 for ; Sun, 5 Jun 2005 19:54:49 +0000 (GMT) (envelope-from Thomas.Wintergerst@nord-com.net) Received: from kalak.lemur.nord.de (dialin-80-228-49-166.ewe-ip-backbone.de [80.228.49.166]) by mail3.ewetel.de (8.12.1/8.12.9) with ESMTP id j55JsbAH017426; Sun, 5 Jun 2005 21:54:39 +0200 (MEST) Received: from [192.168.2.4] (lullog.lemur.nord.de [192.168.2.4]) by kalak.lemur.nord.de (8.12.3/8.12.3) with ESMTP id j53GHXGG001949; Fri, 3 Jun 2005 18:17:33 +0200 (CEST) (envelope-from Thomas.Wintergerst@nord-com.net) Message-ID: <42A0829D.3090704@nord-com.net> Date: Fri, 03 Jun 2005 18:17:33 +0200 From: Thomas Wintergerst User-Agent: Mozilla Thunderbird 0.9 (X11/20041220) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-isdn@freebsd.org References: <20050526202222.E2BD81EAE291@alice.turbocat.de> <20050527140607.GA41449@minerva.krx.nl> <200505281534.58499.hselasky@c2i.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CheckCompat: OK Cc: Steven Looman Subject: Re: Asterisk on FreeBSD + ISDN BRI X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: twinterg@gmx.de List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 19:54:50 -0000 Hello Jussi, Juha-Matti Liukkonen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 28.5.2005, at 16.34, Hans Petter Selasky wrote: > >> I know that Windows uses CAPI to support ISDN devices, but the >> problem there >> is that only one ISDN device is allowed at a time. So can CAPI handle >> more >> than one physical device per CAPI interface (/dev/capi20) ? > > > The CAPI specs (www.capi.org), part 2 section 8.5 (unix interface), > which is obviously written with Solaris in mind, says: > > "COMMON-ISDN-API's device name is /dev/capi20. To allow multiple access > by different UNIX processes, > the device is realized as a clone streams device." > > In the same section the CAPI_GET_PROFILE operation is defined to return > a 16-bit unsigned value for number of supported controllers. So > multiple clients for multiple controllers is possible, unless the > implementation somehow restricts it. Small correction: The message parameter CID is divided into an NCCI, a PLCI and a controller part. The controller part has 8 bits, the msb beeing a flag for addressing a headset. That delivers 127 usable controllers, each with 2 or 30 B-channels. I think, that is currently enough for existing machines. And the hint for a "clone device" should rather address the possiblilty to allow multiple applications CAPI access. The controllers themselves are all addressed by an application through the single device entry "/dev/capi20". > >>> On 27.5.2005, at 17.06, Steven Looman wrote: >>> >>>> The ability to use CAPI with cheap cards (like in Windows for >>>> example) sounds >>>> great as it would be easier to write multiplatform applications. >>>> >> >> I don't think that CAPI is fit for every situation. Putting things in a >> library on top of "isdnd" is going to be much more powerful than if one >> writes a dedicated CAPI-compatible telephony application? > > > CAPI is a lower-level thing than isdnd; it is more akin to i4b layer 3. > It allows moving call control logic to userspace processes - but more > improtantly, it is sort-of a standard. Which would potentially mean > binary compatibility with some lunix apps. Ack. Using CAPI one can use (nearly) all ISDN features. Other APIs mostly have some restrictions. But this flexibility also makes some things a little bit complicated (no example here ;-) ). [...] -- Regards, Thomas Wintergerst