IETF Logo Mail Archive

Re: [rtcweb] Working group last call for draft-ietf-rtcweb-audio

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Sat, 19 December 2015 00:10 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99AF41A00ED for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 16:10:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.51
X-Spam-Level:
X-Spam-Status: No, score=-114.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OhStV7LZI_rY for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 16:10:38 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF4101A00EA for <rtcweb@ietf.org>; Fri, 18 Dec 2015 16:10:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2818; q=dns/txt; s=iport; t=1450483837; x=1451693437; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=XTHwXZzD5FNQZgg8xlyIugOu0PZSD7g3jgJ9h/bng7g=; b=XYfxeuCxPN2vrRXKGKYAnaEweppPqeXp5pcJWONCTvwnPzHT79GNe9lF lRTnkZ+iAbELae+dAx7J+AvCmSKtCbjDfdmGMp5SUZhSUbTykFBugtevo vOyO2KUBYbmGrqTaVszptFqmTNrdNT3JiaXZqy03r4ECm56ixtpvtahfe s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AaAgBtn3RW/5NdJa1egm5MgT8GvVcBDYFjhg0CHIEZOBQBAQEBAQEBgQqENQEBBB0GVhACAQgEAToDAgICMBQRAgQOBYgvq3ySAwEBAQEBAQEBAQEBAQEBAQEBAQEBARiIZYJvh3cvgRoFln8BjUmdKAEgAQFChARyhBGBCAEBAQ
X-IronPort-AV: E=Sophos; i="5.20,448,1444694400"; d="scan'208,217"; a="55047709"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Dec 2015 00:10:37 +0000
Received: from XCH-RTP-002.cisco.com (xch-rtp-002.cisco.com [64.101.220.142]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id tBJ0Aa6x030405 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 19 Dec 2015 00:10:37 GMT
Received: from xch-rtp-004.cisco.com (64.101.220.144) by XCH-RTP-002.cisco.com (64.101.220.142) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 18 Dec 2015 19:10:36 -0500
Received: from xch-rtp-004.cisco.com ([64.101.220.144]) by XCH-RTP-004.cisco.com ([64.101.220.144]) with mapi id 15.00.1104.009; Fri, 18 Dec 2015 19:10:36 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [rtcweb] Working group last call for draft-ietf-rtcweb-audio
Thread-Index: AQHROb/f1JspZ+M0ik+ShWOkxZul4p7RZUcAgAARSQCAABq6gIAACYYAgAAHU4CAAANBAIAAEVmAgAAM8oA=
Date: Sat, 19 Dec 2015 00:10:35 +0000
Message-ID: <F9264ABC-E856-44B4-9E7E-8359B5D39A55@cisco.com>
References: <CA+9kkMDAL1mKqt7cTRmU4YqX2S5QN4RKn2cfbPaBeDgx=yiN0Q@mail.gmail.com> <CAD5OKxtvhaqx=H10=fUiGAjvnGAb_g89p2TZT9iNEg2F9k+6FA@mail.gmail.com> <CA+9kkMApyK4YPaWbQATy9zGfCOd3Dyfr8cY2amODgFE4XQCA=A@mail.gmail.com> <CAD5OKxtDGUv3akJTe6ZRYNhQN=SMY_R+GeV_Kg67Y6EYq+aV=A@mail.gmail.com> <CA+9kkMCvAcxnc=QdGvTm3=VNOQ3TtO+d8PfbfVA8sLeEA6rRqg@mail.gmail.com> <CAD5OKxtu-dsahdwL7t7Br34V-guqKmsdTsztOK_8sSsvWYsF=g@mail.gmail.com> <CA+9kkMBxbmGggCUaBPVtsJ7o3ZvBS=xvDKkmvfJxdVbM8NgiEQ@mail.gmail.com> <CAD5OKxvaJTRtfDQLwpvi+etdh8ZQvP5eRROSvRY2Hg-Uasisww@mail.gmail.com>
In-Reply-To: <CAD5OKxvaJTRtfDQLwpvi+etdh8ZQvP5eRROSvRY2Hg-Uasisww@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.64.117]
Content-Type: multipart/alternative; boundary="_000_F9264ABCE85644B49E7E8359B5D39A55ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/Y_dIsmQTP5hoYWVXIFiAKqpB1Ac>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Working group last call for draft-ietf-rtcweb-audio
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 19 Dec 2015 00:10:39 -0000

On Dec 18, 2015, at 3:24 PM, Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>> wrote:

This applies to all DTMF tones, not A-D specifically. What I am saying is that WebRTC endpoints must be able to generate all DTMF tones including A-D and send them to legacy PSTN (gateway).

The thing people keep asking is why? what is the use case ?

I don’t feel like I have seen an answer to this.

v2.23.0 | Report a Bug | By Email