From ef15055e0aabf3481057811b514ad7f6582b8600 Mon Sep 17 00:00:00 2001 From: David Baker Date: Tue, 2 May 2023 16:59:31 +0100 Subject: [PATCH] Add spec requiring tracks to be within streams. --- content/client-server-api/modules/voip_events.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/content/client-server-api/modules/voip_events.md b/content/client-server-api/modules/voip_events.md index 01f21825..de49c722 100644 --- a/content/client-server-api/modules/voip_events.md +++ b/content/client-server-api/modules/voip_events.md @@ -54,6 +54,19 @@ Or a rejected call: Calls are negotiated according to the WebRTC specification. +Clients are expected to send one stream with one track of kind `audio` (creating a +voice call). They can optionally send a second track in the same stream of kind +`video` (creating a video call). + +Clients implementing this specification use the first stream and 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. + +A client may send other streams and tracks but the behaviour of the other party +with respect to presenting such streams and tracks is undefined. + ##### Glare "Glare" is a problem which occurs when two users call each other at