Re: [rtcweb] DTMF resolution proposal
Jean-Marc Valin <jmvalin@mozilla.com> Wed, 09 March 2016 15:49 UTC
Return-Path: <jmvalin@mozilla.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 9674812E0DF for <rtcweb@ietfa.amsl.com>; Wed, 9 Mar 2016 07:49:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mozilla-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([127.0.0.1]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GtzwotCCUfl3 for <rtcweb@ietfa.amsl.com>; Wed, 9 Mar 2016 07:49:24 -0800 (PST)
Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2ECB12DFC4 for <rtcweb@ietf.org>; Wed, 9 Mar 2016 07:35:49 -0800 (PST)
Received: by mail-pf0-x22e.google.com with SMTP id n5so5166927pfn.2 for <rtcweb@ietf.org>; Wed, 09 Mar 2016 07:35:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=0hTmmBiaxYtdLXDZEXYcjUh4/N9GagcQDMujFlJc6vU=; b=ItURj/F0aeikppjJ9yj7Lp2ne8XmvQBk1gcPrUyURfCe31yIQk0FkcD1SfYISAt4O2 buavRYkrHh/YVcYxjwgAYcndSBg/TCdHiM13+QtIQxcHcS/Tmc6OFda9KoD9Bmz6wgGl kk3W/Ie0klbmG6WYf3Rf9JGtEY4YHtnm9waYdyMLFM06ZpRuWMhp5fksu0eEZyn7EPTc HrkSSoL97Yunep8KTPFuRW+yteIbjsuSLpC653Kt0E7MhN+Dc6QcmPkZDAB3cAepPsr7 3dcLHNekTcQAGjvPhqIoFG63PH3QUUV7NX/TNZ6o84gKoxsNt0sZRQVVDKgvTAgS5FLN Alqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=0hTmmBiaxYtdLXDZEXYcjUh4/N9GagcQDMujFlJc6vU=; b=l50IpuseuuXvrz20fPzbaKPFi9AyocTA7zto0dXIGgnwnLqZWNaOQbHWk6s6A3635q axlsVJU+nNEOJ7I6khS0axMSdPbWuZxudL5apfMvCVr/QN9sJlZvob97R/j1KvPPiJcg /rtKnMSe/jDe+yDOue+6x/+J02749dU1VQpITGF1ZmLgWe2oPqqmleEDErDy52alKj94 Vv7nSIpk/8SKVkhUJWk2Yxfk+zcWchwKtzMwHRR6xYCT1reqXkfHGKCb54i8+MDyoTip O8SK/48JpJ4P0V84i7XMv5fe4QbJol4kti2GlUFYlcrLFO9GThNrkysrqAY2KwHpVHce +H2w==
X-Gm-Message-State: AD7BkJIN7wUQeUEvzrcbzOKsPWkk+SQ5YGRxxDV5+g3Ri8ZB25FR+rY2wFgzGMUlMwBIAxt4
X-Received: by 10.98.18.195 with SMTP id 64mr40997255pfs.131.1457537749472; Wed, 09 Mar 2016 07:35:49 -0800 (PST)
Received: from panoramix.jmvalin.ca ([12.207.17.3]) by smtp.gmail.com with ESMTPSA id z5sm13316512par.21.2016.03.09.07.35.47 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Mar 2016 07:35:47 -0800 (PST)
To: Roman Shpount <roman@telurix.com>
References: <CA+9kkMANw8uPLObeGt68Rz+usObeDjQDYp-eQjp=WiCnWPByaQ@mail.gmail.com> <56DDF13F.1050505@mozilla.com> <CA+9kkMA3S2rgts+HRHqoDjzySzfq7w-mi4Ge8e_1b9wD=bEs8g@mail.gmail.com> <SN1PR0301MB15514F08779F54B3CD74BA34B2B20@SN1PR0301MB1551.namprd03.prod.outlook.com> <CAD5OKxsJpvGi3rp-AhCibei8vxvJ77cLf_z1b7GuJDzO2mq-Nw@mail.gmail.com> <56DF7C6B.4050400@mozilla.com> <CAD5OKxvLFJh7At0dS8yFP1khcqA09SOA30gd_fKcrsMYvSK2iQ@mail.gmail.com>
From: Jean-Marc Valin <jmvalin@mozilla.com>
Message-ID: <56E042D2.6000806@mozilla.com>
Date: Wed, 09 Mar 2016 10:35:46 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxvLFJh7At0dS8yFP1khcqA09SOA30gd_fKcrsMYvSK2iQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/e-6UbZcQ6Xz9bepFbpAPIqUClLg>
Cc: Cullen Jennings <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] DTMF resolution proposal
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Mar 2016 15:49:28 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 03/09/2016 10:31 AM, Roman Shpount wrote: > I would prefer the recommended values to stay in audio draft. OK, I can live with that and include the text you proposed: "WebRTC endpoints generated events MUST have duration of no more than 8000 ms and no less than 40 ms with the recommended default duration of 100 ms for each tone. The gap between events MUST be no less then 30 ms with the recommended default duration of 70 ms." Cheers, Jean-Marc > This draft already specifies preferences, such as not using CN with > OPUS, so it would make sense to include DTMF tone and gap duration > preferences as well. > > The recommendations are there to improve interoperability of > WebRTC end points with traditional PSTN, so it is not something > that should be defined by W3C document. > > This data useful in providing guidance for interop tests for > gateways, SBCs. or any other equipment which is designed to work > with WebRTC. I do not think gateway implementer should go through > the API document to find the typical tone and gap duration for > WebRTC. > > Finally, I have proposed to include this data as non-normative, > information only value, so there is very little harm in it being > there. > > Regards, _____________ Roman Shpount > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJW4ELMAAoJEJ6/8sItn9q9dEoH/AjAZZJc/f2CQzMOR8oPDI4n 2O4RNEu90vkGN4Tpy9JUOOEtt8pLAP+2j4e8VNz9/nG/YOsM2VZrbGMJn4LJEG/q Iyf65HKXoM6vdU3h9v1joT1qAVpKfdboP+VEEBxCl3Yg8B5b7IAshEIduqu1ucHh Oi3qzHOFUO2CAacjpSCk2ArZ+rPuse04NunV1P2Muuoge1TZt8psgtaN30MxtnDH dBhmI8tk1k7yikc4hn1tDfkSXxH2vHp6V/DwdBDOqxk9J0uWG+VJMl8zeI1Asl7i K6L2+0/vsYegJWlXN/7TwQj4ZRy1A4R05H3tDOLXkrgOs9QezOGSC1OEZuC8bqc= =oTLR -----END PGP SIGNATURE-----
- [rtcweb] DTMF resolution proposal Ted Hardie
- Re: [rtcweb] DTMF resolution proposal Jean-Marc Valin
- Re: [rtcweb] DTMF resolution proposal Ted Hardie
- Re: [rtcweb] DTMF resolution proposal Asveren, Tolga
- Re: [rtcweb] DTMF resolution proposal Roman Shpount
- Re: [rtcweb] DTMF resolution proposal Jean-Marc Valin
- Re: [rtcweb] DTMF resolution proposal Mark Harris
- Re: [rtcweb] DTMF resolution proposal Asveren, Tolga
- Re: [rtcweb] DTMF resolution proposal Asveren, Tolga
- Re: [rtcweb] DTMF resolution proposal Roman Shpount
- Re: [rtcweb] DTMF resolution proposal Jean-Marc Valin
- Re: [rtcweb] DTMF resolution proposal Jean-Marc Valin
- Re: [rtcweb] DTMF resolution proposal Roman Shpount
- Re: [rtcweb] DTMF resolution proposal Asveren, Tolga
- Re: [rtcweb] DTMF resolution proposal Roman Shpount
- Re: [rtcweb] DTMF resolution proposal Asveren, Tolga
- Re: [rtcweb] DTMF resolution proposal Ted Hardie
- Re: [rtcweb] DTMF resolution proposal Roman Shpount