RFC 8688: A Session Initiation Protocol (SIP) Response Code for Rejected Calls
In plain English — editorial summary, not part of the RFC
This document defines the 608 (Rejected) Session Initiation Protocol (SIP) response code. This response code enables calling parties to learn that an intermediary rejected their call attempt. No one will deliver, and thus answer, the call. As a 6xx code, the caller will be aware that future attempts to contact the same User Agent Server will likely fail. The initial use case driving the need for the 608 response code is when the intermediary is an analytics engine. In this case, the rejection is by a machine or other process. This contrasts with the 607 (Unwanted) SIP response code in which a human at the target User Agent Server indicates the user did not want the call. In some jurisdictions, this distinction is important. This document also defines the use of the Call-Info header field in 608 responses to enable rejected callers to contact entities that blocked their calls in error. This provides a remediation mechanism for legal callers that find their calls blocked.
Document record
- Document ID
- RFC8688
- Published
- December 2019
- Authors
- E.W. Burger; B. Nagda
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8946Personal Assertion Token (PASSporT) Extension for Diverted CallsCurrent
February 2021
- RFC 8356Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)Current
March 2018
- RFC 9029Updates to the Allocation Policy for the Border Gateway Protocol - Link State (BGP-LS) Parameters RegistriesObsoleted
June 2021
- RFC 9184BGP Extended Community Registries UpdateCurrent
January 2022
- RFC 9281Entities Involved in the IETF Standards ProcessCurrent
June 2022
- RFC 9304Locator/ID Separation Protocol (LISP): Shared Extension Message and IANA Registry for Packet Type AllocationsCurrent
October 2022
- RFC 9371Registration Procedures for Private Enterprise Numbers (PENs)Current
March 2023
- RFC 9448TNAuthList Profile of Automated Certificate Management Environment (ACME) Authority TokenCurrent
September 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?