Fork of https://github.com/marschap/isdn4k-utils as well as custom CVS import with proper author name/email ('cvsimport' branch)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Karsten Keil a3dffde8f1 Some CAPI implementations do not accept 0 for MaxLogicalConnection or 13 years ago
FAQ Version 2.0.103 17 years ago
Mini-FAQ General updates 22 years ago
act2000 Small fixes to avoid warnings with newer gcc 16 years ago
ant-phone initial cvs import of ant-phone v0.1.12, http://www.antcom.de/ant-phone/ 17 years ago
areacode areacode.dat Version 2.0.3 24 years ago
avmb1 CVS should not be part of .cvsignore 18 years ago
capi20 newer gcc do not include stdlib.h by default (needed for size_t) 15 years ago
capi20.new Force fritzbox buffer address to be zero 14 years ago
capifax Correct output when checking for global configuration of libcapi20. 16 years ago
capiinfo Some CAPI implementations do not accept 0 for MaxLogicalConnection or 13 years ago
capiinit Newer generated files. 18 years ago
divertctrl First changes to compile utils without /usr/src/linux/drivers/isdn 21 years ago
doc * have a seperate config directory for firmware 18 years ago
eicon * have a seperate config directory for firmware 18 years ago
etc More changes to compile without kernel source 21 years ago
eurofile Small fixes to avoid warnings with newer gcc 16 years ago
hisax make GCC4 happy 17 years ago
icn Small fixes to avoid warnings with newer gcc 16 years ago
imon First changes to compile utils without /usr/src/linux/drivers/isdn 21 years ago
imontty - fix library directories 14 years ago
ipppcomp Fix warning for 2.4 and MODUL_LICENSE 21 years ago
ipppd - fix library directories 14 years ago
ipppstats First changes to compile utils without /usr/src/linux/drivers/isdn 21 years ago
iprofd More changes to compile without kernel source 21 years ago
isdnctrl * have a seperate config directory for firmware 18 years ago
isdnlog Numerous corrections from Jochen Frieling 14 years ago
lib - replaced prototype for basename() by #include <libgen.h> 16 years ago
loop Small fixes to avoid warnings with newer gcc 16 years ago
pcbit * have a seperate config directory for firmware 18 years ago
pppdcapiplugin - fix library directories 14 years ago
rcapid Newer generated files. 18 years ago
scripts * have a seperate config directory for firmware 18 years ago
ttyId Added distclean target so that "make distclean" from top level directory 22 years ago
vbox -fix build with additional CFLAGS on commandline 14 years ago
vbox3 secfix for vbox3 18 years ago
xisdnload fix bufferoverflow 17 years ago
xmonisdn - fix library directories 14 years ago
.config.rpm Added spec-file and sample-config for RPM. 24 years ago
COPYING New CVS tree 26 years ago
LEGAL.ipppcomp might be important for distributors in the U.S. 23 years ago
Makefile - bump versione to 3.13 14 years ago
NEWS Added last changes of eiconctrl. 23 years ago
README remove telesctrl 23 years ago
distexclude Add .cvsignore 23 years ago
isdn4k-utils.spec Added spec-file and sample-config for RPM. 24 years ago

README

#
# $Id$
#
This is the README file for the "isdn4k-utils" package from "The i4l-crew".

This package contains the following stuff:

1. Runtime configuration tools:
isdnctrl, general link-level setup utility.
iprofd, daemon for realizing AT&W0 on ttyI's.
icnctrl, setup utility for the icn driver.
hisaxctrl, setup utility for the HiSax driver.
pcbitctl, setup utility for the pcbit driver.
avmcapictrl setup utility for the avmb1 driver.
actctrl setup utility for the act2000 driver.
eiconctrl setup utility for the eicon driver.
divertctrl setup utility for dss1 diversion services

2. Tools for monitoring activity:
imon, a ncurses based utility for monitoring ISDN-activities.
imontty, a tty based utility for monitoring ISDN-activities.
isdnlog, a set of utilities for connection logging.
ipppstats a utility for showing syncPPP statistics.
xisdnload, an xload-like meter.
xmonisdn, a utility for monitoring and controlling ISDN-activity.
isdnmon, a Tcl/Tk based utility for monitoring ISDN-activities.

3. Applications:
vbox, an answering machine/voice mailbox.
ipppd, daemon need for syncPPP and MPP.

4. Miscellaneous:
scripts/makedev.sh for creating the ISDN device files under /dev .

5. Documentation:
A very detailed FAQ and the generic manpages ttyI.4, isdninfo.4,
isdn_audio.4 and isdn_cause.7.
Manpages for the above utilities:
actctrl.8 avmcapictrl.8, hisaxctrl.8 icnctrl.8, eiconctrl.8, imon.8, ipppd.8,
ipppstats.8, iprofd.8, isdnctrl.8, isdnlog.8, isdnrep.1,
isdnrate.1, rate-files.5, xisdnload.1x and xmonisdn.1x

IMPORTANT:
This will be the last release of isdn4k-utils as is. From now
(February 2000) on, the package will be splitted into the
following packages:

base: common configuration tools and Documentation
isdnlog: D-Channel logging, charge calculation etc.
audio: the answering machine vbox
additional: ipppcomp ipppstats iprofd xisdnload xmonisdn

hardware-dependent packages:
hisax: tools for passive isdn cards
avmb1: tools for the AVM B1/T1/M1/M2 *active* cards
(not for Fritz!classic, Fritz!pnp, Fritz!PCI, these are in hisax)
act2000: tools for IBM Active 2000
eicon: tools for Eicon.Diehl *active* cards
icn: tools for ICN 2B and 4B
pcbit: tools for PCBIT-D
loop: tools for the loopback isdn device

These packages will appear on ftp.isdn4linux.de when they are ready.

COPYRIGHT/COPYING:

Until explicitely stated, all programs in this package can be freely
redistributed and/or modified under the terms of the GNU General
Public License as published by the Free Software Foundation; either
version 2, or (at your option) any later version.

This package is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details. (File: COPYING)

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.


System prerequisites:

To use this package, you need a kernel with an ISDN-subsystem configured.
To get a such a kernel, take a clean standard-kernel (Version > 2.0.37 or
> 2.2.14 resp.) enable the isdn-related features you want and build the
kernel as usual. Older kernels may work as well, but bugs have been found
and fixed, so better use the recommended versions (or above)

3. Configuration, Compilation.

Run "make config"

This will run an interactive configuration tool and the various
configuration-scripts for each sub-package. (You may know that
tool from kernel menuconfig.)
There is a global configuration directory, where most programs
expect their configuration files. The default is /etc/isdn.

- Alternatively you can edit the .config file by hand (once that
has been created once with "make config"), and run "make subconfig"
instead. This might be useful if you want to automate the building
of the package, e.g. for a Red Hat rpm or a Debian deb.

Run "make"

This builds all previously selected utilities.

4. Installation

For the following steps, root permissions are necessary

Install the utilities, the man pages and config-files:

make install

The config files usually are installed in /etc/isdn if not
specified otherwise during configuration.

If no existing ISDN devices in /dev are detected (via an admittedly
simple test), script/makedev.sh is run during "make install". Check
that the permissions / groups are suitable for your needs.
You can run the makedev.sh script again if necessary.

5. Application

The directory ./etc contains an example startup-script which gets
not installed automatically, because it MUST BE CONFIGURED IN ANY
CASE! Please don't try to connect to the Internet without setting
your own IP-addresses. This script is intended to be used with
the modularised version of the ISDN-subsystem. Refer to the
Documentation/isdn subdirectory of your kernel-source-tree for
more information on configuring Lowlevel drivers.

For the utilities refer to the man pages or look into their
subdirectories for Documentation.

For tips, troubleshooting etc. look into the FAQ subdirectory.

-Fritz