Contacts from 3CX Company Phonebook showing as <unnamed> on Yealink W52 provisioned handsets

[aspect]

Bit of an odd issue, we have a customer that uses Yealink W52P dect bases.

When adding contacts to the global company phonebook, the contact on the portable handset shows up as 'Unnamed' despite the First Name in the address book being populated. The number against the contact shows up correctly though, it sounds like a templating issue to me but I can't be sure.

Is this something anyone else has seen before?

Many thanks

 

[Saqqara]

What version of 3CX ?

 

[aspect]

V15.5 install on Debian.

 

[leejor]

Is it possible that the number is in the handset (local) phone book, without a name (a blank field) that is overriding the name from the common phone book ?

 

[aspect]

The numbers in the local phone book are the ones showing up as <unnamed> these are extracted from entries added to the company phonebook in 3CX.

For example, user adds to the 3CX Company Phonebook, Company: test mobile number: 07778 833842
The phone eventually reprovisions and gets Contact name: <unnamed> number: 0778 833842

Originally they had been missing out the 'First Name' field against the contact adding the company name in the 'Company' text field instead in 3CX which made me think that this was related but I have since asked them to include the company name as the First Name, and they are still showing up as <unnamed> on there after reprovisioning the dect base handset.

 

[leejor]

If the handset receives a call from another extension, does both the name and extension number show? if you go though the local (internal) directory on the handset, do you see the entries (outside and/or local numbers) with name and number? if you check the 3CX Activity log, just after an outside call to the set, do you see both the name and number being sent?

This is old, and I'm not sure it is applicable, but perhaps worth a look at...
https://www.3cx.com/community/threads/yealink-display-name-provisioning.20128/