[-sRdv] -l -- only list to standard output
-su -- only unload zaptel modules
-h -- Help screen
is a script to detect zaptel devices (currently mostly TDM cards are
supported). It generates both
(with ZapBRI) cards are basically identified as well. However the span
configiration is a default that I only hope is sane. Looking for feedback
A two-letter country code. Sets the country-code for the zonezone
, The default is the value of
and failing that, "us".
Also try to detect modules. Unloads all zaptel modules and loads them
one by one. Considers a module useful if it loaded successfully and if
loading it has generated at least one zapata channel.
The list of detected modules is written as the value of
i . This is mostly for the caller-id values. Crude, but may be good enough.
Disable writing FXS extensions in zapata.conf
Only list deceted channels and their signalling. Don't write
configuration files. Note, however that
will still rewrite the modules line in
with a list of our modules, thereby
triggers their loading via modprobe on the next boot.
This triggers the
option as well.
Don't restart asterisk even if it was stopped using
Stop asterisk for the duration of the test. The detection will only
work if nobody uses the zaptel channels:
* To allow unloading of modules
* to allow reading configuration files.
This option tells the script to stop asterisk (if it was running) and to
try to start it after the end of the test.
Be verbose. lists the detected modules if
is used. Lists detected channls. In the end tries to connect to asterisk
to get a list of configured zaptel channels.
emulate the operation of zapscan.bin: generate
with the results of the scan.
Look at the beginning of the script for a number of variables that can
be overriden through the configuraion file. Some variables can also be
overriden through the environment. The configuration file is sourced by
bash but for compatibility expected to have only 'var=VALUE' lines and
comments or empty lines.
The configuration will first be read from
if it exists, and
otherwise (But those file names may be overriden, see
below). Variables set in those files will override the default settings
and setting rom the environment.
The following variables may be set from the environment:
ZAPCONF_FILE, ZAPATA_FILE, ZAPTEL_BOOT_DEBIAN, ZAPTEL_BOOT_FEDORA,
The default country. Can be also overriden by the option -c
The base number used for automatic numbering
If set to 'yes', no context changes are made in zapata-channels.conf
The context into which calls will go from zaptel trunks.
The context into which calls will go from zaptel phones.
If set to 'yes', no group settings are made in zapata-channels.conf
The group number for zaptel trunks.
The group number for zaptel phones.
modules list. Used for unloading and modules detection. The order of modules
is the same for both.
ztcfg's configuration file. The sane default is /etc/zaptel.conf .
The generated partial zapata.conf snippet. Default:
The Debian Zaptel defaults file. Normally
The Zaptel defaults file on various other distributions. Normally
Maximal number of seconds to wait for /dev/zap to be initializaed by
The full path to the ztcfg tool. Default:
genzaptelconf will also explicitly test for
as a last resort.
The configuration file used by
to configure zaptel devices. re-written by
genzaptelconf . A backup copy is saved to
The configuration file of Asterisk's
Not modified directly by
If you want genzaptelconf's setting to take effect, add the following
line at the end of
This is the snippet of
configuration file that
genzaptelconf generates. . A backup copy is saved to
This file holds configuration for both
It is sourced by both scripts and can thus be used to override settings
of variables from those scripts.
A debian-specific list of kernel modules to be loaded by modprobe at
boot time. When the option
(detect) is used, genzaptelconf will write in this file zaptel modules
to be loaded. If you want to use a different file, set
MOD_FILELIST . If it is rewritten, a backup copy is saved to
If you override a configuration variable both through the environment
and through the configuration file, the value from the configuration
This manual page was written by Tzafrir Cohen <email@example.com>
Permission is granted to copy, distribute and/or modify this document under
the terms of the GNU General Public License, Version 2 any
later version published by the Free Software Foundation.
On Debian systems, the complete text of the GNU General Public
License can be found in /usr/share/common-licenses/GPL.