Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mitel 53xx issues #212

Open
kyle95wm opened this issue Aug 18, 2016 · 0 comments
Open

Mitel 53xx issues #212

kyle95wm opened this issue Aug 18, 2016 · 0 comments

Comments

@kyle95wm
Copy link

Hi there,

Not sure if this is the right place to put this so here goes!

To give you a context on my server setup, I have a DigitalOcean $5 server running CentOS 6.8 with the latest IncrediblePBX (therefore we're dealing with OSS Endpoint Manager) with Asterisk 13.x and FreePBX 12.x.x

Ive also managed to setup a TFTP server which is accessible only to the whitelisted IP's, so phones can register no problem (when provisioned manually)

However I've run into a problem with provisioning a couple of phones.

The first phone I have is a Mitel 5330e running:

Main Load Version: 06.02.00.01
Boot Load Version: 06.02.00.01
L2Boot Load Version: 06.01.00.10
DSP Load Version: 3.0.0.20

For this phone, I can manually set the provisioning server (I don't have a router capable of proving DHCP option 66 (my Asus RT-AC87R runs dnsmasq though and has SSH access so if anyone has any brilliant ideas let me know)), which the phone connects to fine (I can tail the output of /var/log/messages and see that the phone IS grabbing the needed files over TFTP (well. with the exception of the firmware since I don't have access to that)

After it has grabbed the configs, the phone never has any SIP accounts set up. So trying to provision this phone automatically is pointless

Now let's move onto phone 2

This phone is a Mitel 5304 and is running:
Main Load Version: 06.02.00.07
Boot Load Version: 06.01.00.09
L2Boot Load Version: 06.01.00.09
DSP Load Version: 3.0.0.21

With this phone, two things happen upon configuring the TFTP server. It grabs the needed files with the exception of the firmware since I don't have access to it like I said before. It reboots the phone and I see my display name of my extension so I think "yippee it actually works!" only to find out that it in fact does not work, no SIP accounts like our first phone, but it did configure the display name.

Now you may be thinking "but he said two things happened". You're correct about that and let me tell you what it is. For SOME reason after the phone has provisioned with the server, I am "locked" out of the web portal (fairly limiting but it gives me access to configure my SIP account if needed) and the default username "admin" and password "5304" DO NOT work. I tried looking through the configs to see if there was a username and password string anywhere that was pre-set and there was none

If any Mitel junkies have any pointers, or perhaps can point me in the general direction on how to get firmware for my phones, I would be most grateful for any help I can get. Remember, I can NOT get firmware officially from Mitel. If one of you has access to the firmware, you should consider adding it to the GitHub so others can benefit as well.

So please, help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant