Integrations

An integration is a configured connection between your PBX and an external service. It is mostly infrastructural plumbing and rarely affects inbound callers directly.

Overview

This page covers PBX-level integrations only. Partner organizations have a separate, unrelated Odoo CRM feature in the partner portal, which is not configured here and does not appear in the table below.

Each integration has a type that sets which fields it needs and what it does. The type is chosen at creation and cannot be changed afterwards, so to switch you delete and recreate. Most types can be added more than once to connect to several instances, but TAPI, Famulor, and AI Realtime are limited to one per tenant. Each type links to its own guide below.

Type	Connects to	Primary use
Microsoft 365	Microsoft Entra ID + Graph	Sync users (via SCIM) and contacts both directions.
Odoo	Odoo ERP instance	Push PBX SIP credentials into Odoo's VoIP module. Not the same as partner-level Odoo CRM.
Microsoft Teams	Teams via SBC (Direct Routing)	Let Teams users place/receive calls through your PBX.
Profile Guesser	External caller-lookup API	Surface incoming-caller name and company on the answering phone.
Famulor	Famulor AI voice agent API	Powers Famulor agents.
AI realtime	OpenAI realtime voice API	Powers Smart assistants.
DSK	DSK badge-reader / time-attendance	Sync employee badge events into Tempus.
TAPI	TAPI desktop CTI bridge	Click-to-dial with Windows TAPI applications.
Salary.lu	Salary.lu HR system	Push Tempus time records to Salary.lu for payroll.

Form fields

Fields available in the create and edit forms.

General

Type: The type of external service to connect with. Cannot be changed after creation.
Is active: Controls whether this integration is active. For Microsoft integrations, admin consent must be granted first.

Microsoft 365

Fetch Microsoft users to Cockpit: When turned on, users from Microsoft Entra are fetched and synchronized into the PBX as user accounts.

Shown when
Type is Microsoft
Push contacts to Microsoft: When turned on, PBX users with the "show in address book" flag are pushed to Microsoft as contacts for each user.

Shown when
Type is Microsoft
Fetch contacts from Microsoft: When turned on, contacts from Microsoft are fetched into the PBX to represent each user.

Shown when
Type is Microsoft

Odoo

Odoo URL: The URL of your Odoo instance (e.g. https://mycompany.odoo.com).

Shown when
Type is Odoo
Odoo database: The name of the Odoo database to connect to.

Shown when
Type is Odoo
Odoo username: The Odoo username used for API access.

Shown when
Type is Odoo
Odoo API key: The API key generated in Odoo under your user settings. Do not use your password.

Shown when
Type is Odoo
Sync SIP connection configurations to Odoo for all users?: When turned on, installs or updates the Odoo VoIP module and pushes SIP connection settings to Odoo for all PBX users.

Shown when
Type is Odoo
Provider WebSocket: Read-only. The WebSocket URL generated automatically for the Odoo VoIP module.

Shown when
Type is Odoo
Provider PBX server IP: Read-only. The PBX server IP address, derived from the server configuration.

Shown when
Type is Odoo

Profile Guesser

Profile Guesser URL: The URL of the Profile Guesser API endpoint. Must be a POST endpoint that accepts a JSON payload with a phone_numbers array.

Shown when
Type is Profile Guesser
Profile Guesser API key: The authentication token sent with each API request to the Profile Guesser endpoint.

Shown when
Type is Profile Guesser

Microsoft Teams

Teams SBC host: The hostname or IP address of your Session Border Controller (SBC) for Teams Direct Routing.

Shown when
Type is Microsoft Teams Direct Routing
Teams SBC port: The SIP port on the SBC. Default is 5060. Valid range: 1 to 65535.

Shown when
Type is Microsoft Teams Direct Routing

Famulor

API key strategy: Selects which Famulor account to use. Mixvoip uses the shared key. Customer uses the key you enter below.

Shown when
Type is Famulor (AI Integration)
Famulor API key: Required only when the strategy is set to Customer. Paste the API key from the Famulor dashboard.

Shown when
API key strategy is Customer

DSK

DSK base URL: The base URL of your DSK instance, with no trailing slash (for example, https://dsk.example.com).

Shown when
Type is DSK (Time & Attendance)
DSK API user: The username used to authenticate with the DSK API.

Shown when
Type is DSK (Time & Attendance)
DSK API password: The password used to authenticate with the DSK API.

Shown when
Type is DSK (Time & Attendance)
DSK bearer token: Read-only. Issued automatically by DSK when you save and refreshed as needed.

Shown when
Type is DSK (Time & Attendance)

Salary.lu

Base URL: The base URL of the Salary.lu API endpoint.

Shown when
Type is Salary.lu
Username: The username used to authenticate with Salary.lu.

Shown when
Type is Salary.lu
Enable custom rules: When turned on, lets you define custom rules that add extra fields to each Salary.lu request.

Shown when
Type is Salary.lu

Name: A name to identify this integration in lists and logs.
api_key: The key value. Use it as the Bearer token when calling the API. Treat it like a password.
Scopes: The API abilities this key is limited to. Grant only what the integration needs.
Expiration date: When this key stops working. Leave empty for a key that never expires.
rate_limit: The maximum number of API requests per minute allowed for this key (set by your plan).
last_used_at: When this key was last used to call the API. Read-only.
created_at: When this key was created. Read-only.

Updated 2026-08-24