Is it possible to use inbound dispatching rules to launch a named worker with a call if I'm using an on-premises Livekit server?

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

is there a way to check if a dispatching rule is set for an agent using the livekit CLI?

Hey there! You can easily check if a dispatching rule is set for an agent using the LiveKit CLI with these simple commands: 1. List all dispatches for a room: `lk dispatch list <room_name>`This will show you all the agent dispatches for the room you specify, including the

AgentName

. Just keep an eye out for the agent's name in the list. 2. Get details of a specific dispatch: `lk dispatch get <room_name> <dispatch_id>`This one gives you a closer look at a particular dispatch, showing details like the assigned

AgentName

. If you want a hand running these commands or making sense of what you see, just give me a shout—I’m here to help!

how can I find out the room name if it is listed like this translate__<caller>_<random>

Room names like

translate__<caller>_<random>

usually come from dispatch rules that create unique rooms for each caller. Here’s how you can figure out the room name: 1. Run the

listSipDispatchRule

command to see all the dispatch rules. This will give you a peek at the room name format being used. 2. Take a look at the

roomPrefix

value in the dispatch rule setup. This prefix gets combined with the caller's number and a random string to make the full room name. 3. Keep in mind the room name follows this pattern:

<roomprefix>_<caller>_<random>

. Breaking it down like this helps you spot which parts stay the same and which change. If you want a hand with any specific commands or settings, just give me a shout! Sources: cmd/lk/sip.go | SIP dispatch rule | LiveKit Docs | sip/sip.go

yes, what I need is the exact room name to be able ot use the lk dispatch get command

Figuring out the exact room name for a dispatch when it’s generated on the fly can be a bit tricky, but here are some friendly tips to help you out: 1. Check the Logs: Whenever a call is dispatched, the server logs usually include the generated room name. Taking a peek at these logs can often reveal the exact name you’re looking for. 2. Use the API: If you have access to the LiveKit API, you can pull dispatch details or keep an eye on API responses to spot the room name. 3. Set a Room Prefix: If you have control over the dispatch rule setup, try setting a

roomPrefix

. This way, the room name becomes more predictable, following the format

<roomPrefix>_<caller>_<random>

. If you’d like a hand with accessing logs or working with the API to find that room name, just give me a shout—I’m here to help! Sources: SIP dispatch rule | LiveKit Docs | SIP dispatch rule | LiveKit Docs | Dispatching agents | LiveKit Docs

what logs should I check?

To find the exact room name generated for a dispatch, you can take a look at these logs: 1. Server Logs: These capture the room name when the dispatch rule kicks in. Just look for entries about room creation or dispatch execution. 2. Client-Side Logs: If a client joins the room, you'll see the room name in the client-side logs. This comes in handy especially if you’re using the LiveKit SDK. 3. Job Logs: When an agent is dispatched to the room, the room name shows up in the job logs along with some other helpful details. If you want, I’m here to help you access or make sense of these logs—just let me know!

what if the dispatching rule has never been used to create a room? i just want to see how it is configured

If you want to check out the configuration of a dispatching rule without actually using it to create a room, here’s how you can do it: 1. List All Dispatch Rules: `lk sip dispatch list`Running this command will show you all the dispatch rules along with their details. 2. Retrieve a Specific Dispatch Rule: If you have the dispatch rule ID handy, you can narrow down the list to just that rule. You can do this using the LiveKit API or SDK to pull up the configuration. 3. Inspect Configuration Details: The configuration includes things like

roomPrefix

,

metadata

,

attributes

, and

room_config

— all the bits that explain how the rule is set up. Feel free to reach out if you want a hand running these commands or making sense of what you see! Sources: cmd/lk/sip.go | livekit-api/livekit/api/sip_service.py | SIP APIs | LiveKit Docs | livekit/livekit_sip.pb.go

are you sure that dispatching rules for SIP calls created with "lk sip inbound create" can be tied to an agent? I have read elsewere that only direct dispatchings can be tied to agent names.

You're absolutely right— not all dispatching rules can be linked directly to agent names. Only certain types, like direct dispatching, let you assign an agent directly. SIP dispatch rules created with

lk sip inbound create

usually work a bit differently and aren't tied to agents in the same way. If you want me to help clarify anything or walk you through setting up dispatch rules, just give me a shout! Sources: Accepting incoming calls | LiveKit Docs | Accepting incoming calls | LiveKit Docs | Dispatching agents | LiveKit Docs | SIP dispatch rule | LiveKit Docs