Re: [Sipforum-discussion] SIP INFO and RFC 2833 support?

Jonathan Rosenberg <jdrosen@cisco.com> Tue, 21 December 2004 15:24 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18973; Tue, 21 Dec 2004 10:24:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cgm1i-0006S5-Es; Tue, 21 Dec 2004 10:34:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cglmp-0006VR-NU; Tue, 21 Dec 2004 10:18:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cglgh-0004UL-AZ for ietf@megatron.ietf.org; Tue, 21 Dec 2004 10:12:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17788 for <ietf@ietf.org>; Tue, 21 Dec 2004 10:12:33 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cglq8-0006Bd-11 for ietf@ietf.org; Tue, 21 Dec 2004 10:22:23 -0500
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-2.cisco.com with ESMTP; 21 Dec 2004 07:17:12 -0800
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com [171.71.163.28]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iBLFBvHn029028; Tue, 21 Dec 2004 07:11:57 -0800 (PST)
Received: from [10.252.132.187] (che-vpn-cluster-2-3.cisco.com [10.86.242.3]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AGL94628; Tue, 21 Dec 2004 07:11:55 -0800 (PST)
Message-ID: <41C80DB5.4070103@cisco.com>
Date: Tue, 21 Dec 2004 06:49:09 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vijay Shanmugam <Vijay.Shanmugam@caritor.com>
References: <OFFE61A9B0.EC0C5CEA-ON65256F71.0010D54B-65256F71.0010D552@caritor.com>
In-Reply-To: <OFFE61A9B0.EC0C5CEA-ON65256F71.0010D54B-65256F71.0010D552@caritor.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
X-Spam-Score: 0.7 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id KAA17788
Cc: sipforum-discussion@lists.su.se, Madabhushi Pramod <madabhushi_p@yahoo.com>, implementors-requesto@cs.columbia.edu, ietf@ietf.org
Subject: Re: [Sipforum-discussion] SIP INFO and RFC 2833 support?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: quoted-printable

Let me try to clarify here.

The IETF has two standards-track techniques for DTMF carriage. These are:

1. RFC 2833
2. KPML and the app interaction framework (draft-ietf-sipping-kpml, 
draft-ietf-sipping-app-interaction-framework). This uses a 
subscribe/notify model to carry user input.

The framework gives some guidance on the usage of RFC2833 vs. KPML.

The usage of INFO for carrying DTMF is not based on any IETF standards. 
It has numerous known problems. There are implementations doing it, many 
in different ways, as they pre-date the standards track KPML/app 
interaction work.

-Jonathan R.


Vijay Shanmugam wrote:
> Hi,
>  
> /1) What is the latest draft on SIP INFO?
> /The RFC we are following is 2976.
>  
> But recently I had noticed a draft saying SIP INFO harmful.
> http://www.softarmor.com/wgdb/docs/draft-rosenberg-sip-info-harmful-00.txt
>  
> 
> /2) Is it mandatory to signal DTMF via SIP INFO?
> /It is not mandatory to use SIP INFO for DTMF. For normal calls, just an 
> inband RFC 2833 DTMF implementation is enough.
>  
> But if you are willing to provide 3rd party call control service, 
> where you do not have direct control over media and you just have 
> control over signaling, implementation of out-of-band DTMF signaling 
> using SIP INFO becomes mandatory. 
>  
> Thanks & regards,
> Vijay Shanmugam
> 2476, Swedesford Road,
> Malvern, PA 19355.
> Ph: 610 648 4547
> 
> -----sipforum-discussion-admin@lists.su.se wrote: -----
> 
> To: implementors-requesto@cs.columbia.edu, 
> sipforum-discussion@lists.su.se, ietf@ietf.org
> From: Madabhushi Pramod <madabhushi_p@yahoo.com>
> Sent by: sipforum-discussion-admin@lists.su.se
> Date: 12/20/2004 08:45PM
> Subject: [Sipforum-discussion] SIP INFO and RFC 2833 support?
> 
> Hi all,
> 
> I have couple of questions:
> 
> 1) What is the latest draft on SIP INFO?
> 2) Is it mandatory to signal DTMF via SIP INFO?
> 3) Do SIP vendors support RFC 2833 for G711 along with
> G729 also? I mean is it common for vendors to support
> RFC 2833 for G711?
> 
> Any help is appreciated.
> 
> Thanks,
> Pramod Madabhushi
> 
> =====
> Pramod Madabhushi
> email: mpramod@hotmail.com,
>       madabhushi_p@yahoo.com
> Phone:001-408-204-8077
> 
> 
> 
> __________________________________
> Do you Yahoo!?
> All your favorites on one personal page – Try My Yahoo!
> http://my.yahoo.com
> ------
> To unsubscribe from the Sipforum-discussion mailing list visit 
> https://mbox.su.se/mailman/listinfo/sipforum-discussion
> ------ To unsubscribe from the Sipforum-discussion mailing list visit 
> https://mbox.su.se/mailman/listinfo/sipforum-discussion

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf