-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xmlns of <parameter> inside <source> is wrong #81
Comments
I think this should resolve it: #82 Jicofo will need updating too: https://github.com/jitsi/jicofo/blob/master/src/main/kotlin/org/jitsi/jicofo/conference/source/Source.kt#L44 |
Good catch! Have you checked if lib-jitsi-meet checks the NS too? |
It doesn't seem to care about the namespace: https://github.com/jitsi/lib-jitsi-meet/blob/e1ca2f5a7b74ca2443f6cb4948f5e53b78aee1c6/modules/sdp/SDP.js#L759 It also produces |
Nice! |
Opened jitsi/jicofo#961 for the Jicofo part. |
What about jigasi? |
I can't find any use of I'll prepare a PR for JVB. This would require JVBs to be updated together though, looks like it's used for relay sources. Maybe it's better to somehow make the parsing side lenient so that |
I'm not sure we need "parameter" in colibri at all. I'm still trying to verify, but don't waste time on a more complex workaround. |
@jbg actually, why do you need to parse these parameters? As far as I can see "parameter" inside "source" is only used for "msid", and they are not really necessary. Currently our client uses them to set the msid of the associated track, but in the new "ssrc rewriting" mode it just picks "remote-video-1", "remote-video-2", etc. I can confirm that the use of "parameter" in colibri2 can be removed, so you don't need to worry about the jvb/jicofo compatibility. |
@bgrozev I don't really need the value of the parameter, but the incorrect namespace causes the whole Jingle stanza to fail to parse, forcing us to use a fork of the XMPP library. |
@jbj, we merged the removal of "parameter" use in colibri2. We can accept your changes if you just update them to not touch colibri (and rebase on top of jitsi/jicofo#997) |
Dear all, Have you progressed on this problem? |
The
<source>
element is defined in XEP-0339 and both it and the contained<parameter>
are defined in the Jingle SSMA namespace (urn:xmpp:jingle:apps:rtp:ssma:0
).However, Jicofo produces a
session-initiate
with<source>
s containing<parameter>
s in the Jingle RTP namespace (urn:xmpp:jingle:apps:rtp:1
) instead:Relevant code is here.
Note that Jingle RTP (XEP-0167) does define a
<parameter>
element too, but despite having the same name it's a different element due to being in a different namespace.This causes interop problems with other software supporting Jingle, notably
xmpp-parsers
whichgst-meet
uses.The text was updated successfully, but these errors were encountered: