To ensure a better experience, icastGo uses many advanced features of your browser.
There are certain technical requirements that must be met, such as using a relatively modern web browser.
These prerequisites are summarized on this page
We strongly advise you to perform both technical tests:
| Test your network | Audio and Video Test |
|---|
In this article :
VPN and Firewall Configuration
Network requirements
icastGo is a platform hosted on the cloud and therefore theoretically accessible through any Internet connection. However, some corporate firewalls may need to specifically authorize certain ports.
Firewall configuration
| 443 (TCP) | HTTPS outgoing port |
| 40000-49999 (UDP)* | WebRTC UDP outgoing ports for transmitting video and audio from a browser |
| 40000-49999 (TCP)* | When outgoing UDP is not available WebRTC TCP outgoing ports for transmitting video and audio from a browser |
*If the 443 (TCP) post is the only available outgoing port, then the WebRTC connection will be established on this port as a fallback.
Meeting servers addresses
As of October19th, 2023 the IP addresses of the servers* are as follows
Canada 01: 15.222.156.13
Canada 02: 15.222.198.204
Canada 03: 35.182.135.81
Canada 04: 3.99.118.86
Canada 05: 35.183.188.234
Canada 06: 15.156.37.128
Canada 07: 3.96.121.109
Canada 08: 15.156.233.122
Canada 09: 3.97.58.133
Canada 10: 3.97.230.148
Eastern US: 01 54.90.146.2
Eastern US: 02 52.22.107.212
Eastern US: 03 3.214.87.58
Eastern US: 04 44.208.41.19
Europe 01: 15.188.121.49
Europe 02: 13.36.13.192
Europe 03: 15.236.124.205
Europe 04: 13.36.6.192
Asia 01: 3.7.148.67
Asia 02: 3.108.33.61
Asia 03: 3.111.60.198
Asia 04: 65.1.143.162
*this list is subject to change
VPN and Firewall Configuration
The FQDN meet.icastgo.com returns a single IP depending on several parameters
- request geolocation
- local servers pool availability
- servers health
- randomness if the response is multiple
Once WebRTC connection established with a signaling server another one is established for the media layer. This other server could be used, it will be one of the same list (it might also be the same than the signaling one.
To avoid any issue regarding VPN split tunneling and/ot firewall, we recommand to include all IPs of meeting servers in the rules/authorisations.
Split tunneling
For better performances and latency during audio and video calls we recommend to enable split tunneling for VPN connections.
Split tunneling allows precisely identified traffic to not be handled by the VPN but by the local Internet access of the speaker.
We recommend to add the following domains as non-VPN traffic :
| Domain | Audience | Purpose | Traffic | Typical per user bandwidth |
| meet.icastgo.com* | Speakers | Audio-video traffic and VMR control | HTTPs, WebRTC | ~3 Mpbs Up/Down |
| app.icastgo.com | Speakers and admins | Plateform control | HTTPs | Negligible |
| mediacdn.icastgo.com | Participants | Webcast media | HTTPs | 1,5 Mbps Down |
| assetscdn.icastgo.com | Participants | Webcast Slides | HTTPs | 3 kpbs Down |
| appcdn.icastgo.com | Participants | Webcast Data | HTTPs | Negligible |
* to avoid split tunneling issues we recommand to exclude all IPs of meeting proxy servers from VPN tunnel
Proxy configuration
We recommend whitelisting the *.icastgo.com sub-domain.
In particular, the application uses two advanced technologies:
- long running HTTP requests (Sever Sent Events)
- WebSockets
And advanced proxy filtering or caching could interfere with these technologies.
Zscaler proxies and webcast presenter/participant connection issue
Zscaler is a cloud security platform designed to scan data for potential threats. When installed on a presenter's computer, it reroutes both Webcast and Virtual Meeting Room (used by presenters) audio and video streams through the Zscaler security cloud before reaching the Webcast network. This can sometimes result in blocked video and audio or lead to call quality issues.
Since Webcast and Virtual Meeting Room connections don’t carry executable data, there is no need for Zscaler to scan them. To prevent interruptions, we recommend configuring Zscaler to bypass Webcast/VMR related traffic. If you're a Webcast presenter or participant with Zscaler installed, please contact your IT organization for assistance with this configuration.
For instructions on setting up Zscaler bypasses, visit: https://help.zscaler.com/z-app/best-practices-adding-bypasses-z-tunnel-2.0
To properly configure Zscaler, you can reference the complete list of network requirements : Technical requirements for using icastGo meeting rooms from a browser – icastGo User Help Center
Browser requirements
Important note: icastGo is compatible with all browsers for participants.
However, for speakers who use their browsers to transmit audio and video or simply to collaborate live during a webcast, we recommend the latest versions of the following browsers:
- Google Chrome version 109 and later
- Mozilla Firefox version 114 and later
- Microsoft Edge version 114 and later
- Opera version 99 and later
- Apple Safari version 15.6 and later on macOS
- Apple Safari version 16.0 and later on iOS