Yealink Forums

Hello,

my W52P was running like a charm for monthes till today where I had to power it down. After few hours, I plugged it back on power and since, network is no more working, I have the "Invalid IP" message on the headset screen.

I did a base reset as well as a hard reset. What I saw in captures is

1 0.000000 0.0.0.0 -> 255.255.255.255 DHCP 590 DHCP Discover - Transaction ID 0x72fc0a1f
2 0.000202 192.168.10.250 -> 192.168.10.106 DHCP 384 DHCP Offer - Transaction ID 0x72fc0a1f
3 0.037272 0.0.0.0 -> 255.255.255.255 DHCP 590 DHCP Request - Transaction ID 0x72fc0a1f
4 0.071438 192.168.10.250 -> 192.168.10.106 DHCP 390 DHCP ACK - Transaction ID 0x72fc0a1f
5 243.539260 0.0.0.0 -> 255.255.255.255 DHCP 590 DHCP Discover - Transaction ID 0x8d83aa7e
6 243.539467 192.168.10.250 -> 192.168.10.106 DHCP 384 DHCP Offer - Transaction ID 0x8d83aa7e
7 243.586918 0.0.0.0 -> 255.255.255.255 DHCP 590 DHCP Request - Transaction ID 0x8d83aa7e
8 243.626360 192.168.10.250 -> 192.168.10.106 DHCP 390 DHCP ACK - Transaction ID 0x8d83aa7e
9 246.732890 192.168.10.106 -> 192.168.10.254 DHCP 590 DHCP Request - Transaction ID 0x8d83aa7e
10 246.772809 192.168.10.250 -> 192.168.10.106 DHCP 390 DHCP ACK - Transaction ID 0x8d83aa7e

where IP 192.168.10.106 is the one for the W52P, fixed in dhcp server. At this time, all seems good, the 3 lights are green. After 30 seconds or so, the bases losses the network and the LAN led is blinking. Rebooting or other manipulation does nothing, to get back a dhcp trace I have to reset the base again.

I tried with fixed IP, no more luck. The FW version is 25.73.0.25. After a reset I could register the handset again, so problem seems to lie only on network interface.

Thanks for any clues.

Regards

Daniel

Hello Daniel,

Can you please try connecting the W52P to another network environment?
Also please try disabling LLDP feature when you can access it.

Regards,
James

Hello James,

Indeed, on another network it's working after a base reset. I disabled LLDP and went back to my network, problem still here :-(
My switch is a Netgear GS728 TP. I tried with and without the power supply. I also tried to connect it to an Asus RT-N16 Wireless/switch point: no changes.

Why suddenly this problem appears? How to solve it? The dhcp server is dnsmasq running on a Linux Debian 8.2 server.

Thanks for your support.

Hello,

no one on this ?

Regards

Sorry for the late.

Can you please set syslog of base to 6, then connect it to your network. After the issue happens, connect it to a working network and export the log to us.
Thanks

James

Hello,

I can't send you the logs as as soon as the base is connected to my network the problem appears and stays even when connecting bases back to the working network :-( !
I have to do a factory reset to make the network going back to life and this manipulation destroys the current logs.

In the mean time I upgraded to 25.73.0.40 firmware, no changes. I tought it could be a network cable failure, tried 3 of them including new one, no changes.

Other tip ?

Hello,

anyone concerning this matter ?

Regards

Is the Yealink support still alive ? Should I considere the phone as dead ?