Multi-Protocol Audio Bridge

Join a live call from the browser to whisper, join or take over, and connect WebRTC, WebSocket and gRPC legs.

Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.

The audio bridge joins SIP, WebRTC, WebSocket and gRPC in one live call. While an agent talks to a customer on the phone, a person on your team can open the call in a browser and whisper, join in or take over, with no transfer and no redial. Every party keeps its own protocol, codecs are converted automatically, and one recording covers every leg.

The legs of a call

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

The bridge relays audio and call events between every party in real time, converts codecs such as G.711 and Opus where they differ, and records the call once. Xebit never provides the phone line: the SIP leg connects to the carrier or SBC you already use.

Join a call from the browser

  1. Sign in to the dashboard at voice.xebit.ai in a browser with microphone access.
  2. Sign in to the Xebit VoiceKit admin console on your host in a browser with microphone access. Your network must allow WebRTC between the browser and the platform.
  3. Open the list of live calls, or the live view of a running campaign, and choose the call.
  4. Choose how to take part: whisper, join or take over.
  5. Allow the browser to use your microphone when it asks.

Whichever mode you pick, the customer stays on the same call. There is no hold, no new number and no redial, and the recording keeps running.

Whisper, join and take over

ModeWho hears whomUse it when
WhisperYou speak to one side only. The customer does not hear you.Coaching a colleague, or steering the conversation without interrupting it.
JoinEveryone hears everyone: the customer, the agent and you.A specialist answers one question, or a team lead confirms an exception, and the agent carries on.
Take overYou continue the call. The agent drops off or goes quiet.Disputes, distress, compliance sensitive moments, or anything the agent should not handle alone.

Write the agent's handoff rules so it knows when to call a person in, and tell it what to say while someone joins. See Configure an Agent.

Connect WebRTC, WebSocket and gRPC legs

Beyond the phone leg, you can bring other parties into a call over the protocol that suits them.

WebRTC: browsers and apps

Use WebRTC when people join from a browser or your own app, either your team joining live calls or customers calling an agent from inside your app rather than from a phone. The agent is the same; only the way the caller arrives changes.

WebSocket: your own services

Use WebSocket to stream a call's audio to your own services or a third party bot, for example to run your own analysis alongside the call. The bridge handles the codec conversion, so your service receives audio it can use.

gRPC: internal services and other agents

Use gRPC for services that exchange audio and call events with the platform, including handing a live call from one AI agent to another specialised agent on a different service without the caller noticing a seam.

The endpoints, authentication and connection details for each leg are in the API Reference; authenticate as described in Auth Setup. Xebit can also build the connection into your system as part of deployment.

On Xebit VoiceCloud, legs connect to Xebit's infrastructure at api.voice.xebit.ai.

On Xebit VoiceKit, legs connect to your own host, so your services and browsers must be able to reach it inside your network. In an air gapped deployment every leg stays inside the network.

One recording across every leg

The bridge produces one recording and one transcript of the whole call, whichever protocol each party used, including the part where a person joined from a browser. That matters for quality review and audits. See Call Recordings.

Next steps