ghosts in the (video) room

[Flavia Sparacino]

I am polling for clues on a bug that we keep running into. Today during a four people call, one user could see and hear me but he could not see or hear the other two. On the other hand the other two could hear and see him and me.

We are using the Video Room plugin on 0.12.2 

Our logs don’t show any errors so I wonder if anyone has any suggestions. This usually happens when one of the users is on a Mac either Chrome or Safari. The user that had the issue today was on Chrome 102.0.5005.115 on Macos 10.13.6

What should we check or log so we can find out what we may be doing wrong?

Any suggestions would be appreciated. Thanks!

 Flavia

[Flavia Sparacino]

Let me clarify for relevant feedback

F invited J R and J to the call.

F joined first followed by K and R. We could all see and hear each other

F (me) then saw J come into the call. So F can see and hear all the other three participants as expected.

After a few minutes we realized that J cannot see or hear K and R. They are like ghosts to him. J can only see me (F) as in a 2 people's call.

I am seeing a total of 4 people including myself, but Jeff can only see me (F) -- two people in his client broser.

In the meanwhile K and R can see everyone including F and J.

I asked K and R to leave and rejoin the call and we could finally all see and hear each other.

Quite spooky.

Since we can't get those people back on to test we're looking for suggestions on what to test so that we can eventually reproduce or fix.

We're using the video room plugin but have not updated to multistream yet.

Thanks,

Flavia

[Mirko Brankovic]

I'm not sure what client side code are you using (janus demo ones or some custom build) but i presume that codebase would rely on new member join events and when joining room on response to room being joined with a list of participants that are already publishing so that you can subscribe to.

So your best option is to try to replicate it with inspection of network in browser console and make sure those events are given to clients correctly, if yes then might be error in client side code.

Oder option might be that at the moment J is joining, K didn't fully publish, so he wasn't in a list of participants, and then J needs to wait for new member event...if this event doesn't get to client, then it is a Janus bug

--
You received this message because you are subscribed to the Google Groups "meetecho-janus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetecho-janu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/meetecho-janus/61b3c13c-088e-4ce3-a7cb-23a33eac7062n%40googlegroups.com.

[Stefano Coser]

Similar thing happened to me using the new videoroom plugin as you can see in the image ( and to everyone else in the room, someone couldn't hear, someone had just white video but audio was working etc). Next days I'll look into server logs. Could it be a turn server problem? I'll look into that too. If you have any suggestions of other things to look into I'd appreciate a lot.

[Lorenzo Miniero]

Looks like either missing keyframes (video can't be decoded even if it's coming since the bitrate moves) or a client side issue (you're not attaching the stream/track to the video element, or the video element isn't played). If you're putting audio and video together in the video element, there may be autoplay issues you have to take into account too.

L.

[Stefano Coser]

Thanks lorenzo for the answer,

I'm using v1.0.3 and the videoroom demo as it is ( except for the number of publishers set to 25 to test some limits, so I just modified the html, the js and the publishers number on the config ). I noticed that this problem seems to occur only on Chrome: I can see through browser logs that the ice state change to disconnected ("ICE state changed to disconnected" ) and stop there, while on Firefox when those events occur they're followed by an immediate reconnection. When this happens other peers see the "No remote video available" message, and if the peer that got disconnected try to reconnect looks like the connection get restablished but the white video is showed instead .

Will dig more into it the next days.