Remote Phonebook and LDAP on a Softphone: One Directory
Tom Reed · Updated 3 November 2026
A remote phonebook puts one shared company directory inside every softphone. Instead of staff saving numbers by hand, contacts sync from an external directory via API or LDAP, so the same up-to-date address book appears on every mobile and desktop device. When someone joins or leaves, the directory changes once and every device follows.
This guide is for IT admins and MSPs who are tired of staff keeping their own contact lists. It explains what a remote phonebook is, how an LDAP phonebook differs from an API-fed one, what a synced directory gives a team and how to roll it out.
What is a remote phonebook on a softphone?
A remote phonebook is a contact directory held outside the app and pulled into it. SessionTalk's business softphone apps for mobile and desktop list it as Remote Phonebook & LDAP: the softphone syncs contacts from external directories via API or LDAP and keeps the address book unified and up to date across every device automatically.
That's different from contacts saved on the phone. A saved contact lives on one device, belongs to one person and goes stale the moment a colleague changes desk, number or job. A remote phonebook lives in one place that IT controls, and every softphone reads from it. Staff still see a familiar contact list in the app; the difference is where the list comes from and who keeps it right.
For a team, that means one company directory everywhere: the same names and numbers on a receptionist's desktop, a salesperson's mobile and a manager's tablet.
What is an LDAP phonebook?
LDAP (Lightweight Directory Access Protocol) is a standard way for an application to read a directory your company already keeps. If your staff accounts, names, departments and phone numbers already sit in a central directory, an LDAP phonebook lets the softphone read contacts straight from it. Nobody copies the list into the app; the app looks it up.
An API-fed phonebook works the other way round. Instead of the softphone reading an existing directory, another system pushes a contact list in through an API. That suits contacts that don't live in a staff directory at all, such as a customer list in a CRM or a custom list your team maintains.
Both sources are supported. SessionTalk's softphones sync contacts from external directories via API or LDAP, on mobile and on the desktop app. Because the app speaks standard SIP, it works with SIP-based PBXs and hosted platforms rather than being tied to one system. Which one you use depends on where your contacts already live, and if you're not sure where extensions and the team directory come from on the phone system side, our guide to the PBX phone system explains it.
LDAP or API: which phonebook source should you use?
Pick the source that already holds the contacts you want staff to see. Here's how the options compare.
Table: phonebook sources compared
| Source | Best when | Who maintains it | Watch out for |
|---|---|---|---|
| LDAP directory | Your company already keeps staff in a central directory | IT, in the existing directory | Decide which fields and groups to expose; keep it read-only for the app |
| API-fed phonebook | Contacts live in another system (a CRM or a custom list) | Whoever owns that system or integration | Someone must own the sync and its format |
| Contacts saved on each phone | One person, no shared list needed | Each user | Duplicates, stale numbers, nothing removed when staff leave |
For most internal staff directories, LDAP is the natural fit, because the directory already exists and IT already keeps it current. Use an API-fed phonebook when the contacts you want on every device sit somewhere else. Leave saved contacts for genuinely personal numbers.
Why give a team one shared directory?
A shared directory fixes the small, daily problems that come from everyone keeping their own list:
- Find people by name. Staff search the directory for a colleague or customer instead of hunting through old call history or asking someone for a number.
- The same contacts on every device. The address book stays unified across iPhone, iPad, Android, Windows and Mac, so a contact added once is there on the mobile app and the desktop app alike.
- No stale numbers after staff changes. When someone joins, moves or leaves, the directory changes once and every softphone follows. Nobody keeps calling a number that belongs to a person who left.
- Fewer misdials. Tapping a name from the directory is less error-prone than typing a number from memory or a sticky note.
On the desktop, the desktop softphone for Windows and Mac includes Remote Phonebook & LDAP with a unified address book across devices, alongside easy contact management. On mobile, the SIP softphone for iPhone, iPad and Android carries the same directory, so a salesperson on the road sees the same names as the office.
How do you set up a remote phonebook for your softphones?
Setup is mostly planning. The steps:
- Pick the source. Choose an LDAP directory if your staff already live in one, or an API-fed list if your contacts sit in another system. Name an owner for it.
- Decide what to show. Agree which details belong in the shared list, such as name, extension, mobile and company or department, and leave out anything private.
- Set it centrally. Configure the softphones from the cloud management portal, where SIP settings, dial plans, feature sets and user permissions are managed from a single web dashboard and changes are pushed to all users, so settings aren't entered device by device.
- Provision devices by QR code. Users scan a QR code from the portal and the softphone is ready to call, with no manual setup. For rolling this out to a whole team, see zero-touch softphone provisioning for remote teams.
- Check a pilot device. Before the whole team goes live, confirm the contacts appear correctly on one mobile and one desktop device.
How does the directory work with click-to-dial and BLF?
The directory is where calls start, so it pairs naturally with the features around it. On the desktop app, click to dial lets staff start a call from a CRM, email or browser using sip:// and tel:// links, and the directory gives them the right number to start from; see desktop click-to-call for SIP softphones. Busy Lamp Field (BLF) shows whether a colleague is idle, ringing or on a call, so staff can see who's free before they dial; the busy lamp field softphone guide covers it in more detail.
What about staff with several SIP accounts?
Some staff carry more than one line, such as a work account and a client account. One app can hold up to 16 SIP accounts with independent settings per account, so the shared directory sits alongside whichever accounts a person uses. For how to organise those accounts, read multiple SIP accounts on one softphone.
Remote phonebook rollout checklist
Checklist: before the directory goes live
- Directory source chosen (LDAP or API) and an owner named for it
- Fields agreed: name, extension, direct number, mobile, department
- Private or personal numbers excluded from the shared list
- Phonebook configured once in the cloud management portal
- Devices provisioned by QR code so users don't type anything
- Contacts checked on one mobile and one desktop pilot device
- Leaver process updated so removing someone from the directory is the only step
- TLS and SRTP on where the PBX supports it
Pair it with a hosted PBX
Pair it with a hosted PBX so extensions, the team directory and app provisioning come from one place: SessionPBX hosted PBX. SessionPBX lets your team find colleagues in the team directory and keep business contacts in a shared address book, and configures mobile apps with a QR code or desktop apps with a setup link. SessionPBX doesn't supply numbers or lines: it is a bring-your-own SIP trunk system, so you connect the SIP trunk you already use for outside calls.
FAQ
What is a remote phonebook?
A remote phonebook is a contact directory kept outside the softphone and synced into it, so every device shows the same list. IT maintains the directory in one place instead of each person saving contacts on their own phone.
Can a softphone use LDAP contacts?
Yes. SessionTalk's softphones sync contacts from external directories via API or LDAP, so staff can see contacts from the directory your company already keeps.
Does the directory work on both mobile and desktop?
Yes. The address book stays unified across devices, on the mobile app for iPhone, iPad and Android and on the desktop app for Windows and Mac.
What happens when an employee leaves?
Remove them from the directory and the change follows to every device. No one edits phones by hand, and nobody keeps a stale number for a person who has left.
Do users still keep their own contacts?
Keep the shared directory for work contacts, and set a clear rule for personal ones. Our BYOD softphone policy guide covers what to agree when staff use their own devices.
