Repos came back up last night. Must have been a SourceForge issue. Maybe they had a server down or something.

Long ago I had an article on this on my own blog but that is no longer up, so I am copying it here...

https://web.archive.org/web/20150221062029/http://www.scottalanmiller.com/linux/2012/09/02/improving-elastix-memory-usage/

The default installation of Elastix has more services running than are typically needed or desired on a PBX. These services eat far more memory that is necessary and can very easily be cleaned up to improve memory utilization.

First we will stop a series of unnecessary services from starting at boot time (this will disable shared storage, local email handling, new hardware detection, etc. so be aware that this does stop some things but any service that proves to be needed is trivial to re-enable.)

chkconfig nfslock off chkconfig cyrus-imapd off chkconfig iscsi off chkconfig iscsid off chkconfig netfs off chkconfig kudzu off

Further, if your system is like mine you likely use the web server very lightly but will find that the default configuration of Apache is set to spawn, by default, eight processes. This is far too many for a normal deployment. Each process uses memory. For an average deployment of Elastix, three is more than enough. You need only raise this number if web performance suffers. This will not impact telephony performance regardless.

In the file /etc/httpd/conf/httpd.conf we need to edit the section:

<IfModule prefork.c> StartServers 2 MinSpareServers 2 MaxSpareServers 8 ServerLimit 256 MaxClients 256 MaxRequestsPerChild 4000 </IfModule>

to something more like this:

<IfModule prefork.c> StartServers 3 MinSpareServers 2 MaxSpareServers 10 ServerLimit 256 MaxClients 256 MaxRequestsPerChild 4000 </IfModule>

You can wait for the system to reboot or restart Apache manually:

service httpd restart

And finally, to control swapping activity on the box, assuming that you want to avoid swapping when unnecessary, which I do because my box is virtualized, simply add this line on to /etc/sysctl.conf:

vm.swappiness = 10

You’ll want to test that number carefully. A setting of “10” is quite standard for virtualized systems. The default is “60”. For a physical deployment the higher value is likely better as it allows CentOS to make better decisions about how to utilize memory for maximum throughput. But on a virtualized system we really want to avoid, typically, any additional contention at the storage IO layer.
[Testing on Elastix 2.0 and 2.3]

The one feature that I really loved with 3CX was the incredible ease of setting up soft phones over a VPN. They do that beautifully.

@JaredBusch said:

Great news of course, but I just do not know if I can trust them to keep it up to date.

I'd be curious to know that too, especially after your adventure with yum updates and going from Elastix 2.4 to 2.5.

Got this fixed. Issue is all connected. It has to do with how the dependencies are picked up from the repo.

@scottalanmiller Yes... Everything works fine when I dialed in and pointed inbound route to an extension, rings and audio is perfect. Web interface, logs, Asterisk functions, modules loaded everything works fine. This is what confuses me the most. Unfortunately I cant just erase the entire server and start from scratch.

@scottalanmiller Ok, I think I got it. Per http://bugs.elastix.org/view.php?id=2549:

Starting with PHPMailer v5.2.7, the default HELO hostname is not set anymore to 'localhost' if not supplied on the Hello() function... This generates that the Elastix remotesmtp configuration checker ends up sending an empty HELO/EHLO command, which makes Gmail (and probably many other SMTP servers) really unhappy.

A possible solution would be to modify /var/www/html/modules/remote_smtp/libs/paloSantoEmailRelay.class.php on line 156:

if(!$smtp->Hello()){

change to:

if(!$smtp->Hello(getHostname())){

If you are using the Multi Tenant version the location is /usr/share/elastix/apps/remote_smtp/libs/paloSantoEmailRelay.class.php

Changed that and it worked. However, whenever I create a new organization and the email is sent to the "admin", I never receive anything... what could it be now? Any ideas? Thanks!

Yes, the number of people who are out there looking for "whatever is called Elastix" is way more than enough to keep the website and brand name around. Elastix has a huge presence in South America and in LATAM countries in general alone.

Wow, on a high end Juniper switch? That's more bad ports on a single Juniper than I've seen first hand on decades of use of Netgear!

@hubtechagain said:

Cause it's what they've got scott

@scottalanmiller said:

That's an odd answer - especially given they are apparently introducing a new system with Hylafax.

That is not an odd answer. They have an existing VM infrastructure. Normal business do not look to change core infrastructure every time they look at adding a new VM for some task or another.

Asking if there is any compatibility issues is a very normal thing that has to be done with ANY system.

Answer the question that was asked without tossing in craptastical bias.

Want to toss in the rest of your opinion? Great! Don't lead with it.

Back to the OP's question. I have never ran any type of 2008R2 Hyper-V servers. I know that Hyper-V prior to 2012 had many issues compared to ESXi. Which is why all of my clients started out on the virtualization path using VMWare.

Sounds like.... fun?

@scottalanmiller Can I borrow your password for a few weeks? I need to watch Game of Thrones after I finish the books, lol.

@scottalanmiller said:

OH okay. I think maybe someone responded to you about your setup or something and then it looked like there had been a question that there wasn't. Thanks for clearing that up.

you are welcome

@g.jacobse said:

I rant that over in my mind, and it seemed that if the reboot failed, you would not get any type of email.

If the reboot failed to run completely (like the system was down, cron had crashed, things were frozen) you would get no email either. You are making the system report on itself with is not good.

That's why the system should reboot itself (no way around that) but the monitoring of whether it is up or not should be done externally.

He is referring to this philosophy, above and beyond direct patching concerns:

Why We Reboot Servers

For SEO reasons, what had prompted this was finding:

./asterisk status asterisk dead but subsys locked

@thecreativeone91 said:

What the Adavantage with Pbx in a flash? That's the only one I haven't used. I've mostly used FreePBX (and some straight up asterisk)

The PBX in a Flash team also has a lot of nice extra features baked in and some that you can add (Traveling Man is a good example).

PBX in a Flash existed long before FreePBX had a distribution of its own. Obviously, PIAF uses the FreePBX GUI just like Elastix.unli,e Elastix, they do not wrap everything around in their own GUI. All that PIAF does is add a quick and dirty landing page to let you access the various tools directly from one place.

You basically need to know more to truly admin a PIAF system well.

It is also heavily focused on security.

@JaredBusch said:

@scottalanmiller said:

Oh, tricky. It is called Elastix MT and the "3.0" monicker has been retired. That is VERY confusing.

@scottalanmiller said:

I don't look at the site very often. First I've seen the MT monicker.

I've told you this before in another thread.

I missed that the name changed too. I knew that the products had split.

Here is the wiki article on how to do it.

http://dokuwiki.elastix.org/doku.php?id=how-to_install_elastix_from_centos5

This is CentOS 5... although you should be able to use it to help with the new version.