--- title: Adding SRT Targets slug: zen-master/adding-srt-targets docTags: createdAt: 2024-12-27T19:19:09.545Z --- ZEN Master can send a Source directly to an SRT Pull Target. :::hint{type="info"} 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: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Targets**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Target** window is displayed. ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/LxmYOhwQV9fXXnUWIb80Z_image.png" size="80" width="730" height="1406" position="center" alt="Create New Target window" darkWidth="730" darkHeight="1406" showCaption="false"} ::: :::WorkflowBlockItem Click on **SRT**. The **Create New SRT Target** window is displayed. ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/8kr_RZ2nW02KobSxnOSOR-20251104-150219.png" size="80" width="1380" height="2908" position="center" alt="New SRT Target" darkWidth="1380" darkHeight="2908" showCaption="false"} ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a logical name for the SRT Target. ::: :::WorkflowBlockItem 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 [Creating a Tag](docId\:YpM9tw81ap6nq8sTKv4Rd). ::: ::::WorkflowBlockItem 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. :::hint{type="info"} *Events Profiles *consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::: :::WorkflowBlockItem The Target's location is used to represent it in the proper position in the Map display (see [Maps](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. ::: ::::WorkflowBlockItem 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*. :::hint{type="info"} 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. ::: :::: :::WorkflowBlockItem 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. ::: :::WorkflowBlockItem For a *MediaConnect Flow*, under **AWS MediaConnect** **Flow, **select a flow from the drop-down list. ::: :::WorkflowBlockItem For a *MediaConnect Flow*, in the **VPC **field, select the VPC interface name. ::: :::WorkflowBlockItem For a AWS *MediaConnect Flow*, the **Type ***Pull* (Listener) is selected by default. ::: :::WorkflowBlockItem For a AWS *MediaConnect Flow*, in the **Port** field, enter the port number of the receiving end. ::: ::::WorkflowBlockItem 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. :::hint{type="info"} 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. ::: :::: :::WorkflowBlockItem For a *MediaConnect Flow*, in the **Latency \[ms]** field, enter the latency in milliseconds. ::: :::WorkflowBlockItem 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). ::: ::::WorkflowBlockItem 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. :::hint{type="info"} 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. ::: :::: :::WorkflowBlockItem For a *ZEN Master Channel*, under **Type**, select the method for sending the stream. Options are: *Pull* (Listener) or *Push (Caller)*. ::: ::::WorkflowBlockItem 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. :::hint{type="info"} 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 [PID Mapping Profiles](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. :::: ::::WorkflowBlockItem 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. :::hint{type="info"} 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*. :::hint{type="info"} 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 [PID Mapping Profiles](docId\:OFVPYMHYVq4XqhIi3UMnS) . :::: :::WorkflowBlockItem In the **Initial State** section, select the **Disabled** checkbox if you would like to disable this Target upon initial configuration. ::: ::::WorkflowBlockItem Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Target upon initial configuration. :::hint{type="info"} You can Enable/Unmute the Target at any time. ::: :::: :::WorkflowBlockItem 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. ::: :::WorkflowBlockItem If you use POIS, expand the **SCTE-35 Manipulation (POIS)** section to see additional options. ![SCTE-35 Settings](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/u_kJpVt3DRHk78LSBYop7-20260326-183853.png) ::: :::WorkflowBlockItem Select **Enable SCTE-35 Manipulation** to enable insertion and management of SCTE-35 messages (used typically to create ad breaks). ::: :::WorkflowBlockItem If you have created [SCTE-35 Modification Profiles](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. ::: :::WorkflowBlockItem 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 ::: :::WorkflowBlockItem In the **SCTE-35 PID** field, specify a specific PID number for SCTE-35 insertion. ::: :::WorkflowBlockItem 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. ::: :::WorkflowBlockItem 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. ::: :::WorkflowBlockItem 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). ::: :::WorkflowBlockItem 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. ![](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/aaDdMQuZoYYyrn-lM63_5_srt-target-advanced.png) ::: :::WorkflowBlockItem Click **Save**. ::: ::::: ## SRT Target Configuration Parameters Table | **Parameter** | **Description** | | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the SRT 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 an 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 [Creating a Tag](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 [Maps](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*** | | | Channel Type | Select the type of Channel that the Target will receive. Options are: *ZEN Master Channel* or *AWSMediaConnect Flow*. | | **For *AWS MediaConnect Flow:*** | | | AWS MediaConnect Flow | Select an AWS MediaConnect Flow from the drop-down list. | | VPC | Select the VPC interface name. | | Type | Choose between Push or Pull. | | Port | Enter the number of the port on the receiving end. | | CIDR Allow List | Enter the range of IP addresses that should be allowed to contribute content to your source.
**Note**: 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 *Zen Master Channel:*** | | | Type | Select the method for receiving the stream. Options are: *Pull* or *Push.* | | 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** – 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.
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. | | ***For Pull Method (Zen Master Channel Only):*** | | | Bind to local NIC by CIDR | Enter the CIDR that represents the IP range where the desired NIC is accessed. | | Prefer Private Broadcaster IP | Select this checkbox if you would like ZEN to configure connections to use private broadcaster IPs when available. The default behavior when this is not selected is to prefer use of public IPs. Broadcasters typically have a public and private ip address for each network interface. If you pull from the public IP, the request goes out over the internet, even if the target system is on the same local private ip range. To avoid paying for unecessary egress data rates, enabling this setting tells the Broadcaster to seek for the private network connection. | | ***For Push Method (Zen Master Channel Only):*** | | | Single Output | Mark this checkbox if you would like to limit the output to a single stream. | | Host | Enter the Target port on the receiving device. | | Stream ID | Enter the Stream ID that matches the stream in the SRT feed. | | ***For All Methods:*** | | | Port | Enter the port that the server will listen on. | | Latency \[ms] | Enter the latency in milliseconds. | | Password (Zen Master Channel Only) | Enter the SRT stream access credentials – Password. Click **show** to display the password. | | Encryption (Zen Master Channel Only) | 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*.
Note: 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. | | Passphrase | If encryption is enabled (AES 128/AES 192/AES256), type the **Passphrase** that you want to use. | | 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 [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z). | | ***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.
**Note: in Broadcasters prior to v19, if the value is set to anything other than 0, the search window will be 2 seconds.** | | SCTE-35 PID | Specify a specific PID number for SCTE-35 insertion. | | Remove Existing SCTE-35 | If you wish to override any existing SCTE-35 messages with your own, you can elect to have existing ones removed. | | 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 . (Supported for Broadcasters v14.8+) | | Billing Password | Enter the password that corresponds to this billing code. | | Billing Channel ID | An optional arbitrary string - you can enter anything you want to for your record-keeping. This is **not** related to ZEN Master Channels. | | 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. | | SRT Version | Specify a version of SRT to use from the dropdown list. Note that Zixi uses the latest version and we recommend that you use that unless your systems use an earlier version that is not compatible with the latest one. |