Jerry Geis wrote:
>>
>> ounds like the module got auto-unloaded due to not being in use.
>>
>> I have found the most reliable way to invoke zaptel/ztdummy is using the
>> proper init script:
>>
>> 1. In your zaptel source directory, do "make config". That will create
>> /etc/rc.d/init.d/zaptel and the rcX.d links to it.
>> 2. Likeewise, in your asterisk source directory, also do "make config"
>> if you haven't already. That will create /etc/rc.d/init.d/asterisk and
>> the rcX.d links.
>> 3. Do "chkconfig zaptel on" and "chkconfig asterisk on" just to be sure.
>> 4. Do "service zaptel start". That will load the modules and do any
>> configuration necessary. Try that and then watch /proc/interrupts.
>> 5. Also do "service asterisk start".
>> 6. When the system is booted up in future, zaptel and asterisk should
>> automatically start.
>>
>>
> Tony,
>
> This is what I do. In this case I also editied /etc/sysconfig/zaptel
> and removed (commented) all modules except ztdummy.
>
> Jerry
>
Well after conversations on the list (thanks so much for responses) and
much google searching
it comes down to adding a kernel boot command line of "acpi=off" to
grub.conf.
This keeps the real time clock ticking and playing wave files.
Thanks to all!
Jerry
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
