Closed daimoc closed 5 months ago
Yes, it seems to come from here: https://docs.rs/xmpp-parsers/latest/src/xmpp_parsers/muc/user.rs.html#107
xmpp-parsers validates that exactly one of jid
or nick
is set on the actor
element. Since Jicofo is setting both, the error occurs.
xmpp-parsers seems to deviate from the spec here, which allows both to be set (https://xmpp.org/extensions/xep-0045.html#schemas-user), meaning it probably should not have been modelled as an enum.
Filed an issue upstream: https://gitlab.com/xmpp-rs/xmpp-rs/-/issues/88
I've implemented a workaround in https://github.com/avstack/gst-meet/commit/a42e069d282db43fc8ed088db79be1b3ec6a3557
If you can confirm that current master works for you, I'll make a release with the workaround.
I'll keep this issue open until it's fixed upstream and I can remove the workaround.
Hi @jbg, Your workaround works fine. I don't know if xmpp-rs will be fixed or if someone must ask prosody to change its implementation (see the Jitsi Forum post). But now Gst-Meet works with my JItsi-Meet environment, so thank you.
Hi, I made some test with the last gst-meet version and a Jitsi-Meet instance with JWT auth token enabled. I can connect the gst-meet user on a running meeting if I add a valid JWT token on the wss url and it works well.
But if a new moderator joins the room, gst-meet failed to parse the presence message, and it leaves the room with this error :
Here is the XMPP message that generate the error :
After digging the gst-meet code, I think the error "parse error: Either 'jid' or 'nick' attribute is required." came from the rust xmp-parser library on the actor element but I'm not sure.
Does anyone has already see this error with Gst-Meet ?