* `m.intent` to describe the intended UX for handling the call. One of:
1. `m.ring` if the call is meant to cause the room participants devices to ring (e.g. 1:1 call or group call)
2. `m.prompt` is the call should be presented as a conference call which users in the room are prompted to connect to
3. `m.room` if the call should be presented as a voice/video channel in which the user is immediately immersed on selecting the room.
Element Call implements `m.room` effectively (in that you get slung directly into the call once you click on the link). Once we integrate this into Element itself, then the plan is to support all three different intent types: `m.ring` for "group calls", `m.prompt` for "conferences" and `m.room` for discord-style voice/video rooms.
I assume m.ring would not be needed if its a something like a Teamspeak room.
(N.B. we might not bother with the group-calling option in Element; haven't decided yet - but Matrix needs to support it for folks who want those semantics :)
So m.ring existing isn't a problem.
How it is exposed in the UI, is a completely different thing, although I don't think it would be impossible to make a button that creates a room with a m.room call aka voice/video room