RFC 3261 requires all SIP elements to implement both UDP and TCP.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- SIP transport
- Deployment
- on-premises, multi-tenant
- Region
- not restricted
- Release range
- RFC 3261 as published
- Checked
- 2026-10-02
Sources
- RFC 3261 — SIP: Session Initiation Protocol — IETF / RFC Editor · tier 1 standards and regulators · Section 18 Transport, introductory paragraphs
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting failed calls caused by large SIP messages over UDP: source note sip-fragmentation-troubleshooting-rfc3261-udp-tcp-mandatory. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-fragmentation-troubleshooting-rfc3261-udp-tcp-mandatory
BibTeX
@misc{warmtransfer-claim-sip-fragmentation-troubleshooting-rfc3261-udp-tcp-mandatory,
title = {Troubleshooting failed calls caused by large SIP messages over UDP: source note sip-fragmentation-troubleshooting-rfc3261-udp-tcp-mandatory},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-fragmentation-troubleshooting-rfc3261-udp-tcp-mandatory},
note = {Source note sip-fragmentation-troubleshooting-rfc3261-udp-tcp-mandatory, checked 2026-10-02}
}