It boils down Jitsi trying to iterate over a list of audio output devices, which in Firefox. With this configuration 2 clients will try to get P2P, if P2P is not possible TURN Server will be used. Additional notes: - This issue does not occur on Chrome. I will keep my configuration: useStunTurn: true, Okay now I understand it, thank you for explanation. Īny ideas why Jitsi only show some gray screen? All containers up and running. After I commented out the line back to original everything is working fine. I have tested iceTransportPolicy: relay after restart all containers the Jitsi Webpage will only show a gray screen, the same with iceTransportPolicy: all. When a 3rd participant joins all participants seamlessly move to the JVB connection. If there are 2 participants we’ll try to establish the P2P connection and fall back to the JVB one if the former fails. I don’t understand why you’d want this, unless you are in some hostile networking environment which requires it. IceTransportPolicy: relay means only TURN servers will be used as ICE candidates for the P2P connection. IceTransportPolicy: all means we’ll try all ICE candidates when establishing the P2P call (note this option goes inside the p2p config block). There are no ENV settings for STUN and useStunTurn: true In my docker-compose.yml I must configure a volume like this to set this settings persistent, because at every container reboot default config.js will overwrite my changes. To route the audio signal directly into Jitsi you need. Peer-To-Peer mode: used (if enabled) when there are just 2 participants. Sound: If you just play the video now, the sound will naturally come from your speakers (or headphones). My config.js is like this here: useStunTurn: true, I would like to configure that all P2P calls go to my TURN Server no P2P! I have a call with 2 participants but traffic goes over the JVB Bridge Port 10000. But P2p calls not go through my TURN Server.
0 kommentar(er)
