Source note · Call transfer semantics REFER and Replaces

RFC 7647 deprecates the 202 response code for REFER: an element accepting a REFER request must not reply with 202, must treat any 202 it receives as identical to a 200, and must send 200 wherever RFC 3515 requires 202. Accepting a REFER with any 2xx still obliges the recipient to create a subscription and notify the status of the refer.

Checked 2026-09-16

an element accepting a REFER request MUST NOT reply with a 202 response code and MUST treat any 202 responses received as identical to a 200 response. Wherever [ RFC3515 ] requires sending a 202 response code, a 200 response code MUST be sent instead.

Vendor: IETF
Product: Session Initiation Protocol
Subsystem: REFER
Deployment: not restricted
Region: not restricted
Release range: Updates RFC 3515
Checked: 2026-09-16

Sources

RFC 7647 — Clarifications for the Use of REFER with RFC 6665 — IETF / RFC Editor · tier 1 standards and regulators · RFC 7647 section 5 The 202 Response Code Is Deprecated

Cite this note

APA

WarmTransfer. (2026, September 16). Call transfer semantics REFER and Replaces: source note xfersem-202-is-deprecated-for-refer. WarmTransfer. https://warmtransfer.net/knowledge/claims/xfersem-202-is-deprecated-for-refer

BibTeX

@misc{warmtransfer-claim-xfersem-202-is-deprecated-for-refer,
  title  = {Call transfer semantics REFER and Replaces: source note xfersem-202-is-deprecated-for-refer},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/xfersem-202-is-deprecated-for-refer},
  note   = {Source note xfersem-202-is-deprecated-for-refer, checked 2026-09-16}
}

Read in context