Re: [Sip] SIP DTMF
Bert Culpepper <bertculpepper@netscape.net> Mon, 19 January 2004 16:13 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23906 for <sip-archive@odin.ietf.org>; Mon, 19 Jan 2004 11:13:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aic13-0002Fh-LT for sip-archive@odin.ietf.org; Mon, 19 Jan 2004 11:12:42 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0JGCfSi008651 for sip-archive@odin.ietf.org; Mon, 19 Jan 2004 11:12:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AibzT-0002BE-AD; Mon, 19 Jan 2004 11:11:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AibzF-0002AU-9M for sip@optimus.ietf.org; Mon, 19 Jan 2004 11:10:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23596 for <sip@ietf.org>; Mon, 19 Jan 2004 11:10:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aibz2-0006Wf-00 for sip@ietf.org; Mon, 19 Jan 2004 11:10:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aibv4-0006JV-00 for sip@ietf.org; Mon, 19 Jan 2004 11:06:31 -0500
Received: from imo-d02.mx.aol.com ([205.188.157.34]) by ietf-mx with esmtp (Exim 4.12) id 1AibtR-0006B7-00 for sip@ietf.org; Mon, 19 Jan 2004 11:04:49 -0500
Received: from bertculpepper@netscape.net by imo-d02.mx.aol.com (mail_out_v36_r4.12.) id c.eb.c242211 (22683); Mon, 19 Jan 2004 11:03:35 -0500 (EST)
Received: from netscape.net (87.67.33.65.cfl.rr.com [65.33.67.87]) by air-in04.mx.aol.com (v97.18) with ESMTP id MAILININ44-589b400bffd616e; Mon, 19 Jan 2004 11:03:35 -0500
Message-ID: <400BFFFC.6030907@netscape.net>
Date: Mon, 19 Jan 2004 11:04:12 -0500
From: Bert Culpepper <bertculpepper@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
CC: Paul Long <plong@packetizer.com>, sip@ietf.org
Subject: Re: [Sip] SIP DTMF
References: <BC30A7A1.2D252%fluffy@cisco.com>
In-Reply-To: <BC30A7A1.2D252%fluffy@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
X-AOL-IP: 65.33.67.87
X-Mailer: Unknown (No Version)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA23597
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
The SIPPING work group web page on the IETF site has http://www.ietf.org/internet-drafts/draft-ietf-sipping-kpml-01.txt as the current draft. This version has significant differences than the one quoted below, one in particular is the use of SUBSCRIBE/NOTIFY for requesting and reporting key presses. Best regards, Bert Cullen Jennings wrote: > The draft is > http://www.ietf.org/internet-drafts/draft-burger-sipping-kpml-02.txt > > 2833 is the preferred method, but if an off media axis device wished to get > notification about key presses, it could. How these all relate is covered in > > http://www.softarmor.com/wgdb/docs/ > draft-ietf-sipping-app-interaction-framework-00.txt > > Cullen > > > On 1/15/04 11:21 AM, "Paul Long" <plong@packetizer.com> wrote: > > >>Sreeram, >> >>I can't find a "kpxml" draft on the IETF site or via Google--anywhere. >>Can you provide a link to it? >> >>Also, from my experience, the preferred method of DTMF carriage is RFC >>2833, followed by in-band audio, and then various proprietary >>INFO-method schemes. What is the standing of RFC 2833 vis-à-vis "kpxml?" >> >>Paul >> >>-----Original Message----- >>From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of >>sreeram.kanumuri@wipro.com >>Sent: Tuesday, January 13, 2004 9:06 PM >>To: xyxie@udtech.com.cn; sip@ietf.org >>Cc: sipping@ietf.org >>Subject: RE: [Sip] SIP DTMF >> >>Wendy, >> >>There was a discussion in the list some time back and it was decided >>that SIP-INFO method should not be used to >>Send the DTMF info. >> >>It was proposed that it is better to you kpxml for sending DTMF tones. >> >>Please look in to the SIP-Kpxml draft for sending DTMF tomes in-midcall >>processing and all.... >> >> >>Regards, >>Sreeram >> >>===================================================== >>Sreeram Kanumuri Plot No 72, Keonics Electronics City >> Hosur Main Road >>Wipro Technologies Bangalore -29 INDIA >>sreeram.kanumuri@wipro.com Phone: 8520408 Ex:3208 >>skanumury@yahoo.com ESN : >>www.wipro.com Mobile: >>====================================================== >> >> >>-----Original Message----- >>From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of wendy >>Sent: Wednesday, January 14, 2004 8:08 AM >>To: sip@ietf.org >>Cc: sipping@ietf.org >>Subject: [Sip] SIP DTMF >> >> >>Hello all, >> >>Who can tell me whether there is a RFC or I-D on DTMF in SIP which is >>still not expired? I remember someone proposed using SIP INFO method for >>DTMF one or two years ago. Is the DTMF relay implemented only by RTP >>now? >> >> >>Regards, >>Wendy >> >> >>_______________________________________________ >>Sip mailing list https://www1.ietf.org/mailman/listinfo/sip >>This list is for NEW development of the core SIP Protocol >>Use sip-implementors@cs.columbia.edu for questions on current sip >>Use sipping@ietf.org for new developments on the application of sip >> > > > > _______________________________________________ > Sip mailing list https://www1.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol > Use sip-implementors@cs.columbia.edu for questions on current sip > Use sipping@ietf.org for new developments on the application of sip > _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] SIP DTMF wendy
- RE: [Sip] SIP DTMF sreeram.kanumuri
- RE: [Sip] SIP DTMF Paul Long
- Re: [Sip] SIP DTMF Cullen Jennings
- Re: [Sip] SIP DTMF Bert Culpepper