matrix-org / matrix-org/matrix-spec
Multi-way VoIP (SPEC-174)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Need to specify a standard profile for multi-way VoIP/Video calls.
Options include:
- Signalling for all calls is mixed into the same room (useful for multicast traffic)
- Signalling between calls and conference server is in side-channel 1:1 rooms
- We use EDUs of some kind for non-stateful conference signalling
Do we do SFU, MCU, full mesh, multicast, or some combination?
Do we hook into Jitsi or Kurento or Janus or FreeSWITCH or what?
(Imported from https://matrix.org/jira/browse/SPEC-174)
(Reported by @ara4n)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue's listed alternatives for signalling, conference topology, and integration with Jitsi, Kurento, Janus, or FreeSWITCH. Done would require agreement on a standard multi-way VoIP/video profile and documenting that decision in the Matrix specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100