IETF Logo Mail Archive

Re: [codec] #5: Mention DTMF in requirements

Brian West <brian@freeswitch.org> Fri, 02 April 2010 14:09 UTC

Return-Path: <brian@freeswitch.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 83F683A67AE for <codec@core3.amsl.com>; Fri, 2 Apr 2010 07:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, 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 BfGxUwAZHZRj for <codec@core3.amsl.com>; Fri, 2 Apr 2010 07:09:44 -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 591F23A688F for <codec@ietf.org>; Fri, 2 Apr 2010 07:09:43 -0700 (PDT)
Received: by pwj2 with SMTP id 2so356389pwj.31 for <codec@ietf.org>; Fri, 02 Apr 2010 07:10:14 -0700 (PDT)
Received: by 10.141.89.14 with SMTP id r14mr1552269rvl.33.1270217414533; Fri, 02 Apr 2010 07:10:14 -0700 (PDT)
Received: from [192.168.1.221] (adsl-70-234-189-29.dsl.tul2ok.sbcglobal.net [70.234.189.29]) by mx.google.com with ESMTPS id 22sm8245412iwn.0.2010.04.02.07.10.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Apr 2010 07:10:13 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: Brian West <brian@freeswitch.org>
In-Reply-To: <q2j6e9223711004020701u5151687dx7c5be128e3517560@mail.gmail.com>
Date: Fri, 02 Apr 2010 09:10:11 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0BD7AE28-298A-4586-9FB4-33925A8F8B8C@freeswitch.org>
References: <05542EC42316164383B5180707A489EE1D0AA5F54E@EMBX02-HQ.jnpr.net> <4BAF776D.20904@acm.org> <6e9223711003281100q7e1f7ac0pd548a2ab40e95ba4@mail.gmail.com> <4BAF9E7B.1070708@acm.org> <4BB58E31.2050809@coppice.org> <617DF0128820F9458AC39149A627EE6C01A2A21146@MBX.dialogic.com> <m2o6e9223711004020653jb5d773eejdea1ec98367c7ff0@mail.gmail.com> <4BB5F7B6.1080808@stpeter.im> <q2j6e9223711004020701u5151687dx7c5be128e3517560@mail.gmail.com>
To: stephen botzko <stephen.botzko@gmail.com>
X-Mailer: Apple Mail (2.1078)
Cc: 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: Fri, 02 Apr 2010 14:09:45 -0000

But Codecs themselves do not detect DTMF.  Thats the job of the DTMF detector.  NOT the codec.  In all my work with codecs I have not once seen one that knows anything about DTMF.  And if the codec is too lossy inband is out of the question.

/b

On Apr 2, 2010, at 9:01 AM, stephen botzko wrote:

> I heard no decision as to DTMF tone encoding. 
> 
> As far as I am concerned, the question of whether the codec MUST encode DTMF tones accurately enough to be detected at the decoder output (or SHOULD or non-requirement) is still open.
> 
> That question clearly is in-scope, and has nothing to do with signaling.
> 
> Stephen Botzko

v2.23.0 | Report a Bug | By Email