A SIP Response Code (497) for Call Transfer Failure
draft-khatri-sipcore-call-transfer-fail-response-05
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Shrawan Kumar Khatri , Vikram Singh , Cherng-Shung Hsu | ||
| Last updated | 2024-01-25 (Latest revision 2023-07-24) | ||
| 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
This document defines the 497 (Call Transfer Failure) SIP response code, allowing Call Pull and Call Push parties to indicate that the operation was rejected. Optional warning codes are defined to carry granular information. SIP entities may use this information to adjust how subsequent calls can be handled intelligently.
Authors
Shrawan Kumar Khatri
Vikram Singh
Cherng-Shung Hsu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)