Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2025-12-28 03:48:36 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Fix hangup reasons

Browse source
This commit is contained in:
David Baker 2023-05-17 10:05:25 +01:00
parent 5b8e3ef92a
commit 1023399997
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
data/event-schemas/schema/m.call.hangup.yaml
View file

@ -5,10 +5,11 @@ description: |
be sent either once the call has has been established or before to abort the call.
The meanings of the `reason` field are as follows:
* `ice_timeout`: The connection failed after some media was exchanged (as opposed to current
* `ice_failed` which means no media connection could be established). Note that, in the case of
an ICE renegotiation, a client should be sure to send `ice_timeout` rather than `ice_failed` if
media had previously been received successfully, even if the ICE renegotiation itself failed.
* `ice_failed`: ICE negotiation has failed and a media connection could not be established.
* `ice_timeout`: The connection failed after some media was exchanged (as opposed to `ice_failed`
which means no media connection could be established). Note that, in the case of an ICE
renegotiation, a client should be sure to send `ice_timeout` rather than `ice_failed` if media
had previously been received successfully, even if the ICE renegotiation itself failed.
* `invite_timeout`: The other party did not answer in time.
* `user_hangup`: Clients must now send this code when the user chooses to end the call, although
for backwards compatibility with version 0, a clients should treat an absence of the `reason`