Subject: Where to put CCXML and VoiceXML (was RE: [mediactrl] SIP Control Framework and IVR Package)

From: "Burger, Eric" <[email-masked]>
Date: Tue, 14 Feb 2006 18:23:22 GMT

CCXML positively belongs on the application server.
VoiceXML positively belongs in the media server.

If you are an IMS-head, then I can see VoiceXML running in the MRFC rather than the MRFP.  If all you are building is a box of DSP's at the end of a wire, or the software version of such, then you are building an MRFP.  If you are building a stand-alone MRFP, then H.248 is done.  If you are building an integrated MRF (which is what most everyone does), then VoiceXML MUST run on the MRF.  Why?  Because you cannot put the MRFC functionality in the AS.  That clearly does not work, because you cannot share resource management from the AS.  That MUST be below the S-CSCF. 

________________________________________
From: [email-masked] [mailto:[email-masked]] On Behalf Of Shtirmer, Gene
Sent: Friday, February 03, 2006 5:29 PM
To: Chris Boulton; [email-masked]
Subject: RE: [mediactrl] SIP Control Framework and IVR Package

We have reviewed both drafts.  We have no objections to the SIP Framework for establishing and conducting control sessions between the app server and the media server.
 
We are, however, not on board with using/adapting VoiceXML (in the case of IVR package) and possibly CCXML (in the case of upcoming conferencing package) as the syntax for the control messages.  VoiceXML and CCXML scripts carry in them part, if not all, of the application logic.  As such VoiceXML and CCXML interpreters belong on the application server, not a media server.  A media server, when properly separated from the application logic, is a stateless device that presents a pool of media resources to the application server(s) - it does not have a concept of a call, it can't do CDRs, transfers, initiate calls, etc.  
 
We believe a more suitable protocol for the media server control by the application server is MSML/MOML, as it provides lower level, more granular and more complete control over media resources, without requiring the state of the dialog or a conference to reside on the media server.
 
Regards,
Gene Shtirmer

________________________________________
From: Chris Boulton [mailto:[email-masked]] 
Sent: Friday, December 23, 2005 7:23 AM
To: Shtirmer, Gene
Subject: FW: [mediactrl] SIP Control Framework and IVR Package
FYI.

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On Behalf Of Chris Boulton
Sent: 23 December 2005 11:06
To: [email-masked]
Cc: McGlashan, Scott; Tim Melanchuk; Asher Shiratzky; Eric Burger; [email-masked]; Dolly, Martin C, ALABS
Subject: [mediactrl] SIP Control Framework and IVR Package
 
Hi All,
 
A small group has just submitted two new drafts and would like expert opinion/review from the 'Mediactrl' mailing list.  The following provides a brief introduction to the technology contained within the two specifications:-
 
- A Control Framework for the Session Initiation Protocol (SIP)
 
Abstract
This document describes a Framework and protocol for application deployment where the application logic and processing are distributed.  The framework uses the Session Initiation Protocol (SIP) to establish an application-level control mechanism between Application Servers and tightly associated external Servers e.g.Media Server.
 
The motivation for the creation of this Framework is to provide an interface suitable to meet the requirements of a distributed, centralized conference system, as defined by the XCON work group of the IETF.  It is not, however, limited to this scope and it is envisioned that this generic Framework will be used for a wide variety of de-coupled control architectures between network entities.

- An Interactive Voice (IVR) Control Package for the Session Initiation Protocol (SIP)
 
Abstract
This document defines a Session Initiation (SIP) Control Package for Interactive Voice Response (IVR) interaction.  The control of Media Servers and their related resources in decomposed network architectures plays an important role in various Next Generation Networks.  This Control Package aims to fulfill IVR requirements using the SIP Control Framework [7].
 
Until the drafts appear in the archives, they will be available from the following links:-
 
http://www.ubiquitysoftware.com/ietf/draft-boulton-sip-control-framework-00.txt
http://www.ubiquitysoftware.com/ietf/draft-boulton-sip-control-framework-00.html
 
and
 
http://www.ubiquitysoftware.com/ietf/draft-boulton-ivr-control-package-00.txt
http://www.ubiquitysoftware.com/ietf/draft-boulton-ivr-control-package-00.html

More packages to follow in the New Year to expand and provide proof points for the Control Framework as well as strengthening the Media Server Control proposal (e.g. package for Conference support).
 
Mr Burger, the authors would be grateful if you could include these drafts on the Media Control web pages and remove Media Server Request Protocol. 

Seasons Greetings to all,
 
The Authors.

Information contained in this e-mail and any attachments are intended for the use of the addressee only, and may contain confidential information of Ubiquity Software Corporation. All unauthorized use, disclosure or distribution is strictly prohibited.  If you are not the addressee, please notify the sender immediately and destroy all copies of this email.  Unless otherwise expressly agreed in writing signed by an officer of Ubiquity Software Corporation, nothing in this communication shall be deemed to be legally binding. Thank-you 

--------------------------
Ubiquity Software does not control or endorse the content, messages or information found in this mail list and it specifically disclaims any liability with regard to these communications.
Ubiquity Software reserves the right the restrict access to any communications in violation of the Terms and Conditions of Use for this website or as otherwise deemed improper.