Native Matrix VoIP with Element Call
element.io
Native Matrix VoIP with Element Call
1–10 of 130 posts
Re: Native Matrix VoIP with Element Call
#2this does not seem to have changeable room addresses right now like jitsi.
we use jitsi common url to have weekly meetings. meet.jit.si/meeting2. everyone knows the url and time. we just join and talk. this is a nice concept
Re: Native Matrix VoIP with Element Call
#3this does not seem to have changeable room addresses right now like jitsi. we use jitsi common url to have weekly meetings. meet.jit.si/meeting2. everyone knows the url and time. we just join and talk. this is a nice concept
I think it does in theory (Matrix supports changing room addresses), however what is the benefit of this as opposed to using the same address for all meetings?
Re: Native Matrix VoIP with Element Call
#4this does not seem to have changeable room addresses right now like jitsi. we use jitsi common url to have weekly meetings. meet.jit.si/meeting2. everyone knows the url and time. we just join and talk. this is a nice concept
I think it does in theory (Matrix supports changing room addresses), however what is the benefit of this as opposed to using the same address for all meetings?
The person you're replying to wants to set it to something custom, to make it memorable and meaningful.
Re: Native Matrix VoIP with Element Call
#5this does not seem to have changeable room addresses right now like jitsi. we use jitsi common url to have weekly meetings. meet.jit.si/meeting2. everyone knows the url and time. we just join and talk. this is a nice concept
I think it does in theory (Matrix supports changing room addresses), however what is the benefit of this as opposed to using the same address for all meetings?
I think that's what they want, I believe by "changeable" they meant "customizable"?
Re: Native Matrix VoIP with Element Call
#6Do the Homeservers act as Signaling, STUN and TURN servers or are there additional components necessary? Will the SFU part in the future also be part of Synapse or will/are these things split?
Re: Native Matrix VoIP with Element Call
#7> Element Call is built entirely on Matrix: it doesn’t need any additional servers to get going. You can run it against your existing Matrix homeserver to provide complete self-sovereignty…
> In the near future, we will support using the app with any homeserver
I really hope this isn't an indicator how how Element the company will be focusing more on their paid offerings to the exclusion of supporting private homeservers. I've recently been experimenting with running a Matrix homeserver on a Raspberry PI in my basement--I'm excited about actual self-sovereignty in messaging but it isn't quite to the point where I can tell my family to rely on it instead.
Re: Native Matrix VoIP with Element Call
#8> And, the big one drum roll, please... we will be integrating this into Element so you can have voice and video rooms, and hold group video calls inside the Element app natively over Matrix.
I'd love to replace my teamspeak server with this. Discord is tempting, but I'd rather host it myself.
Re: Native Matrix VoIP with Element Call
#9this does not seem to have changeable room addresses right now like jitsi. we use jitsi common url to have weekly meetings. meet.jit.si/meeting2. everyone knows the url and time. we just join and talk. this is a nice concept
That seems to be available, though?
https://call.element.io/meetingwiththegang opens a meeting for a room named "meetingwiththegang".
Ideally, you'd want to use such a system with accounts so you can apply some kind of ACL, but if you want to use randomly generated room names for secret links then everything you need is there already.
Looks like you can't change the room name after starting the call, but you can start a new one at the new address if you want to change the name.
Re: Native Matrix VoIP with Element Call
#10Do the Homeservers act as Signaling, STUN and TURN servers or are there additional components necessary? Will the SFU part in the future also be part of Synapse or will/are these things split?
As I understand it, signalling will happen over the matrix protocol. as matrix/element already had a 1:1 voice chat, synapse integrates well with coturn, so you typically run coturn along side synapse.