Session Initiation Protocol (SIP) History-Info Header Call Flow Examples
RFC 7131
|
| Document |
Type |
|
RFC - Informational
(March 2014; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-barnes-sipcore-rfc4244bis-callflows
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Paul Kyzivat
|
|
Shepherd write-up |
|
Show
(last changed 2013-09-05)
|
| IESG |
IESG state |
|
RFC 7131 (Informational)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Richard Barnes
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
No IC
|
Internet Engineering Task Force (IETF) M. Barnes
Request for Comments: 7131
Category: Informational F. Audet
ISSN: 2070-1721 Skype
S. Schubert
NTT
H. van Elburg
Detecon International Gmbh
C. Holmberg
Ericsson
March 2014
Session Initiation Protocol (SIP) History-Info Header Call Flow Examples
Abstract
This document describes use cases and documents call flows that
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 document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7131.
Barnes, et al. Informational [Page 1]
RFC 7131 History-Info Call Flows March 2014
Copyright Notice
Copyright (c) 2014 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
(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 ........................................................2
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 .................16
3.4. Automatic Call Distribution ...............................20
3.5. Determining the Alias Used ................................27
3.6. PBX Voicemail Example .....................................29
3.7. Consumer Voicemail Example ................................35
3.8. GRUU ......................................................41
3.9. Limited-Use Address .......................................44
3.10. Service Invocation .......................................47
3.11. Toll-Free Number .........................................48
4. Security Considerations ........................................51
5. Acknowledgements ...............................................51
6. Informative References .........................................51
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 [RFC7044], for example, applications and common scenarios.
The optional "rc" and "mp" header field parameters defined in
[RFC7044] are required for several of the use cases. Descriptions of
the example use cases, call flow diagrams, and messaging details are
provided.
Barnes, et al. Informational [Page 2]
RFC 7131 History-Info Call Flows March 2014
2. Conventions and Terminology
The term "retarget" is used as defined in [RFC7044]. The terms
"location service", "redirect", and "address-of-record (AOR)" are
Show full document text