millions-actor-17966
08/08/2025, 7:10 AMtall-airline-16756
08/08/2025, 7:10 AMmillions-actor-17966
08/08/2025, 7:13 AMtall-airline-16756
08/08/2025, 7:13 AMmillions-actor-17966
08/08/2025, 7:25 AMtall-airline-16756
08/08/2025, 7:25 AMagent_name
in WorkerOptions
, automatic dispatch gets turned off. To make sure your agent actually gets dispatched, you'll want to use one of these clear methods:
• Calling the AgentDispatchService API to create a dispatch request with the agent name and room.
• Adding the agent name in the room configuration when you generate the participant's access token.
• Setting the agent name within your SIP dispatch rules.
Also, it’s a good idea to double-check that:
• Your agent is up and running, registered with the LiveKit server.
• The room exists or has been created before you try dispatching the agent.
If any of this feels tricky or you want a hand walking through the steps, just give me a shout—I’m here to help!millions-actor-17966
08/08/2025, 7:52 AMtall-airline-16756
08/08/2025, 7:53 AMagent_name
in WorkerOptions
exactly matches the one used in your dispatch rule.
• Explicit Dispatch: Since agent_name
turns off automatic dispatch, be sure your dispatch rule is set up to explicitly assign the agent to the room.
• Dispatch Rule Validation: Take a look for any conflicts in your dispatch rules, like duplicate trunk IDs, inbound numbers, or priority mix-ups.
• Trunk Configuration: Double-check that the trunk ID and inbound numbers are correct and align with your dispatch rule.
• Agent Registration: Confirm the agent is running and properly registered with the LiveKit server.
If you want, I’m happy to walk you through validating your dispatch rules or help troubleshoot any specific parts of your setup. Just let me know how you’d like to move forward!
Sources: sip/sip.go | livekit-protocol/livekit/protocol/sip.pyi | SIP Integration | livekit/livekit_composite | DeepWiki | Agents telephony integration | LiveKit Docs | Dispatching agents | LiveKit Docstall-airline-16756
08/08/2025, 7:55 AMRegisterWorkerResponse
message. This happens behind the scenes in the agent’s setup.
So, based on what you’ve shared, your agent seems to be registered just fine. If you want to double-check anything else or run into any issues, just give me a shout—I’m here to help!
Sources: test/agent.go | livekit-agents/livekit/agents/worker.py | Anatomy of an Agent | LiveKit Docs | Anatomy of an Agent | LiveKit Docs | Anatomy of an Agent | LiveKit Docs