This message was deleted.

yeah you definitely can. as long as users join the same room name, it should work. it sounds like you are seeing segregated rooms where users aren't able to see each other? If so can you tell us more about how you are able to reproduce it? • Server version (cloud or self hosted) • Client platform and version • How you are joining these rooms

we’re using AWS ECS for the server, Angular 15 how user join room : 1. everytime Admin login, Admin will join or create the room with 1 standard room name “standby_room” for the example. 2. everytime Guest access a spesific page, Guest will also join or create “standby_room”. 3. when the Admin and Guest are join in almost the same time, they will connected. But if Admin already join for a long time and then Guest join they are not connected. the Admin are not see any new participant join and the Guest also not see any participant existed. 4. to handle that i create an interval for admin to rejoin the room every 5 mins but sometime it doesn’t fix the issue and still not connected with the guest.

Please describe this in terms of specific livekit APIs that are being called (and the parameters of the API). FWIW, this doesn't sound like a bug within livekit, but more specific to your application's handling of users. Also, be sure to provide requested information above

we use Livekit SDK in Java Springboot and using accessToken creation from the Back End and using room.connect from the client side. We create every accessToken with the same room name. Then i take a look at the session there’s 3 active room with the same room name. What should i do to only have 1 active room with the unique room name?

I see, taking a look at your session since you are using Cloud. For this session, looks like you are not publishing any video or audio? Is that expected? I see the issue you are talking about, the Cloud dashboard shows multiple session ids for the same room. This can happen occasionally and is a bug in the analytics display. The participants should all be in the same room in Cloud and they will be able to see each other (you can check for them in

room.participants

). Typically, dashboard showing multiple session IDs for the same room should happen rarely. I'll look into it to understand why it appears to happen more frequently for you.

yeah in this session user are not publishing any video or audio, we playing with room.event.participantConnected and metadata. So basically if a user join the room the each user will know if someone join or someone existed in the same room. It’s actually working already, but sometimes the user can’t recognize or detect other user that was join in the same room. It’s feel like they in the same room name but different session.

Just an update here @most-terabyte-42518, we've fixed an issue on the server side that reduces the likelihood of multiple sessions appearing for the same room. Let us know if it happens for you again!

Sure, Thanks a lot! @dry-elephant-14928

ParticipantRemoved is only sent when

RemoveParticipant

API is called

no, it’s in idle condition and the web is not focused

sorry I don't understand what that means.. looking through the code.. that condition only happens with an explicit API call..

I will help to explain this. I've been looking into the backend code and couldn't find any usage of

removeParticipant

in our standby room implementation, which makes it weird for me that we're getting notifications about participants being removed. The issue seems to happen when users are idle for some time, whether not interacting with the desktop, focusing on another tab, or using another app. Is there other condition where this disconnect reason being triggered?

That is the only path this reason would get triggered. I'll DM you with a screenshot of examples of such calls