Re: [codec] #5: Mention DTMF in requirements
Koen Vos <koen.vos@skype.net> Wed, 07 April 2010 17:28 UTC
Return-Path: <koen.vos@skype.net>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 160C53A694A for <codec@core3.amsl.com>; Wed, 7 Apr 2010 10:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level:
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YxMtUvQ0an3r for <codec@core3.amsl.com>; Wed, 7 Apr 2010 10:28:50 -0700 (PDT)
Received: from mail.skype.net (mail.skype.net [212.187.172.39]) by core3.amsl.com (Postfix) with ESMTP id 2CD5C3A6AA1 for <codec@ietf.org>; Wed, 7 Apr 2010 10:28:16 -0700 (PDT)
Received: from mail.skype.net (localhost [127.0.0.1]) by mail.skype.net (Postfix) with ESMTP id 236E06097EC1B for <codec@ietf.org>; Wed, 7 Apr 2010 18:28:13 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=skype.net; h=message-id :date:from:to:subject:references:in-reply-to:mime-version :content-type:content-transfer-encoding; s=mail; bh=T2R+nM2Dw2nw m1V0afcyEZXQzq8=; b=PSkdP41cP4Z0tZw1RSy/AiLZaiWgOWNlAQro/+8GC+MX Sbt/wEwvx7FaDb6DxojSv8wQYzbcPoKxxHLoQqm5WLb+K5VYYcTSLRz+AJalYT6v BdroEVqykjfd5oiEdITjZkkMNkvjwhj3ov2Ud32pC+65pamBIYxD/lUi00hwdDw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=skype.net; h=message-id:date:from :to:subject:references:in-reply-to:mime-version:content-type: content-transfer-encoding; q=dns; s=mail; b=sO0VXfRdM8Q/ICBi0/2T pNLM2rhGK6JVqYHQxeNRwFhLp6g/eQS6aLLWrDv5JhgzVDq/sKhqKWOIy3i3zZyE YlrJ19jo9DiPjYVud5qPhEqloGsj1zPaLBQeignOHUgQzsCu051n9FN18qzfYsAY JW6F/eX8yMqSUkq+8CpiXeY=
Received: from localhost (localhost [127.0.0.1]) by mail.skype.net (Postfix) with ESMTP id 21B6860970269 for <codec@ietf.org>; Wed, 7 Apr 2010 18:28:13 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at dub-mail.skype.net
Received: from mail.skype.net ([127.0.0.1]) by localhost (dub-mail.skype.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id prk4+gGV6PuQ for <codec@ietf.org>; Wed, 7 Apr 2010 18:28:12 +0100 (IST)
Received: by mail.skype.net (Postfix, from userid 33) id 31AB76097EC1A; Wed, 7 Apr 2010 18:28:12 +0100 (IST)
Received: from adsl-71-141-129-119.dsl.snfc21.pacbell.net (adsl-71-141-129-119.dsl.snfc21.pacbell.net [71.141.129.119]) by mail.skype.net (Horde Framework) with HTTP; Wed, 07 Apr 2010 10:28:12 -0700
Message-ID: <20100407102812.15301dp1i39umzsc@mail.skype.net>
Date: Wed, 07 Apr 2010 10:28:12 -0700
From: Koen Vos <koen.vos@skype.net>
To: codec@ietf.org
References: <05542EC42316164383B5180707A489EE1D0AA5F58E@EMBX02-HQ.jnpr.net> <003d01cad270$91acee00$b506ca00$@de> <h2i6e9223711004020749u48c533eaq720b89f374cfbe9f@mail.gmail.com> <000301cad28a$ca0c6450$5e252cf0$@de> <n2j28bf2c661004021202s507c675ek50a1a216da540f8f@mail.gmail.com> <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3B86EB6@IRVEXCHCCR01.corp.ad.broadcom.com> <w2r28bf2c661004021825p4e3a6749k8888ecdc672ee427@mail.gmail.com> <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3B87056@IRVEXCHCCR01.corp.ad.broadcom.com> <4BBB1F67.2080101@digium.com> <p2u6e9223711004060749tac75f8fbs926257d8ee5e0743@mail.gmail.com>
In-Reply-To: <p2u6e9223711004060749tac75f8fbs926257d8ee5e0743@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.4)
Subject: Re: [codec] #5: Mention DTMF in requirements
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Apr 2010 17:28:51 -0000
The distinction between use case and testing makes sense to me. DTMF is a real use case. For example some PSTN gateways still don't support out-of-band DTMF. It's unclear what to test about DTMF though. The Codec will support a range of sample rates and bitrates. The requirements specify coding of music at near-transparent quality. I don't see how a such a codec could not provide sufficient quality for in-band DTMF. At the same time, the requirements talk about bitrates down to 8 kbps, where it may be quite tricky to get DTMF to work well. Therefore, specifying that the codec SHOULD or MUST encode DTMF with sufficient quality is meaningless. If anything, the bitrate settings that allow in-band DTMF could be characterized after the Codec is formed. Nevertheless it's good to be aware of these use cases during development. For instance, with SILK we included DTMF signals in the LSF quantizer training database. Similarly, I see tandem coding as a use case to keep in mind during development, but again don't see a need for testing or MUST/SHOULD requirements. koen. Quoting stephen botzko: > I agree that there is a pretty strong consensus that carriage of "analog" > fax and modem signals is a non-requirement. If by "payload switching" we > are talking about switching codecs, then that is beyond the charter scope. > > I am thinking that we are getting a bit too focused on testing methods. In > my view it would be more efficient to capture use cases, and derive MUST and > SHOULD requirements from them first. Then go back and figure out what we > will test and how we will test it. > > Stephen Botzko > > > > On Tue, Apr 6, 2010 at 7:47 AM, Kevin P. Fleming <kpfleming@digium.com>wrote: > >> Raymond (Juin-Hwey) Chen wrote: >> >> > 2. Did you ever test your CODEC for other telephony signals, such as >> > /ANSam, ANS, CED, and CI tones? These tones are needed in order to >> > detect modems and fax machines and switch to an appropriate payload. >> > What about progress tones? >> > [Raymond]: No, we didn't. However, if these are single-frequency tones, >> > I would expect that it should be easier for a typical codec to pass >> > these tones than to pass the dual-frequency DTMF signals without causing >> > significant degradation in the subsequent processing of these tones. >> >> This is pretty much a dead-end based on the other comments on this list, >> but in general, no, most of these tones are *not* single-frequency >> simple tones. ANSam, for example, is a single frequency, but is >> amplitude modulated. There are also variants that have phase reversals, >> and these must be preserved for them to be discriminated from the >> non-phase-reversal versions. >> >> -- >> Kevin P. Fleming >> Digium, Inc. | Director of Software Technologies >> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA >> skype: kpfleming | jabber: kfleming@digium.com >> Check us out at www.digium.com & www.asterisk.org >> >> _______________________________________________ >> codec mailing list >> codec@ietf.org >> https://www.ietf.org/mailman/listinfo/codec >> >
- [codec] #5: Mention DTMF in requirements codec issue tracker
- Re: [codec] #5: Mention DTMF in requirements codec issue tracker
- Re: [codec] #5: Mention DTMF in requirements Christian Hoene
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Michael Knappe
- Re: [codec] #5: Mention DTMF in requirements, Tes… Christian Hoene
- Re: [codec] #5: Mention DTMF in requirements Marc Petit-Huguenin
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Marc Petit-Huguenin
- Re: [codec] #5: Mention DTMF in requirements, Tes… Wyss, Felix
- Re: [codec] #5: Mention DTMF in requirements, Tes… Steve Underwood
- Re: [codec] #5: Mention DTMF in requirements Steve Underwood
- Re: [codec] #5: Mention DTMF in requirements James Rafferty
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Peter Saint-Andre
- Re: [codec] #5: Mention DTMF in requirements James Rafferty
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Brian West
- Re: [codec] #5: Mention DTMF in requirements Brian West
- Re: [codec] #5: Mention DTMF in requirements Brian West
- Re: [codec] #5: Mention DTMF in requirements Brian West
- Re: [codec] #5: Mention DTMF in requirements Michael Knappe
- Re: [codec] #5: Mention in requirements, FAX? Christian Hoene
- Re: [codec] #5: Mention in requirements, FAX? James Rafferty
- Re: [codec] #5: Mention DTMF in requirements Christian Hoene
- Re: [codec] #5: Mention in requirements, FAX? Marc Petit-Huguenin
- Re: [codec] #5: Mention in requirements, FAX? Michael Knappe
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention in requirements, FAX? stephen botzko
- Re: [codec] #5: Mention in requirements, FAX? Michael Knappe
- Re: [codec] #5: Mention DTMF in requirements Christian Hoene
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements James Rafferty
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Roman Shpount
- Re: [codec] #5: Mention DTMF in requirements Marc Petit-Huguenin
- Re: [codec] #5: Mention DTMF in requirements Wyss, Felix
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Roman Shpount
- Re: [codec] #5: Mention DTMF in requirements Roman Shpount
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Marc Petit-Huguenin
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Brian West
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Roman Shpount
- Re: [codec] #5: Mention DTMF in requirements Benjamin M. Schwartz
- Re: [codec] #5: Mention DTMF in requirements Roman Shpount
- Re: [codec] #5: Mention DTMF in requirements Peter Saint-Andre
- Re: [codec] #5: Mention DTMF in requirements codec issue tracker
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Raymond (Juin-Hwey) Chen
- Re: [codec] #5: Mention DTMF in requirements Kevin P. Fleming
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Koen Vos
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Wyss, Felix
- Re: [codec] #5: Mention DTMF in requirements stephen botzko
- Re: [codec] #5: Mention DTMF in requirements Michael Knappe
- Re: [codec] #5: Mention DTMF in requirements codec issue tracker