-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Support for revision 0.7 of XEP-0215 #5786
Comments
Actually we use a slightly modified version of the module that supports multiple turn hosts as response. |
@damencho: Yes it is important to have the up-to-date module with your changes. |
Any news on this? ejabberd 20.04 with support was released already: https://www.process-one.net/blog/ejabberd-20-04/ And more servers are getting STUN/TURN support day by day: https://compliance.conversations.im/test/turn/ But at least 42% of them (https://nitter.net/iNPUTmice/status/1257543944486785030) can't enable the use of TURN for Jitsi Meet since this is a Prosody (custom module) only thing :( |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Always here. |
Seems this has been implemented, many thanks! |
Jitsi Meet (optionally) uses XEP-0215 to discover STUN/TURN services. Version 0.7 of the XEP bumped the namespace to
urn:xmpp:extdisco:2
in 2015, it would be nice if Jitsi Meet could use that instead ofextdisco:1
. Presumably, you could just useextdisco:2
in place ofextdisco:1
and ignore the new attributes returned by the server.Prosody's
mod_turncredentials
supports the new namespace for some months now; and I'm currently adding XEP-0215 support to ejabberd and would be happy not having to support the old one 😄The text was updated successfully, but these errors were encountered: