ZEN MASTER April 2024 RELEASE NOTES

the following updates will be included in the zen master april 1, 2024 release features the following new features were implemented in this release new details ui for sources • zen master source details screens are now updated to align with broadcaster screens ui, this includes o persistent vital statistics information in the top panel o configurable widget's view o vlc and webrtc playback from the top panel thumbnails on targets • where applicable, target details pages now include thumbnails auto login into broadcasters, zecs, feeders, and receivers • when accessing the gui of broadcasters and zec’s via zen master, the system now logs users in directly without the need to copy and paste in credentials scte35 logs can be colored by type • scte 35 logs can now be optionally color coded by using the show/hide colors toggle to help with rapid identification and confirmation added the option to export scte35 ui logs • data can be downloaded as an xml report priority client support for zixi push other sources • zen master now supports the broadcaster priority dource functionality for the zixi push other source type azure public ip prefixes support • unlike aws, there is no ip pool feature in azure • azure admins will need to create a public ip prefixes pool and create public ips • the id/name of the public ip pool can be provided in the cluster settings • zen master will then create ips on demand from the pool redirection routing rules for pull requests • zen master now provides the ability to set specific routing rules for pull requests from clusters or cidr ip ranges • the rules can be accessed and created via “+add rule” button on the new “redirection rules” tab of the cluster page • rules can be applied to the client end point cluster, or ip cidr range, from where the pull request is initiated o when using ‘cluster’ the rule applies to auto pull requests only o cidr rules apply to any zixi pull request, including those from zecs, irds etc • rules are evaluated in order from lowest order to highest • the first matching rule will apply • latency is determined by the following order redirection rule latency > source auto pull/pull target latency > default 1000ms • additional notes o if there is no match, the default rule prefer public ip with dtls will be used o private/nic cidr do not support dtls and will redirect to a non dtls port o a configuration conflict is possible, such as a cluster enabled for dtls only, where a private/nic redirection will never successfully connect o it is possible to use this as feature as an allow list by creating a 0 0 0 0/0 block rule and give it the highest order in this case, any connection not matched by a rule with a lower order will finally be matched by the blocking rule additional improvements and changes the following additional improvements and changes were implemented in this release • azure broadcasters no longer use nvidia images from azure marketplace o zixi now fully manages azure images • hls ad markers moved from the events log to their own log/page in the ui • client ip is now logged for zixi push sources on connection/reconnection • zen master now shows the last time tr101/cqa stats were reset • failover sources will now recover correctly when re enabling their component sources • added optional billing code column to sources list • renamed ‘termination protection’ to ‘deletion protection’ for clarity in the scaling cluster settings • added table column selection to broadcasters sub table in clusters list • improved webrtc error handling/reporting • moved webrtc pass through mode to ‘more options’ source setting • added missing common fields to multiview source form • added max bitrate setting to demux sources • added target broadcaster configuration to failover channels • exposed threads configuration for x264 transcoding • exposed authentication options for http targets • added dtls only mode for clusters • small ui improvements bug fixes the following issues were resolved • clusters with no broadcasters are now in a gray/pending state instead of a green/ok state • fixed unnecessary restart warnings • fixed download ssh key option available and on imported keys • fixed io server host key download • fixed automation actions grayed out after some actions • fixed live events timeline becoming "shorter" on every manual refresh • fixed aws mediaconnect tr101 info not available • removed html overlay input from transcoded channels • fixed transcoding errors not generating zen master events/alerts • fixed transcoding channel transcoding errors escalating too fast • fixed issue preventing creation of failover sources when using frozen/blank video rules • fixed zen master not updating cluster dns settings when all broadcasters are in an error state • fixed invalid password detection + windows broadcaster stuck in error state • fixed tag multiviewer not working with self signed https certificates • fixed aws/azure/gcp broadcasters not launching when using redundant i/o servers • fixed issue with loading more scte 35 messages in main scte 35 log