Setup: voice agents on livekit-agents 1.4.6 (Python 3.11), inbound SIP via Twilio Elastic SIP Trunking → LiveKit Cloud SIP (project p_3tqm7ro6kbs), agent dispatch via inbound trunk + dispatch rule. Each call = one agent worker process. What we saw (2026-06-08, UTC): ┌────────────┬──────────────…

What do you see in your agent logs?

{"message": "received job request", "level": "INFO", "name": "livekit.agents", "job_id": "AJ_NWYstzRMnfLS", "dispatch_id": "AD_b4jVwW8jpGMJ", "room": "twilio_fsa_use2_000_inbound_prod_deployment_+13134028862_BLheSpcxKWTQ", "room_id": "RM_jusR5FARB6hz", "agent_name": "prod_inbound", "resuming": false…

Looks like there was no agent capacity, and the server was waiting for agents to report WS_AVAILABLE. A worker became available at 31.46 and the parked job was placed immediately.

Thanks for the response. We have autoscaling and we spin up resources at 50% CPU / memory capacity. So that we can handle the burst of calls quickly. The default capacity for the worker is 80% I believe. Do you see any logs around why the worker mentioned no worker available? We are on 1.4.6 versi…

What do you have num_idle_processes set to? How do you see the work distributed through out your cluster during that time? How long had the “new” instances been added before the dispatch happened. “Cold” instances can take time to warm up. What was the load before you hit the high load moment?

num_idle_processes - set to default, 4 cores CPU - so 4 processes Work distribution - 3 worker pods at the time, on AWS EKS (us-east-2). Load at the timeframe - steady ~300 job dispatches per 5 minutes (~1 new call/sec) across the 3 pods from 14:15–14:40 UTC — no spike at 14:29 Autoscaling - we sca…

No the Signal Connection times out is a separate issue - hence raised it as a separate post

I dug into the logs for (RM_cHCojGmsaoQw and the worker logs). Quick summary of what I’m seeing: This isn’t a dispatch problem, jobs are getting assigned in ~0.2s. The delay is entirely in the agent joining the room after assignment. In the worst case the agent took ~13s to join, and cloud-sip hold…

@CWilson - I am a bit confused now - are we saying that this is because of network connectivity issues and NOT due to worker capacity issues? Is this related to Signal connection times out on the "v0 path" at agent join, forcing a fallback that adds 0.5–5s of call-setup latency - #5 by Zaheer_Abbas …

Inbound SIP call: agent job dispatched ~8s after the INVITE reached LiveKit Cloud — caller had already hung up

Getting Started

CWilson June 10, 2026, 6:43pm 12

This issue is a network issue that is aggravated by the capacity issue.

Signal connection times out on the "v0 path" at agent join, forcing a fallback that adds 0.5–5s of call-setup latency

Topic		Replies	Views
SIP Inbound call - Agent is not joining and Getting Started	5	277	February 18, 2026
TwiML SIP dispatch occasionally ringing endlessly Telephony sip-twilio , sip-trunking , livekit-cloud	10	85	May 13, 2026
Inbound SIP calls from Asterisk keep ringing - no 200 OK sent Self Hosting sip-trunking	2	150	February 16, 2026
Did something change recently? Agents agent-development , other , livekit-cloud	5	100	May 27, 2026
Livekit Agent Dispatch issue, hosted on livekit cloud Agents agent-development , other , livekit-cloud	15	336	June 2, 2026

Inbound SIP call: agent job dispatched ~8s after the INVITE reached LiveKit Cloud — caller had already hung up

Related topics