Google Gemini

Google Gemini Live

Pair Google Gemini Live API Integration with Teler for a working AI voice agent in minutes.

Category

Overview

Google’s Gemini Live API runs a low-latency, native-audio dialog agent. The bridge proxies Teler call audio into Gemini and relays the model’s spoken response back.

The bridge resamples Gemini’s 24 kHz audio down to Teler’s 8 kHz by default (or up to 16 kHz if you configure your Stream flow for higher fidelity), and lets you tune input buffering to trade off latency against smoother turn-taking.

Key Features

  • Reference implementations in Python and Node – Clone teler-gemini-bridge (Python) or teler-gemini-node-bridge (Node) and get a working bridge in minutes.
  • One-command Docker setup – Clone the repo, configure your .env, and start with a single command.
  • Tunable latency – GEMINI_AUDIO_CHUNK_COUNT controls input buffering, letting you trade off latency against smoother turn-taking.

How to Integrate

Prerequisites

  • A Google Cloud project with Gemini API access and a GOOGLE_API_KEY (refer to Google Gemini Live docs)
  • A Teler account with an active API key
  • One Teler phone number on your account
  • An ngrok auth token (for local development)
  • Docker and Docker Compose

Step 1: Clone and configure

git clone https://github.com/frejun-tech/teler-gemini-bridge
cd teler-gemini-bridge
cp .env.example .env
docker compose up -d --build

Step 2: Initiate a call

curl -X POST http://your-domain.com/api/v1/calls/initiate-call \
  -H "Content-Type: application/json" \
  -d '{
    "from_number": "+91XXXXXXXXXX",
    "to_number":   "+91XXXXXXXXXX"
  }'

Integration at a Glance

Requirements Google Cloud project with Gemini API access, Teler account with API key and phone number, Docker + Docker Compose, ngrok auth token (local dev)
Support support@frejun.com, or file an issue directly on the GitHub repo for bridge-specific bugs

Frequently Asked Questions

Have more questions?

Reach out to us at support@frejun.com.

Why is the agent silent?

Usually a typo in GEMINI_MODEL, or the model isn't released yet - check it against current Google docs.

Likely free-tier limits - check your usage in the Google Cloud Console.

Send a warm-up message before connecting the call - the first token is usually a cold start.

GEMINI_SYSTEM_MESSAGE is probably empty - set the system prompt explicitly.

Tune GEMINI_AUDIO_CHUNK_COUNT. Lower values reduce latency but increase network overhead and token consumption; higher values feel smoother but laggier. The default of 20 is a reasonable starting point.

Yes. Configure your Stream flow with sample_rate: "16k" and adjust the bridge's downsampling code - by default, it resamples Gemini's 24 kHz audio down to 8 kHz.

Get started with Teler today

Real-time voice APIs tor Al agents. WebSocket streaming.
SIP trunking, globalnumbers. Ship voice applications in hours.