In Your Honest Opinion??

[jml2665]

OK, after being told to upgrade to the latest release many times by Avaya, then reading on here the pitfalls of many of the releases. I am taking an non-scientific poll.

What version of 2.1, 3.0 and 3.1, in your opinion, is the most stable??

 

[NuggiFirst]

The version that has the best reputation on our systems are 2.1 (27). I can't really explain why...

 

[IPhello]

Anything with 44xx sets 2.1(27). 54xx 3.0(44)

 

[AguaFria]

3.0(44) had a few issues that my cutomers lost (call intrude - Call listen) 3.0(59) seemed to clear all of that up. I haven't found a truly stable 3.1 yet. 3.0(44) also gave me issues on erasing button labels on 5400 series under a dial feature.

Ian Engel
Agua Fria Communications

 

[IPGuru]

for total honesty the last release of V1.4 is hard to beat
V2.1(27) is fairly robust & stable with no real "show stopper" issues

V3.(59) is probably the best although I havent seen enough of V3.0(69) to be certain & V3.0(59) is know to have a lot of VoIP problems

V3.1 is still fairly new & i would say V3.1(48) is the version to go for at present

 

[AguaFria]

Let's put it this way - what do you want to work and what can you deal with being broken? That question will help you narrow your version down .

 

[crumthwacket]

We've got a couple (only a couple) of 3.1(48) versions installed and everyone seems pretty happy so far. With all due respect to the "big boys" (IPhello, IPGuru), those earlier 2.1(27) versions lack some important functions that make the field technicians job easier.

 

[aarenot]

I say,
1) Do not be on the latest release unless, you have issues that it is proven to fix. (let others prove its issues before you use it)
2) Do not upgrade until you know the known issues it will cause.
3) Be on the release you have now, unless you have an issue that you can not deal with.
4) Upgrade when you have an issue that needs support and Avaya will not support your current release.
5) Pray before, during, and after all upgrades.
6) It takes an hour to upgrade, and days to test how it went. Be prepared to go back to deal with issues.
7) Charge for upgrades labor.
8) Do upgrades while your support outlets are available.
9) If you have a ticket open on an issue, and they tell you to upgrade to fix it, do the upgrade while on the phone with them, and test it before you hang up.

Remember, if it was not an inconvenience, we would not get paid. Sometimes we get paid by the head ache.

You do not always get what you pay for, but you never get what you do not pay for.

 

[jml2665]

lot's of good information, with the theme "if it ain't broke, don't fix it" which is what I thought.
Thanks for everyones opinion.
I just hope someday the Avaya software comes out with more known "fixes" then known "issues

 

[aarenot]

I would suggest downloading the admin CD's as they become available for each release upgrade. Keep them on file, for when you choose to upgrade. Also get the tech bulletins for each admin release, and keep them.

You do not always get what you pay for, but you never get what you do not pay for.

 

[magix2kewl]

We have had very few problems with any of the latest release, 3.0.59 or 3.1.48. According to Avaya 3.1.48 is the same as 3.0.69 with the new 3.1 stuff in it. We never went to 3.0.69 because we wanted the stuff that was in 3.1. Mainly trouble shooting. Had one issue with 3.1.48 and that was on a small office - 4t8a3v - they use it as a voice mail system for 3 offices with vmpro. They have 466 Users on the SOE and when we went to 3.1.48 even though it is supposed to support 190K it would no longer load. Had to drop back to 3.0.59. Other than that we stay with 3.1.48.

Magix