RFC 8656 defines four transports between a TURN client and server (UDP, TCP, TLS over TCP and DTLS over UDP) and specifies that TURN always uses UDP between the server and the peer.
Checked 2026-09-30
- Vendor
- IETF
- Product
- TURN
- Subsystem
- transports
- Deployment
- protocol
- Region
- not restricted
- Release range
- RFC 8656 (February 2020)
- Checked
- 2026-09-30
Sources
- RFC 8656 — Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) — RFC Editor / Internet Engineering Task Force · tier 1 standards and regulators · Section 3.1 (Transports) (section number as relayed)
Cite this note
APA
WarmTransfer. (2026, September 30). Troubleshooting browser softphone audio in cloud contact centers: source note browser-softphone-audio-troubleshooting-rfc-turn-transports. WarmTransfer. https://warmtransfer.net/knowledge/claims/browser-softphone-audio-troubleshooting-rfc-turn-transports
BibTeX
@misc{warmtransfer-claim-browser-softphone-audio-troubleshooting-rfc-turn-transports,
title = {Troubleshooting browser softphone audio in cloud contact centers: source note browser-softphone-audio-troubleshooting-rfc-turn-transports},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/browser-softphone-audio-troubleshooting-rfc-turn-transports},
note = {Source note browser-softphone-audio-troubleshooting-rfc-turn-transports, checked 2026-09-30}
}