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.
 
 
 
 
 
 
Shaun Ruffell 17027df04b dahdi_scan: Support gaps in channel numbering. 8 years ago
build_tools menuselect: Remove last bits completely from the repo 9 years ago
doc dahdi_cfg: add '-S <spanno>' and '-C <chan-ranges>' 10 years ago
ppp PPP: Fix an incorrect function call that was causing dahdi.so to fail to load 11 years ago
xpp xpp: Fix compile error with fedora 17 8 years ago
LICENSE Import DAHDI-Tools r9159 11 years ago
LICENSE.LGPL Import DAHDI-Tools r9159 11 years ago
Makefile Disable menuselect in dahdi-tools 10 years ago
README menuselect: Remove last bits completely from the repo 9 years ago
UPGRADE.txt README, UPGRADE.txt, system.conf.sample: Add documentation for using HWEC 11 years ago
acinclude.m4 Import DAHDI-Tools r9159 11 years ago
autoconfig.h.in astribank_is_starting: use semop if no semtimedop 11 years ago
bittest.h Import DAHDI-Tools r9159 11 years ago
blacklist.sample blacklist: Add hfcmulti, hfcpci, and netjet. 9 years ago
bootstrap.sh Import DAHDI-Tools r9159 11 years ago
config.guess Import DAHDI-Tools r9159 11 years ago
config.sub Import DAHDI-Tools r9159 11 years ago
configure Disable menuselect in dahdi-tools 10 years ago
configure.ac menuselect: Remove last bits completely from the repo 9 years ago
dahdi.init dahdi.init: LSB short description 11 years ago
dahdi.xml Import DAHDI-Tools r9159 11 years ago
dahdi_cfg.c Fix GCC 4.6 "set but not used" warnings 10 years ago
dahdi_diag.c Import DAHDI-Tools r9159 11 years ago
dahdi_maint.c Fix GCC 4.6 "set but not used" warnings 10 years ago
dahdi_monitor.c dahdi-monitor: Fix broken control-C behavior and -F output option 9 years ago
dahdi_pcap.c dahdi_pcap: Imported user space utility for managing pcap streams 10 years ago
dahdi_scan.c dahdi_scan: Support gaps in channel numbering. 8 years ago
dahdi_speed.c Import DAHDI-Tools r9159 11 years ago
dahdi_test.c dahdi_test: Enforce range from 0.0% - 100.0% for accuracy. 10 years ago
dahdi_tool.c Import DAHDI-Tools r9159 11 years ago
dahdi_tools_version.h Import DAHDI-Tools r9159 11 years ago
fxotune.c Import DAHDI-Tools r9159 11 years ago
fxotune.h Import DAHDI-Tools r9159 11 years ago
fxstest.c Import DAHDI-Tools r9159 11 years ago
hdlcgen.c Import DAHDI-Tools r9159 11 years ago
hdlcstress.c Import DAHDI-Tools r9159 11 years ago
hdlctest.c Import DAHDI-Tools r9159 11 years ago
hdlcverify.c Import DAHDI-Tools r9159 11 years ago
ifup-hdlc Import DAHDI-Tools r9159 11 years ago
init.conf.sample Import DAHDI-Tools r9159 11 years ago
install-sh Import DAHDI-Tools r9159 11 years ago
makeopts.in Disable menuselect in dahdi-tools 10 years ago
modprobe.conf.sample Import DAHDI-Tools r9159 11 years ago
modules.sample Import DAHDI-Tools r9159 11 years ago
patgen.c tools: Allow pattern tools to access channels above the device file limit 10 years ago
patlooptest.c patlooptest: Ignore the first buffered event 10 years ago
pattest.c tools: Allow pattern tools to access channels above the device file limit 10 years ago
sethdlc.c Import DAHDI-Tools r9159 11 years ago
system.conf.sample system.conf.sample: Add note regarding cross connecting spans on B410P. 10 years ago
timertest.c Import DAHDI-Tools r9159 11 years ago
tonezone.c Import DAHDI-Tools r9159 11 years ago
tonezone.h Import DAHDI-Tools r9159 11 years ago
wavformat.h Import DAHDI-Tools r9159 11 years ago
zonedata.c zonedata: Add support for United Arab Emirates. 10 years ago

README

DAHDI Telephony Interface Driver
=================================
Asterisk Development Team <asteriskteam@digium.com>
$Revision$, $Date$

DAHDI stands for Digium Asterisk Hardware Device Interface. This
package contains the user-space tools to configure the kernel modules
included in the package dahdi-linux.

Build Requirements
------------------
This package needs the headers from dahdi-linux. Thus you should install
dahdi-linux before building dahdi-tools.

Build System
~~~~~~~~~~~~
GCC and friends. Generally you will need to install the package gcc.
There may be cases where you will need a specific version of gcc to build
kernel modules.


Extra Libraries
~~~~~~~~~~~~~~~
Some libraries are needed for extra utilities that are provided with
DAHDI.

- libusb is needed for building fpga_load, needed for firmware loading of
the Xorcom Astribank.
- libnewt is needed to build the optional but useful utility dahdi_tool.


Installation
~~~~~~~~~~~~
Note: If using `sudo` to build/install, you may need to add /sbin to your PATH.
----------------------------------
./configure
make
make install
# To install init scripts and config files:
#make config
----------------------------------


Build Tweaks
~~~~~~~~~~~~
Partial Build/Install
^^^^^^^^^^^^^^^^^^^^^
There are some make targets that are provided to build or install just
parts of DAHDI:

. Build targets:
- make: Build DAHDI user-space programs. partial
targets of it:
* make 'utilname': builds 'utilname' alone (e.g: `make dahdi_diag`)
* make utils: Build libtonezone.
* make libs: Build libtonezone.
. Install targets:
- make install: Installs user space tools into /usr/sbin/ (TODO - list
partial targets)
- make config: should be run once to configure


Installation to a Subtree
^^^^^^^^^^^^^^^^^^^^^^^^^
The following may be useful when testing the package or when preparing a
package for a binary distribution (such as an rpm package) installing
onto a subtree rather than on the real system.

make install DESTDIR=targetdir

This can be useful for any partial install target from the list above.


Options For ./configure
^^^^^^^^^^^^^^^^^^^^^^^
The configure script executes various tests and based on them generates
makeopts. You can pass it --with options and variable settings, for
instance:

./configure --without-ncurses CC="gcc-4.10"

If you just want to recreate the same files without a full detection
run, use:

./config.status

To re-run ./configure with the same parameters it was run with last
time, use:

./config.status --recheck


Configuration
-------------
Configuration for DAHDI resides under /etc/dahdi .

/etc/dahdi/system.conf
~~~~~~~~~~~~~~~~~~~~~~
The main method to configure DAHDI devices is using the utility
*dahdi_cfg*. dahdi_cfg reads data from the configuration file
/etc/dahdi/system.conf , figures out what configuration to send to
channels, and send it to the kernel.

A sample annotated system.conf is included in this directory and
installed by default. Edit it to suit your configuration. Alternatively
use the script dahdi_genconf to generate one that should work with your
system. Note that while dahdi_genconf will generate a working configuration,
it will not automatically detect hardware echo cancellation modules. These
will have to be enabled manually in system.conf.

/etc/dahdi/init.conf
~~~~~~~~~~~~~~~~~~~~
The configuration file of the dahdi init.d script is
/etc/dahdi/init.conf . That file is used to override defaults that are
set at the beginning of the init.d script.

Reference Configuration
~~~~~~~~~~~~~~~~~~~~~~~
Sample system.conf
~~~~~~~~~~~~~~~~~~
include::system.conf.asciidoc[]


Sample init.conf
~~~~~~~~~~~~~~~~
include::init.conf.asciidoc[]


Sample genconf_parameters
~~~~~~~~~~~~~~~~~~~~~~~~~
FIXME: still not properly formatted.

include::genconf_parameters.asciidoc[]


Tonezones
~~~~~~~~~
The file zonedata.c contains the information about the tone zones used
in libtonezone (and hence also in dahdi_cfg). Here is a list of those zones:

include::tonezones.txt[]


DAHDI PERL modules
~~~~~~~~~~~~~~~~~~
The directory xpp has, in addition to helper utilities for the
Xorcom Astribank, a collection of PERL modules to provide information
related to DAHDI. The PERL modules themselves are under xpp/perl_modules/ .
In xpp/ there are several utilities that use those modules:
- xpp-specific: dahdi_registration, xpp_sync, xpp_blink .
- General: lsdahdi, dahdi_genconf, dahdi_hardware, dahdi_drivers

The DAHDI PERL modules will currently only be automatically installed if you
happen to install the xpp directory. Those utilities require the PERL modules
to be installed, however they will also look for them in the directory
perl_modules, and thus can be run directly from the DAHDI source tree. For
example:

./xpp/dahdi_hardware -v

To get usage information on a program, you can also use perldoc
(sometimes provided in a package separate from perl itself). For
instance:

perldoc ./xpp/lsdahdi

Some of them are specific for the Xorcom Astribank and described in its
documentation. the others are:

lsdahdi::
A somewhat glorified `cat /proc/dahdi/*`.
dahdi_genconf::
Generates configuration based on the existing DAHDI channels and on
/etc/dahdi/genconf_parameters (replaces genzaptelconf as well).
dahdi_drivers::
A two-liner script (not installed by default) that simply returns the
modules that should be modprobe-d on this system.
dahdi_hardware::
Uses the information from SysFS and its own knowledge to show
what PCI/USB DAHDI hardware is connected and if it is currently used
by a driver. Shows also some more information for Astribanks from
/proc/xpp .


PPP Support
~~~~~~~~~~~
DAHDI digital cards can provide data channels through PPP as
point-to-point connections. This requires a plug-in to the PPP daemon
that is included in the ppp/ subdirectory. To install it:

1. Make sure you have the PPP source / headers installed. On Debian:

apt-get install ppp-dev

2. Run 'make' on the ppp subdirectory:

make -C ppp
make -C ppp install

3. Make sure your kernel has support for both PPP (which is common is
distribution kernels and for HDLC (much less common) - CONFIG_PPP and
CONFIG_HDLC .


include::UPGRADE.txt[]


License
-------
This package is distributed under the terms of the GNU General Public License
Version 2, except for some components which are distributed under the terms of
the GNU Lesser General Public License Version 2.1. Both licenses are included
in this directory, and each file is clearly marked as to which license applies.

If you wish to use the DAHDI drivers in an application for which the license
terms are not appropriate (e.g. a proprietary embedded system), licenses under
more flexible terms can be readily obtained through Digium, Inc. at reasonable
cost.


Reporting Bugs
--------------
Please report bug and patches to the Asterisk bug tracker at
http://bugs.digium.com/[] in the "DAHDI" category.


Links
-----
- http://asterisk.org/[] - The Asterisk PBX
- http://voip-info.org/[]
- http://voip-info.org/wiki/view/DAHDI[]
- http://docs.tzafrir.org.il/dahdi-tools/README.html[Up-to-date HTML version
of this file]