Re: [rtcweb] DTMF resolution proposal

[Roman Shpount <[e-mail]>]

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

>  “WebRTC endpoint is specifically different from WebRTC-compatible
> endpoint. WebRTC-compatible endpoints do not have to implement OPUS or CN.
> They just need to interop with full WebRTC endpoints.”
>
> As the bottom line, would a gateway need to comply with the range
> restrictions for the RFC4733 it is sending toward the WebRTC leg or not? I *
> *think** what you say is that it does not. I strongly would prefer that
> the text is clear on this issue.
>
>
>
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?

I think I have previously proposed the following:

Receivers MUST be able to consume any audio/telephone-event events
in such a way that it will not generate audio artifacts, jitter buffer
adjustments, payload mismatches, or invalid RTCP statistics calculation.
Receivers MAY generate audio corresponding to the received events
but are also allowed to discard them in a manner that does not affect
regular audio processing.

This language was dropped as obvious, but can be included if you think is
necessary and no one objects.

Regards,
_____________
Roman Shpount