Re: [rtcweb] The DTMF API [Was: Traffic should be encrypted. (Re: Let's define the purpose of WebRTC)]

[Hadriel Kaplan <[e-mail]>]

FYI - I asked an expert and he said that for the default DTMF duration that although 50ms is the official minimum, in practice it's safer to use 100ms and people often do that (or even longer but we don't need to).  We also need to have a 50ms gap minimum.
So basically confirming what was already stated in other emails in this thread.

-hadriel


On Nov 16, 2011, at 1:38 AM, Hadriel Kaplan wrote:

> 
> On Nov 16, 2011, at 1:13 AM, Justin Uberti wrote:
> 
>> [Local]MediaStreamTrack.sendDTMF(in DOMString tones, in optional long duration)
>> 
>> ex:
>> sendDTMF("1")  // plays tone 1 for 50 ms
>> sendDTMF("2", 200)  // plays tone 2 for 200 ms
>> sendDTMF("123")  // plays tones 1, 2, 3 in succession, each for 50 ms
>> sendDTMF("456", 200)  // plays tones 4, 5, 6 in succession, each for 200 ms
> 
> Sounds good to me, but supporting a multi-digit-string as you did above reminds me that I'll have to check with some experts if this is ok - it reminded me there have been issues with DTMFs being too close to each other in time, but I am not an expert in that and it may not be an issue at all.  (there were issues in PSTN when multiple DTMFs were generated back-to-back from a saved address-book contact-entry type thing, but it may have only been a problem for using in-band DTMF which won't be an issue here)
> I'll ask.
> 
> -hadriel
> 
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb