Session Initiation Protocol (SIP) Cause URI parameter for Service Number translation
draft-mohali-cause-for-services-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Marianne Mohali | ||
| Last updated | 2015-04-16 (Latest revision 2014-10-13) | ||
| 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
[RFC4458] defines a "cause" URI parameter as having predefined values for Redirecting reasons as a mapping from ITU-T Q.732.2-5 Redirecting Reasons. The "cause" URI parameter is to be used in SIP or SIPs URI. In particular, it may appear in the History-Info header defined in [RFC7044] that MUST be added in retargeted requests. This specification creates a new predefined value for cases when the retargeting is caused by a specific service action leading to a called number translation. This document updates [RFC4458].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)