See section config_msn .
Have a look in section hardware .
The new ISDN drivers in 2.0.36 defaults to manual dialmode, not autodial. This is done to prevent unexpected (and unnoticed) dialouts.
To enable autodial for a given interface e.g. ippp0, use
isdnctrl dialmode ippp0 auto
The meaning of the values for dialmode is:
means that you (or the system) cannot make any connection (neither incoming nor outgoing connections are possible). Use this if you want to be sure that no connections will be made.
means that the interface is in auto-dial mode, and will attempt to make a connection whenever a network data packet needs the interface's link. Note that this can cause unexpected dialouts, and lead to a high phone bill! Some daemons or other pc's that use this interface can cause this. Incoming connections are also possible.
(DEFAULT) is a dial mode created to prevent the unexpected dialouts. In this mode, the interface will never make any connections on its own. You must explicitly initiate a connection with:
isdnctrl dial ippp0
huptimeout
may still end the connection
automatically! To ensure that you have to hang up manually, you have to switch
this off:
isdnctrl huptimeout ippp0 0
isdnctrl hangup ippp0
For PCI cards Plug and Play works automatically, they donīt need any manual configuration if the correct card type is provided. ISA PNP cards will require some manual configuration:
pnpdump > /etc/isapnp.conf
/etc/isapnp.conf
has to be set by
hand. Set the following values:
isapnp /etc/isapnp.conf
modprobe hisax io=4,2,INT,IO0,IO1
ISDN usage depends on the permissions to the devices /dev/ttyI*
and
/dev/cui*
. To restrict dialout permissions you can establish the
group `isdn' in /etc/group
, and then do
chgrp isdn /dev/ttyI* /dev/cui* chmod o-rw /dev/ttyI* /dev/cui*
kerneld does not work well with the ISDN modules, since the ISDN modules can not store their status, and could miss important messages on the D channel. Newer versions of i4l ensure that they wonīt be unloaded by kerneld, but you should not try to use kerneld with any version of i4l.
Yes, you can define two different run level for this (under SysVInit) in
/etc/inittab
. One run level includes the ISDN processes, where the
other one does not.
Please note: these link list may be outdated, they have not been checked for a long while.
http://www.rosat.mpe-garching.mpg.de/~web/ISDN.html
http://www.lrz-muenchen.de/~ui161ab/www/isdn/
http://www.sfs.nphil.uni-tuebingen.de/~hipp/isdn/
http://www.provi.de/~gvz/chargeint.html
http://www.techfak.uni-kiel.de/~stn/i4l/
http://fb4-1112.uni-muenster.de/pub/ffwd/
http://www.datenhighway.com/isdn4linux.html
ftp://ftp.franken.de/pub/isdn4linux/
ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ
http://www.rosat.mpe-garching.mpg.de/~web/ISDN.html
http://www.lrz-muenchen.de/~ui161ab/www/isdn/
http://www.fzi.de/sim/people/trautw/i4l/index.html
ftp://ftp.hamburg.pop.de/pap/LOCAL/linux/i4l-eft/