Source record · tier 1 standards and regulators
RFC 8688: A Session Initiation Protocol (SIP) Response Code for Rejected Calls
- Publisher
- IETF / RFC Editor
- URL
- https://www.rfc-editor.org/rfc/rfc8688.html
- Published
- 2019-12-01
- Updated
- unknown
- Accessed
- 2026-09-24
- HTTP status
- 200
- License
- IETF Trust Legal Provisions; short excerpts and locators only
Source notes citing this source
- RFC 8688 defines SIP 608 (Rejected) for an intermediary, such as a call analytics engine, that blocked the call; it can carry a jCard in Call-Info giving the intermediary operator's contact for redress. in context
- RFC 8688 defines 608 Rejected so that a calling party can learn that an intermediary, rather than the called party, rejected the call attempt. in context
- RFC 8688 requires that a Call-Info header field in a 608 response carry the purpose parameter jwscard and refer to a valid JWS encoding of a jCard, giving a blocked caller a contact for redress. in context
Cite this source record
APA
WarmTransfer. (2019, December 1). RFC 8688: A Session Initiation Protocol (SIP) Response Code for Rejected Calls. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-8688-sip-608-rejected
BibTeX
@misc{warmtransfer-rfc-8688-sip-608-rejected,
title = {RFC 8688: A Session Initiation Protocol (SIP) Response Code for Rejected Calls},
author = {{WarmTransfer}},
year = {2019},
url = {https://warmtransfer.net/knowledge/sources/rfc-8688-sip-608-rejected},
note = {IETF / RFC Editor, accessed 2026-09-24}
}