Public Safety Answering Point (PSAP) Callback (RFC7090)
Original Publication Date: 2014-Apr-01
Included in the Prior Art Database: 2014-Apr-18
Internet Society Requests For Comment (RFCs)
H. Schulzrinne: AUTHOR [+3]
Summoning police, the fire department, or an ambulance in emergencies is one of the fundamental and most valuable functions of the telephone. As telephone functionality moves from circuit-switched telephony to Internet telephony, its users rightfully expect that this core functionality will continue to work at least as well as it has for the legacy technology. New devices and services are being made available that could be used to make a request for help and that are not traditional telephones. Users are increasingly expecting them to be used to place emergency calls.
Internet Engineering Task Force (IETF) H. Schulzrinne Request for Comments: 7090 Columbia University Category: Standards Track H. Tschofenig ISSN: 2070-1721 C. Holmberg Ericsson M. Patel Huawei Technologies (UK) Co., Ltd. April 2014
Public Safety Answering Point (PSAP) Callback
After an emergency call is completed (terminated either prematurely by the emergency caller or normally by the call taker), the call taker may feel the need for further communication. For example, the call may have been dropped by accident without the call taker having sufficient information about the current state of an accident victim. A call taker may trigger a callback to the emergency caller using the contact information provided with the initial emergency call. This callback could, under certain circumstances, be treated like any other call and, as a consequence, it may get blocked by authorization policies or may get forwarded to an answering machine.
The IETF emergency services architecture specification already offers a solution approach for allowing Public Safety Answering Point (PSAP) callbacks to bypass authorization policies in order to reach the caller without unnecessary delays. Unfortunately, the specified mechanism only supports limited scenarios. This document discusses shortcomings of the current mechanisms and illustrates additional scenarios where better-than-normal call treatment behavior would be desirable. We describe a solution based on a new header field value for the SIP Priority header field, called "psap-callback", to mark PSAP callbacks.
al. Standards Track [Page 1]
RFC 7090 PSAP Callback April 2014
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Enginee...