Date: Wed, 2 Oct 1996 08:16:20 +0200 (MET DST) From: hm@kts.org (Hellmuth Michaelis) To: michaelh@cet.co.jp (Michael Hancock) Cc: terry@lambert.org, phk@critter.tfs.com, hackers@FreeBSD.org Subject: Re: isdn code Message-ID: <m0v8KbU-000009C@ernie.kts.org> In-Reply-To: <Pine.SV4.3.93.961002090602.1243A-100000@parkplace.cet.co.jp> from "Michael Hancock" at Oct 2, 96 09:14:58 am
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
First of all, i'm talking about bisdn, not about the stuff which is currently
in the sourcetree, which is in my opinion really unsupported.
The stuff which is in the sourcetree is ii-0.1 which has been replaced by
its authors by ii-0.2. bisdn has its origins in ii-0.2, but it is much more
powerful and does actually work.
Michael Hancock wrote:
> Or you can look at it as not strongly supporting a broader audience. For
> example, most of the major vendors support multiple international
> interfaces. It's should just be a configuration option, select
>
> ATT, NT, NTT, EuroISDN, etc.
>
> The communications gurus tell me that it really isn't that difficult to
> provide support the for various interfaces.
It would be very very nice, if bisdn could support ATT, NT and NTT besides
DSS1 (EuroISDN) and 1TR6 which it currently supports, but _someone_ with
access to communications equipment talking that protocol dialects has to
actually implement support for that.
It cannot be done in Europe without ISDN simulators noone of us has access
to. As much as i would like to do it.
hellmuth
--
Hellmuth Michaelis hm@kts.org Hamburg, Europe
(A)bort, (R)etry, (I)nstall BSD ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0v8KbU-000009C>