Open jmatsushita opened 4 months ago
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 @jbg, what is your plan for Colibri SCTP support ? Do you have identified a rust SCTP stack ?
I also got this error in gst-meet
trying to connect to our self-hosted docker running stable-9753
, still works in stable-8252
.
Hi there,
Just tried to test gst-meet running the master branch at commit 5b1f842920a8a31c211a9bf02acc0c299ebdecc1 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: