Network flow & firewall related information
In order to use WeSeeDo your network needs to permit some basic & default communication using known and tested protocols. Even though for the majority of the devices that our clients use many of these ports & protocols are permitted by default, more restrictive, enterprise grade and customized networks might prohibit. This applies when we speak about virtualized environments, secured networks, VPN connections, network behind a firewall and even some custom integrations like modified browser engines.
The way to find out which of this applies to a certain customer, they need first to contact the IT team which supplied and configured their network or devices. Certain symptoms can be seen when WeSeeDo is used in such environments, symptoms which may include:
Inability to login (HTTPS access is restricted, most probably due to an IP whitelist mechanism)
Inability to provide approval of video/audio device usage (Browser might be modified to not permit such rights)
Inability to select video/audio devices in the configuration screen (Environment might be modified to not permit physical device usage)
Inability to turn the status button to on (Websocket access is restricted)
Inability to connect to a meeting (Either an IP Whitelist filtering or websocket issue)
Inability to receive or send media either audio or video (UDP traffic might be blocked)
As WeSeeDo cannot operate, modify or find out exactly which setting is causing this, the customer will have to find themselves where the issue resides and attempt to fix it. What WeSeeDo can do is provide a diagram with the network flow for a better understanding of the network requirements and a list with all the services, IPs, ports and protocols required for running WeSeeDo.
List of services
Service | Domain name | IP Address | Port/Protocol |
|---|---|---|---|
App Frontend (via Loadbalancer) | 85.10.152.37 / 85.10.142.36 (Backup) | 80/443 - HTTP/HTTPS | |
Deprecated Admin | 85.10.152.41 | 80/443 - HTTP/HTTPS | |
Logging API | 85.10.142.39 | 80/443 - HTTP/HTTPS | |
Outage Message API | 136.144.246.178 | 80/443 - HTTP/HTTPS | |
Admin Frontend (via Loadbalancer) | 85.10.152.37 / 85.10.142.36 (Backup) | 80/443 - HTTP/HTTPS | |
Main API (via Loadbalancer) | 85.10.152.37 / 85.10.142.36 (Backup) | 80/443 - HTTP/HTTPS 80/443 - WS/WSS | |
Media Server (via Loadbalancer) | 85.10.150.92 | 80/443 - HTTP/HTTPS 80/443 - WS/WSS | |
Media Server #1 (also connects directly) | 85.10.150.210 | 80/443 - HTTP/HTTPS 80/443 - WS/WSS | |
Media Server #2 (also connects directly) | 85.10.150.217 | 80/443 - HTTP/HTTPS 80/443 - WS/WSS | |
Turn server | 87.253.157.73 | 80/443 - HTTP/HTTPS 25000-65535 - UDP Traffic |
Any changes will be notified by WeSeeDo staff to all customers in a timely manner to provide a smooth transition when required.
All these services must be whitelisted and permitted on the ports specified to provide the best WeSeeDo experience possible.
To enhance the network traffic flow knowledge, a diagram is also attached providing an overview of how a WeSeeDo agent/participant client instance communicates with the necessary services:
