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

Re: DTMF v4

From: Roman Shpount <roman@telurix.com>
Date: Fri, 14 Dec 2012 16:10:29 -0500
Message-ID: <CAD5OKxuZ2Xx+WUmP=tR9mqDVOt0GG5Yt=Uo2ZbVvsOi+vGX-WA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
WebRTC-SIP Interworking Requirements Draft states that:

A3-4 WebRTC MUST provide a means for the Javascript application to invoke
[RFC4733] DTMF events to be generated, and their duration, with a default
duration of 100ms.

A3-6 WebRTC MUST NOT generate [RFC4733] events closer than 50ms
back-to-back.  In other words, even if                      the Javascript
calls the API repeatedly or provides a string of digits to send, the
browser must enforce a minimum of 50ms inter-event gap.

There are several fairly old recommendations, such as ITU-T V.18, on which
these values are based, but the bottom line that these values are usually
considered safe.

_____________

Roman Shpount

On Fri, Dec 14, 2012 at 3:53 PM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 14 December 2012 12:40, Harald Alvestrand <harald@alvestrand.no> wrote:
> > Bernard mentioned a minimum gap (I think he said 50 ms), but I'm not sure
> > where that came from.
>
> Minimum values come from experience with IVR interoperation for cases
> where the tone is subsequently mixed into the audio.  Too short a tone
> (or gap) and some IVRs fail to detect the tone.  I've seen minimum
> tone duration of 100ms and gap of 50ms in some cases, though more
> conservative values might be appropriate.  I have no good data to back
> any specific choice.  I expect fluffy has more data than I.
>
>
Received on Friday, 14 December 2012 21:11:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 14 December 2012 21:11:03 GMT