Post
@dcatoffm Please do not use c0nnect. This is an outdated fork of #Conversations_im with several severe security issues (simply due the fact the developers haven't kept up with fixes I made to Conversations over the years.)
These days Conversations and aTalk are the only actively maintained Android clients that aren't just bad copies of something else.
In terms of calls not working this does depend on your server (and network situation)
Try conversations.im (the server) for example.
@daniel
I did try the conversations.im server (w/ aTalk) about a month ago, it locked me out within a couple hours with no explanation. That's why I went with another server. 🤷♂️
I am absolutely double NAT at the house but that's not where I have an issue.. it doesn't work cell to cell either, it only works WiFi to WiFi.
I suppose I can try the conversations app as well, and see if there's a way to test the stun/turn at CBT (it definitely strikes me as a hobby server). Thank you.
@dcatoffm as others pointed out any server with TURN support will do. conversations.im is just an example of one where I know this to be the case.
@daniel @dcatoffm I agree.
I had serious trouble getting the TURN server included with the OpenFire XMPP server working behind NAT, even though it's direct 1:1 NAT and all relevant ports were open.
Messages and attachments would work. Voice and video calls would dial, but the other end could never be able to pick up.
In the end, I had to set up the TURN plugin on my firewall instead.
Now it works fine :)
I have no idea what server software your host is using I'm afraid.
I have been using @monocles and conversations.im for clients on android.
A space for Bonfire maintainers and contributors to communicate
