Read dicko's rather scathing review of 2.0. Scares the hell out of me. What good reason would a person have to move to 2.0 then? Seems to be some improvements with the dashboard, auto backup, etc. But is it worth it? Should one wait for 2.0.x? Especially Newbies who know 1.6 and don't want a fresh can of worms?

Cory:

Please don't get me wrong I am very supportive of the Elastix project in general , however when it comes to 2.0 these iso's are publicly available at sourceforge:

Elastix-2.0.0-stable-i386-bin-03Aug2010.iso dated 2010-07-30
Elastix-2.0.1 dated 2010-08-08
Elastix-2.0.2 dated 2010-08-25


In contrast there is only one for 1.6

Elastix-1.6.0-i386-bin-29Oct2009.iso dated 2009-10-31

Some questioned the "stability" of 2.0.0-stable prior to it's release, Some questioned it loudly after it's release and in what I considered the appropriate place, some others didn't, I suggest that in retrospect perhaps they might now agree.

Unfortunately you can't put toothpaste back in it's tube.

I personally have not used 2.0.? in a production environment yet, why? well . . .

There are many posts here about "bugs" in 2.0 from email to backups to MOH . . . the list goes on.

None of these perceived bugs will be attested to until they are seen by the developers, i.e. they will not be seen, these guys just don't come here.


The good thing is that bugs are suddenly now being taken a little more seriously and I hope for a final and stable resolution shortly.

But to get there, I implore these posters to post the noted buggy behavior at:-

bugs.elastix.org/

It is unfortunately now up to us, the users, to get this fixed. The alpha testers, the beta testers (myself included) but ultimately PaloSanto, just dropped the ball here.

I further absolutely agree that a newbie should not have to fight his way through daily yum updates and file patches to get a functional system, as such I suggest they stay rooted firmly in 1.6 and wait for the dust to settle.

regards to all who read this, and please remember this is JM2CWAE, I represent only myself.

dicko

Well spoken dicko. I have followed elastix for a couple years now and have replaced all of my clients running trixbox and pbxiaflash with elastix 1.6. Up until recently I have always built my own servers and took advantage of the free software without financially contributing to the project. On my most recent installation I figured I would start to contribute by purchasing the elastic appliances therefor helping in some way to support elastix. I was thrilled that it arrived with elastix 2.0 installed until I started programing it for my client only to find there are still many bugs that popping up. So my thought is if I'm now going to start selling appliances opposed to building my own they better be ready for a production environment when it arrives to my office, this is unfortunately not the case. As much as I enjoy working with elastix that really pisses me off.

I'm sure they'll fix it. They got 1.6 to a pretty stable state. Look what they did with that old Forum and Site. The new Site works. Bad businness to release a buggy version to market on your appliances, though. Try Rhino Equipment. Tell Jim Rhones I sent you.

I feel your pain. I downloaded 2.0 and was very excited about the look and feel of the distro in general. After spending 2 days on trying to get a PAP2 ata device to dial a local extension, I am going to download 1.6 and get things going.

A couple of engineers at Vitelity said the 1.6 is rock solid. I have had issues about 2.0 and have posted request on this forum but no one can fix them. I will pay more attention in the future, but 2.0 still look promising for the future.

I can only post (and repost, repetitively perhaps recusively,, and perhaps to some folks chagrin, and as I intend to for every problem related to Elastix 2.0.? and it's ongoing bugginess) :-

www.elastix.org/component/kunena/25-newb...6.html?lang=en#59174

The important bit is to PLEASE post a bug-report, no-one here has the power to help, unless and until the developers "get-it"

It just won't work until folks actually get up and say, "I won't take this anymore". You guys have to do that where the Dev's hangout, and believe me, they just don't come here.

Just spend two minutes and express your concerns, OK?

regards

dicko

Well there are a lot of changes in this version including asterisk 1.6. There are is a lot to watch out for as versions change in different projects like freepbx and asterisk. I suppose the change is unknown or untested in elastix until some reports the bug.

I am still trying to get the MoH embedded bug fixed for both 1.6 and 2.0 which I reported here:
bugs.elastix.org/view.php?id=471

The status is still in feedback even though I replied to the bug after the stated they needed more info. Oh well...

One major/minor thing I noticed going to asterisk 1.6 is the new feature (which most might think is a bug) for sip session timers. If you don't change the setting in asterisk, some endpoints/sip providers don't support this, and the asterisk 1.6 will drop the call if there are no responses to the time expire message... something to that extent. You can change this by setting this in the general section of the sip.conf:

ignoresdpversion=yes
session-timers=refuse
session-expires=120

Other than that, I have been running 2.0.1 since it went "stable" and haven't had any amjor problems. That might be to the fact that I don't use PSTN/TDM cards and just use SIP trunks. I don't know. I have yet to test the call center module and a bunch of other modules I rarely use in the new version.

Where are the issues with 2.0 that Dicko reported. I would like to take a look at them to see if I can help in the patches.

Thanks,
Gil

Thank you gl1176:

This is exactly the analytical thinking that needs posting in the bug-list and perhaps you should join the developers listserv (also linked below).

There is a serious disjunct between Elastix and FreePBX, (Elastix cares needlessly to repackage an old version , so fixes in FreePBX will not show up "any day soon" in Elastix), for example an esoteric but significant example here, where the Elastix Packaging breaks the FreePBX intension, go figure . . .

bugs.elastix.org/view.php?id=485

Some bugs are FreePBX' , but we are officially stuck with the re-packaged versions here (unless you break the rules) so the bugs must currently be posted here.

As ever in FreePBX please make your changes in the sip_custom* files.

regards

dicko

I agree with all the posters here.

2.0 was released too early.

In my humble and un educated opinion, one of the mayor problems of elastix, is the upgrade from one version to the new one.

there's no support on that.

I have about a dozen or so PBXs running different versions, and i will NOT update them to 2.0 just because I need to do it by hand. I know it will not go smoothly.

If I may suggest one thing to Palosanto, is keep this update process transparent, or CHARGE for an easy update module. I would pay, it would be fair, for both parties. There is not enough beta testers, because we dont really want to risk it.

For me, as a end user, once the PBX is working, I am NOT touching it. Even if 2.0 dances and speaks by itself. But if I get an easy upgrade module, I might test it.

I will deploy a 2.0 this week in production. I'll cross my fingers, and post bugs and notes.

Palosanto, keep on the great work, we appreciate it a lot.
best wishes

agidi, How did your install with 2.0 go? I need to do a customer install (SIP only) at the start of October and would like the new features, but don't want to experience the pain or time drag. I'm fairly well proficient with 1.6 and don't want to go through learning again. Thanks.