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

Re: [Bug 18485] Change DTMF API to be on PeerConnection

From: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
Date: Wed, 8 Aug 2012 17:26:08 +0200
Message-ID: <50228510.8090905@ericsson.com>
To: public-webrtc@w3.org
On 08/08/2012 04:28 PM, Randell Jesup wrote:

>> I agree in principle, but to me DTMF is only relevant for apps
>> interoperating with legacy, and in those cases you need to also deploy
>> e.g. an ICE terminating GW - in my view we could allow DTMF use to be
>> a bit more complex since it is not relevant for the simple
>> (browser-browser) case anyway.
> That's kind of my point - many apps may not know (especially in
> federated cases) that they're talking to a PSTN legacy gateway and to an
> IVR.
Not sure I follow. Why would the app use DTMF at all if it wasn't 
(knowing that it was) talking to GW to legacy or to an IVR?

> I'll agree an app designed to be a virtual softphone from a
> company that provides PSTN gateways would likely include whatever is
> needed to get working DTMF.  So that why I suggest include a simple
> default action on the event (assuming we define MediaStream events,
> which I've suggested) and let the app override that.
> All that said, this isn't a big issue either way.  Echo-cancelling local
> feedback is more important.
I agree to both points!
Received on Wednesday, 8 August 2012 15:26:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:32 UTC