No Service To This Number Reject Code
draft-schwartz-sip-nsr-code-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | David Schwartz | ||
| Last updated | 2007-07-05 | ||
| 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) allows calls to both addresses of record (AORs) such as sip:alice@example.com and telephone numbers with either sip or tel schemes such as tel:+12127771234. As opposed to the AOR where the domain specifies the exact location or realm of the user and a reject code provides enough visiblity to the calling party to exit gracefully (e.g. a 404 indicates that there is no point in trying further as the requested user either does not exist or is offline with no voicemail) with telephone numbers (TNs) this is not the case. With more and more TNs representing actual IP endpoints there is a need to differentiate in an error code between rejecting a call due to a misdialed number (i.e. the number does not exist) and a number that is just not associated with an IP endpoint (for example in a case where there is no billing relationship and as such the rejecting proxy cannot forward to a PSTN termination provider. This specification defines a new SIP response code (No Service Reject - nsr) for this purpose.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)