-
Notifications
You must be signed in to change notification settings - Fork 6
Description
In our implementation, our mute/unmute functionality calls jingle-media-session.switchStreams. We have found if one or multiple people mute/unmute too fast it causes all sorts of issues. We tracked it down to this:
Notice two setRemoteDescriptions then two setLocalDescriptions? I'm guessing the first one is the unmute so we are adding a new stream which takes a bit longer to fully process compared to the second one which is much quicker since it doesn't have to process the addStream. In any case, I would think the call to switchStreams would process fully (add and remove) before running the next call to switchStreams. This is definitely a race condition as it doesn't happen every time, but it does happen enough to be a problem for us. Can I provide any more information or can you provide any feedback/suggestions?
