Does anyone have the experience of setting up Asterisk-GUI 2.0 using Dadhi driver without the issue of hangup detection problems with FXO ports?
It seems most of settings in Asterisk-GUI 2.0 for TDM400P cards do not apply. I believe that it may due to Zaptel driver is used instead of Dahdi driver in Asterisk-GUI.
If you know the way of fixing this problems, please please let us know. Otherwise whenever callers from FXO ports hangup before the callee picks up the calls. The callee's phone will ring for around 1 minute and stop.
YH作者: 角色 時間: 2010-8-30 21:23
In order to fix the hangup problem, I believe that I have to recompile the Asterisk-GUI using the Dahdi driver.
YH作者: 角色 時間: 2010-8-30 22:03
With the compiled version, the settings in the GUI looks better. The adjusted values are still there after reboot.
With the compilfed version, the hangup problem still perisists.
YH作者: ckleea 時間: 2010-8-30 22:10
How about to put my files into your conf?作者: 角色 時間: 2010-8-30 22:27
The file is more or less the same. They are automatically generated by the system. However the outgoing dialling method has been changed. For instance, _9. as the calling pattern, if I dial 92001, after stripping the digit 9, 2001 will be sent. However, from CLI, it show nothing to be sent.
YH作者: 角色 時間: 2010-8-30 22:34
本帖最後由 角色 於 2010-8-30 23:06 編輯
OS Version:
Linux leo 2.6.18-194.11.1.el5 #1 SMP Tue Aug 10 19:09:06 EDT 2010 i686 i686 i386 GNU/Linux
active=yes
alarms=OK
description=Wildcard TDM400P REV I Board 5
name=WCTDM/4
manufacturer=Digium
devicetype=Wildcard TDM400P REV I
location=PCI Bus 05 Slot 01
basechan=1
totchans=4
irq=82
type=analog
port=1,FXO
port=2,FXO
port=3,none
port=4,none
YH作者: 角色 時間: 2010-8-30 23:24
It seems that there is a software bug in SVN 5072 for "using this filter" and still waiting for a bug-fixed version. For the timing, I shall use the ordinary plain Asterisk only.
If someone wants to use Asterisk-GUI, I still recommend Asterisk 1.7: Option 4.
圖片附件: 0025.png (2010-8-30 23:26, 71.67 KB) / 下載次數 449