cancel
Showing results for 
Search instead for 
Did you mean: 

BT voice connect. Unable to download group phone book

Ukchri2
Member

We have bt cloud voice connect, most yealink 46u handsets have access to group phone book so see the name of the caller if the number is declared in the directory.

 

However, a few phones cannot download the directory. Message states unable to download phone book.

 

I have restarted the phone by command and by disconnecting. Phone returns but directory is still missing.

 

Any suggestions??

thanks

chris

 

3 REPLIES 3

BethM
Administrator
Administrator

AlanM1
Administrator
Administrator

Hi Chris,

Thanks for getting in touch. If some Yealink T46U handsets can download the Cloud Voice Connect group directory but a few can’t, it’s usually one of the following:

1. Check the handset’s provisioning status

Sometimes the affected phones haven’t fully synced with the Cloud Voice Connect platform.
Ask the user to go to:
Menu → Status → Phone → Auto Provision
If it hasn’t provisioned recently, trigger a “Resync Device” from the Cloud Voice Connect portal.

2. Confirm the handset is assigned to the correct user

If the handset has accidentally been linked to an old or incorrect user profile in the portal, it won’t pull the group directory.
Worth double‑checking in Devices → Assigned Devices.

3. Check network access to the directory URL

Some handsets can reach the directory service and others cannot if:

  • they're on different VLANs
  • certain firewall rules are blocking access
    A quick test is to move one of the faulty phones onto a port where a working phone was plugged in.

4. Update firmware

Older firmware on Yealink T46U devices can block phonebook syncing.
In the Cloud Voice Connect portal:
Devices → Firmware Management → Update Firmware

5. Reset the handset to factory settings

If all else fails, a factory reset often forces a clean re‑download of the directory:
Menu → Settings → Advanced → Reset → Factory Reset
(Password is usually admin unless customised.)


If they still can’t sync after these steps, you’ll need a fault logged so the platform team can check the phonebook provisioning from the server side: 

norman89till
Member

Hi Chris, this usually happens because the specific handsets are missing the Remote Phonebook URL in their web interface or have a firmware mismatch. Log into the phone's IP address, go to Directory > Remote Phonebook, and ensure the XML server path matches your working phones.