salmon-rainbow-65629
12/15/2025, 5:49 PMtall-airline-16756
12/15/2025, 5:49 PMtall-airline-16756
12/15/2025, 5:49 PMX-LK-Room-Name SIP header for selecting the room. You can accomplish room routing using SIP trunk dispatch rules and other routing mechanisms instead.
If you'd like, tell me how you expect calls to be routed (example: by caller ID, dialed number, SIP request URI, or a custom header you control) and I can suggest the specific dispatch rule setup that will map incoming calls to the correct room.
Sources: Authentication | LiveKit docssalmon-rainbow-65629
12/15/2025, 6:10 PMtall-airline-16756
12/15/2025, 6:11 PMX-Event-Log-Id) can be used directly in a dispatch rule room-name template, or how to get a predictable room name you control.
You cannot use a SIP header directly in the static room name template. Instead, map the header to a participant attribute and use that attribute in your agent/dispatch logic to determine or create the room name. Steps:
1. On the inbound trunk, add a headers_to_attributes mapping (e.g., map X-Event-Log-Id → event_log_id).
2. In your agent code, read the participant attribute (event_log_id) for SIP participants and:
◦ create/join a room named from that value (for predictable names), or
◦ route the call based on that attribute.
Alternative if you control dialed numbers: use roomPrefix in dispatchRuleCallee to derive room names from the called number.
If you want, tell me which method you prefer (header-based attribute mapping or callee-prefix) and share an example header value or dialed number; I’ll give the exact trunk config and sample agent code.
Sources: SIP dispatch rule | LiveKit docs | SIP participant | LiveKit docs