similar to: Re: Problem with TDM400P

The REV I card shows up in the PCI table as: 02:05.0 Network controller: Tiger Jet Network Inc. Intel 537 (or 02:05.0 Class 0280: e159:0001) Subsystem: Unknown device b119:0001 But the REV E/F shows up as: 02:0d.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface (or 02:0d.0 Class 0780: e159:0001) Subsystem: Unknown device b100:0003 One

Hi all, I was wondering if anyone had any pointers on how to determine whether or not a module has gone wonky on the TDM400P? I have a 2 FXO (channels 3 and 4) and 2 FXS unit (channels 1 and 2). The bad (?) module in question is the FXO module on channel 3. I can't dial in to or out of that channel; dialing in gives a busy signal, dialing out just shows * hanging around after attempting a

I installed the TDM400P and installed it on a system running on Fedora Core1, please refer to the steps below. I connected an analogue phone to the FXS port. When I pick up the speaker I don't hear the dialtone although when I press a number key I hear a DTMF generated. What could be the problem? I appreciate your help 1- First I installed the TDM400P in the PCI slot and connected

I have a TDM400P with one FXO module and two FXS modules in it. I also have a Wildcard X101P. After trying hard to get things working on various Intel computers, but having echo problems that made it not really usable, I decided to try it on some older PowerPC (Macintosh) hardware running Yellow Dog Linux. Things started off smoothly. Both zaptel and asterisk seemed to compile okay, and both

I have a TDM21B (A new TDM20B that just arrived plus a X100M that I already had). This card sometimes works, and sometimes only the FXO module is seen. (correction to previous message that incorrectly listed X400M/S400M when I'm using only the single port versions of these modules (X100M/S110M). By "works", I mean all 3 modules have the green lights on the ports on and when

Hi all, I'm trying to install a TDM400P card, and I need some help. Please, see below... after dmesg command: [root@voip root]# dmesg via82cxxx: board #1 at 0xD800, IRQ 5 Zapata Telephony Interface Registered on major 196 PCI: Found IRQ 3 for device 00:09.0 PCI: Sharing IRQ 3 with 00:10.1 Freshmaker version: 71 Freshmaker passed register test Module 0: Installed -- AUTO FXS/DPO Module 1:

Hi all, I'm trying to install a TDM400P card, and I need some help. Please, see below... after dmesg command: [root@voip root]# dmesg via82cxxx: board #1 at 0xD800, IRQ 5 Zapata Telephony Interface Registered on major 196 PCI: Found IRQ 3 for device 00:09.0 PCI: Sharing IRQ 3 with 00:10.1 Freshmaker version: 71 Freshmaker passed register test Module 0: Installed -- AUTO FXS/DPO Module 1:

I'm running Asterisk on a Gentoo box with the Zaptel 1.2.1 drivers. If I boot the machine without having the wcfxs module autoload, then install the module with modprobe, asterisk works just fine. If I boot the machine and autoload the wcfxs module, the module loads fine: > Jan 11 11:06:55 asterisk Zapata Telephony Interface Registered on major 196 > Jan 11 11:06:55 asterisk ACPI: PCI

Hello. I have this problem. In my asterisk box, I was running debian woody with asterisk package from backports.org. Last friday I upgraded from debian to sarge and change from kernel 2.4.18-1-686 to kernel 2.6.8-1-686, rebuild zaptel kernel module and also upgrade to asterisk 1.0.2. But now asterisk won't start. Here is more info #asterisk -vvvvvvvv (last lines) [chan_zap.so] =>

Hi, I recently installed a gentoo on a PC, purchased a TDM400 and installed asterisk. Kernel is 2.6.11-rc3 First, there seems to be a problem with my system: I must put the pci=routeirq to make the card detected. The modules are loaded ok (dmesg output) Zapata Telephony Interface Registered on major 196 ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 16 (level, low) -> IRQ 16 Freshmaker

I apparently have a dead FXS module. Is there any kind of test I can run on it (on a live system) to determine if its good or bad? The telephone has no dialtone, gets no calls. It has been working for several months, and just quit yesterday. Thanks! Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules) Freshmaker version: 73 Freshmaker passed register test Module 0: Installed -- AUTO

Hi, I have a TDM21B (A new TDM20B that just arrived plus a X400M that I already had). This card sometimes works, and sometimes only the FXO module is seen. By "works", I mean all 3 modules have the green lights on the ports on and when zaptel is loaded the log shows: Freshmaker version: 73 Freshmaker passed register test Module 0: Installed -- AUTO FXS/DPO Module

Hi , I have an asterix (1.2.7.1) box with 3 TDM400P and 10 FXO modules, and zaptel (1.2.5). The problem is that 6 modules can't be initaized and i get the folowing error: May 7 09:17:37 WARNING[7739] chan_zap.c: Unable to specify channel 9: No such device May 7 09:17:37 ERROR[7739] chan_zap.c: Unable to open channel 9: No such device here = 0, tmp->channel = 9, channel = 9 ztcfg output

Hi, I have received a new card TDM400P revision E, from digium. When I tried to modprobe wcfxs it gave me the following errors: Freshmaker version: 63 Freshmaker passed register test ProSLIC on module 0 insane (1) 255 should be 2 Module 0: Not installed ProSLIC on module 1 insane (1) 255 should be 2 Module 1: Not installed ProSLIC on module 2 insane (1) 255 should be 2 Module 2: Not installed

I am having trouble with chan_zap.so not loading. When I load it from modules.conf, Asterisk bails out without any error message. When I load it from the console, it just says "Unable to load module chan_zap.so" no matter what verbose level I am using. dmesg says: Zaptel Version: 1.4.4 Zaptel Echo Canceller: MG2 Freshmaker version: 73 Freshmaker passed register test Module 0:

I got this nice TDM22B with two green modules left and two modules right /var/log/messages shows: Nov 26 23:47:48 dns kernel: Zapata Telephony Interface Registered on major 196 Nov 27 00:37:53 dns kernel: Freshmaker version: 71 Nov 27 00:37:56 dns kernel: Freshmaker passed register test Nov 27 00:37:56 dns kernel: Module 0: Installed -- AUTO FXS/DPO Nov 27 00:37:56 dns kernel: Module 1: Installed

I got this nice TDM22B with two green modules left and two modules right /var/log/messages shows: Nov 26 23:47:48 dns kernel: Zapata Telephony Interface Registered on major 196 Nov 27 00:37:53 dns kernel: Freshmaker version: 71 Nov 27 00:37:56 dns kernel: Freshmaker passed register test Nov 27 00:37:56 dns kernel: Module 0: Installed -- AUTO FXS/DPO Nov 27 00:37:56 dns kernel: Module 1:

I have a small system based on one TDM400 card with - 2 FXO modules for incoming lines - 1 FXS module for one phone The system was working fine in the past. The motherboard was exchanged and during the switch, the phones line was rewired with a mistake and a incoming phone line was connected to the FXS module, and there was ringing voltage on the module. Now, the system kinda works but the FXS

Hi all, Does somebody know why no load modules to FXS? I used zaptel-1.0.7 version driver. [root@server1 zaptel-1.0.7]# modprobe wctdm ZT_CHANCONFIG failed on channel 3: Invalid argument (22) Did you forget that FXS interfaces are configured with FXO signalling and that FXO interfaces use FXS signalling? /lib/modules/2.4.21-27.EL/misc/wcfxs.o: post-install wcfxs failed

I have a TDM400. Just updated Fedora 12 to kernel 2.6.32. Rebuilt and installed dahdi-2.2.1. kernel modules loaded. lsmod | grep wctdm wctdm 37233 0 dahdi 194985 1 wctdm lsmod | grep dahdi dahdi 194985 1 wctdm crc_ccitt 1549 2 dahdi,isdnhdlc dmesg: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.2.1