Submitted 2 days ago by guynamedzero@piefed.zeromedia.vip to selfhosted@lemmy.world
Hi there! Recently I’ve been setting up a self-hosted instance of matrix, using Synapse in docker, but I’ve been struggling to get voice chat working, could anyone give me some pointers? It looks like I need something called a TURN server, but I can’t find any good instructions to set this up, or if this is actually what I need to enable voice chat.
Thank you so much to any responses!
I have written a tutorial to set it up. Here you go: ztfr.de/matrixrtc-with-synology-container-manager…
Did you create your own docker container, or ded you use the official one?
I have the official one up and running, and it voice and video chat work out of the box.
I just updated the post with my compose.yaml file in case that’s helpful
I’m using the docker container at ghcr.io/element-hq/synapse, whenever someone tries to call another, it just stays on “connecting” forever
You’ll need a TURN server to relay calls and provide signalling capabilities, which is needed most of the time. Here’s Synapse docs on it, and I’ll probably use coturn:
element-hq.github.io/synapse/…/turn-howto.html
There’s also this new technology called Element Call, which uses a diffent tool called LiveKit. You should check it out too
Look at github.com/coturn/coturn
I'd recommend using https://github.com/spantaleev/matrix-docker-ansible-deploy. It makes managing synapse and related services pretty easy.
You have a higher chance of solving this issue if you ask in #webrtc:matrix.org
JadedBlueEyes@programming.dev 1 day ago
All of the other answers here are wrong - your friend is trying to call you using element call, which needs an instance of a livekit and a JWT micro service to grant permissions to use the livekit instance. You can use a livekit cloud account, but you do need to host the JWT service. I would suggest looking up Element’s documentation
suzune@ani.social 21 hours ago
This is probably the reason. Older element versions has video and telephony via native interfaces and coturn/turnserver for firewall hole poking.
The newer Element X uses a different infrastructure that even allows multi user conferences. You need to update your well-known server response to point it to the new infrastructure: github.com/element-hq/element-call