Re: [Sip] Media Server info notification
Rohan Mahy <rohan@cisco.com> Mon, 12 May 2003 23:22 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 TAA08393 for <sip-archive@odin.ietf.org>; Mon, 12 May 2003 19:22:15 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CMm0q10232 for sip-archive@odin.ietf.org; Mon, 12 May 2003 18:48:00 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CMlcB10213; Mon, 12 May 2003 18:47:38 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CMdYB09794 for <sip@optimus.ietf.org>; Mon, 12 May 2003 18:39:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08187 for <sip@ietf.org>; Mon, 12 May 2003 19:13:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FMVp-0005SO-00 for sip@ietf.org; Mon, 12 May 2003 19:15:17 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237]) by ietf-mx with esmtp (Exim 4.12) id 19FMVo-0005Rx-00 for sip@ietf.org; Mon, 12 May 2003 19:15:16 -0400
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h4CNFeND019249; Mon, 12 May 2003 16:15:42 -0700 (PDT)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR) with ESMTP id AHA31070; Mon, 12 May 2003 16:09:29 -0700 (PDT)
Date: Mon, 12 May 2003 16:15:52 -0700
Subject: Re: [Sip] Media Server info notification
Content-Type: text/plain; delsp="yes"; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Goix Walter <Walter.Goix@tilab.com>, sip-ietf <sip@ietf.org>
To: Cullen Jennings <fluffy@cisco.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <BAE14160.77EA%fluffy@cisco.com>
Message-Id: <AD268676-84CF-11D7-8E16-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
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
specifically: http://www.softarmor.com/sipping/drafts/draft-burger-sipping-kpml-01.txt http://www.softarmor.com/sipping/drafts/draft-culpepper-sipping-app- interact-reqs-03.txt http://www.softarmor.com/sipping/drafts/draft-jennings-sip-app-info- 00.txt http://www.softarmor.com/sipping/drafts/draft-rosenberg-sipping-app- interaction-framework-00.txt On Friday, May 9, 2003, at 11:28 AM, Cullen Jennings wrote: > > > Have a look at the app-interaction stuff and KPML. > > On 5/9/03 2:29 AM, "Goix Walter" <Walter.Goix@tilab.com> wrote: > >> Is there any recent standard work on the use of SIP by media >> servers/IVR to >> send out params/collect digits/... to some other SIP entity ? >> >> I know there are many proprietary implementations but I'm not aware >> about a >> common agreement that solves this issue. Any INFO/Info-Type or Event >> package >> solution? >> >> Any suggestion appreciated. >> Thanks in advance. >> Regards, >> >> Walter Goix >> >> ________________________ >> Laurent-Walter Goix >> Telecom Italia S.p.A. >> Telecom Italia Lab - StarSIP >> Services Innovation - Intelligent Services and Platforms (SI/P) >> Via Reiss Romoli 274 >> I-10148 Torino (Italy) >> Tel. +39 011 228 5046 >> Fax +39 011 228 5069 >> E-mail mailto:laurentwalter.goix@telecomitalia.it >> ________________________ >> Visit us @ http://starsip.telecomitalialab.com >> >> >> >> ==================================================================== >> CONFIDENTIALITY NOTICE >> This message and its attachments are addressed solely to the persons >> above and may contain confidential information. If you have received >> the message in error, be informed that any use of the content hereof >> is prohibited. Please return it immediately to the sender and delete >> the message. Should you have any questions, please contact us by >> replying to MailAdmin@tilab.com. Thank you >> ==================================================================== >> _______________________________________________ >> 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] Media Server info notification Goix Walter
- Re: [Sip] Media Server info notification Cullen Jennings
- Re: [Sip] Media Server info notification Rohan Mahy