- Joined
- Feb 13, 2017
- Messages
- 16
- Reaction score
- 2
After we have migrated to v16 a few months ago I didn't realise at first that the dropped LDAP contact lookup would have an impact on our daily work but when there was new staff employed the 3CX PBX just didn't resolve their mobile phone number in the 3CX clients anymore. While I have configured our Snom desktop phones to do an LDAP lookup including the name and the contact's picture, the 3CX client apps do not store their names but their plain phone number.
Taking a look at what replaced LDAP lookup I found Exchange public folders (which Microsoft already tried to drop support for with version 2007 over ten years ago in the first place) which we have just gladly decommissioned and Office 365. Yes, we use O365 globally but if I understood correctly 3CX only synchonises the local user's contacts (from Outlook) but honestly, who uses their local Outlook's contact to duplicate information from Exchange's global offline address book in which are around 10000 entries to make sure they get incoming phone numbers resolved?
So in my opinion LDAP support has been dropped with no real replacement - or do I miss something here?
This is really an issue for us so any help is appreciated.
Thanks in advance!
Taking a look at what replaced LDAP lookup I found Exchange public folders (which Microsoft already tried to drop support for with version 2007 over ten years ago in the first place) which we have just gladly decommissioned and Office 365. Yes, we use O365 globally but if I understood correctly 3CX only synchonises the local user's contacts (from Outlook) but honestly, who uses their local Outlook's contact to duplicate information from Exchange's global offline address book in which are around 10000 entries to make sure they get incoming phone numbers resolved?
So in my opinion LDAP support has been dropped with no real replacement - or do I miss something here?
This is really an issue for us so any help is appreciated.
Thanks in advance!