I sent this off to digium, but have received no reply yet. Unfortunately, my freepbx system is down now. This happened suddenly but sometime after thunderstorm.
I’m trying to determine if I have a hardware or software problem with the subject setup.
When I plug in the analog line, the card takes the line off-hook after about 10 seconds.
Some stats:
[root@phone zaptel-1.4.11]# modinfo wctdm
filename: /lib/modules/2.6.9-34.0.2.EL/extra/wctdm.ko
description: Wildcard TDM400P Zaptel Driver
author: Mark Spencer [email protected]
alias: wcfxs
license: GPL
vermagic: 2.6.9-34.0.2.EL 686 REGPARM 4KSTACKS gcc-3.4
depends: zaptel
alias: pci:v0000E159d00000001sv0000A159sdbcsci
alias: pci:v0000E159d00000001sv0000E159sdbcsci
alias: pci:v0000E159d00000001sv0000B100sdbcsci
alias: pci:v0000E159d00000001sv0000B1D9sdbcsci
alias: pci:v0000E159d00000001sv0000B118sdbcsci
alias: pci:v0000E159d00000001sv0000B119sdbcsci
alias: pci:v0000E159d00000001sv0000A9FDsdbcsci
alias: pci:v0000E159d00000001sv0000A8FDsdbcsci
alias: pci:v0000E159d00000001sv0000A800sdbcsci
alias: pci:v0000E159d00000001sv0000A801sdbcsci
alias: pci:v0000E159d00000001sv0000A908sdbcsci
alias: pci:v0000E159d00000001sv0000A901sdbcsci
[root@phone zaptel-1.4.11]# modinfo zaptel
filename: /lib/modules/2.6.9-34.0.2.EL/extra/zaptel.ko
author: Mark Spencer [email protected]
description: Zapata Telephony Interface
license: GPL
version: 1.2.19 7DF9F18FA0FC6EFA00B3D31
vermagic: 2.6.9-34.0.2.EL 686 REGPARM 4KSTACKS gcc-3.4
depends: crc-ccitt
[root@phone zaptel-1.4.11]# gcc -v
Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.6/specs
Configured with: …/configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux
Thread model: posix
gcc version 3.4.6 20060404 (Red Hat 3.4.6-8)
I had thought it was a kernel module problem after doing a module up date to the freepbx system. I got the latest libusb and zaptel sources and am trying to build it, but getting an error during the compile:
[root@phone zaptel-1.4.11]# make modules
make -C /lib/modules/2.6.9-34.0.2.EL/build ARCH=i386 SUBDIRS=/usr/src/zaptel-1.4.11/kernel HOTPLUG_FIRMWARE=yes KBUILD_OBJ_M=“wctdm.o zaptel.o ztdummy.o ztdynamic.o zttranscode.o wct4xxp/ wctc4xxp/ xpp/ wctdm24xxp/ wcte12xp/” modules
make[1]: Entering directory /usr/src/kernels/2.6.9-34.0.2.EL-i686' CC [M] /usr/src/zaptel-1.4.11/kernel/zaptel-base.o /usr/src/zaptel-1.4.11/kernel/zaptel-base.c:407: error: syntax error before "zone_lock" /usr/src/zaptel-1.4.11/kernel/zaptel-base.c:407: warning: type defaults toint’ in declaration of zone_lock' /usr/src/zaptel-1.4.11/kernel/zaptel-base.c:407: error: incompatible types in initialization /usr/src/zaptel-1.4.11/kernel/zaptel-base.c:407: error: initializer element is not constant /usr/src/zaptel-1.4.11/kernel/zaptel-base.c:407: warning: data definition has no type or storage class /usr/src/zaptel-1.4.11/kernel/zaptel-base.c:408: error: syntax error before "chan_lock" /usr/src/zaptel-1.4.11/kernel/zaptel-base.c:408: warning: type defaults toint’ in declaration of chan_lock' /usr/src/zaptel-1.4.11/kernel/zaptel-base.c:408: error: incompatible types in initialization /usr/src/zaptel-1.4.11/kernel/zaptel-base.c:408: error: initializer element is not constant /usr/src/zaptel-1.4.11/kernel/zaptel-base.c:408: warning: data definition has no type or storage class make[2]: *** [/usr/src/zaptel-1.4.11/kernel/zaptel-base.o] Error 1 make[1]: *** [_module_/usr/src/zaptel-1.4.11/kernel] Error 2 make[1]: Leaving directory/usr/src/kernels/2.6.9-34.0.2.EL-i686’
make: *** [modules] Error 2
I’ve googled for these errors and have found many older references to a problem with spinlock.c in the kernel, but the changes have been made in the kernel sources.
The modules previously built appear to be loading: An lsmod reveals:
[root@phone zaptel-1.4.11]# lsmod
Module Size Used by
ztdummy 3924 0
wctdm 32832 0
wcfxo 11424 0
zaptel 192932 3 ztdummy,wctdm,wcfxo
and the output of dmesg…
Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.2.19
Zaptel Echo Canceller: KB1
PCI: Found IRQ 11 for device 0000:00:09.0
PCI: Sharing IRQ 11 with 0000:00:11.0
Freshmaker version: 73
Freshmaker passed register test
Module 0: Not installed
Module 1: Not installed
Module 2: Not installed
Module 3: Installed – AUTO FXO (FCC mode)
Found a Wildcard TDM: Wildcard TDM400P REV I (1 modules)
Registered tone zone 0 (United States / North America)
Registered tone zone 0 (United States / North America)
Any hints on whether this is a hardware or software problem?
thanks,
ted