Active Directory as the phone book for phone system and phones
Active Directory holds colleagues, often also contacts, with phone and mobile numbers. For these names to appear on calls, a service reads the directory via LDAP and passes the names on to the phone system and the phones.
What to prepare in the directory
- A service account with read access to the areas where users and contacts are stored, or the account under which the reading service runs.
- The starting point of the search (base DN), e.g.
DC=company,DC=localfor the whole directory orOU=Contacts,DC=company,DC=localfor a part. - The attributes holding numbers: usually
telephoneNumberandmobile; for the display namedisplayName, with the company if you like. - Encryption: LDAPS on port 636 instead of LDAP on 389.
Phones and phone systems can also query Active Directory themselves via LDAP. Then the notation of the number in the directory must match the one the phone searches with; customers from CRM or ERP are usually missing there.
With CallerHub: the directory as a data source
- Under Data sources, create a data source “LDAP”.
- Enter LDAP server and port, e.g.
dc01.company.localand 636 (LDAPS, recommended), plus the base DN. - Enter user and password of the service account (e.g.
COMPANY\svc-callerhub) or leave them empty: CallerHub then uses the account of the program or service. - Define which entries are read, which attributes contain phone numbers and how the display name is built. For OpenLDAP, simple bind is available.
- Test connection, then Save and apply.
The template for Active Directory and OpenLDAP has been checked with OpenLDAP.

Active Directory and CRM together
A typical setup has two sources: “CRM” (e.g. SQL Server) for customers and “Phone book” (Active Directory) for colleagues. CallerHub queries them in the order you set; the first source with a match provides the name. If one source fails, the others keep answering.
The names reach every phone system CallerHub connects to: via HTTP (STARFACE, 3CX, Asterisk), as an LDAP phone book for desk phones and phone systems with an external directory, through the STARFACE address book and as an export for the FRITZ!Box. The phones then ask CallerHub instead of the domain controller, and customers from the CRM are included as well.
If a field contains more than one number, CallerHub takes each valid number separately. The numbers are normalised before the search, see phone numbers in E.164 format.
Frequently asked questions
Does CallerHub need write access to Active Directory?
No. CallerHub only searches the directory, read-only. A service account with read access is enough.
Does this also work with OpenLDAP?
Yes. For OpenLDAP, choose simple bind. The template for Active Directory and OpenLDAP has been checked with OpenLDAP.
And users in Microsoft 365?
For users and contacts in Microsoft 365 there is a separate data source through Microsoft Graph, see Microsoft 365 and Exchange.
How up to date are the names?
In phone number list mode, CallerHub reloads the directory at the set interval, e.g. every 15 minutes; “Reload” loads at once. If loading fails, the previous list stays in use.
Test it with your own data.
Try the full edition for 30 days: choose “Request trial …” in CallerHub and the trial key arrives by e-mail. The setup wizard guides you through data source, phone system and test lookup. After that, CallerHub continues as the free basic edition without losing settings or data.