DNS, IP Addresses, and Ports
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.
Content Formatting Macros for Confluence cannot be exported to this format.
For example:
srt://hai-XXXXX-testrouteA-output-607984c3.routes.hub.haivision.com:32331
Topics Discussed
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.
Inbound 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.
Outbound IP Addresses
For outbound connections, the HUB uses a static, single outbound IP per region. This applies to all the Hublets that use a caller connection to an external destination: Akamai Hublet, RTMP Output Hublet, SRT Output Hublet in Caller mode, etc.
To view the IP ranges based upon the Haivision Hub regions, choose the appropriate Zone below:
To view the static IP addresses for each HUB region, choose the appropriate Zone below:
UDP Port Assignment
Once the HUB route is stopped, the Hublets retain the assigned UDP ports for a 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
Content Formatting Macros for Confluence cannot be exported to this format.