Skip to main content

Additional Data Related to an Emergency Call
RFC 7852

Revision differences

Document history

Date By Action
2022-05-17
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2022-02-15
(System) Received changes through RFC Editor sync (added Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'When an emergency call is sent to a Public Safety Answering Point (PSAP), the originating device, …
Received changes through RFC Editor sync (changed abstract to 'When an emergency call is sent to a Public Safety Answering Point (PSAP), the originating device, the access network provider to which the device is connected, and all service providers in the path of the call have information about the call, the caller, or the location, which is helpful for the PSAP to have in handling the emergency. This document describes data structures and mechanisms to convey such data to the PSAP. The intent is that every emergency call carry as much of the information described here as possible using the mechanisms described here.

The mechanisms permit the data to be conveyed by reference (as an external resource) or by value (within the body of a SIP message or a location object). This follows the tradition of prior emergency services standardization work where data can be conveyed by value within the call signaling (i.e., in the body of the SIP message) or by reference.')
2016-08-02
(System) IANA registries were updated to include RFC7852
2016-07-29
(System) RFC published