IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Fri, 18 November 2011 10:06 UTC

Return-Path: <ibc@aliax.net>
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 D2F0921F8B21 for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 02:06:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.64
X-Spam-Level:
X-Spam-Status: No, score=-2.64 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 R7j0Hf8c-0Ni for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 02:06:19 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id DD3AE21F8B16 for <rtcweb@ietf.org>; Fri, 18 Nov 2011 02:06:18 -0800 (PST)
Received: by vcbfl15 with SMTP id fl15so3594088vcb.31 for <rtcweb@ietf.org>; Fri, 18 Nov 2011 02:06:16 -0800 (PST)
Received: by 10.52.36.41 with SMTP id n9mr2708147vdj.41.1321610775067; Fri, 18 Nov 2011 02:06:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.107.206 with HTTP; Fri, 18 Nov 2011 02:05:55 -0800 (PST)
In-Reply-To: <4EC60963.8060508@alvestrand.no>
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>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Fri, 18 Nov 2011 11:05:55 +0100
Message-ID: <CALiegfmFizZ7zC55MCHVs_w6EO-FHfn2fSH4+yqCD5O82T3MTw@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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:06:20 -0000

2011/11/18 Harald Alvestrand <harald@alvestrand.no>:
>> 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.
>
> OK, thanks.
>
> So the discussion that is really part of the IETF's task here is to pick one
> (and preferably one) way that WebRTC applications are recommended to do
> DTMF.

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.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email