DECT Yealink W60B phones losing their config

[Br00kee]

Current having issues with DECT Yealink W60B phones losing their config:
3 sites with 2 phones each site so total of 6 phones all of which are Yealink W60B running Fw. 77.83.0.25. Running version 16.0.4.493 of the 3CX controller on a windows 10 machine with latest updates. We have been using the FQDN for the provisioning on the 2 external sites. The phones at one of the sites work fine for around 4 days then shows the extension being down in the controller, red light on the extensions page. The 1st time this happened a reboot on the phones and everything was fine. The 2nd time 4 days later extensions where showing as down but this time the phones had lost their config and needed to be reprovisioned
Appears to be some issues with resolving the FQDN (one created in 3cx) currently running a vpn between sites to see what happens over the next 4 days
Also have double checked that the phones are set to trust all certificates.

 

[cobaltit]

So you said W60B phones but the W60B is a base, and the WxxP are the phones. So in the second example where you say the config was lost was it the handsets (lost pairing with the base) or the base (had no 3CX configuration?). The W60B is touchy regarding DNS so if it is happening that often it's likely your internet is a bit flakey. If you have a local DNS server that will always be reaching even if the internet is down and can put a static entry for your FQDN that will work. Or provision by IP address.

 

[Br00kee]

yep sorry W60B base station with W53P phones. Base station is losing it 3cx config