Major error going on somewhere
Here's exactly what I did, step by step.
Removed all network cables.
Inserted CD.
Entered p/w, time zone etc and let it run.
Removed CD when it popped out and let the computer restart.
netconfig - set up the network stuff.
reboot
All good so far.
yum install wan* reboot
All good here.
Setup-sangoma
And here the problems start.
STARTING ASTERISK Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. mpg123: no process killed Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. mpg123: no process killed ----------------------------------------------------- Asterisk could not start! Use 'tail /var/log/asterisk/full' to find out why. -----------------------------------------------------
So like a good little trooper I checked out the log.
Jul 30 13:33:27] VERBOSE[3515] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log
[Jul 30 13:33:28] ERROR[3515] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
3. If you need Zaptel services, you must correctly configure Zaptel.
[Jul 30 13:33:32] VERBOSE[3539] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log
[Jul 30 13:33:32] ERROR[3539] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
3. If you need Zaptel services, you must correctly configure Zaptel.Doesn't mean I understand it though. Obviously, Zaptel is messing up, but it seems to be caused by the sangoma thing.
I've tried reinstalling; with and without the sangoma card installed.
I've reverted to a previous version and made sure the card works. It does.
I've tried commenting all the zaptel things out, and uncommenting the dummy.
I've tried yum update.
I tried removing zaptel, which made asterisk work... but obviously zaptel wouldn't. It also wouldn't reinstall zaptel. I had to reinstall again.
I tried removing and reinstalling wan*
I tried installing all needed stuff from the package screen on the web interface.
Oh, I also get the 'does /etc/asterisk/asterisk.ctl exist?' message. Or something like that.
I tried the 'chown asterisk:asterisk /etc/asterisk/asterisk.ctl' I read on some other thread.
As a little test, I just stopped amportal, zaptel and wanrouter.
I tried 'amportal restart' It worked fine.
I then tried 'wanrouter start' followed by 'amportal restart'. And it throws back the error above. (asterisk died with code 1)
Then I tried 'service zaptel start' and again 'amportal restart' and it reverted to the error message above.
The card is an A101; the PC is a Dell Poweredge 840. If there's any particular logs you want, or commands you want me to run, let me know.
I'd like to get this sorted this week as I'm off for the next two.
Thanks
Mandi
If you go over to the Sangoma Trixbox install page they tell you how to install a newer version of the wanpipe drivers etc. worked for me.
see:
http://wiki.sangoma.com/wanpipe-asterisk-trixbox-rpms
J
Thank for the suggestion wcg, however I tried that a few installs ago and still had the same problem. But I'm on a test machine at the moment anyway so I can always reinstall if anything goes wrong. So here goes. *trundles off to install latest versions*
All done, but I'm still getting the 'asterisk died with code 1' error when I try to start asterisk wanrouter is running.
I'm quite irritated that the machine works fine until I run setup-sangoma though. No errors or anything until then.
Also, if I try to restart asterisk while I'm in the asterisk cli, it keeps repeating the error message and I have to reboot the machine.
If I run setup-sangoma and tell it to NOT start wanrouter on reboot, then I reboot the machine, asterisk runs okay.
The if I manually run 'wanrouter start' and 'genzaptelconf -vvv' it *seems* to be okay. But I can't test it until later because we're still at work here and I can't disconnect the working phones while in use obviously.
Saying that, I'd prefer not to have to run these commands each time we need to restart the computer. It'll get old real fast.
edit: It seems to run okay until I try restart amportal while wanrouter is running.
And now I've just had a kernel panic when I tried to reboot.
So; if I don't start wanrouter on boot, then start both it and zaptel manually, and run genzaptelconf -vvv by hand, it runs okay. Until amportal restart, in which case I need to stop wanrouter, restart amportal and then wanrouter again.
Someone please help me figure this one out =(
Okay, I've been hunting here.
Would it be possible to remove wanrouter and zaptel from the rc*.d startups, and add them to the rc.local, AFTER amportal? Because it *seems* to run okay when I start amportal first, then wanrouter and zaptel.
I know I technically can remove them with 'rm S**wanrouter ' or whatever the filename is, but would it break anything? And more importantly, would it fix anything?
So, I added wanrouter and zaptel to start after amportal, and they all run!
But (not sure if it's related) I have no sound at all on the phone. Voicemail works (I watched on the asterisk CLI, it runs all the 'no new msgs' stuff), but still, incoming and outgoing won't.
I'm going to power up the machine now (not connected to the phone line as working hours = rest of company need phones) and run random commands until I fix or break something.
Suggestions would be most appreciated, as my linux and asterisk experience is a grand total of about 2 weeks.
If there are any logs etc that could help someone help me figure out what's wrong, just tell me the name / where to find them and I'll post them
Hi,
The correct starting order is wanrouter then zaptel then Asterisk, so please insure your system is setup in that order. Next this issue is typically caused by our card being unable to generate interrupts on the system. So please run "cat /proc/interrupts" a few times and see if the interrupts are being processed. If they are not then your kernel and motherboard are not working well together. Typically this issue can be resolved by turning on or off acpi option in grub.conf, also please insure you have APIC turned on.
title CentOS-4 i386 (2.6.9-34.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.0.2.ELsmp ro root=LABEL=/1 acpi=on apic=on
initrd /initrd-2.6.9-34.0.2.ELsmp.img
If all this does not resolve the issue then please send an email with the following information into techdesk@sangoma.com. Also please insure you reference this forum so we know the exact issue.
-the output from "wanrouter version"
-the output from "wanrouter restart" (asterisk needs to be turned off for this so it may need to be done after hours)
-the file /var/log/messages (the entire file containing a wanrouter restart)
-the output from "wanrouter hwprobe verbose"
-the output from “wanrouter status”
-the file(s) /etc/wanpipe/wanpipeX.conf (where X is the wanpipe number)
-the file /etc/zaptel.conf
-the file(s) /etc/asterisk/zapata*.conf
-the output from "ifconfig", (re run a couple of times with a second or so delay in between each run)
-the output from "cat /proc/interrupts" (re run a couple of times with a second or so delay in between each run)
-the output from "wanpipemon -i wXg1 -c Ta" (where X is the interface number 1,2,3,etc) for each interface
Marc
Sangoma Technologies
Thanks Marc.
I'd tried stopping asterisk & wanrouter & zaptel and starting them in the order you said, but asterisk refused to start. It just kept on saying "asterisk died with code 1" etc. The *only* way i could get it to start was to start it, then wanrouter and zaptel.
I emailed the techdesk yesterday and got a reply from Yannick about an hour ago.
I'm doing a fresh install and documenting my exact steps so if it doesn't work, I can send that over too.


Member Since:
2008-07-23