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

Marc Petit-Huguenin <petithug@acm.org> Sun, 28 March 2010 18:22 UTC

Return-Path: <petithug@acm.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 B90573A68EE for <codec@core3.amsl.com>; Sun, 28 Mar 2010 11:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.206
X-Spam-Level:
X-Spam-Status: No, score=-100.206 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 Hlpi5l-lIM9c for <codec@core3.amsl.com>; Sun, 28 Mar 2010 11:22:56 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91]) by core3.amsl.com (Postfix) with ESMTP id 65C0E3A68F3 for <codec@ietf.org>; Sun, 28 Mar 2010 11:22:33 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001) id D301A6C984E2; Sun, 28 Mar 2010 18:22:59 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1]) by server.implementers.org (Postfix) with ESMTPA id 426536C984E4; Sun, 28 Mar 2010 18:22:52 +0000 (UTC)
Message-ID: <4BAF9E7B.1070708@acm.org>
Date: Sun, 28 Mar 2010 11:22:51 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100307 Iceowl/1.0b1 Icedove/3.0.3
MIME-Version: 1.0
To: stephen botzko <stephen.botzko@gmail.com>
References: <05542EC42316164383B5180707A489EE1D0AA5F54E@EMBX02-HQ.jnpr.net> <4BAF776D.20904@acm.org> <6e9223711003281100q7e1f7ac0pd548a2ab40e95ba4@mail.gmail.com>
In-Reply-To: <6e9223711003281100q7e1f7ac0pd548a2ab40e95ba4@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Sun, 28 Mar 2010 18:22:57 -0000

On 03/28/2010 11:00 AM, stephen botzko wrote:
> I would agree with this if I saw reasonable evidence that a
> preponderance of gateways and sending systems provide the signaling in
> these RFCs.
> 
> Since I am not sure that this is the case, I am unconvinced that we can
> totally remove the requirement.
> 
> I'd also say that an encoder that detects the DTMF tones and outputs the
> RFC 4733/34 events would fully meet the requirement.

As former CTO of a VoIP provider, I never saw a PSTN provider not supporting at
least RFC 2833 (even if one of them did not declare it in its SDP)

Perhaps the question can be asked at the next SIPit event.

> 
> Stephen Botzko
> 
> On Sun, Mar 28, 2010 at 11:36 AM, Marc Petit-Huguenin <petithug@acm.org
> <mailto:petithug@acm.org>> wrote:
> 
>     I disagree with the "SHOULD".  RFC 4733 and RFC 4734 takes care of
>     DTMF and much
>     more, so this must be an explicit non-goal.  This is an *Internet*
>     codec that we
>     are talking about so it should reuse as much as possible of the existing
>     Internet framework.
> 
>     And BTW, RFC 473[34] is not out of band, it's codec switching.  RFC
>     47[34] is an
>     audio codec, simply very good at compressing a very specific set of
>     frequencies/phases, and replacing everything else by silence.  RFC
>     4730 and RFC
>     2676 are out of band.
> 
>     On 03/26/2010 03:37 PM, Michael Knappe wrote:
>     >  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 <mailto:codec-bounces@ietf.org>
>     <codec-bounces@ietf.org <mailto:codec-bounces@ietf.org>>
>     > *To*: Christian Hoene <hoene@uni-tuebingen.de
>     <mailto:hoene@uni-tuebingen.de>>
>     > *Cc*: codec@ietf.org <mailto:codec@ietf.org> <codec@ietf.org
>     <mailto: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>
>     > <mailto: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
> 
> 
>     --
>     Marc Petit-Huguenin
>     Personal email: marc@petit-huguenin.org <mailto:marc@petit-huguenin.org>
>     Professional email: petithug@acm.org <mailto:petithug@acm.org>
>     Blog: http://blog.marc.petit-huguenin.org
> 
> 


-- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org