Hot Desking with mixed Versions 7.0/7.1 and 8.0 1

[Opsmgr06]

I have an issue got a with various versions of 7.0/7.1 on several systems I have upgraded the main systems to 8.0 UR5, although hot desking was tested from 7.1.4.9_1 and 8.0 UR5 all ok locally there are issues with the 7.0/7.1 systems where an 8.0UR5 Hot Desk Profile works on some systems but not on others in the Network even though the systems in question are both running 7.1.4.9_1
Mitel states the workaround is to statically IP the TFTP svr on the phone to the version 8.0UR5 MN3300, however I have tested this by homing a handset to the 7.0/7.1 system and logging in the 8.0 UR5 Hot Desk profile which works ok.
Mitel recommends upgrading all systems at the same time to the same load which causes an unacceptable risk factor issues as this network runs into double figures in terms of numbers of MN3300's.
I have thought about replacing the Main Load for phones on the 7.0/7.1 systems with the 8.0 UR5 file but unsure of the consequences on the MN3300 itself, or just changing the DHCP TFTP IP address to point to the nearest version 8.0UR5
MN3300.
Not sure if its the revison of phones or an inter version interoperability software issue, but this raises questions of backward compatibilty with Mitel MN3300's.
I am also a disciple of the same version O/S within a cluster methodology before anyone asks, it was not possible in this as I did not have full control of the MN3300 Network.
Any suggestions or relavent experiences would be gratefully receivedas this will help restore the faith as this has been a well received Network installation but this issue around upgrades and software versions with Hot Desking has shaken confidence badly in the Mitel MN3300.

 

[Mitel100]

To statically assign all phone with the TFTP address of the 3300 running 8UR5 is a laborious job.

I had this on one site and I pointed the DHCP scope for TFTP to the 3300 running V8, rebooted all the phones through the maintenance command line and all the phone got their new firmware.

__________________________

There is no 'I' in 'Team'
__________________________

 

[kwbMitel]

Although I accept your reservations with respect to upgrading all systems at the same time, I must point out that you jumped more than a couple of Revision levels of software.

7.0 Software is old enough to be on the cusp of non-support by Mitel

7.1.4.9 Is a mid level 7.1 Load (revision UR1 or UR2 I believe) 7.1.6.10 was UR3 and released Sept 2007

8.0 represented a Major overhaul of the software and functionality

8.0 UR5 Was released a full Year later and is at least 6 GR'd levels above the 7.1 system.

Your expectation that they will all play nice together is not reasonable and needs to be reassessed.

Get your hands on the release notes for all the releases between 7.1 and 8.0 UR5 if you want to see for yourself.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[kwbMitel]

Not to belabour the point but...

Here is the software release History.

As you will note 8.0UR5 is not particularily current

7.1 - 3300 ICP Release 7.1 UR3 (7.1.6.10_1) - RN Sep/17/2007
8.0 - 3300 Rel 8.0 (8.0.5.12) - RN Sep/6/2007
8.0 - 3300 ICP Release 8.0 UR1 - RN Nov/5/2007
8.0 - Mitel 3300 ICP Release UR3 8.0.9.18 Release Notes Mar/7/2008
All Releases - 3300 ICP Release 8.0 UR3-PR1 - RN Apr/8/2008
8.0 - 3300 ICP Release 8.0 UR4 (8.0.10.7_1) - RN May/26/2008
All Releases - 3300 ICP Release 8.0 UR5 (8.0.11.7) - RN Aug/5/2008
9.0 - 3300 ICP Release 9.0 UR1 Release Notes Nov/19/2008
9.0 - 3300 ICP Release 9.0 UR2 PR2 Release Notes May/14/2009
MCD 4.0 - SIP CoE SIP Interop Reference V30 Aug/14/2009
9.0 - 3300 ICP Release 9.0 UR2 PR3 Release Notes Jul/2/2009
9.0 - 3300 ICP Release 9.0 UR3 Release Notes Jul/16/2009
Various - MCD 4.0 - Rel 10.0.0.10_2 Release Notes Jul/14/2009


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Canuckvoip]

I agree with kwbmitel.
What type of controllers are in the cluster (CX/CXI/MXE/LX etc)? You say you have over 10 of them. How many of them do you have direct control over?
Based on the fact that they are running 7/8 software some or all may only have 256meg of ram. This will limit upgrade possibilities to R9 (very stable) without a ram upgrade. Current software is MCD4 but requires the 512 meg.

It's an old subject but we live in a software driven world. Oddly, people have no problem upgrading the Exchange/OCS/Bes/Lotus servers to get new features. This is no different. We are installing/supporting/upgrading VOICE servers.
The time is now to get the voice budget in sync with the data budget.
The customer should not be disapointed, whomever insinuated that purchasing a server and OS that would never need an upgrade needs re-education...
;>)

Dave

You can't believe anything you read... unless of course it's this sentence.

 

[Opsmgr06]

Thanks Mitel100 for giving a working example of what I was after,KWBMitel I know all the release notes and I know they are behind and that in the current situation the aim was to get everyone to a level playing field but we were let down
by the other maintainer some time back to get to the same 7.1 version.
As with all clients phones if they work they don't want to know about upgrades etc, unless you mention manufacturer support - I have SX2000s running N16 and CTU's!
It has taken over a year for approval to go 8.0UR5 despite new installations going in at 8.0UR5 due to hardware requirements MXeII and CX/CXi512's.
The next phase is to skip 9 and go straight to MCD 4.X and implement Hardware upgrades and system swapouts at the same time.
As can be seen there are always immediate Fix loads within a small time frame on software and clients do tend to question the second upgrade that quickly follows the first one.
Anyway Thanks for the quick responses this has helped me greatly

 

[kwbMitel]

Opsman06

You seem to know your stuff so I won't bore you with details. Within any Cluster it is reasonable to expect SW loads starting with the same number to cooperate. If you mix 7.x to 8.x or 10.x, you should expect issues until they are all at the same Main Release.

P.S.
Are you new to the forum? If so welcome, we need a few more experienced players.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[slapin]

Running 8.0UR5 withing a cluster of 9.0UR3 nodes just because Polycom IP4000/6000/7000 don't work properly. Actually the problem is multisite conferences. In version 9.0 SIP stack has changed dramaticaly and I'm stuck with a whole bunch of Polycome's which cannot be used for internal conferencing.
So far I have problems with SDS inside the cluster. Manual configuration of all things which normally done over SDS is pain.
The bottom line is that cluster must be on the same release level, no exlusions unless you must have it.