Avaya's WebRTC solution is based on a TURN client residing on the Avaya Aura® Media Server or Scopia Elite MCU inside the enterprise. If the WebRTC browser is behind a restricted firewall that blocks UDP traffic, WebRTC media connections to Avaya Meetings Server or another WebRTC browser will not work. The solution for this issue is to use the WebRTC TURN client in the browser and send media to Avaya SBC through UDP port 3478 or TCP/TLS port 443. The UDP port is preferable for Quality of Service (QoS) reasons. If you use TURN on TLS, media will be encoded back to UDP by the TURN server on Avaya SBC.
Note:
For performance reasons, Avaya recommends enabling TURN in the browser client instead of using server-side TURN.
If you use TURN from browser, disable TURN on the Avaya Aura® Media Server and Scopia Elite MCU. If you need to place a firewall between Avaya SBC and the Avaya Aura® Media Server or Scopia Elite MCU, enable STUN on the Avaya Aura® Media Server or Scopia Elite MCU.
Avaya SBC must be configured to support the combination of the following ports:
STUN UDP 3478
TURN UDP 3478
TURN TCP/TLS 443
For more information about Avaya SBC configuration, see Administering Avaya Session Border Controller.
Currently, the TURN feature is supported in the following browsers:
Google Chrome
Mozilla Firefox
