datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Basic Network Media Services with SIP
RFC 4240

Document type: RFC - Informational (December 2005; Errata)
Was draft-burger-sipping-netann (individual in tsv area)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 4240 (Informational)
Responsible AD: Allison Mankin
Send notices to: eburger@brooktrout.com, mankin@psg.com, jvandyke@brooktrout.com

Network Working Group                                     E. Burger, Ed.
Request for Comments: 4240                                   J. Van Dyke
Category: Informational                                       A. Spitzer
                                             Brooktrout Technology, Inc.
                                                           December 2005

                 Basic Network Media Services with SIP

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).

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
   interface between Application Servers, which provide application
   services to SIP-based networks, and Media Servers, which provide the
   basic media processing building blocks.

Burger, et al.               Informational                      [Page 1]
RFC 4240                   SIP Media Services              December 2005

Table of Contents

   1. Overview ........................................................2
      1.1. Conventions Used in This Document ..........................3
   2. Mechanism .......................................................3
   3. Announcement Service ............................................5
      3.1. Operation ..................................................8
      3.2. Protocol Diagram ...........................................9
      3.3. Formal Syntax ..............................................9
   4. Prompt and Collect Service .....................................11
      4.1. Formal Syntax for Prompt and Collect Service ..............12
   5. Conference Service .............................................13
      5.1. Protocol Diagram ..........................................14
      5.2. Formal Syntax .............................................16
   6. IANA Considerations ............................................17
   7. The User Part ..................................................17
   8. Security Considerations ........................................20
   9. Contributors ...................................................20
   10. Acknowledgements ..............................................20
   11. References ....................................................21
      11.1. Normative References .....................................21
      11.2. Informative References ...................................22

1.  Overview

   In SIP-based media networks (RFC 3261 [10]), there is a need to
   provide basic network media services.  Such services include playing
   announcements, initiating a media mixing session (conference), and
   prompting and collecting information with a user.

   These services are basic in nature, are few in number, and
   fundamentally have not changed in 25 years of enhanced telephony
   services.  Moreover, given their elemental nature, one would not
   expect them to change in the future.

   Multifunction media servers provide network media services to clients
   using server protocols such as SIP, often in conjunction with markup
   languages such as VoiceXML [20] and MSCML [21].  This document
   describes how to identify to a multifunction media server what sort
   of session the client is requesting, without modifying the SIP
   protocol.

   It is critically important to note that the mechanism described here
   in no way modifies the SIP protocol, the meaning, or definition of a
   SIP Request URI, or does it put any restrictions, in any way, on
   devices that do not implement this convention.

Burger, et al.               Informational                      [Page 2]
RFC 4240                   SIP Media Services              December 2005

   Announcements are media played to the user.  Announcements can be
   static media files, media files generated in real-time, media streams
   generated in real-time, multimedia objects, or combinations of the
   above.

   Media mixing is the act of mixing different RTP streams, as described
   in RFC 3550 [13].  Note that the service described here suffices for
   simple mixing of media for a basic conferencing service.  This

[include full document text]