Re: [codec] #5: Mention DTMF in requirements, Testing DTMF?
Steve Underwood <steveu@coppice.org> Fri, 02 April 2010 06:23 UTC
Return-Path: <steveu@coppice.org>
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 5EA8E3A6899 for <codec@core3.amsl.com>; Thu, 1 Apr 2010 23:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.131
X-Spam-Level: *
X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
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 gY03LWpMW0Fu for <codec@core3.amsl.com>; Thu, 1 Apr 2010 23:23:57 -0700 (PDT)
Received: from cwb.pacific.net.hk (cwb.pacific.net.hk [202.14.67.92]) by core3.amsl.com (Postfix) with ESMTP id 13F323A6A61 for <codec@ietf.org>; Thu, 1 Apr 2010 23:23:30 -0700 (PDT)
Received: from i7.coppice.org (93.176.64.202.dyn.pacific.net.hk [202.64.176.93]) by cwb.pacific.net.hk with ESMTP id o326O27d009330 for <codec@ietf.org>; Fri, 2 Apr 2010 14:24:03 +0800
Message-ID: <4BB58D82.5010508@coppice.org>
Date: Fri, 02 Apr 2010 14:24:02 +0800
From: Steve Underwood <steveu@coppice.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc11 Thunderbird/3.0.3
MIME-Version: 1.0
To: codec@ietf.org
References: <05542EC42316164383B5180707A489EE1D0AA5F54E@EMBX02-HQ.jnpr.net> <001d01cace82$1c8a0c80$559e2580$@de> <B043FD61A001424599674F50FC89C2D7A083117BF7@ININMAIL.i3domain.inin.com>
In-Reply-To: <B043FD61A001424599674F50FC89C2D7A083117BF7@ININMAIL.i3domain.inin.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [codec] #5: Mention DTMF in requirements, Testing DTMF?
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: Fri, 02 Apr 2010 06:23:59 -0000
Hi, I'm the author of the SpanDSP library people have referenced. People seem to have only mentioned DTMF talk-off in these discussions, but the issue of corrupting the DTMF so it is less detectable is probably more of an issue. Over the years there have been two reference data sets for testing DTMF talk off - the one from Mitel, and the one from Bellcore. Both started out as audio cassette tape products. The files I use for DTMF testing with SpanDSP are: - A wave file produced by resampling to 8k samples/second the MP3 version of the Mitel tape, which Mitel's heirs provide freely. If this is fed to TDM equipment it seems to give pretty much the same hits and near misses as the original Mitel cassette tape version. It seems, therefore, that aging of the original tape and transcription to MP3 have no unduly affected he signal. - A set of wave files which were produced years ago from a pristine set of the Bellcore test tapes, using a cassette player with speed adjustment, so the pitch could be tweaked to be bang on target. Later, Telcordia/Bellcore stopped selling the tapes, and they gave me permission to hand out these files to a couple of people. Since they are transcribed from copyright tapes, I only handed them out where permission was sought. Now they seem to have introduced an audio CD version of the tapes. You could use almost any long passages of speech for this kind of testing, but the above two data sets are the industry accepted ones, as you can compare different DTMF detectors reasonably well by comparing their false hits on this data. The Bellcore tapes are about 3 hours of audio, taken from the PSTN, where the call changes several times per seond. This is quite a tough test. The Mitel tape is about 30 minutes of audio passages recorded from the PSTN. Here they change the call every sentance or two, so the character os the test is somewhat different. It is much easier to get a good result with the Mitel tape, for various reasons, although I have found the Mitel tape a pretty good one for exercising talk-off issues in things like 2280Hz and 2600Hz signalling tone detectors. The detection performance of DTMF detectors is usually quoted by their performance against the other data Mitel provided - a set of DTMF digits with various distortions of level, frequency and noise component. I took the spec for that data, and built a test suite which synthesises the relevant signals more precisely than the recordings on the Mitel tape. I encourage anyone interested in DTMF to make use of that work. Regards, Steve On 03/29/2010 06:17 AM, Wyss, Felix wrote: > > Christian, > > Telcordia sells the "Bellcore tape" DTMF talk-off immunity test > recordings as a set of 3 CDs: > > http://telecom-info.telcordia.com/site-cgi/ido/docs.cgi?ID=SEARCH&DOCUMENT=FR-763-01 > <http://telecom-info.telcordia.com/site-cgi/ido/docs.cgi?ID=SEARCH&DOCUMENT=FR-763-01> > > --Felix > > *From:* codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] *On > Behalf Of *Christian Hoene > *Sent:* Sunday, March 28, 2010 10:22 > *To:* codec@ietf.org > *Subject:* Re: [codec] #5: Mention DTMF in requirements, Testing DTMF? > > Hi, > > I found some open source DTMF code at > > http://www.soft-switch.org/spandsp-modules.html > > Does anybody has access to nice DTMF sample files such as those > describe in > > http://www.soft-switch.org/spandsp_faq/ar01s13.html ? > > Christian > > --------------------------------------------------------------- > > Dr.-Ing. Christian Hoene > > Interactive Communication Systems (ICS), University of Tübingen > > Sand 13, 72076 Tübingen, Germany, Phone +49 7071 2970532 > http://www.net.uni-tuebingen.de/ > > *From:* Michael Knappe [mailto:mknappe@juniper.net] > *Sent:* Friday, March 26, 2010 11:38 PM > *To:* stephen.botzko@gmail.com; hoene@uni-tuebingen.de > *Cc:* codec@ietf.org > *Subject:* Re: [codec] #5: Mention DTMF in requirements > > I would agree with 'should'. Lot's of dtmf out there still, but also > out of band options (rfc 2833 / 4733) that make in-band carriage less > a concern for SIP telephony applications. > > Mik > > ------------------------------------------------------------------------ > > *From*: codec-bounces@ietf.org <codec-bounces@ietf.org> > *To*: Christian Hoene <hoene@uni-tuebingen.de> > *Cc*: codec@ietf.org <codec@ietf.org> > *Sent*: Fri Mar 26 18:10:31 2010 > *Subject*: Re: [codec] #5: Mention DTMF in requirements > > Perhaps analog DTMF carriage is a SHOULD? > > I agree that out-of-band is preferable, however, there still are > scenarios where coded DTMF tones will be sent. It would be nice > (though IMHO not essential) for this carriage to work. > > Stephen Botzko > > On Fri, Mar 26, 2010 at 3:04 PM, Christian Hoene > <hoene@uni-tuebingen.de <mailto:hoene@uni-tuebingen.de>> wrote: > > Hi, > > > > If the point of this issue to allow this codec to be used to > successfully > > transit an IP network between two TDM networks, > > which is not the primary use-case. > > > > I'd suggest that out-of- > > band tone transport is far preferable to trying to ensure that the codec > > will carry the tones adequately to allow them to be detected after > > regeneration. > > I totally agree. Out-of-band is much better than inband. > > Sorry for my radical view but I believe that analog DTMF is an old and > obsolete technology not worth considering anymore. > > Christian > >
- [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