Adding Zixi Push Targets

t zen master enables you to 'push' a channel to an zixi broadcaster you can configure redundant hosts to ensure consistency to learn more about redundancy in zen master see docid\ k9mukecy4pzgeowujdrhh the following procedure describes how to add a zixi push target in zen master in addition, an explanation of each of the configuration parameters is given in the table below to add a new push target in the main navigation, click targets click + add the create new target window is displayed click on zixi the create new zixi target window is displayed new zixi push target in the info section, in the name field, enter a logical name for the push 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, in the channel field, select from the drop down list the channel that will be sent to the target (optional field) 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 in the type section, select push the fields relevant for push targets are shown under channel type, verify that zen master channel is selected (default) 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 – select one of the specific sources listed the target will only establish a connection to the selected source 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 under redundancy , select one of the following alt host in case of error, the stream will failover to the alternative host, defined in the alt target host field bonding uses all the nics available on the broadcaster in parallel you can select between auto bonding and custom bonding in the target host field, enter the hostname of the primary broadcaster in the alt target host field, enter the hostname of a backup broadcaster (optional field) if you are using dtls on the server side but don't have access to the certificate, then select the ignore dtls certificate checkbox even when this option is selected, the stream is still transmitted in the encrypted format, you are only losing the ability to verify the identity of the source in the stream id field, enter the stream id as defined in the broadcaster in the password field , enter a password for accessing the stream (optional field) in the latency field, enter the latency in milliseconds 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 encryption section, 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 if encryption was selected, in the encryption key field, enter an encryption key that will be used to encrypt the connection or click random to generate a random encryption key 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 scte 35 manipulation (pois) options select enable scte 35 manipulation to enable insertion and management of scte 35 messages (used typically to create ad breaks) 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 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 zixi push target configuration parameters table parameter description info name specify a name for the zixi pull target in zen master tags 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 events configuration profile select from the dropdown list the profile that you would like to apply to this target by default, the default profile is applied note events profiles consist of a series of rules that determine precisely how various types of events are logged and what results they trigger location (optional) 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 enter identifying info for the location (e g street address, zip code, coordinates) and select the desired location from the suggestions that are shown configuration type select push channel type verify that zen master channel is selected (default) channel (optional) select from the drop down list the channel that will be sent to the target note 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 source preference select from the drop down list one of the following 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 – select one of the specific sources listed the target will only establish a connection to the selected source and will not try to connect to any other source in the channel note 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 redundancy select one of the following alt host in case of error, the stream will failover to the alternative host, defined in the alt target host field bonding uses all the nics available on the broadcaster in parallel target host enter the hostname of the primary broadcaster alt target host (optional) enter the hostname of a backup broadcaster ignore dtls certificate select one or more of the receiver's outputs note if you would like to remove the selected receiver output, click on the ‘ x ’ in the receiver output textbox stream id enter the stream id as defined in the broadcaster password enter a password for accessing the stream latency \[ms] enter the latency in milliseconds or leave empty to use remote configuration (default) note if you would like to remove the selected broadcaster output, click on the ‘ x ’ in the broadcaster output textbox pid mapping profile (optional) if you would like to apply a pid mapping profile to this target, then select the desired profile from the dropdown list to create a new pid mapping profile, see docid\ gftcayurpl7dinouyd14z 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 encryption key (for encryption enabled) enter an encryption key that will be used to encrypt the connection or click random to generate a random encryption key initial state disabled select this checkbox if you would like to disable this target upon initial configuration muted select this checkbox if you would like to disable error/recovery notifications for this target upon initial configuration protections channel reassignment protection select this option 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 scte 35 manipulation (pois) enable scte 35 manipulation select to enable insertion and management of scte 35 messages (used typically to create ad breaks) null packet search window (ms) 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 scte 35 pid specify a specific pid number for scte 35 insertion remove existing scte 35 select if you wish to override all existing scte 35 messages with your own external id the id that is used when integrating zen master with an external esni/esam server the id is whatever you use in the external system to reference the zen master object, though depending on what you are doing, it might serve different purposes used by pois to identify the source of scte 35 messages used by esni to identify the audience that is receiving the content regardless, the external id is the same whether entered in the scte 35 manipulation settings or the advanced settings, and you cannot enter different values in the two fields pois latency offset \[ms] 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 make timeline continuous select this option to normalize the timeline, making it continuous note that it will add 100ms latency and it creates a variant of the input, which means that it doubles your input advanced billing code if you would like to track usage for this target, enter your billing code details, see docid\ lalxj n928tegcpdpbirj (supported for broadcasters v14 8+) billing password enter the password that corresponds to this billing code traffic shaping traffic shaping is a network management technique used to control and optimize the flow of data it ensures a smooth streaming experience by prioritizing video traffic and managing bandwidth usage set at 0 (default) for no traffic shaping, or 1 for automatic traffic shaping note this option is only for sources for zixi broadcaster 18 2 or later max fec overhead specify a limit to the additional data that can be added for fec (forward error correction) defailt 30% available for sources for zixi broadcaster 18 2 or later frame thinning select this option to allow non critical frames to be dropped to reduce latency default value is 0 (no frame thinning) note this option is available for push sources only coming for broadcaster 18 2 or later adaptive fec adaptive fec improves the efficiency of fec by adjusting the amount of extra data sent according to network conditions by default adaptive fec is turned on, but there are some cases where fixed fec is needed and you will want to disable it some examples of cases where fixed rate fec is preferable when network bonding is used, and one of the network links periodically fails when low latency is required, the lost packet rate is high, and lost packet rate is high the round trip time is long (meaning arq can't get replacements for lost packets quickly enough) mtu specify the maximum transmission unit (largest data packet that a network connected device will accept) in bytes external id the id that is used when integrating zen master with an external esni/esam server the id is whatever you use in the external system to reference the zen master object, though depending on what you are doing, it might serve different purposes used by pois to identify the source of scte 35 messages used by esni to identify the audience that is receiving the content regardless, the external id is the same whether entered in the scte 35 manipulation settings or the advanced settings, and you cannot enter different values in the two fields