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

 
Document
Type Replaced Internet-Draft (individual)
Last updated 2012-09-26 (latest revision 2012-03-27)
Replaced by draft-ietf-sipcore-rfc4244bis-callflows
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Replaced by draft-ietf-sipcore-rfc4244bis-callflows
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-barnes-sipcore-rfc4244bis-callflows-03.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.

Authors

Mary Barnes (mary.ietf.barnes@gmail.com)
Francois Audet (francois.audet@skype.net)
Shida Schubert (shida@ntt-at.com)
Hans van Elburg (ietf.hanserik@gmail.com)
Christer Holmberg (christer.holmberg@ericsson.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)