The netinstall for Issabel should be used as Elastix is no longer maintained. IssabelPBX is a fork of Elastix, so it is the same Familliar interface and features, but updated, and more added.
The NetInstall script can be found here: https://sourceforge.net/projects/issabelpbx/files/Issabel%204/ -- Do not use the Beta netinstall... It is too old, and the regular install script has a prompt for installing the beta repo. If this is a Production PBX server, then don't use the Beta Repos.
The netinstall script borks the firewall, so you can't open the webinterface... But just ssh into your server, and type in systemctl stop iptables, then login to the webinterface, then enable the firewall there, then reboot the server. Then everything seems to work :)
Here is the Original readme:
Ok, So I wanted to setup Elastix in a cloud. There are some VPS's that are built for VOIP, but if you want it even cheaper than $30 per month, then there are other options out there. If only you could just install it on a VPS with centos 7... I use Hostmada's OVZ-3 plan for $5.99 per month. It may not be the fastest, but it works pretty well for me.
I searched for instructions on how to do put Elastix on a VPS, or over CentOS, and didn't find any. The closest I found were instructions on asteriskonvps.com that helped me out. How to install Elastix on a VPS without loop devices (OpenVZ)
I expounded on their instructions, and made scripts that extract the source ISO instead of repacking it then sending it to the VPS/openVZ. Since OpenVZ & my VPS provider do not have access to a loop device by default, this gets around it.
These scripts also work well if you have a linux server that you want to run Elastix in a openVZ container.
I wrote a couple scripts that do everything for you. It installs everything except for NetworkManager, which breaks the virtual network interfaces and makes it unreachable. If you want to do this on a CentOS 7 that uses other Virtualazation, you can install it by yum install NetworkManager NetworkManager-glib NetworkManager-tui when you are finished and have it be the Full Elastix setup. --Doesn't seem needed.
I also setup Elastix on digitalocean.com, and it seems to work even better. sign up through me, and you get $10 credit to start and play with. The $5 plan + $1 for backups is an awesome option!
To start out, ssh into your host. Then at the command, download the install scripts. If you do not have wget, install it by yum -y install wget, then you will just need to run this:
wget -O Elastix4onCentos7vz.tar.gz --no-check-certificate https://github.com/thpryrchn/Elastix4onCentos7vz/tarball/master
tar zxvf Elastix4onCentos7vz.tar.gz --strip-components=1
If you are using the Digital Ocean 512 MB Memory / 20 GB Disk / NYC3 - CentOS 7.2 x64 setup, you will want to create a Swapfile, or else your memory will run out, and the database will crash. to do this, run ./create-swapfile.sh
If you are not installing on a VPS, and have hardware you want Elastix to support, then swap inst2-hardware.txt with inst2.txt
Then proceed to run the first install script:
./elastix-install-p1.sh
This will download the Elastix Install DVD, unpack it to /mnt/iso, add it as a source to yum, then install all the files. It also adds Elastix's repo, so that it starts with the latest version. If you already have Elastix-4.0.74-Stable-x86_64-bin-10Feb2016.iso downloaded and in the same place as the install files, It will use it instead. Usefull if you find it on a faster Mirror.
Once it finishes, it needs to reboot. Reboot, then run the 2nd script
./elastix-install-p2.sh
This will run the First-Run for Elastix that will have you setup the Mysql Database password, and your ADMIN password.
It will also clean off the install files so they won't take up space anymore.
After it finishes, it will have you reboot once more. Then you can configure through the Web interface, and however else you work with Elastix.
If you can't access the web interface after the reboot, it is because you may have a firewall that is preventing it. To access it, you can temporarrly disable the firewall by running systemctl stop iptables and systemctl stop firewalld