asterisk users - Dec 2009 - Starting and installing Dahdi (2.2.0)?

Hello

Unless I overlooked it, the "Asterisk Reference Information 
Version 1.6.1.6" at www.asterisk.org/docs doesn't include instruction
on how to start Dahdi when used to drive a TDP PCI card (OpenVox A400P
with a single FXO module
www.openvox.cn/products/show.php?itemid=20&lang=2).

I'd like to know...

1. How to start Dahdi manually. Is this the right way?

modprobe wctfxo
modprobe wctdm
modprobe zaptel

2. How to add a startup script in CentOS through chkconfig

If this is covered in an up-to-date document on the Net, please tell
me where it can be found.

Thank you.

It looks like "make config" takes care of installing an init script,
so I can just run "/etc/init.d/dahdi start to load the required
modules.

I get the following error, however:
-----------
# /etc/init.d/dahdi start
Loading DAHDI hardware modules:
  wcfxo:  [  OK  ]

Running dahdi_cfg:  DAHDI_CHANCONFIG failed on channel 1: No such
device or address (6)
[FAILED]
-----------

FWIW, the PCI card seems to be correctly detected:
-----------
# lspci -v

03:00.0 Communication controller: Tiger Jet Network Inc. Tiger3XX
Modem/ISDN interface
        Subsystem: Unknown device b100:0003
        Flags: bus master, medium devsel, latency 64, IRQ 12
        I/O ports at a000 [size=256]
        Memory at e2000000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2
-----------

Here's /etc/dahdi/system.conf:
-----------
loadzone=fr
defaultzone=fr
fxsks=1
-----------

Any idea what is wrong?

Thank you.

On Tue, Dec 08, 2009 at 02:15:40PM +0100, Vincent wrote:
> Hello
> 
> Unless I overlooked it, the "Asterisk Reference Information 
> Version 1.6.1.6" at www.asterisk.org/docs doesn't include
instruction
> on how to start Dahdi when used to drive a TDP PCI card (OpenVox A400P
> with a single FXO module
> www.openvox.cn/products/show.php?itemid=20&lang=2).
> 
> I'd like to know...
> 
> 1. How to start Dahdi manually. Is this the right way?
> 
> modprobe wctfxo
Not needed.
> modprobe wctdm
> modprobe zaptel
zaptel? You use dahdi, not zaptel. And zaptel will be pulled by wctdm
anyway.

Hint: dahdi_hardware .

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir