The following ports are used by the VidiU, VidiU Mini, VidiU Pro, and VidiU Go to allow streaming with the RTMP or RTMPS protocol as well as local device control:
- outbound port 1935/TCP : outbound streaming over RTMP to most streaming providers such as YouTube Live, Vimeo or Twitch
- outbound port 80/TCP : outbound streaming over RTMP to Periscope
- outbound port 443/TCP : outbound streaming over RTMPS to Facebook Live
- outbound port 1936/TCP : outbound streaming over RTMP to LinkedIn Live (port 1935 is also used for RTMP streaming to LinkedIn)
- outbound ports 2935/TCP and 2396/TCP : outbound streaming over RTMPS to LinkedIn Live
- outbound ports 2545-2565/TCP : VidiU speed test function, not required for streaming operation -- only to run the built-in speed test to a Teradek-hosted server at a specific IP address
- outbound port 443/TCP (HTTPS) : used for authentication with the built-in providers such as YouTube Live, Facebook Live, Ustream, Livestream, and Twitch
- outbound port 53/UDP (DNS) used for DNS lookups converting hostnames to IP addresses
- local port 80/TCP (HTTP) : local access to the built-in Web UI of the VidiU for configuration and stream control, as described in this article
- local multicast DNS on 224.0.0.251 port 5353 (aka Apple's Bonjour) : service advertisement sent out by the VidiU to the local network, advertising local clients to connect with the VidiU app for iOS as described in this article
The minimum required would be RTMP and DNS to allow functionality to a remote RTMP server under the customer's own control, such as Adobe Media Server or Wowza Streaming Engine.
To ensure that you are able to send out your stream:
- the firewall on the network must not filter or block outbound communication on these ports
- the firewall on the network must not be performing content filtering / policy rules blocking access to these sites, especially sites which may be categorized as social media (Twitter/Periscope, Facebook, YouTube)
Comments
0 comments
Article is closed for comments.