Yealink W52 bases - power light but no communication

[dgsmith]

A few years ago we bought 4 Yealink W52 bases with a few of the handsets. Recently, two of them went offline and despite going through the suggested factory reset procedure, I can't get them to detect on the network or show signs of data activity. They both power up (mains and poe) and the reset procedure appears to progress as suggested, but they fail to be detectable or show in dhcp/3cx.

Am I looking at two units that whilst not totally dead, are as good as dead if I can't establish any connection to them, or is there perhaps some secret few know about that can get them back into action?

[bald_pig]

I've had similar with broken ethernet cables before, phone still got poe, but the break was on another wire so no ethernet.

[dgsmith]

I've had similar with broken ethernet cables before, phone still got poe, but the break was on another wire so no ethernet.

 

My diagnostic testing has been in my office using cables I know work (and indeed a different switch that I also use for phone commissioning). Two different boxes plugged in next to each other have the same issue though!

[Chris_Cook]

You could try setting up a mirror port on the switch and wiresharking it.

[bald_pig]

My diagnostic testing has been in my office using cables I know work (and indeed a different switch that I also use for phone commissioning). Two different boxes plugged in next to each other have the same issue though!

 

Always worth checking, the number of times I'll just leave the cable plugged in to the phone and test with the same cable...

[rich_tech]

Their not the best devices we have found, have had to remove them from our system, I vaguely recall having to create a standalone network for them when they reset as they had a hard coded IP on a 192 network

[dgsmith]

Always worth checking, the number of times I'll just leave the cable plugged in to the phone and test with the same cable...

 

Given it's the same in the original location and my back office, which I use for quite alot (and the cables themselves are tested a fair bit given their use) I know it's not the cable(s).

 

Their not the best devices we have found, have had to remove them from our system, I vaguely recall having to create a standalone network for them when they reset as they had a hard coded IP on a 192 network

 

Interesting thought. If it's assigning a class C IP and not budging, can you remember what the third octet was so I can see if this is the case, and indeed the default IP it would assign? When we bought them new, the default config was DHCP and so they were detected from new immediately.

[bald_pig]

According to the manual here: https://www.internetvoipphone.co.uk/product_data/yealink-w52p-user-guide.pdf

 

They default to DHCP