Mitel phone dhcp timeout

Mitel phone dhcp timeout DEFAULT

Contact US


Thanks. We have received your request and will respond promptly.

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!

  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Us!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Tek-Tips Posting Policies

Contact US

New Mitel 5360 Won't Pull DHCP - All other phones ok.

New Mitel 5360 Won't Pull DHCP - All other phones ok.

A D(IS/IT--Management)


Have a HX5000 with about 70% older digital phones and about 30% IP phones, mostly 5340's. Recently needed another phone so I bought a 5360 refurbished. First thing I did was plug it in with 8+9 pressed then did a restore to defaults. Phone rebooted, found the server, and did a firmware update. After the update it rebooted again but now won't get past DHCP Discovery. Just says:

DHCP: Discovery
Using Options 43:43

We have a VLAN setup for phones and all phones come into the switch untagged and we tag them at that level. I have both options 43 and 125 set (identical). I tried turning one off, rebooting the phone, then switching them, rebooting the phone, but no change. All other IP phones are fine. So I checked the DHCP server and there is a lease in there for it's MAC address and it's valid from when it first connected to the network (for its update). Tried deleting the lease and rebooting the phone again but same thing, stuck in discovery. Eventually goes to "DHCP Timeout" and tries again.

Just for the heck of it I manually assigned it a IP address on that subnet and the phone came right up and went into Calibration mode. Afterward it worked fine. Did a reset to defaults again, same issue.

Any ideas?

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.


Alright, I really despise it when technology out smarts me when it should be something simple to do.  

Here is my situation. We have a Mitel 5000, trying to add some new endpoints (5330e) to our system.  I plug it in and find out that I have DHCP options that I need to configure.  So I added my DHCP Option 43 and plug in the string that gives the end points all the required info on where it needs to communicate.;sw_tftp=;call_srv=;vlan=1;l2p=6;dscp=46

Short story long, the end points seem to step through the procedure of:

"Hey, I need an IP address"

DHCP server replies 

"Hey, here is your IP info" 

Then it just sits there with DHCP Discovery.

What a PITA..!  

Here are some of the trouble shooting steps I attempted:

I have manually configured the IP address of the end point and gave it it's need IP info contained in the magical DHCP Option String above and what do you know, BAMM!  I have an end point on my system and I can make calls and use this pretty new phone.  Yes, I know I can just use a hard coded IP address and manually key in this info to every freaking phone.  But I should have to..  

What am I missing...? 

As I bang my head against my desk, read through all of the stars... I would say that it is either a VLan issue or a Firewall issue.  

I really liked it when the phones were more dumber than me and all I had to do was plug it in...  Sheesh!

2 Replies

· · ·




Very similar issue in the past with a deployment of Mitel.  Ended up being a VLAN issue.  The DHCP was not passing to the voice VLAN we had assigned.  I cannot remember if the resolution was on the Mitel side or on our LAN.  It has been quite some time. 


· · ·

A Vigil



First off, I have to say that I'm quite jealous about the stache!

Secondly, thanks for your response.  After scouring the interweb, I might have to agree with you about the VLAN causing this havoc.  I'm sure that there is a need for a tag to a port on a switch trunk that I didn't implement. 


This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

  1. Auto followers instagram bot
  2. Sugar baby photo props
  3. Construction memes funny
  4. Baby bully dog

Phones on some switches cannot complete DHCP process


I have a Windows DHCP server (Server 2008 R2) handing out addresses for several scopes. One of those scopes is for some Mitel IP Phones. The phones are configured to use dhcp option 125 to get configuration information. When a phone starts up, it doesn't know what vlan to use, and so it just gets the default (untagged) vlan of whatever port it's connected to. The dhcp server gives it a response that includes option 125 information, and the phone is able to read what vlan it should use from this response. The phone then releases its original address and requests a new dhcp lease using the correct vlan tag. The phones also usually have computers connected to a pass-through port. The packets from the computers are never tagged, and so the PCs will stay on the original (untagged) vlan for the port. This has worked for us for years.

Problem and Symptoms

Somewhere in the last several weeks, something changed, and I'm not sure what. The phones will continue to work as long as they do not restart, meaning dhcp renew requests must be processed correctly. Phones connected to certain switches can even a survive a restart. Phones connected to other switches, however, will fail to complete the process when they reboot. All of our phones are using PoE that is backed up by a UPS, so it's been a long time since any have restarted. This means I have no idea when the problem first appeared. What I do know is that one phone failed when it restarted yesterday, and in troubleshooting it today we reset that switch closet. Now none of the phones on that switch are working (thankfully it's still a small number). I also know that things were working near the end of the January, when we moved a phone for an injured user to a temporary workspace on the ground floor.

As I watch a phone boot up, I can see it successfully get the first address. It then successfully reads the option 125 information, sets the correct vlan tag, and releases the original IP lease. It is even able to receive and accept an offer on the correct vlan from the server. However, that's where things stop. The phone has a message on the screen that says, "", but the Windows DHCP server has not recorded the lease and the phone never moves on. I can only guess that the DHCP REQUEST packet never reaches the Windows server, and so the phone is waiting for the final ACK from Windows that it's okay to continue.


I was finally able to get a phone working again. To do it, I had to first disconnect the computer. Then I set the phone's switch port to be untagged on the phone vlan, with no membership on the PC vlan. The phone will now reboot correctly. At this point, I can put the switch port configuration back where it should be, and as long as no one tries to call that number as I'm resetting the port, the phone never misses a beat. Then I can reconnect the computer. Obviously, that's not an ideal process, though since phones reboot so rarely I will be able to use it to get people working again until I can find the root cause. Offices are closed now for the week, and so this issue will actually be allowed to sit over the weekend (I don't have keys for individual offices where the phones are).

This phone I fixed is the service phone in the server room, connected directly to our core switch. It is possible the problem is an issue with routing or processing tags on the core switch, such that the workaround will not be effective on the remote offices where packets are first passed through (tagged by) other switches, but I'll be very surprised if that happens, given that I know it must be processing dhcp renewals and actual phone conversations correctly.

A twist is that leaving the port tagged on the PC vlan means that phone instead fails with the message "". I need to remove that vlan entirely for this to succeed.

Note: I have now confirmed that the work-around is effective in remote buildings. This leads me to suspect that my devices are somehow not assigned to the correct vlan. That fact that I experienced the problem on my core switch, and that it happened in several places on the network at about the same time, indicates that the core switch may be the problem. With nothing specific to look at, I'm scheduling a maintenance window near the end of the week to reboot the switch. I may also update the firmware.


Our core switch is an HP 5406zl. This switch handles inter-vlan routing. The Windows DHCP server is connected directly to the switch. Endpoint switches are connected to the core switch via fiber SFPs, and these ports are tagged for all vlans on both ends. The core switch configures each vlan with an setting that points it to our DHCP server, and a line so that the dhcp server will know what scope to use. These configurations, and the port configurations on the endpoint switches, have not changed in at least 16 months. We have had other switch and phone resets in that time.

Most of our endpoint switches are HP 2530 series. These switches seem to work correctly (phones on 3 different 2530's have restarted correctly today). It's older switches that have problems. We have one old 3Com 4200 and one 4210 that will not work. The service phone connected directly to the core switch mentioned earlier also would not work.


At this point my best guess is that a Windows update on the dhcp server changed the behavior, but I can't see how. Or possibly the core switch is not handling that REQUEST packet correctly, but I'm sure that nothing changed there, and it doesn't explain why only certain endpoint switches are effected. How can I resolve this issue?


Here is a dhcp log excerpt from a failed phone:

10,03/06/15,12:40:40,Assign,,,08000F197844,,3189088995,0,,, 11,03/06/15,12:40:40,Renew,,,08000F197844,,3189088995,0,,, 12,03/06/15,12:40:41,Release,,,08000F197844,,3189088995,0,,, 15,03/06/15,12:40:45,NACK,,,08000F197844,,0,6,,, 15,03/06/15,12:40:45,NACK,,,08000F197844,,0,6,,,

The 10.x.x.x addresses are the PC vlan (that choice pre-dates me at this place). Phones should get that kind of address at first, so that's expected. However, after the release message I also expect to find an offer for an address in the 192.168.16.x range, because I can see on the phone that an offer was accepted (unless I'm misinterpreting "ACC"). It's interesting that I never see the server try to issue an address like that, even though the phone thinks it received one.

I considered the idea there's a rogue dhcp server on the network (it hands out an address before the Windows server, but without the dhcp options needed by the phone to continue), but that doesn't explain why the phones work if and only if I completely remove any path to the PC vlan. I'll test for it anyway in the morning by connecting my laptop to a port set for the phone vlan, but if anyone else has a better explanation in the meantime, I'd love to hear it.

Here's a copy of the switch config:


Coming closer with an indecent gait, Jeanne began to touch me in the groin area. As if it should be. I was crazy.

Timeout mitel phone dhcp

I see an inflatable boat. There are two black men with machine guns in it. The ridge is white.

HOW TO: Set IP address in Mitel handsets (connection issue fix).

She continued to knead the hard shank of her clitoris. Ignoring her partner, she began to annoy the bump sticking out like a little finger with circular strokes. And then she felt a large ball of fire being born in her stomach. Feeling powerful shocks into the uterus through the thin septum, she began to moan, thanks to her partner for the pleasure they brought.

Similar news:

Lenka stopped washing the dishes, dried her hands with a kitchen towel and, freed from my hands, sat down on a stool by. The table. - Do you think that only the fucking can get up when they see in front of their nose a naked girl with an ass and a pussy in. The foreground.

1414 1415 1416 1417 1418