Source note · SDP offer answer and codec negotiation
The recipient of an offer for a held stream should not automatically answer with the corresponding stream held, and RFC 3264 gives the reason: certain third party call control scenarios do not work when an answerer responds to held SDP with held SDP.
Checked 2026-09-15
Certain third party call control scenarios do not work when an answerer responds to held SDP with held SDP.
- Vendor
- IETF
- Product
- SIP
- Subsystem
- SDP offer/answer
- Deployment
- not restricted
- Region
- not restricted
- Release range
- RFC 3264
- Checked
- 2026-09-15
Sources
- RFC 3264 — An Offer/Answer Model with the Session Description Protocol (SDP) — IETF / RFC Editor · tier 1 standards and regulators · RFC 3264 section 8.4 Putting a Unicast Media Stream on Hold
Cite this note
APA
WarmTransfer. (2026, September 15). SDP offer answer and codec negotiation: source note sdp-oa-answerer-should-not-mirror-held-sdp. WarmTransfer. https://warmtransfer.net/knowledge/claims/sdp-oa-answerer-should-not-mirror-held-sdp
BibTeX
@misc{warmtransfer-claim-sdp-oa-answerer-should-not-mirror-held-sdp,
title = {SDP offer answer and codec negotiation: source note sdp-oa-answerer-should-not-mirror-held-sdp},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sdp-oa-answerer-should-not-mirror-held-sdp},
note = {Source note sdp-oa-answerer-should-not-mirror-held-sdp, checked 2026-09-15}
}