I have Snom, Cisco, Grandstream & YeaLink phones.
Is there a way to push a centralized phone book to these phones ??
With Snom phones (and also Yealink I think) you can use centralised LDAP
directories on a server
Grandstreams support an XML format phone book download – it would susprice
me if the others didn’t, but I’ve no 1st hand experience of them.
So you’d need to get some central process to generate the phone books for
each type of phone then arrange the phones to download ther own phonebook.
Alternatively, use a programmable PBX such as Asterisk to maintain the
phone book centrally for you – have it update the name field for incoming
calls and allow it to take a short-code for outbound speed-dialling –
which can be accessed via a web interface to the PBX in a click to dial
sort of thing.
Well, that’s what I do anyway. It’s better than mucking about downloading
phone books to all the different types of phones.
This is a public server on the internet. I don’t think I can use LDAP to
push then ?
res_phoneprov has had a directory from the start… Try using
to get an idea.
your idea is not that bad…
I will seriously take this into consideration…
This is the input I needed :-)… Now to implement it !
If you can set up and administer LDAP on the server you will be able to
use it on the Snom (and maybe Yealink) phones.
Here’s a good starting point
Indeed, found this link also via google. Thank you.
On Thu, Dec 2, 2010 at 6:56 AM, Gordon Henderson
Cisco (at least the 79×1 series) phones also have a special XML format
for the directory. I have implemented it before as an interactive web
app the phones query. No information is stored on the phone itself.
Real-time query (Live XML/LDAP) back-ended on a database are really
the best way to go for Corporate style directory. Unfortunately, you
have to get a license from Polycom for LDAP, and static XML files get
out of sync way to fast…
I can use different Organizational Units for different phone books ??
For the Yealink – you can use a ‘remote’ XML file. The XML is stored on
a web server and is retrieved by the phone every time you press the
phones ‘key’. This has the advantage of not needing the directory to be
pushed to the handset – and the handset always gets the latest version.
Of course, the XML file needs to be kept up to date every time someone’s
When on a public server, I find this insecure.
Then secure it? Tie down by IP address, or some phones support the username:password@ in a URL.