BluSKY Network Port Requirements
Outgoing traffic port requirements
This article defines the BluSKY outbound network port and domains that must remain open to allow BluSKY to communicate with specific local hardware.
Platform / Access Control
Service | Protocol | Port | Destination | Purpose |
---|---|---|---|---|
BluSKY | TCP | 80, 443 | *.blub0x.com | Access to BluSKY cloud-based services |
BluSKY | TCP | 443 | *.azurewebsites.net | Access to Azure-hosted BluSKY services |
BluSKY | TCP | 3010-3033 | blub0x.cloudapp.net | Communication with BluSKY cloud services |
Time NTP Server | UDP | 123 | time.nist.gov | Synchronization of time |
Time NTP Server | TCP | 123 | time.nist.gov | Synchronization of time |
Time NTP Server | UDP | 123 | pool.ntp.org | Synchronization of time |
Time NTP Server | TCP | 123 | pool.ntp.org | Synchronization of time |
DNS Servers | UDP | 53 | dns.google.com | Domain name resolution |
DNS Servers | TCP | 53 | dns.google.com | Domain name resolution |
Azure IoT Hub | TCP | 443,5671,8883 | *.azure-devices.net | Azure IoT device host/communication |
( ' * ' means all sub-domains of this domain.)
Video/Storage/IO
Service | Protocol | Port | Destination | LVSM Version | Purpose |
---|---|---|---|---|---|
Azure Blob Storage | TCP | 443 | *.blob.core.windows.net | v2 | Storage of video data |
Security | TCP | 443 | *.azurewebsites.net | v2 | Secure access to Azure-hosted services |
Video Licensing | TCP | 443 | *.evostream.com | v2 | Video streaming license verification |
Video Licensing | TCP | 5555 | *.evostream.com | v2 | Video streaming license verification |
Azure SignalR Service | TCP | 443 | signalrhub.blub0x.com | v2 | Real-time communication service |
Public IP Checker | TCP | 443 | api.ipify.org | v2.1 | Checking public IP address |
Service Bus | TCP | 5671, 5672, 9350-9354, 443 | *.servicebus.windows.net | v2 | Cloud messaging service |
Cloud Video/HLS Up/Down | TCP | 5544, 8420, 8888 | *.blub0x.com | v2 | Video streaming up/down communication |
Azure Redis Service | TCP | 6380 | *.redis.cache.windows.net | v2 | Caching and message brokering |
Cloud Video/HLS Down | TCP | 8889, 8420 | *.blub0xSecurity.com | v2 | Video streaming down communication |
( ' * ' means all sub-domains of this domain.)
Intercom
Service | Protocol | Port | Destination | Purpose |
---|---|---|---|---|
VoIP | TCP | 22 | portsip1.blub0x.com | Secure shell access |
VoIP | UDP | 25 | portsip1.blub0x.com | Email transmission |
VoIP | TCP | 80 | portsip1.blub0x.com | HTTP communication |
VoIP | UDP | 123 | portsip1.blub0x.com | Synchronization of time |
VoIP | TCP | 443 | portsip1.blub0x.com | Secure communication (HTTPS) |
VoIP | UDP | 5060 | portsip1.blub0x.com | SIP (Session Initiation Protocol) |
VoIP | TCP | 5061, 5062, 5063, 5065 | portsip1.blub0x.com | SIP over TLS (Transport Layer Security) |
VoIP | UDP | 3478, 3479 | portsip1.blub0x.com | STUN (Session Traversal Utilities for NAT) |
VoIP | UDP | 4000-5999 | portsip1.blub0x.com | RTP (Real-time Transport Protocol) |
VoIP | TCP | 8080, 8081 | portsip1.blub0x.com | Alternative HTTP communication |
VoIP | TCP | 8881 | portsip1.blub0x.com | Alternate communication port |
VoIP | TCP | 8887, 8888 | portsip1.blub0x.com | Alternate communication ports |
VoIP | TCP | 8899, 8900 | portsip1.blub0x.com | Alternate communication ports |
VoIP | TCP | 9333 | portsip1.blub0x.com | Alternate communication port |
VoIP | UDP | 10000-20000 | portsip1.blub0x.com | High-range RTP communication |
VoIP | UDP | 25000-35000 | portsip1.blub0x.com | Mid-range RTP communication |
VoIP | UDP | 45000-64999 | portsip1.blub0x.com | High-range RTP communication |
Software Updates
Service | Protocol | Port | Destination | Purpose |
---|---|---|---|---|
Software Updates | TCP | 443 | registry.npmjs.org | Downloading software updates |
Software Updates | TCP | 443 | v8.dev | Downloading V8 engine updates |
Software Updates | TCP | 443 | drive.google.com | Accessing software updates on Google Drive |
Software Updates | TCP | 443 | bb0xdockerhub.azurecr.io | Downloading software updates |
Camera Discovery
Following traffic should be allowed between NVR and every LAN segment where cameras are present.
Service | Protocol | Port | IP Multicast Address | Purpose |
---|---|---|---|---|
WS-Discovery | TCP | 3702 | 239.255.255.250 | Web Services Dynamic Discovery |
WS-Discovery | TCP | 3702 | 239.255.255.250 | Web Services Dynamic Discovery |