similar to: TDM400 problem

Hi My card is working, but when I reboot the machine, most of the times it is not working, I get "ztcfg: ZT_CHANCONFIG failed on channel 1: No such device or address (6)" To make it work again I have to shut down, remove the card, reboot so kudzu will remove the config. shut down again, put the card back in, reboot, now kudzu see it, I choose "Ignore" and then it's

Hi, Some weird problem (or I'm too sleepy) happens with a tdm04B revision G (4fxo) Steps: modprobe zaptel modprobe wctdm ztcfg -vv /etc/zaptel.conf fxsls=1-4 # TDM04B defaultzone=us loadzone=us /etc/asterisk/zapata.conf signalling=fxs_ls group=1 context=incoming channel => 1-4 modprobe zaptel and wctdm load fine, however ztcfg -vv shows: 0 channels configured Im using centos 4.4 with

Hello I setup Asterisk@Home with purely VoIP and it worked fine. I then added an X100P card so I could call out / take inbound calls via PSTN and that went fine. But I have just added a TDM400P card (specifically a TDM30B) and now problems. Here is some of the output. Any ideas on what I should be looking at next? When I run genzaptelconf -s -d I get lots of erors on screen - bit I can

Has anyone had success with the TDM400 in production? I have multiple boxes where these cards lock up and the only thing that will fix them is to unload *, modprobe -r wctdm, modprobe wctdm, load asterisk. Does not matter if it is a FXS/FXO module. I know this topic has been discussed many times before, but my questions is not "is anyone else having this problem" since I know that

Just installed Asterisk 1.2 on a brand new clean machine running RedHat 9.0. I have a TDM400 card inside. When I boot, the card seems dead. When I do: modprobe wctdm modprobe Zaptel the lights come on and all seems fine, until I reboot that is... After a reboot I have to repeat the modprobe. I shouldn't have to do a modprobe every re-boot should I? How do you get the drivers to load

Hi all, I have been looking at the code for both the zaptel driver (wctdm.c/wcfxs.c) and the asterisk channel driver (chan_zap.c) trying to figure out how much of this that has been implemented. So far I can see that the current stable 1.0.9.1 zaptel driver don't have the SETPOLARITY ioctl that would be required to properly signal the Swedish/Dutch CLIP, but the 1.2 beta1 has this

Ouch, part reset, quickly restoring reality (0) Power alarm on module 1, resetting! I have looked though a lot of email on this issue, and no one seems to have the answer. How many people are seeing this on a TDM400 card? Does anyone have a "REAL" answer to it. Yes, I do have the power connected to it! Regards Garry Taylor

Hi, I got my TDM11B and am trying to get it to work on my PC. However, I'm having difficulty getting the wcfxs driver to load. I've Googled this problem, and while there are others who have ran into the same problem, none of the solutions work for me. I would very much appreciate it if you could suggest things I could try to resolve this problem. Details follow. The PC is somewhat

Hi, I'm curious what chip Digium is using in the latest TDM400 cards. Specifically, to my recollection, they used to use the TigerJet 320G, however somewhat recently, Tigerjet was bought out, and now the 320G is no longer produced. Maybe a better question is: is there a way I can take the latest DAHDI source and get a list of supported chipsets from it? Thanks. MCH -------------- next part

Hello I am (attempting) to run the astlinux version of Asterisk on a VIA embedded platform. I have a TDM04B and pretty sure zaptel.conf and zapata.conf setup OK. They worked fine with same card in traditional PC anyway. I think need the module wcfxs for a Digium TDM04B card. Is this module not part of astlinux? Do I need to download it? Or is it in opt? I see wctdm - but think that is

Hi all i need urgent help our entire switchboard is down only 5 days after it came up. this is the second time this has happened and i am thinking that asterisk is not worth the trouble it gives. mostly it runs without hassle. but around 2 weeks ago during the test phase we rebooted the machine and did the normal modprobes and this error popped up. coming back to work after the weekend the

Hello, I have the following configuration : E100P -> * -> TDM400 -> Modem When I receive FAXes, about 20% of them are corrupted : pages are not always complete. If the fax is complex or with numerous pages, it's usually a mess. Before that, I was using spandsp with success. Unfortunately it's too picky with some broken fax (training failed). Since this failure only occurs with

/bin/sh: -c: line 0: syntax error near unexpected token `;' /bin/sh: -c: line 0: `if [ -n "" ]; then if [ -f ]; then mv -f .bak ; fi; cat .bak | grep -v "alias char-major-250" | grep -v "post-install torisa /sbin/ztcfg" | grep -v "post-install wcfxsusb /sbin/ztcfg" | grep -v "alias wctdm" | grep -v "post-install wctdm

Hi List; If I am configuring Diguim Analoge card, then I need to run #modprobe wctdm, but the question why I need to run #modprobe zaptel also? What #modprobe zaptel does a things that #modprobe wctdm does not do? Any help? Regards Bilal ____________________________________________________________________________________ Looking for a deal? Find great prices on flights and hotels

Folks, I have a Xen Asterisk VM with a TDM400 card. When I try to run dahdi_cfg, I get: tempest:~# dahdi_cfg -vvv DAHDI Tools Version - 2.2.0 DAHDI Version: 2.2.0 Echo Canceller(s): Configuration ====================== Channel map: Channel 01: FXO Kewlstart (Default) (Echo Canceler: none) (Slaves: 01) Channel 03: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 03) Channel 04: FXS

Hi all, I've struggled for several days trying to get a Digium TDM04B 4-port wxfco card working on a Dell 1U PowerEdge 750 machine running Fedora Core 1. I finally got a call back from Digium who indicated that there is a fundamental conflict between the card and the PowerEdge having to do with PCI interrupts. Asterisk version is stable v1-0 12/29/04. The symptoms of the problem were as

Hi All, I have the problem setting up TDM22B card. Steps what I have followed are: [1] compiled zaptel-1.0.9.2 & installed the same. [2] modprobe wcfxo /lib/modules/2.4.20-8/misc/wcfxo.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg

I have fixed this before, but I cannot for the life of me remember how I did it. I have a TDM400P with one fxo module and one fxs module. I setup Asterisk @Home and everything works fine, except when I try and call out. If I call out with a SIP phone it calls the zap extension and not the pstn line? If I take the zap extension offhook and call with the SIP phone it dials out the pstn line

Hi All I've bought a TDM400P and need some help with configuration. Can you tell me what to do ? I've tried to install and the message below has appeared: [root@voip asterisk]# modprobe zaptel [root@voip asterisk]# modprobe wcfxo /lib/modules/2.4.22-1.2115.nptl/misc/wcfxo.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid

I am getting quite frustrated today, so please bear with me. I just installed Fedora Core 4 (was running RedHat 9 with a working Asterisk) now my Fedora does not appear to be recognizing my X100P (clone) at all. Hardware browser just shows them as unknown device. driver: hisax So, of course, my zaptel drivers do not work and therefore my asterisk does not work. any help would be greatly