Calls Support (MSC3401)

[fkwp]

This is an epic issue. List of individual issues is below:

Highlevel overview

Epic for getting MSC3401 (aka Element Call) support. This Epic covers mostly user facing "application" features.

Linked Tickets

Beta Give feedback

1. Calls: prevent olm from OOM'ing vector-im/hydrogen-web#967
   +0
2. Calls: clarify localmedia ownership vector-im/hydrogen-web#968
   +0
3. Calls: handle an peercall failing in a group call vector-im/hydrogen-web#969
   +0
4. Calls: cleanup vector-im/hydrogen-web#970
   +0
5. Calls: handle to_device vs call event race vector-im/hydrogen-web#971
   +0
   
6. Calls: better error handling vector-im/hydrogen-web#972
   +0
   
7. Calls: test between Hydrogen and Element Call, make them compatible vector-im/hydrogen-web#973
   +0
   
8. Calls: hangup on call from service worker if needed vector-im/hydrogen-web#894
   +0
9. Calls: ringing & notifying vector-im/hydrogen-web#895
   +0
10. Calls: device selection vector-im/hydrogen-web#896
    +0
11. Calls: detect active speaker vector-im/hydrogen-web#897
    +0
12. Calls: screensharing vector-im/hydrogen-web#898
    +0
13. Calls: left panel UI vector-im/hydrogen-web#900
    +0

Linked Pull Requests

[Thatoo]

• Video Room (native call)

[toger5]

I think it makes sense to close this epic since it describes a path to full mesh calling and not the MatrixRTC approach.
It might make more sense to create a new epic adapted to the MatrixRTC msc's.

In its current state it might communicate that the plan for hydrogen is to add MSC3401 support to hydrogen which makes no sense to do before Livekit backed MatrixRTC.

@fkwp Feel free to open it again if you disagree or if there is a better approach.