IETF Logo Mail Archive

Re: [rtcweb] DTMF usecase before DTMF API [was RE: The DTMF API]

Hadriel Kaplan <HKaplan@acmepacket.com> Fri, 18 November 2011 03:02 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 AB0861F0C7E for <rtcweb@ietfa.amsl.com>; Thu, 17 Nov 2011 19:02:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level:
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114, 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 LKFDll+3W6WH for <rtcweb@ietfa.amsl.com>; Thu, 17 Nov 2011 19:02:51 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9DDBB1F0C61 for <rtcweb@ietf.org>; Thu, 17 Nov 2011 19:02:51 -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; Thu, 17 Nov 2011 22:02:50 -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; Thu, 17 Nov 2011 22:02:50 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: [rtcweb] DTMF usecase before DTMF API [was RE: The DTMF API]
Thread-Index: AQHMpZ6NMlLbVzl57kqSzWfRKkntqQ==
Date: Fri, 18 Nov 2011 03:02:49 +0000
Message-ID: <6725A83E-0BB0-4F86-AB27-75027E317710@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> <733D6CE2-2360-4688-8268-3503F7E2460C@acmepacket.com> <9A05449A-C0FB-4548-AA80-728EC82218BB@acmepacket.com> <387F9047F55E8C42850AD6B3A7A03C6C01CE9B22@inba-mail01.sonusnet.com> <4EC5C6FB.4040804@alvestrand.no>
In-Reply-To: <4EC5C6FB.4040804@alvestrand.no>
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: <C2AEC4D195E90546BA1B6D9E98C7AB6B@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] DTMF usecase before DTMF API [was RE: The DTMF API]
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: Fri, 18 Nov 2011 03:02:57 -0000

On Nov 17, 2011, at 9:46 PM, Harald Alvestrand wrote:
> 
>>  AFAIK, DTMF is not directly going to useful in browser-browser scenario and it is possible to pass DTMF in the signaling layer for H.323, SIP in the standard manner.
> What do you mean by "the standard manner"?

H.323 and SIP both offer a signaling-plane means of indicating DTMF, other than RFC 2833/4733.  For H.323 it's H.245 User Input Indications (UII) messages.  For SIP it's officially KPML (RFC 4730), but in practice it's not popular.  Two vendors I know of support it, but it's a drop in the bucket compared to rfc2833 or SIP INFO.


>> IMO, There are way to solve DTMF in WebRTC without including media level API.
> How do you propose to allow Alice in the use case to navigate the IVR without having some API that allows injecting DTMF?

Well in theory the Javascript could send a message to the Web Server to generate a "dtmf event", which the server interworks to a SIP KPML NOTIFY in a KPML subscription.

-hadriel

v2.23.0 | Report a Bug | By Email