Admin at 01:50, 14 May 2015

2015-05-14T01:50:55Z

Admin: Created page with "===Why does the NT module fail to be used in the mode of bri_net_ptmp in Asteriak-1.8.7.0 and above versions? === This is because the macro definition HAVE_PRI_CALL_HOLD in As..."

2015-05-13T01:45:46Z

Created page with "===Why does the NT module fail to be used in the mode of bri_net_ptmp in Asteriak-1.8.7.0 and above versions? === This is because the macro definition HAVE_PRI_CALL_HOLD in As..."

New page

===Why does the NT module fail to be used in the mode of bri_net_ptmp in Asteriak-1.8.7.0 and above versions? ===
This is because the macro definition HAVE_PRI_CALL_HOLD in Asterisk has been cancelled by default in Asterisk-1.8.7.0 and above versions, which makes the NT module fail to connect with BRI phones while its signal type is set to bri_net_ptmp.
To solve this problem, modify as follows: add the sentence ‘#define HAVE_PRI_CALL_HOLD 1’ to the file ‘include/asterisk/autoconfig.h’ under the Asterisk source code directory, then execute the command ‘#make’ and ‘#make install’.
Note: ‘./configure’ command cannot be used here, otherwise the file ‘autoconfig.h’ will be reset to default settings.

===How to determine the board arrangement when there are more than one AST board?===
If zaptel is configured automatically, you may check /etc/zaptel.conf or /etc/dahdi/system.conf to see the board arrangement.
If zaptel is configured manually, you may execute the command #cat /var/log/messages | grep "Launching card" to check the board arrangement.
If the board arrangement is determined by their serial number, pay attention to the time when you execute the command.

===How to install the SynAST driver in a dahdi version for which driver and tools are published separately?===
Please download the driver and tools of dahdi separately. <br />

1.By Script
<pre>
#cd /opt # enter the directory to source codes
#tar –zxvf SynAST-2.0.1.0.tar.gz # decompress the SynAST driver
#cd SynAST-2.0.1.0 # enter the directory to the SynAST driver
#cd dahdi # enter the directory to the ‘synway ast for dahdi’ driver
#./Setup install # install the driver
Would you like to install SynAST AST package now? y # enter ‘y’ to install
Please enter working dahdi directory [q](exit install) : /opt/dahdi_driver
# enter the directory to dahdi_driver source codes
Please enter dahdi_tools source directory [q](exit install):
# enter the directory to dahdi_tools source codes
SELECT TEJ MODE [t, e, j] :e # select the tej mode, or the driver will be installed in e1 mode
SELECT TEJXAPCI [75, 120]ohm # set the impedance of the TEJ pci board, 75 for coaxial cables, 120 for twisted-pair cables
SELECT TEJ201E [75, 120]ohm # set the impedance of the tej201e board, 75 for coaxial cables, 120 for twisted-pair cables
</pre>
2.Manually
<pre>
#cd /opt # enter the directory to the package of SynAST source codes
#tar –zxvf SynAST-2.0.1.0.tar.gz # decompress the source codes
#cp –rf /opt/SynAST-2.0.1.0/dahdi/srcs/fxm/fxm8apci /opt/dahdi_driver/drivers/dahdi
# copy the fxm8apci driver to the dahdi_driver directory.
#cd /opt/dahdi/linux/drivers/dahdi/fxm8apci
# enter the directory to SynAST source codes in dahdi
#make # compile the driver
#insmod fxm8apci.ko # load the driver

#cd /opt/dahdi_tools # enter the directory to dahdi tools
#./configure
#make # compile dahdi_tools
#make install # install dahdi_tools
</pre>

===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 solve the problem that the system fails to detect the hangup at remote end as the volume of the recorded busy tone is quite low? ===
Modify the file main/dsp.c under the Asterisk directory, changing the previous content ‘#define DEFAULT_THRESHOLD 512’ to ‘#define DEFAULT_THRESHOLD 448’. The value can be reduced again if the problem is not solved yet.

===How to solve the problem that the zaptel driver fails to be installed in the system of Ubuntu 8.10, kernel 2.6.27-7-server?===
Use the dahdi driver.

===How to solve the problem that the configuration files zaptel.conf and zapata.conf cannot be found under dahdi?===
/etc/dahdi/system.conf under dahdi corresponds to /etc/zaptel.conf under zaptel. The configuration files system.conf and zaptel.conf, although differ in name, are the same in content.
/etc/asterisk/chan_dahdi.conf under dahdi corresponds to /etc/asterisk/zapata.conf under zaptel. The configuration files chan_dahdi.conf and zapata.conf, although differ in name, are the same in content.

@@ Line 3: / Line 3: @@
 To solve this problem, modify as follows: add the sentence ‘#define HAVE_PRI_CALL_HOLD 1’ to the file ‘include/asterisk/autoconfig.h’ under the Asterisk source code directory, then execute the command ‘#make’ and ‘#make install’.
 Note: ‘./configure’ command cannot be used here, otherwise the file ‘autoconfig.h’ will be reset to default settings.
 ===How to determine the board arrangement when there are more than one AST board?===

BRI FAQ - Revision history

Admin at 01:50, 14 May 2015

Admin: Created page with "===Why does the NT module fail to be used in the mode of bri_net_ptmp in Asteriak-1.8.7.0 and above versions? === This is because the macro definition HAVE_PRI_CALL_HOLD in As..."