You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just tried to test gst-meet running the master branch at commit 5b1f842 built with cargo build --release on macos with the public meet.jit.si server. It gets "pretty far" into connecting but fails with a fatal: no colibri channel. Here's the end of the log:
Jitsi has recently switched from defaulting to WebSocket for the secondary ("Colibri") signaling channel that goes directly from the client to the JVB, to defaulting to SCTP. Most likely meet.jit.si is offering only SCTP here. We don't yet support that, so it bails out. I'll use this issue to track progress to supporting SCTP for Colibri signalling.
Hi there,
Just tried to test gst-meet running the master branch at commit 5b1f842 built with
cargo build --release
on macos with the public meet.jit.si server. It gets "pretty far" into connecting but fails with afatal: no colibri channel
. Here's the end of the log:The text was updated successfully, but these errors were encountered: