I recently burned way too much time implementing a Mitel IP phone system for a customer, and it should not have been this difficult. Doing it the "easy" way - giving each phone a static IP on the same VLAN as the rest of the network - is just sloppy, especially considering that the phones are happy to play well on a more properly segregated network.
Our local support person was a great and helpful guy, but he simply didn't have this information, and my impression was that we were expected to go to Mitel Professional Services for network consulting (presumably for a fee).
Um, no.
So, I wrote this paper to help the next guy accomplish what we did, and maybe the general direction will be useful for other kinds of IP phones: feedback and related experiences are welcome.
Tech Tip: Deploying Mitel IP Phones in a VLAN/DHCP Environment
Excellent article. We spent all day trying to get a new Mitel phone system installed because the IP Phones couldn't discover the DHCP server.
The issue was the DHCP options as we use a Win2008R2 DHCP server and VLAN's across multiple sites.
After reading you article we got it working! Mitel Support in the UK couldn't fix the problem!
Thanks
Paul.
Posted by: Paul Slade | May 26, 2012 at 06:50 AM
Now, I suspect many phones act this way, as it sort of makes sense. Is there a configuration file to look into? It's quite possible things are in there to define what VLAN it should use for the PC port.
Posted by: iOS Application Developers | June 12, 2012 at 12:30 AM
Anyone get the error "tftperr: Packet Send" after following these instructions? Its getting one the right vlan etc... not sure what I am missing.
Posted by: John White | August 06, 2012 at 09:09 AM
Great writeup! Do you know, do the Mitel phones work with the "switchport voice vlan " command on interfaces? I know this is typically how we set things up in a Cisco environment but not sure if it would play well with Mitel stuff or not... An example of this would look something like:
interface FastEthernet0/7
description Mike's phone
switchport mode access
switchport access vlan 1
switchport voice vlan 4
Posted by: root_taker | August 22, 2012 at 07:35 AM
Excellent article and instruction on this, what should otherwise be, a simple process.
Before finding this article, I spent the better part of an entire weekend, plus the Monday afterwards, searching google, digging through forums, testing phones, and calling every Mitel support tech who speaks Layer 2 and 3 that I could find.
What ended up saving us was your procedure (with the Magic Mitel String :) ) and a DHCP Helper Address entered into the router.
Posted by: Tonym Pa | September 14, 2012 at 11:53 AM
The information regarding Mitel IP phone system seems to be great.we using so many IP phone system with different facility which they provide on it.But after reading this blog for the mitel IP phone system which you provide them with a static IP on the same VLAN as the rest of the network is interesting.
Posted by: Phone system | November 21, 2012 at 07:12 PM
Don't stress yourself out in finding a way to solve this experimentation. Time will be the best solution there. Take it easy and for sure, you can find what you are looking for.
Posted by: how to attract women | January 03, 2013 at 07:07 AM
I wrote a similar article to this a little while back on doing DHCP with linux or Cisco DHCP services rather than windows. Check it out at http://technologyordie.com/mitel-phone-dhcp-configuration-with-multiple-vlans
Posted by: root_taker | January 10, 2013 at 07:57 PM
Excellent article.
I have been trying for months to move DHCP from the Mitel controller to our own microsoft dhcp server because I wanted to make use of the superscope option which the Mitel controller does not have. I was battling to get this to work.
I was just on the verge of calling a consulting company, when I came across this blog. I have actually saved my company some few bucks.
Thanks
Posted by: Mojalefa | July 14, 2014 at 01:14 AM
Thanks Steve , I got clear idea
Posted by: Sunil Shirurkar | February 03, 2015 at 01:50 AM
Excellent article! It was something I thought dominate.
I just migrate a domain from Windows Server 2000 to Windows Server 2008 R2 happening, of course, for Windows Server 2003. Everything has been great and we have corrected the details have been me. The company has urged Mitel PBX, one 3300, with about 320 IP phones. Everything works fine, just 5 IP 5224 phones are not working. We have reviewed the DHCP option 43 and 125 and is correct. It also works for other phones. Also, on each terminal or position where the phones do not work, they have tried other phone and operating properly.
If I connect one of these devices, which do not work, live telephone VLAN, then working properly, but not on the corporate VLAN. Only occurs 5 IP phones 5224 and another 25 are connected properly.
I thought it might be something with the OS version of the IP phone. What do you recommend we do?
My personal email is rodrigorojo2000@gmail.com
Best regards.
Rodrigo
Posted by: Rodrigo Rojo | November 21, 2015 at 07:04 AM
Hello
This article was really helpful. Anyone have experience deploying a Mitel 3300 with 5330 phones on Cisco SG500 or similar switches? When the server is first connected, the phones register, and all appears to be well, but after about 20 minutes, the phones lose the ability to connect to server, and go back into boot mode, until we reset the NIC on the server.
Posted by: why_mitel | December 16, 2017 at 09:53 AM