Unusual Yealink issue

[Glen.c]

I have a strange yealink issue. This is very Yealink specific, not so much 3CX specific but i just thought I'd bounce it off people in here in case someone else is seeing the same problem and scratching their head.

Over the past 2 days I've had 3 clients with W70B base stations contact me to say the phones had stopped working. Different clients, on different network gear, on different IPS's.

After doing a few things like factory reset, checking firmware etc etc i decided to replace one of the units at one of the clients sites, we go out yesterday to do this and we pull out a brand new out of the box W70B and it too does the exact same thing. I'll details what's happening.

- Plug in W70B and it boots up
- W70B gets an IPV4 and registers the handset (W56h)
- The base then drops the IPv4 and never regains an IP again
- The base and the W56h then lose contact with each other and can no longer see each other

This then repeats over and over.

I took the new out of the box W70B back to the office to check it out and from what I can see, the phone goes through its normal boot process and as part of that it contacts Yealinks RPS server. I can see the phone going out to this IP 52.71.103.102 (an amazon IP).

I think, ok, has this MAC and serial been added to Yealinks RPS server (we don't use their RPS at all, so it wasn't us that did it), so I call our distributor and ask them to check if they accidentally added these MACs and serials to the RPS server (they are also a voip provider, breezeconnect). They had a look and came back with no. They didn't add them to the yealink RPS server.

From what I can see, I have a set of clients, mostly on W70B's that are going out the yealink RPS server and then getting a corrupted config file which kicks them off the LAN and then never return until the device is factory reset but once you factory reset the device the process kicks off all over again as there is no way to stop the device going out to the Yealink RPS.

I have 5 W70Bs with this issue and so far a set of T53w's, all at different sites, all with completely different environments.

Unfortunately, Yealink are on holidays until the 17th because of Chinese new year.

I have submitted a case to them to enquire about a specific MAC and ask if they have that in their RPS server. Due to holidays they haven't responded yet but that will tell me a lot i guess.

Is anyone else seeing similar behaviour?

Putting my tin foil hat on, it seems like someone is adding MACs and serials to Yealink RPS and then sending those phones a corrupted config file. Chinese new year would be a perfect time to do that.

 

[TheodorosG_3CX]

Unfortunately those MAC addresses will need to be removed from Yealink RPS.

 

[Glen.c]

Catch 22 though, we don't know if they are in fact in the yealink RPS server, I'm taking an educated guess they are because the behaviour seems to point to that and the catch being, yealink is the only one who can tell us (or who ever added them if they are in fact added) if they are and they are currently on break.

I was just curious if anyone else is seeing this behaviour as well or is it just me.

Yeah not a 3CX issue in any way shape or form but thought I'd just bounce this off the community here as it's a pretty active community on here vs say the yealink forums.

 

[TheodorosG_3CX]

You can add this MAC in 3CX and try to provision with our RPS, in case this does not proceed you will see a related error in the PBX event log.