advise me
Setting Up LiveKit Agent Dispatch
Sin...
# ask-aim
melodic-garage-3113
07/10/2025, 6:29 PMadvise me
Setting Up LiveKit Agent Dispatch
Since you're not using SIP and need pattern-based room matching for app-generated rooms, you
have two options:
Option 1: Use a Wildcard/Prefix Pattern (If Supported)
In the dispatch rule creation form:
1. Rule name: Mother Moon Agent Dispatch
2. Rule type: Keep as Direct
3. Room name: Try entering mother-moon-* or just mother-moon to see if it accepts wildcards
or prefix matching
4. Agent dispatch: Already enabled ✓
5. Agent name: Enter the name that matches your Python agent worker (it's showing "My
telephony agent" as placeholder)
6. Dispatch metadata: You can add:
{
"agent_type": "mother_moon",
"version": "1.0"
}
Option 2: Explicit Room Name (For Testing)
If wildcards aren't supported, you'll need to either:
1. Use a fixed room name in your iOS app:
⏺️ *Update*(MotherMoonV2/LiveKitVoiceAssistantView.swift)
⎿ Updated MotherMoonV2/LiveKitVoiceAssistantView.swift with 2 additions and 1 removal
456 room!.add(delegate: self)
457
458 // Generate token with agent configuration
459 - let roomName = "mother-moon-\(UUID().uuidString.prefix(8))"
459 + // Use a fixed room name for dispatch rule matching
460 + let roomName = "mother-moon-room" // Fixed name for dispatch rule
461 let participantName = "user-\(UUID().uuidString.prefix(8))"
462
463 print("LiveKit: Creating room: \(roomName) for participant:
\(participantName)")
⏺️ 2. Create multiple dispatch rules for different room patterns if needed
Option 3: External Dispatcher (Production Solution)
For production with dynamic room names, you'll need an external dispatcher service that:
⏺️ *Write*(agent/external_dispatcher.py)
⎿ Wrote 73 lines to agent/external_dispatcher.py
#!/usr/bin/env python3
"""
External dispatcher for LiveKit agents
Monitors room creation and dispatches agents based on room name patterns
"""
import asyncio
import logging
from livekit import api
from dotenv import load_dotenv
… +63 lines (ctrl+r to expand)
⏺️ Recommended Setup Steps:
For Immediate Testing:
1. In the LiveKit dashboard dispatch rule form:
- Rule name: Mother Moon Voice Agent
- Room name: mother-moon-room (exact match since we changed iOS app to use fixed name)
- Agent name: Leave empty or enter your agent identifier
- Click Create
2. Make sure your Python agent is running:
cd /Users/jesselinson/mother-moon-v2/agent
python simple_agent.py dev
3. Build and run the iOS app - it will now connect to the fixed room name
For Production:
1. SIP Trunks Option: If you can use SIP trunks, you can create pattern-based dispatch rules
in the dashboard
2. External Dispatcher: Run the external dispatcher service that monitors rooms and
dispatches agents programmatically
3. Server-Side Token Generation: Generate tokens on your backend and include agent dispatch
metadata
The key insight from the documentation is that LiveKit Cloud's built-in dispatch rules work
best for SIP scenarios. For app-generated dynamic room names, you'll need either:
- Use fixed room names (simplest for testing)
- Implement an external dispatcher service (best for production)
Once you create the dispatch rule in the dashboard with the fixed room name mother-moon-room,
your voice agent should automatically join when the iOS app creates that room.
t
tall-airline-16756
07/10/2025, 6:29 PMThanks for reaching out, Jesse. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
tall-airline-16756
07/10/2025, 6:30 PMLiveKit Agent Dispatch currently only supports exact room name matching in dispatch rules. Wildcard or pattern-based matching (such as using prefixes or wildcards like
mother-moon-* Copy code
dispatch = await lkapi.agent_dispatch.create_dispatch(
api.CreateAgentDispatchRequest(
agent_name=agent_name,
room=room_name,
metadata='{"user_id": "12345"}'
)
) Copy code
token = (
AccessToken()
.with_room_config(
RoomConfiguration(
agents=[
RoomAgentDispatch(agent_name="test-agent", metadata='{"user_id": "12345"}')
],
),
)
)s
stocky-accountant-55381
07/10/2025, 11:28 PMIf I wanted to manually generate the JWT token what would the JWT payload need to look like for me to be able to do token based dispatch
t
tall-airline-16756
07/10/2025, 11:29 PMHey there! Let me walk you through generating a JWT token for agent dispatch in LiveKit. It's pretty straightforward, and I'll break it down in a friendly way.
Example JWT payload:
Copy code
{
"iss": "your-api-key",
"sub": "participant-identity",
"exp": 1234567890,
"nbf": 1234567890,
"video": {
"room": "room-name",
"roomJoin": true
},
"roomConfig": {
"agents": [
{
"agentName": "your-agent-name",
"metadata": "{\"user_id\": \"12345\"}"
}
]
}
}trueRoomAgentDispatchagentss
stocky-accountant-55381
07/10/2025, 11:33 PMthis token is allowing the room and participant to be added but the agent is not being dispatched
t
tall-airline-16756
07/10/2025, 11:34 PMHey there! Having trouble getting your agent dispatched? No worries, I'll walk you through some quick troubleshooting steps that might help solve the mystery.
• Agent Name Match: Double-check that the
agentNameroomConfig.agentsagent_nameWorkerOptionsroomConfigLIVEKIT_URLLIVEKIT_API_KEYLIVEKIT_API_SECRETs
stocky-accountant-55381
07/10/2025, 11:40 PM{
"iss": "key",
"sip": {
"admin": true,
"call": true
},
"sub": "identity",
"video": {
"roomList": true,
"roomAdmin": true,
"roomCreate": true,
"roomJoin": true,
"room": "room-name"
},
"roomConfig": {
"agents": [
{
"agentName": "agent-name"
}
]
}
}
above is an example of my JWT payload and I have confirmed that all details are correct and matching the agent working including, agent name, keys, secrets, and url
t
tall-airline-16756
07/10/2025, 11:41 PMHey there! I totally get how frustrating JWT payload issues can be. Let me help you troubleshoot this LiveKit agent dispatch challenge in a way that'll hopefully make things click.
• Field naming must match
camelCaseagentNameagent_nameroomConfigroom_configroomConfig.agentsagent_name="agent-name"metadataagentNameagent_nameagent_namecamelCasem
melodic-garage-3113
07/11/2025, 3:42 AMsolve this ConnectionError: could not establish signal connection: invalid token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoiSmVzc2UgTGluc29uIiwibWV0YWRhdGEiOiJ7XCJ1c2VyX3R5cGVcIjogXCJjdXN0b21lclwiLCBcInJvb21fbmFtZVwiOiBcImJkNzEtNWMzZC02YmQ1XCIsIFwiZW52aXJvbm1lbnRcIjogXCJQUk9EXCJ9IiwidmlkZW8iOnsicm9vbUpvaW4iOnRydWUsInJvb20iOiJiZDcxLTVjM2QtNmJkNSIsImNhblB1Ymxpc2giOnRydWUsImNhblN1YnNjcmliZSI6dHJ1ZSwiY2FuUHVibGlzaERhdGEiOnRydWUsImNhblVwZGF0ZU93bk1ldGFkYXRhIjp0cnVlfSwic3ViIjoiY3VzdG9tZXJfamVzc2UrOTA1OTQzNEBib29rdmlkLmNvbSIsImlzcyI6IkFQSXdiUUZVZ3BKUUVvUSIsIm5iZiI6MTc1MjIwMzA3NiwiZXhwIjoxNzUyMjI0Njc2fQ.4iJkK1wn0Gu1zPS6ZQso67HBfxomKdyF5OsMT16HkDY, error: go-jose/go-jose: error in cryptographic primitive
t
tall-airline-16756
07/11/2025, 3:43 AMHey there! Looks like you're running into a tricky JWT verification error with LiveKit. Don't worry, we'll help you get this sorted out. 😊
• API Secret Mismatch: Let's double-check your API secret. Make sure it's an exact match between what you're using to sign the token and what's set up in your LiveKit project.
• Signing Algorithm: Quick tip - you'll want to use
HS256isssubexpnbfvideoroomJoinroomissexpHS256