Well, I just received my replacement Digium card today! It does appear that it was the problem as my machine no longer hangs during boot!
However, in the process of trying to figure that out, I reformatted the box and reinstalled all the software. I saved my config files before doing that and have now dropped them back in, but it’s not working!
Running ztcfg -vv results in:
[code]asterisk:/etc # ztcfg -vv
Notice: Configuration file is /etc/zaptel.conf
line 252: Cannot get number of tones for channel 1
line 252: Cannot init tones for channel 1
line 252: Cannot get number of tones for channel 2
line 252: Cannot init tones for channel 2
line 252: Cannot get number of tones for channel 3
line 252: Cannot init tones for channel 3
line 252: Cannot get number of tones for channel 4
line 252: Cannot init tones for channel 4
8 error(s) detected[/code]
Trying to start asterisk:
[chan_zap.so] => (Zapata Telephony w/PRI)
== Parsing '/etc/asterisk/zapata.conf': Found
Apr 19 15:32:00 WARNING[8476]: chan_zap.c:1097 zt_open: Unable to specify channel 1: No such device
Apr 19 15:32:00 ERROR[8476]: chan_zap.c:7237 mkintf: Unable to open channel 1: No such device
here = 0, tmp->channel = 1, channel = 1
Apr 19 15:32:00 ERROR[8476]: chan_zap.c:12001 setup_zap: Unable to register channel '1'
Apr 19 15:32:00 WARNING[8476]: loader.c:414 __load_resource: chan_zap.so: load_module failed, returning -1
Apr 19 15:32:00 WARNING[8476]: loader.c:554 load_modules: Loading module chan_zap.so failed!
Argh. I have no idea why that is, nothing should have changed as I re-installed the same exact version of the OS off the same CD!
lsmod shows the drivers loaded. If I remove the channel line from the end of zaptel.conf, then ztcfg -vv will successfully load and show the channels, but asterisk still throws the same error.
could you post your zaptel.conf and zapata.conf?
[/quote]
I stripped them down to bare minimums for testing right now, hopefully I didn’t strip out something else I need too… Here’s what I’m working with right now.
[quote=“ianplain”]
What version of zaptel are you using ?
There are some issues with earlier versions of zaptel and cards.
IE The latest TE110p cards need the latest version.[/quote]
The card is a wctd24xxp. Version of zaptel, I’m not so sure about… rpm -qa|grep zap gives me the following:
zaptel-1.2.10-21
asterisk-zaptel-1.2.13-21
Either way, this was working before… Machine crashed during a software update (unrelated to asterisk), reloaded software, couldn’t get it going again, kept randomly crashing. Isolated the problem as being in the card, replaced card with a new one of the same model (RMA’d through Digium), system doesn’t crash anymore, but asterisk just won’t run. Same software as before… I’m guessing that perhaps something got corrupted in one of my backup config files. I just can’t seem to find it.
Asterisk should be started at this point
ztcfg -vv and it should show you your channels, if not try a different slot
What I have also done is remove the card let the system come up and have kudzu remove it. Shutdown again and put card in and let kudzu find it.
and then do the above commands. Let me know if that helps!!
Asterisk should be started at this point
ztcfg -vv and it should show you your channels, if not try a different slot
What I have also done is remove the card let the system come up and have kudzu remove it. Shutdown again and put card in and let kudzu find it.
and then do the above commands. Let me know if that helps!![/quote]
Well, ztcfg doesn’t have any problems seeing the channels. It’s asterisk that doesn’t see them! Very strange. I decided to start over fresh, on a brand new box with the newly RMA’d card and a fresh Linux install. I’m getting exactly the same results with my old configs that used to work before the hardware failure Starting to wonder if the new card is bad too, just in a different way from the first? I’d like to blame it on a config error, but this is the same set of config files that used to work!
[quote=“DoxBrian”]
Well, ztcfg doesn’t have any problems seeing the channels.[/quote]
Can you revisit this - your original post said ztcfg threw out errors about channel not found, then you removed channel lines from zaptel.conf? If you can reproduce those problems, Digium should assist troubleshooting.
Text file invisible corrupt is really rare. But you can try cat -A to see if anything unusual.
[quote=“valley”][quote=“DoxBrian”]
Well, ztcfg doesn’t have any problems seeing the channels.[/quote]
Can you revisit this - your original post said ztcfg threw out errors about channel not found, then you removed channel lines from zaptel.conf? If you can reproduce those problems, Digium should assist troubleshooting.
Text file invisible corrupt is really rare. But you can try cat -A to see if anything unusual.[/quote]
I had a note about not using the “channel” parameter in ztcfg, so I removed that and then ztcfg was perfectly happy, seeing all the channels. Guess I forgot to mention that I did that!
I’ve tried typing the configs by hand now and no change, still blows up with errors that it didn’t have before. I’m wondering now if it’s a kernel revision/ztdummy/USB controller issue (I’ve been reading about difficulties when an exact certain USB driver isn’t present, I think it’s “UHCI”)?
OK, here’s the latest… I’ve gone back to the documentation and completely rebuilt by hand the minimal configs necessary and I still have the problem. Here’s what’s getting logged in /var/log/asterisk/messages:
Apr 24 09:57:50 WARNING[3989] chan_zap.c: Unable to specify channel 1: No such device
Apr 24 09:57:50 ERROR[3989] chan_zap.c: Unable to open channel 1: No such devicehere = 0, tmp->channel = 1, channel = 1
Apr 24 09:57:50 ERROR[3989] chan_zap.c: Unable to register channel '1'
Apr 24 09:57:50 WARNING[3989] loader.c: chan_zap.so: load_module failed, returning -1
Apr 24 09:57:50 WARNING[3989] loader.c: Loading module chan_zap.so failed!
Right now ztcfg sees the channels just fine, but asterisk just doesn’t seem to pick them up. Is there some system service that might be missing/disabled that “connects” the 2?
ztdummy, USB shouldn’t matter because you are using a Digium card; shouldn’t even load ztdummy. What’s the output of ztcfg -vv, and your minimum zaptel.conf, zapata.conf?
My original setup had 3 defined. However, I cut it down to 1 during testing. I get the same error now with either 1 or 3. Doesn’t even appear to attempt to process more than the first one…
My original setup had 3 defined. However, I cut it down to 1 during testing. I get the same error now with either 1 or 3. Doesn’t even appear to attempt to process more than the first one…[/quote]
your ztcfg output suggests 4 mods installed. if 1 and 3 are not working, maybe it is worth trying 4. Just a thought!
Don’t we all wish Digium had better support Most of the time no one answers - E-mail or phone. But some people do get lucky and have support people seriously look. May as well give them a try during day time.
Starting to wonder if the new card is bad too, just in a different way from the first? I’d like to blame it on a config error, but this is the same set of config files that used to work!