3.2 Stability?(VM)

[victor5908]

We are about to begin IPO installs again after a layoff.
I'm a little gunshy reading about the VMPro issues with the 3.2 releases.
Can anyone provide feedback on the most stable versions?
Would it hurt to run 3.2 53 Manager and an older VM?
I've done that countless times in the past with no ill effects.I know Avaya won't support but I won't need support if everything works the 1st time.

 

[janni78]

As usual it might work and it might not.

It may have worked in the past and you may suddenly run into problem. Usually there no problem within the same release 3.2.x mixing different maint releases.

But if you run into trouble you already know that Avaya will tell you to run matching version and usually people here also do that so it's all up to you

 

[cztech]

I've had been involved in five 3.2 upgrades thus far with no ill effects whatsoever. First three I went General release 3.2, and the last two have been the maintenance 3.2(53) and voicemail 3.2(28). These have been all digital locations except for 1 that was SCN'd. I do not have experience with the 3.2 releases and upgrades with IP phones in the environment.

CZ

http://www.ipofficeinfo.com

/

http://www.cztechnologies.net

 

[PhoneGuy98]

I have done about 4 upgrades now with none of the issues I have seen in the forums.

3.2.53 for switch and 3.2.28 for VM.

That said 3.1 was the same way, some sites worked great, some had issues.

For me the 3.2.53 fixed alot of issues I found throughout the revisions of 3.1, but going through the forums I see alot of people had issues after upgrading.

 

[victor5908]

Thanks a lot for the feedback folks-
I guess I'll go with the latest.I will be mixing in some IP sets.A 2-site scn with a shared VMPro.
I'll post the results.Not sure when this is going in,but I will keep informed.Thanks again.

 

[aarenot]

from what avaya says, you can admin a 3.1 ipo from the 3.2 admin software. i am not sure if when 3.2 manager is left running, it will handle tftp correct if it is used for a 3.1 ipo. maybe others have input on this.

i would think as long as the ipo, and vmpro releases match on the vmpro, and the ipo, you could install the 3.2 manager to make changes to the cfg. then again, it may have issues others have seen.

i do not think he was stating that the ipo would be running a mismatched release with the vm pro, just administering the older release ipo with the new admin software 3.2
i could be wrong in my interpretation of his posting.

 

[victor5908]

Actually,I was considering running 3.2 53 on IPO for the Twinning,Ring control,etc.
And mulling over finding a more stable release of VM Pro since 3.2 really gives you nothing new there.
Although the client app is a great idea.
In the past I performed plenty of Control Unit upgrades
and left VM Pro where it was.
Never really heard of any problems doing that.
I was looking for feedback in that regard as well,although it's great to here of no issue installs with the latest releases as well.
Any thoughts?Is there a particularly stable 3.0 or 3.1 VM Pro I should know about?

 

[janni78]

What stability issue do you have with VM Pro 3.2 28?

 

[victor5908]

Just what I've read here about the Lan connection going down,requring a reboot.
Hasn't happened to me but...

 

[intrigrant]

What you hear on this tek-tips is not a good base to make a representative conclusion.

Here you only see about 1% of all IP Office installers / users wich run into problems and/or have random programming / use questions.

As far as i know as a distributer then IP Office 3.2.53 has some minor bugs and VM Pro 3.2.28 may have some also but these are not often encountered in a good programmed environment and i think it is stable enough to use at any customer site.

 

[mattKnight]

Just what I've read here about the Lan connection going down,requring a reboot.

I agree with Intrigrant's point about this forum not being truely representative of the whole IPO world.

However, do not confuse this LAN issue with the stability of 3.2. As I understand it, this issue appears on a small number of IP 406V2 units, and is independant of the software level.

The software based fix for this has only just been developed and consequently is a private build of the 3.2 family of releases.

So if you have not experienced this issue with the LAN ports locking up on a particular 406, it is highly unlikely to occur because of an upgrade to 3.2.

Yes, there are bugs in 3.2 releases, but there are bugs in every release of every piece of software (not just PBX stuff either) i.e. it is not possible to test software to 100% reliabilty. I have not had any real stability issue the 3.2 systems I have out there.

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[aarenot]

i have written test plans, and executed test plans for software before with a little company called manahattan associates software. you find little bugs, but your intent is to try to mess with the software, and make it have an error when doing this. you try to think of ways to make it error, but it is impossible to think of every possible way to muck up the works. it takes field people to really find every way to mess with software, and no amount of testing will ever find every possible scenario to throw at a piece of software.
this forum is really just a small portion of the ipo world, and you find issues here which you may never see yourself. when i was testing software, they did respond sometimes with statements that they recognized the error, but the scenario i created was statistically improbable to ever occur in the real world, and so they would fix the issue down the road. not everything can be foreseen, and so software is not perfect, nor will it ever be. the reality is that the ipo is solid, but everything has a few cracks that you can find in time.

 

[victor5908]

Thanks for the input folks.
It all makes sense.I've installed tons of these without ever seeing the issues that have been discussed here.
We also lab-test these ourselves before installing in the field.Although we can't simulate the volume the system will be subjected to we can test all functions and some level of stability first.
Thanks again.