Data sources
CallerHub reads names from the systems where your contacts are already maintained. It only reads and creates no database of its own.
Step-by-step guides: DATEV export · Microsoft 365 and Exchange · SQL databases · Active Directory · E.164 format · all solutions
Types of data sources
| Source | Access | Port (example) | Notes |
|---|---|---|---|
| Microsoft SQL Server | SQL or Windows authentication, SELECT | 1433 | named instances with \; read-only user e.g. with db_datareader or rights on a view |
| Oracle | Service name, SELECT | 1521 | driver Oracle.ManagedDataAccess.dll is in the Drivers folder; no Oracle client required |
| MySQL / MariaDB | ODBC | 3306 | MariaDB ODBC 3.1 or MySQL ODBC 8.0 Unicode Driver (64-bit) |
| PostgreSQL | ODBC | 5432 | PostgreSQL Unicode (x64) |
| Other ODBC databases | ODBC, optionally a custom connection string | per database | e.g. Firebird, SAP SQL Anywhere, SAP HANA (HDBODBC) |
| CSV file | file local or on a share | SMB 445 | re-read on every change; DATEV, Excel and CRM exports via “Map columns” |
| REST API | GET/POST with none, basic, bearer, OAuth2 or NTLM | 443 | templates for HubSpot, Salesforce, Zoho, Odoo, SAP S/4HANA, Dynamics 365 and more |
| LDAP / Active Directory | LDAP search | 389 / 636 (LDAPS) | also OpenLDAP (bind=simple); LDAPS recommended |
| Microsoft 365 (Graph) | App registration in Entra ID | 443 | what=contacts (mailbox contacts, Contacts.Read) or what=users (User.Read.All) |
| Exchange (EWS) | Exchange Server on-premises | 443 | For Exchange Online, use Microsoft 365 (Graph) instead; Microsoft has announced the retirement of EWS in Exchange Online. |


Example of a phone number list (SQL Server)
-- The column names nummer, anzeigename, rang, land and id are fixed.
SELECT c.phone AS nummer, c.company + ' - ' + c.name AS anzeigename,
0 AS rang, c.country AS land, c.id AS id
FROM dbo.contacts c WHERE c.phone IS NOT NULL
For Oracle and SQL Server, the help describes how to create a read-only user CALLERHUB and how to find the right query in an unfamiliar database. An SQL assistant and the “Draft with AI” function help with this.
Templates for CRM and ERP systems
“Template” inserts a ready-made query or definition for the selected system. Apart from Infor COM, no template has been tested against a real installation; table and field names are based on published data models.
| System | Source | Status |
|---|---|---|
| Infor COM | Oracle | tested with R7.9 |
| Infor CRM (Saleslogix) | SQL Server | Testers wanted |
| Infor CloudSuite Industrial / SyteLine | SQL Server | Testers wanted |
| Infor VISUAL | SQL Server, Oracle | Testers wanted |
| Infor M3 | SQL Server | Testers wanted |
| Infor LN / Baan | SQL Server, Oracle | Testers wanted |
| Microsoft Dynamics CRM / 365 CE (on-premises) | SQL Server | example |
| Microsoft Dynamics 365 Business Central / NAV (on-premises) | SQL Server | example |
| SAP Business One | SQL Server | example |
| SAP Business One on SAP HANA | ODBC | Testers wanted |
| Sage CRM | SQL Server | Testers wanted |
| Oracle E-Business Suite | Oracle | Testers wanted |
| Oracle JD Edwards EnterpriseOne | Oracle, SQL Server | Testers wanted |
| SuiteCRM / SugarCRM CE | MySQL/MariaDB | syntax tested with test tables |
| vtiger CRM | MySQL/MariaDB | syntax tested with test tables |
| Dolibarr ERP/CRM | MySQL/MariaDB | syntax tested with test tables |
| Open Dental | MySQL/MariaDB | syntax tested with test tables |
| Odoo | PostgreSQL | syntax tested with test tables |
| Firebird, SAP SQL Anywhere | ODBC | template |
| HubSpot CRM | REST | Testers wanted |
| Pipedrive | REST | Testers wanted |
| Salesforce | REST | Testers wanted |
| SuiteCRM 8 / 7.x (V8 API) | REST | Testers wanted |
| SugarCRM (REST v11) | REST | Testers wanted |
| Zoho CRM | REST | Testers wanted |
| Odoo (JSON-RPC) | REST | Testers wanted |
| SAP S/4HANA | REST (OData) | Testers wanted |
| Microsoft Dynamics 365 / Dataverse (online) | REST | Testers wanted |
| Microsoft Dynamics 365 Business Central (online) | REST, OAuth2 | Testers wanted |
| Microsoft Dynamics 365 Finance & Supply Chain | REST, OAuth2 | Testers wanted |
| Infor CloudSuite via ION API | REST, OAuth2 | Testers wanted |
| bexio | REST | Testers wanted |
| HERO (trades software) | REST (GraphQL) | Testers wanted |
| Clio (law firms) | REST, OAuth2 | Testers wanted |
| Jobber (field service) | REST (GraphQL), OAuth2 | Testers wanted |
| DATEV (export of customers/suppliers) | CSV file | suggestion by column names |
| Active Directory, OpenLDAP | LDAP | tested with OpenLDAP |
| Microsoft 365 contacts or users | Graph | Testers wanted |
| Exchange contacts | EWS | Testers wanted |
Open Dental processes patient data; this is health data within the meaning of the GDPR. There is no template for ServiceTitan because its contact interface does not return names.
CSV file and DATEV export
Without further settings, CallerHub reads UTF-8 with semicolons, without a header row, in the order phone number, display name, country and link. Lines starting with # are ignored.
“Map columns” reads any layout, such as a customer/supplier export from DATEV, an Excel list or a CRM export. CallerHub detects the delimiter, encoding (UTF-8 or ANSI) and the DATEV header row itself. Multiple phone columns and fallback values such as {Company} || {First name} {Last name} are possible.
CallerHub only reads the exported file and does not access DATEV itself.

# Phone number;Display name;Country (optional);Link (optional)
040 66969000;Testkunde GmbH - Frau Beispiel;DE;https://crm.example.com/kontakt/1001
+41 44 000 45 67;Seeland Immobilien AG;;
044 000 43 21;Alpenblick Treuhand AG;CH;
REST APIs
A REST source is described line by line with key=value. This also lets you connect your own interfaces.
For the systems in the template list, “Template” inserts a ready-made definition. Details on connecting your own interfaces are available on request from support.
Phone number list and direct query
Phone number list (recommended): CallerHub loads all phone numbers into memory at start-up and at the configured interval (1 to 1440 minutes) and answers every call from there. If a refresh fails, the previous list stays active.
Direct query: CallerHub queries the source on every call. Parameters such as :num_e164, :num_national, :num_digits, :num_local and :num_country are translated appropriately for each database. Results are cached (at most 20,000).
Phone numbers are normalised: spaces, hyphens, slashes, brackets and “(0)” are removed; + and 00 mark international numbers.
Multiple data sources
- Sources are queried in the order shown; the first one with a match supplies the name.
- For each phone system, you decide which sources it queries.
- If one source fails, the others keep answering. If no source finds the number and one is failing, CallerHub answers with 503 so that the outage is not cached as “unknown”.
- The basic edition allows one data source, the full edition up to ten (more with a special licence).
Countries and dialling codes
National numbers need a country code. If the source supplies a column land, it applies per row; otherwise the configured code (e.g. 49) applies. Recognised are ISO codes (CH, AT, DEU), vehicle registration codes (D, A, FL), country calling codes (41, +41, 0041) and common country names. The trunk prefix is handled per country, e.g. none in Italy and Spain, 06 in Hungary or 8 in Russia.