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

"Raymond (Juin-Hwey) Chen" <rchen@broadcom.com> Fri, 02 April 2010 19:26 UTC

Return-Path: <rchen@broadcom.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 3AE333A6B6B for <codec@core3.amsl.com>; Fri, 2 Apr 2010 12:26:52 -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 DWLYe4nDa3BL for <codec@core3.amsl.com>; Fri, 2 Apr 2010 12:26:50 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by core3.amsl.com (Postfix) with ESMTP id 7F57A3A6B0D for <codec@ietf.org>; Fri, 2 Apr 2010 11:53:44 -0700 (PDT)
Received: from [10.9.200.133] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Fri, 02 Apr 2010 11:54:08 -0700
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Fri, 2 Apr 2010 11:55:33 -0700
From: "Raymond (Juin-Hwey) Chen" <rchen@broadcom.com>
To: Brian West <brian@freeswitch.org>, stephen botzko <stephen.botzko@gmail.com>
Date: Fri, 02 Apr 2010 11:54:00 -0700
Thread-Topic: [codec] #5: Mention DTMF in requirements
Thread-Index: AcrSbkLl/+OtG4IbRliwMoqBvakvvgAIBaGQ
Message-ID: <CB68DF4CFBEF4942881AD37AE1A7E8C74AB3B86D78@IRVEXCHCCR01.corp.ad.broadcom.com>
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> <0BD7AE28-298A-4586-9FB4-33925A8F8B8C@freeswitch.org>
In-Reply-To: <0BD7AE28-298A-4586-9FB4-33925A8F8B8C@freeswitch.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-cr-hashedpuzzle: CYZN C38P E3kT GTRY Lqae MMLu RpaN TKzq Te1B UAdf XYlA Xew6 Xk7D Y7kt bYj6 fjTJ; 3; YgByAGkAYQBuAEAAZgByAGUAZQBzAHcAaQB0AGMAaAAuAG8AcgBnADsAYwBvAGQAZQBjAEAAaQBlAHQAZgAuAG8AcgBnADsAcwB0AGUAcABoAGUAbgAuAGIAbwB0AHoAawBvAEAAZwBtAGEAaQBsAC4AYwBvAG0A; Sosha1_v1; 7; {F5EDFD7D-EBF9-4E12-906E-545B904C48D2}; cgBjAGgAZQBuAEAAYgByAG8AYQBkAGMAbwBtAC4AYwBvAG0A; Fri, 02 Apr 2010 18:54:00 GMT; UgBFADoAIABbAGMAbwBkAGUAYwBdACAAIwA1ADoAIABNAGUAbgB0AGkAbwBuACAARABUAE0ARgAgAGkAbgAgAHIAZQBxAHUAaQByAGUAbQBlAG4AdABzAA==
x-cr-puzzleid: {F5EDFD7D-EBF9-4E12-906E-545B904C48D2}
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 67A8E2DA38O161155616-01-01
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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: Fri, 02 Apr 2010 19:26:52 -0000

(Responding to an earlier email on this topic...)

I think the issue here is not for a codec to detect DTMF, but for a codec to encode and decode the DTMF waveform with sufficient fidelity so it will not cause DTMF detection problems later in a DTMF detector.  

Although most codecs do not explicitly make use of DTMF properties to improve their coding fidelity with DTMF waveforms, a codec developer can indeed test a codec by passing DTMF tones through the codec followed by a DTMF detector and try to tune or otherwise improve the codec so that it minimizes the DTMF detection error rate as seen by the DTMF detector.  In fact, this is exactly what we have done when we developed the BV16 codec, and as a result of such testing and tuning, we were indeed able to modify the BV16 codec algorithm to improve the DTMF detection error rate after DTMF tones were passed through BV16 and then detected by a commercial DTMF detector.  Such DTMF pass-through test results of BV16, G.711, G.728, G.729E, and G.729 are described in our BroadVoice16 paper in the Proceedings of the 40th Asilomar Conference on Signals, Systems and Computers, 2006, available at our BroadVoice website www.broadcom.com/broadvoice.  That's why I could answer with confidence the DTMF pass-through question raised right after my BroadVoice codec presentation at our IETF 77 codec WG meeting on March 22.

I think in those conditions where out-of-band DTMF signaling is not available or is not implemented properly, it is crucial for the codec to pass DTMF tones through without causing significant increase of the DMTF detection error rate in a DTMF detector downstream, otherwise you may not even be able to get the correct telephone number through, or a credit card number or key press responses to a voice response system (press 1 for this, press 2 for that,...) may not go through correctly. That's why we went through the trouble of testing BV16 with DTMF tones and modifying BV16 to minimize the DTMF detection error rate, and that's why I agree with Stephen's comments below.

Raymond

-----Original Message-----
From: codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] On Behalf Of Brian West
Sent: Friday, April 02, 2010 7:10 AM
To: stephen botzko
Cc: codec@ietf.org
Subject: Re: [codec] #5: Mention DTMF in requirements

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

_______________________________________________
codec mailing list
codec@ietf.org
https://www.ietf.org/mailman/listinfo/codec