draft-rosenberg-sipping-app-interaction-framework
draft-burger-sipping-kpml
draft-jennings-sip-app-info
draft-culpepper-sipping-app-interact-reqs
draft-rosenberg-sip-vxml-00
draft-vandyke-mscml
draft-burger-sipping-netann
draft-rosenberg-sip-app-components-01
draft-rosenberg-sipping-app-interaction-framework-00.txt  | A Framework and Requirements for Application Interaction in SIP |
| Author(s) | Jonathan Rosenberg |
| Organization | ietf |
| State | unknown |
| Date | 2002-11-01 |
| Size | 109503 bytes |
| Abstract | This document describes a framework and requirements for the interaction between users and Session Initiation Protocol (SIP) based applications. By interacting with applications, users can guide the way in which they operate. The focus of this framework is stimulus signaling, which allows a user agent to interact with an application without knowledge of the semantics of that application. Stimulus signaling can occur to a user interface running locally with the client, or to a remote user interface, through media streams. Stimulus signaling encompasses a wide range of mechanisms, ranging from clicking on hyperlinks, to pressing buttons, to traditional Dual Tone Multi Frequency (DTMF) input. In all cases, stimulus signaling is supported through the use of markup languages, which play a key role in this framework. Table of Contents |
| draft-burger-sipping-kpml-01.txt
|
| draft-jennings-sip-app-info-00.txt | SIP Support for Application Initiation |
| Author(s) | Cullen Jennings |
| Organization | ietf |
| State | unknown |
| Date | 2002-10-31 |
| Size | 20090 bytes |
| Abstract | This document describes SIP extensions to allow network elements to request a UA to initiate a scripted application that is associated with a dialog. It provides a mechanism for the network elements to find out a UA's ability to fetch and execute scripts. |
| draft-culpepper-sipping-app-interact-reqs-03.txt
|
"Session Initiation Protocol Based Application Interaction Requirements",
Bert Culpepper, Robert Fairlie-Cuninghame, 06-MAR-03,
This document defines the high level requirements for a framework and/or one or more mechanisms that support user interaction, via SIP-based user agents, with applications residing on remote network servers. The requirements in this document address the overall features of such a system, without regard to its architecture. SIP currently supports media-based application interactions using methods such as speech, video and end-to-end telephony-related tones; however, it is desired that more general application interaction models are defined, especially those that are not restricted to the media plane. In addition, it is desired that an application be able to present the user with application-specific user interfaces and information. The user agent should also be able to generate activity indications back to an application to communicate actions on physical or logical user interfaces. The document also defines a number of topic-related terms to assist in disambiguating discussions of the issues. |
| draft-rosenberg-sip-vxml-00.txt | A SIP Interface to VoiceXML Dialog Servers |
| Author(s) | J Rosenberg |
| Organization | ietf |
| State | unknown |
| Date | 2001-07-18 |
| Size | 39082 bytes |
| Abstract | VoiceXML is an XML based scripting language for describing voice dialogs. VoiceXML interpreters run within an interpreter context that, among other tasks, provides a call control interface for accessing the interpreter. It is very natural to provide a VoIP-based interpreter context that uses SIP and RTP to communicate with the outside world. In this document, we provide detailed specifications for a SIP/RTP based interpreter context. |
| draft-vandyke-mscml-01.txt | SnowShore Media Server Control Markup Language (MSCML) and Protocol |
| Author(s) | Eric Burger, Jeff Van Dyke, Andy Spitzer |
| Organization | ietf |
| State | unknown |
| Date | 2003-02-04 |
| Size | 68047 bytes |
| Abstract | Media Server Control Markup Language (MSCML) is a markup language used in conjunction with SIP to provide advanced conferencing and IVR functions. |
| draft-burger-sipping-netann-05.txt | Basic Network Media Services with SIP |
| Author(s) | Eric Burger, Jeff Van Dyke, Andy Spitzer |
| Organization | ietf |
| State | unknown |
| Date | 2003-03-05 |
| Size | 50815 bytes |
| Abstract | In SIP-based networks, there is a need to provide basic network media services. Such services include network announcements, user interaction, and conferencing services. These services are basic building blocks, from which one can construct interesting applications. In order to have interoperability between servers offering these building blocks (also known as Media Servers) and application developers, one needs to be able to locate and invoke such services in a well-defined manner. This document describes a mechanism for providing an interoperable protocol interface between Application Servers, which provide application services to SIP-based networks, and Media Servers, which provide the basic media processing building blocks. |
| draft-rosenberg-sip-app-components-01.txt | An Application Server Component Architecture for SIP |
| Author(s) | J Rosenberg, H. Schulzrinne, Peter Mataga |
| Organization | ietf |
| State | unknown |
| Date | 2001-03-09 |
| Size | 113554 bytes |
| Abstract | An application server is defined as an entity that is capable of providing advanced features to users. Examples of features include call forwarding, call screening, debit card calling, web interactive voice response, etc. However, the set of functions needed to enable a broad range of such applications is quite large - it includes speech recognition, DTMF recognition and digit collection, text-to-speech synthesis, database interfacing, audio and video coding and decoding, audio and video bridging and mixing, and signaling, to name a few. Supporting such a large set of functions on the same box presents a major challenge. To solve this problem, the industry is proposing a decomposition of the application server into two components - a media server that handles the media component, and an application server that handles the call control, data, and signaling. The interface that has been proposed between these two elements is a control mechanism along the lines of MGCP or Megaco. In this paper, we propose an orthogonal decomposition, which breaks an application server into application server components. Each component represents a application server in its own right, but it provides a well defined component that by itself may be a complete, but simpler, application. |