WebRTC External Client Access

Last Updated : Jan 21, 2025 |

External client access uses the following ports. These ports need to be enabled and correctly routed to the WebRTC Gateway:

  • TCP/HTTPS/Web Socket access on port 9443. Not adjustable.

  • TCP or TLS on the public ports range set in the WebRTC Gateway service configuration. The defaults are 56000 to 58000.

  • To handle address translation between the external and internal networks, the WebRTC Gateway supports STUN and TURN.

  • The devices used must also support the security certificate CA chain as the WebRTC Gateway.

Using an Avaya Session Border Controller for Enterprise

All the above requirements can be configured on an Avaya Session Border Controller for Enterprise. Refer to the Deploying Remote IP Office SIP Phones with an ASBCE manual.

The basic steps required are:

  1. Enable STUN and TURN operation on the Avaya Session Border Controller for Enterprise and in the WebRTC Gateway settings.

  2. Create a reverse proxy policy for HTTPS connections to the server hosting the WebRTC Gateway service.

  3. Add security certificates that use the same CA source to the ASBCE and create a TLS profile that uses those certificates.