RFC 3264 says the recipient of an offer that puts a stream on hold SHOULD NOT automatically answer with its own side of that stream on hold.

Checked 2026-09-24

The recipient of an offer for a stream on-hold SHOULD NOT automatically return an answer with the corresponding stream on hold.
Vendor
IETF
Product
SIP
Subsystem
hold
Deployment
any
Region
not restricted
Release range
RFC 3264 as published
Checked
2026-09-24

Sources

Cite this note

APA

WarmTransfer. (2026, September 24). Hold resume and conference signaling: source note hold-resume-conference-3264-no-auto-hold-answer. WarmTransfer. https://warmtransfer.net/knowledge/claims/hold-resume-conference-3264-no-auto-hold-answer

BibTeX

@misc{warmtransfer-claim-hold-resume-conference-3264-no-auto-hold-answer,
  title  = {Hold resume and conference signaling: source note hold-resume-conference-3264-no-auto-hold-answer},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/hold-resume-conference-3264-no-auto-hold-answer},
  note   = {Source note hold-resume-conference-3264-no-auto-hold-answer, checked 2026-09-24}
}

Read in context