Cisco BroadWorks handles large SIP messages by switching them to TCP rather than relying on UDP fragmentation, with transport settable per interface, network server, media server and routing NE as UDP, TCP or unspecified.
Checked 2026-10-02
- Vendor
- Cisco
- Product
- Cisco BroadWorks
- Subsystem
- SIP transport
- Deployment
- on-premises
- Region
- not restricted
- Release range
- as of 2020-11-11 document update
- Checked
- 2026-10-02
Sources
- Working with large SIP packets — Cisco Systems · tier 2 current vendor documentation · Solution section
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting failed calls caused by large SIP messages over UDP: source note sip-fragmentation-troubleshooting-bw-switch-to-tcp. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-fragmentation-troubleshooting-bw-switch-to-tcp
BibTeX
@misc{warmtransfer-claim-sip-fragmentation-troubleshooting-bw-switch-to-tcp,
title = {Troubleshooting failed calls caused by large SIP messages over UDP: source note sip-fragmentation-troubleshooting-bw-switch-to-tcp},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-fragmentation-troubleshooting-bw-switch-to-tcp},
note = {Source note sip-fragmentation-troubleshooting-bw-switch-to-tcp, checked 2026-10-02}
}