Hi Tzafrir
I'm still testing so I start asterisk manually after boot. You are right
that 99 would normally be too late but as long as zaptel + modules are
loaded first with a lesser boot sequence number and is running when
asterisk starts on boot up it shouldn't matter where it is done in the
If I boot my server and manually type modprobe wctdm, it correctly
loads both wctdm and zaptel. If I put the modprobe in /etc/rc.local
and reboot, it fails. Why? I am running the latest svn source of
zaptel on Fedora Core 5 (w/latest updates as of 8/15)
Here are the error messages from
Hi Robert
Why don't you select the modules in /etc/sysconfig/zaptel and allow the
system to boot via /etc/init.d/zaptel by placing a link S99zaptel in
your appropriate run level directory. I found that S09zaptel, the
default, didn't work for me in my setup because it was too early in the
On Tue, Aug 15, 2006 at 09:32:00PM -0400, Robert La Ferla wrote:
If I boot my server and manually type modprobe wctdm, it correctly
loads both wctdm and zaptel. If I put the modprobe in /etc/rc.local
and reboot, it fails. Why?
Maybe /sbin is not in the path?
Anyway, rc.local is
On Tue, Aug 15, 2006 at 10:02:06PM -0700, Martti Tienhaara wrote:
Hi Robert
Why don't you select the modules in /etc/sysconfig/zaptel and allow the
system to boot via /etc/init.d/zaptel by placing a link S99zaptel in
your appropriate run level directory. I found that S09zaptel, the
