salmon-belgium-62133
12/17/2025, 8:26 AMtall-airline-16756
12/17/2025, 8:26 AMtall-airline-16756
12/17/2025, 8:26 AMsalmon-belgium-62133
12/17/2025, 8:27 AMtall-airline-16756
12/17/2025, 8:27 AMsalmon-belgium-62133
12/17/2025, 8:27 AMtall-airline-16756
12/17/2025, 8:27 AMgoogle.realtime.RealtimeModel to route audio/video to Gemini for live inference.
• You can use its built‑in TTS/turn detection or disable those to combine with other STT/TTS plugins (for custom voices or separate streaming STT).
• Typical uses: voice assistants, vision‑enabled agents (support, tutoring, accessibility), and interactive apps needing very low latency.
If you want, I can:
• Show a minimal AgentSession example for Gemini Realtime.
• Explain how to combine Gemini Realtime with a separate TTS or STT plugin.
Which would you like?
Sources: Gemini Live API plugin | LiveKit docs | Vision | LiveKit Docs | Google AI and LiveKit | LiveKit Docssalmon-belgium-62133
12/17/2025, 8:28 AMtall-airline-16756
12/17/2025, 8:29 AMap-south-1, GCP asia-south1 (Mumbai), or Azure Central India — colocate your agent VM/container in the same region.
Why
• Gemini Realtime runs inference close to the agent when agents are in the same region, reducing network hops and round‑trip time.
• Using a Mumbai region minimizes client → agent → model latency for users in India.
Actionable steps
1. Choose LiveKit Cloud and set agent region to Asia‑Pacific (Mumbai).
2. Or, self‑host in Mumbai (AWS/GCP/Azure) and ensure networking to Gemini endpoints is routed from that region.
3. Monitor latency with Agents metrics like Time To First Token (TTFT) and Time To First Byte (TTFB); adjust region if needed.
Would you like a short deployment checklist for LiveKit Cloud Mumbai or self‑hosting commands for one cloud provider?salmon-belgium-62133
12/17/2025, 8:30 AMtall-airline-16756
12/17/2025, 8:30 AM