Hi,
I was using a TDM400P with cvs version of asterisk, loading the driver
with modprobe wctdm.
Some days ago I switched to stable version 1.0.6, where I found no
trace of such module ... is wcfxo to be used instead ?
Do I also have to change something in zaptel.conf ?
Tnx for any help!
If you have any FXS ports, use wcfxs.
On Fri, 18 Mar 2005 15:17:57 +0100, Alessio Focardi
[EMAIL PROTECTED] wrote:
Hi,
I was using a TDM400P with cvs version of asterisk, loading the driver
with modprobe wctdm.
Some days ago I switched to stable version 1.0.6, where I found no
trace of
Hello Dana,
Friday, March 18, 2005, 3:23:36 PM, you wrote:
DO If you have any FXS ports, use wcfxs.
No, only green modules.
But this is what I get when loading driver
modprobe wcfxs
FATAL: Error inserting wctdm (/lib/modules/2.6.9-1.667/misc/wctdm.ko): Unknown
symbol in module, or unknown
Can you run dmesg after that command and tell us what the relevant output is?
On Fri, 18 Mar 2005 15:32:02 +0100, Alessio Focardi
[EMAIL PROTECTED] wrote:
Hello Dana,
Friday, March 18, 2005, 3:23:36 PM, you wrote:
DO If you have any FXS ports, use wcfxs.
No, only green modules.
But
Hello Dana,
Friday, March 18, 2005, 3:40:21 PM, you wrote:
DO Can you run dmesg after that command and tell us what the relevant output
is?
# modprobe zaptel
modprobe wcfxs
FATAL: Could not open '/lib/modules/2.6.9-1.667/misc/wctdm.ko': No such file or
directory
# dmesg
Zapata Telephony
Try using module wctdm instead. That solved a lot of headaches for me.
On Fri, 18 Mar 2005 16:02:23 +0100, Alessio Focardi
[EMAIL PROTECTED] wrote:
Hello Dana,
Friday, March 18, 2005, 3:40:21 PM, you wrote:
DO Can you run dmesg after that command and tell us what the relevant output
Hello Scott,
Friday, March 18, 2005, 5:10:14 PM, you wrote:
SG Try using module wctdm instead. That solved a lot of headaches for me.
There is no wctdm module in zaptel-1.0.6.tar.gz .
So why when I call wcfxs ...
modprobe wcfxs
FATAL: Could not open
