W52P - No network

[mannebk]

Rob,

no way you could change it AFTER the base droped dead. I even tried finding the base in the zero conf IP range by pinging ever singel ip inside the zero conf range 169.245.0.0/16, without sucess.

I also think that this behavior is only an indicator, and I think PNP is NOT the reason for a dead base, mabe only the reason that the base starts behaving funny before dieing.

So: IF PNP is set to active, AND something in the hardware of the base is at its failure point, the base behaves funny (droping and recovering the network and dect in a 10 seconds cycl).
If PNP is set to disabled, maybe the base just drops dead one day w/o funny behavior as an indicator. BUT I dont know.

IF PNP ACTIVE: Then do nothing, = the base finally will die. after that: no chance to access it in any way anymore.

IF PNP is then set to INactive = maybe the base works some time and then dies, or maybe PNP is causing the fault, I have no clue as I didint had the possibillity to try and check.

For a fact, I got a brand new replacement base who had this "feature" right out of the box. *start of joke* So maybe this was a already 200 Years old Base *end of bad joke* as Karl here told me the MTBF is 200 years for all Yealink phones. Well, I do belive many things, but I dont trust this statement.

Too many times did I experience that especially Chinese manufacturer presented me with an updated factsheet for a hardware part wihtin minutes or days, right after I told them that the specs on the original fact sheet didnt meet my requirements, but for truly checking there would be a minimum requirement of time of several weeks for tests and analysis. And too many times did I got hardware from China that told me on its lable what it could do and then not even met 50% of that on a test bench.

I dont know of any equipment that has 200 Years MTBF! Not even satelite equipment for space use. So from my experience I divide facts from China by 4 and hope to be near the truth. But in this case I guess Karl maybe wanted to say 200 Days or Hours *lol* The Days would fit my first base, the hours the second one.

But I also have to say that I have severals Phones that are almost 2 years old and are working fine.

Back on topic:

It had nothing to do with firmware, we did an upgrade on an "infected" base, and the Problem (the indicator in form of funny behavior like dropping its link every 10 seconds or so) vanished only for a few days, as did a reboot from the UI. A reboot by pulling the cord didnt do it! So I had a ping runing in CMD.exe and only klicked the webinterface while the ping got through, while it timed out I didnt touch the webinterface.

That tells us, that only the link died, not even the session id of the admin session in the web interface.

Thats how I got to my conclusions.

At least for Germany, Im not sure for EU and rest of world: Since this is a common known failur for the w52p base now, the German warranty law extends the warranty period for this ond only for this failure from 24 to 60 monthes.

Sometimes Im not so happy beeing a German, but with such cases, I truly am. :-D

---

Rob,

maybe this helps you out, since I dont have a dead base any more, I cant test it.

http://forum.yealink.com/forum/showthread.php?tid=12850