Source note · SIP 488 and codec negotiation failures
Because SDES carries keying material in clear SDP, RFC 4568 requires confidentiality and integrity protection of the signaling and says SIP deployments should use SIPS or S/MIME.
Checked 2026-09-25
- Vendor
- IETF
- Product
- SDES
- Subsystem
- SRTP keying
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 4568
- Checked
- 2026-09-25
Sources
- RFC 4568: Session Description Protocol (SDP) Security Descriptions for Media Streams — IETF / RFC Editor · tier 1 standards and regulators · Section 3 Applicability; Section 8.3
Cite this note
APA
WarmTransfer. (2026, September 25). SIP 488 and codec negotiation failures: source note sip-488-codec-failures-sdes-needs-secure-signaling. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-488-codec-failures-sdes-needs-secure-signaling
BibTeX
@misc{warmtransfer-claim-sip-488-codec-failures-sdes-needs-secure-signaling,
title = {SIP 488 and codec negotiation failures: source note sip-488-codec-failures-sdes-needs-secure-signaling},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-488-codec-failures-sdes-needs-secure-signaling},
note = {Source note sip-488-codec-failures-sdes-needs-secure-signaling, checked 2026-09-25}
}