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 :
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.
|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 July 30th, 2021 the IP addresses of the servers* are as follows
Canada 01 220.127.116.11 Canada 02 18.104.22.168 Canada 03 22.214.171.124 Eastern US 01 126.96.36.199 Eastern US 02 188.8.131.52 Europe 01 184.108.40.206 Europe 02 220.127.116.11 Asia 01 18.104.22.168 Asia 02 22.214.171.124
*this list is subject to change
VPN and Firewall Configuration
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.
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|
* to avoid split tunneling issues we recommand to exclude all IPs of meeting proxy servers from VPN tunnel
We recommend whitelisting the *.icastgo.com sub-domain.
In particular, the application uses two advanced technologies:
- long running HTTP requests (Sever Sent Events)
And advanced proxy filtering or caching could interfere with these technologies.
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 61 and later
- Mozilla Firefox version 60 ESR and later
- Microsoft Edge version 74 and later
- Opera version 53 and later
- Apple Safari version 11.1 and later on macOS. Apple Safari on iOS 11.2 and later.