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

Michael Knappe <mknappe@juniper.net> Fri, 26 March 2010 22:39 UTC

Return-Path: <mknappe@juniper.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 0AE9C3A67EF for <codec@core3.amsl.com>; Fri, 26 Mar 2010 15:39:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.033
X-Spam-Level:
X-Spam-Status: No, score=-5.033 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, MIME_BAD_LINEBREAK=0.5, 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 wRsRYUhqG-FG for <codec@core3.amsl.com>; Fri, 26 Mar 2010 15:39:19 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by core3.amsl.com (Postfix) with ESMTP id A6A9B3A67D6 for <codec@ietf.org>; Fri, 26 Mar 2010 15:39:19 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKS603qBBXecm9TbfjjfwFk1ZluWTozbod@postini.com; Fri, 26 Mar 2010 15:39:44 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Fri, 26 Mar 2010 15:37:53 -0700
From: Michael Knappe <mknappe@juniper.net>
To: "stephen.botzko@gmail.com" <stephen.botzko@gmail.com>, "hoene@uni-tuebingen.de" <hoene@uni-tuebingen.de>
Date: Fri, 26 Mar 2010 15:37:53 -0700
Thread-Topic: [codec] #5: Mention DTMF in requirements
Thread-Index: AcrNMbCUpO08LZM6R4mGjyonveIq9AAA0aH4
Message-ID: <05542EC42316164383B5180707A489EE1D0AA5F54E@EMBX02-HQ.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_05542EC42316164383B5180707A489EE1D0AA5F54EEMBX02HQjnprn_"
MIME-Version: 1.0
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, 26 Mar 2010 22:39:21 -0000

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 mailing list
codec@ietf.org<mailto:codec@ietf.org>
https://www.ietf.org/mailman/listinfo/codec