Session Initiation Protocol (SIP) History-Info Header Call Flow Examples
draft-barnes-sipcore-rfc4244bis-callflows-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mary Barnes , Francois Audet , Shida Schubert , Hans Erik van Elburg , Christer Holmberg | ||
| Last updated | 2012-09-26 (Latest revision 2012-03-27) | ||
| Replaced by | draft-ietf-sipcore-rfc4244bis-callflows | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sipcore-rfc4244bis-callflows | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Francois Audet
Shida Schubert
Hans Erik van Elburg
Christer Holmberg
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)