The Continue Header Field for the Session Initiation Protocol (SIP)
draft-sinha-dispatch-sip-continuation-option-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Amardeep Sinha , Subhrajyoti De , Sunil Kumar Sinha | ||
| Last updated | 2012-10-04 (Latest revision 2012-04-02) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Before placing a call, it is quite often useful for the Caller to know whether a Callee is in favorable state to receive a call or not. This document defines an optional tag "continue" and a header "Continue" to address the purpose. The "Continue" header field is to confirm the session continuity with the Callee from the Caller after an option for session continuity is placed by the Callee based on the unfavorable state of the Callee. This functionality is needed to resolve the unwillingness of the Callee to receive any call. An option is given to the Callee by the Service Provider or by the Handset Manufacturer or by the Carrier to establish this requirement.
Authors
Amardeep Sinha
Subhrajyoti De
Sunil Kumar Sinha
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)