I excitedly installed my TDM dev kit earlier this weekend, installing asterisk and all the kernel drivers to make it work. And it did, it was fantastic. I then reboot the machine, and even after doing a modprobe wctdm, I get the following: == Parsing '/etc/asterisk/zapata.conf': Found Jan 31 13:34:27 WARNING[342]: chan_zap.c:793 zt_open: Unable to specify channel 1: No such device or address Jan 31 13:34:27 ERROR[342]: chan_zap.c:6347 mkintf: Unable to open channel 1: No such device or address here = 0, tmp->channel = 1, channel = 1 Jan 31 13:34:27 ERROR[342]: chan_zap.c:9403 setup_zap: Unable to register channel '1' Jan 31 13:34:27 WARNING[342]: loader.c:388 __load_resource: chan_zap.so: load_module failed, returning -1 == Unregistered channel type 'Zap' Jan 31 13:34:27 WARNING[342]: loader.c:509 load_modules: Loading module chan_zap.so failed! I've confirmed the module was loaded - I see the messages on the console describing how it found the two modules. I've confirmed the card is powered, I see the two green lights on the PCI card's bracket on. I'm using the exact same configureation file I had the first time it work. I'm baffled on why it stopped working. The reboot was to change power supplies on this machine. Thinking the new one might not be giving the right kick, I tried switching back, no luck. I've ensured the power cable is hooked to the TDM400 card. But when I pick up the phone, I don't even get the same buzzing at before. I'm leaning towards a hardware issue, but before I send this card back to Alabama I was seeking some advice. Any ideas on why after a reboot the card might suddenly stop working, yet have all the signs of life? Here are some key configs: zapata.conf: signalling=fxo_ks echocancel=yes ; You can set this to 32, 64, or 128, tweak to your needs. echocancelwhenbridged=yes echotraining=400 ; Asterisk trains to the beginning of the call, number is in milliseconds callerid=asreceived group=1 context=default ; Points to the default context of your extensions.conf channel => 1 mailbox=1234 signalling=fxs_ks group=2 context=incoming channel=> 4 ; Again change the 'X' to the number of FXO modules you have zaptel.conf: loadzone=us defaultzone=us # Load FXS device (a TDM400P) as Channel #, and use fxoks=1 # Load FXO device (a T100X) as Channel #, and use kewlstart fxsks=4 Thanks!
> -----Original Message----- > From: Matthew Laird [mailto:zapa@luther.ca]> I excitedly installed my TDM dev kit earlier this weekend, installing > asterisk and all the kernel drivers to make it work. And it > did, it was > fantastic. > > I then reboot the machine, and even after doing a modprobe > wctdm, I get > the following: > == Parsing '/etc/asterisk/zapata.conf': Found > Jan 31 13:34:27 WARNING[342]: chan_zap.c:793 zt_open: Unable > to specify > channel 1: No such device or addressDid you remember to run ztcfg after loading the module? You have to do it every time or the channels won't be configured.
> -----Original Message----- > From: Matthew Laird [mailto:zapa@luther.ca]> Hmm, found the problem, I just manually ran it again (I did > last night) > specifying the configuration file.... well that's annoying. I have > zaptel.conf in /etc/asterisk along with the other configs, ztcfg looks > in /etc.... So, why does it expect the file somewhere else > from all the other asterisk configuration files?Left hand doesn't know what the right hand is doing, I'd guess. The people who wrote the hardware driver and the people who wrote Asterisk may not be the same.
Same problem here. "./asterisk stop;./zaptel restart;./asterisk start" seems to get it working. Question: will "ztcfg -vv" alone get it working? Andy Howell wrote:> I have a weird problem in which my digium card stops answering. After > running for a couple days, incoming calls are not seen. Running asterisk > -r shows no incoming calls. Restarting Asterisk does not help. After a > reboot it is fine. > > Any ideas? > > Thanks, > > Andy > > > _______________________________________________ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >
Andy Howell wrote:> I have a weird problem in which my digium card stops answering. After > running for a couple days, incoming calls are not seen. Running asterisk > -r shows no incoming calls. Restarting Asterisk does not help. After a > reboot it is fine.This problem was fixed in CVS (HEAD and v1-0) quite some time ago; what versions are you running?
Kevin P. Fleming wrote:> Andy Howell wrote: > >>I have a weird problem in which my digium card stops answering. After >>running for a couple days, incoming calls are not seen. Running asterisk >>-r shows no incoming calls. Restarting Asterisk does not help. After a >>reboot it is fine. > > > This problem was fixed in CVS (HEAD and v1-0) quite some time ago; what > versions are you running?Its 1.0.9, as part of Asterisk@Home 1.3 Thanks
Andy Howell wrote:> Its 1.0.9, as part of Asterisk@Home 1.3Then I would suggest upgrading to 1.0.9.1 or the just-released 1.0.9.2.
On Tuesday 13 September 2005 04:12 pm, Kevin P. Fleming wrote:> Andy Howell wrote: > > I have a weird problem in which my digium card stops answering. After > > running for a couple days, incoming calls are not seen. Running asterisk > > -r shows no incoming calls. Restarting Asterisk does not help. After a > > reboot it is fine. > > This problem was fixed in CVS (HEAD and v1-0) quite some time ago; what > versions are you running?I also see this from time to time. Running: Asterisk CVS-Nv1-0-9-09/02/05-14:07:10 built by root@pbx.axint.net on a i686 running Linux Setup a little cron job that, in the wee hours, does a: service asterisk restart and then * will start answering the lines again. Not ideal, but......