IETF Logo Mail Archive

[Sip] Re: [Sip-implementors] (no subject)

Bert Culpepper <bertculpepper@netscape.net> Wed, 18 December 2002 00:27 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27631 for <sip-archive@odin.ietf.org>; Tue, 17 Dec 2002 19:27:26 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBI0U2U15681 for sip-archive@odin.ietf.org; Tue, 17 Dec 2002 19:30:02 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBI0MVv15365; Tue, 17 Dec 2002 19:22:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBI0F4v15176 for <sip@optimus.ietf.org>; Tue, 17 Dec 2002 19:15:04 -0500
Received: from imo-d09.mx.aol.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27215 for <sip@ietf.org>; Tue, 17 Dec 2002 19:11:57 -0500 (EST)
Received: from bertculpepper@netscape.net by imo-d09.mx.aol.com (mail_out_v34.13.) id r.1c.6807a0a (22680); Tue, 17 Dec 2002 19:14:51 -0500 (EST)
Received: from netscape.net (159.252.8.67.cfl.rr.com [67.8.252.159]) by air-in04.mx.aol.com (v89.21) with ESMTP id MAILININ41-1217191451; Tue, 17 Dec 2002 19:14:51 -0500
Message-ID: <3DFFBE79.2040706@netscape.net>
Date: Tue, 17 Dec 2002 19:16:57 -0500
From: Bert Culpepper <bertculpepper@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4.1) Gecko/20020314 Netscape6/6.2.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: sathish kumar <sathises@yahoo.com>
CC: sip@ietf.org, sip-implementors@cs.columbia.edu
References: <20021217101736.10903.qmail@web40702.mail.yahoo.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Mailer: Unknown (No Version)
Content-Transfer-Encoding: 7bit
Subject: [Sip] Re: [Sip-implementors] (no subject)
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: 7bit

Standardization of mechanisms on sending DTMF in INFO has not occurred. 
    For SIP, the use of DTMF is seen as a means for user interaction 
with network-based applications.  To this end, work is ongoing on to 
define a framework and mechanisms for users to interact with 
applications in SIP.  See the I-Ds below for how this is expected to be 
supported.

http://www.ietf.org/internet-drafts/draft-culpepper-sipping-app-interact-reqs-02.txt
http://www.jdrosen.net/papers/draft-rosenberg-sipping-app-interaction-framework-00.txt
http://www.ietf.org/internet-drafts/draft-burger-sipping-kpml-00.txt
http://www.ietf.org/internet-drafts/draft-jennings-sip-app-info-00.txt

Regards,
Bert

sathish kumar wrote:

> Hi,
> 
> Pertaining to the SIP INFO method defined in RFC 2976 used for sending 
> mid call signaling information.
> 
> After establishment of Voice path between two user agents i wish to send 
> the DTMF digits from UAC to UAS.
> 
> 1. Can anyone tell me the format of sending the information (Header, 
> Message Body if any).
> 
> thanx and regards
> 
> sathises.
> 
> 
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Yahoo! Mail Plus 
> <http://rd.yahoo.com/mail/mailsig/*http://mailplus.yahoo.com> - 
> Powerful. Affordable. Sign up now 
> <http://rd.yahoo.com/mail/mailsig/*http://mailplus.yahoo.com>


_______________________________________________
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

v2.23.0 | Report a Bug | By Email