I think you can refer to to this documentation. By default it’s 8448 but it can be different if this port is already used.
So about element call you should have all doc here. So by default the old system with coturn and the new one with livekit is configured. Event if you don’t really need any more coturn I would not recommend to remove it as the package is still managing it. For now I don’t plan to remove it because it probably still used by users. Maybe if there are a lot of request we can maybe provide a possibility to disable it.
Is the yuno_synapse supporting Element X now? The element classic app on iOS is starting to finally feel inferior to the Element X version not to mention the bug speed diffs from sliding sync.
Hrm, I’m getting an error when trying to connect. Is there something I need to enable?
Error: We couldn’t reach this homeserver. Please check that you have entered the homeserver URL correctly. If the URL is correct, contact your homeserver administrator for further help.
Dear @Josue ,
I have changed Internet access provider, and I try to set up correctly port forwarding, that’s why my previous questions.
So my public IP address has changed also.
Messages through Matrix works well again.
But I tested again Element X calls and it doesn’t work anymore. Call ring on the other phone, I can answer, but the media can not be shared and the call end before I can talk (“unexpected error occurred (Error Code: Unkwown_Error)”). The same from within the same network, or connected to external IP (through 4G).
I have updated coturn IP address in /etc/matrix-synapse/coturn.conf but I understood it is useless for Element Call, no?
Is there anything else I should update to make it work in my new setting?
What I would recommend if it don’t work as expected is:
Ensure that the port are correctly open. You can use netcat or a tool like this to ensure that the service is available for the TCP ports at last.
Also doing a test with element web from a browser is quite easier to debug because you can open the browser console to see the log and also you can open the network tab to see the different communication and if something fail.
I never got a reply about why I can’t connect to my server using element x but it turns out that it’s because the iOS client doesn’t support TLS 1.3 yet something about the rust library not supporting it yet. It does sound like it’s coming soon. Just thought I’d share for any others having the same problem.
