IETF Logo Mail Archive

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

Matthew Kaufman <matthew.kaufman@skype.net> Fri, 18 November 2011 11:57 UTC

Return-Path: <matthew.kaufman@skype.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 28ADA21F8B03 for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 03:57:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.374
X-Spam-Level:
X-Spam-Status: No, score=-6.374 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 plzV1KKCrq-y for <rtcweb@ietfa.amsl.com>; Fri, 18 Nov 2011 03:57:09 -0800 (PST)
Received: from mx.skype.net (mx.skype.net [78.141.177.88]) by ietfa.amsl.com (Postfix) with ESMTP id 67F2A21F8B02 for <rtcweb@ietf.org>; Fri, 18 Nov 2011 03:57:08 -0800 (PST)
Received: from mx.skype.net (localhost [127.0.0.1]) by mx.skype.net (Postfix) with ESMTP id B7D867FE; Fri, 18 Nov 2011 12:57:07 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=skype.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mx; bh=3yxzlqrGiC3auP A2kU9WsPeS5dw=; b=L/8TaDTwlsvZST11uPYlOVglEHLUthCtsIQHtWZHoBuyxi 4BTehqXfGbIkHAAOEMHZqHi+oQhqVFq+pT45A1VILueIVuxyddCHLtxPtTytC5MU YRdeMZ93HoEDfHmJpd9s1oZ5tORtqRWqn6avW0n6lQFyJE+1iNER9VfpXWK4w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=skype.net; h=message-id:date:from :mime-version:to:cc:subject:references:in-reply-to:content-type: content-transfer-encoding; q=dns; s=mx; b=Khi6gSqrPVA4tPzSHHpPWX qUh/8805XNgMG63uY1lGHiTVC//AF47HAJzq0HOiKwpcD5srLaLF4+fEBLntVmgd VY8CqyuqYvcSrJh0II82hOuDVsYg4/1WMa+3chgIrV8NL5Qo3SOallkdAc+ROBue GRt88YFHPN7OM00gvD1zM=
Received: from zimbra.skype.net (zimbra.skype.net [78.141.177.82]) by mx.skype.net (Postfix) with ESMTP id B65D47EB; Fri, 18 Nov 2011 12:57:07 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by zimbra.skype.net (Postfix) with ESMTP id 553821672681; Fri, 18 Nov 2011 12:57:07 +0100 (CET)
X-Virus-Scanned: amavisd-new at lu2-zimbra.skype.net
Received: from zimbra.skype.net ([127.0.0.1]) by localhost (zimbra.skype.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WtyVYNwSTVdt; Fri, 18 Nov 2011 12:57:06 +0100 (CET)
Received: from Matthew-Kaufman-Air.local (unknown [203.69.99.16]) by zimbra.skype.net (Postfix) with ESMTPSA id 37D5C35074B9; Fri, 18 Nov 2011 12:57:04 +0100 (CET)
Message-ID: <4EC6480D.7080505@skype.net>
Date: Fri, 18 Nov 2011 19:57:01 +0800
From: Matthew Kaufman <matthew.kaufman@skype.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Iñaki Baz Castillo <ibc@aliax.net>
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> <CALiegfnraby3e_TKMj95VUvaEyg3deomL=yciw0EW13O5q9w5w@mail.gmail.com>
In-Reply-To: <CALiegfnraby3e_TKMj95VUvaEyg3deomL=yciw0EW13O5q9w5w@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
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 11:57:10 -0000

On 11/18/11 7:53 PM, Iñaki Baz Castillo wrote:
> So sending DTMF's over the signaling path is just better than sending 
> them over the media stream, IMHO for all the possible cases.


Except for all use cases where the only way to send DTMF is over the 
media path, because (for instance) there is no signaling protocol which 
supports sending DTMF and/or the signaling service is no longer in-path 
when DTMF needs to be sent.

Matthew Kaufman

v2.23.0 | Report a Bug | By Email