LDAP Server Integration Guide
Cloud Voice can connect to a third-party LDAP (Lightweight Directory Access Protocol) directory server, such as MetaDirectory, to draw on the contacts stored there. Once linked, an incoming call prompts the system to look the caller up in the directory and show their name on screen whenever a record matches. You can also synchronize directory entries into Cloud Voice phonebooks, which lets users place calls to those contacts from the Cloud Voice App and lets the system steer inbound calls to specific destinations based on which phonebook a caller belongs to.
Requirements
Section titled “Requirements”| Item | Requirement |
|---|---|
| Cloud Voice | Plan: Enterprise Plan (EP) or Ultimate Plan (UP) Firmware: Version 84.18.0.102 or later |
| Third-party LDAP server | None |
What the integration enables
Section titled “What the integration enables”The LDAP link supports three capabilities: displaying a caller’s name from directory records, keeping phonebook contacts in sync with the directory, and routing inbound calls according to phonebook matches. The steps you follow depend on which of these you want to turn on.
Caller ID name display
Section titled “Caller ID name display”To have inbound calls trigger a directory lookup and surface the caller’s name on a match, complete one task:
Caller ID name display with contact synchronization
Section titled “Caller ID name display with contact synchronization”To show caller names and also mirror directory contacts into your phonebooks, complete both tasks in order:
Caller ID name display, synchronization, and phonebook-based routing
Section titled “Caller ID name display, synchronization, and phonebook-based routing”To add intelligent inbound routing on top of name display and synchronization, complete all three tasks in order:
- Integrate Cloud Voice with an LDAP Server
- Set up Contact Synchronization from the LDAP Server
- Configure inbound routes that select their destination based on matched phonebook contacts.