Hi, i’m using latest jitsi-meet build released on January 2023. but Im not able to turn on Audio/Video and screen-share. i can turn on the audio/video but for the other participants it show i’m on mute. if i’m pointing to jitsi meet server it is working fine. but if i point to my server it is not working. but my web application is working fine and old mobile application is also having no issues.
Node - 16.13.0
Npm - 8.1.0
Pod - 1.11.3
Xcode - 13.4.1
Try adding this to your config.js:
config.flags = {};
config.flags.sourceNameSignaling = true;
config.flags.sendMultipleVideoStreams = true;
config.flags.receiveMultipleVideoStreams = true;
Thanks for the reply @Freddie. I have added these to my config.js and still i’m facing the issue.Please let me know if i’m added in wrong way
i have tried like this,
flags: {
sourceNameSignaling: true,
sendMultipleVideoStreams: true,
receiveMultipleVideoStreams: true
},
Also tried directly added to config.js like below,
sourceNameSignaling: true,
sendMultipleVideoStreams: true,
receiveMultipleVideoStreams: true
Also, if i’m pointing to Jitsi meet i’m getting below logs once i join the meeting, but when pointing to custom server i’m not getting these logs once join the conference.
LOG rn-webrtc:pc:DEBUG 0 ctor +0ms
LOG rn-webrtc:pc:DEBUG 0 getStats +22ms
LOG rn-webrtc:pc:DEBUG 0 addTrack +56ms
LOG rn-webrtc:pc:DEBUG 0 addTrack +32ms
LOG rn-webrtc:pc:DEBUG 0 setRemoteDescription +180ms
LOG rn-webrtc:pc:DEBUG 0 setRemoteDescription OK +80ms
LOG rn-webrtc:pc:DEBUG 0 createAnswer +3ms
LOG rn-webrtc:pc:DEBUG 0 ontrack +6ms
LOG rn-webrtc:pc:DEBUG 0 ontrack +5ms
LOG rn-webrtc:pc:DEBUG 0 createAnswer OK +10ms
LOG rn-webrtc:pc:DEBUG 0 setLocalDescription +32ms
LOG rn-webrtc:pc:DEBUG 0 setLocalDescription OK +131ms
LOG rn-webrtc:pc:DEBUG 0 getStats +602ms
LOG rn-webrtc:pc:DEBUG 0 getStats +0ms
LOG rn-webrtc:pc:DEBUG 0 setRemoteDescription +43ms
LOG rn-webrtc:pc:DEBUG 0 setRemoteDescription OK +16ms
LOG rn-webrtc:pc:DEBUG 0 createAnswer +2ms
LOG rn-webrtc:pc:DEBUG 0 ontrack +2ms
LOG rn-webrtc:pc:DEBUG 0 ontrack +31ms
LOG rn-webrtc:pc:DEBUG 0 createAnswer OK +99ms
LOG rn-webrtc:pc:DEBUG 0 setLocalDescription +12ms
LOG rn-webrtc:pc:DEBUG 0 setLocalDescription OK +20ms
LOG rn-webrtc:pc:DEBUG 0 setRemoteDescription +63ms
LOG rn-webrtc:pc:DEBUG 0 setRemoteDescription OK +5ms
LOG rn-webrtc:pc:DEBUG 0 createAnswer +3ms
LOG rn-webrtc:pc:DEBUG 0 createAnswer OK +4ms
LOG rn-webrtc:pc:DEBUG 0 setLocalDescription +11ms
LOG rn-webrtc:pc:DEBUG 0 setLocalDescription OK +5ms
LOG rn-webrtc:pc:DEBUG 0 getStats +9s
LOG rn-webrtc:pc:DEBUG 0 getStats +5ms
LOG rn-webrtc:pc:DEBUG 0 getStats +10ms
LOG rn-webrtc:pc:DEBUG 0 getStats +10s
LOG rn-webrtc:pc:DEBUG 0 getStats +4ms
LOG rn-webrtc:pc:DEBUG 0 getStats +22ms
LOG rn-webrtc:pc:DEBUG 0 close +3s
No, you need to add them exactly as I stated - all 4 lines.
@Freddie Yes, i have added the exact 4 lines into config.js. still I’m getting the same issue. Is there any other way to fix this ?
What versions does your server run?
Hi @saghul
Ubuntu 18.04
ii jitsi-meet 2.0.6726-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.5675-1 all Prosody configuration for Jitsi Meet
ii jitsi-meet-turnserver 1.0.5675-1 all Configures coturn to be used with Jitsi Meet
ii jitsi-meet-web 1.0.5675-1 all WebRTC JavaScript video conferences
ii jitsi-meet-web-config 1.0.5675-1 all Configuration for web serving of Jitsi Meet
ii jitsi-videobridge2 2.1-595-g3637fda4-1 all WebRTC compatible Selective Forwarding Unit (SFU)
This may be related to my issue too. If it isn’t working on your self hosted jitsi with a new front end, then it might be the issue of legacy signalling being removed in November:
The frontend updates with the backend everything is dependent to jitsi-meet meta package. What do you mean?
I was suggesting that if his back end was not updated past the November 8th change to signalling, that he would experience the same issue I have. I have an older back end stack and new front ends no longer work with the regional bridges because the signalling is gone. I have current builds of Jicofo, prosody, etc, but I think the configurations must have changed to enable the new signalling? Still trying to sort it out and compare to a new build.
Yep, you need to update all components. That old signalling is gone both from the client and from the backend. That’s the reason versions matching via the meta package as client moves with backend.