> For the complete documentation index, see [llms.txt](https://manual.fotokite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.fotokite.com/system-profile/remote-livestream/technical-requirements.md).

# Technical Requirements

For seamless operation of the live streaming service, the user installation must meet specific requirements:

## Fotokite Sigma Install Requirements

When internet connectivity is provided to the Fotokite Sigma via the customer’s own upstream Wi-Fi or Ethernet connection, the connection must meet the following requirements:

* Bandwidth: 2 MBit/s or greater (see "Bandwidth" below for context)
* Max. 0.6GiB of data usage/hour (see "Bandwidth" below for context)
* Latency: < 200ms
* Open ports (outbound from the Sigma System to the internet):
  * TCP
    * 443: HTTPS, to *coordinator.live.fotokite.com*
    * 8189: Websocket, to *\*.sfu.live.fotokite.com*
  * UDP
    * 12345: latencytest, to *\*.sfu.live.fotokite.com*
    * 20000-30000: video WebRTC/RTSP, to *\*.sfu.live.fotokite.com*

If the cellular modem built into the Sigma System is used for streaming, those requirements are already fulfilled if there is sufficient cellular reception at the site of operation.

## End User Web Browser

The Remote Stream webclient is compatible with most modern devices, provided that the internet connection and web browser are up to date.

It is currently being successfully tested with the following browsers:

| Operating System                             | Browser                      |
| -------------------------------------------- | ---------------------------- |
| <p>Windows 11 Pro<br>OS Build 22631.5039</p> | Chrome Version 135.0.7049.42 |
|                                              | Firefox 137                  |
| Mac OS Sonoma 14.1.1                         | Safari 17.1                  |
|                                              | Firefox 137                  |
| iPad OS Version 18.1.1                       | Safari                       |
| Android Version 14                           | Chrome 134.0.6998.135        |

## Networking Requirements

Open ports (from browser to internet). A **list of static IP addresses** for *\*.sfu.live.fotokite.com* is available, see [#static-ip-addresses](#static-ip-addresses "mention").

* TCP
  * 80: HTTP, to *live.fotokite.com* (will redirect to HTTPS immediately)
  * 443: HTTPS, to *live.fotokite.com* and *coordinator.live.fotokite.com*
  * 8189: WebSocket, to *\*.sfu.live.fotokite.com*
* UDP
  * 20000-30000: video ICE/DTLS/RTP/RTCP, to \*.sfu.live.fotokite.com

## Static IP Addresses

There is a list of static IP addresses for the *\*.sfu.live.fotokite.com* servers. Customers can configure their firewalls to allow the ports listed above inbound from this list.

No static IPs are available for *\[coordinator.]live.fotokite.com*. The browser will walk to those endpoints only via HTTP(S), TCP port 80/443, which should already be allowed by standard firewalls.

Before using the list below in their Firewall configuration, the customer or Fotokite customer representative must fill [this Google Form](https://forms.gle/ozzUMEJBcvoiuxc9A) (<https://forms.gle/ozzUMEJBcvoiuxc9A>) so that Fotokite IT staff knows who to contact in case the list changes.

Log of changes the list:

* 2022-11-19: Initially published static IP addresses list
* 2022-09-22: Removed some addresses from the list, current list is now a subset of initial list (no configuration change needed)

**List:**

```
35.206.142.200,
35.210.17.64,
35.210.176.1,
35.210.49.131,
35.210.6.255,
35.212.101.252,
35.212.104.237,
35.212.66.7,
35.212.75.217,
35.212.95.7,
35.215.108.7,
35.215.118.83,
35.215.126.168,
35.215.95.111,
35.215.97.234,
35.216.130.161,
35.216.187.169,
35.216.224.113,
35.216.246.118,
35.216.247.229
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://manual.fotokite.com/system-profile/remote-livestream/technical-requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.