Building Elastix MT via RPM Repo

scottalanmiller

Elastix 4 offers much more features vs features in Elastix MT, as I see. Do you have a script to install Elastix 4 from repo?

Very different products, you should not be switching from one to the other. Elastix MT is for multitenant hosting. Elastix 4 is the continuation of their single tenant system. Different products for different scenarios.

scottalanmiller

@tellusys said:

Elastix 4 offers much more features vs features in Elastix MT, as I see. Do you have a script to install Elastix 4 from repo?

http://mangolassi.it/topic/6242/building-elastix-4-via-rpm-repo

tellusys

HI Scott,

A single organization in MT is nothing but Elastic 4 which is for s single tenant. How do I give latest features to a customer defined in MT? Both offer IVR features, but 4 offer custom destinations etc. What am I missing?

scottalanmiller

@tellusys said:

HI Scott,

A single organization in MT is nothing but Elastic 4 which is for s single tenant. How do I give latest features to a customer defined in MT? Both offer IVR features, but 4 offer custom destinations etc. What am I missing?

I've not supported MT, we don't (currently) offer multitenant solutions. What makes Elastix 4 not right for you?

tellusys

If we need to host multiple customers, do we not need to install elastix 4 for each of them? Some times a customer may just require a simple Digital Receptionist! It may not be worth the effort to install a complete E4 for them

scottalanmiller

@tellusys said:

If we need to host multiple customers, do we not need to install elastix 4 for each of them? Some times a customer may just require a simple Digital Receptionist! It may not be worth the effort to install a complete E4 for them

Correct, if you want to host like that, you pretty much need MT. but you will lose features, too. So it is a trade off.

zathiro

Hi, Scott, i check this script and run in a Centos 6 over Rackspace cloud , but, i can`t view the web interface, asterisk run ok, but, the web interface maybe is a problem with a mysql or httpd services.
Any suggestion?

scottalanmiller

@zathiro said:

Hi, Scott, i check this script and run in a Centos 6 over Rackspace cloud , but, i can`t view the web interface, asterisk run ok, but, the web interface maybe is a problem with a mysql or httpd services.
Any suggestion?

Did the script correctly set the password before completing? Did you reboot after the script ran?

scottalanmiller

@zathiro welcome to MangoLassi, by the way!

zathiro

@scottalanmiller Thanks !! Yes i run the complete Script, elastix-firstboot for config password and then reboot the server, but can't see the web interface, I have done as 4 times and nothing...

scottalanmiller

@zathiro said:

@scottalanmiller Thanks !! Yes i run the complete Script, elastix-firstboot for config password and then reboot the server, but can't see the web interface, I have done as 4 times and nothing...

What does...

/etc/init.d/httpd status

Return?

zathiro

@scottalanmiller

httpd (pid 2773) is running...

scottalanmiller

What is the output of...

netstat -tulpn

scottalanmiller

I'm guessing that your firewall is closing the ports.

zathiro

@scottalanmiller Oh, I see, activate a fw accept to see if the problem was, and this is resolved, I never imagined that the default was fw reject all connections, but now I can enter the dashboard, scoot thanks for your help

Scritp for fw-accept.

#!bin/bash
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT

scottalanmiller

@zathiro said:

@scottalanmiller Oh, I see, activate a fw accept to see if the problem was, and this is resolved, I never imagined that the default was fw reject all connections, but now I can enter the dashboard, scoot thanks for your help

Scritp for fw-accept.

#!bin/bash
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT

Yes, the default is to accept nothing but port 22, which is the SSH port for management. This is the industry standard (that Linux started.) Every OS blocks everything by default now on the firewall. Having the web open by default would be very bad. But rather easy to open up when needed.

zathiro

@scottalanmiller Yes off course, now I can open ports only for my vpn network that I have and not for the public

scottalanmiller

All working now?

zathiro

@scottalanmiller Yes! now it working and performance the firewall with iptables, thanks scott, for all!!

scottalanmiller

No problem. Glad that we got that fixed. I'll update the doc to mention that. Firewall is default on in CentOS 6 so I had ignored it.