665
edits
Changes
Jump to navigation
Jump to search
Line 52:
Line 52: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Add notes on how to migrate from zaptel to dahdi
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
=== 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).
=== Components ===
=== Components ===