I decided to bite the bullet and switch from dendrite to conduit as many of you have suggested. The only problem is I cannot get my calls to connect. It just says “call connecting…” But never does. I figured it was a turn server issue but if I type in the secret key wrong in my config file calls don’t pop up at all. So it is connecting to it to some extent.

I have no idea why dendrite just works with the coturn config setup yet when I apply the exact same methodology with the conduit config file it doesn’t connect calls at all but seems to still connect to the turn server.

For my turn server I am using a debian digital ocean droplet. It was working perfectly for dendrite yet does not want to function with conduit.

Any help is appreciated!

EDIT: I am using a combo of element and element x. On element x android (grapheneos) there is no notification for a call. No pop up or anything. On Element android (grapheneos) there is a popup but the call will not connect.

EDIT 2: I am starting to believe it is coturn. I just don’t know how I am supposed to configure it any different than dendrite. I was starting to believe maybe conduit isn’t reading the config at all. However, it configured the registration key properly. if the secret key is wrong element won’t receive notifications either. I have tried altering my coturn.conf on my vps but to no avail.

EDIT 3: so it seems I can join the call on element x. Even though their is no popup indicating I am recieving a call I can go into the chat and click the call button. Once I do I can connect and talk no problem. Maybe the turn server is working after all. (One phone on mobile the other on my home wifi). I judt don’t know why regular element won’t connect.

EDIT 4: the notification bug in element x seems to be coming from an error with ntfy. I did a notification test in the app and it came up with an error on: “test push gateway” and “test push loop back”

The error for both is:

Http 500

EDIT 5: I think the error has something to do with my conduit server not trusting my ntfy server but I don’t know how to fix that.

EDIT 6: Is Conduit just not compatible with the original element client?

EDIT 7: the original element client gets no errors when troubleshooting notifications. It passes all the checks with flying colors. Element x fails the two checks mentioned above.

  • justme@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 days ago

    Not sure if it helps you, but I think it’s worth looking into. element is using “legacy call” and element x is using the new “element call” which are incompatible. So you can never call from Mobile element to element x. The Web and desktop version supports both afaik. I never tried a HS other than synapse, soi unfortunately can’t help further.