Closed RedSteel-1 closed 1 year ago
Do you experience the same on meet.jit.si?
Upload js console logs from the browser
Do you experience the same on meet.jit.si?
I have no idea how it is on meet.jit.si, it requires some weird login so I am not able to use it.
Upload js console logs from the browser
Sure, here is what I had in the console when I first opened a link with a meeting with a participant, activated video/audio, and joined the meeting:
` This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”. fdlkl34k5glnkjknftghrb8 Some cookies are misusing the recommended “SameSite“ attribute 2 [NoScript]:0 Prompt Hook installation https://jitsi.riot.im/fdlkl34k5glnkjknftghrb8 log.js:32:13 (TIME) index.html loaded: 1014 fdlkl34k5glnkjknftghrb8:62:17 2023-09-16T21:35:34.398Z [modules/browser/BrowserCapabilities.js] This appears to be firefox, ver: 102.0 Logger.js:154:22 2023-09-16T21:35:34.399Z [modules/statistics/LocalStatsCollector.js] <79/tn.connectAudioContext>: Connecting audio context Logger.js:154:22 2023-09-16T21:35:35.161Z [features/base/redux]
: redux state persisted. 954fa6071c683ed65ed8597465fcb0a1 -> 38223a84a94077b68aecb9c50df3b03d Logger.js:152:50 2023-09-16T21:35:35.376Z [FeatureFlags] : Source name signaling: true, Send multiple video streams: true, SSRC rewriting supported: false, uses Unified plan: true Logger.js:154:22 2023-09-16T21:35:35.377Z [modules/RTC/RTCUtils.js] : Disable AP: false Logger.js:154:22 2023-09-16T21:35:35.378Z [modules/RTC/RTCUtils.js] : Stereo: false Logger.js:154:22 2023-09-16T21:35:35.379Z [modules/connectivity/NetworkInfo.js] : updateNetworkInfo Object { isOnline: true } Logger.js:154:22 2023-09-16T21:35:35.394Z [features/base/media] <5027/</</</<>: Start muted: audio, video Logger.js:152:50 2023-09-16T21:35:35.407Z [features/base/media] <5027/</</</<>: Start audio only set to false Logger.js:152:50 2023-09-16T21:35:35.409Z [modules/statistics/AnalyticsAdapter.js] : Disposing of analytics adapter. Logger.js:154:22 2023-09-16T21:35:35.411Z [features/analytics] <5027/</</</a<>: Initialized 0 analytics handlers Logger.js:152:50 2023-09-16T21:35:35.556Z [features/base/devices] : setAudioOutputDevice: undefined[default] Logger.js:152:50 2023-09-16T21:35:35.556Z [features/base/devices] : Adjusting audio output is not supported Logger.js:152:50 2023-09-16T21:35:35.572Z [index.web] <5027/<>: (TIME) document ready: 2235 Logger.js:152:50 2023-09-16T21:35:36.028Z [modules/RTC/RTCUtils.js] : list of media devices has changed: Array [ MediaDeviceInfo, MediaDeviceInfo ] Logger.js:154:22 2023-09-16T21:35:36.030Z [modules/RTC/RTCUtils.js] <79/init/<>: Available devices:
Array [ MediaDeviceInfo, MediaDeviceInfo ] Logger.js:154:22 2023-09-16T21:35:36.032Z [features/base/devices] <5027/</</</<>: Device list updated: audioInput: Microphone (High Definition Audio Device)[FLZebnRyKNWE4kGHAONQ9O1AR+LyXss1awQFvkV+SC8=] audioOutput:videoInput: Integrated Camera[NDWTcRR8wlm/34QuCk5ZrKigDYSgFAycs9pj1t9xmO8=] Logger.js:152:50 2023-09-16T21:35:36.058Z [features/base/connection] <5027/Hle/o<>: Using service URL wss://meet.element.io/xmpp-websocket Logger.js:152:50 2023-09-16T21:35:36.059Z [modules/xmpp/xmpp.js] <_initStrophePlugins>: P2P STUN servers:
Array [ {…} ] Logger.js:154:22 2023-09-16T21:35:36.065Z [modules/xmpp/xmpp.js]: Source-name signaling is enabled Logger.js:154:22 2023-09-16T21:35:36.066Z [modules/xmpp/xmpp.js] : Receiving multiple video streams is enabled Logger.js:154:22 2023-09-16T21:35:36.067Z [modules/xmpp/xmpp.js] : (TIME) Strophe connecting: 2730 Logger.js:154:22 2023-09-16T21:35:36.071Z [features/prejoin] <5027/Yie/<>: Failed to execute pre call test - Error: Callstats is disabled init PrecallTest.js:85 Yie actions.js:316 n React 5027 middleware.js:27 5027 middleware.js:32 5027 middleware.js:18 5027 middleware.web.js:26 5027 middleware.any.js:42 5027 actions.js:58 5027 middleware.js:41 5027 middleware.js:61 5027 middleware.js:19 5027 middleware.js:175 5027 middleware.js:68 5027 middleware.js:84 5027 middleware.js:36 5027 middleware.ts:158 5027 middleware.js:79 5027 middleware.ts:18 5027 middleware.js:74 5027 middleware.js:30 5027 middleware.web.js:42 5027 middleware.web.js:21 5027 middleware.any.js:90 5027 middleware.js:75 5027 middleware.web.js:325 5027 middleware.js:44 5027 middleware.js:20 5027 middleware.js:15 5027 middleware.js:17 5027 middleware.js:18 5027 middleware.js:20 5027 middleware.js:15 5027 middleware.js:102 5027 middleware.ts:23 5027 middleware.js:227 5027 middleware.js:33 5027 middleware.js:20 5027 middleware.js:27 5027 middleware.web.js:19 5027 Redux 5027 middleware.js:332 5027 middleware.js:20 5027 middleware.ts:33 5027 middleware.js:46 5027 middleware.js:96 5027 middleware.js:11 5027 middleware.js:36 5027 middleware.js:32 5027 middleware.web.js:93 5027 middleware.any.js:106 5027 middleware.js:201 5027 middleware.js:103 5027 middleware.any.js:42 5027 middleware.js:52 5027 middleware.js:24 5027 middleware.js:22 5027 middleware.web.js:9 5027 middleware.web.js:32 5027 middleware.any.js:108 5027 middleware.js:15 5027 middleware.js:87 5027 middleware.js:72 5027 middleware.js:23 5027 middleware.js:42 5027 middleware.js:14 5027 actions.js:301 5027 middleware.js:22 5027 middleware.js:20 5027 middleware.js:72 5027 middleware.js:235 5027 middleware.web.js:20 5027 middleware.web.ts:32 5027 middleware.any.js:143 5027 actions.js:356 o middleware.ts:41 5027 middleware.ts:7 5027 middleware.ts:44 5027 middleware.web.js:122 5027 middleware.js:176 init conference.js:835 _start actions.web.js:33 promise callback*5027/_start/< actions.js:126 n React 5027 middleware.js:27 5027 middleware.js:32 5027 middleware.js:18 5027 middleware.web.js:26 5027 middleware.any.js:42 5027 actions.js:58 5027 middleware.js:41 5027 middleware.js:61 5027 middleware.js:19 5027 middleware.js:175 5027 middleware.js:68 5027 middleware.js:84 5027 middleware.js:36 5027 middleware.ts:158 5027 middleware.js:79 5027 middleware.ts:18 5027 middleware.js:74 5027 middleware.js:30 5027 middleware.web.js:42 5027 middleware.web.js:21 5027 middleware.any.js:90 5027 middleware.js:75 5027 middleware.web.js:325 5027 middleware.js:44 5027 middleware.js:20 5027 middleware.js:15 5027 middleware.js:17 5027 middleware.js:18 Logger.js:152:50 2023-09-16T21:35:36.073Z [modules/RTC/RTCUtils.js] <79/obtainAudioAndVideoPermissions/r<>: Got media constraints: {"video":false,"audio":{"autoGainControl":true,"deviceId":"Bru4APYojKjiz1IdBcwHs9TZT+BXdOfsEkL77u0mwro=","echoCancellation":true,"noiseSuppression":true}} Logger.js:154:22 2023-09-16T21:35:36.098Z [modules/RTC/RTCUtils.js] <79/_getUserMedia/</<>: onUserMediaSuccess Logger.js:154:22 2023-09-16T21:35:36.111Z [modules/RTC/JitsiLocalTrack.js] <_setStream>: Setting new MSID: {a0dd8e25-628e-4863-a80a-ac18818c379b} {9eacd7a3-e995-4e36-a47c-6a0d99dcd369} on LocalTrack[undefined,audio] Logger.js:154:22 2023-09-16T21:35:36.134Z [features/base/media] <5027/</</</<>: Sync audio track muted state to muted Logger.js:152:50 2023-09-16T21:35:36.145Z [modules/RTC/JitsiLocalTrack.js] Mute LocalTrack[1,audio]: true Logger.js:154:22 2023-09-16T21:35:36.295Z [features/base/devices] <5027/</</</<>: Device list updated: audioInput: Microphone (High Definition Audio Device)[FLZebnRyKNWE4kGHAONQ9O1AR+LyXss1awQFvkV+SC8=] audioOutput: videoInput: Integrated Camera[NDWTcRR8wlm/34QuCk5ZrKigDYSgFAycs9pj1t9xmO8=] Logger.js:152:50 2023-09-16T21:35:36.330Z [features/base/devices] <5027/</</</<>: Device list updated: audioInput: Microphone (High Definition Audio Device)[FLZebnRyKNWE4kGHAONQ9O1AR+LyXss1awQFvkV+SC8=] audioOutput:
videoInput: Integrated Camera[NDWTcRR8wlm/34QuCk5ZrKigDYSgFAycs9pj1t9xmO8=] Logger.js:152:50 2023-09-16T21:35:36.345Z [features/base/lastn] <5027/bde<>: There is no active conference, not updating last N Logger.js:152:50 Cookie “” has been rejected as third-party. xmpp-websocket 2023-09-16T21:35:37.192Z [features/base/redux]
: redux state persisted. 38223a84a94077b68aecb9c50df3b03d -> c6cf51889cfeeaf7387e506ba36cd781 Logger.js:152:50 2023-09-16T21:35:38.073Z [modules/xmpp/XmppConnection.js] <_maybeEnableStreamResume>: Enabling XEP-0198 stream management Logger.js:154:22 2023-09-16T21:35:38.075Z [modules/xmpp/XmppConnection.js] <_maybeStartWSKeepAlive>: WebSocket keep alive interval: 60000ms Logger.js:154:22 2023-09-16T21:35:38.077Z [modules/xmpp/XmppConnection.js] <_maybeStartWSKeepAlive>: Scheduling next WebSocket keep-alive in 105741.36011283164ms Logger.js:154:22 2023-09-16T21:35:38.078Z [modules/xmpp/strophe.ping.js] : XMPP pings will be sent every 10000 ms Logger.js:154:22 2023-09-16T21:35:38.079Z [modules/xmpp/xmpp.js] : (TIME) Strophe connected: 4741 Logger.js:154:22 2023-09-16T21:35:38.081Z [modules/xmpp/xmpp.js] : My Jabber ID: 6veiaiitbnwuqtvvewmuv41c@meet.jitsi/9HcLejiHNAOd Logger.js:154:22 2023-09-16T21:35:42.683Z [modules/RTC/RTCUtils.js] <79/obtainAudioAndVideoPermissions/r<>: Got media constraints: {"video":{"height":{"ideal":720},"width":{"ideal":1280},"facingMode":"user"},"audio":false} Logger.js:154:22 2023-09-16T21:35:43.324Z [features/base/redux] : redux state persisted. c6cf51889cfeeaf7387e506ba36cd781 -> 31ab0af1f88d529322239b8fae8f4e3f Logger.js:152:50 2023-09-16T21:35:44.092Z [modules/RTC/RTCUtils.js] <79/_getUserMedia/</<>: onUserMediaSuccess Logger.js:154:22 2023-09-16T21:35:44.107Z [modules/RTC/JitsiLocalTrack.js] <_setStream>: Setting new MSID: {581170dd-22b3-4453-b788-37f3600fb4b9} {3ddee6e1-df3a-4040-bede-ffe41658989e} on LocalTrack[undefined,video] Logger.js:154:22 2023-09-16T21:35:44.471Z [features/base/devices] <5027/</</</<>: Device list updated: audioInput: Microphone (High Definition Audio Device)[FLZebnRyKNWE4kGHAONQ9O1AR+LyXss1awQFvkV+SC8=] audioOutput: videoInput: Integrated Camera[NDWTcRR8wlm/34QuCk5ZrKigDYSgFAycs9pj1t9xmO8=] Logger.js:152:50 2023-09-16T21:35:44.930Z [modules/RTC/JitsiLocalTrack.js] Mute LocalTrack[1,audio]: false Logger.js:154:22 2023-09-16T21:35:45.324Z [features/base/redux]
: redux state persisted. 31ab0af1f88d529322239b8fae8f4e3f -> 2abbceaf110e870c08228afd6932e77a Logger.js:152:50 2023-09-16T21:35:52.054Z [modules/RTC/CodecSelection.js] : Codec preferences for the conference are JVB: vp8, P2P: vp8 Logger.js:154:22 2023-09-16T21:35:52.056Z [modules/xmpp/xmpp.js] : JID 6veiaiitbnwuqtvvewmuv41c@meet.jitsi/9HcLejiHNAOd using MUC nickname 7850d8ec Logger.js:154:22 2023-09-16T21:35:52.057Z [modules/xmpp/ChatRoom.js] : Joined MUC as fdlkl34k5glnkjknftghrb8@muc.meet.jitsi/7850d8ec Logger.js:154:22 2023-09-16T21:35:52.060Z [modules/statistics/AvgRTPStatsReporter.js] : Avg RTP stats will be calculated every 15 samples Logger.js:154:22 2023-09-16T21:35:52.061Z [JitsiConference.js] : backToP2PDelay: 5 Logger.js:154:22 2023-09-16T21:35:52.062Z [modules/videosipgw/VideoSIPGW.js] : creating VideoSIPGW Logger.js:154:22 2023-09-16T21:35:52.063Z [modules/util/TaskQueue.js] <_executeNext>: Executing a task. Logger.js:152:50 2023-09-16T21:35:52.064Z [modules/util/TaskQueue.js] <_onTaskComplete>: Task completed. Logger.js:152:50 2023-09-16T21:35:52.064Z [conference.js] <5027/_setLocalAudioVideoStreams/t<>: _setLocalAudioVideoStreams is calling useVideoStream with track: LocalTrack[2,video] Logger.js:152:50 2023-09-16T21:35:52.064Z [conference.js] : useVideoStream: LocalTrack[2,video] Logger.js:152:50 2023-09-16T21:35:52.065Z [modules/util/TaskQueue.js] <_executeNext>: Executing a task. Logger.js:152:50 2023-09-16T21:35:52.065Z [conference.js] <5027/useVideoStream/</<>: useVideoStream: Replacing LocalTrack[2,video] with LocalTrack[2,video] Logger.js:152:50 2023-09-16T21:35:52.066Z [modules/util/TaskQueue.js] <_onTaskComplete>: Task completed. Logger.js:152:50 2023-09-16T21:35:52.066Z [JitsiConference.js] <79/Mh.prototype._doReplaceTrack>: _doReplaceTrack - no JVB JingleSession Logger.js:154:22 2023-09-16T21:35:52.067Z [JitsiConference.js] <79/Mh.prototype._doReplaceTrack>: _doReplaceTrack - no P2P JingleSession Logger.js:154:22 2023-09-16T21:35:52.067Z [JitsiConference.js] <79/Mh.prototype._doReplaceTrack>: _doReplaceTrack - no JVB JingleSession Logger.js:154:22 2023-09-16T21:35:52.068Z [JitsiConference.js] <79/Mh.prototype._doReplaceTrack>: _doReplaceTrack - no P2P JingleSession Logger.js:154:22 2023-09-16T21:35:52.095Z [modules/xmpp/moderator.js] <79/pr.prototype.setFocusUserJid>: Focus jid set to: focus@auth.meet.jitsi Logger.js:154:22 2023-09-16T21:35:52.096Z [modules/xmpp/moderator.js] <79/pr.prototype.createConferenceIq>: Session ID: null machine UID: c6e84d907cf01a08ffd0026b7f6375eb Logger.js:154:22 2023-09-16T21:35:52.098Z [conference.js] <5027/_setLocalAudioVideoStreams/<>: Initialized with 2 local tracks Logger.js:152:50 2023-09-16T21:35:52.161Z [modules/xmpp/moderator.js] <79/pr.prototype.parseConfigOptions>: Authentication enabled: false Logger.js:154:22 2023-09-16T21:35:52.162Z [modules/xmpp/moderator.js] <79/pr.prototype.parseConfigOptions>: External authentication enabled: false Logger.js:154:22 2023-09-16T21:35:52.165Z [modules/xmpp/moderator.js] <79/pr.prototype.parseConfigOptions>: Sip gateway enabled: false Logger.js:154:22 2023-09-16T21:35:52.353Z [modules/xmpp/ChatRoom.js] : (TIME) MUC join started: 19016 Logger.js:154:22 2023-09-16T21:35:52.451Z [modules/xmpp/ChatRoom.js] : entered fdlkl34k5glnkjknftghrb8@muc.meet.jitsi/focus Object { isReplaceParticipant: 0, affiliation: "owner", role: "moderator", jid: "focus@auth.meet.jitsi/focus", isFocus: true, isHiddenDomain: false } Logger.js:154:22 2023-09-16T21:35:52.469Z [modules/version/ComponentsVersions.js] <79/ch.prototype.processVersions/<>: Got focus version: 1.0.911 Logger.js:154:22 2023-09-16T21:35:52.475Z [JitsiConference.js] <79/Mh.prototype._updateProperties>: Audio unmute permissions set by Jicofo to false Logger.js:154:22 2023-09-16T21:35:52.480Z [JitsiConference.js] <79/Mh.prototype._updateProperties>: Video unmute permissions set by Jicofo to false Logger.js:154:22 2023-09-16T21:35:52.481Z [modules/xmpp/ChatRoom.js] : Jicofo supports restart by terminate: true Logger.js:154:22 2023-09-16T21:35:52.494Z [modules/UI/videolayout/LargeVideoManager.js] <5027/scheduleLargeVideoUpdate/<>: hover in 7850d8ec Logger.js:152:50 2023-09-16T21:35:52.519Z [modules/xmpp/ChatRoom.js] : entered fdlkl34k5glnkjknftghrb8@muc.meet.jitsi/bfcbc98a Object { isReplaceParticipant: 0, affiliation: "owner", role: "moderator", jid: "pvkfnyyjaxv1kyxwrjwnixeb@meet.jitsi/EQBH-ORSjVqI", isFocus: false, isHiddenDomain: false, statsID: "Marcos-9py", features: Set(1), nick: "fdgfe5rgfbg" } Logger.js:154:22 2023-09-16T21:35:52.592Z [conference.js] <5027/_setupListeners/<>: USER bfcbc98a connected: Object { _jid: "fdlkl34k5glnkjknftghrb8@muc.meet.jitsi/bfcbc98a", _id: "bfcbc98a", _conference: {…}, _displayName: "fdgfe5rgfbg", _supportsDTMF: false, _tracks: [], _role: "moderator", _status: undefined, _hidden: false, _statsID: "Marcos-9py", … } Logger.js:152:50 2023-09-16T21:35:52.642Z [conference.js] <5027/_setupListeners/<>: My role changed, new role: none Logger.js:152:50 2023-09-16T21:35:52.667Z [modules/xmpp/ChatRoom.js] : (TIME) MUC joined: 19330 Logger.js:154:22 2023-09-16T21:35:52.788Z [JitsiConference.js] <79/Mh.prototype._maybeStartOrStopP2P>: Auto P2P disabled Logger.js:154:22 2023-09-16T21:35:52.821Z [modules/xmpp/ChatRoom.js] : Subject is changed to Logger.js:154:22 2023-09-16T21:35:52.831Z [modules/xmpp/strophe.jingle.js] : Found a JSON-encoded element in session-initiate, translating to standard Jingle. Logger.js:154:22 2023-09-16T21:35:52.833Z [modules/xmpp/strophe.jingle.js] : Received session-initiate from fdlkl34k5glnkjknftghrb8@muc.meet.jitsi/focus with sources=jvb:[2948503818,238099417] Logger.js:154:22 2023-09-16T21:35:52.834Z [modules/xmpp/strophe.jingle.js] : (TIME) received session-initiate: 19494 Logger.js:154:22 2023-09-16T21:35:52.851Z [modules/RTC/TraceablePeerConnection.js] : Create new TPC[id=1,type=JVB] Logger.js:154:22 2023-09-16T21:35:52.853Z [modules/RTC/BridgeChannel.js] : constructor() with wsUrl:"wss://meet.element.io/colibri-ws/172.20.11.226/167d2d09eacd5617/7850d8ec?pwd=1actq0lnn8tgb8gufdhvsajmva" Logger.js:154:22 2023-09-16T21:35:52.857Z [modules/xmpp/JingleSessionPC.js] : JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] Queued setOfferAnswerCycle task Logger.js:154:22 2023-09-16T21:35:52.857Z [JitsiConference.js] <79/Mh.prototype._acceptJvbIncomingCall>: Starting CallStats for JVB connection... Logger.js:154:22 2023-09-16T21:35:52.857Z [modules/statistics/RTPStatsCollector.js] <79/_n.prototype.start>: Using RTCRtpSynchronizationSource for remote audio levels Logger.js:154:22 2023-09-16T21:35:52.859Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype.addTrack>: TPC[id=1,type=JVB] adding LocalTrack[1,audio] Logger.js:154:22 2023-09-16T21:35:52.861Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype.addTrack>: TPC[id=1,type=JVB] adding LocalTrack[2,video] Logger.js:154:22 2023-09-16T21:35:52.932Z [modules/xmpp/JingleSessionPC.js] <_responderRenegotiate>: JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] Renegotiate: setting remote description Logger.js:154:22 2023-09-16T21:35:53.026Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype._remoteTrackAdded>: TPC[id=1,type=JVB] ignored remote 'stream added' event for non-user stream[id=mixedmslabel] Logger.js:154:22 2023-09-16T21:35:53.028Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype._remoteTrackAdded>: TPC[id=1,type=JVB] ignored remote 'stream added' event for non-user stream[id=mixedmslabel] Logger.js:154:22 2023-09-16T21:35:53.086Z [modules/xmpp/JingleSessionPC.js] <79/_responderRenegotiate/<>: JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] Renegotiate: creating answer Logger.js:154:22 2023-09-16T21:35:53.096Z [modules/xmpp/JingleSessionPC.js] <79/_responderRenegotiate/</<>: JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] Renegotiate: setting local description Logger.js:154:22 2023-09-16T21:35:53.115Z [modules/xmpp/JingleSessionPC.js] <79/setOfferAnswerCycle/<>: JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] setOfferAnswerCycle task done Logger.js:154:22 2023-09-16T21:35:53.135Z [modules/xmpp/JingleSessionPC.js] : JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] Sending session-accept Logger.js:154:22 2023-09-16T21:35:53.136Z [modules/xmpp/JingleSessionPC.js] : Logger.js:154:22 Cookie “” has been rejected as third-party. 7850d8ec 2023-09-16T21:35:53.279Z [modules/UI/videolayout/LargeVideoManager.js] <5027/scheduleLargeVideoUpdate/<>: hover in bfcbc98a Logger.js:152:50 2023-09-16T21:35:54.133Z [modules/xmpp/strophe.jingle.js] : Found a JSON-encoded element in source-add, translating to standard Jingle. Logger.js:154:22 2023-09-16T21:35:54.135Z [modules/xmpp/strophe.jingle.js] : Received source-add from fdlkl34k5glnkjknftghrb8@muc.meet.jitsi/focus with sources=bfcbc98a:[2735772222,939554489,3177939835] Logger.js:154:22 2023-09-16T21:35:54.136Z [modules/xmpp/JingleSessionPC.js] <_addOrRemoveRemoteStream>: JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] Queued addRemoteStream task Logger.js:154:22 2023-09-16T21:35:54.150Z [modules/xmpp/JingleSessionPC.js] <79/_addOrRemoveRemoteStream/<>: JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] Processing addRemoteStream Logger.js:154:22 2023-09-16T21:35:54.165Z [modules/xmpp/JingleSessionPC.js] <_responderRenegotiate>: JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] Renegotiate: setting remote description Logger.js:154:22 2023-09-16T21:35:54.217Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype._remoteTrackAdded>: TPC[id=1,type=JVB] adding remote track for stream[id=bfcbc98a-audio-0-2,type=audio] Logger.js:154:22 2023-09-16T21:35:54.219Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype._remoteTrackAdded>: TPC[id=1,type=JVB] creating remote track[endpoint=bfcbc98a,ssrc=3177939835,type=audio,sourceName=bfcbc98a-a0] Logger.js:154:22 2023-09-16T21:35:54.222Z [modules/RTC/JitsiRemoteTrack.js] : New remote track added: RemoteTrack[userID: bfcbc98a, type: audio, ssrc: 3177939835, p2p: false, sourceName: bfcbc98a-a0, status: readyState: live, muted: true, enabled: true] Logger.js:154:22 2023-09-16T21:35:54.247Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype._remoteTrackAdded>: TPC[id=1,type=JVB] adding remote track for stream[id=bfcbc98a-video-0-2,type=video] Logger.js:154:22 2023-09-16T21:35:54.248Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype._remoteTrackAdded>: TPC[id=1,type=JVB] creating remote track[endpoint=bfcbc98a,ssrc=2735772222,type=video,sourceName=bfcbc98a-v0] Logger.js:154:22 2023-09-16T21:35:54.249Z [modules/RTC/JitsiRemoteTrack.js] : New remote track added: RemoteTrack[userID: bfcbc98a, type: video, ssrc: 2735772222, p2p: false, sourceName: bfcbc98a-v0, status: readyState: live, muted: true, enabled: true] Logger.js:154:22 2023-09-16T21:35:54.251Z [modules/qualitycontrol/ReceiveVideoController.js] : Updating ReceiverVideoConstraints {"constraints":{"bfcbc98a-v0":{"maxHeight":720}},"defaultConstraints":{"maxHeight":0},"lastN":-1,"onStageSources":["bfcbc98a-v0"],"selectedSources":[]} Logger.js:154:22 2023-09-16T21:35:54.259Z [modules/connectivity/TrackStreamingStatus.ts] : RtcMuteTimeout set to: 10000 Logger.js:154:22 2023-09-16T21:35:54.260Z [modules/RTC/JitsiRemoteTrack.js] <_addEventListener>: Initializing track streaming status: bfcbc98a-v0 Logger.js:154:22 2023-09-16T21:35:54.284Z [modules/UI/videolayout/LargeVideoManager.js] <5027/scheduleLargeVideoUpdate/<>: hover in bfcbc98a Logger.js:152:50 2023-09-16T21:35:54.310Z [modules/xmpp/JingleSessionPC.js] <79/_responderRenegotiate/<>: JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] Renegotiate: creating answer Logger.js:154:22 2023-09-16T21:35:54.317Z [modules/xmpp/JingleSessionPC.js] : JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] setSenderVideoConstraint: 2160, sourceName: 7850d8ec-v0 Logger.js:154:22 2023-09-16T21:35:54.318Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype.setSenderVideoConstraints>: TPC[id=1,type=JVB] Setting degradation preference [preference=maintain-framerate,track=LocalTrack[2,video] Logger.js:154:22 2023-09-16T21:35:54.320Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype.setSenderVideoConstraints>: TPC[id=1,type=JVB] setting max height=2160,encodings=[{"active":true,"degradationPreference":"maintain-framerate","maxBitrate":2500000,"rid":"1","scaleResolutionDownBy":1},{"active":true,"degradationPreference":"maintain-framerate","maxBitrate":700000,"rid":"2","scaleResolutionDownBy":2},{"active":true,"degradationPreference":"maintain-framerate","maxBitrate":200000,"rid":"3","scaleResolutionDownBy":4}] Logger.js:154:22 2023-09-16T21:35:54.344Z [modules/xmpp/JingleSessionPC.js] : JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] sendIceCandidate: last candidate Logger.js:154:22 2023-09-16T21:35:54.354Z [modules/xmpp/JingleSessionPC.js] : JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] sendIceCandidate: last candidate Logger.js:154:22 2023-09-16T21:35:54.364Z [modules/xmpp/JingleSessionPC.js] <79/_responderRenegotiate/<>: JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] Renegotiate: setting local description Logger.js:154:22 (TIME) Render audio: 21036 JitsiRemoteTrack.js:294:16 (TIME) TTFM audio: 19445 JitsiRemoteTrack.js:313:16 2023-09-16T21:35:54.373Z [modules/RTC/JitsiRemoteTrack.js] <_containerEventHandler>: canplaythrough handler was called for a container with attached RemoteTrack[userID: bfcbc98a, type: audio, ssrc: 3177939835, p2p: false, sourceName: bfcbc98a-a0, status: readyState: live, muted: true, enabled: true] Logger.js:154:22 2023-09-16T21:35:54.376Z [modules/xmpp/JingleSessionPC.js] <79/doInitialize/this.peerconnection.oniceconnectionstatechange>: (TIME) ICE checking JVB: 21038 Logger.js:154:22 2023-09-16T21:35:54.416Z [modules/xmpp/JingleSessionPC.js] <79/_addOrRemoveRemoteStream/<>: JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] addRemoteStream - OK Logger.js:154:22 2023-09-16T21:35:54.420Z [modules/RTC/BridgeChannel.js] <79/_handleChannel/e.onopen>: websocket channel opened Logger.js:154:22 2023-09-16T21:35:54.420Z [JitsiConferenceEventManager.js] <79/Mn.prototype.setupRTCListeners/<>: (TIME) data.channel.opened: 21083 Logger.js:154:22 2023-09-16T21:35:54.423Z [modules/RTC/BridgeChannel.js] : Sending SourceVideoTypeMessage with video type 7850d8ec-v0: camera Logger.js:154:22 2023-09-16T21:35:54.424Z [modules/RTC/BridgeChannel.js] : Sending ReceiverVideoConstraints with {"constraints":{"bfcbc98a-v0":{"maxHeight":720}},"defaultConstraints":{"maxHeight":0},"lastN":-1,"onStageSources":["bfcbc98a-v0"],"selectedSources":[]} Logger.js:154:22 2023-09-16T21:35:54.425Z [modules/RTC/BridgeChannel.js] <79/_handleChannel/e.onmessage>: Received ServerHello, version=undefined. Logger.js:154:22 2023-09-16T21:35:54.426Z [modules/RTC/BridgeChannel.js] <79/_handleChannel/e.onmessage>: SenderSourceConstraints: {"sourceName":"7850d8ec-v0","maxHeight":2160} Logger.js:154:22 2023-09-16T21:35:54.427Z [modules/qualitycontrol/SendVideoController.js] <_onSenderConstraintsReceived>: Sender constraints for source:7850d8ec-v0 changed to maxHeight:2160 Logger.js:154:22 2023-09-16T21:35:54.427Z [modules/xmpp/JingleSessionPC.js] : JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] setSenderVideoConstraint: 2160, sourceName: 7850d8ec-v0 Logger.js:154:22 2023-09-16T21:35:54.428Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype.setSenderVideoConstraints>: TPC[id=1,type=JVB] Setting degradation preference [preference=maintain-framerate,track=LocalTrack[2,video] Logger.js:154:22 2023-09-16T21:35:54.431Z [modules/RTC/TraceablePeerConnection.js] <79/Ld.prototype.setSenderVideoConstraints>: TPC[id=1,type=JVB] setting max height=2160,encodings=[{"active":true,"degradationPreference":"maintain-framerate","maxBitrate":2500000,"rid":"1","scaleResolutionDownBy":1},{"active":true,"degradationPreference":"maintain-framerate","maxBitrate":700000,"rid":"2","scaleResolutionDownBy":2},{"active":true,"degradationPreference":"maintain-framerate","maxBitrate":200000,"rid":"3","scaleResolutionDownBy":4}] Logger.js:154:22 2023-09-16T21:35:54.432Z [modules/RTC/BridgeChannel.js] <79/_handleChannel/e.onmessage>: Dominant speaker: bfcbc98a, previous speakers: Logger.js:154:22 2023-09-16T21:35:54.485Z [modules/xmpp/JingleSessionPC.js] : JingleSessionPC[session=JVB,initiator=false,sid=cso23a2si7lt7] sendIceCandidates [{"candidate":"candidate:0 1 UDP 8331263 172.20.61.249 53387 typ relay raddr 172.20.61.249 rport 53387","sdpMid":"0","sdpMLineIndex":0,"usernameFragment":"6ed7df0a"}] Logger.js:154:22 2023-09-16T21:35:54.640Z [modules/UI/videolayout/LargeVideoManager.js] <5027/scheduleLargeVideoUpdate/<>: hover in bfcbc98a Logger.js:152:50 2023-09-16T21:36:54.635Z [modules/RTC/BridgeChannel.js] <79/_handleChannel/e.onmessage>: Endpoint connection status changed: 7850d8ec active=false Logger.js:154:22 2023-09-16T21:36:55.207Z [modules/RTC/BridgeChannel.js] <79/_handleChannel/e.onmessage>: Endpoint connection status changed: 7850d8ec active=true Logger.js:154:22 `
Do you experience the same on meet.jit.si?
I have no idea how it is on meet.jit.si, it requires some weird login so I am not able to use it.
Then what is the jitsi-meet version you use?
2023-09-16T21:35:34.398Z [modules/browser/BrowserCapabilities.js] This appears to be firefox, ver: 102.0 Logger.js:154:22
That is a pretty old version of Firefox, were you able to try something more recent?
Then what is the jitsi-meet version you use?
That is a pretty old version of Firefox
Absolutely not old, as mentioned in the initial post the browsers I use are of recent versions: "Mullvad v12.5.4, Librewolf v116"
firefox, ver: 102.0
This comes from Mullvad v12.5.4 which was released a few days ago and is based on recent 102.15.1 ESR
That link doesn't tell us what server version they installed.
It would be best if you could test with meet.jit.si since it always runs the latest.
It would be best if you could test with meet.jit.si since it always runs the latest.
I would do that with pleasure, however I don't know how:
it requires some weird login so I am not able to use it.
Once you click on login you'll be presented with a site which allows you to login with either Google, Facebook or GitHub. After logging in you'll be redirected to the meeting, but authenticated.
You only need to do this for the first participant which joins the meeting.
Sorry, but I cannot do this.
You are using GitHub right now.
"Once you click on login you'll be presented with a site which allows you to login with either Google, Facebook or GitHub. After logging in you'll be redirected to the meeting, but authenticated.
You only need to do this for the first participant which joins the meeting."
This is terrible, buggy, and inefficient. Change it back to what it was before.
"Using Jitsi Meet is straightforward, as it's browser based. Head over to meet.jit.si and give it a try. It's anonymous, scalable and free to use. All browsers are supported!"
As you can see, anonymous is bolded. So please don't tell people they need to have accounts with either Google, Facebook or GitHub to moderate a room they themselves started.
I just tested the issue using MullVad on Windows, together with Firefox/Chrome too, specifically on meet.jit.si.
Apart from a few bandwidth drops, which seem unrelated, both the microphone and camera worked as expected. I did notice that Firefox performed slightly better compared to Mullvad, which could be due to some requests being blocked by the VPN.
If you're not using meet.jit.si and have customized your installation, could you please provide more details? It's possible that the issue isn't directly related to Jitsi but rather due to specific security settings in your environment.
Otherwise, I think we should close this one.
I just tested the issue using MullVad on Windows, together with Firefox/Chrome too
Wait, was it Mullvad Browser, or Mullvad the VPN thing?
Apart from a few bandwidth drops, which seem unrelated, both the microphone and camera worked as expected.
You mean the meeting participants could see and hear you, and you could see and hear them?
Firefox performed slightly better compared to Mullvad, which could be due to some requests being blocked by the VPN
Which VPN do you mean, there is no VPN, Mullvad is basically Tor browser without the Tor component
and have customized your installation
I have tested using default clean profiles in Mullvad Browser and Librewolf
could you please provide more details? It's possible that the issue isn't directly related to Jitsi but rather due to specific security settings in your environment.
Ok, later in a few days I will test and check the firewall logs again and report if there was something I didn't notice before
I'll reopen if you can provide logs of a failed meeting, otherwise theee is nothing actionable here.
I'll reopen if you can provide logs of a failed meeting, otherwise theee is nothing actionable here.
I already provided the log, see above.
Moreover, in my response to Codeshark-NET I replied that I will check everything again later in a few days.
So, could you open it?
I just tested the issue using MullVad on Windows, together with Firefox/Chrome too
Wait, was it Mullvad Browser, or Mullvad the VPN thing?
Mullvad browser.
You mean the meeting participants could see and hear you, and you could see and hear them?
Yep!
Which VPN do you mean, there is no VPN, Mullvad is basically Tor browser without the Tor component
That's my mistake, I was referring to the browser and its security features.
That's my mistake, I was referring to the browser and its security features.
I remember I also disabled fingerprint resistance in about:config in Mullvad to see if it makes it work (it didn't), and double-checked that WebRTC feature is enabled (and it was enabled by default)
(And the same issue was faced in Librewolf, which uses a different and non-ESR browser engine version)
Anyway, this is very strange that you got it work in Mullvad Browser, did you alter any default parameters or was it a fresh vanilla profile?
Anyway, this is very strange that you got it work in Mullvad Browser, did you alter any default parameters or was it a fresh vanilla profile?
No, I installed it fresh to check this exact issue. Couldn't replicate. I'm afraid you may have to be open to it being something on your end.
I'll keep an eye out for your further testing here, but until then, @saghul is right that there's not much we can do outside of this.
I finally got to test it again.
One more thing I wanted to check was my Firewall. Even though I configured it to allow UDP for Mullvad and Librewolf, I decided to temporarily disable it completely and test again, the results were the same as before.
Also, it seems like the remote video/audio-stream are just not allowed to play. When camera turns on in Mullvad/Librewolf, something happens, but instead of the image a black screen is shown. And when camera turns on on the opponent's side, something happens again, but the black screen is shown instead of the opponents image. (despite the fact that I can see myself from my local camera in Mullvad/Librewolf)
I can confirm that Firefox under Linux OS (Debian, Fedora) does not work....audio and video are muted Firefox version from 94.x to 112. Tested on 2 different HW platforms(native) , additional in 2 different Linux flavours in VirtualBox'es. Browsers that works in all above cases: Konqueror, Brave, Chrome
But a WIN 7 OS, Firefox 115 works All test via meet.jit.si
I don't think the operating system is the problem but the version, can you confirm?
Fedora 37 kernel 6.5.7-100, Firefox 118.0.2 --- works ok Fedora 37 kernel 6.5.7-100, Firefox 106.0.1 --- not working Fedora 36 kernel 6.2.15.100, Firefox 112.0.1 ---- not working Fedora 32 kernel 5.11.22-100, Firefox 88.0.1---- not working OpenSuse tumbleweed kernel 6.5.9-1, Firefox 119.0 --- ok
So maybe Firefox 115 => works
Update: Fedora 36 with Firefox 113.0 ---ok For what ever reason FF 113.0 is only in koji.fedoraproject.org not in update repository
Ping @jallamsetty1
I tried FF 102esr and I confirm it does not work:
2023-11-15T14:17:04.433Z [modules/xmpp/JingleSessionPC.js] <560/setOfferAnswerCycle/<>: JingleSessionPC[session=JVB,initiator=false,sid=2im0ejobgdult] setOfferAnswerCycle task failed: TypeError: s is undefined [Logger.js:155:26](webpack://JitsiMeetJS/node_modules/@jitsi/logger/lib/Logger.js)
r Logger.js:155
setOfferAnswerCycle JingleSessionPC.js:1192
Test it on alpha.
Thanks @damencho, I will try with FF 102 ESR.
When will this fix float into meet.jit.si ?
Hopefully sometime this week.
My jitsi installation completely started crashing every single meeting on EVERY browser yesterday. I did a clean installation of jitsi and after much configuration I managed to get it back to work. However; I has completely stopped working with firefox and firefox related browsers.
I will admit I had not updated any packages since it's initial installation back in August. Moreover, I checked my traffic and found that 30% of my users are on firefox.
Is there something that changed or that could have gotten misconfigured somehow?
In between all the debugging I saw a very quick message about firefox and it doing something new maybe having to do with websockets. I've since looked for that message again but have not been able to locate it in my logs or in the firefox console output.
Any help is appreciated
However; I has completely stopped working with firefox and firefox related browsers.
What version of Firefox are you seeing this on? Are you seeing the same behavior on meet.jit.si as well?
I have no more information for now but some customer using Firefox started to tell us that Jitsi (on prem) is not working anymore : continuous deconnexion . We will provide more details when we have them
Can confirm, firefox doesn't work. Tried on multiple systems. Using Firefox 128 on W11 & W10
Will fetch all the logs from my containers tomorrow, I've been troubleshooting this for a few hours now and didn't for ONCE think it could be the damn browser so I'mma just take the L and go home to my dog to make up.
Be back in ~18 hours.
@guemi Are you able to reproduce this issue on meet.jit.si? If you are not able to reproduce it there, we suggest you to update your deployments to the latest stable and test it again.
I'll try, I updated to latest stable like a week ago as part of major update of infra. But I'll verify tomorrow and let you know.
Any specific things you want from the browser, or only the container logs?
I can connect, chat is working but no video or audio is coming through or received by other user.
Please try to reproduce the issue on meet.jit.si first. If you reproduce it there, please share the browser console logs.
meet.jit.si works splendid with the same systems, same browsers but not on the on premises solution.
Just tried, I deleted all the images off the docker host and ran the stack again so it 100% pulled the images:
But no dice. Firefox does not work, picture is available until someone joins, then it disappears. If I join the same meeting in Edge, it works flawlessly. Chat message from client1 and client2 works splendid.
Attached is the console output from Firefox . jitsi console.txt
meet.jit.si works splendid with the same systems, same browsers but not on the on premises solution.
Just tried, I deleted all the images off the docker host and ran the stack again so it 100% pulled the images:
But no dice. Firefox does not work, picture is available until someone joins, then it disappears. If I join the same meeting in Edge, it works flawlessly. Chat message from client1 and client2 works splendid.
Attached is the console output from Firefox . jitsi console.txt
same here
Can you pls compare meet.jit.si settings at https://meet.jit.si/config.js with that of your deployment and see what is different?
These files are extremely different, the variable names and what not are not the same -is that to be expected?
Here's a snippetof the on prem solution;
/ Jitsi Meet configuration.
var config = {};
if (!config.hasOwnProperty('hosts')) config.hosts = {};
config.hosts.domain = 'meet.jitsi';
config.focusUserJid = 'focus@auth.meet.jitsi';
var subdir = '';
var subdomain = "";
if (subdir.startsWith('<!--')) {
subdir = '';
}
if (subdomain) {
subdomain = subdomain.substring(0,subdomain.length-1).split('.').join('_').toLowerCase() + '.';
}
config.hosts.muc = 'muc.' + subdomain + 'meet.jitsi';
config.bosh = '/' + subdir + 'http-bind';
// Video configuration.
//
if (!config.hasOwnProperty('constraints')) config.constraints = {};
if (!config.constraints.hasOwnProperty('video')) config.constraints.video = {};
config.resolution = 720;
config.constraints.video.height = { ideal: 720, max: 720, min: 180 };
config.constraints.video.width = { ideal: 1280, max: 1280, min: 320};
config.disableSimulcast = false;
config.startVideoMuted = 10;
config.startWithVideoMuted = false;
if (!config.hasOwnProperty('flags')) config.flags = {};
config.flags.sourceNameSignaling = true;
config.flags.sendMultipleVideoStreams = true;
config.flags.receiveMultipleVideoStreams = true;
// ScreenShare Configuration.
//
config.desktopSharingFrameRate = { min: 5, max: 5 };
// Audio configuration.
//
config.enableNoAudioDetection = true;
config.enableTalkWhileMuted = false;
config.disableAP = false;
if (!config.hasOwnProperty('audioQuality')) config.audioQuality = {};
config.audioQuality.stereo = false;
config.startAudioOnly = false;
config.startAudioMuted = 10;
config.startWithAudioMuted = false;
config.startSilent = false;
config.enableOpusRed = false;
config.disableAudioLevels = false;
config.enableNoisyMicDetection = true;
Is that correct?
Many if statements seem completely missing from SaaS JITSI, but is present on on-premises.
Can you pls add
config.bridgeChannel = { preferSctp: true };
config.flags.ssrcRewritingEnabled = true;
and check if that makes any difference?
Hi We are using latest jitsi js library (https://web-cdn.jitsi.net/meetjitsi_8077.4968/libs/lib-jitsi-meet.min.js?v=8077.4968). Facing an issue with Firefox version 127 and above, 1) Call connected but audio is not audible. 2) Screen share not working.
Checked the solution 'config.bridgeChannel = { preferSctp: true }; config.flags.ssrcRewritingEnabled = true;' but it did not fix the issue.
Observation: When p2p is enabled, then one-to-one call between chrome user and firefox user (OR) both firefox users, call gets connected and voice is audible but screenshare is still not working.
Is there any specific config setting for latest version of firefox to fix the issue?
Thanks!
Note: Firefox version that tested up to 124 is working fine.
Can someone please share the JVB log from their deployment? I am unable to reproduce the issue on meet.jit.si
meet.jit.si works splendid with the same systems, same browsers but not on the on premises solution.
Just tried, I deleted all the images off the docker host and ran the stack again so it 100% pulled the images:
But no dice. Firefox does not work, picture is available until someone joins, then it disappears. If I join the same meeting in Edge, it works flawlessly. Chat message from client1 and client2 works splendid.
Attached is the console output from Firefox . jitsi console.txt
Are these logs from the latest stable? There seems to be some mixup with the upgrade process, as per the logs you are running a much older version of the client. Release 8252 is from Jan 2023 which explains the issue that you are seeing.
Hi We are using latest jitsi js library (https://web-cdn.jitsi.net/meetjitsi_8077.4968/libs/lib-jitsi-meet.min.js?v=8077.4968). Facing an issue with Firefox version 127 and above,
- Call connected but audio is not audible.
- Screen share not working.
Checked the solution 'config.bridgeChannel = { preferSctp: true }; config.flags.ssrcRewritingEnabled = true;' but it did not fix the issue.
Observation: When p2p is enabled, then one-to-one call between chrome user and firefox user (OR) both firefox users, call gets connected and voice is audible but screenshare is still not working.
Is there any specific config setting for latest version of firefox to fix the issue?
Thanks!
Note: Firefox version that tested up to 124 is working fine.
What backend version are you using?
meet.jit.si works splendid with the same systems, same browsers but not on the on premises solution. Just tried, I deleted all the images off the docker host and ran the stack again so it 100% pulled the images: But no dice. Firefox does not work, picture is available until someone joins, then it disappears. If I join the same meeting in Edge, it works flawlessly. Chat message from client1 and client2 works splendid. Attached is the console output from Firefox . jitsi console.txt
Are these logs from the latest stable? There seems to be some mixup with the upgrade process, as per the logs you are running a much older version of the client. Release 8252 is from Jan 2023 which explains the issue that you are seeing.
Ugh, apparently the version variable in the docker compose was set to -stable-8252 rather than -stable. Fixed that now. And you're right, Firefox worked.
I recommend the rest of you checking the same, I'm not sure why you'd specify a specific version but recommend you configure your docker-compose like this;
services:
# Frontend
web:
image: jitsi/web:${JITSI_IMAGE_VERSION:-stable}
# XMPP server
prosody:
image: jitsi/prosody:${JITSI_IMAGE_VERSION:-stable}
# Focus component
jicofo:
image: jitsi/jicofo:${JITSI_IMAGE_VERSION:-stable}
# Video bridge
jvb:
image: jitsi/jvb:${JITSI_IMAGE_VERSION:-stable}
Rather than what I had before;
services:
# Frontend
web:
image: jitsi/web:${JITSI_IMAGE_VERSION:-stable-8252}
# XMPP server
prosody:
image: jitsi/prosody:${JITSI_IMAGE_VERSION:-stable-8252}
# Focus component
jicofo:
image: jitsi/jicofo:${JITSI_IMAGE_VERSION:-stable-8252}
# Video bridge
jvb:
image: jitsi/jvb:${JITSI_IMAGE_VERSION:-stable-8252}
Hi We are using latest jitsi js library (https://web-cdn.jitsi.net/meetjitsi_8077.4968/libs/lib-jitsi-meet.min.js?v=8077.4968). Facing an issue with Firefox version 127 and above,
- Call connected but audio is not audible.
- Screen share not working.
Checked the solution 'config.bridgeChannel = { preferSctp: true }; config.flags.ssrcRewritingEnabled = true;' but it did not fix the issue. Observation: When p2p is enabled, then one-to-one call between chrome user and firefox user (OR) both firefox users, call gets connected and voice is audible but screenshare is still not working. Is there any specific config setting for latest version of firefox to fix the issue? Thanks! Note: Firefox version that tested up to 124 is working fine.
What backend version are you using?
Hi, I have two backends and the issue happens in both. Attaching both backend versions for your reference....
Hi jallamsetty1,
Any update on my above comment.
Thanks
Hi jallamsetty1,
Any update on my above comment.
Thanks
Both the versions are old, one is an year old and the other one is 6 months old. We suggest upgrading to the latest stable from July 2nd for the issue to be fixed.
Both the versions are old, one is an year old and the other one is 6 months old. We suggest upgrading to the latest stable from July 2nd for the issue to be fixed.
Hi, Thanks. Upgrade fix the issue. Thanks again Jallamsetty
Does anyone have any idea what change/commit fixes this issue?
Thanks.
Description:
Jitsi doesn't work in Firefox-based browsers. Meanwhile, it works in Chromium-based browsers.
Steps to reproduce:
Expected behavior:
Everything works.
Actual behavior:
When I start a conference in Jitsi (with camera and mic enabled ofc), the situation is as follows:
Server information:
Client information:
Additional information: