This is the Frequently Asked Question section of the Webmin - Dahdi HW module
No, Zaptel is the original version of Dahdi. Think of Zaptel as verision 1 and Dahdi is version 2. The name was changed due to a trademark infringement. At the same time, significant changes in Dahdi were implemented to address Zaptel's shortcomings.
If the vendor has a Digium compatible card that uses a Dahdi driver then it should work providing the Linux kernel recognizes it. Unfortunately, there are many aftermarket vendors who have their own kernel drivers or interfaces to Dahdi that are poorly documented and "do not like to play with others" properly.
They are located in /etc/dahdi directory and consist of
init.conf - Allows you to pass kernel driver parameters during initialization
modules - controls the order and loading of kernel drivers
system.conf - configures the card's hardware telephony parameters (T1/E1/BRI, FXO, FXS, Dynamic, etc.)
genconf_parameters - controls the operation of the dahdi_genconf program
They are located in /etc/asterisk directory and may consist of
chan_dahdi.conf - (REQUIRED) main file that may include global parameters and "#include"s to other configuration files
chan_dahdi_additional.conf - file created by FreePBX that contains the FXS extensions
chan_dahdi_groups.conf - file created by FreePBX Dahdi Config module that contains FXO/E1/T1 trunk channel configuration
chan_dahdi_trunk.conf - file created by Webmin - Dahdi HW Config module for E1/T1/BRI, FXO and Dynamic Dahdi trunks
dahdi_channels.conf - file created by dahdi_genconf that consists of FXS extensions, E1/T1 and FXO trunk configuration
There might be others such as chan_dahdi_general.conf or files with the word _custom in it. The whole dahdi configuration issue is hit or miss.
You need Webmin version 1.5.1 or higher. They changed the API starting with 1.5.0
You can contact me but you need a sourceforge account first. Once you have a sourceforge account, you can get my email information.