How can we deploy agent in australia because right now agent is in US by default so latency is more for australians customers over SIP but we wanted to deploy in Australian.

Thanks for reaching out, Sana. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

We are using live kit cloud and our STT/TTS/LLM are in australia?

Great — thanks for confirming you’re on LiveKit Cloud and your STT/TTS/LLM are already in Australia. Here are the exact next steps to deploy an agent in Australia and keep traffic local to minimize SIP latency. 1. Deploy a LiveKit Cloud agent in Sydney

lk agent create [working-dir] \
     --secrets-file .env \
     --region ap-southeast-2

• Replace

[working-dir]

and

.env

with your paths. 1. Ensure SIP traffic stays in APAC ◦ Configure your SIP trunk to use the APAC/Sydney SIP endpoint or enable region pinning so PSTN ingress/egress is routed via the APAC region. ◦ Verify your provider can route calls to an APAC endpoint (ask them if needed) and update any SIP DNS or trunk settings to point at the regional endpoint. 1. Confirm AI co‑location ◦ Since your STT/TTS/LLM are in Australia, point the agent’s plugin/integration configs to those regional endpoints so inference calls never cross to the US. ◦ If using provider-specific keys/regions (Azure, Google, etc.), ensure the agent’s plugin config references the APAC region and credentials. 1. Test and verify ◦ Make SIP calls from Australia and measure RTP/RTT and audio quality. ◦ Check agent logs for connection regions and plugin request latencies to confirm traffic is APAC-local. If you want, tell me: • your SIP provider name (I can give the likely APAC endpoint/pinning steps), and • whether you need the exact env variables or plugin config snippet for your STT/TTS/LLM — I’ll provide them., with interactive elements

Can we change the Deploy a LiveKit Cloud agent in Sydney via UI from here https://cloud.livekit.io/

Thanks — you’re asking if you can change the LiveKit Cloud agent region to Sydney via the Cloud UI. Short answer: No — the Cloud UI does not provide a way to deploy an agent to Sydney. LiveKit Cloud currently supports a limited set of regions (us-east, eu-central, ap-south) and region selection for agents is done via the CLI or by self-hosting. What you can do now: • Use the CLI to create an agent in a supported APAC region (if that meets latency needs):

lk agent create [working-dir] --secrets-file .env --region ap-south

• If you need an agent physically in Australia (Sydney) and Cloud doesn’t offer that region, self-host an agent in an Australian cloud region so SIP and inference traffic remain local. If you want, tell me: • whether the APAC region

ap-south

would be acceptable, or • if you prefer instructions for self-hosting an agent in Sydney (I can provide step-by-step setup and the required config snippets). Sources: Agents on LiveKit Cloud | Deploy voice AI on global infrastructure | LiveKi... | examples/drive-thru | livekit/livekit_composite | DeepWiki | Agent deployment overview | LiveKit Documentation | Checklist for Regional Deployments | LiveKit, with interactive elements