RFC 8656 advises using a TURN server only when a direct communication path cannot be found, noting that relaying is costly to the TURN server's provider.
Checked 2026-09-30
- Vendor
- IETF
- Product
- TURN
- Subsystem
- relay usage
- 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 1 (Introduction)
Cite this note
APA
WarmTransfer. (2026, September 30). Troubleshooting browser softphone audio in cloud contact centers: source note browser-softphone-audio-troubleshooting-rfc-turn-last. WarmTransfer. https://warmtransfer.net/knowledge/claims/browser-softphone-audio-troubleshooting-rfc-turn-last
BibTeX
@misc{warmtransfer-claim-browser-softphone-audio-troubleshooting-rfc-turn-last,
title = {Troubleshooting browser softphone audio in cloud contact centers: source note browser-softphone-audio-troubleshooting-rfc-turn-last},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/browser-softphone-audio-troubleshooting-rfc-turn-last},
note = {Source note browser-softphone-audio-troubleshooting-rfc-turn-last, checked 2026-09-30}
}