CallerHub
EN
Download

STARFACE: caller name from CRM, ERP or SQL

On its own, STARFACE knows the names in its own address books. If your customers are stored in a CRM, an ERP or a database, the phone system needs a lookup for every call or a sync into the address book. This page describes both.

How STARFACE gets a name

  • Address book of the phone system: contacts stored in a STARFACE address book appear as the name. If they are imported or maintained there by hand, a second copy of the data has to be kept up to date.
  • A module per call: STARFACE has no built-in name lookup via a web address. A module of the type Call-Processing can call an address for every incoming call and set the response as the caller name.

For the module you need administrator access to the STARFACE. Modules are imported under Admin → Modules → Module library → Import module (STARFACE guide, German). A cloud STARFACE must reach the queried service from the internet; the port is then forwarded in your firewall to that computer.

With CallerHub: a name for every incoming call

CallerHub ships a finished module: the file CallerHub_Interface_….sfm in the Samples folder. For an incoming call the module asks CallerHub for the name and shows the response. The guide was tested with STARFACE 10.0.2.6 (cloud).

  1. In CallerHub, choose STARFACE under Interfaces → Add interface, enter a label and click Create. Under Allowed IP addresses, enter the sender of the STARFACE, check the queried data sources and click Save and apply.
  2. In the STARFACE, open Admin → Modules → Module library → Import module and choose the file from the Samples folder.
  3. In the Module manager, tab Module configuration, create a new configuration for the module CallerHub. At LOOKUP_URL, enter the CallerHub address, e.g. https://callerhub.example.com:8080/lookup (ending in /lookup, no parameters); at API_KEY, the key of the interface. Save and set the configuration to active.
  4. Forward the CallerHub port (default 8080) in the firewall to the CallerHub computer.
  5. Call from a number stored in the CRM. The access appears in CallerHub under Recent requests.
Interfaces · Phone system
Phone system card with the guide for STARFACE.

“Copy instructions” on the card provides the same guide with the real API key. The names come from all data sources selected for this interface, e.g. an SQL database, a DATEV export or Active Directory.

Outgoing calls, app and web client: sync the address book

For outgoing calls, the STARFACE app, the web client and the call lists only show names from STARFACE address books. For these, CallerHub writes the contacts of your data sources into a separate address book via the STARFACE REST interface: nightly at the set time, after every reload of the data sources and at the push of a button.

  • Only in its own address book: CallerHub creates, changes and deletes contacts only there. If a source is empty or has shrunk by more than half, it deletes nothing.
  • Connection from the inside: CallerHub connects to the phone system; no inbound firewall rule is needed for this. From STARFACE 10 with OAuth.
  • Create the address book: from STARFACE 10 you create it under Administration → Address book → Directory configuration with write access, using the same name as in CallerHub.

Call analytics and live view

Also enter EVENT_URL in the module: the same address ending in /event. The module then reports every event of a call (ringing, answer, hang-up, forwarding) for call analytics, statistics and the live view. CallerHub needs the base number of the phone system for this (e.g. +49 40 66969); otherwise it cannot recognise direction and internal calls.

For past calls, use the export of the call data: Administration → Evaluation → Export call data, then put the file output.csv into the folder of the interface.

Common errors

ObservationCause and remedy
Module Designer, tab Log File: ConnectTimeoutExceptionThe STARFACE cannot reach CallerHub. Check the address, port forwarding and HTTPS.
Log: status=401The API key in the module configuration is wrong.
Log: status=403The IP address of the STARFACE is missing from the allowed IP addresses; the log shows it as ip=….
Log: status=404The address does not end in /lookup.
No request on callsThe module type must be Call-Processing and the configuration active.
All calls appear as outgoingEnter the base number of the phone system in CallerHub.

The STARFACE module log can contain credentials. Check it before passing it on and remove passwords.

Frequently asked questions

Do I have to build the STARFACE module myself?

No. CallerHub ships the module as a file in the Samples folder; you import it and enter address and API key. If the import shows “Licence required”, support will help.

Does this work with STARFACE Cloud?

Yes. The guide was tested with STARFACE 10.0.2.6 in the cloud. CallerHub then needs an address that is reachable from the internet, and the allowed IP addresses limit requests to the sender of your STARFACE.

Is customer data copied into the STARFACE?

Not for the name lookup: the module asks for every call and CallerHub answers from its list in memory. Only the optional address book sync writes contacts into a separate STARFACE address book.

Which data sources can STARFACE query this way?

All CallerHub data sources: SQL Server, Oracle, MySQL/MariaDB, PostgreSQL and other ODBC databases, CSV files such as the DATEV export, REST APIs of CRM and ERP systems, LDAP/Active Directory, Microsoft 365 and Exchange. The basic edition allows one data source, the full edition up to ten.

Try it

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.