Routing of Service Numbers with-in SIP (Session Initiation Protocol) networks
draft-jesske-dispatch-servicenumber-routeing-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Roland Jesske | ||
| Last updated | 2013-01-31 (Latest revision 2012-07-30) | ||
| 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 combination of "rn" and "npdi" parameters which are normally used for number portability (NP) can also solve numbering and routing problems. Database dips to obtain routing numbers are not only needed for NP, but also for the routing of service numbers and short code numbers in the PSTN and also in SIP networks. This document defines the use of the tel URI parameters defined for NP ("rn" and "npdi") to route service numbers and short code numbers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)