Elastix 4 beta 1 released

[Bob1]

Just a heads up....

Elastix 4.0 beta 1 is online for download (downloads section)
This is the Elastix built on Centos 7

Now just so that we are clear, Elastix 4.0 is the next version after the Elastix 2.x series which includes the FreePBX system. It is not the next version of the Elastix 3.0 series (which is called Elastix MT). This link may help make thinks clearer.
http://www.elastix.com/en/elastix-split ... -products/

Simple Feature log
http://www.elastix.org/index.php/en/dev ... ml?id=1089

More detailed Feature log
http://www.elastix.org/index.php/en/dev ... ml?id=1088

Regards
Bob

 

[milocheri]

Thanks Bob!

 

[gershte]

Thank you, Bob!

I have a couple of questions.

First. Could you recommend a proper procedure to migrate from 2.X on 4.X Elastix?
Second Would I be able to upgrade this Beta to Final Release of Elastix 4 without a necessity to reconfigure the system from the scratch?

Thank you for your answers!

 

[Bob1]

gershte,

I think it is worth summarising across all versions regarding upgrading.

1) Elastix 4 beta 1

First of all, this is the first beta of the Elastix 4. It is definitely not suitable for production use. Whilst many including myself, might take a 2.x late beta or RC and use in production, it is with the knowledge that major infrastructure has not changed, and a large amount of testing of standard functions before implementing in production.

Elastix 4beta1 is a major change underneath utilising Centos 7 (Elastix 2.5 - is on Centos 5), so this is a huge jump. As part of this jump, everyone's favourite issue, replacing the deprecated php 5.1 with 5.3 has required a reasonable amount of rewriting of scripts and routines as PHP 5.3 was a major departure from PHP 5.1.

So in all, it has the potential to have some reasonable unforeseen issues pop up.

With this in mind, I would not like to take the chance that it does not upgrade correctly. As well as that, the Elastix developers could make some further changes before 4.0 goes stable. I am not privy to any decisions, but I would not put it past them (should they find no major issues with the Centos 7/PHP 5.3 upgrade), if they decide to move to Asterisk 12 or even Asterisk 13 before 4.0 release (please note again there is nothing known - they may keep it as is and look at this for future 4.x releases)

One real use for Elastix 4.x beta is as a test release that you can use on hardware that doesn't work on Elastix 2.5.

One more thing - One thing that does remain reasonably stable is the FreePBX version. It is still a 2.11.x version, Whilst I have not tried it myself, you could perform a FreePBX (not an Elastix backup) Backup on an Elastix 2.5 box and restore it to your Elastix 4.0 system. I am currently testing this at the moment in the lab. One main rule to remember is that restoring to/from FreePBX that is not in the same major version 2.11.xx to 2.12.xx will most likely fail. Again just restoring FreePBX is not a complete restore of Elastix functions, but it does take 70% of the work out of the way.

When it is finally released as stable, Elastix may have a migration/YUM upgrade. Its not beyond the realms of possibility, but it would require a far bit of work, so probably don't expect it to be available for a while when Elastix 4.x is stable.

2) Elastix MT (Previously 3.0)
This version is mainly a MultiTenant version e.g. for Hosted PBX systems. It is not intended to be an functionality upgrade from Elastix 2.5, it is its own product. It does not contain FreePBX, and as such does not contain all FreePBX functionality from Elastix 2.5. It has the basic functions just like a Hardware based Digital PBX. Its functions, I am sure, will grow over time.

There is NO migration path (and probably never will) from an Elastix 2.x system. As mentioned, it is basically a different product line.


3) Elastix 2.2, 2.3, 2.4 (possibly earlier) to Elastix 2.5 (inc FreePBX 2.11)

Whilst I have not done a few upgrades from the earlier versions for a while now, it is my understanding that YUM updates will bring these versions up to the latest 2.5. The best thing is to ask someone on the forum that has done one recently. There are some known issues (e.g. need to remove G729 codecs before upgrading), so it is worth asking.

This will at least bring you up to 2.5 and FreePBX 2.11.


Finally a major caveat.....before I do upgrades, I perform a test migration, in most cases on a Virtual Environment (e.g. VMware or similar or a spare machine). I perform an image of the system with clonezilla (or similar image software) and place it on another machine and perform a test upgrade. It is the safest way to go. I then test and test to make sure it is working correctly. I then upgrade a machine, knowing also that I have an image to roll back to if everything turns to dust.

In many cases, I prefer, especially when moving to versions with major changes, export the Extensions list to a CSV and completely rebuild on the new version. I currently have a 2.4 to 2.5 migration happening with 80 extensions and doing a fresh rebuild. But I do this in the knowledge that this will be a clean system.

You might say there needs to be a tried and tested upgrade path, but due to the flexibility, the amount or third party products included in Elastix, additional products e.g. codecs, NO Elastix system is the same. To give you an idea, I know of one Commercial PBX provider e.g. not Open Source product, where they charge $AU4500 per firmware upgrade on their system. And this is on a system that is closed in terms of software changes. So a labour charge of 10-20 hours is not unrealistic, particularly if you are adding new features and functionality.

Note: I am not an employee of Palosanto, nor a Palosanto deveoloper. I have used Elastix since 2007. Nothing I have written should be taken as fact, and should not be relied on. As I mentioned, I perform offline tests in almost all cases on systems that I have imaged first, which you should also do. You should work on the basis that any upgrade has the potential to break your Elastix system and work on the basis that the upgrade will fail.

Regards

Bob

 

[madscientist159]

I notice the beta is only available for x86_64. Will the production version of 4.0.0 retain i386 support? There are many low-power machines (e.g. Atom-based) that are ideal for small Elastix setups; it would be a shame to increase power use needlessly.

Thanks!

 

[Marcelo-DONN]

Are there a specific topic to specify errors?

I installed Elastix 4 Beta 1 and when i tried to run yum upgrade, there are a lot of errors:

Error: Package: 2009020507:asterisk-11.17.1-1.x86_64 (elastix-updates)
Requires: libcurl.so.3()(64bit)
Error: Package: 2009020507:asterisk-11.17.1-1.x86_64 (elastix-updates)
Requires: libnetsnmpmibs.so.10()(64bit)
Error: Package: 2009020507:asterisk-11.17.1-1.x86_64 (elastix-updates)
Requires: librpm-4.4.so()(64bit)
Error: Package: 2009020507:asterisk-addons-11.17.1-1.x86_64 (elastix-updates)
Requires: libmysqlclient.so.15(libmysqlclient_15)(64bit)
Error: Package: 2009020507:asterisk-11.17.1-1.x86_64 (elastix-updates)
Requires: libtermcap.so.2()(64bit)
Error: Package: 2009020507:asterisk-11.17.1-1.x86_64 (elastix-updates)
Requires: libnetsnmpagent.so.10()(64bit)
Error: Package: 2009020507:asterisk-addons-11.17.1-1.x86_64 (elastix-updates)
Requires: libmysqlclient.so.15()(64bit)
Error: Package: 2009020507:asterisk-11.17.1-1.x86_64 (elastix-updates)
Requires: libodbc.so.1()(64bit)
Error: Package: 2009020507:asterisk-11.17.1-1.x86_64 (elastix-updates)
Requires: libnetsnmp.so.10()(64bit)
Error: Package: 2009020507:asterisk-11.17.1-1.x86_64 (elastix-updates)
Requires: librpmio-4.4.so()(64bit)
Error: Package: 2009020507:asterisk-11.17.1-1.x86_64 (elastix-updates)
Requires: libsensors.so.3()(64bit)
Error: Package: 2009020507:asterisk-11.17.1-1.x86_64 (elastix-updates)

Please verify.
thanks,

Marcelo Merenda
DONN Soluções - Brasil

 

[Tinker3433]

Hi,
Is there another Forum covering the Beta?
Or any more updated version?

I am running the Beta and already spent time banging my head against the wall on what i found out (from paid support) was a bug.
Now i am fighting another issue and want to make sure it is not a know issue before i pursue it further.

Thanks,
Jeff

 

[russman]

Hi,
Is there another Forum covering the Beta?
Or any more updated version?

I am running the Beta and already spent time banging my head against the wall on what i found out (from paid support) was a bug.
Now i am fighting another issue and want to make sure it is not a know issue before i pursue it further.

Thanks,
Jeff

Speaking of such things, are we going to see new betas or or news on updates to 4.0 and MT anytime soon? Last public release of anything I can find was 8 months ago. I've seen a number of people senior contributors to the spiceworks forums say they used to love Elastix but its development has really dropped off and they now recommend FreePBX. I'd love to go further with this platform and invest in development but what I'm seeing isn't very reassuring.

PS: It speaks volumes that I'm the only one logged into Elastix forums right now. Also, I'd update the copyright at the bottom, "Copyright © 2006 - 2013 PaloSanto Solutions."

 

[tirsojrp]

Hi,
Is there another Forum covering the Beta?
Or any more updated version?

I am running the Beta and already spent time banging my head against the wall on what i found out (from paid support) was a bug.
Now i am fighting another issue and want to make sure it is not a know issue before i pursue it further.

Thanks,
Jeff

Why would you pay for support if you are running a beta software?

 

[russman]

@tirsojrp

Probably so that he can have support for attempting to use the beta... I tip my hat to him for not only supporting them financially, but working with them to ensure the error is not on his end and aid development efforts.

 

[Tinker3433]

Hi,
Is there another Forum covering the Beta?
Or any more updated version?

I am running the Beta and already spent time banging my head against the wall on what i found out (from paid support) was a bug.
Now i am fighting another issue and want to make sure it is not a know issue before i pursue it further.

Thanks,
Jeff

Why would you pay for support if you are running a beta software?

1. The Beta is the only image i could get to cleanly install in my VM server. The other one hung during install.
2. Much more likely that the transition will be (would have been) smoother from the Beta to RC then from an older version.
3. I had never worked with IP phones and why learn on something that is outdated and being replaced?
4. I thought that the beta would have forums, progress, updated, etc. that it would go RC within a month or 2 since it was out in public beta. But that has all not turned out to be true.
5. I paid for support because i was stuck without a working system and i thought it was just something i was doing wrong.

None the less, it did not work out, and so was a waste of $. I am now getting ready to convert over to a different package due to the lack of response on the Beta. I got the system working but i don't want to be stuck on a beta forever. None of the add-ins work. Hard to make changes to network adaptors, etc.

.

 

[tirsojrp]

@tirsojrp

Probably so that he can have support for attempting to use the beta... I tip my hat to him for not only supporting them financially, but working with them to ensure the error is not on his end and aid development efforts.

I understand how important is to collaborate to Open Source projects as Elastix, but that wasn't the expected result as stated by the OP.

1. The Beta is the only image i could get to cleanly install in my VM server. The other one hung during install.
2. Much more likely that the transition will be (would have been) smoother from the Beta to RC then from an older version.
3. I had never worked with IP phones and why learn on something that is outdated and being replaced?
4. I thought that the beta would have forums, progress, updated, etc. that it would go RC within a month or 2 since it was out in public beta. But that has all not turned out to be true.
5. I paid for support because i was stuck without a working system and i thought it was just something i was doing wrong.

None the less, it did not work out, and so was a waste of $. I am now getting ready to convert over to a different package due to the lack of response on the Beta. I got the system working but i don't want to be stuck on a beta forever. None of the add-ins work. Hard to make changes to network adaptors, etc.

1. What hypervisor? You could have asked in the forums for help. I do most of testing in VM's
2. Probably, but most of the knowledge you acquire in ELX2.5 can be applied to ELX4 and others voip platforms.
3. See #2
4. If you want to learn keep yourself away from beta software, stick to final versions.
5. Sorry about that, see #4

 

[Tinker3433]

@tirsojrp

Probably so that he can have support for attempting to use the beta... I tip my hat to him for not only supporting them financially, but working with them to ensure the error is not on his end and aid development efforts.

I understand how important is to collaborate to Open Source projects as Elastix, but that wasn't the expected result as stated by the OP.

1. The Beta is the only image i could get to cleanly install in my VM server. The other one hung during install.
2. Much more likely that the transition will be (would have been) smoother from the Beta to RC then from an older version.
3. I had never worked with IP phones and why learn on something that is outdated and being replaced?
4. I thought that the beta would have forums, progress, updated, etc. that it would go RC within a month or 2 since it was out in public beta. But that has all not turned out to be true.
5. I paid for support because i was stuck without a working system and i thought it was just something i was doing wrong.

None the less, it did not work out, and so was a waste of $. I am now getting ready to convert over to a different package due to the lack of response on the Beta. I got the system working but i don't want to be stuck on a beta forever. None of the add-ins work. Hard to make changes to network adaptors, etc.

1. What hypervisor? You could have asked in the forums for help. I do most of testing in VM's
2. Probably, but most of the knowledge you acquire in ELX2.5 can be applied to ELX4 and others voip platforms.
3. See #2
4. If you want to learn keep yourself away from beta software, stick to final versions.
5. Sorry about that, see #4

Yep, I agree with all your points.
It is always easier to see your mistakes after you make them.
1. No, a windows machine running my BlueIris Camera software. on which i am running VMware for my Firewall, and now VOIP server.
2-4. i expected it to be a short beta since it was released publicly. i expected a couple of weeks till a RC. I should have investigated further.

 

[danardf]

To declaring any bugs for this version, you still have bugs.elastix.org

 

[Amphibian]

I think not many peoples fully understand the meaning of what a "Beta 1" release is all about.

1: Believe it or not ---- it's the first of many more to come --- of a new software product or software version

2: It's not "expected" to work 100% right out the door ---- in fact if it works 25% that's pretty darn good,

3: Programmers put the first beta release out so that "Users" know something new has come about, so that "users" (if they desire to help out) can try it for them on a national scale, and so the programmers have some sort of feedback on development issues (hence the term "bug reports"),

4: and most of all, if it is a beta 1 release of a version 2 or higher, there is never a user manual up front, the programmers are seeing if the user can easily upgrade to and use the newer version based on what they already know from using the current stable versions,

5:and the most important part, forums like this allow those of us that don't have a bunch of funds to work with and whom are using free software to give back by offering up our time to try, test, and report back any bugs or issues we may have to the developers of the free software we are using ( and I might add -- to make money with), and, for those that can afford to pay for tech support on a beta version ----- I solute you in your efforts and desire to help further such a great effort of free and open source software.

So help out by remembering:
1: Usually the person that notifies you of the new release ---- he/she generally are not part of the development crew so cut them some slack ---- they probably don't know any more about the new release then we do. And, unless you've sat down, started from scratch, built a new piece of software with over a million lines of code by yourself (like I have in the past) it's hard to fully understand the grief, pains and expense that's gone into the free stuff you are using or testing,

2: try to first understand where the programmer is coming from, understand where he is trying to head to, and put yourself in their shoes in trying to see how and what direction it will take you in once it's completed, and work with them in getting there.

and 3: Software programming is like a great football game ( or any other game), you have the basic rules of the game, you have a bunch of players that claim to know how to play the game, but unless you come up with the right plays, are flexible enough to change those plays during the game, and have really great winning players ----- you’re never going to win the game.

So lets all work together for a better end results. Remember it's free open source software we are using. Instead of complaining ( I know -- I've done my fair share of it over the years) let us figure out what it takes to get the job done and done right so that we all can benefit by/from working together and maybe even making some money for Palosanto and maybe even ourselves.....

And by the way Bob, thanks for your efforts and being the one to keep old fools like me updated on new versions and releases. I know we sometimes forget that you (like the many other on here that have regular jobs, family and a life and do the same), have gone out of your way to devote a little time and effort out of your day to being part of this forum. I solute you and the many others that do so on a regular basis. Thank you.

Of course, as usual, this is just my honest opinion (MHO)......

amphibian

 

[Tinker3433]

To declaring any bugs for this version, you still have bugs.elastix.org

Thanks, I will go there and post further bugs.

Off the top of my head i know that none of the Addons I purchased will install. They all hang at some point and often force a reboot to clear them.

I did find a workaround posted for the previous bug i had reported to the Helpdesk regarding the inability to change network settings.

 

[Tinker3433]

I think not many peoples fully understand the meaning of what a "Beta 1" release is all about.

1: Believe it or not ---- it's the first of many more to come --- of a new software product or software version

2: It's not "expected" to work 100% right out the door ---- in fact if it works 25% that's pretty darn good,

3: Programmers put the first beta release out so that "Users" know something new has come about, so that "users" (if they desire to help out) can try it for them on a national scale, and so the programmers have some sort of feedback on development issues (hence the term "bug reports"),

4: and most of all, if it is a beta 1 release of a version 2 or higher, there is never a user manual up front, the programmers are seeing if the user can easily upgrade to and use the newer version based on what they already know from using the current stable versions,

5:and the most important part, forums like this allow those of us that don't have a bunch of funds to work with and whom are using free software to give back by offering up our time to try, test, and report back any bugs or issues we may have to the developers of the free software we are using ( and I might add -- to make money with), and, for those that can afford to pay for tech support on a beta version ----- I solute you in your efforts and desire to help further such a great effort of free and open source software.

So help out by remembering:
1: Usually the person that notifies you of the new release ---- he/she generally are not part of the development crew so cut them some slack ---- they probably don't know any more about the new release then we do. And, unless you've sat down, started from scratch, built a new piece of software with over a million lines of code by yourself (like I have in the past) it's hard to fully understand the grief, pains and expense that's gone into the free stuff you are using or testing,

2: try to first understand where the programmer is coming from, understand where he is trying to head to, and put yourself in their shoes in trying to see how and what direction it will take you in once it's completed, and work with them in getting there.

and 3: Software programming is like a great football game ( or any other game), you have the basic rules of the game, you have a bunch of players that claim to know how to play the game, but unless you come up with the right plays, are flexible enough to change those plays during the game, and have really great winning players ----- you’re never going to win the game.

So lets all work together for a better end results. Remember it's free open source software we are using. Instead of complaining ( I know -- I've done my fair share of it over the years) let us figure out what it takes to get the job done and done right so that we all can benefit by/from working together and maybe even making some money for Palosanto and maybe even ourselves.....

And by the way Bob, thanks for your efforts and being the one to keep old fools like me updated on new versions and releases. I know we sometimes forget that you (like the many other on here that have regular jobs, family and a life and do the same), have gone out of your way to devote a little time and effort out of your day to being part of this forum. I solute you and the many others that do so on a regular basis. Thank you.

Of course, as usual, this is just my honest opinion (MHO)......

amphibian

I agree with all your points and explanations.

However, I posted my question on Thu Apr 16, 2015. It was Thu Jun 04, 2015 before Anyone responded. And he did so just to check and see if the project was even still alive. 90+ days.........

 

[real_magiz]

where could I ask about Elastix 4.0 and grandstream phones?

 

[danardf]

Hi

Like everytime for all beta verisons : bugs.elastix.org :wink:

 

[real_magiz]

the only thing I like about Elastix 4 is auto phone configurator or auto provisioning tool. But I dont know how to set settings for Grandstream GXP1405. like time zone or correct time or something useful.