Change from zaptel to dahdi (搞定)

角色

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

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

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


角色

角色

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

YH

ckleea

The files are taken from file editor from web GUI. I shall check the location for you

角色

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

YH

ckleea

As stated before, yum install asterisk but not asterisk-gui. Use svn checkout to install GUI.

There is problem in using YUM to install GUI.

角色

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

ckleea

A working example using Asterisk 1.6 and GUI 2.0
Asterisk Build:
Asterisk/1.6.2.9
Asterisk GUI-version : SVN-branch-2.0-r5001

Server Date & Timezone
Mon Aug 30 20:09:02 HKT 2010

Uptime:
20:09:01 up 53 days, 5:29, 0 users,
Load Average: 0.42, 0.53, 0.81


dahdi_scan.conf
[general]
  active=yes
  alarms=OK
  description=Wildcard TDM400P REV I Board 5
  name=WCTDM/4
  manufacturer=Digium
  devicetype=Wildcard TDM400P REV I
  location=PCI Bus 03 Slot 02
  basechan=1
  totchans=4
  irq=217
  type=analog
  port=1,FXO
  port=2,FXO
  port=3,none
  port=4,none

dahdi_guiread.conf
[general]
  fxsks=1
  echocanceller=mg2,1
  fxsks=2
  echocanceller=mg2,2
  loadzone=us
  defaultzone=us

角色

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

角色

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

角色

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

ckleea

You find the tricks. For me, we have used asterisk 1.6 all along. So always dahdi

角色

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

角色

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

角色

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

ckleea

Are you using Asterisk 1.4? For 1.6, it is fairly easy to use dahdi to setup.