W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2012

[Bug 18485] Change DTMF API to be on PeerConnection

From: <bugzilla@jessica.w3.org>
Date: Wed, 17 Oct 2012 08:38:30 +0000
To: public-webrtc@w3.org
Message-ID: <bug-18485-4991-i2lEhwWJmh@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18485

--- Comment #6 from Harald Alvestrand <harald@alvestrand.no> ---
The previous suggestion, with a track on which feedback would be given, gave
some pushback - what the feedback should be, whether a track is the appropriate
form of feedback, and so on.

New suggestion (still not valid IDL):

pc.canSendDTMF(MediaStreamTrack)
pc.sendDTMF(MediaStreamTrack outTrack, tones, duration, optional callback)

with the handling rule being

1) If the outTrack argument to sendDTMF is not an audio track connected to this
PeerConnection on an outgoing SSRC where use of RFC 4733 DTMF has been
negotiated, throw a <ArgumentError?> exception.
2) Simultaneously do the following:
- Send the tones using RFC 4733 signalling on the outTrack
- Every time a tone starts and stops, call the callback with either the
character of the tone being played or an empty string argument.

Then people can do whatever they like with the feedback tone.

Is this simple enough to let us close this issue?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Wednesday, 17 October 2012 08:38:35 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:30 UTC