Recent changes to FAQ

WikiPage FAQ modified by Eugene Blanchard

Eugene Blanchard — Mon, 13 Aug 2012 07:24:47 -0000

--- v9
+++ v10
@@ -28,7 +28,7 @@
 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_dadhi_additional.conf - file created by FreePBX that contains the FXS extensions 
+    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

WikiPage FAQ modified by Eugene Blanchard

Eugene Blanchard — Mon, 13 Aug 2012 07:24:11 -0000

--- v8
+++ v9
@@ -19,7 +19,7 @@
     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 dadi_genconf program
+    genconf_parameters - controls the operation of the dahdi_genconf program
 
 ---

WikiPage FAQ modified by Eugene Blanchard

Eugene Blanchard — Sat, 23 Jun 2012 15:09:54 -0000

--- v7
+++ v8
@@ -33,6 +33,8 @@
     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.
+
 ---
 
 * What version of Webmin is required?

WikiPage FAQ modified by Eugene Blanchard

Eugene Blanchard — Sun, 08 Apr 2012 07:08:14 -0000

--- v6 
+++ v7 
@@ -32,3 +32,15 @@
     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
+
+---
+
+* What version of Webmin is required?
+
+You need Webmin version 1.5.1 or higher. They changed the API starting with 1.5.0
+
+---
+
+* How do I contribute?
+
+You can contact me but you need a sourceforge account first. Once you have a sourceforge account, you can get my email information.

WikiPage FAQ modified by Eugene Blanchard

Eugene Blanchard — Tue, 03 Apr 2012 17:36:31 -0000

WikiPage FAQ modified by Eugene Blanchard

Eugene Blanchard — Tue, 03 Apr 2012 17:33:42 -0000

--- v4 
+++ v5 
@@ -4,14 +4,31 @@
 
 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. 
 
+---
+
 * Will you support vendor XYZ's legacy telephony driver?
 
 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.
 
-* Where are the Dahdi kernel configuration files?
-
-They are located in /etc/dahdi directory and consist of
-
-init.conf
-modules
-system.conf
+---
+
+* Where are the Dahdi hardware driver configuration files located?
+
+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 dadi_genconf program
+
+---
+
+* Where are the Asterisk software configuration files located?
+
+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_dadhi_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

WikiPage FAQ modified by Eugene Blanchard

Eugene Blanchard — Tue, 03 Apr 2012 16:59:46 -0000

--- v3 
+++ v4 
@@ -7,3 +7,11 @@
 * Will you support vendor XYZ's legacy telephony driver?
 
 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.
+
+* Where are the Dahdi kernel configuration files?
+
+They are located in /etc/dahdi directory and consist of
+
+init.conf
+modules
+system.conf

WikiPage FAQ modified by Eugene Blanchard

Eugene Blanchard — Tue, 03 Apr 2012 16:58:11 -0000

--- v2 
+++ v3 
@@ -1,9 +1,9 @@
 This is the Frequently Asked Question section of the Webmin - Dahdi HW module
 
-1. Will this module support Zaptel?
-
+* Will this module support Zaptel?
+
 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. 
 
-+ Will you support vendor XYZ's legacy telephony driver? 
+* Will you support vendor XYZ's legacy telephony driver?
 
 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.

WikiPage FAQ modified by Eugene Blanchard

Eugene Blanchard — Tue, 03 Apr 2012 16:55:17 -0000

--- v1 
+++ v2 
@@ -4,6 +4,6 @@
 
 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. 
 
-2. Will you support vendor XYZ's legacy telephony driver? 
++ Will you support vendor XYZ's legacy telephony driver? 
 
 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.

WikiPage FAQ modified by Eugene Blanchard

Eugene Blanchard — Tue, 03 Apr 2012 16:54:31 -0000

This is the Frequently Asked Question section of the Webmin - Dahdi HW module 1. Will this module support Zaptel? 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. 2. Will you support vendor XYZ's legacy telephony driver? 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.