what does ctx.wait_for_participant() do ?

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

I want to wait until SIP participant joins

Thanks — you want to wait until a SIP participant joins. You can do that by using

ctx.wait_for_participant()

and then checking the participant’s

kind

, looping until you get a SIP participant. Below are concise examples and a couple of options (looping vs. event-based) so you can pick what fits your workflow. Python (simple loop)

from livekit import rtc
from livekit.agents import JobContext

async def entrypoint(ctx: JobContext):
    while True:
        participant = await ctx.wait_for_participant()
        if participant.kind == rtc.ParticipantKind.PARTICIPANT_KIND_SIP:
            print(f"SIP participant joined: {participant.identity}")
            break
        # otherwise continue waiting for the next participant

Node.js / TypeScript (simple loop)

import { ParticipantKind } from 'livekit-server-sdk';

export default defineAgent({
  entry: async (ctx: JobContext) => {
    let participant = await ctx.waitForParticipant();
    while (participant.kind !== ParticipantKind.SIP) {
      participant = await ctx.waitForParticipant();
    }
    console.log(`SIP participant joined: ${participant.identity}`);
  },
});

Event-based alternative • Listen for the

participant_connected

event and inspect

participant.kind

. This avoids awaiting repeatedly and may be cleaner if you already use room events. Timeout / cancellation considerations • If you need to stop waiting after a certain time, add a timeout or cancellation check around the loop so your job doesn’t block indefinitely. If you’d like, tell me which of these you prefer and: • Whether you need a timeout example, or • If you want to filter further using participant metadata or identity (I can show that). Sources: Job lifecycle | LiveKit Documentation | SIP Lifecycle Management Agent | LiveKit Documentation