Advice please - What version to upgrade to. 1

[daffymd]

We have a customer who is running a single IP403 - 1.4(25) with a POTS30 and POTS16 - both 3.4(25). They also use Phone Manager Pro - 1.4.6.

We are going to site to look at problems with Phone Manager Pro on various machines and thought that we really should be upgrading as 1.4 is rather old now.

So I just wanted some thoughts as to what version you would recommend.

 

[IPGuru]

1.4(27)
but if you want support from Avya in future you will need to go to V3.0(59)

 

[aarenot]

If it isn't broke, don't fix it.

 

[kholladay]

I wouldn't even bother with an upgrade until 3.1. As aarenot stated "If it isn't broke...". But since 3.1 is the final "free" upgrade you might as well get them to it once you feel comfortable with it's stability.

Kyle Holladay
Certified: ACACN, ACSCI, ACSCM, TIA-CTP
"If it worked the way it should you wouldn't need me

 

[daffymd]

Thanks to you all for your thoughts on this. Are Avaya going to be charging for upgrades after 3.1 then?

 

[kholladay]

IP Office Release 3.1 will be downloadable and usable free of charge however please note that it
is Avaya’s intent to charge for future software releases after release 3.1 via a license key
upgrade."

IPO 3.1 is available for download on Avaya's web site now.


Kyle Holladay
Certified: ACACN, ACSCI, ACSCM, TIA-CTP
"If it worked the way it should you wouldn't need me

 

[cobragb]

Has anyone upgraded a 3.0 system to 3.1 yet? any problems??

 

[kholladay]

We have been running 3.1 for a few months and nothing to report. At least nothing that we weren't experencing with 3.0(59) as well.

Kyle Holladay
Certified: ACACN, ACSCI, ACSCM, TIA-CTP
"If it worked the way it should you wouldn't need me

 

[edhead]

Upgraded from 2.1(24)to 3.1 last night. Only problem so far is that we had a Group Page button that was programmed on our 4412D+'s and it was programmed as Group Page - "Group Name" 3.1 doesn't like the "Group Name" and we had to change it to Group Page "Group#".

That and our 4400 sets no longer work, but that was in the release notes.

 

[aramsay]

Upgraded from 3.0.59 to 3.1.29 today, and no problems as yet.

The twinning feature works well; I no longer have to remember to divert my desk phone to my DECT phone when I leave the office. I would like the ability to transfer between the main phone and the DECT, but if I enable that it allows one phone to ring when I'm on the other. It would be nice if it implemented a DND exception list, but it doesn't.

Apart from that it all seems fine.

 

[sizbut]

!Try setting the number of twinned calls down to 1 in the user settings. Having it set to 2 (the default) is meant to allow you to use twinning and call waiting.

 

[aramsay]

If it's set to two; it allows any other calls to come through

If it's set to one; it doesn't allow you to transfer from your primary to secondary handsets.

Catch 22! In an ideal world, if set to one, it would allow you to transfer from primary to secondary and vice-versa.

 

[sizbut]

I'll have to set one up tomorrow and play again - you shouldn't need to transfer, should be able to hold/park on one and then unhold/unpark on the other - should never need to dial the number of the twin. I know when originally speced for field trials twinning wasn't supposed to work with multiple call appearance and then somewhere along the line that changed.

 

[aramsay]

Ah; I've not actually tried that.

So (if I understand what you're saying) I should be able to take the call on my 5410 desk phone. Press the HOLD button to put the caller on hold, pick up my DECT (analogue) phone and press RECALL to retrieve the call.

I'll give it a go in the morning and report back.

 

[aramsay]

sizbut,

You are quite correct, you can hold a call on one station and unhold it on the other.

It would be nice if you got the stuttered dial tone on the analogue to know that there was a call on hold, or the H on the display on the 5410, but I can live without that.

 

[greskit]

The 2.1.44 version is stable and has alot of software fixes in it. Also, it is still supported. I was told by Tier 3 last week that, they will be supporting 2.1.48(coming), 3.1.29(out), and 3.0.68(coming).
Don't forget the firmware update on the 403.