An Architectural Framework for Media Server Control
RFC 5567
|
Document |
Type |
|
RFC - Informational
(June 2009; No errata)
|
|
Author |
|
Tim Melanchuk
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
RFC 5567 (Informational)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Robert Sparks
|
|
Send notices to |
|
(None)
|
Network Working Group T. Melanchuk, Ed.
Request for Comments: 5567 Rain Willow Communications
Category: Informational June 2009
An Architectural Framework for Media Server Control
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) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Abstract
This document describes an architectural framework for Media Server
control. The primary focus will be to define logical entities that
exist within the context of Media Server control, and define the
appropriate naming conventions and interactions between them.
Melanchuk Informational [Page 1]
RFC 5567 Mediactrl Architecture June 2009
Table of Contents
1. Introduction ....................................................2
2. Terminology .....................................................3
3. Architecture Overview ...........................................4
4. SIP Usage .......................................................7
5. Media Control for IVR Services .................................10
5.1. Basic IVR Services ........................................11
5.2. IVR Services with Mid-Call Controls .......................11
5.3. Advanced IVR Services .....................................11
6. Media Control for Conferencing Services ........................12
6.1. Creating a New Conference .................................14
6.2. Adding a Participant to a Conference ......................14
6.3. Media Controls ............................................15
6.4. Floor Control .............................................16
7. Security Considerations ........................................21
8. Acknowledgments ................................................22
9. Contributors ...................................................22
10. Informative References ........................................23
1. Introduction
Application Servers host one or more instances of a communications
application. Media Servers provide real-time media processing
functions. This document presents the core architectural framework
to allow Application Servers to control Media Servers. An overview
of the architecture describing the core logical entities and their
interactions is presented in Section 3. The requirements for Media
Server control are defined in [RFC5167].
The Session Initiation Protocol (SIP) [RFC3261] is used as the
session establishment protocol within this architecture. Application
Servers use it both to terminate media streams on Media Servers and
to create and manage control channels for Media Server control
between themselves and Media Servers. The detailed model for Media
Server control together with a description of SIP usage is presented
in Section 4.
Several services are described using the framework defined in this
document. Use cases for Interactive Voice Response (IVR) services
are described in Section 5, and conferencing use cases are described
in Section 6.
Melanchuk Informational [Page 2]
RFC 5567 Mediactrl Architecture June 2009
2. Terminology
The following terms are defined for use in this document in the
context of Media Server control:
Application Server (AS): A functional entity that hosts one or more
instances of a communication application. The application server
may include the conference policy server, the focus, and the
conference notification server, as defined in [RFC4353]. Also, it
Show full document text