Session Initiation Protocol Service Example -- Music on Hold
draft-worley-service-example-13

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-09-13 (latest revision 2013-06-25)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd None
Shepherd write-up Show (last changed 2013-08-16)
IESG IESG state IESG Evaluation
Telechat date
Needs a YES.
Responsible AD Richard Barnes
IESG note Rifaat Shekh-Yusef (rifaat.sy@gmail.com) is the document shepherd.
Send notices to worley@ariadne.com, draft-worley-service-example@tools.ietf.org, rifaat.sy@gmail.com
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Dispatch                                                       D. Worley
Internet-Draft                                                   Ariadne
Intended status: Informational                             June 25, 2013
Expires: December 27, 2013

      Session Initiation Protocol Service Example -- Music on Hold
                    draft-worley-service-example-13

Abstract

   The "music on hold" feature is one of the most desired features of
   telephone systems in the business environment.  "Music on hold" is
   where, when one party to a call has the call "on hold", that party's
   telephone provides an audio stream (often music) to be heard by the
   other party.  Architectural features of SIP make it difficult to
   implement music-on-hold in a way that is fully compliant with the
   standards.  The implementation of music-on-hold described in this
   document is fully effective and standards-compliant, and has a number
   of advantages over the methods previously documented.  In particular,
   it is less likely to produce peculiar user interface effects and more
   likely to work in systems which perform authentication than the
   music-on-hold method described in section 2.3 of RFC 5359.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 27, 2013.

Copyright Notice

   Copyright (c) 2013 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

Worley                  Expires December 27, 2013               [Page 1]
Internet-Draft                Music on Hold                    June 2013

   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Intended Status . . . . . . . . . . . . . . . . . . . . .   3
   2.  Technique . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Placing a Call on Hold and Establishing an External Media
           Stream  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Taking a Call off Hold and Terminating the External Media
           Stream  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Example Message Flow  . . . . . . . . . . . . . . . . . .   6
     2.4.  Receiving Re-INVITE and UPDATE from the Remote UA . . . .  15
     2.5.  Receiving INVITE with Replaces  . . . . . . . . . . . . .  15
     2.6.  Receiving REFER from the Remote UA  . . . . . . . . . . .  17
     2.7.  Receiving Re-INVITE and UPDATE from the Music-On-Hold
           Source  . . . . . . . . . . . . . . . . . . . . . . . . .  19
     2.8.  Handling Payload Type Numbers . . . . . . . . . . . . . .  19
       2.8.1.  Analysis  . . . . . . . . . . . . . . . . . . . . . .  19
       2.8.2.  Solution to the Problem . . . . . . . . . . . . . . .  20
       2.8.3.  Example of the Solution . . . . . . . . . . . . . . .  21
     2.9.  Dialog/Session Timers . . . . . . . . . . . . . . . . . .  25
     2.10. When the Media Stream Directionality is "inactive"  . . .  25
     2.11. Multiple Media Streams  . . . . . . . . . . . . . . . . .  25
   3.  Advantages  . . . . . . . . . . . . . . . . . . . . . . . . .  26
   4.  Caveats . . . . . . . . . . . . . . . . . . . . . . . . . . .  27
     4.1.  Offering All Available Media Formats  . . . . . . . . . .  27
     4.2.  Handling Re-INVITES in a B2BUA  . . . . . . . . . . . . .  28
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  28
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  28
   7.  Revision History  . . . . . . . . . . . . . . . . . . . . . .  29
     7.1.  Changes from draft-worley-service-example-00 to draft-
Show full document text