665
edits
Changes
Jump to navigation
Jump to search
mLine 52:
Line 52: − === Migrate from Zaptel to DAHDI === − If you used previous version of smeserver-freepbx, and was using some Zaptel supported hardware, you'll want to migrate your configuration to the new driver: DAHDI. Here're the steps: − − *Remove any zaptel module (as they requires the main zaptel package, which conflicts with dahdi) − You can get the list of installed modules with: − rpm -qa 2> /dev/null | grep zaptel-kmdl − − Now remove the modules: − yum remove zaptel-kmdl-2.6.9-0.78.EL zaptel-kmdl-2.6.9-0.78.ELsmp − − *Update FreeePBX: it will automatically download dahdi-tools and dahdi-linux − yum --enablerepo=smecontribs update smeserver-freepbx − − *Install the module for your current kernel − yum --enablerepo=smecontribs install dahdi-linux-kmdl-$(uname -r) − − *Edit /etc/dahdi/modules − This files controls which drivers are loaded (the same as /etc/sysconfig/zaptel at the time of zaptel). You can comment any driver you don't need. − − *Start DAHDI drivers − You can load the selected drivers with: − /etc/init.d/dahdi start − − *Auto-detect your available channels and migrate the old config file: − − dahdi_genconf − sed -i -e "s/from-pstn/from-zaptel/g" /etc/asterisk/dahdi-channels.conf − cat /etc/asterisk/zapata.conf.rpmsave > /etc/asterisk/chan_dahdi.conf − sed -i -e "s/zapata-auto.conf/dahdi-channels.conf/g" /etc/asterisk/chan_dahdi.conf − − Now edit the file /etc/dahdi/system.conf and adapt it to your zone (loadzone and defaultzone) − − *Restart FreePBX service − signal-event freepbx-update − amportal restart − − Now, go in FreePBX admin interface, and click on the orange button (apply the configuration). Line 141:
Line 104: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Add how-to configure dahdi supported card
You should now be able to start using FreePBX on https://server.domain.tld/freepbx/admin
You should now be able to start using FreePBX on https://server.domain.tld/freepbx/admin
=== Components ===
=== Components ===
*'''dahdi'''
*'''dahdi'''
**'''status''': (enabled|disabled) You should let this to enabled, even if you don't have any hardware card because some functions (like meetme) requires the dahdi_dummy driver to be loaded.
**'''status''': (enabled|disabled) You should let this to enabled, even if you don't have any hardware card because some functions (like meetme) requires the dahdi_dummy driver to be loaded.
=== How-to ===
==== Migrate from Zaptel to DAHDI ====
If you used previous version of smeserver-freepbx, and was using some Zaptel supported hardware, you'll want to migrate your configuration to the new driver: DAHDI. Here're the steps:
*Remove any zaptel module (as they requires the main zaptel package, which conflicts with dahdi)
You can get the list of installed modules with:
rpm -qa 2> /dev/null | grep zaptel-kmdl
Now remove the modules:
yum remove zaptel-kmdl-2.6.9-0.78.EL zaptel-kmdl-2.6.9-0.78.ELsmp
*Update FreeePBX: it will automatically download dahdi-tools and dahdi-linux
yum --enablerepo=smecontribs update smeserver-freepbx
*Install the module for your current kernel
yum --enablerepo=smecontribs install dahdi-linux-kmdl-$(uname -r)
*Edit /etc/dahdi/modules
This files controls which drivers are loaded (the same as /etc/sysconfig/zaptel at the time of zaptel). You can comment any driver you don't need.
*Start DAHDI drivers
You can load the selected drivers with:
/etc/init.d/dahdi start
*Auto-detect your available channels and migrate the old config file:
dahdi_genconf
sed -i -e "s/from-pstn/from-zaptel/g" /etc/asterisk/dahdi-channels.conf
cat /etc/asterisk/zapata.conf.rpmsave > /etc/asterisk/chan_dahdi.conf
sed -i -e "s/zapata-auto.conf/dahdi-channels.conf/g" /etc/asterisk/chan_dahdi.conf
Now edit the file /etc/dahdi/system.conf and adapt it to your zone (loadzone and defaultzone)
*Restart FreePBX service
signal-event freepbx-update
amportal restart
Now, go in FreePBX admin interface, and click on the orange button (apply the configuration).
==== Configure a hardware card supported by DAHDI ====
FreePBX require that you configure your hardware card by hands before it can use it.
This example is with a TDM400 card from Digium. It should be about the same for other models.
* Insert the card
The first step is of course to connect physicaly the card on your server
* Check the server detects it
Now check your server can see the card with lspci
[root@sme ~]# lscpi
With the TDM400, you should see something like:
00:0d.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
* Remove useless drivers
Edit the file /etc/dahdi/modules and comment all the driver you don't need (the file is well commented). For example, with the TDM400P card, the only driver needed is the wctdm
* Restart DAHDI
run the following command to unload all the drivers, and load only the one(s) you need
/etc/init.d/dahdi restart
* Generate a basic configuration file
dahdi-tools include dahdi_genconf, a utility which can autodetect the available channels of your card, and create a basic configuration file
dahdi_genconf
Now, you need to adapt it so it can be used with FreePBX:
sed -i -e "s/from-pstn/from-zaptel/g" /etc/asterisk/dahdi-channels.conf
And edit /etc/dahdi/system.conf to adapt to your zone, for example:
# Global data
loadzone = fr
defaultzone = fr
* Adapt the main dahdi configuration
Now edit to your need the file /etc/asterisk/chan_dahdi.conf, you should include the file /etc/asterisk/dahdi-channels.conf. For example, here's my configuration:
;
; Zapata telephony interface
;
; Configuration file
[trunkgroups]
[channels]
language=fr
context=from-zaptel
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes
busydetect=yes
busycount=6
hanguponpolarityswitch=yes
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=6.0
txgain=6.0
group=0
callgroup=1
pickupgroup=1
immediate=no
;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no
;Include genzaptelconf configs
#include dahdi-channels.conf
group=1
;Include AMP configs
#include chan_dahdi_additional.conf
* Create your trunk and extensions in FreePBX
Now you can go on the admin interface of FreePBX and create your extension and trunks. To know which channel number is an FXO or an FXS, edit the file /etc/asterisk/dahdi-channels.conf. The section with context=from-internal are for extensions, the ones with context=from-zaptel are for trunks.
=== Uninstall ===
=== Uninstall ===