2.704 Phone Code and DHCP Conflict

[randyb19]

I recently pushed the 2.704 firmware (still burning in 2.8 in our lab) to all phones and suddenly I've had three cases of 'DHCP Conflict' errors at sites that have never had issues before. I am wondering if this is an issue with the phone code.

I understand what is entailed in that error and I know for a fact that there are no hard coded phones at the sites. What is truly weird is, two of the cases happened at one site. The first time I could see the phone hit the TFTP server with a x.x.x.108 address, but still came up with the error. After about five minutes of not touching the phone, it connected to the PBX, dial tone and all. The second instance, a week later, different phone, different floor, same building, the phone came across the TFTP server with x.x.x.100 as the address, but I still cannot get it to come online.

As I said, I know for fact that there are no hard coded phones on that site, and they were fine until I loaded the 2.704 code.

Any help is appreciated.

 

[tlpeter]

ping the ip adres when the phone is not connected
then you seeif the adres is already in use
if it is then give the phone a reset
or wait till the dhcp lease time is over (or manualy delete it)



______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[Gielo]

You have a conflict on your DHCP server - not on the phones

 

[randyb19]

I now know it is the DHCP server, but the timing made it hard to rule anything out. We excluded an IP from the scope and that seemed to clear up the issue. It's just finding the device that was using the IP, or figure out if the DHCP server had an issue releasing the IP. I've seen PCs and Laptops bleed over into the voice VLAN, so who knows. Thanks for the help.

 

[Gielo]

Also had this issue and eventually find that there were a second DHCP server on the network. What happened is that the Avaya phones tried to connect to the wrong DHCP server which did not have a option 176. Then I got the same error