Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-23 19:44:09 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Rework paragraph about streamless tracks and move to the end

Browse source 
Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
This commit is contained in:
Kévin Commaille 2024-03-13 10:32:28 +01:00
parent d6d3c50729
commit 671685e330
No known key found for this signature in database
GPG key ID: 29A48C1F03620416
1 changed files with 2 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
content/client-server-api/modules/voip_events.md
View file

@ -189,17 +189,14 @@ If an incoming stream is not described in `sdp_stream_metadata` and
a `purpose` of an unknown type (i.e. not `m.usermedia` or `m.screenshare`), it
should be ignored.
Clients implementing this specification will ignore any streamless tracks. Note
that in the JavaScript WebRTC API, this means `addTrack()` must be passed two
parameters: a track and a stream, not just a track, and in a video call the
stream must be the same for both audio and video track.
For backwards compatibility, if `sdp_stream_metadata` is not present in the
initial [`m.call.invite`](/client-server-api/#mcallinvite) or [`m.call.answer`](/client-server-api/#mcallanswer)
event sent by the other party, the client should ignore any new incoming streams
(i.e. it should use the first one) and it shouldn't send more than one stream
(i.e. clients cannot send a video feed and a screenshare at the same time).
Clients implementing this specification should ignore any streamless tracks.
##### Invitees
The `invitee` field should be added whenever the call is intended for one
specific user, and should be set to the Matrix user ID of that user. Invites