Server 2012R2 DHCP reservations problem with my VOIP equipment?
-
Assuming the reservations were made before the gateway was changed, and the phones were online before the change - i.e. they were working with the old gateway - perhaps the phones aren't respecting the updated information from DHCP.
Did you power off a phone wait 1 min, then power it back on and see if got the updated default gateway when using an old reservation?
-
@Dashrender Yeah, the gateway was different back when the reservations were made a couple years ago. I just tried another phone by deleting the reservation and recreating it, then rebooting and it gets the proper address.
The other gateway has been gone for at least 6 months. The phones have been for sure powered off multiple times for a few minutes. Whenever I update my poe switch firmware they power off for the duration of the reboot, sometimes up to 5 minutes I would guess. I just unplugged one phone for 10+ min and it still has the wrong address. I even reset another phone to factory settings and it still took the wrong address. That's why I think it's something with the DHCP server.
-
@bnrstnr said in Server 2012R2 DHCP reservations problem with my VOIP equipment?:
@Dashrender Yeah, the gateway was different back when the reservations were made a couple years ago. I just tried another phone by deleting the reservation and recreating it, then rebooting and it gets the proper address.
The other gateway has been gone for at least 6 months. The phones have been for sure powered off multiple times for a few minutes. Whenever I update my poe switch firmware they power off for the duration of the reboot, sometimes up to 5 minutes I would guess. I just unplugged one phone for 10+ min and it still has the wrong address. I even reset another phone to factory settings and it still took the wrong address. That's why I think it's something with the DHCP server.
OK - yeah weird... so DHCP is providing bad info... you could wireshark that shit to prove it.
-
Do you guys even use reservations for phones? I rarely even touch them, so I guess it wouldn't be that big of a pain in the ass to just let them get a random address from the pool.
-
@bnrstnr said in Server 2012R2 DHCP reservations problem with my VOIP equipment?:
Do you guys even use reservations for phones? I rarely even touch them, so I guess it wouldn't be that big of a pain in the ass to just let them get a random address from the pool.
I do not. I don't know why you would need to.
-
I don't ever reserve IP for phones.
-
@wrx7m said in Server 2012R2 DHCP reservations problem with my VOIP equipment?:
@bnrstnr said in Server 2012R2 DHCP reservations problem with my VOIP equipment?:
Do you guys even use reservations for phones? I rarely even touch them, so I guess it wouldn't be that big of a pain in the ass to just let them get a random address from the pool.
I do not. I don't know why you would need to.
idk I guess I just thought it would be easier to manage them. When we first got the phones I set them all up manually from the web interface and there was a lot of experimenting going on, I always knew extension 103 would be x.x.x.103, etc. if somebody had an issue, I knew their extension and automatically knew the IP of the phone.
-
@bnrstnr said in Server 2012R2 DHCP reservations problem with my VOIP equipment?:
@wrx7m said in Server 2012R2 DHCP reservations problem with my VOIP equipment?:
@bnrstnr said in Server 2012R2 DHCP reservations problem with my VOIP equipment?:
Do you guys even use reservations for phones? I rarely even touch them, so I guess it wouldn't be that big of a pain in the ass to just let them get a random address from the pool.
I do not. I don't know why you would need to.
idk I guess I just thought it would be easier to manage them. When we first got the phones I set them all up manually from the web interface and there was a lot of experimenting going on, I always knew extension 103 would be x.x.x.103, etc. if somebody had an issue, I knew their extension and automatically knew the IP of the phone.
I haven't dealt with anything other than shoretel for 9 years, now. I don't need to know the ip of any phone. The MAC is what is the most important. Everything is cross referenced so you can find pretty much everything if you only know one attribute. That's why I wouldn't care about the IP. Obviously, I haven't used freepbx, so I don't know how useful it is to know the IP there.
-
I never use reservations for phones.
Specifically with Yealink phones, I set the DHCP hostname value in the config file.
So when I am on the network, I can easily just ping ext103.domain.local and shit..
Or If I look at the DHCP server lease list, I see the hostnames listed as ext101, ext103, etc.
-
@bnrstnr said in Server 2012R2 DHCP reservations problem with my VOIP equipment?:
@wrx7m said in Server 2012R2 DHCP reservations problem with my VOIP equipment?:
@bnrstnr said in Server 2012R2 DHCP reservations problem with my VOIP equipment?:
Do you guys even use reservations for phones? I rarely even touch them, so I guess it wouldn't be that big of a pain in the ass to just let them get a random address from the pool.
I do not. I don't know why you would need to.
idk I guess I just thought it would be easier to manage them. When we first got the phones I set them all up manually from the web interface and there was a lot of experimenting going on, I always knew extension 103 would be x.x.x.103, etc. if somebody had an issue, I knew their extension and automatically knew the IP of the phone.
I also do not manually manage phones like that.
You were learning, so that is pretty common. But take the time now and move to centralized provisioning.
I guess I should write up some up to date posts on the subject.
-
@JaredBusch said in Server 2012R2 DHCP reservations problem with my VOIP equipment?:
I never use reservations for phones.
Specifically with Yealink phones, I set the DHCP hostname value in the config file.
So when I am on the network, I can easily just ping ext103.domain.local and shit..
Or If I look at the DHCP server lease list, I see the hostnames listed as ext101, ext103, etc.
Love this idea
