

Misconfiguration with SMTP is likely or their SMTP server is under maintenance and you just tried at a poor time.
Granted for a production environment there should be some notice to users.


Misconfiguration with SMTP is likely or their SMTP server is under maintenance and you just tried at a poor time.
Granted for a production environment there should be some notice to users.


Setting up Element Call on my instance was difficult on its own, I understand why Synapse doesn’t come with it out of the box, essentially you spin up Matrix’s JWT service for authenticating clients and it if approved forwards the connection to the Livekit ports which must be opened on your firewall (ie port forwarded), otherwise people will not be able to connect to calls.
Big PITA and in my experience, on my home network, can conflict with games with VOIP chats so don’t follow the default 50000:55000 port range Livekit recommends or you’ll run into issues like I did, each person consumes 2 ports so adjust the range to your need.
Edit: I don’t suggest running Element Call standalone, it has issues of its own, once you get Livekit and JWT running and follow This guide you should have your element call support in Synapse now, pro-tip for those running synapse behind docker and get confused on the whole ./well-known part of the documentation you can edit your ./well-known in your homeserver.yaml file like such:
serve_server_wellknown: true
extra_well_known_client_content:
optional: client
"org.matrix.msc4143.rtc_foci": [
{
"type": "livekit",
"livekit_service_url": "https://livekit-jwt.your.domain/"
}
]


Element and Element Call, although no streaming audio support on the horizon anytime soon.
I just abruptly switched to Matrix and encouraged anyone who wanted to get a hold of me to do the same, held my ground and did not look back, now a good handful of my friends have a Matrix account.