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

[Bug 18485] Change DTMF API to be on PeerConnection

From: <bugzilla@jessica.w3.org>
Date: Wed, 08 Aug 2012 10:23:07 +0000
Message-Id: <E1Sz3Pv-0005EX-OR@jessica.w3.org>
To: public-webrtc@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18485

Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stefan.lk.hakansson@ericsso
                   |                            |n.com

--- Comment #2 from Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com> 2012-08-08 10:23:07 UTC ---
(In reply to comment #1)

As for alternatives B and C, I think that the tones should not be inserted in
the same MediaStream as the outgoing DTMF. The tones are to be used for local
feedback, and you would not like to play the other outgoing audio locally.

I think we should go for alternative A initially.



> based on discussion on the list, there seems to be 3 alternate descriptions of
> what sendDTMF actually does.
> 
> I outline them below as text that can be inserted into the description.
> 
> A) 
> 1) If the track 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 <IllegalParameter> exception.
> 2) Send the tones using RFC 4733 signalling.
> 
> B)
> 1) If the track argument to sendDTMF is not an audio track connected to this
> PeerConnection, throw an <illegalParameter> exception.
> 2) If sendDTMF is connected to an outgoing SSRC where use of RFC 4377 is
> negotiated, send the tones using RFC 4377 and return.
> 3) Insert the corresponding tones into the media stream as if they were coming
> from the media source.
> 
> C)
> 1) If sendDTMF is connected to an outgoing SSRC on this PeerConnection where
> use of RFC 4377 is negotiated, send the tones using RFC 4377 and return.
> 2) Insert the corresponding tones into the media stream as if they were coming
> from the media source.
> 
> The difference between B) and C) is that B) insists on using the right PC to
> generate tones.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- 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, 8 August 2012 10:23:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 8 August 2012 10:23:13 GMT