Cannot update phonebook via Yealink handsets

[Godzilla881]

Hi,

My employers network has recently migrated over to a new system and this has caused most of our handsets to lose access to the phonebook via their Yealink handsets. I know we can factory reset then re-provision but there are 100+ handsets. Is there a quick fix via the 3CX management console or something 3CX can configure their end?

Thanks

 

[TheodorosG_3CX]

Is your base provisioned behind n SBC? Some more details will be helpful

 

[Charles_3CX]

Can you please porvide the follwoing information:

3CX Version, e.g., Standard Annual 18.0 update 4 (Build 965)
Server OS, e.g., Debian 10 / Windows Server 2019 / Raspberry Pi
Is the 3CX Server Hosted, and where? e.g. On-premises / Hosted in [AWS/Google/Azure/by 3CX]
IP Phone Make/Model/Firmware version, e.g., Yealink T46U version 108.86.0.20
Provisioning Method: Local / VPN / STUN / SBC ?
Trunk Provider or VoIP Gateway Make/Model, e.g., AT&T SIP-Trunk / Grandstream GXW-4104.
Has the Firewall Checker passed: YES / NO?
Are custom Phone Templates being used: YES / NO?

 

[Godzilla881]

3CX Version, Standard Annual 18.0 update 4 (Build 965)
Server OS, Windows Server 2019 Is the 3CX Server Hosted, and where? e.g. On-premises IP Phone Make/Model/Firmware version, e.g., Yealink T42S, Yealink T43UProvisioning Method: STUN
Trunk Provider or VoIP Gateway Make/Model, e.g., Gamma SIP-Trunk
Has the Firewall Checker passed: YES
Are custom Phone Templates being used: NO

Hope this helps

 

[Charles_3CX]

Once more question then since the phones are provisioned as stun, do you have your own custom FQDN or using a 3cx FQDN?

 

[Godzilla881]

We have our own custom FQDN

 

[Saqqara]

guessing the fqdn change in the migration ?

 

[Godzilla881]

guessing the fqdn change in the migration ?

Im thinking that. Would we have to change this over to a 3CX FQDN?

 

[Saqqara]

The address book on the phone is probably pointing to the wrong fqdn.

You can not use a 3cx fqdn, now you are using a custom fqdn.

How did you reprovision the phones, after the migration

 

[Godzilla881]

The address book on the phone is probably pointing to the wrong fqdn.

You can not use a 3cx fqdn, now you are using a custom fqdn.

Ah right, could i find the information for the right FQDN through our management console? or would I have to log into handset with the ip and re-provision from there?

 

[Godzilla881]

The address book on the phone is probably pointing to the wrong fqdn.

You can not use a 3cx fqdn, now you are using a custom fqdn.

How did you reprovision the phones, after the migration

Factory reset then logged into the handset ips and reprovisioned

 

[Saqqara]

If you factory default the phone, and logged into each phone, it should have pulled across the new phonebook settings

Log into a phone, check the url - Directory -> Remote Phone Book

It should be the server provisioning url taken from the phone provisioning link with suffix of /yealink_phonebook.xml

 

[Godzilla881]

If you factory default the phone, and logged into each phone, it should have pulled across the new phonebook settings

Log into a phone, check the url - Directory -> Remote Phone Book

It should be the server provisioning url taken from the phone provisioning link with suffix of /yealink_phonebook.xml

"cannot download remote phonebook" is what I can when I try to update. Guess Ill have to log into the phones and check the provisioning link for each one?

 

[Charles_3CX]

We have our own custom FQDN

Regarding your question, with a custom FQDN and certificate, you will need to check if the phones support the certificate. You can contact the vendor's support for their list of supported certificates and ensure that the certificate you use is under their supported certificates list.