Thanks. I will investigate that tomorrow.
PDW
On 12/18/2016 6:07 PM, Lonnie Abelbeck wrote:
> Also, possibly the DAHDIMODS variable in /mnt/kd/rc.conf.d/user.conf may be
> missing a module.
>
> DAHDI
> https://doc.astlinux.org/userdoc:dahdi
>
> Lonnie
>
>
> On Dec 18, 2016, at 4:45 PM, John No
Also, possibly the DAHDIMODS variable in /mnt/kd/rc.conf.d/user.conf may be
missing a module.
DAHDI
https://doc.astlinux.org/userdoc:dahdi
Lonnie
On Dec 18, 2016, at 4:45 PM, John Novack_PIV2 wrote:
> You may want to try and lower the sleep delay time
>
> You may also want to examine Asteri
You may want to try and lower the sleep delay time
You may also want to examine Asterisk and the modules.conf and noload the
modules you are not ever going to use
This should speed up the loading of Asterisk. There are LOTS of stuff we will
never use
I assume you have also looked in system.co
Thanks all,
I added the rc.elocal script and made it a 30 second delay.
It seems to have cleared out the T1 channel bank this time but I have no
reason why.
When I boot, the T1 goes busy after about a minute. It appears that
Asterisk booting it will clear everything after the delay.
Thanks f
Thanks John for the extra info,
Looking at the order of the startup services:
--
ls -l /etc/runlevels/default/S*
--
dahdi occurs before elocal, and then asterisk later on. So make a
"/mnt/kd/rc.elocal" script ...
-- /mnt/kd/rc.elocal --
#!/bin/sh
DELAY=10
printf "[elocal] Delay $DELAY second
In much earlier non AstLinux installs, where Zaptel and asterisk were started
in rc.local, we used to insert a sleep 10 between Zaptel and starting Asterisk.
In current configurations I believe this process takes place elsewhere
John Novack
Paul Wills wrote:
Hello Lonnie,
I need to make sur
I think what Paul needs to do, though he didn't mention to the list, is a delay
after Dahdi, to allow additional time before proceeding.
In certain instances, Dahdi needs additional time to do something ( can't now
remember what or why ) but there needs to be a pause before the process
proceeds
Hello Lonnie,
I need to make sure that Dahdi is up an running before I start
Asterisk. Right now, all of the T1 channels are "stuck" in an active
state after a boot. I have to go into the CLI and do a dahdi restart to
clear them. I was going to put an arbitrary 30 second delay in before
sta
Hi Paul,
If you just need to execute commands at startup, create a "/mnt/kd/rc.local"
script, make it executable (chmod 700 /mnt/kd/rc.local) and it will be executed
on every boot, at the end of startup, after Asterisk is started, for example:
-- /mnt/kd/rc.local --
#!/bin/sh
. /etc/rc.conf
ma
Hello all,
Another quick question:
I need to add something to /etc/init.d/asterisk
Is there a way to do it while insuring that it will be there after a reboot?
Thanks,
PDW
--
Check out the vibrant tech community on o
10 matches
Mail list logo
