Session Initiation Protocol (SIP) History-Info Header Call Flow Examples
draft-ietf-sipcore-rfc4244bis-callflows-06

The information below is for an old version of the document
Document Type Active Internet-Draft (sipcore WG)
Last updated 2013-10-10 (latest revision 2013-07-15)
Replaces draft-barnes-sipcore-rfc4244bis-callflows
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Paul Kyzivat
Shepherd write-up Show (last changed 2013-09-05)
IESG IESG state Approved-announcement to be sent::Point Raised - writeup needed
Telechat date
Responsible AD Richard Barnes
Send notices to sipcore-chairs@tools.ietf.org, draft-ietf-sipcore-rfc4244bis-callflows@tools.ietf.org
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
SIPCORE                                                        M. Barnes
Internet-Draft                                                   Polycom
Intended status: Informational                                  F. Audet
Expires: January 2, 2014                                           Skype
                                                             S. Schubert
                                                                     NTT
                                                           H. van Elburg
                                              Detecon International Gmbh
                                                             C. Holmberg
                                                                Ericsson
                                                                Jul 2013

Session Initiation Protocol (SIP) History-Info Header Call Flow Examples
             draft-ietf-sipcore-rfc4244bis-callflows-06.txt

Abstract

   This document describes use cases and documents call flows which
   require the History-Info header field to capture the Request-URIs as
   a Session Initiation Protocol (SIP) Request is retargeted.  The use
   cases are described along with the corresponding call flow diagrams
   and messaging details.

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 January 2, 2014.

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

Barnes, et al.           Expires January 2, 2014                [Page 1]
Internet-Draft           History-Info Call Flows                Jul 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.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions and Terminology  . . . . . . . . . . . . . . . . .  3
   3.  Detailed call flows  . . . . . . . . . . . . . . . . . . . . .  3
     3.1.  Sequentially Forking (History-Info in Response)  . . . . .  3
     3.2.  History-Info with Privacy Header Field . . . . . . . . . . 11
     3.3.  Privacy for a Specific History-Info Entry  . . . . . . . . 14
     3.4.  Automatic Call Distribution  . . . . . . . . . . . . . . . 18
     3.5.  Determining the Alias used.  . . . . . . . . . . . . . . . 23
     3.6.  PBX Voicemail Example  . . . . . . . . . . . . . . . . . . 26
     3.7.  Consumer Voicemail Example . . . . . . . . . . . . . . . . 31
     3.8.  GRUU . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
     3.9.  Limited Use Address  . . . . . . . . . . . . . . . . . . . 38
     3.10. Service Invocation . . . . . . . . . . . . . . . . . . . . 41
     3.11. Toll Free Number . . . . . . . . . . . . . . . . . . . . . 41
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 44
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 44
     5.1.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . 44
   6.  Informative References . . . . . . . . . . . . . . . . . . . . 44
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 45

Barnes, et al.           Expires January 2, 2014                [Page 2]
Internet-Draft           History-Info Call Flows                Jul 2013

1.  Overview

   Many services that use SIP require the ability to determine why and
   how the call arrived at a specific application.  The use cases
   provided in this document illustrate the use of the History-Info
   header [I-D.ietf-sipcore-rfc4244bis] for example applications and
   common scenarios.  The optional "rc" and "mp" header field parameters
Show full document text