[Sipping] Question on draft-vandyke-mscml-06

"Song, Youngsun" <ysong@telcordia.com> Tue, 28 February 2006 01:06 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDtJy-0001w2-8g; Mon, 27 Feb 2006 20:06:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDtJw-0001vu-MA for sipping@ietf.org; Mon, 27 Feb 2006 20:06:32 -0500
Received: from dnsmx2pya.telcordia.com ([128.96.20.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDtJv-0005UH-D2 for sipping@ietf.org; Mon, 27 Feb 2006 20:06:32 -0500
Received: from rrc-dte-ieg01.cc.telcordia.com (rrc-dte-ieg01.cc.telcordia.com [128.96.20.22]) by dnsmx2pya.telcordia.com (8.11.7+Sun/8.9.3) with SMTP id k1S16LJ04808; Mon, 27 Feb 2006 20:06:25 -0500 (EST)
Received: from rrc-dte-exbh01.dte.telcordia.com ([128.96.150.31]) by rrc-dte-ieg01.cc.telcordia.com (SMSSMTP 4.1.9.35) with SMTP id M2006022720061616845 ; Mon, 27 Feb 2006 20:06:16 -0500
Received: from rrc-dte-exs02.dte.telcordia.com ([128.96.109.15]) by rrc-dte-exbh01.dte.telcordia.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 27 Feb 2006 20:06:16 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Feb 2006 20:06:16 -0500
Message-ID: <5D21DF1BB43D0C4F8473E6202EF99757058FC5D2@rrc-dte-exs02.dte.telcordia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Question on draft-vandyke-mscml-06
Thread-Index: AcQiA97c3ul6E0g3QDKE6JljdIAGT4Qz82xg
From: "Song, Youngsun" <ysong@telcordia.com>
To: sipping@ietf.org
X-OriginalArrivalTime: 28 Feb 2006 01:06:16.0584 (UTC) FILETIME=[2D195080:01C63C03]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: Andy Spitzer <woof@snowshore.com>
Subject: [Sipping] Question on draft-vandyke-mscml-06
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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

Hi,

On the draft-vandyke-mscml-06, I have a question on which SIP messages
can carry a MSCML payload for IVR commands.

Section 5.2 has the following text:

   The application server can include any MSCML command in the initial
   INVITE, with the exception of asynchronous commands, such as <play>
   or <record>.  The application server must issue asynchronous commands
   separately (e.g., in INFO messages) to avoid ambiguous responses.

Section 6, IVR, has the following text:

   One may carry the request payload for IVR in either the initial SIP
   INVITE or INFO requests.

Based on the above, it is not clear whether an initial INVITE can carry
a MSCML request for an IVR command such as <play>.

For example, is the following flow valid?

App Server ----INVITE (IVR service, MSCML request for <play>, SDP of
caller)---> Media Server
App Server <----200 OK (SDP of Media Server)---- Media Server
App Server ---- ACK ----> Media Server
Announcement is completed.
App Server <---- INFO (MSCML Response for <play>)---- Media Server
App Server ---- 200 OK ----> Media Server

Thanks for your help in advance,
YoungSun


_______________________________________________
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