https://livekit.io logo
Join Slack
Powered by
I'm using a self-hosted livekit python server conn...
# ask-ai
a
I'm using a self-hosted livekit python server connected to a livekit cloud proyect. How can I modify the livekit-proyect agents dispatch from europe instead of US
t
Thanks for reaching out, Antonio. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I understand you want agents dispatched from Europe instead of the US for a self‑hosted LiveKit Python server that’s connected to a LiveKit Cloud project. Here’s what you can and cannot change, plus the steps to get European-hosted agents. Short answer • You cannot change a LiveKit Cloud project to “force” dispatch to Europe for self‑hosted agents. Dispatch will go to whatever agent servers are currently registered and connected. • To have agents served from Europe, deploy your self‑hosted agent servers in a European region (for example AWS eu‑west, GCP europe‑west, Azure West Europe). Once those agent instances are running and connected to your LiveKit Cloud project, they will receive work just like any other connected agent. What to do (step-by-step) 1. Deploy your self-hosted LiveKit Python agent server instances in Europe (choose your cloud provider / region). 2. Configure each agent instance to connect to your LiveKit Cloud project using the same 
LIVEKIT_URL
, 
API_KEY
, and 
API_SECRET
you already use. 3. Start/registrar the agent processes. They will register with the LiveKit control plane and become available for dispatch. 4. If you want regional isolation (only European agents receive work), ensure you do not run any agent instances in US regions (or stop existing US-based agents). When LiveKit Cloud-hosted agents are relevant • If you were using LiveKit Cloud-hosted agents instead of self-hosted, you can pick a region at creation (for example 
lk agent create --region <europe-region>
). That flag applies to Cloud-hosted agent deployments only. If you’d like, I can help with next steps • Tell me which cloud provider and region you plan to use (e.g., AWS eu-west-1, GCP europe-west1). • Share how you currently start your agent (command / config) and I’ll show the exact config changes or a sample command to run in the European deployment. Sources: Agent dispatch | LiveKit Documentation | examples/drive-thru | livekit/livekit_composite | DeepWiki | Data Processing Addendum | LiveKit | Self-hosted deployments | LiveKit Documentation
a
This is my agent log of a session: Publishers Participant identity Name Location Tracks Region Used features liveavatar-avatar-agent liveavatar-avatar-agent 9 mar 2026, 155250United States US Central 9 mar 2026, 155325— voice_assistant_user_1312 user 9 mar 2026, 155244Spain France 9 mar 2026, 155302— Subscribers Participant identity Name Location Region Used features agent-AJ_XwGxGukPgo6x —9 mar 2026, 155251Spain France 9 mar 2026, 155326— As I mentioned before, how could i do to make the livekit-avatar agent be dispatched from EU
t
Thanks — I can see from your session log that the avatar agent is currently running from a US location while the user participant is in Spain/France. I’ll clarify how dispatch works and exactly what you need to do so your livekit-avatar agent is served from Europe. Key point • For self‑hosted agents, the dispatch location is determined by where your agent servers are actually deployed. You cannot change a LiveKit Cloud project to force self‑hosted agents to dispatch from a different region. To have the avatar agent run from Europe, you must run the agent instances in a European region. What to do next (practical steps) 1. Deploy the livekit-avatar agent server(s) into a European cloud region (for example AWS eu‑west‑1, GCP europe‑west1, Azure West Europe) or onto hosts physically located in Europe. 2. Configure each European agent instance with your LiveKit Cloud connection values (
LIVEKIT_URL
, 
API_KEY
, 
API_SECRET
) so they register with the same project. 3. Start the agent process on those European hosts. Once connected, those agents will be available for dispatch and will receive sessions just like your US instances. 4. If you want only EU agents to receive work, stop or remove any US‑hosted agent instances so only the European agents remain registered. If instead you want LiveKit Cloud–hosted agents in Europe • Use the Cloud agent create flow with an explicit region (for example 
lk agent create --region <europe-region>
). That only applies to agents hosted by LiveKit Cloud, not to self‑hosted servers. Follow-up questions to help me give exact commands • Which cloud provider and region do you want to deploy to (AWS/GCP/Azure and the specific EU region)? • How do you currently run the avatar agent (a Docker image, a Python script/virtualenv, or another method)? Share the start command or config if possible. If you give me those details I’ll provide the exact commands or a sample Docker/systemd start snippet and point out any config values to change so your avatar agent appears as EU in future logs.
Open in Slack
PreviousNext
Powered by