Source note · Troubleshooting calls that drop on hold or transfer
If any change requested in a re-INVITE, or in a transaction within it, has already been executed, the UAS SHOULD return a 2xx response rather than an error.
Checked 2026-09-30
- Vendor
- IETF
- Product
- SIP
- Subsystem
- sip-dialog
- Deployment
- any
- Region
- not restricted
- Release range
- RFC as published
- Checked
- 2026-09-30
Sources
- RFC 6141: Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP) — IETF / RFC Editor · tier 1 standards and regulators · Section 3.3 (UAS Behavior)
Cite this note
APA
WarmTransfer. (2026, September 30). Troubleshooting calls that drop on hold or transfer: source note sip-reinvite-call-drops-uas-2xx-after-change. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-reinvite-call-drops-uas-2xx-after-change
BibTeX
@misc{warmtransfer-claim-sip-reinvite-call-drops-uas-2xx-after-change,
title = {Troubleshooting calls that drop on hold or transfer: source note sip-reinvite-call-drops-uas-2xx-after-change},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-reinvite-call-drops-uas-2xx-after-change},
note = {Source note sip-reinvite-call-drops-uas-2xx-after-change, checked 2026-09-30}
}