# WebRTC port number

**URL:** <https://community.wowza.com/t/webrtc-port-number/93274>\
**Category:** Wowza Streaming Engine\
**Created:** [May 7, 2021, 1:24pm UTC](https://community.wowza.com/t/webrtc-port-number/93274 "2021-05-07T13:24:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Janez\_Makovsek](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@Janez\_Makovsek](https://community.wowza.com/u/Janez_Makovsek)\
**Post date:** [May 7, 2021, 1:24pm UTC](https://community.wowza.com/t/webrtc-port-number/93274/1 "2021-05-07T13:24:20Z")

</div>

Dear All,

We are already using port 443 for HTTPS of Apple HLS. We would like to try WebRTC. Would Apple HLS on port 443 stop working, if we check the “Enable WebRTC” on VHost port edit page of the Engine Manager?

Do we need a separate IP, domain and SSL Certificate to use WebRTC next to Apple HLS?

Thanks!  
Atmapuri

---

<div class="post-metadata">

**Author:** ![Rose\_Power-Wowza\_Com](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/rose_power-wowza_com/32/431_2.png) [@Rose\_Power-Wowza\_Com](https://community.wowza.com/u/Rose_Power-Wowza_Com)\
**Post date:** [May 8, 2021, 12:18am UTC](https://community.wowza.com/t/webrtc-port-number/93274/2 "2021-05-08T00:18:34Z")

</div>

Yes your webrtc will need to be on its own port, but it doesn’t HAVE to be port 443. So you can keep port 443 as you have it now for HLS and HTTPS, but you’ll need to configure a different port for webrtc.

We have port 443 set as for the default though in Engine for webrtc, so if 443 is in use for something else already, you’ll need to set a different port for webrtc and make some small changes

Please see this [post](http://community.wowza.com/t/how-to-set-webrtc-port-to-444/55776/2) for steps:

* * *

Please play close attention to this 🙂 In this example port 444 was used instead for webrtc.

\*when you enter your signaling url, you will need to enter it with the port 444 instead of 443.

wss://5ab4321c0xxxx.streamlock.net:444/webrtc-session.json

---

<div class="post-metadata">

**Author:** ![Rose\_Power-Wowza\_Com](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/rose_power-wowza_com/32/431_2.png) [@Rose\_Power-Wowza\_Com](https://community.wowza.com/u/Rose_Power-Wowza_Com)\
**Post date:** [May 8, 2021, 12:19am UTC](https://community.wowza.com/t/webrtc-port-number/93274/3 "2021-05-08T00:19:14Z")

</div>

| Port | Type | Description |
| --- | --- | --- |
| 443 | TCP | During the WebRTC signaling process, Wowza Streaming Engine uses a secure WebSocket connection to establish a connection between peers. This requires a port for encrypted connections using SSL/TLS. By default, port 443 is used. The SSL/TLS port is defined in a **HostPort** entry in **[_install-dir_]/conf/VHost.xml**. |
| 6970 to 9999 | UDP | For WebRTC over UDP, Wowza Streaming Engine uses a default port range of 6970 to 9999. UDP ports are assigned dynamically, and each additional peer WebRTC connection increments the port number used. The starting port number is controlled by the **DatagramStartingPort** value specified in **[_install-dir_]/conf/Server.xml**. |
| 1935 | TCP | For WebRTC over TCP, Wowza Streaming Engine uses a non-SSL-protected streaming port for TCP-level connections. The TCP port is defined in a **HostPort** entry in **[_install-dir_]/conf/VHost.xml**. By default, port 1935 is used. TCP ports are referenced in the **IceCandidateIpAddresses** property in **[_install-dir_]/conf/[application-name]/Application.xml**. |

> **Note:** Port 554 isn’t supported for TCP ICE candidates.|

  

Reference article for chart:

> **[About WebRTC workflows in Wowza Streaming Engine](https://www.wowza.com/docs/webrtc-workflows-in-wowza-streaming-engine)**
>
> Describes the Wowza Streaming Engine implementation of WebRTC, including the supported codecs, workflows, and limitations.