All of the other answers mentioning coturn 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
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
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: https://github.com/element-hq/element-call
I have written a tutorial to set it up. Here you go: https://ztfr.de/matrixrtc-with-synology-container-manager-docker/
Thanks! I had gotten it working by setting element_call in the .well-known to call.element.io, but I followed this and it works great! Unfortunately, the legacy call is oddly inconsistent, some people can use it, but some can't.
Did you create your own docker container, or did you use the official one?
I have the official one up and running, 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've tried using the docker container at ghcr.io/element-hq/synapse and https://hub.docker.com/r/matrixdotorg/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:
https://element-hq.github.io/synapse/latest/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
https://github.com/element-hq/element-call/blob/livekit/README.md
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