Source note · Troubleshooting SIP 403 Forbidden from a carrier
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.
Checked 2026-09-30
- Vendor
- IETF
- Product
- SIP
- Subsystem
- response codes
- Deployment
- any
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- RFC 8688: A Session Initiation Protocol (SIP) Response Code for Rejected Calls — IETF / RFC Editor · tier 1 standards and regulators · section 3.1
Cite this note
APA
WarmTransfer. (2026, September 30). Troubleshooting SIP 403 Forbidden from a carrier: source note sip-403-forbidden-troubleshooting-rfc8688-call-info. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-403-forbidden-troubleshooting-rfc8688-call-info
BibTeX
@misc{warmtransfer-claim-sip-403-forbidden-troubleshooting-rfc8688-call-info,
title = {Troubleshooting SIP 403 Forbidden from a carrier: source note sip-403-forbidden-troubleshooting-rfc8688-call-info},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-403-forbidden-troubleshooting-rfc8688-call-info},
note = {Source note sip-403-forbidden-troubleshooting-rfc8688-call-info, checked 2026-09-30}
}