This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27213 - DTMFSender should hang off RTCRTPSender, not MediaStreamTrack
Summary: DTMFSender should hang off RTCRTPSender, not MediaStreamTrack
Status: RESOLVED LATER
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Peter Thatcher
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 25497
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-31 18:13 UTC by Harald Alvestrand
Modified: 2014-12-15 10:39 UTC (History)
1 user (show)

See Also:


Attachments

Description Harald Alvestrand 2014-10-31 18:13:10 UTC
Now that RTCRTPSender is available, the abstractions layer better this way.
Comment 1 Harald Alvestrand 2014-11-04 18:16:51 UTC
From Peter Thatcher:

At TPAC 2014, we realized that now that we have RtpSender, we don't need a DTMFSender to be tied to a track.  We can tie it to an RtpSender instead, and that would clean things up a fair bit.

Based on that, I propose we: 

1. Remove RTCPeerConnection.createDTMFSender
2. Add RTCRtpSender.dtmf, of type "RTCDTMFSender?".
3. Remove RTCDTMFSender.canInsertDTMF and RTCDTMFSender.track.
  
The rule is: If RtpSender.dtmf is non-null, you can send DTMF.  Here is an example:

var pc = ...;
var track = ...;
var rtpSender = pc.addTrack(track);
if (rtpSender.dtmf) {
  rtpSender.dtmf.insertDTMF(...);
}
Comment 2 Dominique Hazael-Massieux 2014-12-15 10:39:45 UTC
WebRTC API bugs have been moved to github issues: https://github.com/w3c/webrtc-pc/issues

Please subscribe to the issues you want to keep watching.