Response Codes Regarding URIs that Cannot Be Routed to a Destination in the Session Initiation Protocol (SIP)
draft-worley-ex-uri-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dale R. Worley | ||
| Last updated | 2007-02-26 | ||
| 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
The Session Initiation Protocol (SIP) provides a number of response codes which a SIP agent can use to indicate that it cannot find a suitable destination to which to send a request. Unfortunately, this set of response codes was not carefully designed, making it difficult in many cases for a proxy to select a response code that accurately reflects the proxy's knowledge about the request URI. This document describes these response codes and their current usage.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)