Asterisk General Issues
Contents
- 1 How to determine the board arrangement when there are more than one AST board?
- 2 How to solve the problem that the system reports error in loading channel_unicall.so when you start Asterisk after restarting ISDN in a system ever installed with SS1?
- 3 How to determine the use of Zaptel or Dahdi for Asterisk?
- 4 How to deal with the compile errors for dahdi-linux-complete-2.3.0+2.3.0 software package?
- 5 When the SynAST driver is compiled under the environment of dahdi-linux-complete-2.1.0.4+2.1.0.2, why will the following prompts pop up:
- 6 How to upgrade Linux kernel?
- 7 How to deal with the compile errors during dahdi-2.4.1 installation in GoAutodial2.1 system?
- 8 How to check if the echo cancellation feature is enabled or not after you finish loading the driver?
- 9 How to enable the residual echo cancellation?
How to determine the board arrangement when there are more than one AST board?
If dahdi is configured automatically, you may check /etc/dahdi/system.conf to see the board arrangement.
How to solve the problem that the system reports error in loading channel_unicall.so when you start Asterisk after restarting ISDN in a system ever installed with SS1?
1.Enter the Asterisk directory previously installed with SS1 and execute the following command:
#make uninstall
2.Enter the Asterisk directory to be installed with ISDN and execute the following command:
#make install
How to determine the use of Zaptel or Dahdi for Asterisk?
For Asterisk-1.4.21 and versions below, use Zaptel; for Asterisk-1.4.22 and versions above, use Dahdi.
How to deal with the compile errors for dahdi-linux-complete-2.3.0+2.3.0 software package?
Compile errors may occur while compiling dahdi-linux-complete-2.3.0+2.3.0 software package in the LINUX system under PAE mode or the 64bit LINUX system. To fix these errors, delete the line XPP in the file linux/drivers/dahdi/Kbuild under the directory of dahdi-linux-complete-2.3.0+2.3.0,
When the SynAST driver is compiled under the environment of dahdi-linux-complete-2.1.0.4+2.1.0.2, why will the following prompts pop up:
rmdir: /usr/include/zaptel: No such file or directory
make[1]:[install-include] Error 1 (ignore)
Such problem comes from the file ‘Makefile’ of dahdi-linux-complete-2.1.0.4+2.1.0.2 itself and has nothing to do with the SynAST driver.
How to upgrade Linux kernel?
Take the upgrade to linux-2.6.35 for example.
#wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.36.tar.bz2 Download the kernel source file from the Internet. Skip this step if the file already exists in your local computer. #tar -xjf linux-2.6.36.tar.bz2 -C /usr/src/kernels #cd /usr/src/kernels/linux-2.6.36 #make mrproper #make menuconfig
Save the default configuration and exit.
# Use an edition tool (e.g. vi) to edit the config. file, adding contents or modifying it to: #CONFIG_SYSFS_DEPRECATED_V2=y #make –j2 #make –j2 all # Go back to check whether ‘CONFIG_SYSFS_DEPRECATED_V2=y’ is still there after executing ‘make all’, as we ever came across the loss of this option. #make –j2 modules_install #make –j2 install # Compile /boot/grub/menu.lst Modify: default=0 #Reboot
Copy the file include/generated/autoconf.h under the kernel directory to include/linux after the compilation is completed; or compiling errors may occur on dahdi.
How to deal with the compile errors during dahdi-2.4.1 installation in GoAutodial2.1 system?
Delete the line XPP from the file ‘Kbuild’ under the directory of dahdi-2.4.1 so as to prevent the compilation of the XPP module.
How to check if the echo cancellation feature is enabled or not after you finish loading the driver?
#cat /sys/module/fxm32/parameters/echokey
If it returns 0, echo cancellation is disabled; if it returns 1, echo cancellation is enabled.
How to enable the residual echo cancellation?
#insmod fxm32.ko offline = val (val=1 indicates the feature is enabled; val=0 indicates the feature is disabled. The default value is 0.)