RFC 8197: A SIP Response Code for Unwanted Calls
In plain English — editorial summary, not part of the RFC
This document defines the 607 (Unwanted) SIP response code, allowing called parties to indicate that the call or message was unwanted. SIP entities may use this information to adjust how future calls from this calling party are handled for the called party or more broadly.
Document record
- Document ID
- RFC8197
- Published
- July 2017
- Authors
- H. Schulzrinne
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8224Authenticated Identity Management in the Session Initiation Protocol (SIP)Updated
February 2018
- RFC 8262Content-ID Header Field in the Session Initiation Protocol (SIP)Current
October 2017
- RFC 8266Preparation, Enforcement, and Comparison of Internationalized Strings Representing NicknamesCurrent
October 2017
- RFC 8076A Usage for Shared Resources in RELOAD (ShaRe)Current
March 2017
- RFC 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent
December 2016
- RFC 8373Negotiating Human Language in Real-Time CommunicationsUpdated
May 2018
- RFC 8396Managing, Ordering, Distributing, Exposing, and Registering Telephone Numbers (MODERN): Problem Statement, Use Cases, and FrameworkCurrent
July 2018
- RFC 7989End-to-End Session Identification in IP-Based Multimedia Communication NetworksCurrent
October 2016
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?