Agreeing how to do 1:1 voice and video is very much part of Matrix's spec: it's right here: https://matrix.org/docs/spec/client_server/r0.6.1#module-voip https:

Agreeing how to do 1:1 voice and video is very much part of Matrix's spec: it's right here: https://matrix.org/docs/spec/client_server/r0.6.1#module-voip https://matrix.org/docs/spec/client_server/r0.6.1#module-voi... For multiway calls, we currently embed Jitsi as a Widget - but widgets themselves are also (almost) part of the spec - they're MSC1236 (https://github.com/matrix-org/matrix-doc/issues/1236 https://github.com/matrix-org/matrix-doc/issues/1236). Element may be the only client that implements widgets so far, but we expect that to change once MSC1236 finally gets merged into the spec. Meanwhile, "ability to iframe random content into a chatroom" is a pretty useful thing, and solves the whole video conferencing thing fairly nicely. Finally, in the longer term, we still plan to implement native voice/video conferencing in Matrix as per https://github.com/matrix-org/matrix-doc/blob/matthew/msc2359/proposals/2359-e2ee-voip-conferencing.md https://github.com/matrix-org/matrix-doc/blob/matthew/msc235... - but for now we'd rather focus on polishing the messaging bits of Matrix.