Adding SRT Targets

zen master can send a source directly to an srt pull target when this method is used, the stream is not protected by the zixi protocol the following procedure describes how to add an srt target in zen master in addition, an explanation of each of the configuration parameters is given in the table below to add a new srt target in the main navigation, click targets click + add the create new target window is displayed click on srt the create new srt target window is displayed in the info section, in the name field, enter a logical name for the srt target in the tags field, select one or more of the predefined tags from the drop down list tags are used for access control by selecting a tag you are relating this target to that tag tags are associated with certain roles (through the users & roles screen), and roles, in turn, are associated with users and user groups if you would like to create a new tag, see docid\ ypm9tw81ap6nq8stkv4rd in the events configuration profile field, select from the dropdown list the profile that you would like to apply to this target by default, the default profile is applied events profiles consist of a series of rules that determine precisely how various types of events are logged and what results they trigger the target's location is used to represent it in the proper position in the map display (see docid\ sfzm6jvorvuigo7x0dnue ) by default, the location is determined automatically based on the target's ip if you would like to manually set the location of the target (optional), use the following procedure click on the edit icon next to the location field a search box is shown below the location field enter identifying info for the location (e g street address, zip code, coordinates) search results are displayed below the search box as you type click on the desired location the selected location populates the location field in the configuration section, under channel type , select the type of channel that the target will receive options are zen master channel or mediaconnect flow the target will only become functional once a channel has been assigned to it however, you can configure the target settings and then add a channel to the target after the initial configuration if you selected zen master channel , skip to step 16 if you selected aws mediaconnect flow , follow steps 10 15, then skip to step 21 for a mediaconnect flow , under aws mediaconnect flow, select a flow from the drop down list for a mediaconnect flow , in the vpc field, select the vpc interface name for a aws mediaconnect flow , the type pull (listener) is selected by default for a aws mediaconnect flow , in the port field, enter the port number of the receiving end for a aws mediaconnect flow , in the cidr allow list field, enter the range of ip addresses that should be allowed to contribute content to your source the whitelist cidr block is a range of ip addresses that should be allowed to contribute content to your source these ip addresses must be in the form of a classless inter domain routing (cidr) block; for example, 10 0 0 0/16 the source needs to be in the range covered by this cidr block any ip address within this range is allowed to send content to this flow for a mediaconnect flow , in the latency \[ms] field, enter the latency in milliseconds for a zen master channel , in the channel field, select from the drop down list the channel that will be sent to the target (optional field) for a zen master channel , in the source preference field, select one of the following options any source – the target will establish a connection to any available source in the channel upon any disconnects with the current source, the target will reconnect to another available source in the channel primary sources only – the target will establish and maintain connection to a source designated as primary in the channel upon loss of connection to that source, the target will establish a connection to another available primary source in the channel backup sources only – the target will establish and maintain connection to a source designated as backup in the channel upon loss of connection to that source, the target will establish connection to another available backup source in the channel specific source – the target will only establish a connection to the source specified by the user and will not try to connect to any other source in the channel it is not possible to select "prefer primary sources" or "prefer backup sources" this means you cannot have a target failover from a primary to a backup source in the channel unless "any source" is selected for a zen master channel , under type , select the method for sending the stream options are pull (listener) or push (caller) for a zen master channel , if you selected pull method, then do the following in the port field, enter the port that the server will listen on in the bind to local nic by cidr field , you can enter the cidr that represents the ip range where the desired nic is accessed (optional) for a zen master channel, in the latency \[ms] field, enter the latency in milliseconds for a zen master channel, under encryption , if you would like to encrypt the stream, select one of the encryption methods options are disabled (default), aes 128, aes 192 or aes 256 the encryption and decryption for srt targets is done automatically based on the password string, there is no need to enter a decryption key on the target input in the passphrase field, enter the srt stream access credentials – passphrase click show to display the passphrase if you would like to apply a pid mapping profile to this target, then in the pid mapping profile field, select the desired profile from the dropdown list for more information, see docid\ ofvpymhyvq4xqhii3umns for a zen master channel, select the prefer private broadcaster ip checkbox if you would like zen to configure connections to use private broadcaster ips when available for a zen master channel , if you selected push method, then do the following select the single output checkbox if you would like to limit the output to a single stream this setting is required for servers that do not properly support concurrent connections by selecting single output you will be losing failover functionality in the host field, enter the hostname or ip address of the receiving device in the port field, enter the target port on the receiving device in the stream id field, enter the stream id that matches the stream in the srt feed in the latency \[ms] field, enter the latency in milliseconds under encryption , if you would like to encrypt the stream, select one of the encryption methods options are disabled (default), aes 128, aes 192 or aes 256 the encryption and decryption for srt targets is done automatically based on the password string, there is no need to enter a decryption key on the target input in the passphrase field, enter the srt stream access credentials – passphrase click show to display the passphrase if you would like to apply a pid mapping profile to this target, then in the pid mapping profile field, select the desired profile from the dropdown list for more information, see docid\ ofvpymhyvq4xqhii3umns in the initial state section, select the disabled checkbox if you would like to disable this target upon initial configuration select the muted checkbox if you would like to disable error/recovery notifications for this target upon initial configuration you can enable/unmute the target at any time under protections , select the channel reassignment protection chekbox if you want to prevent the reasssignment of this target to another channel this is helpful in cases where you are switching the channel on multiple targets at once and can accidetaly select a target that should not have been switched to the new channel if you use pois, expand the scte 35 manipulation (pois) section to see additional options select enable scte 35 manipulation to enable insertion and management of scte 35 messages (used typically to create ad breaks) if you have created docid qymffvmc18nqpumz7t3d and want to apply it to this target, select it from the dropdown list note that if you select a profile, the remove existing scte 35 option will automatically be checked and non editable the way the modification works is that the broadcaster will remove all scte 35 messages, and then re insert them in original or modified form acccording to the rules defined in the profile in the null packet search window field, specify the time window in milliseconds of null packets to search for in order to insert scte 35 messages into the stream if the stream is vbr , set the value to 0 scte 35 messages can be inserted anywhere, and do not need a null packet if the stream is cbr , the downstream receiver may need a cbr stream inserting the scte 35 message into a null packet ensures the stream will remain cbr; however, it may delay the insertion of the message up to the length of the search window in the scte 35 pid field, specify a specific pid number for scte 35 insertion select remove existing scte 35 if you wish to override all existing scte 35 messages with your own note that if you select one of the docid qymffvmc18nqpumz7t3d , this option will be checked automatically and cannot be changed if you are using an external pois or esni system, enter the external id that you use to reference the zen master object in the other system see the parameters table below for more information in the pois latency offset field, if you would like to offset the pois modification path to allow for api latency, enter a value in miliseconds this value can be zero, but it establishes that this output should receive pois scte conditioning if you want the timeline adjusted (normalized) to account for insertion and/or removal of scte 35 messages, select make timeline continuous (note that the processing will add approximately 100ms to latency) if you would like to configure advanced settings, click on advanced and enter values for the desired fields see the paramaters table below for explanations of the fields click save srt target configuration parameters table true 154,100#4283c7 unhandled content type #4283c7 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type