Elbuz connects to the Ringostat API with one project key: managers call customers from the card in one click, and calls with recordings go to the log and customer history automatically.
When you need this:
- The manager doesn't know who's calling — an incoming call card with the customer's name and recent orders pops up in Elbuz.
- Dialing by hand — the “Call” button in the card starts a Ringostat callback.
- You need to spot new customers — Ringostat data fills the “New customer” column in the log.
- Managers can't answer — an AI employee takes the call.
Where to start: copy the Auth-key in Ringostat (where exactly).
What Elbuz can do with Ringostat
- One-click call from the customer card — from the Ringostat project number (calling from the button).
- Call log and recordings — a permanent recording link is stored in the log (what reaches Elbuz).
- “New customer” flag — first-time calls are visible in the log (new customers).
- Incoming and missed call card — name, recent orders, a “Call back” task (call card).
- Call summary in the customer's history — AI analysis and the next step (AI call analysis).
- AI employee on incoming calls — a destination in the Ringostat forwarding scheme (voice AI).
What you need from Ringostat
The project key — the Auth-key — is in your Ringostat account:
- “Settings” → “Integration” → “Ringostat API”.
- Copy the Auth-key.
Ringostat doesn't need a login, so the Elbuz form has a single field for the key. You'll also need:
- A project number connected in the virtual PBX as incoming — Ringostat starts the callback from it.
- Employees' extensions — in the employee profile: “General settings” → “Employees” → the employee → the “Additional (extension) number” field (usually three digits, for example 101).
The Ringostat account paths come from the operator's official help center. If a menu item is named differently, go by these pages or ask Ringostat support:
- Ringostat: setting up an integration with API methods (Auth-key)
- Ringostat: API request to connect two numbers (callback)
- Ringostat: Webhooks — creating a webhook request
- Ringostat: creating an employee profile — extension, external SIP account
- Ringostat: setting up MicroSIP — “Virtual PBX” → “SIP accounts”, login and password
- Ringostat: installing and setting up PhonerLite — the sip.ringostat.com server
- Ringostat: forwarding schemes, the “external SIP account” destination
- Ringostat: standard SIP setup — server, port, codecs
- Ringostat: cost of communication services
How to connect Ringostat to Elbuz
Three steps in order: keys, extensions and the . Without extensions, calls aren't linked to managers. Without the webhook, the log is filled only by the hourly reconciliation — up to an hour late.
Step one: Ringostat keys
Open the Ringostat row in the “Telephony” group. The “Active” toggle is already on — leave it that way. Fields you fill in:
| Form field | What to enter |
|---|---|
| “Project key (Auth-key)” | the Auth-key from the “Ringostat API” section |
| “Line for outgoing calls” | required for the “Call” button: a project number connected in the virtual PBX as incoming (why) |
1
Link to the guide2
Active switch3
Project key (Auth-key)4
Line for outgoing calls5
Check connection- The “Where exactly — step by step in the guide for your operator” link leads to this page.
- The “Active” switch — the integration is on.
- The “Project key (Auth-key)” field — the only key; Ringostat needs no login.
- The “Line for outgoing calls” field — required for Ringostat: the project number connected as incoming.
- The “Check connection” button — a read-only request to the operator that changes nothing in the account.
The form saves itself about a second after each edit: “Saving...” shows at the bottom, then “Saved”. There is no “Save” button.
Finally, click “Test connection”. The Ringostat has no employee list, so Elbuz reads the last hour of the call log to see if the key works. The reply is “Connected to the PBX. Employees in the PBX: 0”; the “PBX extensions without an Elbuz employee” line doesn't appear — there are no numbers to take.
Step two: extensions
The number in the “Internal phone” field links calls in the log to a manager: the “Manager” column shows the Elbuz employee who has this number. Which Ringostat employee is rung first after the “Call” button is set by the project number's settings in the Ringostat virtual PBX.
Where: employee card (“Users”) → the “Internal phone” field.
Elbuz treats only a short value as an extension — up to six digits, like an additional (extension) number in Ringostat. If an incoming Ringostat event has a full phone number as the destination, the manager won't be identified and the call goes to the log without one.
Below the connection form there is an “Employee extensions” card — a “Manager” / “Extension” table for all active employees. Rows with a dash are the ones whose number hasn't been entered yet.
Step three: a webhook to the Elbuz address
The form has a “PBX webhook address” card with the address and a “Copy” button. You set up the webhook in Ringostat yourself, following the Ringostat help center:
- Ringostat account → the “Integration” section → the “Webhooks” page.
- Click “Add event”.
- Give it a name under “Name” and pick the events from the list: incoming call (before the call and after the call) and outgoing call.
- Under “Destination”, paste the address from Elbuz; under “Data sending method”, choose GET, POST or PUT; under “Data sending format”, json or Form. Elbuz accepts any of these options.
1
Address for the operator2
Copy- The address you give to the operator; the secret key at the end is masked in the screenshot.
- The “Copy” button — puts the address into the clipboard.
Ringostat expects a “200 OK” reply to every event; otherwise it marks the webhook as failing and stops sending events until someone turns it back on manually. Elbuz replies 200 to every event it can parse. If the address is wrong (an old domain, someone else's key), Ringostat may disable the webhook — check its status in your account.
To get Ringostat working with Elbuz
What reaches Elbuz
Everything below has been checked against the Ringostat integration module in Elbuz and the Ringostat help center.
| Feature | How it works with Ringostat |
|---|---|
| Calling from the card and the log (“Call”) | yes, via a Ringostat callback from the project number in the “Line for outgoing calls” field |
| Incoming and outgoing calls in the log | yes, from webhook events and the hourly reconciliation |
| Call recording | yes: a permanent link arrives in the event and is stored in the log |
| “New customer” flag | yes: Elbuz inverts Ringostat's “repeat call” flag |
| Incoming call card | yes, when the event sent before the call ends contains the short extension being called |
| Hourly log reconciliation | yes, at minute 25 of every hour, covering the past 24 hours |
| Hanging up from the incoming call card | no: Ringostat has no such method |
| The customer's name on the phone screen | no: Ringostat doesn't expect anything in reply |
| Voice AI employee | incoming — yes, via the forwarding scheme; outgoing — no (see below) |
How Elbuz tells webhook events apart: if an event has no call duration yet, the call is in progress — Elbuz looks up the customer and shows the incoming call card. If there is a duration, the call has ended and goes to the log. That's why event names in the Ringostat account don't matter.
Ringostat specifics
Calling from the button: what is sent to Ringostat
For the “Call” button, Elbuz uses Ringostat's simple callback method, passing the “Line for outgoing calls” in the “from” field (extension) and the customer's number in the “to” field (destination). Per Ringostat documentation, extension can only be a project number connected as incoming in the virtual PBX. So the button needs the “Line for outgoing calls”.
The “Line for outgoing calls” field was left empty — Elbuz then passes the manager's extension to Ringostat, and per Ringostat documentation that request fails: you'll see “The PBX rejected the request: …”. Make your first call after connecting a test call.
The method doesn't return a call ID — it arrives later in a webhook event. Elbuz then finds your attempt to the same number in the log within the last 30 minutes and updates it instead of adding a second row.
Don't share the webhook address
Ringostat events aren't signed, and the operator doesn't publish its server addresses. The only protection is the secret key in the address itself, so don't show it to anyone outside your team.
Call recordings
Ringostat puts the recording link right into the event, and the link is permanent. Elbuz stores it in the log together with the call; playback needs no separate request to the operator.
“New customer” flag
Ringostat marks repeat calls, and Elbuz inverts this flag: not a repeat means new. The hidden “New customer” column in the log is filled for Ringostat, and you can use it to filter first-time calls.
Hourly reconciliation
Every hour, Elbuz requests the call log for the past 24 hours from Ringostat. Ringostat doesn't publicly document the response format, so Elbuz parses it by the same fields that arrive in the webhook. If the key is rejected, the reconciliation doesn't pretend there were no calls — it records the failure.
Voice AI employee on a Ringostat number
An Elbuz AI employee can answer calls and call customers on its own. The conversation is handled not by your PBX but by the Elbuz voice platform, so the number has to be routed to it. Settings for the “Voice on the phone” section are in the Voice AI employee article.
Incoming calls: how to route the number to AI
In the “Operator” field of the “Voice on the phone” section, choose “Other operator”. Ringostat doesn't publish the IP addresses it sends calls from, so leave “Operator addresses” empty or enter the addresses support gives you. If the field is empty, Elbuz accepts calls to your SIP address from any address.
The section shows an address like <number>@<SIP domain>. Ringostat forwards calls to external SIP accounts, including third-party PBXs and SIP services (confirmed by Ringostat support). Where to enter it in your Ringostat account:
- “Virtual PBX” → “Forwarding”: open the number's scheme or create a new one.
- “Add destination” → type “external SIP account” → paste the address from the “Voice” section.
- For AI to answer only when managers haven't picked up, place this destination after the managers in sequential forwarding. Ringostat recommends a destination timeout of 30 seconds or more.
Elbuz accepts the G.711 A-law and μ-law codecs that Ringostat recommends. Calls to Ringostat SIP accounts are free; whether forwarding to another service's SIP address is billed — check with your Ringostat manager.
Ringostat support hasn't yet confirmed in what form Ringostat passes the caller's number: after setup, call your number and check that your number shows in the call log.
Outgoing calls: not available through Ringostat
Ringostat allows outgoing calls only from SIP accounts registered on the sip.ringostat.com server. The Elbuz voice platform calls without registration, and Ringostat support hasn't confirmed that. Leave the “Outgoing calls” block of the “Voice” section empty for Ringostat. For AI to make calls, use another operator's SIP line — see the Voice AI employee article.
Scenarios
A manager calls a customer back from the card
- Enter the project number in “Line for outgoing calls” (step one).
- The manager opens the customer card and clicks “Call” — Ringostat starts a callback from the project number.
- After the conversation, a webhook event updates the attempt in the log: duration, outcome, recording link.
Find first-time calls for the week
Turn on the hidden “New customer” column in the call log and filter by it — you'll be left with calls Ringostat didn't mark as repeat. More about the columns: call log.
AI picks up when managers are busy
- Turn on “Answer calls” in the “Voice on the phone” section and copy the SIP address (incoming calls to AI).
- In the Ringostat forwarding scheme, place the “external SIP account” destination after the managers.
- Call your number and check that AI answers and your number shows in the log.
What to do when Ringostat doesn't work with Elbuz
General telephony problems — no call button, an empty log, no recording — are covered in Telephony in Elbuz. Here is what's specific to Ringostat.
| What you see | Why | What to do |
|---|---|---|
| There's no “Call” button in the contact list or in the card | The keys aren't entered or the “Active” toggle is off — then call buttons aren't shown at all | Check the fields and the toggle in the connection form (step one) |
| “Your employee card has no extension number” | The “Internal phone” field in your card is empty | Enter the number in the employee card (step two) |
| “The PBX rejected the request: …” after clicking “Call” | The “Line for outgoing calls” field is empty or wrong: a Ringostat callback starts only from a project number connected as incoming | Enter in “Line for outgoing calls” the project number from the Ringostat virtual PBX; if that doesn't help, check with Ringostat support |
| Events stopped arriving, calls show up only once an hour | Ringostat disabled the webhook after a reply other than 200 — for example, when the address was outdated | Check the address in the Ringostat webhook and turn it back on |
| A call in the log has no manager | The Ringostat event has a full phone number instead of a short extension | Check where Ringostat forwards calls and enter the matching extensions for employees |
| “The PBX did not answer in time. If the call did start, it will show up in the call log — check it before dialing again” | The operator didn't reply within 15 seconds. The request may still have been accepted — then your phone will ring a bit later | Don't dial again right away: wait a minute. If the PBX accepted the request, your phone will ring, and after the conversation the call will appear in the log |
FAQ
Where do I get the Ringostat key for Elbuz?
In your Ringostat account: “Settings” → “Integration” → “Ringostat API”. This is the Auth-key — the project key. Enter it in the “Project key (Auth-key)” field of the Ringostat row in the “Telephony” group in Elbuz.
How do I set up a Ringostat webhook to Elbuz?
“Integration” → “Webhooks” → “Add event”: incoming and outgoing call events, with the address from the “PBX webhook address” card under “Destination”. Any method and format will do: Elbuz accepts both and a form.
Why did Ringostat stop sending events?
Ringostat disables a webhook if it gets a reply other than 200 OK. The cause is usually a wrong or outdated address. Fix the address and turn the webhook back on.
Are Ringostat call recordings stored in Elbuz?
Elbuz stores the permanent recording link that Ringostat passes in the event. The audio file itself stays in Ringostat.
Why does the test show “Employees in the PBX: 0”?
The Ringostat API has no list of employees, so Elbuz checks the key by requesting the call log for the last hour. Zero employees is a normal reply for Ringostat.
Will Ringostat show the customer's name on the manager's phone?
No: Ringostat doesn't expect a reply with a name from the . The manager sees who's calling in the incoming call card on the Elbuz screen (call card).
Can I route a Ringostat number to voice AI?
Yes, for incoming calls: in the forwarding scheme, add an “external SIP account” destination with the address from the “Voice on the phone” section (step by step). Outgoing AI calls through Ringostat don't work.
Where to find it and who has access
The Ringostat connection sits with the other integrations, not in the call log. The window that opens from the operator row is called “API access settings for external services”.
- Menu
- Account → System settings → “Other settings” → “External services and integrations” → “Telephony” → Ringostat
- Other ways in
- “Call log” → window menu → “Telephony connection”
- Access right
- system settings and the “Call log” window; you don't need any rights just to make calls
- Prepare
- the Ringostat project key (Auth-key), the project number, employees' extensions
Without the right to “Call log”, “Test connection”, the webhook address and the settings file don't work.
Related topics
- If you need the overall picture of telephony and a comparison of operators — Telephony in Elbuz.
- If the call is already in the log and you need to understand the columns or “Result” — Call log.
- If you want AI to answer and call customers on its own — Voice AI employee.
- If calls aren't linked to a manager — Users, the “Internal phone” field.
- If you need to find a conversation in the customer's history — Contact card.
