Connect Elbuz to your virtual PBX once: managers then call with a button in the customer card, and every call lands in the call log and customer history.
When you need this:
- You just got provider keys — “Test connection” shows if they're correct.
- “Call” returns an extension error — the “Employee extensions” table shows who lacks one.
- Calls stopped reaching the log after a domain change — the form gives the address to resend.
- You run your own 3CX or Asterisk — you get a ready setup file with the address and key inside.
Where to start: “External services and integrations” → “Telephony” group → your provider → keys.
What the connection form does
Connecting takes three steps, in exactly this order: without keys there's nothing to test, and without extensions the “Call” button doesn't work.
- Provider keys — the form fills in your provider's field labels itself and tests the PBX connection with one button.
- Extensions — a table lists all active employees, including those who don't have an extension yet.
- PBX address or setup file — so the PBX reports every call to the app the moment it happens.
- Checklist — go through it to make sure a test call reached the log.
keys are needed for your employees' calls. A voice AI employee doesn't need them — for what to set up for it, see “API keys or voice AI”.
Step 1. Enter your provider keys
Open your provider in the “Telephony” group, turn on the active switch and enter the keys. Above the fields are the hint “You get the access keys in the operator account.” and the link “Where exactly — step by step in the guide for your operator”, leading to your provider's page with what to click in their account.
1
Telephony group2
Binotel row3
SMS messaging row- The “Telephony” group header — telephony operators live in the common list of integrations.
- The Binotel row — click it to open the connection form.
- The SMS messaging row — a neighbouring service, not telephony.
What to enter depends on the provider — the form fills in its labels itself:
| Provider | First field | Second field |
|---|---|---|
| Binotel | “API key” | “Secret” |
| Zadarma | “API key” | “Secret” |
| Ringostat | no field | “Project key (Auth-key)” |
| UniTalk | no field | “API key” |
| Phonet | “PBX address” — your PBX domain at the provider, for example mycompany.phonet.com.ua | “API key” |
| sipgate | “Token-ID” | “Token” |
| Aircall | “API ID” | “API token” |
| RingCentral | “Client ID” | “Client Secret”; third field — “JWT credential” |
| 3CX | “PBX address” | “Client ID and Secret” — separated by a colon, for example 200:AbCdEf123 |
| Asterisk / FreePBX | “AMI address (host:port)” | “AMI user and secret” |
Step-by-step guides for specific providers: RingCentral, 3CX, Asterisk / FreePBX; SIP trunks for the voice AI employee: Twilio and Telnyx.
Below is the “Line for outgoing calls” field: which of your numbers calls the customer. Leave it empty and the PBX picks one itself. Exceptions:
- Phonet, UniTalk and 3CX don't have this field: their API doesn't accept a line number;
- in Ringostat it's required — a Ringostat callback starts from the project number, and you enter it right here;
- Asterisk has two more fields with default values: “Employee channel” (
Local/{ext}@from-internal) and “Dialplan context” (from-internal); most FreePBX installations don't need to change them.
1
Active switch2
API key field3
Line for outgoing calls4
Test connection button- The “Active” switch turns the connection on.
- The “API key” field — the key issued by the operator (the “Secret” field sits next to it).
- The “Line for outgoing calls” field — which of your numbers the customer is called from.
- The “Test connection” button checks the keys (not pressed here).
The form saves itself about a second after you edit it — at the bottom of the window you see “Saving...”, then “Saved”. There's no separate save button.
A provider's API and WebSocket keys are different but look the same. A key pasted into the wrong field causes no error on save — the integration just silently won't work. Check with the button, not by eye.
Finally, click “Test connection”. The app asks the provider for the list of employees — it doesn't change anything in your account — and replies “Connected to the PBX. Employees in the PBX: ‹count›”.
On a separate line it shows “PBX extensions without an Elbuz employee: …” — extensions that don't match any employee card. That's your ready to-do list for step two.
Step 2. Set employee extensions
The extension is how the PBX knows whom to ring first, and how Elbuz knows who was on the call. You set it in the employee card: Account → System settings → “Users” → card → “Contacts” section → the “Internal phone” field. The field existed before; telephony simply started using it.
1
Where the extension is set2
Extension column3
Row with a dash- The hint says where an employee's extension is set: the “Internal phone” field in the user card.
- The “Extension” column shows each manager's internal number.
- A dash means no extension is set for this employee yet.
To avoid opening cards blindly, the connection form has an “Employee extensions” card: a table of all active employees with two columns, “Manager” and “Extension”. A missing extension shows as a dash, and such rows go last. While any extension is empty, the hint above the table is highlighted in a warning color.
Step 3. Make the PBX report calls
There are two different options here, and your provider decides which one applies, not you.
- The provider accepts an addressBinotel, Zadarma, Ringostat, Phonet, UniTalk, sipgate, Aircall: copy the ready address from the form and give it to the provider
- The PBX is set up with a file3CX and Asterisk: download the ready file and add it to your PBX
RingCentral fits neither option: you don't enter an address in the RingCentral account. Elbuz creates the event subscription itself after “Test connection” and renews it on its own.
The provider accepts an address
The form has a “PBX webhook address” card with a read-only field and a “Copy” button — after you click it, “Address copied” pops up.
The hint says what to do with it: “Copy the address and paste it in the operator account in the call notification (webhook) settings — where exactly is shown in the guide for your operator (link above).” Where this is in each provider's account — see the Binotel, Zadarma, Ringostat, Phonet, UniTalk, sipgate and Aircall pages.
1
Webhook address field2
Copy button- Webhook address field — the read-only address to give to the PBX operator.
- Copy button — copies the address to the clipboard.
The server generates the address, and it contains a 32-character secret key. The key is created once, when you first open the form, and never changes after that. So give the address to the provider and nobody else: anyone who knows it can send you events on behalf of the PBX.
The PBX is set up with a file
3CX and Asterisk have a “PBX setup file” card and a “Download setup file” button instead of an address. 3CX gets an XML template for integration to upload in the PBX management console; Asterisk gets a dialplan snippet to paste into your server's configuration. The receiver address and key are already inside — nothing to fill in.
1
PBX setup file heading2
Download setup file button- The “PBX setup file” card replaces the webhook address for 3CX — the PBX is connected with a file.
- The “Download setup file” button gives the ready file with the address and key inside (not pressed here).
Your own PBX must be reachable from the internet. The app won't connect to internal local network addresses: it checks the address and rejects reserved ranges. If your 3CX or Asterisk sits inside the office, set up access to it from outside, otherwise the “Call” button won't work.
If you changed your store domain or recreated the service in the list, give the provider the receiver address again. The key is built into it, and the old address simply stops working. You won't see any error: calls will just silently stop appearing in the log.
How to check that telephony works
Go through the list after setup — your checkmarks are saved in your browser. The last item is optional: AI call analysis is turned on in the same provider form.
To get telephony working
Scenarios
You're switching providers, and both work for a while
What to do. In the “Telephony” group of the “External services and integrations” window, keep the active switch on and the keys entered for both providers. Give the new provider the receiver address or upload the setup file.
What you get. The log fills with events from both providers, and the hourly reconciliation checks both services. The same conversation won't be recorded twice: the row is identified by the service and the call ID in the PBX.
What you don't get. The “Call” button works through only one of them, and you can't pick the provider for an individual call.
To dial through the new provider, turn off the active switch for the old one — after that the app rejects events from the old provider, and reconciliation stops checking it too. Its call recordings whose links aren't saved in the log will no longer open either — the app replies “Call recording is unavailable”.
Your store moved to a new domain
What to do. Open your provider's form, copy the address from the “PBX webhook address” card and paste it in the provider account instead of the old one. For 3CX and Asterisk, download the setup file again.
What you get. Calls appear in the log again as they happen, and the “Incoming call” card pops up for managers.
What you don't get. The app won't warn you that the address at the provider is outdated: calls will simply stop coming in. That's why you send the address right after changing the domain.
FAQ
I entered the keys and there's no error, but calls don't work. Why?
Most often the key is in the wrong field, or it's a WebSocket key instead of a REST API key — the form saves such a key silently. Click “Test connection”, and don't go further without the “Connected to the PBX” reply (step 1).
Will a 3CX or Asterisk in our office work?
Only if the PBX is reachable from the internet. The app doesn't connect to local network addresses, and the “Call” button won't work (setup file).
Can I give the receiver address to a contractor so they set up the PBX?
Give it only to the provider account. The address contains a secret key: anyone who knows it can send you events on behalf of the PBX.
Can I change the key in the webhook address?
No. The key is created once, when you first open the form, and never changes after that. A new address appears only if you change the store domain or recreate the service in the list — then give it to the provider.
Do I need API keys if a voice AI will answer calls?
No. Voice AI only needs call forwarding set up in the provider account. The keys are needed so managers' calls get into the log (API keys or voice AI).
Where to find it and who has access
- Menu
- Account → System settings → “Other settings” → “External services and integrations” → the “Telephony” group
- From the call log
- window menu → “Telephony connection”
- Extensions
- Account → System settings → “Users” → employee card
- Access right
- the “API & access tokens” window; for the PBX address and file, also “Call log”
- Prepare
- API keys from the provider account and the employees' extensions in the PBX
In the “External services and integrations” window, the “Telephony” group has eleven rows: ten providers and “Рассылка SMS” (SMS sending). SMS has nothing to do with telephony — it's a separate service with its own form.
Related topics
- If you need the big picture — how the app recognizes the customer and the manager, and what each provider supports: Telephony in Elbuz.
- If you don't know where the keys and webhook settings are in the provider account — your provider's page, for example Binotel or Zadarma; the rest are in the provider table.
- If the connection is ready and managers start calling — how to call from Elbuz and see who is calling.
- If the call button returns an error or a call didn't appear in the log — what to do when telephony doesn't work.
