RFC 8085 notes that losing a single IP fragment loses the whole reassembled datagram, and that NATs and firewalls may discard fragments.
Checked 2026-10-02
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- UDP message sizing
- Deployment
- on-premises, multi-tenant
- Region
- not restricted
- Release range
- BCP 145 as published
- Checked
- 2026-10-02
Sources
- RFC 8085: UDP Usage Guidelines — RFC Editor (IETF) · tier 1 standards and regulators · Section 3.2 Message Size Guidelines
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting failed calls caused by large SIP messages over UDP: source note sip-fragmentation-troubleshooting-rfc8085-frag-loss-whole. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-fragmentation-troubleshooting-rfc8085-frag-loss-whole
BibTeX
@misc{warmtransfer-claim-sip-fragmentation-troubleshooting-rfc8085-frag-loss-whole,
title = {Troubleshooting failed calls caused by large SIP messages over UDP: source note sip-fragmentation-troubleshooting-rfc8085-frag-loss-whole},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-fragmentation-troubleshooting-rfc8085-frag-loss-whole},
note = {Source note sip-fragmentation-troubleshooting-rfc8085-frag-loss-whole, checked 2026-10-02}
}