↑↓ selectEnter openEsc close

    1. Elbuz
    2. Connecting a PBX

    How to connect sipgate to Elbuz: CRM telephony for classic and neo with a token and webhooks

    5 min readUpdated

    Elbuz turns the sipgate cloud PBX into CRM telephony: managers call from the card in one click, see who is calling, and every recorded call lands in the log and customer history.

    When you need this:

    • A customer calls — the manager sees a card with their name and recent orders.
    • Calling a customer back — “Call” in the card: sipgate rings the manager, then the customer.
    • A call was missed — “Pulse” gets a “Call back” task.
    • Account moved from classic to neo — Elbuz detects the platform itself, no relinking.

    Where to start: create a Personal Access Token and enter it in the sipgate row under “Telephony”.

    What the sipgate integration does

    The integration uses two channels: through the Elbuz places and hangs up calls and reconciles the log every hour, and through sipgate.io webhooks (Push-API) sipgate itself reports the start and end of every call.

    • Caller card. An “Incoming call” pop-up shows the customer's name and recent orders; an unknown number is added with the “Create contact” button (call card).
    • Calls from the customer card in one click. “Call” in the contact card or in the log — no need to dial the number (how the call goes).
    • Recording and summary in the customer history. The call lands in the customer's feed, “Play recording” opens the recording, and AI analysis writes a summary and suggests the next step (AI call analysis).
    • A missed call becomes a task. “Pulse” gets a high-priority “Call back” task that closes by itself after a conversation with that number.
    • Classic and neo without switches. Elbuz detects the account platform itself (classic or neo).

    What you need from sipgate

    • A Personal Access Token (Token-ID and Token) with five scopes — the list is in step one.
    • A sipgate.io package on classic — webhooks don't work without it; the simplest one, sipgate.io S, is free.
    • On neo, the token owner must be a member of every channel whose calls you need in the log.

    sipgate has two platforms: classic (contracts before September 2025) and neo (new accounts since September 2025; older ones are being migrated). sipgate shows your platform in the profile menu of the web interface — click your avatar in the top right.

    The paths in the sipgate account are taken from sipgate documentation as of 20.10.2026. If a menu item is named differently, use these pages or ask sipgate support:

    How to connect sipgate

    Three steps: the token, employee extensions and the webhook address. Without webhooks, only the hourly reconciliation fills the log, and the incoming call card won't appear.

    Step one: Personal Access Token

    1. Open app.sipgate.com/personal-access-token and create a token.
    2. Give it five scopes:
      • sessions:calls:write — calls from Elbuz on classic;
      • rtcm:write — calls from Elbuz on neo and the “Hang up” button;
      • users:read — the employee list and the device to ring;
      • channels:read — detecting neo and reconciling the log on neo;
      • history:read — log reconciliation and recordings on classic (on neo, recordings come from channel events — the channels:read scope).
      Grant all five even if you don't know your platform: an extra scope does no harm on the other platform.
    3. Copy the Token-ID and the token itself.

    Open the sipgate row in the “Telephony” group. The “Active” switch is already on — leave it that way.

    Form fieldWhat to enter
    “Token-ID”the Token-ID of the Personal Access Token
    “Token”the token itself
    “Line for outgoing calls”your sipgate number the customer will see; leave empty to let sipgate choose
    The “Telephony connection” card of the sipgate form with Token-ID and Token fields
    1Token-ID
    2Token
    1. Token-ID — the identifier of the access token from your sipgate account.
    2. Token — the secret part of the key; it is shown as dots and not displayed in clear text.

    The form saves itself about a second after each edit: you'll see “Saving...” at the bottom, then “Saved”. Finally, click “Test connection” — Elbuz only reads data from sipgate and changes nothing in your account. The response:

    • “Connected to the PBX. Employees in the PBX: ‹count›” and the platform — “sipgate classic” or “sipgate neo”;
    • “PBX extensions without an Elbuz employee:” — s of sipgate users that no Elbuz card matches yet;
    • “Employees in the PBX: 0” ending with “users: HTTP 403…” — the token lacks users:read, and calls from the button won't go through.

    On neo, reconciliation sees calls only in channels the token owner is a member of: the administrator role doesn't grant that access. Create the token under a user who is in every channel whose calls must appear in the log.

    Step two: extensions

    For sipgate, an employee's extension is the sipgate user ID: w0, w1 and so on. That's what sipgate sends in call events, and Elbuz uses it to link a call to the manager. Enter the ID in the “Internal phone” field of the employee card; “Test connection” lists unlinked IDs together with names.

    When a manager clicks “Call”, Elbuz gets that user's default device from sipgate and rings it. You can also enter a device ID (e0) in the field — outgoing calls will work, but incoming calls won't be linked to that manager. How Elbuz recognizes a manager in general is covered in extensions.

    Step three: how to set up sipgate webhooks

    The form has a “PBX webhook address” card with the address and a “Copy” button. The address always starts with https:// — sipgate accepts nothing else.

    The “PBX webhook address” card with the webhook URL and the Copy button
    1Webhook address
    2Copy button
    1. Webhook address — paste it into both sipgate webhook fields, for incoming and outgoing calls.
    2. Copy — copies the address to the clipboard.

    sipgate classic. Webhooks require a sipgate.io package.

    1. Sign in to console.sipgate.com → in the left menu, Webhooks → URLs.
    2. Click the gear in the Incoming row, paste the address from Elbuz and save. Do the same for Outgoing.
    3. Under sources, select the lines and groups whose calls should reach Elbuz. With no line selected, there will be no events.

    sipgate neo. The Push-API works here too, but webhooks are set per channel in the sipgate web interface (Appweb — the hint in Elbuz calls it that too). sipgate documentation doesn't give the exact path to these settings — look for the channel webhook settings in Appweb or ask sipgate support.

    Paste the same address from Elbuz. Neo requires https and doesn't follow redirects, so you can't replace the address with a short link.

    Check. Call your sipgate number. If the call doesn't show up in Elbuz, click “Activate debug log” in the sipgate webhook settings and open the request log at app.sipgate.com/io/log (the “Debug log” item): it shows every request to Elbuz and the response.

    sipgate signs every event, and Elbuz checks the signature. Elbuz silently ignores an event without a valid signature — no error appears on screen.

    The address contains a secret key and the host you opened the form from. If you changed the domain or recreated the service in the list, the address has changed and you need to enter it in sipgate again.

    To get sipgate working with Elbuz

    What reaches Elbuz

    Featuresipgate classicsipgate neo
    Calls from the card and the log (“Call”)yesyes
    “Incoming call” card for the manageryes, on the call start eventyes, on the call start event
    Calls in the logyes, on the call end event; reconciliation refines the durationyes, on the call end event; reconciliation refines the duration
    Hourly log reconciliationfrom sipgate call historyfrom channel events (call history is empty on neo)
    “Hang up” in the incoming call cardyesyes
    Call recording (“Play recording”, AI analysis)yes, from call historyyes, from channel events
    Customer name on the phone screennono
    SMSnono

    sipgate specifics

    Classic or neo

    The platform determines the call request sent from the button and where reconciliation gets calls from. Elbuz detects it like this:

    1. asks sipgate for the account type;
    2. if sipgate doesn't report it, checks whether the account has channels: only neo has channels;
    3. if the channel list comes back empty, treats the account as classic.

    That's why the channels:read scope is needed even for calls. Both “Test connection” and the “Call” error will tell you the token lacks it, if sipgate rejects the call. After your account moves to neo, you don't need to relink anything in Elbuz — the token just needs the rtcm:write and channels:read scopes.

    Call duration

    sipgate's call end event carries neither the duration nor the start time. Elbuz counts the duration from call start to end, ringing included, so right after the call it's approximate. The hourly reconciliation sets the exact duration from sipgate data.

    Group incoming calls

    When a call goes to a group, sipgate sends a list of users, and Elbuz assigns the call to the first of them. Reconciliation then sets the manager from sipgate data: on neo, the call owner; on classic, the user who answered. If a device rather than a user answered, or nobody did, classic keeps the first user listed.

    Call recordings

    sipgate serves recording files only with a token. When you click “Play recording”, the Elbuz server downloads the file from sipgate with your token and passes it to the player — the token never reaches the browser. AI call analysis gets the file the same way.

    • The recording is looked up among recent sipgate calls: in the history on classic, in channel events on neo.
    • You can seek in the player once the file has fully loaded.
    • Files over 25 MB are not played or analyzed.

    How a call from the button goes

    Elbuz asks sipgate to connect the manager's device to the customer's number and doesn't wait for the manager to pick up: sipgate rings the manager's device first, then the customer once the manager answers. Before that, Elbuz may make a few more requests to detect the platform and the manager's device; each waits up to 15 seconds.

    • The device request got no response — the call definitely didn't start: you'll see “The PBX rejected the request: …” and can retry right away.
    • The call request itself got no response — you'll see a timeout message: the call may already have started.

    Scenarios

    Your sipgate account moved to neo

    Change nothing in Elbuz. Check that the token has rtcm:write and channels:read and that the token owner is a member of all channels. Set webhooks for the neo channels in Appweb. “Test connection” should show “sipgate neo”.

    Incoming calls go to a group of managers

    Right after the call, it's assigned to the first user in the group. Within an hour, reconciliation sets the person who answered (on neo, the call owner). For this to work, every manager's “Internal phone” must hold the user ID w…, not a device ID.

    Customers should see one company number

    Enter that sipgate number in “Line for outgoing calls”. All calls from the “Call” button will go out from it, whichever manager is calling.

    What to do when calls don't come through

    What the system says and what to do about it
    What you seeWhyWhat to do
    “The PBX rejected the request: HTTP 401…” after “Test connection” The Token-ID or Token is entered incorrectly, or the token was deleted Create a new token and re-enter both fields (step one)
    “The PBX rejected the request: HTTP 403…” when calling from the button The token lacks the scope for this request: sessions:calls:write on classic, rtcm:write on neo Create a token with all five scopes
    “Test connection” or a “Call” error ends with “… add channels:read to the Personal Access Token” The token lacks the channels:read scope, so Elbuz couldn't tell whether you're on classic or neo Create a token with channels:read and re-enter “Token-ID” and “Token” (classic or neo)
    “Employees in the PBX: 0”, although sipgate has users The token lacks the users:read scope Add the scope — without it, “Call” with a user ID doesn't work either
    “The PBX rejected the request: sipgate user w… has no default device” The sipgate user has no default device set Set one in sipgate, or enter the device ID (e0) in “Internal phone” — then incoming calls won't be linked to the manager
    “Your employee card has no extension number” The “Internal phone” field is empty Enter your sipgate ID (step two)
    Calls appear in the log up to an hour late, and there's no incoming call card Webhooks aren't arriving: the address isn't entered, no lines are selected in sources, there's no sipgate.io package on classic, or the address has the old domain Turn on “Activate debug log” and check the Elbuz response at app.sipgate.com/io/log (step three)
    The “Manager” column in the log is empty The employee card holds a device ID or a phone number instead of the user ID (w…) Enter the user ID from “PBX extensions without an Elbuz employee”
    “Play recording” is there, but the player is silent The Elbuz server couldn't download the file from sipgate: the token was changed or deleted, it lacks history:read (classic) or channels:read (neo), the token owner isn't a member of the channel on neo, or the file is over 25 MB Check the token and scopes with the “Test connection” button (step one)
    “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” sipgate didn't respond in time to the call request itself (up to 15 seconds); the request may have been accepted Don't dial again right away: wait a minute

    If a call doesn't appear in the log at all while webhooks are arriving, see the general troubleshooting in Telephony in Elbuz.

    FAQ

    Which scopes should the sipgate token have for Elbuz?

    Five: sessions:calls:write, rtcm:write, users:read, channels:read and history:read. The first two are for calls from Elbuz on classic and neo, users:read for employees, and channels:read and history:read for log reconciliation on neo and classic.

    What goes in “Internal phone” for sipgate?

    The sipgate user ID — w0, w1 and so on. “Test connection” shows IDs not yet linked in the “PBX extensions without an Elbuz employee” line. A device ID (e0) also lets you call, but incoming calls then won't be linked to the manager.

    Why did the call duration change an hour later?

    Right after the call, Elbuz only knows the time from start to end, ringing included. The hourly reconciliation takes the exact duration from sipgate data.

    Can I send SMS through sipgate from Elbuz?

    No, the integration works with calls only.

    Will the manager see the customer's name on the phone screen?

    No. The customer's name and orders are shown in the “Incoming call” card in Elbuz; Elbuz doesn't pass the name to the sipgate phone.

    Can I put a voice AI employee on a sipgate number?

    There are no ready-made instructions for sipgate: sipgate isn't among the operators in the “Voice on the phone” section. Which operators are supported is covered in Voice AI employee.

    Where to find it and who has access

    Menu
    Account → System settings → “Other settings” → “External services and integrations” → “Telephony” → sipgate
    Extension
    “Users” → employee card → “Internal phone”
    Call log
    Directories → Contacts → Call log
    Access right
    system settings and the “Call log” window; you don't need any rights just to make calls
    Prepare
    a sipgate Personal Access Token; on classic, the sipgate.io package

    Without the right to “Call log”, “Test connection”, the webhook address, “Hang up” and “Play recording” don't work. The general mechanics — log, call card, permissions — are in Telephony in Elbuz.

    Related topics

    • If you need to understand the log, the call card or who sees what — Telephony in Elbuz.
    • If a manager needs to fill in “Internal phone” — Employee card.
    • If you need to find a conversation in the customer history — Contact card.

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free