Recommendations, please, for making an #XMPP audio/video call work between:
a user on iOS and a user on Android
a user on iOS and a user on Linux
Messaging works fine, as does a/v between Linux and Android, but I have yet to find a combination which works for audio / video with an iOS device in the mix.
@neil if you self host (or not), #Snikket works quite well, which is based on #Siskin IM on #iOS and #Conversations on #Android. On GNU/Linux, #Dino is working, otherwise #Movim and #Converse should work (web clients). I believe they all work between themselves (for one2one calls).
Be sure to have an XMPP server with STUN/TURN activated (it's precious to cross NAT/Firewalls).
For the record, I'm implementing A/V calls in #Libervia too, thanks to an #NLnet grant.
@neil Interesting I started the same test a long time ago. I did manage to compile Gajim on MacOS but not everything was working fine. I stopped due to not using Apple hardware anymore. But on the todo list for Apple checking was definitly https://siskin.im/ and https://beagle.im/ and on the Android or Amazon Tablet side I used Conversations, beta version of Dino on Linux and I think on windows I had Gajim. Sadly I didn't finish my XMPP cross OS communication test.
@neil@quincy tried beagle from tigase on ios? back when i had ios, i'm fairly i got calls going on it with a conversations user... i no longer have the device tho.
@neil apols, i think i meant to refer to siskin. i possibly even had your situation of one-way calls for a while. stun/turn is a dilly of a pickle. or rather, verifying what it is actually doing is hard.
It's odd - I don't have "one-way audio", just that I cannot call the iOS device from the Android or Linux device. But if the iOS originates the call, the call works just fine (audio and video), with two-way audio.
So it seems to be down to the notification of an incoming call, but notifications of incoming messages work.
You might have to deal with STUN/TURN (the NAT traversal) features in order to get it to work at all, really.
With TLS nowadays it's a bit difficult to look into the protocol, but I think I'd enable the most verbose logging I could and then try to see if there are any local IP addresses in the XML messages by accident (where there should be public IPs instead)
If you actually want to use it:
Install Jitsi Meet instead. It actually works. Well.
Add comment