IETF Logo Mail Archive

Re: [rtcweb] Support DTMF "codec" or expose DTMF in signaling? (Re: DTMF usecase before DTMF API)

Saúl Ibarra Corretgé <saul@ag-projects.com> Fri, 18 November 2011 10:48 UTC

Return-Path: <saul@ag-projects.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 CA42521F8A69 for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 02:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.688
X-Spam-Level:
X-Spam-Status: No, score=-1.688 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3]
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 SvTFJpHn7474 for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 02:48:52 -0800 (PST)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id 49CFD21F8A62 for <rtcweb@ietf.org>; Fri, 18 Nov 2011 02:48:51 -0800 (PST)
Received: by mail.sipthor.net (Postfix, from userid 5001) id B5AA3B01BE; Fri, 18 Nov 2011 11:48:50 +0100 (CET)
Received: from [192.168.99.36] (ip3e830637.speed.planet.nl [62.131.6.55]) by mail.sipthor.net (Postfix) with ESMTPSA id 782F6B01A5; Fri, 18 Nov 2011 11:48:46 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Saúl Ibarra Corretgé <saul@ag-projects.com>
In-Reply-To: <4EC63561.10909@skype.net>
Date: Fri, 18 Nov 2011 11:48:45 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <19BDB368-9F0F-4DA2-B9EC-16D5586CFFEC@ag-projects.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> <6725A83E-0BB0-4F86-AB27-75027E317710@acmepacket.com> <4EC60963.8060508@alvestrand.no> <CALiegfmFizZ7zC55MCHVs_w6EO-FHfn2fSH4+yqCD5O82T3MTw@mail.gmail.com> <4EC63561.10909@skype.net>
To: Matthew Kaufman <matthew.kaufman@skype.net>
X-Mailer: Apple Mail (2.1084)
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Support DTMF "codec" or expose DTMF in signaling? (Re: DTMF usecase before 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 10:48:52 -0000

>>> 
>> In case http://tools.ietf.org/html/draft-kaplan-dispatch-info-dtmf-package-00
>> becomes a standard, there is no need to send DTMF over the media
>> stream (when interoperating with SIP networks). Since this just
>> concerns the in-the-wire signaling it becomes up to the application
>> developer.
>> 
>> 
> Are you advocating that we not put DTMF-in-media support in browsers (in which case I have a good argument against), or are you simply making an observation about an alternative that may also become available?
> 

Do you have any application for DTMF in mind other than PSTN interoperability? I'd like to hear that argument against not having DTMF-in-media support in the browser :-)

--
Saúl Ibarra Corretgé
AG Projects

v2.23.0 | Report a Bug | By Email