Sangoma Weirdness with 2.2.10, SC-440 and a101 - Solved
Submitted by GSnover on Wed, 12/12/2007 - 8:34pm.
Had a strange problem that I worked on for several hours today - finally figured it out:
Loaded Sangoma drivers either from the package manager, or from source (3.2.1) and it loaded fine and Asterisk started and everything was kosher - PRI was up and we could make calls. Reboot the box, and Wanpipe loads and says "ZT_SPANCONFIG failed on span 1: Invalid argument (22)" and Asterisk Dies on boot but...
amportal stop
wanrouter stop
service zaptel stop
and then
wanrouter start
service zaptel start
amportal start
and we have a happy Asterisk again - reboot, and it fails again - same story (warm or cold boot btw).
Learned some Linux-Geeky stuff today:
Under /etc, you have seven directories named rc0.d through rc6.d that contain files with either a KXXfilename or SXXfilename - these are symbolic links to startup scripts with K being a Kill script and S being a Startup Script. The startup scripts are executed in numeric order, so S01 goes first then S02, etc.
In rc0.d and rc1.d, zaptel and wanrouter are not mentioned - the first mention is in rc2.d and in my rc2.d I had the following:
S09zaptel
S11wanrouter
After reading a couple of posts on how rcX.d works, I switched the files to be the following:
S08wanrouter
S09zaptel
And rebooted the machine - no joy - still the same problem - zaptel was loading before wanrouter, and was bombing. I then looked in rc3.d - same two files in the wrong order, so I fixed it there. Same in rc4.d, and rc5.d - they aren't in rc6.d, so I fixed the load order in rc2.d, rc3.d, rc4.d and rc5.d and rebooted - Hurray - it Works!
1) I have no idea why I had to do this - I have never had to do this with a Sangoma card before, and we have 17 of them deployed.
2) It seems to be working fine, but I wonder if there was an easier way to do this, or if this is a bad way to do it - I don't know.
Hope this helps someone else - I wasted hours on it trying different versions of Wanpipe.
Greg
Clean Load, and no, didn't call Sangoma
Wed, 12/12/2007 - 9:48pm
I thought about it, but I wanted to figure it out - Plus, I learned quite a bit about how the box starts up and shuts down - that is useful info to know.
I was also having Kernel Panics on my test box this morning, but I finally figured out that it was screwed up - Kernel Panics were coming from a corrupt load, not what I was doing with the Sangoma stuff.
Greg
Nope - Let it do everything it asked to do
Wed, 12/12/2007 - 10:30pm
Nope again - I always let it recompile Zaptel
Thu, 12/13/2007 - 10:47am
because I use Mark-2 + Aggressive - Seriously, I let it do everything it asks, and it is reproducible - Clean Load 2.2.10, yum update -y and then either install the Sangoma Package and run setup-sangoma, or download the Source and do a ./Setup install and answer yes to all the questions and you will get the same results - It's nothing that I did - I guess it could be something with the Hardware that I am using (Dell SC-440) but we have LOTS of SC-440's with a101's out there - this is something new.
Greg
this should sort our sangoma a101 issues out
Thu, 12/27/2007 - 8:08am
http://www.trixbox.org/forums/trixbox-forums/open-discussion/2-2-...
i belive this still should work
as long as you get the zaptel source and allow (and make sure that) the sangoma installation script recompiles it
+ 4 incoming call issues you might need to add this to your zapata-auto.conf file (i did)
pridialplan=local
priindication=inband
SysV Init Runlevels
Thu, 12/27/2007 - 1:40pm
SysV init is the initialization system found on most modern Linux distributions including CentOS/RHEL. It is fairly straightforward. You have a directory /etc/rc.d/init.d/ that contains all of your startup scripts. You link these scripts to the corresponding runlevel directory and this controls what starts when booting that runlevel.
For anyone who wants to learn in detail about how the CentOS/RHEL init system works I have placed a reference link below.
Member Since:
2006-11-19