This message was deleted.

you’re doing room egress here?

web egress* but our web client joins the room with the hidden token

hm for web egress you shouldn’t have a room

the way we are using it, the web egress url when hit will have the egress client fetch a token for the pre-created room from the livekit server. that token has permissions recorder:true hidden:true

this is a highly requested feature.. and is currently tracked for here

thanks david. is there any setting for our egress participant token (currently

{hidden: true, recording: true, publisher: false, subscriber: true}

) that we could do? we assume the egress client can be connected until we explicitly end the room, so perhaps we could turn off hidden or recording and set a special metadata flag our clients use to filter out the egress participant?

yeah! that sound like a solid workaround. if the participant isn't hidden from the livekit side, but hidden from your own rendering logic, the SFU will keep the room open