Recent searches
Search options
@raucao@kosmos.socialAnyone here has enough experience with #xmpp audio/video call connections via STUN/TURN from @ejabberd and would be willing to help solve our issues with it for a fair price?
Basically, we have calls failing to connect all the time, but the error messages are either non-existent or maximally unhelpful. I have a hunch that the session tokens are expiring and not automatically renewed on demand. But I'm pretty much stuck, unable to debug it further.
If you can find the problem, we would document it publicly, so that other server operators running into the same issues may be able to find the solution themselves.
If we want people to use #xmpp messengers instead of WhatsApp and Signal, then I think we should all try to improve the situation of audio and video calls across the ecosystem, because for better or worse, they're just table stakes for messaging apps in 2024.
Do you run your own stun/turn ?
@jazzilla Yes. At first we used the built-in ejabberd one, now we're using coturn. Had the same issue with both.
Is it with calls only between people on the same XMPP server, or is it with calls to users on other servers? To my understanding, each server (for each participant in a call) needs to provide STUN/TURN services.
@arcanicanis Happens regularly between people on the same server.
Are all the ports for STUN/TURN open, including the entire ranges for TURN relay (ALL ports from UDP port 49152, to UDP port 65535, as is the default for eturnal and coturn), or if you're using a custom port range, is it enough ports (e.g. at least like ~100 ports or so)?
@raucao @ejabberd I'd suggest asking in ejabberd's or eturnal's XMPP channel(s), as it's probably quicker to track down the details by chat:
xmpp:ejabberd@conference.process-one.net?join
xmpp:eturnal@conference.process-one.net?join