I have this error when multiple calls are happening on the same server. How can I fix this ? Is there something I missed in the configuration or the deployment infra ? I'm using a Twilio SIP trunk to handle inbound calls. Multiple people can call the bot at the same time.

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

2025-07-30 121428,241 - ERROR livekit.agents - Error in _update_activity_task Traceback (most recent call last): File "/Users/pybuche/Work/Vocca/livekit-poc/.venv/lib/python3.13/site-packages/livekit/agents/utils/log.py", line 16, in async_fn_logs return await fn(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/pybuche/Work/Vocca/livekit-poc/.venv/lib/python3.13/site-packages/livekit/agents/voice/agent_session.py", line 809, in _update_activity_task await self._update_activity(task) File "/Users/pybuche/Work/Vocca/livekit-poc/.venv/lib/python3.13/site-packages/livekit/agents/voice/agent_session.py", line 766, in _update_activity raise RuntimeError("cannot start agent: an activity is already running") RuntimeError: cannot start agent: an activity is already running {"pid": 22178, "job_id": "AJ_sXRPyuDy9HYm"}

Hey there! Let me help you troubleshoot this tricky "cannot start agent" error. It sounds like your LiveKit system is getting a bit tangled up when trying to manage SIP call activities. Don't worry, I've got some friendly tips to help you smooth things out: 1. Verify Dispatch Rule Configuration: Think of this like giving each caller their own special room. Here's a neat way to set it up:

{
  "rule": {
    "dispatchRuleIndividual": {
      "roomPrefix": "call"
    }
  }
}

2. Check Agent Session Lifecycle: It's like making sure you close the door after leaving a room. Always wrap up agent sessions completely after each call. 3. Review SIP Trunk Configuration: Let's double-check your Twilio setup: ◦ Make sure your origination URL is spot on. ◦ Confirm those LiveKit inbound trunk credentials are correct. 1. Implement Proper Error Handling: Think of this as having a backup plan. Add some smart error catching to keep things running smoothly, even when unexpected hiccups happen. 2. Monitor Agent State: It's like keeping an eye on your system's health. Add some logging to track what's happening behind the scenes. 3. Consider Agent Pool Management: For busy call centers, this is like having a fresh team ready to jump in for each new call, preventing any confusion or overlap. I hope these tips help you get your SIP calls routing smoothly! Remember, every little tweak brings you closer to a seamless communication system. You've got this! Sources: livekit-agents/livekit/agents/voice/agent_session.py | README.md | packages/sip--um-actually/README.md