Date: Thu, 14 Jul 2005 22:59:26 +0200 From: Thomas Wintergerst <Thomas.Wintergerst@nord-com.net> To: hselasky@c2i.net Cc: freebsd-isdn@freebsd.org Subject: Re: Problem with C4B on FreeBSD-Stable Message-ID: <42D6D22E.9010202@nord-com.net> In-Reply-To: <200506210044.00616.hselasky@c2i.net> References: <7112CBFA-724E-4846-AA2E-1EFBC4B49CE2@cian.ws> <BD18D7E5-79CC-41B5-9755-6D31C5286CA9@cian.ws> <42B53878.2020407@nord-com.net> <200506210044.00616.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42D6D22E.9010202>