Multi-protocol audio bridge

One live call, whatever protocol each party is on.

The Xebit audio bridge joins SIP, WebRTC, WebSocket and gRPC in a single live call. While an AI agent talks to a customer on the phone, a person on your team can join from a browser to whisper, join in or take over, with no transfer and no redial. One recording covers every leg.

A customer on SIP, a team lead on WebRTC, an AI agent on gRPC and a service on WebSocket, all joined into one call by the Xebit audio bridgeCustomerSIP · your carrierTeam leadWebRTC · browserAI agentgRPCYour serviceWebSocketXebit Audio Bridgerelay · transcode · recordOne call · one recording · every protocol
Why it matters

Voice runs on three islands. Calls need all of them.

A real call involves a customer on the phone network, a team that works in browsers, and AI that speaks streaming protocols. Without a bridge each lives in its own system, and every handoff between them is a transfer, a redial or a lost conversation.

Customers call on SIP

The phone network reaches you over SIP, through your own carrier or SBC.

Your team works on WebRTC

Supervisors, specialists and agents live in a browser or an app, not on a desk phone.

AI speaks WebSocket and gRPC

Agents, models and your own services stream audio and events over WebSocket and gRPC.

How it works

Every party keeps its protocol. The bridge makes it one call.

Each party connects on the protocol that suits them. The bridge relays audio and events between all of them, converts codecs where they differ, and records the call once.
Legs the Xebit audio bridge connects
LegProtocolWho is on it
The customer's phoneSIP (RTP over SIP), through your carrier or SBCCallers, inbound and outbound
A browser or an appWebRTCYour team, or customers calling from your app
Your own servicesWebSocketAudio streamed to your services or third party bots
Internal servicesgRPCAI agents and services exchanging audio and call events

Relay and fan out

Audio and call events move between every party on the call in real time, whatever protocol each one arrived on.

Codec transcoding

Telephony and WebRTC codecs, such as G.711 and Opus, are converted automatically. Nobody configures it per call.

One recording, every leg

One recording and one transcript of the whole call, including the parts a person joined from a browser.

Agent to agent handoff

One AI agent can pass the live call to another agent on a different service, without the caller noticing a seam.

Humans on AI calls

A person can step into any call. Three ways.

While an agent talks to a customer on SIP, someone on your team opens the call in their browser over WebRTC and chooses how to take part.

Whisper

Who hears whom
The person speaks to one side only. The customer does not hear them.
Use it when
Coaching a colleague, or steering the conversation without interrupting it.

Join

Who hears whom
Everyone hears everyone: the customer, the AI agent and the person.
Use it when
A specialist answers one question, or a team lead confirms an exception, and the agent carries on.

Take over

Who hears whom
The person continues the call. The AI agent drops off or goes quiet.
Use it when
Disputes, distress, compliance sensitive moments, or anything the agent should not handle alone.
The customer never leaves the callWhichever mode the person picks, the customer stays on the same line. There is no hold, no transfer to a new number and no redial, and the recording keeps running across the whole conversation.
What changes

Why this changes how voice agents get built.

Most voice stacks treat the phone, the browser and the AI as separate systems glued together with transfers. The bridge treats them as legs of the same call.
Voice agents with and without a multi-protocol bridge
Without a bridgeWith the Xebit audio bridge
Escalating to a personTransfer to another system, often a redial, and the caller explains againA person joins the same call from a browser
CoachingAfter the fact, from recordingsWhisper during the call
Recording and transcriptOne per system, stitched together laterOne recording and transcript across every leg
Adding a channelA new stack for each protocolA new leg on the same bridge
Several specialised agentsBot to bot transfers that drop contextAgent to agent handoff on the same call
In practice

Useful on day one, for everyone on the call.

What the bridge means for the business running the agents, for the people they call, and for the teams building them.

For enterprises

  • A team lead steps into a collections call the moment a borrower disputes an amount, from their browser.
  • Sensitive moments go to a person on the same recorded call, so the audit trail has no gaps.
  • Keep your carrier and your existing setup. Your team joins from wherever they work.

For your customers

  • No hold music, no redial and no new number to call when they need a person.
  • The call carries on in the same conversation when someone joins.
  • A person when the moment needs one, and the agent the rest of the time.

For teams building voice agents

  • Build the agent once. Callers can arrive by phone, browser or app.
  • Stream audio to your own models and services over WebSocket or gRPC.
  • Split work across specialised agents that hand calls to each other.
Every deployment

Runs wherever the platform runs.

The bridge is part of the Xebit platform. On Xebit VoiceCloud we run it. On your infrastructure it runs inside your network, including fully air gapped. Either way the telephony stays with your carrier.
  • Xebit VoiceCloudManaged by us, priced per connected minute.
  • On premInside your network, next to your systems.
  • Air gappedInside your network with models on your GPUs. Nothing leaves the network.

Audio bridge questions

What is a multi-protocol audio bridge?

A multi-protocol audio bridge joins parties that use different real time protocols into one live call. The Xebit bridge relays audio and call events between SIP, WebRTC, WebSocket and gRPC, transcodes codecs such as G.711 and Opus, and records the whole call once, so a phone caller, an AI agent and a person in a browser can share a single conversation.

Can a person join an AI agent's phone call from a browser?

Yes. While an AI agent talks to a customer over SIP, a person on your team can join from a browser over WebRTC. They can whisper to one side without the customer hearing, join as a third party so everyone hears everyone, or take over the call from the agent. The customer stays on the same call throughout.

Does Xebit provide the phone line?

No. Xebit never provides telephony or numbers. The SIP side of the bridge connects to the carrier or SBC you already use, so your numbers, routes and rates stay yours. The bridge adds browsers, apps and your own services to those calls.

Is the whole call recorded when parties use different protocols?

Yes. The bridge produces one recording and one transcript of the whole call, across every leg, whichever protocol each party used. That includes the part where a person joined from a browser, which matters for quality review and audits.

Does the audio bridge run on prem and air gapped?

Yes. The bridge is part of the Xebit platform, so it runs wherever the platform runs: on Xebit VoiceCloud, on your own infrastructure, or fully air gapped inside your network.

SEE IT ON A LIVE CALL

Join an AI agent's call from your browser.

We will put an agent on a call, then show you whispering, joining and taking over from a browser, on our cloud or your infrastructure.