General bandwidth requirements can be found here: What’s the minimum required bandwidth?
## HyHyve
The HyHyve Application itself.
Host Port Protocols app.hyhyve.com 443 HTTPS, WSS api.hyhyve.com 443 HTTPS, WSS
## Whereby
Whereby is used for Broadcasting and group video communications if selected in the Release Settings.
### Firewall Whitelist:
Add the following destination domains and the corresponding ports to your firewall whitelist.
.appearin.com .appearin.net .appearin.video .whereby.cloud .whereby.com .whereby.com.mx .whereby.info .whereby.jp .whereby.vc *.whereby.com ;-)
All traffic flows on port 443 TCP/UDP.
### Signaling (secure websockets):
Control messages between the clients and the Whereby servers when in a call ("signaling") is transmitted over secure websockets (wss). These utilize the same ports as https, but will set up persistent two-way connections.
Proxies and firewalls that intercept https traffic need to be configured to allow websocket traffic towards these hosts/domains (some of these are legacy and will be phased out in the near future, but for the time being still need to be accessible):
signal.srv.whereby.com any.sfu.whereby.com *.sfu.whereby.com rtcstats.srv.whereby.com signal.appearin.net sfu.appearin.net rtcstats.appearin.net
### Media:
In order to transmit video and audio, the participants must be allowed to send and receive packets containing media content. The optimal path for these packets is directly between participants, but where this is not possible/allowed, Whereby provides a network of TURN servers that can act as relays for this. These servers are placed across the globe, and participants will connect to the closest ones.
Participants will connect to port 443 on these servers, on either UDP or TCP. For call quality and experience, UDP is the preferred protocol.
The TURN servers are identified by the hostname patterns:
*.turn.whereby.com turnserver.appearin.net
### Summary:
| Service | Dest. | Port | Protocol | Mandatory |
| --------------------- | ------| ---------- | -------- | ------------------------- |
| Signaling (wss) | any | 443 | TCP | Yes, see above |
| turn relay (tcp/tls)* | any | 443 | TCP | Yes, please see note 1 |
| turn relay (udp)* | any | 443 | UDP | Optional, pls see note 1 |
| turn/sfu highport** | any | 1024-65535 | UDP | Optional, pls see note 2 |
* Note 1: Can be omitted, but this is NOT recommended. Media will, if possible, be tunneled over TCP port 443 instead. This tunneling is not http. If it passes through a proxy that drops non-http traffic, make sure that the proxy is configured to make an exception allowing non-http traffic towards the TURN server hostnames.
** Note 2: Recommended, but not mandatory. If closed, some calls will see slightly increased round-trip time (delay).
## Stripe
To use our payment gateways, you should allow connecting to stripe.
api.stripe.com checkout.stripe.com dashboard.stripe.com files.stripe.com js.stripe.com m.stripe.com m.stripe.network q.stripe.com verify.stripe.com stripe.com
For more info, visit [<https://stripe.com/docs/ips>](<https://stripe.com/docs/ips>)
## Twilio (Deprecated)
For group video communications (i.e., if two or more participants run together and get connected).
### Signaling
Host Port and Protocol de1.vss.twilio.com 443 WSS
### Media Servers
Germany
52.59.186.0 - 52.59.186.31 18.195.48.224 - 18.195.48.255 18.156.18.128 - 18.156.18.255
Ports used: 10,000 - 60,000 UDP/SRTP/SRTCP and TLS/443 or UDP/3478
### Additional Connectivity Requirements
### More Info
See: [<https://www.twilio.com/docs/video/ip-addresses>](<https://www.twilio.com/docs/video/ip-addresses>)
Twilio Network Test: <https://networktest.twilio.com/>
## Agora (Deprecated)
Agora is used for the Broadcasting feature.
To allow you to use Agora products in environments with restricted network access, Agora provides two solutions: the firewall whitelist and the Agora cloud proxy.
### Solution A: Firewall Whitelist
Add the following destination domains and the corresponding ports to your firewall whitelist.
.agora.io .edge.agora.io .sd-rtn.com .edge.sd-rtn.com
| Destination ports | Port type | Operation |
| -------------------------------------------------- | --------- | --------- |
| 80; 443; 3433; 4700 - 5000; 5668; 5669; 6080; 6443 | TCP | Allow |
| 8667; 9667; 30011 - 30013 (for RTMP converter) | TCP | Allow |
| 3478; 4700 - 5000 | UDP | Allow |
Source: [<https://docs.agora.io/en/Agora%20Platform/firewall>](<https://docs.agora.io/en/Agora%20Platform/firewall>)
### Solution B: Cloud Proxy
If Agora cannot connect to the mentioned domains and ports above, an automatic connection to the cloud proxy is tried.
| Protocol | Destination | Port | Purpose |
| -------- | -------------- | ----------- | ------------------------- |
| TCP | 23.236.115.138 | 443, 4000 | Message data transmission |
| TCP | 23.236.115.138 | 3433 - 3460 | Media data exchange |
| TCP | 69.28.51.149 | 443, 4000 | Message data transmission |
| TCP | 69.28.51.149 | 3433 - 3460 | Media data exchange |
| TCP | 164.52.87.25 | 443, 4000 | Message data transmission |
| TCP | 164.52.87.25 | 3433 - 3460 | Media data exchange |
| TCP | 47.74.211.17 | 443 | Edge node communication |
| TCP | 52.80.192.229 | 443 | Edge node communication |
| TCP | 52.52.84.170 | 443 | Edge node communication |
| TCP | 47.96.234.219 | 443 | Edge node communication |
| UDP | 23.236.115.138 | 3478 - 3500 | Media data exchange |
| UDP | 164.52.87.25 | 3478 - 3500 | Media data exchange |
| UDP | 148.153.66.218 | 3478 - 3500 | Media data exchange |
Source: [<https://docs.agora.io/en/Interactive%20Broadcast/cloud_proxy_web?platform=Web>](<https://docs.agora.io/en/Interactive%20Broadcast/cloud_proxy_web?platform=Web>)