Sana

Before your company start to use Sana Live, it is important to understand if any traffic is blocked by internal firewalls. This can from time to time be tricky to identify - sometimes it prevents users from joining the session or it can appear suddenly in the session. Typically, error messages then appear, users might lose audio and video and they can get disconnected from the call.

To test this, we recommend following these steps:

Test Sana Live with a colleague, using your company computer on your company's network (see <a href="https://help.sana.ai/en/articles/20633-how-to-set-up-a-sana-live-session" rel="nofollow noopener noreferrer" target="_blank">here</a> on how to set up a session)

Experience issues? Follow the steps in the next cards

Done with the whitelisting? Perfect - try Sana Live one more time with a colleague to make sure everything works smoothly 

- Test Sana Live with a colleague, using your company computer on your company's network (see <a href="https://help.sana.ai/en/articles/20633-how-to-set-up-a-sana-live-session" rel="nofollow noopener noreferrer" target="_blank">here</a> on how to set up a session)
- Experience issues? Follow the steps in the next cards
- Done with the whitelisting? Perfect - try Sana Live one more time with a colleague to make sure everything works smoothly 

If you are experiencing issues with Sana Live, for example issues connecting to a call, you probably need to whitelist some of our services in the network firewall.

Whitelisting new tools is a common procedure in many companies and allows users inside the firewall to connect to websites that have been approved. Sana Live relies on two services to function properly, Agora and Ably.

Sana Live will connect to the following service URLs:

<b>URLs</b> .agora.io .edge.agora.io .sd-rtn.com .edge.sd-rtn.com

<b>In rare cases you also need to whitelist connections to Ably:</b>

- rest.ably.io 
- realtime.ably.io
- eu-a-fallback.ably-realtime.com
- eu-b-fallback.ably-realtime.com
- eu-c-fallback.ably-realtime.com
- eu-d-fallback.ably-realtime.com
- eu-e-fallback.ably-realtime.com

Additionally, Ably uses the following two endpoints for uptime checks: 

<a href="https://internet-up.ably-realtime.com/is-the-internet-up.txt" rel="nofollow noopener noreferrer" target="_blank">https://internet-up.ably-realtime.com/is-the-internet-up.txt</a> 

- <a href="https://internet-up.ably-realtime.com/is-the-internet-up.txt" rel="nofollow noopener noreferrer" target="_blank">https://internet-up.ably-realtime.com/is-the-internet-up.txt</a> 
- wss://ws-up.ably-realtime.com

Depending on your IT setup, whitelisting URLs might not be possible. But don't worry! We can use something called Cloud Proxy. Cloud Proxy is a fallback and it's reserved as a last resort, since it does reduce the audio and video quality.

When normal whitelisting isn't possible, we can use the Cloud Proxy. Please contact your CSM in order to enable it for your organization. 

Destination ports	Port type	Operation
80 443 3433 4700 - 5000 5668 5669 6080 6443 8667 9667 30011 - 30013	TCP	Allow
3478 4700 - 5000	UDP	Allow

Whitelist Sana Live

In rare cases you also need to whitelist connections to Ably:

Using Cloud Proxy