Safe to upgrade to 3.0?

[yipster]

Hello,

Is it safe to upgrade from 2.1.17 to 3.0.x?

Thanks

 

[mforrence]

Although there are no MAJOR show stoppers, if you're happy where you are and don't need any of the 3.0 features, I'd stay put (or upgrade to a more recent 2.1 release). I've learned more than one time (and it has finally sunk in) that upgrading for the sake of upgrading is not a great idea.
Mike

 

[stevea2Z]

my 2 cents, wait for a maintenance release

 

[IPGuru]

Mforrence has it right , only up grade if there is a definite need

"If it aint broke DONT fix it!

 

[yipster]

What new features are in 3.0?

 

[IPGuru]

Check the release documents for a full details.
Probably top of the list was Line apperance to keep US users happy

I suggest that if you need to ask then you do not need to upgrade.

 

[IPOUK]

This is GREAT advice - I have a call centre running V4 etc - all running ok, only a few minor issues. They had been on V2.1(24) for a long time, and reading all the issues with 2.1(15)and(24)I decided to get them on to V3 before any issues arose.

Call Appearances are now working as they should do (they claim that they never had any appearances working...I beg to differ though) so now agents are receieving more than 1 call at a time (they reckon agents in more than 1 group are receiving more than 1 hunt group call....I beg to differ), the queuing for some reason is going to a random queue/still queued message (VMPro) and just tiny little issues! Unless you need to upgrade, don't bother.

 

[crumthwacket]

Don't know if it's safe or not yet, but a major benefit is the elimination of the "call waiting" tone on multiline sets, which has been replaced by an abbreviated ring from the telephone for a second incoming call. It seems we had more complaints about that than any other problems the system had. The bridged appearances and coverage appearances are pretty good as well. The line appearance feature isn't worth the trouble - the system worked quite nicely with simple call appearances and button appearances of parked calls. We tried it at our office and removed it a few days later.

 

[kflounders]

We have upgraded many sites for the call waiting delete and the wonderful 5410s. No major issues.

 

[hohumIPO]

I Have major issues with VOIP all of a suden and offline programming 406V2's on version 3.0(40). These are as follows:
VOIP - when logging into a remote IP Office for a VOIP extension when the PBX IP Address is punched in the user drop down list may or may not populate (totally sporadic) and when I do rarely get to log in and make a call the person I call can hear me clear as a bell while I hear fragments of the conversation. Packet traces show malformed packets and a little EXE file called iClarity.exe now runs when voip is acitve and seems to coincide with the fragments of conversation.... very odd, looking further into this one (even happens on a 2Mg backbone with no apparent port blocking - anyone aware of isses with CISCO Pix firewalls that do the VPN'ing?)
OFFLINE PROGRAMMING - imagine this, put the units together... 406V2 DS + DS30's etc etc.... turn power on, flash unit, load firmware, begin programming online... After a few hours pack the unit's away and continue programming offline by opening via manager File>Offline>open config. When onsite load the config and the system works without issue for quite a few hours and then all of a sudden the box can no longer make calls using the default ?.dial shortcode (In Oz) and requires shortcodes for every number to be dialed in order to dial an outside line, the local is set correctly, flash the unit and test a default config - no problems, load origional config and problems are back. Imagine that and then try fixing it????????

 

[row1030]

There is a maintenance release 2.1(31) that may help.

 

[hohumIPO]

yes but that is only for DT's and these sites are DS sites