This page documents the common ports that IdeaLayer Engine uses in various features.
| Component | Ports/Protocol | Description |
| Built-in Web Browser | TCP 80 (HTTP), TCP 443 (HTTPS) | The web browser in IdeaLayer will connect to external web pages through TCP port 80/443 by default, just as any web browser does. |
| License activation | TCP 443 (HTTPS) | Uses an HTTPS connection back to our licensing server. License activation is only required once at the time of installation. |
| Crash reporting | TCP 8000 (HTTP) | Sends details about crashes if and when they happen. This can be disabled if required. The crash reports (a binary file) have no sensitive data and just provide internal details of the code running. |
| File transfer between Engine instances (‘flicking’) | TCP 9195 or TCP 9199 | Touchscreen instances of the software listen on TCP 9195 and Viewer instances of the software listen on TCP 9199. These are both configurable (and are often changed to run multiple instances of the Viewer on a single machine - i.e. having each instance run on a different port). The protocol is a simple text-based protocol that sends JSON-based metadata and also binary files. |
| Streamed Resources | TCP 10000+ | Streamed resources, such as web browser windows, will use port 10000 or above to send a TCP video stream. Each concurrent stream uses a different port. The start port is configurable with STREAMED_RESOURCE_FIRST_LISTEN_PORT. Typically, ports used in a range of between 10000 and 10200 should be expected, depending on how long Engine is left running. |
| Collab Share web server | TCP 80 (HTTP) | Collab Share is an optional feature that enables a small web server on the touch screen for easy sharing of documents (e.g. from a phone, laptop computer) to the Collab session. The devices must be able to connect to the web server on the IdeaLayer device on port 80, on the same local network. The PIN code for authentication changes each Collab session. |
| Emailer (optional) | TCP 25/465/587 (SMTP) | The Email function enables documents on the screen to be emailed to participants in a meeting. It uses a SMTP connection to a configurable SMTP server. The configuration (SMTP host, username, password, authentication mechanism) is set in the Engine configuration file. |