Release Notes 1.10.129

Haivision Hub Release 1.10.129 Update

Component Versions

Hub: 1.10.129.657edc42
Hub API: 1.0.55.0

This latest release to Haivision Hub focuses on improving public IP and port allocation handling, error descriptions for route provisioning as well as fixes for Makito telemetry visualization.

What's New

Introduction of nodeIP mode. Improved procedure for assigning Public IPs and Ports to the Hublets.
For subscriptions configured with nodeIP, the following changes are applicable:
- Hublet URL (all protocols) will start with Haivision domain: routes.hub.haivision.com
- SRT hublets will get a UDP port in the range from 30000 to 32767.
- In this version, the port will be allocated to a hublet permanently.
- For SRT hublets, short ranges of public IPs will be used in each hub region.
Enhancements to error description for route provisioning failure due to time outs.
Fixes for the Makito telemetry visualization.

Known Limitations

For subscriptions configured with nodeIP mode:
- Changing the region on an existing hublet is not supported (alternative is to recreate the hublet)
- UDP port booking does not expire.
RTMP hublet supports streams with a single audio track only.
Makito video preset has no validations for max bitrate.
Makito devices will need to be repaired do to updates to authorization flow.
When performing bulk operations on routes, some of the status update messages may be missed.
Makito preset creator: Intra-Refresh with framing set to I-frame only GOP is available, but not a valid configuration for Makito X/X4 devices. Configuring this combination will cause the route to fail to provision.
Opening the same route with a Makito Hublet on multiple browser tabs simultaneously makes the telemetry being displayed intermittent.
Bulk actions on notifications have been disabled due to an issue that has been detected. These will be re-enabled in an upcoming release.
Notifications are sent to every user in the active Hub subscription only.
RTP FEC-specific telemetry is not supported.
RTMP hublets in consumer mode reports connected irrespective of the input signal.
RTP output hublet status does not consider the status of the external connections.
Instant bitrate displayed in the topology view is not accurate for internal connections.
Connection state for internal connections is not correctly updated when there is no input signal.
Subscription selector for admins – number of routes is not updated.

API Release: 1.0.55.0

What’s New

hubAPI - payload in the StopHubletRouteRequestDTO is now optional.