DNS, IP Addresses, and Ports
Your PDF has been created and will start downloading in a few seconds! If the download doesn't start, 
Error. Something went wrong. Please Last updated on Jul 27, 2021
Haivision Hub assigns IP addresses and UDP ports dynamically from a regional pool of available resources.
Consequently, all required connection information from a saved and stopped route is accessible (such as: DNS names, IPs, ports, passphrases). This allows you to pre-configure services and equipment that need to connect with the route prior to the route being started.
All hublet URLs (no matter the protocol) will include the Haivision domain: routes.hub.haivision.com.
1
For example:
srt://hai-XXXXX-testrouteA-output-607984c3.routes.hub.haivision.com:32331
DNS Names
The Domain Name Server (DNS) is hosted in a Haivision-controlled DNS zone: routes.hub.haivision.com. The DNS records for your route components are resolvable after the route completes provisioning.
IP Address Ranges
Select from the following IP address ranges to build firewall rules that allow outbound access. DNS names are assigned at route creation and registered to IP addresses at route start.
- For SRT hublets, use an IP within the range listed below (based upon the Haivision Hub region).
- For RTP/TS/RTP/RTMP/Akamai hublets, no change. The public IP is assigned from the IP ranges of the different Azure regions. Reference the Microsoft article: Azure IP Ranges and Service Tags – Public Cloud.
To view the IP ranges based upon the Haivision Hub regions, choose the appropriate Zone tab below:
North America / European Union
| North America | |
| East US | 52.249.234.176/28 52.249.234.160/28 |
| East US 2 | 20.186.165.16/28 20.186.165.32/28 |
| Central US | 20.80.114.64/28 20.80.114.128/28 |
| North Central US | 20.88.14.112/28 20.88.15.80/28 |
| South Central US | 20.88.219.144/28 20.88.219.224/28 |
| West US | 138.91.230.160/28 138.91.230.0/28 |
| West US 2 | 20.51.99.224/28 20.51.99.96/28 |
| Canada Central | 20.200.95.48/28 20.200.94.224/28 |
| Europe | |
| North Europe | 20.93.60.32/28 20.93.59.224/28 |
| West Europe | 20.103.112.16/28 20.103.112.32/28 |
| France Central | 20.74.101.112/28 20.74.100.240/28 |
| UK South | 20.90.236.0/28 20.90.235.224/28 |
Asia/Pacific
| South Asia | |
| Central India | 20.204.111.144/28 20.204.108.80/28 |
| South India | 52.140.34.0/28 52.140.33.224/28 |
| East and Southeast Asia | |
| East Asia | 13.75.50.32/28 13.75.50.48/28 |
| Southeast Asia | 104.43.50.112/28 104.43.51.16/28 |
| Korea Central | 52.141.44.64/28 52.141.44.80/28 |
| East Japan | 20.48.72.48/28 20.48.72.32/28 |
| Oceania | |
| Australia East | 20.92.177.112/28 20.92.177.128/28 |
Rest of World
| South America | |
| Brazil South | 20.201.30.32/28 20.201.29.208/28 |
| Middle East / North Africa | |
| UAE North | 20.74.163.160/28 20.74.162.48/28 |
UDP Port Assignment
Once the Hub route is stopped, the hublets retain the assigned UDP ports for pre-defined period of time. The expiration timer is reset each time a route is started/stopped.Use the following range of UDP ports for Input and Output components. UDP ports are assigned to components at route creation. Routes will retain the UDP port initially assigned – even after the route is stopped.
- SRT hublets – UDP ports on each node range from 30000 to 32767.
- RTP/TS/RTP/RTMP hublets – No change; UDP ports are user-configurable.
NOTES
-
Before the recent switch to
routes.hub.haivision.com, hublet URLs includedcloudapp.azure.com. ↩