Re: Issue 129: Control of Voice Activity Detection (VAD) from Bernard Aboba on 2014-07-15 (public-ortc@w3.org from July 2014)

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Tue, 15 Jul 2014 20:24:10 +0000
To: "public-ortc@w3.org" <public-ortc@w3.org>
Message-ID: <af9b9dbb92e44ccc9e29b0f624cf2eb1@SN2PR03MB031.namprd03.prod.outlook.com>

In WebRTC 1.0 the voiceActivityDetection attribute determines what is put into the Offer (such as inclusion of CN as defined in RFC 3389). 

In ORTC API, we can control the codecs that are offered (such as CN) and/or the settings of those codecs (e.g. support for comfort noise in G.729) via the RTCRtpParameters passed to send.  

Therefore there is not a need for an explicit voiceActivityDetection attribute within RTCRtpParameters.

Received on Tuesday, 15 July 2014 20:24:40 UTC