Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: melabum on September 10, 2014, 02:08:22 PM

Title: Problem with 5330 IP Phone
Post by: melabum on September 10, 2014, 02:08:22 PM
Hi all,

I am having challenges with Mitel 5330 IP Phone which were installed and connected to Mitel 3300 ICP , LX Controller running software rel. 9.0.

The installation is over 5 years old with over 450 IP phones (a mix of 5304, 5302, 5240, 5330 etc). All the phones have been working without problem until yesterday when all the 5330 IP phones  suddenly started to display "Application Loading" continuously even after the reboot of same. The phone are working (that is calls can be made and received on the phone) but the continuous loading of application is not allowing the phones to display the user's configured programmable keys features. There was no form of system software upgrade therefore, the observed behavior of the phones (only the 5330 IP phones) is strange. Please, any idea on how to overcome this challenge? Attached is the picture of our observation.

Thank you.

Melabum
Title: Re: Problem with 5330 IP Phone
Post by: jrg0852 on September 10, 2014, 02:16:20 PM
Have you tried the "Upgrade Bootrom All" maintenance command?
Title: Re: Problem with 5330 IP Phone
Post by: melabum on September 10, 2014, 02:38:07 PM
Hi Jrg0852,

I have not tried the command.  I have to do so tomorrow.


Sent from my GT-P1000 using Tapatalk 2

Title: Re: Problem with 5330 IP Phone
Post by: sarond on September 10, 2014, 07:54:25 PM
You could try "HTMLAPPUPGRADE" from the maintenance commands.
Title: Re: Problem with 5330 IP Phone
Post by: DARWIN on September 11, 2014, 08:11:01 AM
Also, what do you see under the Phone Applications tab of a 5330 under user & device config?
Title: Re: Problem with 5330 IP Phone
Post by: LoopyLou on September 11, 2014, 08:32:19 AM
Since its an LX is there any possibility of connecting a phone directly to the controller to eliminate any type of network issues? You would need a power supply. The only other thought I would have is you need a reboot as a next step.
Title: Re: Problem with 5330 IP Phone
Post by: lundah on September 11, 2014, 10:15:18 AM
Make sure the phones can pull the help files from the controller. These are stored in the "/db/HtmlApps/apps" folder on the controller. I don't remember what protocol is used to pull the files from the controller, but a Wireshark trace should tell you.
Title: Re: Problem with 5330 IP Phone
Post by: melabum on September 12, 2014, 10:17:42 AM
Dear all,
We have used the recommended commands; upgradeboot all, htmlappupgrade etc without solution. We have equally rebooted the 3300 LX controller yet there was no solution.
We have equally done the wireshack but do not know what to look out for.
Please, any idea on what to do next?

Sent from my GT-P1000 using Tapatalk 2

Title: Re: Problem with 5330 IP Phone
Post by: lundah on September 18, 2014, 02:23:49 PM
With Wireshark you want to look at the traffic between the phone, the controller, and the TFTP server (which may or may not be on the controller, it depends on how your installation is set up). You'll want to watch during the boot sequence and shortly after to ensure the phone is doing the TFTP pull requests from the TFTP server of the boot files, and then requesting the help files. FTP into the controller and look at the /db/HtmlApps/Apps folder for the filenames, and see if any of those files are being transferred to the phone.
Title: Re: Problem with 5330 IP Phone
Post by: melabum on September 18, 2014, 04:02:03 PM
Thank you Lundah,

Please, how exactly should I FTP into the controller for the stated filenames? I mean the steps required for the FTP

Sent from my GT-P1000 using Tapatalk 2

Title: Re: Problem with 5330 IP Phone
Post by: lundah on September 19, 2014, 04:25:24 PM
Use a GUI FTP client, I like FileZilla. Connect to the IP of the controller, using the same username and password you use to log in to program the system. Then just navigate to the folder you want (/db, /vmail, or /sysro). Be careful not to delete any files, though.