RE: [Sip] SIP INFO & DTMF

"Chris Boulton" <cboulton@ubiquity.net> Wed, 09 February 2005 09:16 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 EAA11814 for <sip-web-archive@ietf.org>; Wed, 9 Feb 2005 04:16:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyoGx-00023Z-56 for sip-web-archive@ietf.org; Wed, 09 Feb 2005 04:36:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cynut-00024k-Sq; Wed, 09 Feb 2005 04:13:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cyntb-0001dv-AD for sip@megatron.ietf.org; Wed, 09 Feb 2005 04:12:27 -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 EAA11658 for <sip@ietf.org>; Wed, 9 Feb 2005 04:12:25 -0500 (EST)
Received: from cluster-b.mailcontrol.com ([217.68.146.190] helo=rly13b.srv.mailcontrol.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyoDJ-0001x9-HM for sip@ietf.org; Wed, 09 Feb 2005 04:32:53 -0500
Received: from GBNEWP0758M.eu.ubiquity.net ([62.172.205.164]) by rly13b.srv.mailcontrol.com (MailControl) with ESMTP id j199BiJ8004367; Wed, 9 Feb 2005 09:11:44 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sip] SIP INFO & DTMF
Date: Wed, 09 Feb 2005 09:10:38 -0000
Message-ID: <45730E094814E44488F789C1CDED27AE02BDFA47@gbnewp0758m.eu.ubiquity.net>
Thread-Topic: [Sip] SIP INFO & DTMF
Thread-Index: AcUOfeFWT2fImuxrREKyZSxPpCQghwACPTzw
From: Chris Boulton <cboulton@ubiquity.net>
To: Jan.Van_Opstal@alcatel.be, sip@ietf.org
X-Scanned-By: MailControl A-05-00-12 (www.mailcontrol.com)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 4c358d334afcd91b425d436ca5722f22
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============0446480794=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 441f623df000f14368137198649cb083

Take a look at the application interaction work:-

 

http://www.ietf.org/internet-drafts/draft-ietf-sipping-app-interaction-framework-03.txt

 

in association with the 'Key Pad Markup Language':-

 

http://www.ietf.org/internet-drafts/draft-ietf-sipping-kpml-07.txt

 

HTH,

 

Chris.

 

 

 

-----Original Message-----
From: Jan.Van_Opstal@alcatel.be [mailto:Jan.Van_Opstal@alcatel.be] 
Sent: 08 February 2005 08:15
To: sip@ietf.org
Subject: [Sip] SIP INFO & DTMF

 

Hi all,

I am currently confused how DTMF digits can be carried via the 
signalling path using SIP. If I am not mistaking, then a SIP INFO 
message should be used, but the confusion that I have is how should 
the content look like ?

There are some drafts, namely:

 -  draft-choudhuri-sip-info-digit-00.txt expired October 2000
 - draft-mahy-sipping-signaled-digits-00.txt expired May 2002

but as you can see, all expired.

Some think RFC2833 should be used withing a SIP message.  But 
it seems rather unlogical to use a sip info message to carry digits as 
explained in rfc2833 which targets rtp packets ... ?

I have checked the implementation of some MGW manufacturers:
Cisco, Snom and AudioCodes all use draft mahy-sipping-signaled-digits-00.txt,
but is this the way to go ? Or is there maybe a new draft or standard
that tell us what to use ?

Thanks in advance,

    Van Opstal Jan
    R&D Alcatel Antwerp, Belgium

Note: 
1) an example of a SIP INFO message using RFC2833:

INFO sip:192.168.50.7:5060 SIP/2.0
From: <sip:496420033@192.168.50.5;user=phone> <mailto:sip:496420033@192.168.50.5;user=phone> ;tag=0082-00000002-0021
To: <sip:025552024@192.168.50.5;user=phone> <mailto:sip:025552024@192.168.50.5;user=phone> ;tag=0082-000000dd-05d1i0
Call-ID: 0082-00000002-00214204b9f1-167e-433ca000@sipua
CSeq: 4 INFO
Max-Forwards: 29
Contact: "sipua" <sip:192.168.50.6:5060>
Content-Type: audio/telephone-event
Content-Length: 4

,2,100

(the body part is not really correct: should be extracted as
explained in RFC2833)

2) an example of a SIP INFO msg using draft mahy-sipping-signaled-digits-00.txt:

INFO sip:2143302100@172.17.2.33 SIP/2.0 
Via: SIP/2.0/UDP 172.80.2.100:5060 
From: <sip:9724401003@172.80.2.100> <mailto:sip:9724401003@172.80.2.100> ;tag=43 
To: <sip:2143302100@172.17.2.33> <mailto:sip:2143302100@172.17.2.33> ;tag=9753.0207 
Call-ID: 984072_15401962@172.80.2.100 
CSeq: 25634 INFO 
Content-Length: 26 
Content-Type: application/dtmf-relay 

Signal= 7 
Duration= 300 



This email and any attached files are confidential and copyright protected.  If you are not the addressee, any dissemination, distribution or copying of this communication is strictly prohibited.  Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding.
_______________________________________________
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