Using the Session Initiation Protocol REGISTER Method To Obtain an Emergency Dialstring
draft-polk-ecrit-emergency-dialstring-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | James Polk | ||
| Last updated | 2006-02-28 | ||
| 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
Most efforts to address emergency calling challenges over IP (and cellular technologies such as GSM, TDMA, CDMA, etc, for that matter) have focused on locating the calling user in order to route the emergency call set-up request to the appropriate Public Safety Answering Point (PSAP). Little or no effort to date has focused on informing the caller what dialstring sequence they may need to use to initiate a call for emergency help. This document describes how the Session Initiation Protocol (SIP) REGISTER Request message is used to inform a user of which emergency dialstring (of the 60 known dialstring choices around the world) they should use, for where they are geographically.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)