Purpose of This Document
This questionnaire helps identify which streaming protocols and network services your WINK deployment will require. By completing this form, you'll have a clear understanding of the firewall rules and ports that need to be configured for your specific use case.
Instructions: Check the boxes next to the services you need. Services marked as REQUIRED are essential for basic operation. Services marked as OPTIONAL depend on your specific requirements.
1. IP Address Planning
⚠️ Important: Dual IP Address Requirement
WINK Forge and WINK Media Router each require 2 IP addresses for proper operation:
- Management Interface: For web UI, API access, and administrative functions
- Media Interface: For streaming traffic (RTSP, RTMP, HLS, etc.)
Total IP addresses needed: 4 (2 per appliance)
| Appliance | Interface Type | IP Address | Subnet Mask | Gateway |
|---|---|---|---|---|
| WINK Forge | Management | |||
| WINK Forge | Media | |||
| WINK Media Router | Management | |||
| WINK Media Router | Media |
DNS Servers:
NTP Servers (if using internal):
2. Core Administrative Services
Ports: TCP 443 (primary web/API), TCP 444 (admin interface)
Direction: Inbound to both WINK Forge and Media RouterAdministrative access to the WINK web interface and REST API. Port 443 handles primary web UI and API calls. Port 444 is the dedicated admin interface.
Port: UDP 123
Direction: Outbound from both appliancesNetwork Time Protocol for accurate timekeeping. Critical for SSL certificate validation, licensing, and timestamp synchronization across distributed systems.
3. Streaming Distribution Protocols
Ports: TCP 80 (HTTP), TCP 443 (HTTPS - recommended)
Direction: Inbound to WINK Media Router
Appliance: WINK Media RouterApple's HTTP Live Streaming protocol. The industry standard for web browsers, mobile apps (iOS/Android), and smart TVs. Delivers adaptive bitrate streaming with 5-30 second latency.
✓ Browser support: Universal (Chrome, Firefox, Safari, Edge, all mobile browsers)
✓ Scalability: Excellent (supports CDN distribution for millions of viewers)
✓ Latency: 5-30 seconds (configurable)
Ports: TCP 554, TCP 8554 (alternative), UDP 554 (UDP transport)
RTP Media Ports: UDP 1024-32000 (dynamic range for actual media streams)
Direction: Inbound to WINK Forge (for camera inputs), Inbound/Outbound to WINK Media Router (for distribution)
Appliance: Both WINK Forge and WINK Media RouterReal-time streaming protocol used by IP cameras and professional VMS systems. Provides low-latency access (typically <1 second) for live monitoring and integrations with third-party video management systems.
✓ Client support: VLC, professional VMS platforms, dedicated RTSP players
✓ Scalability: Moderate (typically 100-500 concurrent viewers per server)
✓ Latency: Sub-second to 1 second
Do you need to enable RTSP? Yes, for camera inputs Yes, for distribution to partners/VMS
Port: TCP 1935
Direction: Inbound/Outbound to both appliances (Forge publishes to Router on 1935)
Appliance: Both WINK Forge and WINK Media RouterAdobe's legacy streaming protocol, still widely used for live broadcasting. Commonly used for encoder-to-server publishing (e.g., OBS Studio) and restreaming to social media platforms (YouTube Live, Facebook Live, Twitch).
✓ Client support: OBS Studio, Wirecast, legacy Flash-based players
✓ Scalability: Moderate (100-1000 concurrent viewers)
✓ Latency: 2-5 seconds
Use case: OBS/Encoder publishing Social media restream Internal between Forge and Router
Port: UDP 9000 (default, configurable)
Direction: Inbound/Outbound to both appliances
Appliance: Both WINK Forge and WINK Media RouterLow-latency streaming protocol optimized for unreliable networks. Features built-in encryption (AES-128/256) and automatic error recovery (ARQ). Ideal for contribution feeds over the internet, long-distance streaming, and lossy network conditions.
✓ Client support: OBS Studio, FFmpeg, VLC, professional encoders (Haivision, Makito)
✓ Scalability: Point-to-point or small groups
✓ Latency: Sub-second to 2 seconds (configurable)
SRT Port (if different from default 9000):
Port: TCP 8889 (signaling)
ICE/STUN/TURN Ports: UDP 1024-65535 (ephemeral ports for WebRTC connections)
Direction: Inbound to WINK Media Router
Appliance: WINK Media RouterWeb Real-Time Communication protocol for ultra-low latency browser-based streaming. Uses WHIP (WebRTC-HTTP Ingestion Protocol) for publishing and WHEP (WebRTC-HTTP Egress Protocol) for playback. Requires STUN/TURN servers for NAT traversal.
✓ Client support: Modern web browsers (Chrome, Firefox, Safari, Edge)
✓ Scalability: Limited without SFU (100-200 viewers typical)
✓ Latency: <500ms glass-to-glass
4. VMS & Third-Party Integration
Ports: TCP 8000-8016 (primary pool), TCP 8100-8116 (secondary pool), TCP 8200-8216 (Omnicast legacy)
Direction: Inbound to WINK Forge
Appliance: WINK ForgeDirect integration with Genetec Security Center and Omnicast VMS platforms. Each port represents one available stream/channel to the VMS. Up to 48 concurrent streams supported across three port ranges (16 ports each).
✓ Each port = one simultaneous stream to VMS
Number of Genetec streams needed: (max 48)
5. Camera Source Connectivity
WINK Forge must be able to reach your IP cameras on the camera network. Typically cameras are accessed via RTSP (TCP/UDP 554) or RTMP (TCP 1935).
Camera Subnet/VLAN:
Camera Protocol: RTSP (TCP 554) RTSP (UDP 554) RTMP (TCP 1935) Other:
Number of cameras:
Are cameras on the same subnet as WINK appliances? Yes No (firewall rules required)
6. Deployment Summary
Expected concurrent viewers:
Peak usage time:
Public internet access required? Yes No (internal only)
External agencies/partners requiring access:
Preferred authentication method for external access: OTP (One-Time Password) IP Whitelisting Other: