Source note · Troubleshooting calls that drop on hold or transfer
A 488 to a hold or resume re-INVITE does not by itself end the call under the SIP rules; a drop that follows is a decision by one of the devices (for example sending BYE), not a consequence required by the rejection.
inferred · Checked 2026-09-30
- Vendor
- IETF
- Product
- SIP
- Subsystem
- sip-dialog
- Deployment
- any
- Region
- not restricted
- Release range
- RFC as published
- Status
- inferred
- 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.1, read together with RFC 3261 Section 14.1
Cite this note
APA
WarmTransfer. (2026, September 30). Troubleshooting calls that drop on hold or transfer: source note sip-reinvite-call-drops-488-not-a-hangup. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-reinvite-call-drops-488-not-a-hangup
BibTeX
@misc{warmtransfer-claim-sip-reinvite-call-drops-488-not-a-hangup,
title = {Troubleshooting calls that drop on hold or transfer: source note sip-reinvite-call-drops-488-not-a-hangup},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-reinvite-call-drops-488-not-a-hangup},
note = {Source note sip-reinvite-call-drops-488-not-a-hangup, checked 2026-09-30}
}