webinar.net Network and Firewall Configurations (Ports, Domains, and IP Addresses)

If you or your company uses firewall whitelist to restrict network access to only specific websites or software, then you can use the information below to ensure that your service can connect.

Note. TCP Tunneling can be utilized by a single presenter, allowing the other presenters to use higher UDP ports providing low overhead and higher speeds. If a presenter is having audio and/or video difficulties, they can select the Enable TCP Tunneling checkbox to switch to a TCP connection.

Ports
webinar.net uses WebRTC for the presenters to do presentations.

There are 3 parts in WebRTC:
Signaling
Discovery
Establishing the P2P connection
For signaling, we use secure WebSocket (wss://), which requires 443 port.

Please refer to the following article for more info on the discovery and establishing p2p connection.
https://blog.addpipe.com/troubleshooting-webrtc-connection-issues

Domains
For most firewall or proxy systems, webinar.net recommends specifying a whitelist of DNS names for webinar.net services so that outbound connections can be made. The list of webinar.net domains currently includes (but is not limited to) the lists below.

webinar.net domains

admin.webinar.net
my.webinar.net
upload.webinar.net
present.webinar.net
present-api.webinar.net
app.webinar.net
api.webinar.net
rts.webinar.net
reporting.webinar.net
lab.webinar.net
join.webinar.net
registration.webinar.net
assets.webinar.net
cdn.webinar.net
assets.webinar.net
streams.webinar.net
connector-n1.webinar.net
connector-n2.webinar.net

APAC webinar.net domains

ap-admin.webinar.net
ap-my.webinar.net
ap-upload.webinar.net
ap-present.webinar.net
ap-present-api.webinar.net
ap-app.webinar.net
ap-api.webinar.net
ap-rts.webinar.net
ap-reporting.webinar.net
ap-lab.webinar.net
ap-join.webinar.net
ap-registration.webinar.net
ap-assets.webinar.net
ap-cdn.webinar.net
ap-assets.webinar.net
ap-streams.webinar.net
ap-connector-n1.webinar.net
ap-connector-n2.webinar.net

EU webinar.net domains

eu-admin.webinar.net
eu-my.webinar.net
eu-upload.webinar.net
eu-present.webinar.net
eu-present-api.webinar.net
eu-app.webinar.net
eu-api.webinar.net
eu-rts.webinar.net
eu-reporting.webinar.net
eu-lab.webinar.net
eu-join.webinar.net
eu-registration.webinar.net
eu-assets.webinar.net
eu-cdn.webinar.net
eu-assets.webinar.net
eu-streams.webinar.net
eu-connector-n1.webinar.net
eu-connector-n2.webinar.net

IP Addresses

webinar.net Presenter Console Static IP Addresses
52.8.29.55
18.144.139.10
54.176.90.158
54.219.247.146
50.18.255.254
184.169.155.180
13.57.84.179
54.215.24.27
54.177.180.171
13.52.130.31 (TCP Tunneling)

APAC webinar.net Presenter Console Static IP Addresses
54.254.0.169
54.254.86.42
8.139.237.4
18.140.162.227
52.220.97.232
54.179.5.154
18.142.123.224 (TCP Tunneling)

EU webinar.net Presenter Console Static IP Addresses

18.193.145.100
18.159.54.121
18.192.156.181
18.198.233.199
3.69.10.204 (TCP Tunneling)

What UDP ports are being used for TURN/STUN protocols and can you verify the
destinations?

Destinations

52.8.29.55
18.144.139.10
54.176.90.158
54.219.247.146
50.18.255.254
184.169.155.180

Is WebRTC over TCP supported?

No, and here is why: https://testrtc.com/happens-webrtc-shifts-turn-tcp/