Re: [rtcweb] DTMF resolution proposal

[Roman Shpount <[e-mail]>]

On Wed, Mar 9, 2016 at 11:52 AM, Asveren, Tolga <[e-mail]>
wrote:

> “WebRTC endpoints, such as browsers, will not do anything with RFC 4733
> tones sent from the gateway, except gracefully drop them. There is
> currently no API to inform JavaScript about the received DTMF or other RFC
> 4733 tones.
>
>
>
> Do you want the language added to the specification that WebRTC endpoint
> should be able to receive any RFC 4733 tones and process them in a graceful
> manner?”
>
>
>
> This sounds strange to me (using digits unidirectionally) but I would
> think that browser vendors should weigh in on this one. For me, the
> practically important point is that gateway can send RFC4733 digits toward
> the browser/native WebRTC app without being restricted by the defined
> range. There wouldn’t be any issue from my perspective if browsers are
> anyhow going to drop the digits (I assume this would be the same for native
> WebRTC application) but **if** things change so that they may process
> them, then I would prefer the text to be clear that the range restriction
> does not apply for digits from a gateway toward the browser/native app.
>
>
>
>
> WebRTC enabled browsers are clients, so they do not normally need to
process digits. This is similar VoIP Phones, which will send RFC 4733 DTMF
tones but have no reason to process them.

Native applications can do whatever they want with the digits that they
receive.

So, does anybody needs the language that gateways can generate any RFC 4733
digits they like and WebRTC end point can ignore them?

Regards,
_____________
Roman Shpount