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.
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
app.webinar.net
rts.webinar.net
reporting.webinar.net
lab.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-app.webinar.net
ap-rts.webinar.net
ap-reporting.webinar.net
ap-lab.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-app.webinar.net
eu-rts.webinar.net
eu-reporting.webinar.net
eu-lab.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
APAC webinar.net Presenter Console Static IP Addresses
54.254.0.169
54.254.86.42
EU webinar.net Presenter Console Static IP Addresses
18.193.145.100
18.159.54.121
What UDP ports are being used for TURN/STUN protocols and can you verify the
destinations?
| Firewall Ports | Network Protocol | Application Protocol | Description |
| 1719 | UDP | H.323 Gatekeeper RAS Port | |
| 1720 | TCP | H.323 Call Signaling | |
| 2855-2856 | TCP | MSRP | Used for call with messaging |
| 3478 | UDP | STUN service | Used for NAT traversal |
| 3479 | UDP | STUN service | Used for NAT traversal |
| 5002 | TCP | MLP protocol server | |
| 5003 | UDP | Neighborhood service | |
| 5060 | UDP & TCP | SIP UAS | Used for SIP signaling (Standard SIP Port, for default internal Profile) |
| 5070 | UDP & TCP | SIP UAS | Used for SIP signaling (For default "NAT" Profile) |
| 5080 | UDP & TCP | SIP UAS | Used for SIP signaling (For default "External" Profile) |
| 16384-32768 | UDP | RTP/RTCP multimedia streaming | Used for audio/video data in SIP, Verto, and other protocols |
| 5066 | TCP | Websocket | Used for WebRTC |
| 7443 | TCP | Websocket | Used for WebRTC |
| 8081-8082 | TCP | Websocket | Used for Verto |
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/
Comments
0 comments
Please sign in to leave a comment.