Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Intent to implement and ship: RTCDTMFSender

25 views
Skip to first unread message

Daniel Minor

unread,
Aug 26, 2016, 8:13:09 AM8/26/16
to dev-platform
Summary:

DTMF allows for WebRTC to interact with traditional telephone networks by
generating phone keypad tones over an audio channel. It will be implemented
as an additional interface on the RTPRtcSender object associated with a
peer connection. DTMF is currently supported in Chrome, although it appears
they are still on an older version of the standard where you call a
createDTMFSender() function on the peer connection to create an instance
rather than accessing it through the RTPRtcSender object.

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1012645

Link to standard: https://www.w3.org/TR/webrtc/#peer-to-peer-dtmf

Platform coverage: all platforms.

Estimated or target release: 51

Preference behind which this will be implemented: media.peerconnection.dtmf.
enabled

DevTools bug: Not needed.

Anne van Kesteren

unread,
Aug 26, 2016, 8:30:57 AM8/26/16
to Daniel Minor, dev-platform
On Fri, Aug 26, 2016 at 2:12 PM, Daniel Minor <dmi...@mozilla.com> wrote:
> Link to standard: https://www.w3.org/TR/webrtc/#peer-to-peer-dtmf

I ended up filing some GitHub issues. The IDL there is somewhat wrong
(at least if this is indeed an event target as the standard makes it
out to be) and I noted a couple of other things too in passing.

Do you know when Chrome plans to align with the standard and remove
their older version?


--
https://annevankesteren.nl/

Boris Zbarsky

unread,
Aug 26, 2016, 9:52:13 AM8/26/16
to
On 8/26/16 8:30 AM, Anne van Kesteren wrote:
> I ended up filing some GitHub issues.

Thank you. I was about to file some of those too...

I filed a few more. Mostly editorial, but
https://github.com/w3c/webrtc-pc/issues/775 is substantive.

David, do you know whether Edge is generally planning to implement this
too as they implement the WebRTC API? What about Safari?

-Boris

Randell Jesup

unread,
Aug 26, 2016, 10:11:43 AM8/26/16
to
>On 8/26/16 8:30 AM, Anne van Kesteren wrote:
>I filed a few more. Mostly editorial, but
>https://github.com/w3c/webrtc-pc/issues/775 is substantive.

Thanks. We'll get that dealt with.

>David, do you know whether Edge is generally planning to implement this too
>as they implement the WebRTC API? What about Safari?

Edge is generally onboard with the DMTF API from what I know, though I
haven't discussed specifics with them. We did talk about it a little at
Cluecon (Freeswitch conference) two weeks ago, in a panel discussion.
MS guys were in remotely using Edge, connecting via webrtc to a
Freeswitch conference (which uses adapter.js). (Video in Edge (H264
only so far) requires flipping a flag in about:flags in the anniversary
release of win10.) We had someone in via Safari (using a plugin for
webrtc) as well.

Freeswitch developers are very interested in DTMF support since they're
generally PBX/IP-phones and SIP trunking/etc people.

Apple of course never says anything, but they're clearly working on
WebRTC support.

--
Randell Jesup, Mozilla Corp
remove "news" for personal email

Randell Jesup

unread,
Aug 26, 2016, 10:26:05 AM8/26/16
to
>>David, do you know whether Edge is generally planning to implement this too
>>as they implement the WebRTC API? What about Safari?
>
>Edge is generally onboard with the DMTF API from what I know, though I
>haven't discussed specifics with them. We did talk about it a little at
>Cluecon (Freeswitch conference) two weeks ago, in a panel discussion.

Also, the MS guys indicated they will be launching Skype over WebRTC (in
alpha now), and Skype For Business (aka formerly Lync) via WebRTC soon.
Skype and especially Skype For Business need DTMF support, and they
would like to see the API in Firefox.
0 new messages