返回列表 發帖

Change from zaptel to dahdi (搞定)

本帖最後由 角色 於 2010-8-27 18:24 編輯

因为zaptel已经人注册了,所以Digium要把zaptel变为dahdi,但是很多以前的codes都是以zaptel为命名,所以在安装的时候经常出问题。

例如安装AX400P是,用CLI已经可以configure好,但是Asterisk-GUI是认zaptel而不认dahdi,所以在GUI依然认不出FXO卡。看来真的不是那么容易安装FXO/FXS卡。

怎样把AX400P安装好,继续努力中。。。。。。


角色

I am able to install AX4000P in Asterisk 1.4 but not Asterisk-GUI. Asterisk-GUI is not able to detect any analogue board installed because Asterisk-GUI is using zaptel and not dahdi.

Have you come across this situation before?


YH

TOP

1、create a symbolic link between ztscan and dahdi_scan
2、Replace ../zaptel.conf by dahdi-channels.conf in /etc/asterisk/zaptel_guiRead.conf.

YH

TOP

Also, change the extensions.conf as follows:

;trunk_1 = Zap/g1
;trunk_2 = Zap/g2
trunk_1 = Dahdi/g1
trunk_2 = Dahdi/g2

Now the system can be send outbound or inbound calls without any problems.

YH

TOP

No! The point is the Asterisk-GUI in AsteriskNOW is an old version which still use the zaptel terminology. I belive that the new version of Asterisk-GUI will get rid of all zaptel and replaced by dahdi.

YH

TOP

本帖最後由 角色 於 2010-8-28 08:39 編輯

There are some useful website when you troble-shoot your analogue cards:

http://www.sinologic.net/wp-cont ... l_to_dahdi_v0-3.pdf

http://wiki.openvox.cn/index.php/Troubleshooting_of_PRI_cards

TOP

For plain Asterisk, the conversion is okay. For Asterisk-GUI there still have some problems due the design of Asterisk-GUI based on Zaptel instead of Dahdi drivers.

YH

TOP

本帖最後由 角色 於 2010-8-30 20:38 編輯

It seem that your Asterisk-GUI is based on Dahdi instead of Zaptel. How did you get your Asterisk-GUI running? By using yum? or your compile yourself?

Where are the above two conf files located?

Are you able to adjust the setting under "Configure Hardware" tab?

YH

TOP

Okay, I may use yum to remove the Asterisk-GUI and install another Asterisk-GUI from svn checkout.

YH

TOP

I believe that if the Asterisk-GUI is compiled based dahdi, the hangup problem under GUI may disappear.

YH

TOP

返回列表