MSC4075: MatrixRTC m.rtc.notification Call Ringing and Notifications
#4075
+227
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Timo K <[email protected]>
Signed-off-by: Timo K <[email protected]>
Signed-off-by: Timo K <[email protected]>
turt2live
reviewed
Nov 8, 2023
turt2live
added
voip
proposal
Signed-off-by: Timo K <[email protected]>
Signed-off-by: Timo K <[email protected]>
3 tasks
toger5
added a commit
to toger5/ruma
that referenced
this pull request
Nov 22, 2023
See: [MSC4075]( matrix-org/matrix-spec-proposals#4075) Signed-off-by: Timo K <[email protected]>
toger5
added a commit
to toger5/ruma
that referenced
this pull request
Nov 22, 2023
See: [MSC4075]( matrix-org/matrix-spec-proposals#4075) Signed-off-by: Timo K <[email protected]>
toger5
added a commit
to toger5/ruma
that referenced
this pull request
Nov 24, 2023
See: [MSC4075]( matrix-org/matrix-spec-proposals#4075) Signed-off-by: Timo K <[email protected]>
toger5
added a commit
to toger5/ruma
that referenced
this pull request
Nov 24, 2023
See: [MSC4075]( matrix-org/matrix-spec-proposals#4075) Signed-off-by: Timo K <[email protected]>
toger5
added a commit
to toger5/ruma
that referenced
this pull request
Nov 24, 2023
See: [MSC4075]( matrix-org/matrix-spec-proposals#4075) Signed-off-by: Timo K <[email protected]>
toger5
added a commit
to toger5/ruma
that referenced
this pull request
Nov 24, 2023
See: [MSC4075]( matrix-org/matrix-spec-proposals#4075) Signed-off-by: Timo K <[email protected]>
jplatte
pushed a commit
to ruma/ruma
that referenced
this pull request
Nov 27, 2023
jplatte
pushed a commit
to ruma/ruma
that referenced
this pull request
Nov 27, 2023
Member
|
@toger5 You've added some implementations in the PR description. Do these implement the MSC in full, or are there parts of the MSC that are still lacking implementation? |
Author
|
Yes it's implemented in full. At least on the platforms shown in the description (EW). There are optional configurations that are still missing. (Allowing to send a notification to a specific subset of users) but the API for this is already part of the SDK. There is no ui for this however and we are not sure we want that in EW. |
TobiasFella
reviewed
Feb 18, 2024
Signed-off-by: Timo K <[email protected]>
giomfo
reviewed
Apr 12, 2024
giomfo
reviewed
Apr 12, 2024
td-famedly
reviewed
May 12, 2024
4 tasks
2 tasks
toger5
force-pushed
the
toger5/matrixrtc-call-ringing
branch
from
cdc49b8 to
6362c23
Compare
toger5
changed the title
m.rtc.noticiation Call Ringing and Notifications
toger5
changed the title
m.rtc.noticiation Call Ringing and Notificationsm.rtc.notification Call Ringing and Notifications
- dont use custom rel_type - numerous spelling gramar issues and various more explicit explanations. Signed-off-by: Timo K <[email protected]>
github-project-automation
bot
moved this to Tracking for review
in Spec Core Team Workflow
9 tasks
Half-Shot
reviewed
Sep 16, 2025
| "lifetime": 30000, | ||
| "m.mentions": {"user_ids": [], "room": true | false}, | ||
| "m.relates_to": {"rel_type":"m.reference", "event_id":"$rtc_member_event_id"}, | ||
| "notification_type": "ring | notification", |
Contributor
There was a problem hiding this comment.
Noting that I'm playing around with the idea of including a media_hint field that gives a soft indication of whether the call is a "audio" or "video" (+audio) call. This is just to indicate between trusted callers that they can start with audio or video off, but the actual call semantics remain the same and they may switch at will. The intention is so that we can indicate this properly in notifications.
Suggested change
| "notification_type": "ring | notification", | |
| "notification_type": "ring | notification", | |
| "media_hint": "audio | video", |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rendered
To-do:
04635eb(#4075)m.rtc.notificationevent (depreceatem.call.notify) ruma/ruma#21997c996bb(#4075)m.rtc.notificationevent (depreceatem.call.notify) ruma/ruma#21996362c23(#4075)m.rtc.notificationevent (depreceatem.call.notify) ruma/ruma#2199lifetimeconcept makes sense. It allows the sending client to know/control when the receiver stops ringing. Additional precautions need to take place to not allow for infinite rings. This is part of6362c23(#MSC4075)Dependencies:
Implementations: