From owner-freebsd-isdn@FreeBSD.ORG Mon Jul 11 11:02:12 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 2A57416A422 for ; Mon, 11 Jul 2005 11:02:12 +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 3593C43D5E for ; Mon, 11 Jul 2005 11:02:10 +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 j6BB2APH011472 for ; Mon, 11 Jul 2005 11:02:10 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j6BB29Ar011466 for freebsd-isdn@freebsd.org; Mon, 11 Jul 2005 11:02:09 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 11 Jul 2005 11:02:09 GMT Message-Id: <200507111102.j6BB29Ar011466@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, 11 Jul 2005 11:02:12 -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 i4b itjc bad enums for PIB cycle time 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 Mon Jul 11 22:12:52 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 9738616A41C; Mon, 11 Jul 2005 22:12:52 +0000 (GMT) (envelope-from ifrufnlnavt@hushmail.com) Received: from fastermail-com.mr.outblaze.com (AReims-151-1-19-11.w83-192.abo.wanadoo.fr [83.192.145.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21B4643D5D; Mon, 11 Jul 2005 22:12:45 +0000 (GMT) (envelope-from ifrufnlnavt@hushmail.com) message-id: <002901c58665$b06f7300$675d97f0@MZBEGYC> From: "Dennis" To: Date: Mon, 11 Jul 2005 18:12:55 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.1830 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830 Subject: R0LEX REPLICA - GET N0TICED! 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, 11 Jul 2005 22:12:52 -0000 Get the Finest Rolex Watch Replica ! http://www.newprestigewatchez.com We only sell premium watches. There's no battery in these replicas just like the real ones since they charge themselves as you move. The second hand moves JUST like the real ones, too. These original watches sell in stores for thousands of dollars. We sell them for much less. - Replicated to the Smallest Detail - 98% Perfectly Accurate Markings - Signature Green Sticker w/ Serial Number on Watch Back - Magnified Quickset Date - Includes all Proper Markings http://www.newprestigewatchez.com We also carry all top quality Louis Vuitton handbags! To be taken off just visit http://www.newprestigewatchez.com and click the unsc link From owner-freebsd-isdn@FreeBSD.ORG Thu Jul 14 21:18:16 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 22A3F16A41F for ; Thu, 14 Jul 2005 21:18:16 +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 6BDE443D4C for ; Thu, 14 Jul 2005 21:18:15 +0000 (GMT) (envelope-from Thomas.Wintergerst@nord-com.net) Received: from kalak.lemuria.local (dialin-80-228-50-001.ewe-ip-backbone.de [80.228.50.1]) by mail3.ewetel.de (8.12.1/8.12.9) with ESMTP id j6ELI6EB023612; Thu, 14 Jul 2005 23:18:11 +0200 (MEST) Received: from [192.168.2.4] (lullog.lemuria.local [192.168.2.4]) by kalak.lemuria.local (8.13.3/8.13.3) with ESMTP id j6EKxQ0n005782; Thu, 14 Jul 2005 22:59:26 +0200 (CEST) (envelope-from Thomas.Wintergerst@nord-com.net) Message-ID: <42D6D22E.9010202@nord-com.net> Date: Thu, 14 Jul 2005 22:59:26 +0200 From: Thomas Wintergerst User-Agent: Mozilla Thunderbird 0.9 (X11/20041220) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hselasky@c2i.net References: <7112CBFA-724E-4846-AA2E-1EFBC4B49CE2@cian.ws> <42B53878.2020407@nord-com.net> <200506210044.00616.hselasky@c2i.net> In-Reply-To: <200506210044.00616.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-CheckCompat: OK Cc: freebsd-isdn@freebsd.org Subject: Re: Problem with C4B on FreeBSD-Stable 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: Thu, 14 Jul 2005 21:18:16 -0000 Hi Hans Petter, Hans Petter Selasky wrote: > On Sunday 19 June 2005 11:18, Thomas Wintergerst wrote: > [...] > Another problem is that C4B does not support passive devices. > > The way CAPI is designed there cannot be more than one CAPI interface. So one > CAPI interface for passive cards and one for active cards, is not going to > work! The only solution I see is that one upgrades the I4B layer to support > the features required, e.g. overlap-sending, and then puts a CAPI layer on > top of that. If this is done right, not so many features are lost. And maybe > there will be features provided by I4B that CAPI doesn't provide. First you are right, there is only one CAPI interface. But over this interface you can address multiple controllers. On M$ systems there is only one CAPI-DLL and this DLL is manufacturer specific. So only boards from one manufacturer can be installed in one machine. To avoid that c4b has a CAPI manager that performs message dispatching between applications and and controller drivers. And one can even install drivers from multiple manufacturers or board types. Using this mechanism one could use the single interface to address both active and passive boards. The only thing currently missing is a CAPI driver for passive boards. Maybe your i4b-CAPI driver could register its passive controllers at the CAPI manager. Then all applications like Asterisk could use any controller type through a single interface specification. -- Gruss, Thomas Wintergerst From owner-freebsd-isdn@FreeBSD.ORG Thu Jul 14 23:04:27 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 1FA6A16A44A for ; Thu, 14 Jul 2005 23:04:27 +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 8A47543D49 for ; Thu, 14 Jul 2005 23:04:26 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== Received: from mp-217-233-211.daxnet.no ([193.217.233.211] verified) by mailfe06.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 414116316; Fri, 15 Jul 2005 01:04:24 +0200 From: Hans Petter Selasky To: twinterg@gmx.de Date: Fri, 15 Jul 2005 01:05:15 +0200 User-Agent: KMail/1.7 References: <7112CBFA-724E-4846-AA2E-1EFBC4B49CE2@cian.ws> <200506210044.00616.hselasky@c2i.net> <42D6D22E.9010202@nord-com.net> In-Reply-To: <42D6D22E.9010202@nord-com.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507150105.17378.hselasky@c2i.net> Cc: freebsd-isdn@freebsd.org Subject: Re: Problem with C4B on FreeBSD-Stable 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: Thu, 14 Jul 2005 23:04:27 -0000 On Thursday 14 July 2005 22:59, Thomas Wintergerst wrote: > Hi Hans Petter, > > Hans Petter Selasky wrote: > > On Sunday 19 June 2005 11:18, Thomas Wintergerst wrote: > > [...] > > Maybe your i4b-CAPI driver could register its > passive controllers at the CAPI manager. Then all applications like > Asterisk could use any controller type through a single interface > specification. I'll have to take a closer look at C4B before I can say if this is possible. There are some problems like that "i4bcapimgr" must be disabled for passive devices, hence these devices are already sending signals to /dev/i4b. My model is like this: Active <-->-+ +- /dev/i4b + ---- common ----+ Passive <-->-+ +- /dev/capi20 Thomas' model is like this: (x) <--> + +- /dev/i4b + ---- common ----+ Passive <--> + +- /dev/capi20 --+ +- /dev/capi20 Active <--> (x) ---- direct ---- --+ (x) i4bcapimgr I thought that active CAPI controllers could register under I4B using the following functions: i4b_controller_allocate i4b_controller_free i4b_controller_attach i4b_controller_detach Then we upgrade "i4bcapimgr" so that functionality is not lost. This will mean introduction of new signals. All information is transferred through the call descriptor structure (see struct call_desc), which must be extended. Sometimes information will be stored in a CAPI friendly fashion, and other times I4B friendly. Because later we might add fax/modem emulators and other protocols that run between "Layer 1" and what I call "Layer 5", and if the CAPI firmware does not support that, there is no way that the CAPI interface can support those protocols, if we use a direct CAPI to CAPI bridge. But how is performance related NCCI/PLCI lookup. Do you have to do a linear search each time you receive a data-b3-indication to decide to which "/dev/capi20.XX" the frame should go? --HPS