Network and Firewall Requirements
Last updated 4/29/26
NetSpeek Edge VM Network and Firewall Requirements
LAN / Corporate Network Communications (NetSpeek Edge ↔ Intranet)
| Port | Protocol | Direction | Supported Integrations (Devices Contacted) | Purpose |
|---|---|---|---|---|
| 45 | TCP/UDP | In/Out | Sennheiser (SCPv1) | Device control & monitoring |
| 80 | HTTP | Outbound | BrightSign, NEC/Sharp, Sony, Logitech, MiddleAtlantic | Device control & monitoring |
| 443 | HTTPS | Outbound | Crestron, Vaddio, MiddleAtlantic, Logitech | Secure device control & command relay |
| 161 | SNMP | Outbound | SNMP Devices | Network device discovery |
| 1515 | TCP | Outbound | Samsung | Display control (TCP protocol) |
| 3000 | HTTP/WS | Outbound | LG WebOS | Display control |
| 3001 | HTTP/WS | Outbound | LG WebOS | Display control |
| 4000 | HTTPS | Outbound | Samsung | Embedded API control |
| 4003 | HTTPS | Outbound | Barco ClickShare | Device management |
| 8001 | HTTP/WS | Outbound | Samsung | Real-time display control |
| 8080 | HTTP | Inbound | Edge VM’s Browser Interface | Local management |
Internet Communication (NetSpeek Edge ↔ NetSpeek Cloud)
| Port | Protocol | Direction | Connectivity Provided | URLs / Endpoints | Purpose |
|---|---|---|---|---|---|
| 443 | HTTPS | Outbound | NetSpeek Cloud API | *.netspeek.ai | Configuration, metadata sync, API requests, monitoring, cloud updates |
| 443 | WSS | Outbound | NetSpeek Cloud API | *.netspeek.ai | Real-time action dispatch relay |
Outbound ports to NetSpeek platform must be open for *.netspeek.ai addresses – this is commonly referred to as a “wildcard” rule, meaning that any address ending in netspeek.ai is accessible.
Outbound Internet Communication (NetSpeek Edge ↔ Internet Services)
| Port(s) | Protocol(s) | Direction | Connectivity Provided | URLs / Endpoints | Purpose |
|---|---|---|---|---|---|
| 443 8443 | HTTPS MQTT | Outbound | Amazon Greengrass IOT services | *iot.us-east-2.amazonaws.com *iot.us-east-1.amazonaws.com | Managing OTA updates to Edge functionality |
| 443 | HTTPS | Outbound | Amazon S3 storage services | *.s3.amazonaws.com *.s3.us-east-2.amazonaws.com | File delivery for updates to Edge functionality |
Outbound ports to AWS services must be open for *. addresses as described in the table above. This is commonly referred to as a “wildcard” rule, meaning that any address in the defined Amazon Web Services namespace is accessible.
NetSpeek Platform Connectivity Requirements
Administration of the NetSpeek platform requires, in addition to allowing the Edge VM the connectivity described above, allowing the personal devices of administrators to access the URLs below.
As with the Edge VM, it is often simpler to permit *.netspeek.ai connectivity for administrator connectivity rather than permitting connectivity to the below URLs individually.
Platform Administration – Beta Environment and Tenants: https://portal.beta.netspeek.ai/
Platform Administration – Production Environment and Tenants: URL to-be-published