Firefox being muted by other Firefox leaving

1

We are using JAAS and had a meeting with 5 people, 3 on Chrome and 2 on Firefox.

We had strange actions in the Firefox browsers and not in the Chrome ones.
When one FF user moved his performance settings to “Best Performance” my FF became “Non-optimal”. Moving the slider up change mine back. (Or maybe it was the other way around).
When the one FF user left, it muted my camera. And some action (we are not sure what) muted the audio.

Some logs I captured on my Firefox;

2023-02-02T23:16:39.743Z [modules/statistics/AudioOutputProblemDetector.js] <5369/_onLocalAudioLevelsReport/<>: A potential problem is detected with the audio output for participant 1c585fc4, local audio levels: [null,null], remote audio levels: undefined

2023-02-02T23:19:13.286Z [modules/RTC/BridgeChannel.js] : Sending ReceiverVideoConstraints with {“constraints”:{“72ea39d9-v0”:{“maxHeight”:360},“0ef74ccf-v0”:{“maxHeight”:360},“a11e5439-v0”:{“maxHeight”:360}},“defaultConstraints”:{“maxHeight”:0},“lastN”:25,“onStageSources”:,“selectedSources”:} Logger.js:154:22
2023-02-02T23:19:13.316Z [modules/xmpp/JingleSessionPC.js] : JingleSessionPC[session=JVB,initiator=false,sid=6lvahre40qf0a] setVideoCodecs: preferred=null, disabled=h264 Logger.js:154:22
2023-02-02T23:19:13.319Z [features/video-quality] <5735/<>: Video quality level for thumbnail height: 324.5, is: 360, override: false, max full res N: 2 Logger.js:154:12
2023-02-02T23:19:13.346Z [conference.js] <5735/_setupListeners/<>: USER 1c585fc4 LEFT:
Object { _jid: "3269657037@conference.vpaas-magic-cookie-

db4e95b0042744f9a3f10d50f6962704.8x8.vc/1c585fc4", _id: "1c585fc4", _conference: {…}, _displayName: "Philippe Galvez", _supportsDTMF: false, _tracks: (1) […], _role: "moderator", _status: undefined, _hidden: false, _statsID: "pgalvez@coredial.com", … }
Logger.js:154:12
2023-02-02T23:19:13.347Z [JitsiConference.js] <5369/zu.prototype._maybeStartOrStopP2P>:  Auto P2P disabled Logger.js:154:22
The description does not look like plan-b interop.js:351:48
2023-02-02T23:19:13.436Z [modules/RTC/BridgeChannel.js] <5369/_handleChannel/e.onmessage>:  New forwarded sources: 72ea39d9-v0,0ef74ccf-v0,a11e5439-v0 Logger.js:154:22
2023-02-02T23:19:13.490Z [modules/xmpp/JingleSessionPC.js] <notifyMySSRCUpdate>:  JingleSessionPC[session=JVB,initiator=false,sid=6lvahre40qf0a] Sending source-remove for video ssrcs=1196221059,1722596982,2005530896,2692838293,2842117280,3263612960,3311981109,4148611424 Logger.js:154:22
2023-02-02T23:19:13.494Z [modules/xmpp/JingleSessionPC.js] <notifyMySSRCUpdate>:  JingleSessionPC[session=JVB,initiator=false,sid=6lvahre40qf0a] Sending source-add for video ssrcs=122538388,1635622822,2376413913,3251767185,3516124594,3618160139,3911476517,4119683723 Logger.js:154:22
2023-02-02T23:19:13.498Z [modules/xmpp/JingleSessionPC.js] <5369/removeRemoteStreamsOnLeave/<>:  JingleSessionPC[session=JVB,initiator=false,sid=6lvahre40qf0a] removeRemoteStreamsOnLeave done! Logger.js:154:22
2023-02-02T23:19:13.691Z [JitsiConference.js] <5369/zu.prototype._removeLocalSourceOnReject>:  Source-add rejected on JingleSessionPC[session=JVB,initiator=false,sid=6lvahre40qf0a], reason="bad-request", message="SSRC limit (20) exceeded." Logger.js:154:22
2023-02-02T23:19:13.693Z [JitsiConference.js] <5369/zu.prototype._doReplaceTrack>:  _doReplaceTrack - no P2P JingleSession Logger.js:154:22
2023-02-02T23:19:13.703Z [modules/xmpp/JingleSessionPC.js] <5369/replaceTrack/</<>:  JingleSessionPC[session=JVB,initiator=false,sid=6lvahre40qf0a]  Replace track done! Logger.js:154:22
2023-02-02T23:19:13.705Z [features/face-landmarks] <stopDetection>:  Stop face landmarks detection Logger.js:154:12
2

In case anyone else sees this, we solved it by adding these to the config:
enableTcc: false,
disableRtx: true,

1 Like
3

Well, we are still experiencing the muting. When another user leaves the meeting, it mutes my Firefox camera.
The config options above fixed the “Best Performance”.

But sometimes I get in a mode that the other starting a camera or leaving always mutes my camera with this in the console:

2023-02-07T23:22:26.561Z [JitsiConference.js] <5369/zu.prototype._removeLocalSourceOnReject>: Source-add rejected on JingleSessionPC[session=JVB,initiator=false,sid=b3f4j02071g19], reason=“bad-request”, message=“MSID is already used: a53f50e3-video-1-1 d6dbf21a-fb95-443b-94f8-c13349cfde75-1.” Logger.js:154:22

Is there some mixup of MSIDs? Why does it seem to only affect Firefox?

4

This seems the source of the problem.

Next time you reproduce it, can you save the logs and send them to me. Use the save logs button.

Screen Shot 2023-02-08 at 2.40.27 PM

1 Like
5

Of course when I try to reproduce it it never happens :frowning:
What is that SSRC limit? Where is it set? Is it a FF limit? Does it matter if I start / stop my camera does it create a new SSRC? Is there a way we can trigger the limit? Does it matter if I am in the meeting for many hours?

6

It’s a limit in the backend, it’s set to 20 by default and on meet.jit.si. Starting and stopping the camera shouldn’t trigger it as it’s supposed to either reuse the SSRCs or remove the old ones before adding new ones, but you might be hitting a bug. It’s actually 6 SSRCs per session, so if they accumulate just 4 cycles should be enough to trigger the condition (but I’m not able to repro myself).

I don’t think it makes a difference if you stay in the meeting for a long time or not.