update misc i4b documentation to i4b release 0.71.00

This commit is contained in:
Hellmuth Michaelis 1999-03-07 17:18:28 +00:00
parent bb7ca167ae
commit 7e18abbef4
3 changed files with 128 additions and 23 deletions

View File

@ -3,7 +3,7 @@
ISDN4BSD Frequently Asked Questions
===================================
last edit-date: [Fri Dec 25 19:59:21 1998]
last edit-date: [Sun Feb 14 12:06:23 1999]
--------------------------------------------------------------------------------
@ -22,6 +22,7 @@ Contents:
9. Why it always says "no Space in TX FIFO - State F4 awaiting" ?
10. Incoming alert - what does it mean ?
11. How do i change irq's on my teles 16.3 card ?
12. NL: i'm getting CAUSE 100 or CAUSE 101 when dialling out
@ -121,6 +122,25 @@ Contents:
B. How to figure out the ISP's IP address
-----------------------------------------
======================================================================
UPDATE NOTE (February 8, 1999):
Jan Riedinger writes:
---------------------
>I further think Gary should mention
>in the FAQ in the section "B. How to figure out the ISP's IP address
>that it isn't normaly necessary to do it because of the auto
>address negotiation.
Gary answers:
-------------
I think you're right. I wrote that stuff before the support for
negotiation of the IPS's address was added to if_spppsubr.c.
======================================================================
I also intentionally configured the interface with the wrong address for
my ISP, like this:
@ -515,3 +535,73 @@ for this card (hint: read "man isic") which is currently unused in your
machine and generate a new kernel.
12. NL: i'm getting CAUSE 100 or CAUSE 101 when dialling out
================================================================================
This one seems to be specific for the Netherlands. (-hm)
Question:
I'm trying to get i4b running on my new FreeBSD 2.2.8 system. The kernel
compiles smootly and everything is looking fine until it's time to dial.
I get the following error:
Feb 10 20:31:00 goofy isdnd[498]: CHD 00018 I4BPPP outgoing call disconnected (remote)
Feb 10 20:31:00 goofy isdnd[498]: CHD 00018 I4BPPP cause 101: Message not compatible with call state (Q.850)
Feb 10 20:31:00 goofy isdnd[498]: ERR set_channel_idle: controller [0], invalid channel [-1]!
Feb 10 20:31:00 goofy isdnd[498]: ERR msg_disconnect_ind: set_channel_idle failed!
The remote site is a Cisco 4000 type router. I used debug to take a view at
the ISDN events on the router but according to that the call doesn't arrive
over there.
Same hardware has worked fine with FreeBSD 2.2.6/i4b 0.63.
Who knows what's wrong?
Answer:
This sounds very much like your local phone number or remote phone number
is configured wrongly... in the Netherlands you need to specify the number
EXCLUDING the city code... so if you live in Utrecht and your number is
0301234567 you specify 1234567.
I have seen this in several locations in the Netherlands for years, not
just with i4b, but also with differentt isdn equipment.. why? guess it
simply depends on which operator defines your line or what exchange it
is connected to... :P
What I found is that what solved this with other isdn hardware/software,
also solves it for i4b.. ie.. make sure the local phone number is
specified, and is specified without the city code.
The numbering plan should be 'unknown'
Anyway, it would be nice if the Dutch ptt (they are called KPN btw)
would tell us why this happens... they havent been able to tell me in the
past so I guess I give up on that, but if everyone finds out whats exactly
happening here I'd be interested to know... :)
List of number configurations that I have found to almost always work in
the Netherlands:
1. Local phone number:
usually your prefered msn without city code works here.
(ie, 1234567 if you would like to use 0201234567 for outgoing calls)
on some locations leaving it blank or defining it with the city code,
but without the leading 0 works as well here.
2. remote phone number:
When this is a 'local' call, don't specify city code.
For calling parties in other cities you of cource have to use the city
code... in general you can say that KPN only accepts the shortest
possible notation where it would still be clear who you want to call.
3. numbers for incomming call recognition:
KPN always specifies incoming caller ids with city code, but without
leading 0. so 0201234567 will be displayed as 201234567
Hope this helps.
Bart
(from Bart van Leeuwen bart@ixori.demon.nl)

View File

@ -1,8 +1,10 @@
Note: This is the README from the isdn4bsd 0.70.00 ftp-distribution. Shortly
after release, i4b was integrated into the FreeBSD sourcetree and so
the following parts about FreeBSD may not apply anymore.
Note: This is the README from the isdn4bsd 0.71.00 ftp-distribution.
In December 1998, i4b was integrated into the FreeBSD sourcetree
and so the following parts about FreeBSD may not apply completely
anymore.
For information of how isdn4bsd is integrated into FreeBSD now, please
read the file ROADMAP in this directory.
@ -13,7 +15,7 @@ Note: This is the README from the isdn4bsd 0.70.00 ftp-distribution. Shortly
ISDN4BSD
========
beta Version 0.70.00 / December 1998
beta Version 0.71.00 / March 1999
written by:
@ -29,7 +31,7 @@ Note: This is the README from the isdn4bsd 0.70.00 ftp-distribution. Shortly
The isdn4bsd package is:
Copyright (c) 1997, 1998 by Hellmuth Michaelis. All rights reserved.
Copyright (c) 1997, 1999 by Hellmuth Michaelis. All rights reserved.
For details see the file LICENSE.
@ -100,7 +102,7 @@ Contents:
---------------------
ISDN4BSD (or in short i4b) is a package for interfacing a computer running
FreeBSD, NetBSD or OpenBSD to the ISDN.
FreeBSD, NetBSD, OpenBSD or BSD/OS to the ISDN.
The only ISDN protocol currently supported is the BRI protocol specified in
I.430, Q.921 and Q.931; better known as DSS1 or Euro-ISDN.
@ -116,19 +118,11 @@ machine.
------------------------------
FreeBSD:
You need FreeBSD 2.2.6 and higher to run i4b out-of-the-box.
I4B was integrated into FreeBSD in January 1999, so it is part
of FreeBSD-current and FreeBSD 3.1 (stable).
This is because PnP support is now available in i4b and
FreeBSD 2.2.6 was the first version which included PnP support
in the base OS.
In case you want to install i4b on FreeBSD < 2.2.6, you have to
patch your system with the PnP patches from Luigi Rizzo (available
from his home page at http://www.iet.unipi.it/~luigi).
The install/uninstall script in the FreeBSD directory was tested
with 2.2.7 (it should run with 2.2.n, where n >= 6), 3.0-RELEASE
and 3.0-CURRENT as of Dec 22, 1998.
FreeBSD 2.2.x is no longer supported by i4b, this release might
still run on 2.2 but upcoming i4b releases will not!
Please take the time to read the file FreeBSD/INSTALLATION (and
the other available documentation) carefully. Thank you!
@ -175,6 +169,11 @@ OpenBSD/i386:
it would be great to have someone who likes to work on i4b under
OpenBSD regularly and takes over the maintenance for that OS!
BSD/OS
The BSD/OS 4.0 specific support was done by Bert Driehuis. The
support is not yet complete. Please contact Bert directly in case
of questions regarding this at bert_driehuis@nl.compuware.com.
4. Which ISDN cards are supported ?
-----------------------------------
@ -209,6 +208,7 @@ OpenBSD/i386:
Type (passive, PnP) FreeBSD NetBSD/OpenBSD Notes
--------------------- ------- -------------- -----------------------
ELSA 1000pro PCI full full
AVM Fritz!Card PCI full unsupported (Note 14)
Type (passive, PCMCIA)FreeBSD NetBSD/OpenBSD Notes
--------------------- ------- -------------- -----------------------
@ -228,9 +228,10 @@ OpenBSD/i386:
Stollmann Tina-dd unsupported unsupported (Note 8)
Note 1: Only the ISA, non-PnP AVM Fritz!Card is supported; the PnP and PCI
versions are unsupported! The "Teledat 150" sold by the german
Telekom seems to be an AVM Fritz!Card.
Note 1: Only the ISA, non-PnP AVM Fritz!Card (also now known as "Fritz!Card
callsic") is supported; the PnP version is unsupported!
The "Teledat 150" sold by the german Telekom seems to be an AVM
Fritz!Card classic.
Note 2: FreeBSD
This is a PnP card. To run it under FreeBSD, you need
@ -285,6 +286,10 @@ Note 12: This driver was developed by Ignatios Souvatzis (is@netbsd.org)
Note 13: This driver was developed by Martin Husemann under NetBSD and has
not been tested under FreeBSD yet. Feedback welcome!
Note 14: This driver was developed by Gary Jennejohn who develops under
FreeBSD only. In case of problems with this driver, please contact
him directly at garyj@muc.de.
5. Where do i find documentation for ISDN4BSD ?
-----------------------------------------------
@ -306,7 +311,7 @@ Note 13: This driver was developed by Martin Husemann under NetBSD and has
- misc/Resources contains URL's and ISBN's to more interesting ISDN related
stuff.
- handbook/i4b.ps is the start of a handbook for isdn4bsd.
- handbook/i4b.ps contains a handbook for isdn4bsd.
6. How do i install ISDN4BSD ?

View File

@ -5,6 +5,12 @@ Doku: Anwahl von T-Offline mittels i4b und FreeBSD (german)
http://www.de.freebsd.org/de/i4b-t-error.html
Doku: PPP mit isdn4bsd (german)
===============================
http://www.saargate.de/~domi/freebsd/i4b-ppp-newbie.html
ISDN Information:
=================
@ -87,4 +93,8 @@ Books:
James Carlson, Addison-Wesley 1998,
ISBN 0-0201-18539-3
"ISDN - Die Technik",
Andreas Kanbach, Andreas Koerber, Huethig Verlag 1999,
ISBN 3-7785-2288-4
-- EOF -----------------------------------------------------------------------