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

James Rafferty <James.Rafferty@dialogic.com> Fri, 02 April 2010 13:58 UTC

Return-Path: <James.Rafferty@dialogic.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 2F1FE3A63EC for <codec@core3.amsl.com>; Fri, 2 Apr 2010 06:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.737
X-Spam-Level:
X-Spam-Status: No, score=0.737 tagged_above=-999 required=5 tests=[AWL=-0.395, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 WnIQpiOHSl48 for <codec@core3.amsl.com>; Fri, 2 Apr 2010 06:58:33 -0700 (PDT)
Received: from outbound.dialogic.com (outbound.dialogic.com [65.220.90.252]) by core3.amsl.com (Postfix) with ESMTP id 721C83A62C1 for <codec@ietf.org>; Fri, 2 Apr 2010 06:58:33 -0700 (PDT)
Received: from MBX.dialogic.com ([fe80::d09:39e:8fa1:c2a3]) by pysxht02.dialogic.com ([::1]) with mapi; Fri, 2 Apr 2010 09:59:08 -0400
From: James Rafferty <James.Rafferty@dialogic.com>
To: stephen botzko <stephen.botzko@gmail.com>
Date: Fri, 02 Apr 2010 09:59:06 -0400
Thread-Topic: [codec] #5: Mention DTMF in requirements
Thread-Index: AcrSa/FKN5fRPsMJST6b6mYl8f1ciAAAHXDw
Message-ID: <617DF0128820F9458AC39149A627EE6C01A2A2115B@MBX.dialogic.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>
In-Reply-To: <m2o6e9223711004020653jb5d773eejdea1ec98367c7ff0@mail.gmail.com>
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_617DF0128820F9458AC39149A627EE6C01A2A2115BMBXdialogicco_"
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, 02 Apr 2010 13:58:39 -0000

Stephen,

I'd suggest SHOULD.  Using RFC 2833 / RFC 4733 is preferred to ensure passage, but if the DTMF can be passed in native form and still be detectable, that would be a big plus.

James
From: stephen botzko [mailto:stephen.botzko@gmail.com]
Sent: Friday, April 02, 2010 9:54 AM
To: James Rafferty
Cc: Steve Underwood; codec@ietf.org
Subject: Re: [codec] #5: Mention DTMF in requirements

Are you two suggesting that in-band DTMF is a MUST?  Or alternatively a SHOULD?

Stephen Botzko
On Fri, Apr 2, 2010 at 9:48 AM, James Rafferty <James.Rafferty@dialogic.com<mailto:James.Rafferty@dialogic.com>> wrote:
I'd agree with Steve that are still many deployments which do not use RFC 2833 or RFC 4733. In our gateways, we've had to support interworking variations of tone support such as INFO and in-band, in addition to the RFC 2833 / RFC 4733.

James
-----Original Message-----
From: codec-bounces@ietf.org<mailto:codec-bounces@ietf.org> [mailto:codec-bounces@ietf.org<mailto:codec-bounces@ietf.org>] On Behalf Of Steve Underwood
Sent: Friday, April 02, 2010 2:27 AM
To: codec@ietf.org<mailto:codec@ietf.org>
Subject: Re: [codec] #5: Mention DTMF in requirements
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

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