Re: [codec] #5: Mention DTMF in requirements
stephen botzko <stephen.botzko@gmail.com> Tue, 06 April 2010 14:49 UTC
Return-Path: <stephen.botzko@gmail.com>
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 E49663A680E for <codec@core3.amsl.com>; Tue, 6 Apr 2010 07:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 TzwXyMvCTKMW for <codec@core3.amsl.com>; Tue, 6 Apr 2010 07:49:38 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id ACBB23A692B for <codec@ietf.org>; Tue, 6 Apr 2010 07:49:34 -0700 (PDT)
Received: by pwj2 with SMTP id 2so2528373pwj.31 for <codec@ietf.org>; Tue, 06 Apr 2010 07:49:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=LPGyYZYvimiUfoaAy/N7t3HfTTKWnvsqLTybXJ76lIg=; b=nwj54n7nm5YTVmClWxXpXmjjQgSTI4W3SPMDYmpoQh4KXYHNj422I7g+lCh5CWhBTr wLluQcblKEG1P4wl4tCY94lnTrF+ouWilbXFnvw19G69KU516/aEFJ9/HRHY74rix8qE u/ttZ/M2m0wEjRYrbA3RHtHY3rdGB/jGX4b3w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=KYnF9DedFNKJTziP2LTThYmyoqnvl+W2sMjkVRJEuoy0UL2VuACx9r4+o/vhGcKosZ Fzh7tVgvF0X+7uMCDW1ku5e20KqWhllCNzqYMonkOIZN/ec4N9Iz3taVKcvrb7DDqr5Q aO0VTsZAyzv2CaZ0GTZr9CdKdJc18Cv4ilUuc=
MIME-Version: 1.0
Received: by 10.231.85.133 with HTTP; Tue, 6 Apr 2010 07:49:29 -0700 (PDT)
In-Reply-To: <4BBB1F67.2080101@digium.com>
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>
Date: Tue, 06 Apr 2010 10:49:29 -0400
Received: by 10.115.38.21 with SMTP id q21mr6700936waj.217.1270565369466; Tue, 06 Apr 2010 07:49:29 -0700 (PDT)
Message-ID: <p2u6e9223711004060749tac75f8fbs926257d8ee5e0743@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: "Kevin P. Fleming" <kpfleming@digium.com>
Content-Type: multipart/alternative; boundary="0016e64cb95682d48e0483928d09"
Cc: "codec@ietf.org" <codec@ietf.org>
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: Tue, 06 Apr 2010 14:49:40 -0000
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