Public Safety Answering Point (PSAP) Callback

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 18
Abstract: 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.
Publication Date: 2014-04-01
Status Note: Proposed Standard
DOI: 10.17487/RFC7090
Link: https://doi.org/10.17487/RFC7090
Author(s): Henning Schulzrinne
Hannes Tschofenig
Christer Holmberg
Milan Patel
Keyword(s): PSAP, Callback, SIP, Emergency Services, VoIP

Latest version of IETF RFC 7090

Document Versions — IETF RFC 7090

▶ IETF RFC 7090 (2014-04-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 3261 [Active*]
IETF RFC 5234 [Active, Amended*]
IETF RFC 5627 [Active*]
IETF RFC 6878 [Active*]

Bibliographic Reference(s)

IETF, "Secure Telephone Identity Revisited (stir) Working Group", http://datatracker.ietf.org/wg/stir/charter/ , October 2013. EXTERNAL
IETF RFC 3325 [Active*]
IETF RFC 4474 [Superseded*]
IETF RFC 5012 [Active*]
IETF RFC 5222 [Active*]
IETF RFC 6443 [Active*]
IETF RFC 6881 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC7090.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 7090, Public Safety Answering Point (PSAP) Callback. Available at https://doi.org/10.17487/RFC7090

Snippet:

IETF RFC 7090, Public Safety Answering Point (PSAP) Callback. Available at https://doi.org/10.17487/RFC7090

HTML (ISO 690 compliant)

Preview:

IETF RFC 7090, Public Safety Answering Point (PSAP) Callback. Available at https://doi.org/10.17487/RFC7090

Snippet:

<span class="citation"><cite>IETF RFC 7090</cite>, Public Safety Answering Point (PSAP) Callback. Available at <a href="https://doi.org/10.17487/RFC7090" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7090</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 7090, Public Safety Answering Point (PSAP) Callback
doi: 10.17487/RFC7090
url: https://doi.org/10.17487/RFC7090

Snippet:

<li>
<cite id="bib-rfc7090">IETF RFC 7090</cite>, Public Safety Answering Point (PSAP) Callback
<span class="doi">10.17487/RFC7090</span>
</li>

Referenced By

IETF RFC 7852 [Active*]