- From: <bugzilla@jessica.w3.org>
- Date: Thu, 05 Jun 2014 09:41:32 +0000
- To: public-webrtc@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25975 --- Comment #3 from Kiran <kiran.guduru@samsung.com> --- (In reply to Harald Alvestrand from comment #2) > The canInsertDTMF should change when the codecs available change (the DTMF > codec is added or removed). It will be false before negotiation is > completed, may be true after that, and may change later in response to > negotiation. Agreed. > > I think enabled, disabled and ended are irrelevant; they no more change the > ability to send DTMF than muting the track prevent you from whistling into > the microphone - they just change whether or not the signal you're > generating gets there, and you have existing APIs to check that. This is a bit confusing. According to Media Capture spec, MediaStreamTrack.stop() or any other event that makes a track to stop should detach the source. In case of DTMF, "tones" of insertDTMF is the source for track. So, I felt we should stop inserting DTMF tones into the track that was stopped through tracks stop. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
Received on Thursday, 5 June 2014 09:41:33 UTC