Building Elastix 4 via RPM Repo

Doing some work today getting an Elastix 4 server built on a cloud platform on CentOS 7. This, of course, requires some additional work compared to a normal install where you are able to just use the ISO installation method. So rather than just figure it out, I decided that it would be better to script the install. Not hard at all, here you go. This is not a fast install and far from perfect, but thus far, it works.

While this build process works, I must add this warning here... Elastix 4 has proven to be very flaky and I am not recommending that it be used at this time. Hopefully the Elastix team will get things working well and updated regularly, but at the moment this is not the case. If you are interested in this purely to see what Elastix 4 is like, go for it. If you want to run a system in product, I highly recommend that you look at FreePBX instead. Same basic technologies but far better support and much more up to date and used far more heavily today. We will all do our best to support you on Elastix, but you will have a much better time on FreePBX with the current state of things.

Updated the script to be a bit more robust, seems to work now. The one step you have to manually edit one of the files that has errors in it. Details in another script. Basically the entire section dealing with "acl_user" has to be commented out.

At this point you have to log in via a console (which rules out doing this on platforms like AWD and Azure that lack the console option without a lot more work.) This has been tested in the past on Rackspace and in this particular case on Digital Ocean. On the console you will need to fill out the necessary settings to allow the system to configure passwords and the like.

reply

Hello Scott. I've tried on Azure/CentOS7.1 but when step "yum -y install elastic-framework" is done, the root privilege are removed because the instruction inside elastix-framework-4.0.0-1.noarch.rpm to change /etc/sudoers file. That situation on Azure is killing because the root users are disable by default. Do you have any workaround idea? I've tied to rebuild the rpm but it didn't work. I really appreciate any help you can provide.

The issue there is Azure and some other providers modifying CentOS and not using either CentOS itself (in the case of the first provider changing out the kernel itself!) and Azure modifying default behaviour. Likely you could work around this on Azure by enabling root.

I would recommend testing out Digital Ocean or Rackspace. I would avoid Azure for PBX usage. PBXs are very sensitive to latency and performance and Azure is not on par with Amazon, Rackspace, DO, etc.