<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.synway.net/index.php?action=history&amp;feed=atom&amp;title=Asterisk_General_Issues</id>
		<title>Asterisk General Issues - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.synway.net/index.php?action=history&amp;feed=atom&amp;title=Asterisk_General_Issues"/>
		<link rel="alternate" type="text/html" href="https://wiki.synway.net/index.php?title=Asterisk_General_Issues&amp;action=history"/>
		<updated>2026-04-08T14:57:24Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.24.1</generator>

	<entry>
		<id>https://wiki.synway.net/index.php?title=Asterisk_General_Issues&amp;diff=206&amp;oldid=prev</id>
		<title>Admin: Created page with &quot;===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 boar...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.synway.net/index.php?title=Asterisk_General_Issues&amp;diff=206&amp;oldid=prev"/>
				<updated>2015-05-14T01:49:57Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;===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 boar...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;===How to determine the board arrangement when there are more than one AST board?===&lt;br /&gt;
If dahdi is configured automatically, you may check /etc/dahdi/system.conf to see the board arrangement.&lt;br /&gt;
&lt;br /&gt;
===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? ===&lt;br /&gt;
1.Enter the Asterisk directory previously installed with SS1 and execute the following command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#make uninstall&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
2.Enter the Asterisk directory to be installed with ISDN and execute the following command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#make install&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===How to determine the use of Zaptel or Dahdi for Asterisk?===&lt;br /&gt;
For Asterisk-1.4.21 and versions below, use Zaptel; for Asterisk-1.4.22 and versions above, use Dahdi.&lt;br /&gt;
&lt;br /&gt;
===How to deal with the compile errors for dahdi-linux-complete-2.3.0+2.3.0 software package?===&lt;br /&gt;
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, &lt;br /&gt;
&lt;br /&gt;
===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:===&lt;br /&gt;
rmdir: /usr/include/zaptel: No such file or directory&amp;lt;br /&amp;gt;&lt;br /&gt;
make[1]:[install-include] Error 1 (ignore)&amp;lt;br /&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===How to upgrade Linux kernel?===&lt;br /&gt;
Take the upgrade to linux-2.6.35 for example.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.36.tar.bz2&lt;br /&gt;
Download the kernel source file from the Internet. Skip this step if the file already exists in your local computer.&lt;br /&gt;
#tar -xjf linux-2.6.36.tar.bz2 -C /usr/src/kernels&lt;br /&gt;
#cd /usr/src/kernels/linux-2.6.36&lt;br /&gt;
#make mrproper&lt;br /&gt;
#make menuconfig&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Save the default configuration and exit.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
‍‍# Use an edition tool (e.g. vi) to edit the config. file, adding contents or modifying it to: ‍‍‍&lt;br /&gt;
#CONFIG_SYSFS_DEPRECATED_V2=y&lt;br /&gt;
#make –j2&lt;br /&gt;
#make –j2 all&lt;br /&gt;
# 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.&lt;br /&gt;
#make ‍–j2 modules_install&lt;br /&gt;
#make –j2 install&lt;br /&gt;
# Compile ‍‍/boot/grub/menu.lst  Modify: ‍‍default=0&lt;br /&gt;
#Reboot&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===How to deal with the compile errors during dahdi-2.4.1 installation in GoAutodial2.1 system?===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===How to check if the echo cancellation feature is enabled or not after you finish loading the driver?===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#cat /sys/module/fxm32/parameters/echokey&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
If it returns 0, echo cancellation is disabled; if it returns 1, echo cancellation is enabled.&lt;br /&gt;
&lt;br /&gt;
===How to enable the residual echo cancellation?===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#insmod fxm32.ko offline = val (val=1 indicates the feature is enabled; val=0 indicates the feature is disabled. The default value is 0.)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Admin</name></author>	</entry>

	</feed>