[App_rpt-users] Experimenting with loading Asterisk w/o using ACID CD
Bob
kk6ecm at gmail.com
Mon May 12 05:16:48 UTC 2014
I ran an experiment this weekend building a new server, and have some
questions.
I could not get the computer BIOS to boot with a basic network interface, so
began with CentOS 5.10 DVD, which installs the drivers. (The ACID CD could
not see the network when attempting to download phase1.sh.) I then used the
scripts from the ACID CD to install Asterisk/app_rpt. I manually downloaded
and phase1.sh (using parts of ks.cfg on the command line), and made the
script executable, then went from there to complete the "ACID" install. It
worked great as a method to get past the lack of initial network driver, and
the node is registered on Allstarlink.org. I have a couple of issues.
1) The new boot gives me a fail for ip6table load. The CentOS 5.10 did not
have this error on reboot after the load. It only occurs after "completing
the load" with the ACID scripts. How is this used in ACID, and is it
necessary? Is it used for security setup?
2) The build has the same issue with not being able to comm correctly with
the URI as I've had with other computers where the chipset and build are not
compatible. I did not check the compatibility with the CentOS 5.10 build
before the "ACID" install. I use the uridiag program to determine
compatibility (asterisk off). I'm thinking of attempting this with CentOS
6.5, but suspect the overwrite from executing the ACID scripts, which
download Asterisk updates, with not be compatible.
I'm wondering if I can go directly from CentOS 5.10, or 6.5 using the
astinstall.sh script
Any suggestions?
Still a Linux newbie sorting out his options.
Thanks,
r/Bob
kk6ecm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20140511/ec839315/attachment.html>
More information about the App_rpt-users
mailing list