Adding a Source - UDP/RTP

zen master can receive a source directly from a udp/rtp input when this method is used, the stream is not protected by the zixi protocol the udp streams can be one of the following types udp – plain udp rtp (real time transport protocol) fixes packet reordering (when possible) and supports use of fec (forward error correction) the following procedure describes how to add a udp/rtp source in zen master in addition, an explanation of each of the configuration parameters is given in the table below to add a udp/rtp source in the main navigation, click sources click + add the create new source selection window is displayed create new source selection window click on udp/rtp the create new udp/rtp window opens new udp/rtp source in the info section, in the name field, enter a unique name to identify this source in the system 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 source 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 in the events configuration profile field, select from the dropdown list the profile that you would like to apply to this source 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 source'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 source's ip if you would like to manually set the location of the source (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 udp/rtp configuration section, if your input stream uses rtp protocol, then select the use rtp protocol checkbox using rtp protocol fixes packet reordering (when possible) and supports use of fec (forward error correction) if you selected the use rtp protocol checkbox, then if you would like to use fec, then select the use forward error correction checkbox when fec is used, repair packets are sent on additional ports, enabling packet recovery if you selected the use rtp protocol checkbox, then if you would like to preserve the rtp headers (which include the timestamps and sequences) and propagate them the output, then select the preserve rtp headers checkbox if you would like to join a multicast group, in the multicast address field enter the multicast address the multicast address should be in the range of 224 0 0 0 239 225 255 255 if you entered a multicast address, then, in the source specific multicast field, you can specify a particular ip from which you will accept data in the port field, specify the port to listen on for the incoming content this port must be open on all firewalls between the ingest cluster and the input device in the max bitrate field, select from the drop down list the maximum bitrate for this source in the source configuration section, in the ingest cluster field, select from the drop down list one of the available ingest clusters as the destination for the source in the target broadcaster/s field, select your broadcaster preference either select a specific broadcaster to be used or specify your preference for using primary vs backup broadcasters, options are prefer primary broadcasters, primary broadcasters only, backup broadcasters only or prefer backup broadcasters for managed clusters, it is not recommended to select a specific broadcaster, as the broadcaster’s availability may not remain stable in the input nic field, if you would like to specify which nic is used, then select the ip of that nic from the drop down list by default, any is selected if you would like to apply a pid mapping profile to this source, then in the pid mapping profile field, select the desired profile from the dropdown list using this method creates a single source in zen master with pid mapping applied if you would like to maintain a source with the original pids and create an additional source with pid mapping (e g if you want to create several different pid mapped variations), then use the method described in adding a source pid mapping docid\ gockl3upsd8v14ia2an6g to create a new pid mapping profile, see adding pid mapping profiles docid\ gftcayurpl7dinouyd14z select the alert on pid changes checkbox if you would like to generate email notifications whenever a pid change is detected select the log scte 35 checkbox if you would like to log scte 35 markers for this stream to log scte 35 markers, scte 35 needs to be enabled both on the ingest cluster and on the source configuration scte 35 logging is only available for v13 1 40262+ broadcasters if log scte 35 was selected, you can choose to receive alerts for scte 35 markers by selecting the enable scte 35 alerts checkbox additional scte 35 options are available when you expand the scte 35 manipulation section scte 35 manipulation here you can enable scte 35 insertion set the scte 35 pid remove any existing scte 35 messages from the stream replace any existing scte 35 messages with null in the public output field, if you would like to allow access to the stream directly through a supported player, select the allow checkbox if you selected the allow checkbox, then enter a password in the password field to authenticate access to the stream if you would like to enable content analysis (cqa), verify that the enable content analysis checkbox is selected (default) it is generally recommended to enable content analysis unless it is causing technical problems if content analysis is disabled, the system won't detect errors in the video and audio content of the stream and won't generate warnings for such events even when content analysis is disabled the system will still detect tr101 errors in the stream if you would like to monitor cea 608/cea 708 closed captions, select monitor cea 608/cea 708 checkbox monitoring cea 608/cea 708 closed captions requires using a version 14 4 or newer broadcaster if you would like to disable auto pull, select the disable auto pull checkbox disabling auto pull will lock channels using this source to the source's ingest cluster and targets to the source's current active broadcaster this setting only applies to pass through channels if auto pull is enabled , in the auto pull latency \[ms] field, specify the maximum latency for auto pull actions (default 1000 ms) in the webrtc playback section, select the desired playback method webrtc enables you to monitor the stream via web browsers and mobile applications with real time communication (rtc) webrtc needs to be activated independently for each source in zen master (by default it is disabled) select one of the following options disabled users will not be able to view this source using webrtc (default) pass through passes the stream through to webrtc without transcoding this option can only be used if the input stream is already in a webrtc compliant format (video h 264 codec with baseline or main profile and no b frames, audio opus codec) auto zen master automatically transcodes the stream using the optimal profile for each specific user in this option zixi broadcaster will decode the video, transforming it into raw frames, which will be passed to the webrtc library, where it will be re encoded for each individual user best quality however, if monitored by multiple users this can consume extensive resources 1080p/720p/480p/360p zen master transcodes the stream to a webrtc compliant profile with the specified resolution the transcoding is done by zixi broadcaster's transcoder this method requires a zixi broadcaster with x264 or nvidia for transcoding this method allows many users to monitor the stream without encoding separately for each individual user, which saves cpu capacity since there is only one stream version, it is recommended to encode to a low resolution and low bitrate so that the stream will be viewable by all users monitoring the stream in the initial state section, select the disabled checkbox if you would like to disable this source upon initial configuration select the muted checkbox if you would like to disable error/recovery notifications for this source upon initial configuration you can enable/unmute the source at any time if you would like to adjust the advanced settings, click advanced the advanced settings fields are displayed if you would like to track usage for this source, enter your billing code details see billing codes docid\ lalxj n928tegcpdpbirj in the auto pull mtu field, specify the maximum transmission unit (largest data packet that a network connected device will accept) in bytes for the auto pull to set the detection of frozen video, in the frozen video minimal duration field, specify the default minimal duration in seconds of frozen video after which the broadcaster will trigger a frozen video alert default 10 seconds this setting is supported for broadcaster version 16 3 and higher to set the detection of blank video, in the blank video minimal duration field, specify the default minimal duration in seconds of blank video after which the broadcaster will trigger a blank video alert default 10 seconds this setting is supported for broadcaster version 16 3 and higher click save udp/rtp source configuration parameters table parameter description info name specify a name for the udp/rtp source 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 source 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 source 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 source'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 source'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 udp/rtp configuration use rtp protocol if your input stream uses rtp protocol, then select this checkbox using rtp protocol fixes packet reordering (when possible) and supports use of fec (forward error correction) use forward error correction (fec) (for use rtp protocol) if you would like to use fec, then select this checkbox when fec is used, repair packets are sent on additional ports, enabling packet recovery preserve rtp headers select this checkbox to preserve the rtp headers (which include the timestamps and sequences) and propagate them the output multicast address if you would like to join a multicast group, enter the multicast address the multicast address should be in the range of 224 0 0 0 239 225 255 255 source specific multicast (for multicast address) specify a particular ip from which you will accept data port specify the port to listen on for the incoming content this port must be open on all firewalls between the ingest cluster and the input device max bitrate select from the drop down list the maximum bitrate for this source make sure that the value is greater than the max bitrate of the input the default is set automatically based on the current bitrate of the input source configuration ingest cluster select from the drop down list one of the available ingest clusters as the destination for the source target broadcaster/s specify which broadcaster/s within the cluster on which zen master can deploy the source either select a specific broadcaster to be used or specify your preference for using primary vs backup broadcasters options are prefer primary broadcasters, primary broadcasters only , backup broadcasters only or prefer backup broadcasters note for managed clusters, it is not recommended to select a specific broadcaster, as the broadcaster’s availability may not remain stable input nic if you would like to specify which nic is used, then select the ip of that nic from the drop down list by default, any is selected pid mapping profile (optional) if you would like to apply a pid mapping profile to this source, then select the desired profile from the dropdown list to create a new pid mapping profile, see adding pid mapping profiles docid\ gftcayurpl7dinouyd14z note using this method creates a single source in zen master with pid mapping applied if you would like to maintain a source with the original pids and create an additional source with pid mapping (e g if you want to create several different pid mapped variations), then use the method described in adding a source pid mapping docid\ gockl3upsd8v14ia2an6g alert on pid changes if you would like to generate email notifications whenever a pid change is detected, select this checkbox log scte 35 select this checkbox if kyou would like to log scte 35 markers for this stream note to log scte 35 markers, scte 35 needs to be enabled both on the ingest cluster and in the source configuration note scte 35 logging is only available for v13 1 40262+ broadcasters enable scte 35 alerts (for log scte 35) if you would like to receive alerts for scte 35 markers, select this checkbox public output if you would like to allow access to the stream directly through a supported player, select the allow checkbox password (for public output) if you selected allow in the public output field, specify a password in this field to authenticate access to the stream enable content analysis if you would like to enable content analysis (cqa), verify that this checkbox is selected (default) note it is generally recommended to enable content analysis unless it is causing technical problems if content analysis is disabled, the system won’t detect errors in the video and audio content of the stream and won’t generate warnings for such events even when content analysis is disabled the system will still detect tr101 errors in the stream monitor cea 608/cea 708 closed captions if you would like to monitor cea 608/cea 708 closed captions, select this checkbox note monitoring cea 608/cea 708 closed captions requires using a version 14 4 or newer broadcaster disable auto pull if you would like to disable auto pull, select this checkbox note disabling auto pull will lock channels using this source to the source's ingest cluster and targets to the source's current active broadcaster this setting only applies to pass through channels auto pull latency \[ms] specify the desired latency for auto pull actions (default 1,000 ms) webrtc playback select the desired playback method note webrtc enables you to monitor the stream via web browsers and mobile applications with real time communication (rtc) webrtc needs to be activated independently for each source in zen master (by default it is disabled) select one of the following options disabled users will not be able to view this source using webrtc (default) pass through passes the stream through to webrtc without transcoding this option can only be used if the input stream is already in a webrtc compliant format (video h 264 codec with baseline or main profile and no b frames, audio opus codec) auto zen master automatically transcodes the stream using the optimal profile for each specific user in this option zixi broadcaster will decode the video, transforming it into raw frames, which will be passed to the webrtc library, where it will be re encoded for each individual user note best quality however, if monitored by multiple users this can consume extensive resources 1080p/720p/480p/360p zen master transcodes the stream to a webrtc compliant profile with the specified resolution the transcoding is done by zixi broadcaster's transcoder note this method requires a zixi broadcaster with x264 or nvidia for transcoding this method allows many users to monitor the stream without encoding separately for each individual user, which saves cpu capacity since there is only one stream resolution, it is recommended to encode to a low resolution and low bitrate so that the stream will be viewable by all users monitoring the stream initial state disabled select this checkbox if you would like to disable this source upon initial configuration muted select this checkbox if you would like to disable error/recovery notifications for this source upon initial configuration advanced billing codes if you would like to track usage for this source, enter your billing code details, see billing codes docid\ lalxj n928tegcpdpbirj (supported for broadcasters v14 8+) billing password enter the password that corresponds to this billing code auto pull billing code if you would like to track usage for this source when using auto pull connections, enter the billing code that corresponds to this stream the relevant billing can be obtained from the organization that received the billing code from zixi auto pull billing password enter the password that corresponds to this auto pull billing code auto pull mtu specify the maximum transmission unit (largest data packet that a network connected device will accept) in bytes for the auto pull apply input nic selection to network device select this checkbox to apply input nic selection to the network device frozen video minimal duration specify the default minimal duration in seconds of frozen video after which the broadcaster will trigger a frozen video alert default 10 seconds this setting is supported for broadcaster version 16 3 and higher for existing sources, you may need to restart the source blank video minimal duration specify the default minimal duration in seconds of blank video after which the broadcaster will trigger a blank video alert default 10 seconds this setting is supported for broadcaster version 16 3 and higher for existing sources, you may need to restart the source dejitter buffer the length of the de jitter buffer (in milliseconds) the buffer is used to collect packets and measure the jitter of the source that is arriving with jitter dejitter clock source select which mechanism should be used in the calculation of the jitter arrival times rtp timestamps