LDAP Integration as phonebook

[Sven Mitternacht]

As LDAP becomes more and more standard to most PBXs and other devices it must be possible to integrate LDAP in 3CX as well. In V16 you don't even have the old LDAP integration (which was not good at all). LDAP Integration should synchronise Contacts to Phonebook like Office 365 Integration does now or LDAP must be searchable. Number resolution should also be possible.

With a good working LDAP integration, we also solved the Problem with the terrible phonebook integration on devices like yealink, SNOM and so on (only mobile number :-(). With LDAP it works good.

We use metadirectory for LDAP integration in all kinds of PBXs and devices. It is simple, cheap and the best way to keep contacts from various databases sync and all time available.

 

[startechinformatica]

+1

 

[BayAC]

Also missing this greatly, we are trying to ingrate with and migrate away from an Avaya IP office 500, no LDAP for directory contacts feels like a huge step backwards.

 

[Ranac]

+1

 

[hwohlert]

A LDAP database built into 3CX would also allow SIP phones to use it as an address book, eliminating the limitations of the phone's built-in address book when the number of contacts is very large (>5,000)

 

[ccpcologne]

+1

 

[BayAC]

While waiting for integrated LDAP, I was able to at least get incoming call CID lookups working against AD. Pairs nicely with a template modification that allows the yealink devices to do AD queries for incoming calls.

https://github.com/bruor/3CXldap2json

 

[jthomas.tw]

+5

 

[Andreas Conrad]

+1

 

[dan-bln]

+1

 

[blackpearl]

+1

 

[futura-it]

+1