W52P - 3CX Phonebook "Connect Error"

[steve.davidson]

After upgrading from 3CX version 15.5 to version 16, I have been unable to access the 3CX Phone book from any of my Yealink W52P handsets. I have tried changing the provisioning option from HTTPS to HTTP as identified in an earlier thread for a different Yealink portable phone model but, this does not resolve the issue. Does anyone have a solution?

 

[complex1]

Hi,

What you can check / try is:

• make sure the handset is within the range of the base, e.g. 10mtr
• make sure the base and handset is running on 2x.81.0.x0 firmware
• reset the base to factory default
• provisioning the base

 

[Union Tech]

Same problem here. Last night upgraded to 16 from 15.5 and there are several issues that are going on. One is this phone book issue.
We're using T52S and a couple of T58 w video. Both handsets give the same sort of error, Failed to download remote phonebook!.
We had been using a custom template - mainly because when you press phonebook, you want to search it. We moved that button over to the DND button so you could press phonebook, then the same button again to search.
Just factory reset one of the T52's and it seems to have fixed that issue, but that means the button is back to the default location. Try that and see if it helps you.

 

[Union Tech]

I just figured out one issue. The old server had HTTP: port set up as 5000, but the new server was configured for port 80. Thus, all the existing phone provisioning is pointing to :5000 which doesnt exist on the new setup. Hope this helps.

 

[JohnS_3CX]

Hi Steve,

I've noticed this happens on some older firmwares, please ensure you have the latest firmware updates on the device. Install manually as per our guide here https://www.3cx.com/sip-phones/firmware-upgrade-yealink-dect-w52p/

Then factory reset and reprovision from scratch https://www.3cx.com/sip-phones/yealink-dect-w52p/ to ensure everything configured right.

 

[AWS2P]

If you need access to phonebook before trying firmware update , do this
in settings, security settings, at bottom , uncheck this


after you upgrade W60B re check it and try