Configuring and Testing Zaptel Hardware
/etc/zaptel.conf
This is the continuation of Part 2 - Zaptel Drivers. The zaptel.conf file contains data so that the Linux operating system can recognize the hardware. It is a text file that resides in the directory /etc. If you are using FXS/FXO zaptel cards, you do not need to manually configure this file as it is automatically generated. For E1/T1 cards, /etc/zaptel.conf needs to be manually edited.
Automatically Generating zaptel.conf
To automatically generate the /etc/zaptel.conf file, you run the the GENerate ZAPTEL CONFiguration program "genzaptelconf" from the root command line on the server:
root@pbx:~$ genzaptelconf
After running genzaptelconf, view the /etc/zaptel.conf file using the nano text editor to see the assigned channels:
root@pbx:~$ nano /etc/zaptel.conf
For a 4 channel TDM400P card, you should see something similar to the following information depending on the FXS/FXO modules installed:
FXS ports use FXO signaling. The fxoks indicates that it is a FXS port with kewlstart signalling.
FXO ports use FXS signaling. The fxsks indicates that it is a FXO port with kewlstart signalling.
fxoks=1 indicates that it is zaptel channel #1
The Global Data section indicates that it is using US standard signalling for DTMF, etc.. If you were in Australia, you would use the signalling method used there.
At this point the hardware is operating and recognized by the Linux kernel. Next is to go to Part 3 - Asterisk Zapata Interface and tell Asterisk about it.
