Wowza Video™ Real-Time Streaming at Scale provides half-second latency to all your viewers, no matter where they are. Real-time streaming is perfect for interactive use cases like video chats, auctions, e-sports, fitness, e-commerce, gambling, and more.
If your audience is fewer than 300 viewers or you want to stream in near real-time alongside other delivery protocols, you may choose to use our standard WebRTC solution.
This topic is a comprehensive guide to codecs, network ports, IP addresses, and essential Wowza Real-Time Streaming platform requirements.
Before you start
You should have access to the following items:
- A Wowza Video account. Real-time streaming is not available in the free trial.
- A RTS@S license. To enable and purchase capacity for Real-Time Streaming at Scale for your account and access the
/real_time
operations, contact 720.279.8163 or schedule a call.
Codecs
WebRTC – An internet transfer protocol that supports video codecs H.264, H.265, VP8, VP9, AV1, and the Opus audio codec. Broad support is made possible through implementations of WebRTC HTTP Ingest Protocol (WHIP).
RTMP – Internet transfer protocols that can be transmuxed to WebRTC supports only the H.264 video codec.
Read more on Broadcasting to Wowza Video™ Real-Time Streaming at Scale.
Network ports and domains
If your environment is behind a restrictive network, use the information below to configure your firewall whitelist correctly, allowing Real-time Streaming services to pass through.
Traffic Type | Ports | Type |
WebRTC connection | 443 | TCP |
WebRTC media server | 49152-65535 | UDP |
STUN/TURN servers | 443, 3478, 5349 | TCP and UDP |
RTMP publishing | 1935 | TCP |
We also recommend whitelisting the following domains:
- *.wowza.com
- *.flowplayer.com
- *.lwcdn.com
- *.cloudflare.com
- *.millicast.com
- *.twilio.com
IP addresses
Publishing
Certain customers have firewalls and need to whitelist IP servers to publish content. We do not provide a list of IP addresses because we cannot ensure the same range due to the dynamic scaling of our service. Customers with the requirement to whitelist IP ranges can refer to the region-specific IP addresses lists published by our cloud providers.
Region | IP range details |
Bangalore, India | not published by provider (Digital Ocean) |
Phoenix, AZ, USA | us-phoenix-1 |
Singapore | not published by provider (Digital Ocean) |
Sydney, Australia | ap-sydney-1 |
* See Oracle's IP list for a detailed IP range for publishing ingress servers.
STUN/TURN
STUN and TURN servers are crucial in WebRTC communication, allowing users to connect and stream content effectively. These servers follow IETF standard protocols to manage Network Address Translation (NAT) during communication sessions.
The Session Traversal Utilities for NAT (STUN) assist servers and clients in determining their public IP addresses when they are behind a NAT/Firewall. When a host wants to accept an incoming connection, it provides this public IP address as a possible connection point. If the NAT/Firewall still prevents direct connectivity between the viewer and media server, a connection is established using the Traversal Using Relay around NAT (TURN) service, which enables media relay between the two parties.
Note: STUN/TURN IP addresses were last updated 2024-11-04.
Region | IP Range Details |
Bangalore, India |
139.59.49.50 |
Ashburn, VA, USA | 129.213.172.222 141.148.39.122 193.122.165.132 129.80.107.22 129.80.49.52 141.148.63.222 150.230.164.20 150.136.130.194 |
Frankfurt, Germany | 141.144.229.61 89.168.103.9 144.24.168.81 141.147.50.224 144.24.169.241 130.162.224.118 129.159.200.0 130.162.224.21 |
London, UK | 132.226.128.169 84.8.154.194 150.230.127.97 79.72.91.241 141.147.64.72 141.147.113.177 150.230.118.111 141.147.96.45 |
Phoenix, AZ, USA | 129.153.95.186 129.146.214.35 129.153.84.129 141.148.160.171 129.153.216.166 144.24.9.249 152.70.155.112 129.146.10.49 |
Sao Paulo, Brazil | 136.248.75.56 168.138.254.134 136.248.109.105 167.234.230.239 136.248.127.209 144.22.189.247 136.248.68.90 150.230.78.100 |
Singapore | 146.190.195.233 146.190.200.127 146.190.200.155 144.126.241.168 139.59.220.163 157.230.192.175 139.59.192.127 139.59.192.132 |
Sydney, Australia | 192.9.182.131 192.9.177.241 192.9.181.7 192.9.176.25 159.13.38.8 159.13.55.70 158.178.143.49 152.69.174.63 |
In rare cases where vendor failover is required, we may use Twilio's service. Consult the Twilio's IP list for a details IP range for STUN/TURN servers.
Wowza Flowplayer
Wowza Flowplayer utilizes several subdomains. This product is deployed within the AWS infrastructure. The Amazon AWS complete list of IP ranges are available here. Additionally, we suggest checking firewall / network restrictions to enable http/3 QUIC if you have the option.
If you require the complete list of subdomains for whitelisting, refer to the list below.
- dn.flowplayer.com
- embed-input.flowplayer.com
- embed.flowplayer.com
- embed.wowza.com
- ihi.flowplayer.com
- ljsp.lwcdn.com
- player.video.wowza.com
- player.ws.flowplayer.com
- pmi.flowplayer.com
- ptm.flowplayer.com
- sai.wowza.com
- wv-cdn-00-00.wowza.com
- wv-cdn-00-01.wowza.com