Re: [Sip-implementors] [Sipping] DTMF digits through RTP or INFO

Gaurav Kulshreshtha <gaurav@sunrocket.com> Thu, 11 May 2006 14:55 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeCZV-00033T-3V; Thu, 11 May 2006 10:55:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeCZT-00033O-GG for sipping@ietf.org; Thu, 11 May 2006 10:55:19 -0400
Received: from mercury.sunrocket.com ([208.50.38.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FeCZT-0005Uc-8U for sipping@ietf.org; Thu, 11 May 2006 10:55:19 -0400
Received: (qmail 9924 invoked from network); 11 May 2006 14:55:19 -0000
Received: from ip68-100-79-176.dc.dc.cox.net (HELO [192.168.0.2]) (gkulshreshtha@[68.100.79.176]) (envelope-sender <gaurav@sunrocket.com>) by mercury.sunrocket.com (qmail-ldap-1.03) with SMTP for <sipping@ietf.org>; 11 May 2006 14:55:19 -0000
Message-ID: <44635052.2070906@sunrocket.com>
Date: Thu, 11 May 2006 10:55:14 -0400
From: Gaurav Kulshreshtha <gaurav@sunrocket.com>
Organization: SunRocket Inc.
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
Subject: Re: [Sip-implementors] [Sipping] DTMF digits through RTP or INFO
References: <28F05913385EAC43AF019413F674A0170DE0C6BE@OCCLUST04EVS1.ugd.att.com> <44634A5B.9070909@cisco.com>
In-Reply-To: <44634A5B.9070909@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: sip-implementors@cs.columbia.edu, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gaurav@sunrocket.com
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Prince,
 All the VoIP equipments support RFC 2833. However for backward 
compatibilty with existing equipments they also support DTMF. So you end 
up with a configurable option on most devices.
 
Cheers
Gaurav Kulshreshtha
Jonathan Rosenberg wrote:
> There is also RFC 2833, which carries them inband. The app interaction 
> framework:
>
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-app-interaction-framework-05.txt 
>
>
> describes the relative roles of the two.
>
> Thanks,
> Jonathan R.
>
> Dolly, Martin C, ALABS wrote:
>
>> Prince,
>>  
>> KPML, http://tools.ietf.org/wg/sipping/draft-ietf-sipping-kpml, which is
>> in the RFC ed. queue, waiting for the authors final update (oh)
>>  
>> Martin
>>
>> ________________________________
>>
>> From: Prince Arimboor Philip
>> [mailto:prince.philip@flextronicssoftware.com] Sent: Thursday, May 
>> 11, 2006 2:50 AM
>> To: sip-implementors@cs.columbia.edu; sipping@ietf.org
>> Subject: [Sipping] DTMF digits through RTP or INFO
>>
>>
>>
>> Hi all,
>> what is the recommended way of communicating the DTMF digits?
>> Also please tell me which is the mechanism used by most of the SIP end
>> points to communicate the DTMF digits?
>> thanks in advance, Prince
>>
>>
>> ***********************  FSS- Confidential   ***********************
>> _______________________________________________
>> Sip-implementors mailing list
>> Sip-implementors@cs.columbia.edu
>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>>
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP