mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-01-08 08:53:43 +01:00
4fd9f39966
* Change version field to a string And add the notes on how the version field works. * Add spec requiring tracks to be within streams. * Put streams spec in its own section * Add 'invitee' field * Add party_id * Remember how JSON works * Add m.call.select_answer * Update examples * Add select_answer to call flow example diagram * Add m.call.reject * Make party_id required in other events * Add possible ways for client to handle an invite * Convert hangup & reject events to YAML So we can have a bulleted list in the description for the values of 'reason'. * Add new reason codes to hangup & reject * Add m.call.negotiate * Add other sections * Revert changes to package lock * Typos * Fix type of other version fields, fix anchor. * Add newsfragment * Fix reason in hangup/reject * Change tense Co-authored-by: Hubert Chathi <hubertc@matrix.org> * Tense, typos & grammar Co-authored-by: Hubert Chathi <hubertc@matrix.org> * Linkify Co-authored-by: Hubert Chathi <hubertc@matrix.org> * Remove unnecessary parts from link Co-authored-by: Hubert Chathi <hubertc@matrix.org> * Capitalise Co-authored-by: Hubert Chathi <hubertc@matrix.org> * Fix hangup reasons * Clarify who can answer Co-authored-by: Hubert Chathi <hubertc@matrix.org> * Linkify Co-authored-by: Hubert Chathi <hubertc@matrix.org> * Remove reference to 'this MSC'. * Move common VoIP fields into a call event type. * Move common voip events to the content, not the actual event * Remove reason from reject event I confused myself, but it's not in the MSC and it shouldn't be. * Failure to YAML * Fix number of room members allowed when sending voip events. Co-authored-by: Hubert Chathi <hubertc@matrix.org> * Add 'added in' version Co-authored-by: Hubert Chathi <hubertc@matrix.org> * Another added-in Co-authored-by: Hubert Chathi <hubertc@matrix.org> * Add missing comma --------- Co-authored-by: Hubert Chathi <hubertc@matrix.org> Co-authored-by: Travis Ralston <travisr@matrix.org>
29 lines
1.1 KiB
YAML
29 lines
1.1 KiB
YAML
---
|
|
type: object
|
|
description: |
|
|
If the `m.call.invite` event has `version` `"1"`, a client wishing to
|
|
reject the call sends an `m.call.reject` event. This rejects the call on all devices,
|
|
but if the calling device sees an `answer` before the `reject`, it disregards the
|
|
reject event and carries on. The reject has a `party_id` just like an answer, and
|
|
the caller sends a `select_answer` for it just like an answer. If another client
|
|
had already sent an answer and sees the caller select the reject response instead
|
|
of its answer, it ends the call. If the `m.call.invite` event has `version` `0`,
|
|
the callee sends an `m.call.hangup` event. If the calling user chooses to end the
|
|
call before setup is complete, the client sends `m.call.hangup` as previously.
|
|
|
|
Note that, unlike `m.call.hangup`, this event has no `reason` field: the rejection of
|
|
a call is always implicitly because the user chose not to answer it.
|
|
x-addedInMatrixVersion: "1.7"
|
|
allOf:
|
|
- "$ref": core-event-schema/room_event.yaml
|
|
properties:
|
|
content:
|
|
type: object
|
|
allOf:
|
|
- "$ref": core-event-schema/call_event.yaml
|
|
type:
|
|
type: string
|
|
enum:
|
|
- m.call.reject
|
|
|