[EMAIL PROTECTED] zaptel]# chkconfig --list zaptel zaptel 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[EMAIL PROTECTED] zaptel]# chkconfig --list asterisk asterisk 0:off 1:off 2:on 3:off 4:on 5:on 6:off Are not this numbers the runlevels defined on INITTAB? # Default runlevel. The runlevels used by RHS are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # If not, then I should put zaptel on on 1, and asterisk on on 3? Is this correct? Thanks, Carlos -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tzafrir Cohen Sent: Monday, January 16, 2006 3:03 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] loading zaptel drivers automatically upon reboot On Sat, Jan 14, 2006 at 03:55:50PM -0500, Carlos Alperin wrote: > After install everything on the supposedly right place, my conclusion is > that zaptel doesn't load wct1xxp module. That's easy to test: before you restart zaptel, look at /proc/zaptel . if /proc/zaptel exists, zaptel was loaded . if /proc/zaptel/1 exists and reports those 24 channels, then wct1xxp has loaded and identified your card. Another possible reason: make sure that the zaptel init.d script runs before the asterisk one. It needs to have a lower "start" number. Use 'chkconfig --list asterisk' and 'chkconfig --list zaptel' to verify that. > > Then, that is the reason for Asterisk to fail loading. > > However I change the MODULES & RMODULES on the zaptel on /etc/init.d & > /etc/sysconfig, it continuous same way. > > Carlos Alperin > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Tzafrir Cohen > Sent: Saturday, January 14, 2006 2:36 PM > To: asterisk-users@lists.digium.com > Subject: Re: [Asterisk-Users] loading zaptel drivers automatically upon > reboot > > On Fri, Jan 13, 2006 at 09:39:09PM -0500, Carlos Alperin wrote: > > That is right for zaptel. But you still has to do modprobe wctdm on > rc.local > > before to load asterisk. > > rc.local is run after the standard init.d scripts. Thus if you load > asterisk in an init.d script, you'd be loading the zaptel modules too > late. > > Just add another init.d script. See the skeleton in /etc/init.d (there's > a README there IIRC). > > -- > Tzafrir Cohen | [EMAIL PROTECTED] | VIM is > http://tzafrir.org.il | | a Mutt's > [EMAIL PROTECTED] | | best > ICQ# 16849755 | | friend > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il | | a Mutt's [EMAIL PROTECTED] | | best ICQ# 16849755 | | friend _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users