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 25576 - steps for createDTMFSender() are missing.
Summary: steps for createDTMFSender() are missing.
Status: RESOLVED WONTFIX
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: All All
: P2 major
Target Milestone: ---
Assignee: Adam Bergkvist
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-06 11:24 UTC by Kiran
Modified: 2014-11-05 08:52 UTC (History)
2 users (show)

See Also:

Attachments

Description Kiran 2014-05-06 11:24:36 UTC 
In WebRTC spec [1], steps to specify the creation of DTMFsender are missing, while explaining the createDTMFSender.

Adding the following steps may fix this.

1. If the RTCPeerConnection object’s RTCPeerConnection signalingState is closed, throw an InvalidStateError exception and abort these steps.

2. Let sender be a newly created RTCDTMFSender object.

3. set senders track attribute to the received track.

4. set the senders canInsertDTMF attribute to true.

5. If the MediaStreamTrack.readyState is new, set the MediaStreamTrack.readyState to started.

6. Return the newly created sender.

7. In case of any error while creating the sender, return NULL and abort the steps following it.


[1] http://dev.w3.org/2011/webrtc/editor/webrtc.html#dfn-createdtmfsender
Comment 1 Kiran 2014-06-09 12:51:21 UTC 
It seems good to add the following step also to make sure that the track attribute referred by DTMFSender is of audio.

2. If the received track is not of kind 'audio' throw TYPE-MISMATCH error and abort these steps.
Comment 2 Harald Alvestrand 2014-10-31 14:16:15 UTC 
Assigning for editing.

Editors have discretion on how detailed to make the procedure.
Comment 3 Adam Bergkvist 2014-11-05 08:52:09 UTC 
closing as WONTFIX since createDTMFSender() will be removed.