Skip to content

MSC4196: MatrixRTC voice and video calling application m.call#4196

Draft
hughns wants to merge 7 commits into
mainfrom
hughns/matrixrtc-m-call
Draft

MSC4196: MatrixRTC voice and video calling application m.call#4196
hughns wants to merge 7 commits into
mainfrom
hughns/matrixrtc-m-call

Conversation

@hughns

@hughns hughns commented Sep 19, 2024

Copy link
Copy Markdown
Member

Rendered

To-do:

  • how do you distinguish between voice and video calls?
  • implementation using the new field structures

Dependencies:

@hughns hughns changed the title Create xxxx-matrixrtc-m-call.md MSC4196: MatrixRTC voice and video conferencing application m.call Sep 19, 2024
@turt2live turt2live added A-VOIP proposal A matrix spec change proposal. Process state. A-Client Server Client-Server API kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Sep 25, 2024
@ara4n ara4n added the matrix-2.0 Required for Matrix 2.0 (note: do not rename - used in reports/links) label Sep 5, 2025
@github-project-automation github-project-automation Bot moved this to Tracking for review in Spec Core Team Workflow Sep 5, 2025
@fkwp fkwp changed the title MSC4196: MatrixRTC voice and video conferencing application m.call MSC4196: MatrixRTC voice and video calling application m.call Jan 12, 2026
@@ -0,0 +1,195 @@
# MSC4196: MatrixRTC voice and video calling application `m.call`

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could use a short introduction and especially an early backlink to #4143 as the foundation for this proposal.

Comment thread proposals/4196-matrixrtc-m-call.md Outdated
| :---- | :---- | ----- | :---- |
| `type` | string | ✅ | Must be `"m.call"`. Identifies the application type. |
| `m.call.id` | string | ⚪ | Optional call ID of the session. Serves as a unique identifier for the call instance. |
| `m.call.intent` | string | ⚪ | Optional hint expressing the intended use-case of the session, e.g., `"voice"`, `"video"`, or `"spatial-audio"`. This field is **informational only** and non-authoritative, reflecting the participant's perception of the session. |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if this should be an array rather than a single string. Could we possibly foresee any intents that could be combined? Like a video call but you want people to join muted maybe?

"type": "m.call",
// additional fields for m.call:
"m.call.id": UUID
"scope": "m.room"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This field seems undefined here and in #4143. Could it be that this is a leftover from an earlier design?

Suggested change
"scope": "m.room"

@Johennes Johennes mentioned this pull request May 27, 2026
9 tasks
Comment thread proposals/4196-matrixrtc-m-call.md Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Client Server Client-Server API A-VOIP kind:core MSC which is critical to the protocol's success matrix-2.0 Required for Matrix 2.0 (note: do not rename - used in reports/links) needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal. Process state.

Projects

Status: Tracking for review

Development

Successfully merging this pull request may close these issues.

5 participants