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

Steve Underwood <steveu@coppice.org> Fri, 02 April 2010 06:26 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 B81B43A688E for <codec@core3.amsl.com>; Thu, 1 Apr 2010 23:26:25 -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 IS9JOrj94cJg for <codec@core3.amsl.com>; Thu, 1 Apr 2010 23:26:25 -0700 (PDT)
Received: from cwb.pacific.net.hk (cwb.pacific.net.hk [202.14.67.92]) by core3.amsl.com (Postfix) with ESMTP id B9D8F3A680E for <codec@ietf.org>; Thu, 1 Apr 2010 23:26:24 -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 o326QvLC011573 for <codec@ietf.org>; Fri, 2 Apr 2010 14:26:57 +0800
Message-ID: <4BB58E31.2050809@coppice.org>
Date: Fri, 02 Apr 2010 14:26:57 +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> <4BAF776D.20904@acm.org> <6e9223711003281100q7e1f7ac0pd548a2ab40e95ba4@mail.gmail.com> <4BAF9E7B.1070708@acm.org>
In-Reply-To: <4BAF9E7B.1070708@acm.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 06:26:25 -0000

On 03/29/2010 02:22 AM, Marc Petit-Huguenin wrote:
> 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.
>    
Its true that RFC2833 is widely deployed. Its even true that many 
systems have updated to RFC4733. Sadly, its also true that there are 
still many quirky implementations widely deployed, and a lot of people 
still need to interwork with audio DTMF.

Steve