Older Mitel phones with 9.x 1

[AH64Armament]

We have a retail store customer that has over 800 remote phones - one or two at each of their stores across the US.
We're working with them to set a VM solution in their data center. Currently they are on an MXe version 2 running MivB 8.

Thinking ahead, we're planning the migration and the new system will be installed as MiVB 9.x and later on, 10.x

A Majority of their phones are 5215 DM, 5212 and they also have a few dozen 5312.

So with the new software, the 53xx phones are supported, but the 52xx will work, but not supported. Rumor has it that the 52xx will be written out on version 10.

We are working with our Mitel rep to get quotes to the customer for also switching them to NuPoint in a MiCollab environment. The sales folks are forcing the upgrade of all their phones for this.
My suggestion is to allow the customer to do this on their own schedule, not ramrod nearly 800 new phones into a project like this. Since the 5215 DM and 5212's are capable of SIP protocol, I suggested that.

The sales reps are saying NO... that is not supported at all, and that we MUST sell all new phones.

This is one of those customers that will switch to another solution in order to avoid replacing the phones... the Mitel reps aren't willing to see that.

SOOooo... to help save this customer, I'm willing to try to switch a 5215 DM to SIP and have it connect to a MiVB 8.x or 9.x. I can currently handle doing this with an 8.x system, but as of current, I don't have anything running 9.x. Can someone that is running 9.x help out and test it?

 

[kwbMitel]

First the 52XX phones will not work at all at rel 9.0. The software downloads they require to boot are not included and as such they will not work.

As for them working in SIP mode, I can't say for sure. They may still need a download to function even in SIP mode.

**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.

 

[nytalkin]

KWB is correct....you might ask Mitel for special pricing on the new sets to save the account. The 52xx phones will not work in either mode on the Rel 9.0

I suppose you're entitled to your opinion, I'm just not going to suppose very hard.

 

[AH64Armament]

nytalkin,
How would the PBX even know about the set type when all it will see is "Generic SIP". How would it know to not let it connect vs allowing a Polycom, Grandstream, etc connect?

If anyone has access to a 9.x system, I'd be curious to see if this is truly blocked.

Also, regarding NuPoint and other "emulated" phones - are they changing the set type for them? IP paging unit - programmed as an IP 5010.

kwbMitel - according to what we're told, they are supported until July 2020. The Mitel User Group raised a stink over them killing them off, they decided to keep them till July 2020. They aren't developing any features or fixes on them though.


Mitel is really shooting their dealers in the back with this.

 

[AH64Armament]

kwbMitel - the product bulletin says that they will support the users on 8.x until July 2020 if they have Premium Software Assurance.
refer to Product Bulletin number PB20170185 - Title: MiVoice Business - 5200 set support - Clarification

 

[Billz66]

Hi KWB this has been revised

the 52 series still have best effort

I think the firmware needs to be manually added to the MIVB after the migration to r9
there was another bulletin reversing their original decision

If I never did anything I'd never done before , I'd never do anything.....

 

[kwbMitel]

@Billz66 - I based my statements on the Rel 9 course documentation.

@AH64Armament - the phone does not store a boot load and needs to download one everytime. No bootload, no boot. It is not the system programming that matters. As Billz66 has revised, It seems that a bootload can be placed manually on the system post upgrade that will allow the phone to function short term. I have not read this document but you can trust Billz66, he's very reliable.



**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.

 

[AH64Armament]

I agree... you guys both have been a wealth of knowledge over the years. I'm not sure, but I believe I know both of you personally .
Not sure how to message someone individually, but if you'd like I can send the doc.

That makes sense that you'd have to manually load the files. We're like everyone else with this upgrade... scrambling to meet our customer's needs. We have a combined 500k phones across our customer base... many of which will not meet this spec.
I read through the upgrade training and took the cert update test over a month ago.. my reaction was that maybe I should go back into Aviation... or full time into physical security.

 

[kwbMitel]

If you know us that would be quite the feat.
I'm in Western Canada, you show up as Georgia US, and Billz66 shows as an Aussi.

I love how the internet makes the world smaller.

**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.

 

[Billz66]

Hi Kwb

Product Bulletin – PB20170185
"Following the communication that was made as part of the MiVoice Business 8.0 bulletin
(PB20160050), Mitel is clarifying the position regarding the go forward support for the 5200 series
sets. Initially we had communicated that the sets would no longer come into service following an
upgrade to MiVoice Business Release 9.0. This position has been modified, and this bulletin aims to
clarify the intent for all customers who continue to have these sets within their estate."

Following our initial announcement, we engaged in further discussion with the Mitel User Group and
several Mitel channel partners and as a result we have modified our position to facilitate a smoother
migration. As we plan the transition to MiVoice Business Release 9.0 (due in early 2018), Mitel now
intends to allow these devices*1 to come into service following the system upgrade but they will be
subject to a modified support policy.
Whilst we expect the phones will operate as normal, the 5200 sets will not have the normal support
level. Specifically, this means that, should issues arise after the upgrade to release 9.0, Mitel reserves
the right to not fix specific issues isolated to the 5200 series sets operation. In effect, this is a very
similar position as Mitel undertook on the Peripheral Node as we transitioned away from the older
technology to the newer product variants.


I will see if i can find the instructions for the TFTP files but its possibly just the same method that we have been using recently to get newer 69 series firmware uploaded

If I never did anything I'd never done before , I'd never do anything.....

 

[kwbMitel]

@Billz66 - based on the phrase (Due in Early 2018) that bulletin looks like it is quite old.

I'm not saying that it is wrong, but you would think they would have incorporated that into the Course Document

Here is the language from the course document released in August 2018

Obsolete sets
These phone types are no longer supported in MiVoice Business 9.0 as the software loads are not available for download from the system.
• 5001 IP phone
• 5005 IP phone
• 5010 IP phone
• 5020 IP phone
• 5140 IP phone
• 5201 IP phone
• 5205 IP phone
• 5207 IP phone
• 5215 IP phone
• 5220 IP phone
• 5240 IP phone
• 5401 IP
• 5550 IP Console
• 6600 Your Assistant Pro
• App Server
• SS4001
• SS401
• SuperConsole 1000
• SS4015
• SS4025
• SS410
• SS4125

**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.

 

[Billz66]

@Kwb , im sure i read it somewhere but cant find the doc

I have checked the Release Notes Software Release 9.0.0.193 Oct 2018

it says the ss 5235 and the ss5212/5220 are out ( they are before my time so im not even sure what they are)
it does list the Dual 5215 5220 5212/5224 with firmware 2.5.0.5 so i take that as those will be best effort supported

From memory the original statement regarding 52xx series was that mitel were no longer going to put any TFTP related files into the builds and as you said when they
try and connect - no tftp file , no boot

in our CXII recently migrated and then patched to 9.0.0.193 we have these files in the /var/mitelphoneloads


06/10/2017 01:30 AM 613,500 2064_mitel_meridian.bin
28/09/2018 02:41 AM 806,836 69xx_DectHeadset.st
28/09/2018 02:41 AM 87,716 69xx_lang_de.txt
28/09/2018 02:41 AM 21,607 69xx_lang_en.txt
28/09/2018 02:41 AM 90,361 69xx_lang_es.txt
28/09/2018 02:41 AM 90,858 69xx_lang_es_mx.txt
28/09/2018 02:41 AM 91,246 69xx_lang_fr.txt
28/09/2018 02:41 AM 88,138 69xx_lang_it.txt
28/09/2018 02:41 AM 21,607 69xx_lang_l1.txt
28/09/2018 02:41 AM 21,607 69xx_lang_l2.txt
28/09/2018 02:41 AM 85,588 69xx_lang_nl.txt
28/09/2018 02:41 AM 81,762 69xx_lang_pl.txt
28/09/2018 02:41 AM 84,131 69xx_lang_pt.txt
28/09/2018 02:41 AM 83,934 69xx_lang_pt_br.txt
28/09/2018 02:41 AM 81,273 69xx_lang_ro.txt
28/09/2018 02:41 AM 106,258 69xx_lang_ru.txt
28/09/2018 02:41 AM 79,820 69xx_lang_sv.txt
06/10/2017 01:30 AM 730,218 AMB_Flash.hex
06/10/2017 01:30 AM 450,712 APH_FlashUpdate.hex
06/10/2017 01:30 AM 522,302 APH_Project.hex
29/03/2018 05:00 AM 54,980 ASU_FPGA.bit
29/03/2018 05:00 AM 125,742 ASU_MAIN.img
06/10/2017 01:30 AM 7,164 AU.coef
06/10/2017 01:30 AM 8,536 AUv2.coef
28/09/2018 09:02 AM 857,024 BluetoothCordlessModule.bin
[highlight #FCE94F]22/11/2016 06:28 AM 353,248 BootIp5215Dpl_00.bin
22/11/2016 06:28 AM 420,360 BootIp5220Dpl_00.bin
22/11/2016 06:28 AM 582,568 BootIp5235Dpl_00.bin[/highlight]
28/09/2018 09:02 AM 1,043,144 BootIp5324Ttn.bin
28/09/2018 09:01 AM 1,045,312 BootIp5340.bin
28/09/2018 09:02 AM 2,878,552 BootIp5360.bin
28/09/2018 09:02 AM 1,045,424 BootIp5540.bin
26/05/2017 05:03 AM 1,046,224 BootIp5560Ttn.bin
22/11/2016 06:28 AM 355,352 BootIpNavigatorDpl_00.bin
06/10/2017 01:30 AM 8,708 BR.coef
06/10/2017 01:30 AM 6,300 BRv2.coef
28/09/2018 09:01 AM 192,020 CHNcharUnEnc.bin
06/10/2017 01:30 AM 4,624 CN.coef
06/10/2017 01:30 AM 5,656 CN2.coef
06/10/2017 01:30 AM 5,612 CN2v2.coef
06/10/2017 01:30 AM 5,612 CNv2.coef
28/09/2018 09:02 AM 326,350 CVM5505.bin
06/10/2017 01:30 AM 8,536 DE.coef
28/09/2018 09:02 AM 178,024 DectCordlessModule.bin
06/10/2017 01:30 AM 8,536 DEv2.coef
06/10/2017 01:30 AM 8,536 ES.coef
06/10/2017 01:30 AM 8,536 ESv2.coef
28/09/2018 09:01 AM 768 FirmwareVersions.txt
28/09/2018 02:41 AM 344 FirmwareVersions_69xx.txt
06/10/2017 01:30 AM 8,536 FR.coef
06/10/2017 01:30 AM 8,536 FRv2.coef
26/05/2017 04:49 AM 261,404 ipp5005.bin
26/05/2017 04:49 AM 131,336 ipp5005boot.bin
22/11/2016 06:29 AM 164,840 ipp510bootEnc.bin
22/11/2016 06:29 AM 265,328 ipp510main.bin
[highlight #FCE94F]22/11/2016 06:29 AM 173,216 ipp5230bootEnc.bin
22/11/2016 06:29 AM 375,864 ipp5230main.bin[/highlight]
22/11/2016 06:27 AM 225,824 ipptkbmain.bin
18/01/2018 02:37 AM 4,112,400 iprfp.bin
06/10/2017 01:30 AM 8,364 IT.coef
06/10/2017 01:30 AM 8,364 ITv2.coef
28/09/2018 09:02 AM 15,944 L2Boot5360Ttn32M.bin
28/09/2018 09:01 AM 99,384 L2Boot53xxeTtn8M.bin
28/09/2018 09:02 AM 99,456 L2Boot53xxTtn8M.bin
22/11/2016 06:28 AM 2,792 L2Boot_00.bin
[highlight #FCE94F]22/11/2016 06:28 AM 3,000 L2Boot_5235_00.bin[/highlight]
26/05/2017 05:03 AM 71,904 L2Boot_5560.bin
22/11/2016 06:28 AM 3,040 L2Boot_Navigator_00.bin
06/10/2017 01:30 AM 8,708 LA.coef
06/10/2017 01:30 AM 7,332 LAv2.coef
28/09/2018 02:41 AM 10,131,567 M695.st
28/09/2018 09:01 AM 5,598,984 MainIp5320.bin
28/09/2018 09:02 AM 6,134,872 MainIp5324Ttn.bin
28/09/2018 09:01 AM 5,534,432 MainIp5340.bin
28/09/2018 09:01 AM 6,224,256 MainIp5340e.bin
28/09/2018 09:02 AM 12,350,112 MainIp5360.bin
28/09/2018 09:02 AM 5,554,520 MainIp5505Ttn.bin
28/09/2018 09:02 AM 5,330,472 MainIp5540.bin
[highlight #FCE94F]22/11/2016 06:28 AM 929,848 MinetIp5215Dpl.bin
22/11/2016 06:28 AM 1,003,568 MinetIp5220Dpl.bin
22/11/2016 06:28 AM 4,347,104 MinetIp5235Dpl.bin[/highlight]
26/05/2017 05:03 AM 5,519,784 MinetIp5560Ttn.bin
22/11/2016 06:28 AM 1,421,480 MinetIpNavigatorDpl.bin
16/10/2018 08:33 AM 2,016 MinetProtocolVersions.txt
28/09/2018 02:41 AM 32,464,603 MINET_6920-enc.st
28/09/2018 02:41 AM 32,788,251 MINET_6930-enc.st
28/09/2018 02:41 AM 34,422,779 MINET_6940-enc.st
06/10/2017 01:30 AM 419,888 mips_mitel.tgz
06/10/2017 01:30 AM 675,888 mips_opensource.tgz
06/10/2017 01:30 AM 12,320 NA.coef
06/10/2017 01:30 AM 12,664 NA2.coef
06/10/2017 01:30 AM 9,740 NA2v2.coef
06/10/2017 01:30 AM 9,396 NAv2.coef
06/10/2017 01:30 AM 8,536 NL.coef
06/10/2017 01:30 AM 8,536 NLv2.coef
06/10/2017 01:30 AM 12,664 NZ.coef
06/10/2017 01:30 AM 11,804 NZv2.coef
22/11/2016 06:42 AM 524,288 pd11gl3.bin
22/11/2016 06:42 AM 1,179,648 pd11mtd.bin
22/11/2016 06:42 AM 917,504 pd11mtd3.bin
22/11/2016 06:42 AM 131,072 pi110001.bin
06/10/2017 01:30 AM 8,536 PT.coef
06/10/2017 01:30 AM 8,536 PTv2.coef
03/11/2018 09:29 AM 0 r9tftp.txt
28/09/2018 09:01 AM 1,047,168 Recovery5340e.bin
28/09/2018 09:02 AM 1,047,072 Recovery5505Ttn.bin
28/09/2018 09:02 AM 89,567 Sac5360AraAppStrings.txt
28/09/2018 09:02 AM 89,220 Sac5360ChiAppStrings.txt
28/09/2018 09:02 AM 91,897 Sac5360DutAppStrings.txt
28/09/2018 09:02 AM 90,436 Sac5360EngAppStrings.txt
28/09/2018 09:02 AM 94,373 Sac5360FrcAppStrings.txt
28/09/2018 09:02 AM 93,741 Sac5360FreAppStrings.txt
28/09/2018 09:02 AM 94,233 Sac5360GerAppStrings.txt
28/09/2018 09:02 AM 91,739 Sac5360ItaAppStrings.txt
28/09/2018 09:02 AM 90,454 Sac5360Loc1AppStrings.txt
28/09/2018 09:02 AM 90,454 Sac5360Loc2AppStrings.txt
28/09/2018 09:02 AM 92,097 Sac5360PoeAppStrings.txt
28/09/2018 09:02 AM 85,931 Sac5360PolAppStrings.txt
28/09/2018 09:02 AM 91,630 Sac5360SplAppStrings.txt
28/09/2018 09:02 AM 95,287 Sac5360SpsAppStrings.txt
28/09/2018 09:02 AM 91,373 Sac5360SweAppStrings.txt
28/09/2018 09:01 AM 87,225 Sac53xxAraAppStrings.txt
28/09/2018 09:01 AM 86,937 Sac53xxChiAppStrings.txt
28/09/2018 09:01 AM 89,548 Sac53xxDutAppStrings.txt
28/09/2018 09:01 AM 88,179 Sac53xxEngAppStrings.txt
28/09/2018 09:01 AM 91,892 Sac53xxFrcAppStrings.txt
28/09/2018 09:01 AM 91,289 Sac53xxFreAppStrings.txt
28/09/2018 09:01 AM 91,577 Sac53xxGerAppStrings.txt
28/09/2018 09:01 AM 89,519 Sac53xxItaAppStrings.txt
28/09/2018 09:01 AM 88,197 Sac53xxLoc1AppStrings.txt
28/09/2018 09:01 AM 88,197 Sac53xxLoc2AppStrings.txt
28/09/2018 09:01 AM 89,683 Sac53xxPoeAppStrings.txt
28/09/2018 09:01 AM 81,342 Sac53xxPolAppStrings.txt
28/09/2018 09:01 AM 89,201 Sac53xxSplAppStrings.txt
28/09/2018 09:01 AM 92,745 Sac53xxSpsAppStrings.txt
28/09/2018 09:01 AM 89,217 Sac53xxSweAppStrings.txt
28/09/2018 09:02 AM 56,367 sip5324ttnlang_de_DE.bin
28/09/2018 09:02 AM 52,710 sip5324ttnlang_en_US.bin
28/09/2018 09:02 AM 56,680 sip5324ttnlang_es_ES.bin
28/09/2018 09:02 AM 57,089 sip5324ttnlang_fr_FR.bin
28/09/2018 09:02 AM 56,561 sip5324ttnlang_nl_NL.bin
28/09/2018 09:02 AM 2,024 sip5324ttntone_AU.bin
28/09/2018 09:02 AM 2,024 sip5324ttntone_DE.bin
28/09/2018 09:02 AM 2,024 sip5324ttntone_FR.bin
28/09/2018 09:02 AM 2,024 sip5324ttntone_GB.bin
28/09/2018 09:02 AM 2,024 sip5324ttntone_MX.bin
28/09/2018 09:02 AM 2,024 sip5324ttntone_NL.bin
28/09/2018 09:02 AM 2,024 sip5324ttntone_NZ.bin
28/09/2018 09:02 AM 2,024 sip5324ttntone_US.bin
28/09/2018 09:02 AM 96,722 sip5340ttnlang_de_DE.bin
28/09/2018 09:02 AM 58,995 sip5340ttnlang_en_US.bin
28/09/2018 09:02 AM 97,368 sip5340ttnlang_es_ES.bin
28/09/2018 09:02 AM 98,100 sip5340ttnlang_fr_FR.bin
28/09/2018 09:02 AM 96,484 sip5340ttnlang_nl_NL.bin
28/09/2018 09:02 AM 2,024 sip5340ttntone_AU.bin
28/09/2018 09:02 AM 2,024 sip5340ttntone_DE.bin
28/09/2018 09:02 AM 2,024 sip5340ttntone_FR.bin
28/09/2018 09:02 AM 2,024 sip5340ttntone_GB.bin
28/09/2018 09:02 AM 2,024 sip5340ttntone_MX.bin
28/09/2018 09:02 AM 2,024 sip5340ttntone_NL.bin
28/09/2018 09:02 AM 2,024 sip5340ttntone_NZ.bin
28/09/2018 09:02 AM 2,024 sip5340ttntone_US.bin
22/11/2016 06:42 AM 39 slnk_cfg.cfg
06/10/2017 01:30 AM 15,932 UK.coef
06/10/2017 01:30 AM 15,588 UKv2.coef
06/10/2017 01:30 AM 2,166,672 vmlinuz

Its confusing i agree because there is a L2Boot_5235_00.bin file there ?

i no longer trust much of what mitel are saying until i have witnessed it for myself

i think we may still have 1 x 5212 handset in our office so i'll see if i can find it and will give it a go on Monday.

If I never did anything I'd never done before , I'd never do anything.....

 

[AH64Armament]

KWB I guess you're not who I thought you were LOL. But you're a wealth of knowledge in here... might have been from the old Mitel forum - I'm not sure if that's even alive anymore since they messed up the website to what it is now.

Billz66 - I know what you're saying about the 5235 phones - however, I've seen that issue firsthand - oops, I left one running on our system. The user was one of our data techs that one day (about 3 months after the upgrade) asked me if we could program the display on his phone so it would show what buttons were ringing.

I too agree with you on not trusting Mitel sales and marketing for anything these days. All they see anymore is $$$.
If you think this stuff is difficult to wade through, check out their hosted stuff... it's written by folks that don't know anything about IP Routing networking and firewalls, but tell you how to program your firewalls and such... at least the 3300 folks grew the product from a networking origin.

 

[Billz66]

confirmed 5212 connected to our MiVb 9.0.0.193
Main/Boot load 2.05.00.05 L2Boot Load 02.00.01.07

I had to statically assign an IP address to the phone as the MSL version of DHCP doesn't allow option 128 to be assigned
- should be ok with external DHCP



If I never did anything I'd never done before , I'd never do anything.....

 

[AlphaMann]

Regardless of the argument as to when the phones will be killed off a few things for the customer to note:
- 52XX series phones have been out of production for over a decade
- Mitel will definitely offer a deal on 800 phones.
- The deal combined with still having their controller will be massively cheaper than any new system from another provider.
- Phone systems of today are no longer like the ones of the past. How often do you upgrade your cell phone? How many computers or printers are still running in your office that are over a decade old?
- If properly managed soft-phones could be used at a cheaper price than physical sets

I very much doubt that a customer unwilling to spend a few dollars on an existing solution will want to pay more to go with someone else just on principle.