Yealink Forums
Replace Base - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: Dect Phone Series (/forumdisplay.php?fid=6)
+--- Forum: W52P (Wireless) (/forumdisplay.php?fid=23)
+--- Thread: Replace Base (/showthread.php?tid=522)



Replace Base - rfrantik@rfcinc.com - 06-05-2013 02:32 AM

We have a site where we recently installed a W52P setup... one base and two handsets.

Everything appeared to be OK the first day or two... but customer complained about phones "falling off registration"... power-off, power-on seemed to bring them back at first... but now we aren't able to get the phones to register with the base.

We can connect to the base and it looks like it is operating normally, but both the handsets now come up and say "REPLACE BASE" on the top line of the LCD.

Base was at firmware 25.20.0.10 and we upgrade to 25.30.0.20. No help.

Anyone have any advice?


RE: Replace Base - Yealink Support - 06-05-2013 04:29 PM

Hi Rfrantik,
1. It's strange, we didn't have see "Replace base" on the handset, so could you send us a picture to show this?
2. Could you provide PCAP trace, syslog(level 6) and config.bin file to us, so we can analyze?
Before you export the syslog, please set log level as 6, and reboot the phone, then click Start,and reproduce the issue, then click Stop,and export the trace, syslog, config,bin to us.
(About where to export these files, please refer to attached screenshot.)
These three files are very important for us, hope you can kindly understand.
Thanks.


RE: Replace Base - rfrantik@rfcinc.com - 06-05-2013 10:33 PM

Attached is a photo of the phone saying "Replace Base"

It's a banner on the top line of the screen.

We are working to see if we can capture any logs and we will post when available.

OK, trace info is attached. I think he did before and after so there are a couple of files. I zipped them all together.


RE: Replace Base - Yealink Support - 06-06-2013 11:16 AM

Hi Rfrantik,
Did you set the log level as 6 before you reproduce the issue?
I find in your config.bin, the log level is not 6, could you follow my steps describe as above?
Thanks.


RE: Replace Base - rfrantik@rfcinc.com - 06-06-2013 09:46 PM

What line do you expect to find that information on?

In the config (2).bin file I find the following:

8320: 6E 4C 6F 67 4C 65 76 65 6C 20 3D 20 36 0A 62 53 nLogLevel = 6.bs


RE: Replace Base - Yealink Support - 06-08-2013 11:00 AM

Hi Rfrantik,
Sorry for the inconvenience, our R&D still need these information:
1. Provide us two pictures more:
1) Idle status of your handset
2)Settings-Registration-Select Base
2. Could you export the syslog with level 6 as below steps?
1) Power off your handset
2) Power on your handset, and keep it stay about one minute
3) Export the syslog
Thanks very much.


RE: Replace Base - keattto - 10-02-2024 01:19 AM

(06-05-2013 02:32 AM)rfrantik@rfcinc.com Wrote:  We have a site where we recently installed a W52P setup... one base and two handsets.

Everything appeared to be OK the first day or two... but customer complained about phones "falling off registration"... power-off, power-on seemed to bring them back at first... but now we aren't able to get the phones to register with the base.

We can connect to the base and it looks like it is operating normally, but both the handsets now come up and say "REPLACE BASE" on the top line of the LCD.

Base was at firmware 25.20.0.10 and we upgrade to 25.30.0.20. No help.

Anyone have any advice?

The replace base error isn't an error, its the standard message (confusingly) that appears when you try to register handsets to a base and there's already an entry for one. If handsets aren't detecting base and say 'searching for base' or similar language its the reception range. It's poor. Try keeping a handset very close to the base and compare its performance to the other one.

If your not seeing that error, and are genuinely having registration issues try disabling all firewall settings, sip alg, etc use TCP instead of UDP, unique sip ports, accurate DNS to what the network uses.

It'd be a swifter set of troubleshooting for the end user and requires way less diagnostic steps like having server for syslog data available at a client's site.

Gumba