Re: [rtcweb] #1: RFC 4734 citation

Right. But somehow RFC 4734 was cited instead.

On Oct 31, 2012, at 10:41 AM, "Roman Shpount" <roman@telurix.com> wrote:

> 
> On Wed, Oct 31, 2012 at 1:12 PM, Iñaki Baz Castillo <ibc@aliax.net> wrote:
>> Well, as we all assume that media gateways are requried for interoperability with other VoIP networks, I assume it would be not so hard that the gateway receives the "DTMF's" via WWW means (HTTP, WebSocket...) and generates RTP DTMF's in the legacy leg.
>> 
>> Anyhow I expect that it's not so hard to implement RTP DTMF's in a media stack, but I would not like to hear about "my PBX's does not detect Chrome's DTMF's". :)
> 
> We had an extensive discussion few months back on why RFC 4733 tones are required. The main reason is time synchronization of audio and DTMF. If you have an application which does something like "record your name and press pound", and DTMF is delivered over a separate path, you end up with name either truncated or padded with silence. In any case, I believe, there was a group consensus that RFC 4733 DTMF tones will be supported.
> _____________
> Roman Shpount
>  
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb