microscopic-airport-67304
08/07/2025, 3:24 PMtall-airline-16756
08/07/2025, 3:25 PMtall-airline-16756
08/07/2025, 3:25 PMlk sip outbound update --id <sip-trunk-id> --name "My updated outbound trunk"
Inbound Trunk Name Update:
• Using direct flag approach:
lk sip inbound update --id <sip-trunk-id> --name "My updated inbound trunk"
Dispatch Rule Name Update:
• Using direct flag approach:
lk sip dispatch update --id <sip-dispatch-rule-id> --name "My updated dispatch rule"
For more complex updates, you can use JSON files to specify additional fields. Let me know if you need further assistance!
Sources: SIP outbound trunk | LiveKit Docs | autocomplete/fish_autocompletemicroscopic-airport-67304
08/07/2025, 6:56 PMtall-airline-16756
08/07/2025, 6:57 PMlk sip dispatch update --id <dispatch-rule-id> --trunks "<trunk-id1>, <trunk-id2>"
This will update the trunk IDs linked to your dispatch rule. Just swap out <dispatch-rule-id>
with the ID of the rule you’re updating, and replace <trunk-id1>, <trunk-id2>
with the SIP trunk IDs you want to connect.
Feel free to reach out if you want me to walk you through it or if you have any other questions!
Sources: livekit/livekit_sip.pb.go | SIP APIs | LiveKit Docsmicroscopic-airport-67304
08/07/2025, 7:08 PMtall-airline-16756
08/07/2025, 7:08 PMrule
field isn’t properly included in your dispatch rule creation request. Could you double-check if you’re specifying the rule
field, like dispatch_rule_direct
or dispatch_rule_individual
, in your request? If you can, please share the structure or a snippet of the code you’re using to create the dispatch rule—I'd love to help you figure this out!microscopic-airport-67304
08/07/2025, 7:09 PM{
"name": "inbound dispatch rule",
"rule": {
"dispatchRuleIndividual": {
"roomPrefix": "voice_assistant_room_inbound_+###########"
}
},
"trunk_ids": [
"ST_*******"
],
"roomConfig": {
"agents": [
{
"agentName": "voice-agent"
}
]
}
}
tall-airline-16756
08/07/2025, 7:09 PMdispatchRuleIndividual
is properly nested under rule
. From what I see, it looks correct in your JSON.
2. Take a look at the roomPrefix
value. It shouldn’t have any invalid characters. For example, swapping out "voice_assistant_room_inbound_+###########"
for a clean prefix like "voice_assistant_room_inbound_"
could help.
3. Double-check the trunk_ids
array to confirm the trunk ID is valid and actually exists in your system.
4. Also, see if the roomConfig
field is supported by your API version. If you’re unsure, try temporarily removing it to see if the rule creation goes through.
Once you’ve tried these tweaks, give creating the dispatch rule another shot. And if it’s still giving you trouble, just let me know—I’m here to help!