Gemini Live is Google's speech-to-speech API, running speech recognition, the model and the voice inside one session, and it connects to Vobiz for telephony: Vobiz provides the phone numbers and carries the calls, bridged to Gemini by an open-source reference service that Vobiz publishes. The audio formats line up exactly at both ends, so nothing is resampled between the caller and the model.
This one is code you run rather than a provider you select. Vobiz publishes an open-source bridge in Python that joins a Vobiz media stream to a Gemini Live session, and you deploy it somewhere Vobiz can reach over HTTPS and WSS — a tunnel is fine while you are building. It handles inbound and outbound without caring which direction the call came from. You will need a Gemini API key and a Vobiz number.
Why this pairing
Why run a Gemini Live agent on Vobiz
Gemini Live holds a spoken conversation in one session: it hears the caller, decides what to say and says it, with its own sense of when someone has stopped talking. There is no transcription step to tune and no separate voice vendor to pay. What it cannot do is reach a phone.
The usual cost of bridging a model like that to a phone line is conversion — the caller's audio resampled on the way in, the model's speech resampled on the way out, each pass costing a little quality and a little time. Gemini is fixed at one rate in and another out. Vobiz sets the two directions of a stream independently. Line them up and the conversions disappear.
Google owns
The model, the voices and the language
Speech recognition and voice activity detection
Turn-taking, interruption and conversation state
Tool calls, including ending the call
The system prompt and the agent's behaviour
Vobiz owns
Phone numbers and instant provisioning
Placing and receiving the call itself
The bidirectional audio stream to the bridge
Playback control: flush, checkpoint, confirmation
Call detail records and quality telemetry
Local regulatory compliance, including India KYC
What you get
What Vobiz adds to a Gemini Live agent
The bridge is published. What is left is a key, a number and a prompt.
01
One key for the whole conversation
Speech recognition, the model and the voice all run inside a single Gemini session on a single API key. No separate transcription vendor, no separate speech vendor, and no turn-taking logic of your own to write and then debug on a live call.
02
Nothing resampled, end to end
The two directions of a Vobiz stream are configured independently, which means they can be matched to what the model actually wants — one rate arriving, a different rate going back. Set both correctly and the caller's audio reaches the model untouched and the model's speech reaches the call untouched. Other rates work and the bridge converts them; this is the path where it does not have to.
03
Barge-in the platform confirms
When a caller talks over the agent, Gemini reports the interruption and the bridge tells Vobiz to discard the audio still queued on the line. Vobiz confirms the flush. Queued speech can run to seconds, so without both halves the caller keeps hearing a reply the model has already abandoned.
04
Say goodbye, then hang up
Sending audio is not the same as the caller hearing it. After each turn the bridge asks Vobiz to confirm playback, which is what lets the agent finish its closing line before the call ends rather than being cut off mid-word — and makes a reply nobody heard visible in the log rather than only in the call.
05
Numbers in 130+ countries, both directions on one bridge
Local, mobile and toll-free inventory across 130+ countries, including regulated formats where a market demands them — India's 140-series and 1600-series among them. Point a number's answer URL at the bridge for inbound, or place an outbound call with the same URL; the bridge does not distinguish.
06
Hold a whole conversation without placing a call
The repository ships a mock client that opens the socket the way Vobiz does, speaks a prompt, and writes the agent's reply to a file — so the bridge, the model and the formats can all be verified before a number is ever dialled, and in continuous integration afterwards.
How it works
How to connect Gemini Live to Vobiz
Pick a model, fill in a file, run it, dial.
01
Pick a Live model your key can use
Model names on the Live API change often, and choosing one your key cannot reach fails at connect time with a bare socket close and no useful message. The repository includes a script that lists exactly which ones are available to you.
02
Configure the bridge
Clone it, create a virtual environment, install the requirements and fill in the environment file: your Gemini key, the model, the voice, the greeting and system prompt, and your Vobiz credentials. The audio settings already carry the matched defaults.
03
Run it and check itself
A self-test runs dozens of checks without placing a call. Then start the bridge; it prints the answer URL, the socket address and the formats it will use in each direction.
04
Place a call
Dial out with the included script, or point a Vobiz number's answer URL at the bridge for inbound. Transcripts and stream events are readable from the bridge while the call is still running.
The full guide covers the format matrix, the stream protocol, barge-in and checkpoints, the verified call measurements and a behaviour reference mapping each symptom to its cause.
Code you run. Vobiz publishes an open-source Python bridge that joins a Vobiz media stream to a Gemini Live session, and you deploy it on an endpoint Vobiz can reach over HTTPS and WSS. There is no dashboard toggle on either side.
No. Gemini Live runs recognition, the model and the voice inside one session, so a single Gemini API key covers all three. There is no separate transcription or text-to-speech vendor, and no second bill.
You can provision numbers in 130+ countries and place outbound calls to 190, and the same bridge serves both directions — point a number's answer URL at it for inbound, or use the same URL when placing a call. Where a market has its own number formats or registration rules, Vobiz issues under them rather than routing around them, India's 140-series and 1600-series among them.
Yes, and properly. Gemini detects the caller speaking over the agent and the bridge tells Vobiz to discard the audio already queued on the line, with Vobiz confirming the flush. That second half is what stops the caller hearing the rest of a reply the model has already abandoned.
Yes. The repository includes a mock client that impersonates the Vobiz side of the socket, speaks a prompt and writes the agent's reply to a file, exiting with an error if no audio comes back. It works in continuous integration as well as on a laptop.
Gemini Live is Google's API for real-time spoken conversation with a Gemini model. Learn more in Google's Live API documentation. Vobiz is not affiliated with Google; this integration uses the public Live API. Model names and defaults reflect the reference bridge as of 21 October 2026.
We use cookies to run this site and, with your permission, to understand how it's used. Read our Cookie Policy.