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

Hadriel Kaplan <HKaplan@acmepacket.com> Wed, 16 November 2011 06:39 UTC

Return-Path: <HKaplan@acmepacket.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2466111E8181 for <rtcweb@ietfa.amsl.com>; Tue, 15 Nov 2011 22:39:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level:
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jM+xX5wonq-z for <rtcweb@ietfa.amsl.com>; Tue, 15 Nov 2011 22:39:00 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 63A4C11E815A for <rtcweb@ietf.org>; Tue, 15 Nov 2011 22:39:00 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 16 Nov 2011 01:38:59 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Wed, 16 Nov 2011 01:38:58 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Justin Uberti <juberti@google.com>
Thread-Topic: [rtcweb] The DTMF API [Was: Traffic should be encrypted. (Re: Let's define the purpose of WebRTC)]
Thread-Index: AQHMpCprwHHm9UP6Vkmh9RGs1wOxVQ==
Date: Wed, 16 Nov 2011 06:38:58 +0000
Message-ID: <733D6CE2-2360-4688-8268-3503F7E2460C@acmepacket.com>
References: <CAOJ7v-18cNX8xussOPXSEoFxAARu8WriL8XgxPVUXBrWhz=FFg@mail.gmail.com> <4EC28CF5.6000109@jesup.org> <D666B5A5-BF2E-46B7-B97F-06C3736E8357@acmepacket.com> <CAOJ7v-3v5Zu9ZOuL3Qqu+aEDJ4a3cqH+oJ2yj_ewOpxKe=jA_g@mail.gmail.com>
In-Reply-To: <CAOJ7v-3v5Zu9ZOuL3Qqu+aEDJ4a3cqH+oJ2yj_ewOpxKe=jA_g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B775C77C2C89264AA94DE48103699505@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: Randell Jesup <randell-ietf@jesup.org>, "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] The DTMF API [Was: Traffic should be encrypted. (Re: Let's define the purpose of WebRTC)]
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2011 06:39:01 -0000

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