Platform Requirements

Codecs

See the Broadcast streaming guide for additional details about supported audio and video codecs.

Network Ports

If you have an environment that is behind a restrictive network, use the following information to create the proper firewall whitelist configuration to enable the Dolby.io Real-time Streaming services to pass:

Traffic TypePortsType
WebRTC Connection443TCP
WebRTC Media Server49152-65535UDP
STUN/TURN Servers443, 3478, 5349TCP and UDP
RTMP Publishing1935TCP
RTMPS Publishing443TCP
SRT Publishing10000UDP

We also recommend whitelisting the following domains:

  • *.millicast.com
  • *.twilio.com

IP Addresses

Some customers have firewalls in place and need to whitelist IP servers for publishing content to Dolby's cloud. We don't publish a list of IP addresses as we cannot guarantee the same range as we dynamically scale up and down the service.

👍

Dedicated IP Addresses

Dedicated publishing ingest servers are possible on enterprise plans at an additional charge. If you would like to use this capability on your projects, please submit a support ticket or reach out to your sales/solutions contact to discuss.

IP Addresses with Standard Publishing

The service always has servers running ready to receive streams. Unless you are using our Real-time Cloud Transcoder, you are using this method to publish. With RTMP or SRT you use a DNS value (such as rtmp://rtmp-auto.millicast.com:1935/v2/pub for Dolby to automatically determine the closest region, or a regional DNS entry such as rtmp://rtmp-iad-1.millicast.com:1935/v2/pub as an example for Ashburn, VA.) WebRTC uses the same region detection method based on the Publishing token settings.

For this method of publishing, we dynamically manage the servers for you and cannot guarantee the range of IP addresses used. Customers with the requirement to whitelist IP ranges can refer to the region-specific IP addresses lists published by our cloud providers.

You can access a programmatic list of our regions and their abilities with the Get Clusters API.

Dolby RegionAPI IDIP Range Information
Bangalore, Indiablr-1not published by provider (Digital Ocean)
Ashburn, VA, USAiad-1us-ashburn-1
Frankfurt, Germanyfra-1eu-frankfurt-1
London, UKlon-1uk-london-1
Phoenix, AZ, USAphx-1us-phoenix-1
São Paulo, Brazilsao-1sa-saopaulo-1
Singaporesgp-1not published by provider (Digital Ocean)
Sydney, Australiasyd-1ap-sydney-1

See Oracle's IP list for a detailed IP range for publishing ingress servers.

IP Addresses for STUN/TURN

See Twilio's IP list for a detailed IP range for STUN/TURN servers.

IP Addresses with Cloud Transcoders

For customers using our real-time cloud transcoder, a static IP address is provisioned for the duration that the machine is provisioned and in use. The IP address can be found in the Transcoding section of the dashboard or with the Cloud Transcoder. If the instance is restarted it is possible it will use a new IP address. A DNS name is also provided for these instances.

Restricted Territories

The following table lists regions that are currently restricted from full access to Dolby Streaming APIs.

Country / Region / EntityISOAccount creationPortal accessStreaming APIs accessTransact paymentReason
Belarusian banksN/AN/AN/ASanctioned banks are blocked by StripeNoUS sanction
ChinaCN-156YesYesYesNo active block, requires consultationBusiness decision
CubaCU-192NoNoNoNoUS sanction
IranIR-364NoNoNoNoUS sanction
North KoreaKP-408NoNoNoNoUS sanction
RussiaRU-643NoNoCustomers are blocked.
API users are not blocked.
NoBusiness decision
Russian banksN/AN/AN/AAll banks are blockedNoUS sanction
SudanSD-729NoNoNoNoUS sanction
Syria SY-760NoNoNoNoUS sanction
Ukraine - CrimeaUA-43NoNoNoNoUS sanction
Ukraine - DunbassUA-09

UA-14
NoNoNoNoUS sanction
Ukraine - SevastopolUA-40NoNoNoNoUS sanction