Unable to Install "New" Mitel 5324 Phones

[SomeUserName]

The management of the building where I work bought two refurbished Mitel 5324 phones to replace two damaged Mitel 5324 phones. The PBX is an old Mitel 3300 ICP that was installed about 15 years ago by one of my predecessors who no longer works there. For a bit more context, I work for a company that rents space in the building and provides technical support "on the side" to the management of the building. I don't have any training on Mitel PBXs, so forgive me if I sound like a complete novice.

I have deleted and recreated the extension of one of the "old" Mitel 5324 phones and added the mac address of one of the "new" Mitel 5324 phones, but it always gives me an "L2 DL Error" after trying to download something called "main" from tftp.

As recommended on this forum, I tried pressing the # key during boot to get into the special configuration menu. I did several tests, tried adding the network parameters manually, tried changing the phone mode from mitnet to sip, but nothing worked. Ping test to the PBX worked fine. DHCP trace returned the parameters set on option 125. Finally, I tried deleting "main" on the phone, but it gives the same error, and the special configuration menu is now inaccessible. I also tried logging into the tftp server on the PBX with filezilla and it worked.

Since none of the above worked, I'm guessing that the problem is related to the firmware version of the "new" phones being much more recent than that of the "old" phones.

Below are the versions I was able to extract from the two different phones.

Mitel 5324 "Old"

Main 02.00.02.07
Boot 02.00.02.07
L2Boot 02.00.00.31
DSP 2.1.0.3

Mitel 5324 "New"

Main 06.05.00.11
Boot 06.04.01.02
L2Boot: 06.01.00.09
DSP 3.0.0.21

From what I can gather from the posts on this forum, I either need to downgrade the firmware on the "new" phones or upgrade the PBX so that I can then upgrade the "old" phones to the same version as the "new" phones, but to be honest I don't know how to do that or if it is even possible, and the PBX documentation is unhelpful.

1) What is "MOL" and where or how do I download the upgrade .exe?

2) How do I know what version the PBX is on and if it's possible to upgrade it?

3) Is it possible to downgrade the "new" phones? <- this would be preferable

4) If it's not possible to downgrade, how do I upgrade the PBX and the "old" phones?

[lundah]

What software version are you running on the 3300? Based on the "old" phone firmware, this may be a very old release. To upgrade the 3300, you'd have to work with a Mitel partner/dealer to get the system upgraded, which may require new controller hardware as well depending on what the current setup is.

[SomeUserName]

To be honest, I don't know what's the version of the software or how to check it. That was one of my questions.

------

Update: Just remembered to check the logs for reboot events. Here's a few messages I found.

MXe Platform (172.17.xxx.xxx) Booting Software version: 9.0.3.15

Boot File: /partition1/RTC8260

MIPS SP Startup, FAILURE - no Layer 2 Switch IP addr

The link from MCECAAx MN3300 Controller at location 01 1 01 Active to MC266Ax Communication Proc at location 01 1 10 is now in SCANNING mode.

The link from MCECAAx MN3300 Controller at location 01 1 01 Active to MCSTHAx ICP Communications at location 01 1 11 is now in SCANNING mode.

The link from MCECAAx MN3300 Controller at location 01 1 01 Active to MC266Ax Communication Proc at location 01 1 13 is now in SCANNING mode.

The link from MCECAAx MN3300 Controller at location 01 1 01 Active to MC269Ax Universal E1 at location 05 1 02 is now in SCANNING mode.

MC266AA Communication Proc at location 01 1 10 installed

The link from MCECAAA MN3300 Controller at location 01 1 01 Active to MC266AA Communication Proc at location 01 1 10 Active is now OPEN. 

StartUp T.38 licences configured, T.38 DSP module(s)

------

This is all the information I was able to find regarding the hardware on the system from the web administration tool. I don't know if any of it is useful.

System Hardware Compute Cards

Slot ID:    1
PCB Assembly and Rev Level:    56007690 RA.8
Core Speed:    450000000
Bus Speed:    100000000
Memory Size:    536870912
MAC Address:    08:00:0f:xx:xx:xx
IP Address:    172.17.xxx.xxx
BOOTROM Rev:    2.3/11 Jan 13 2009
Post Rev:    2.3/11 Jan 13 2009

System Hardware Modules

Slot Number:    1
Module ID, Driver ID:    1, 1
Minimum Reset Timing:    0
Card Description:    T1/E1 W/DUAL INBAND LOOPBACK
PCB Assembly:    143271301
PCB Revision Level:    R3
Processor Type:    n/a
Processor Speed (Core, Clock):    0, 0
MAC Address:    00:00:00:00:00:00
Country Code:    NA
Variant ID:    2
Serial Number:    n/a

------

Slot Number:    7
Module ID, Driver ID:    93, 6
Minimum Reset Timing:    100
Card Description:    4 SHARC 21363 DSP
PCB Assembly:    n/a
PCB Revision Level:    n/a
Processor Type:    ADSP 21363
Processor Speed (Core, Clock):    200, 25
MAC Address:    00:00:00:00:00:00
Country Code:    NA
Variant ID:    2
Serial Number:    n/a

------

Maintenance Commands

>VERSION

3300 ICP Call Control 39.0.3.15                                                 
                                                                               
MC Complex S/W & Data                                                           
---------------------                                                           
Main Controller -------:  MAINIP3K 39.0.3.15 Wed 17-Jun-2009 20:05             
MC Initialization -----:  SXIP3KINIT 39.0.3.15 Wed 17-Jun-2009 17:29           
Country Tone Plans ----:  COUNTRYTS 39.0.3.15 Wed 17-Jun-2009 15:19             
Package Master Data ---:  PKGMASTER 39.0.3.15 Wed 17-Jun-2009 17:25 si         
                                                                               
PC Complex S/W & Data                                                           
---------------------                                                           
Peripheral Controller -:  PER 39.0.3.15 Wed 17-Jun-2009 16:20 si               
Country Dependent Data :  PERDAT 39.0.3.15 Wed 17-Jun-2009 17:23 si             
Digital Set Data ------:  DNICDEE 39.0.3.15 Wed 17-Jun-2009 17:19 si           
DSP DTMF --------------:  DSPDTMF.F02 13-Sep-2002 11:53 f02/dspdtmfa           
DSP FSK ---------------:  DSPFSK.C05 06-Sep-2002 11:39 c05/dspfska             
                                                                               
Line Card S/W                                                                   
-------------                                                                   
DNI Line --------------:  DNICLC 39.0.3.15 Wed 17-Jun-2009 16:22 si             
                                                                               
DSU S/W                                                                         
-------                                                                         
Conference ------------:  CON.F01 01-FEB-1986 11:03 [SX.CON.F01]CON             
CEPT MSDN/DPNSS -------:  CEPTDPNSS.J01  07-May-2001 19:52 j01/ceptdpnss       
CEPT CAS --------------:  CEPTCAS.G01  07-May-2001 19:52 g01/ceptcas           
DS1  MSDN/DPNSS -------:  DS1DPNSS.K01  07-May-2001 20:03 k01/ds1dpnss         
DS1  CAS --------------:  DS1CAS.K01  07-May-2001 20:02 k01/ds1cas             
CEPT 2 MSDN/DPNSS -----:  SX2KVDSU 21-NOV-2007 15:36 [VER-1.2.3.5]             
CEPT 2 CAS ------------:  SX2KVDSU 21-NOV-2007 15:35 [VER-1.2.3.5]             
DS1 2 MSDN/DPNSS ------:  SX2KVDSU 21-NOV-2007 15:36 [VER-1.2.3.5]             
DS1 2 CAS -------------:  SX2KVDSU 21-NOV-2007 15:35 [VER-1.2.3.5]             
PRI E1 ----------------:  NSU_PRI 9-JUN-2008 14:41 [VER-1.7.1.7]               
PRI T1 ----------------:  NSU_PRI 9-JUN-2008 14:41 [VER-1.7.1.7]               
R2 --------------------:  NSU_R2 17-JAN-2008 14:45 [VER-7.1.2.2]               
                                                                               
System Data                                                                     
-----------                                                                     
Form Descriptors ------:  FORMDESC 39.0.3.15 Wed 17-Jun-2009 15:24 si           
                                                                               
Language Tables                                                                 
---------------                                                                 
English Language Tables:  ENGLISHLT 39.0.3.15 Wed 17-Jun-2009 15:26 si         
English Sets Strings --:  DNITABE 39.0.3.15 Wed 17-Jun-2009 16:22 si           
French  Sets Strings --:  DNITABF 39.0.3.15 Wed 17-Jun-2009 16:47 si           
Italian Sets Strings --:  DNITABI 39.0.3.15 Wed 17-Jun-2009 16:25 si           
German  Sets Strings --:  DNITABG 39.0.3.15 Wed 17-Jun-2009 16:51 si           
LA Span.Sets Strings --:  DNITABS 39.0.3.15 Wed 17-Jun-2009 16:40 si           
Dutch   Sets Strings --:  DNITABD 39.0.3.15 Wed 17-Jun-2009 16:29 si           
Rom.    Sets Strings --:  DNITABR 39.0.3.15 Wed 17-Jun-2009 16:54 si           
BR.Port.Sets Strings --:  DNITABBR 39.0.3.15 Wed 17-Jun-2009 16:33 si           
PT.Port.Sets Strings --:  DNITABPT 39.0.3.15 Wed 17-Jun-2009 16:36 si           
EU.Span.Sets Strings --:  DNITABES 39.0.3.15 Wed 17-Jun-2009 16:43 si           
Russian Sets Strings --:  DNITABRU 39.0.3.15 Wed 17-Jun-2009 16:58 si           
Swedish Sets Strings --:  DNITABSW 39.0.3.15 Wed 17-Jun-2009 17:01 si           
Polish  Sets Strings --:  DNITABPL 39.0.3.15 Wed 17-Jun-2009 17:05 si           
S.Chi Sets Strings --:  DNITABSCH 39.0.3.15 Wed 17-Jun-2009 17:09 si           
Local1  Sets Strings --:  DNITABLOC1 39.0.3.15 Wed 17-Jun-2009 17:12 si         
Local2  Sets Strings --:  DNITABLOC2 39.0.3.15 Wed 17-Jun-2009 17:16 si         
                                                                               
Firmware Version                                                               
----------------                                                               
SS4025 Firmware ver ---: Main  6.3                                             
SS4025 Firmware ver ---: Main  8.21                                             
SS4025 Firmware ver ---: Main  9.12                                             
SS4125 Firmware ver ---: Main  6.3                                             
SS4125 Firmware ver ---: Main  8.21                                             
SS4125 Firmware ver ---: Main  9.12                                             
SS4150 Firmware ver ---: Main  6.3                                             
SS4150 Firmware ver ---: Main  8.21                                             
SS4150 Firmware ver ---: Main  9.12

------

>PLATFORMTYPE
MXe

[acejavelin]

Wait... are you actually on the OLD 3300 MXe/MXeII version 9 software, and not an MCD/MiVB platform (MXe III)?

If that is the case, it looks like you are trying to use 5324e phones and not 5324 phones... The "e" portion means gigabit and are a much later hardware version than the original 5324 devices, but they were not supported properly in the older software that was discontinued 10~15 years ago... you would need old style 5324 phones (without the "e").

[SomeUserName]

Is there any way to tell the difference between mitel 5324 and mitel 5324e? Both the new and old phones say Miltel 5324 with no e. Also, I can't find anything online about 5324e.

[johnp]

Don't know of any 5324e versions, old 2 level may not go to latest without some help, just MHO

[lundah]

Yeah that's the old version 9 release, I'm very familiar with that version as I ran it on a very large network for a while in a previous job.

I think the issue is your new phones have a much more recent firmware version on them, and I don't know with 100% certainty how to downgrade them.

You may be able to do an "Erase Main Load" from the Diagnostics menu in the Tools and Features config menu. Be very careful with this as you can brick the phone with this procedure. You need to be absolutely sure your DHCP settings are correct, and preferably have the phone on the same subnet as the controller, then do the following:

• Enter config mode (hold down the up arrow during boot; or hold both the up and down arrow keys, release the up arrow, then while continuing to hold the down arrow key, enter "234" (CFG) on the keypad)
• If you see "Configure Phone?", press * for Yes
• At "Network Parameters?", press No until you get to "Tools and Features?", then press * for Yes
• At "Erase Pin?", press # for No until you get to "Diagnostics?", then press * for Yes
• At "Last Asser/Except", press the up arrow key, you should see "Erase Main Load", press * to Select

The phone will erase it's firmware and reboot. At this point it has no firmware loaded and must download a fresh copy from the controller. If for whatever reason it can't do that, the phone is essentially bricked until you can correct whatever network issue is preventing the phone from downloading the firmware from the controller.

[SomeUserName]

That is what I did when all else failed. I deleted "main" from the phone and put the phone on the same /24 network as the PBX. It starts downloading "main" up to 1467 (presumably KB?), but still gives the same "L2 DL Error". And as I said, I connected to the tftp with filezilla, logged in and downloaded stuff just fine.

[lundah]

In that case it may not be possible to downgrade those phones to the firmware running on your 3300. The "right" thing to do would be to upgrade the 3300, but you need a RAM upgrade to 1GB (your system currently has 512MB), and active software assurance coverage, which I'm assuming you do not have otherwise you'd already be on a more current release. You'd have to contact a Mitel dealer/partner (preferably the one who installed the system originally) to get the system upgraded.

[johnp]

Here is a link to 4.1 firmware. You might try going to it first

https://drive.google.com/file/d/1q9QeCcQ4K67r5GmnJIWcYfFPvhjS01DI/view?usp=sharing