Adding UDP Streams

this enables the broadcaster to receive a stream the udp stream is not protected by the zixi protocol the udp streams can be one of the following types – the input stream is plain udp – the input stream uses the rtp protocol, which adds rtp headers to the udp stream rtp adds a 12 byte header, which includes a sequence number and a timestamp that can be used to detect dropped packets the sequence number in the rtp headers can be used to do automatic reordering and the timestamps can help overcome inter packet gaps, also known as iat (inter arrival time) however, plain rtp does not feature error recovery or error protection by default, the rtp headers (which include the timestamps and sequences) are being used on the input side, but then they are stripped off and they no longer propagate to outputs rtp + smpte 2022 fec – the input stream includes forward error correction, which enables error recovery or error protection if the stream is an mpts stream and you want to demux it into separate spts input streams, create the stream by following the instructions below, and then follow the instructions in the demuxing an mpts stream docid\ fil363whm6ibixibmn2fz section to add a udp stream in the zixi broadcaster navigation menu, click the inputs tab in the menu bar, click new input and select the udp type the add a new input stream window is displayed new udp input enter the unique stream i d for the broadcaster note this must be identical (case sensitive) to the stream name configured in zec select the maximum concurrent connections to this stream from the max outputs drop down list default unlimited this setting can be modified without interrupting an existing stream select the show in matrix check box to display this stream in the matrix (see using the matrix docid\ bp6mo9f2qbxmu6gurkog4 ) default selected select the log this stream checkbox if you would like to generate event logs for this input select the analyze checkbox if you would like to enable stream analysis for the input specify the stream parameters (see input streams parameters table docid\ iq3fjq 33rjfo1wussieh below) if you want to specify billing codes to identify and differentiate traffic on a zixi broadcaster for billing purposes, select this checkbox (see input stream parameter table below) if you want to enable time shift , select this checkbox (see input streams parameters table) if you want to enable multicast on pull outputs , select this checkbox (see input streams parameters table) if you want to enable encryption , select this checkbox (see input streams parameters table) for more information, see encrypting an input stream in zixi broadcaster docid\ v3ryrbn08r4cojwl wvoq if you want to configure the recording parameters , specify them in the respective fields (see input streams parameters table) click ok the “input added” message appears on the top of the screen the udp stream from the zec is added to the zixi broadcaster and now appears in the list of streams available in the zixi broadcaster inputs ui input stream parameters table parameter description stream parameters port specify the port to listen on this port must be open on all firewalls between the zixi broadcaster and other devices it is communicating with multicast ip if multicast, type the multicast ip address (or leave blank in the case of unicast) ssm source ip specify the source ip for a source specific multicast type select the appropriate protocol type from the drop down list udp – the input stream is plain udp rtp – the input stream uses the rtp protocol, which adds rtp headers to the udp stream rtp adds a 12 byte header, which includes a sequence number and a timestamp that can be used to detect dropped packets the sequence number in the rtp headers can be used to do automatic reordering, and the timestamps can help overcome inter packet gaps, also known as iat (inter arrival time) however, plain rtp does not feature error recovery or error protection by default, the rtp headers (which include the timestamps and sequences) are used on the input side, but then they are stripped off, and they no longer propagate to outputs rtp + smpte 2022 fec – the input stream includes forward error correction, which enables error recovery or error protection 204 bytes ts packet enable this option if the stream has an mpeg ts that uses 204 bytes packets this will allow the udp packets to be aligned with mpeg ts packets bind to ip select from the drop down list the local ip address to be used for this input, or select any to enable any ip to be used max bitrate \[kbps] specify the maximum expected bitrate for memory allocation recommended 2x the actual bitrate, which will prevent buffer overruns (especially with vbr streams) default 8000 note – overflows will typically occur when the max bitrate isn’t sufficient dejitter buffer \[ms] a buffer size used to de jitter rtp and udp inputs for rtp, packet timing is fixed according to packet arrival times and rtp timestamps for udp, dejittering is only based on arrival times default 0 assuming that the timestamps in the rtp are accurate, this feature is helpful when the encoder generates an accurate timestamp on the stream, but the arrival is jittery/bursty in case of jitter, specify a higher value than the rtp input jitter to view the jitter level of the input stream, create the input and select it on the inputs screen; the jitter metric will be displayed in the stats pane at the bottom of the screen keep rtp headers selecting this checkbox will keep the rtp headers of the input keeping the input's rtp headers will propagate rtp headers to later processing steps, including failover groups and outputs (relevant for rtp inputs only) when used together with a failover group – enabling this option enables using smpte 2022 2 fec and 2022 7 hitless failover together the failover group will use 2022 7 and will merge streams based on sequence in the rtp header, and not on content with dna matching when creating the failover group, select the keep rtp headers again (in the failover group screen) to keep the rtp headers after the merge if it is not selected, zixi will merge based on the headers (using smte 2022 7), but then drop the headers thereafter combining keep rtp headers with outputs zixi pull/push – the "keep rtp headers" option can be used with zixi push/pull outputs in these cases, the rtp headers will be a part of the payload udp output – if you create an rtp input and select the keep rtp header checkbox in the input, the udp output will be an rtp output even if the rtp checkbox is not selected in the output this is the preferred way to create an rtp output rtp output it is not possible to use an input with ‘keep rtp headers’ together with an rtp output, as this will double the rtp headers to send the original headers as is, the stream should be sent as udp billing codes billing codes are used to identify and differentiate traffic on a zixi broadcaster for billing purposes when a billing code is added to a source or target, zixi can track the traffic on that broadcaster input or output separately from other inputs and outputs on the same broadcaster billing codes are created by zixi personnel on the zixi customer portal for a particular organization billing code 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 billing password enter the password that corresponds to this billing code enable time shift select this checkbox to record the stream content and broadcast it after a specified delay to deploy an input stream that uses the current stream's time shift, you need to configure a "delayed" input stream (see adding delayed streams docid\ zp5ql 5kthhdphmrhddhe ) maximum delay \[hh\ mm\ ss] (for time shift enabled) specify the maximum time delay of this input enable multicast on pull outputs select this checkbox to enable the transmission of this stream’s outputs as multicast a zixi receiver that will pull the stream will receive it in multicast by default, zixi broadcaster is configured to allow transparent fallback to unicast if it is out of the lan requires enabling multicast pull in the settings multicast only (for multicast enabled) selecting this checkbox will force the transmission of this stream only in multicast enable encryption select this checkbox to encrypt the input stream the stream encryption prevents any further processing, such as analysis, transcoding, etc the encryption works in the following way if the stream has been encrypted at the source the stream will remain encrypted regardless of the output type zixi broadcaster can only encrypt the stream after it has been decrypted if the stream is being encrypted by the zixi broadcaster it will be encrypted only if the output is a zixi pull or zixi push output all other outputs will send out an unencrypted stream for more information, see encrypting an input stream in zixi broadcaster docid\ v3ryrbn08r4cojwl wvoq encryption type (for encryption enabled) specify the type of encryption (aes 128/192/256) encryption key (for encryption enabled) click generate to generate an encryption key the generated encryption key must be sent to the end user to decipher the received encoded stream recording parameters select this checkbox to customize the recording parameters destination type select the radio button for the desired storage type and then fill in the relevant parameters record to disk – the recording is saved on the local disk it is possible to record to an external destination by replacing the default storage location with a symbolic link to learn more, see the using an external storage docid\ z2amp6 fj7crckkfqrthq section record to s3 – the file is saved to your aws s3 bucket the mechanism uses aws multipart upload amazon advises defining a lifetime rule for objects in the destination bucket record to disk parameters file name template specify the file name pattern that zixi will use to generate when saving the recorded content a separate file will be generated for each recording up to the time specified in the max recorded file duration parameter (see above) after this duration, a new file will be generated the file name pattern can include any string and up to five variables listed below only the %t=hh mm ss creation time is mandatory you can change the order of these variables and add text as long as you maintain the legitimate structure of the file in linux and windows %s=stream id optional %y=year optional %m=month optional %d=day optional %t=hh mm ss creation time mandatory %u=yyyymmddthhmmssz utc timestamp optional for example, the following pattern %y recording%t ts will generate the following file name 2017 recording15 32 35 ts max recorded file duration \[hours] specify the maximum time allotted for recording a video stream default 2 hours keep recorded files for \[hours] specify the maximum time for storing the recording default 0 hours custom path optionally specify a storage location for the recorded files that is relative to the root folder this location bypasses the location specified as the root folder in the settings > general screen record to s3 parameters file name template specify the file name pattern that zixi will use to generate when saving the recorded content a separate file will be generated for each recording up to the time specified in the max recorded file duration parameter (see above) after this duration, a new file will be generated the file name pattern can include any string and up to five variables listed below only the %t=hh mm ss creation time is mandatory you can change the order of these variables and add text as long as you maintain the legitimate structure of the file in linux and windows %s=stream id optional %y=year optional %m=month optional %d=day optional %t=hh mm ss creation time mandatory %u=yyyymmddthhmmssz utc timestamp optional for example, the following pattern %y recording%t ts will generate the following file name 2017 recording15 32 35 ts max recorded file duration \[hours] specify the maximum time allotted for recording a video stream default 2 hours url specify the url of the s3 bucket ignore tls certificate errors tls certificate for s3 bucket might be detected as faulty if bucket name contains dot\[s] when this option is selected, zixi broadcaster will ignore the tls certificate errors and transmit the stream to its destination access key the access key that is used for accessing the s3 bucket secret key the secret key that is used for accessing the s3 bucket advanced mode the fields discussed below are optional and available only in advanced mode to enter advanced mode add the url parameter ?advanced=1 to the zixi broadcaster url in your browser and press enter/return to reload the page note the advanced mode settings are generally intended for advanced users and special cases if you do not understand the settings, you should probably accept the default values udp stream input menu general latency offset \[ms] specify the additional buffering time in milliseconds increasing this value can improve stream stability in unstable network conditions, but will increase end to end delay default 0 ms support injection select this checkbox if you would like the stream to support scte 35 insertion scte 35 pid enter a pid number for scte 35 injection you can enter a value manually or use the up/down arrows that appear when clicking the field (or leave as auto to match existing scte 35 pid) inject metadata select this checkbox to insert metadata into the stream remove old scte 35 packets if scte 35 injection is supported, select this checkbox to clear out existing packets timeout for time in ms to wait for a null packet to inject scte 35 into stream parameters filter by source ip select this checkbox if you would like the broadcaster to accept multicast packets only from the ip specified in the ssm source ip field, even if the os delivers packets from multiple sources for the same multicast group bind to select from the drop down list the cidr that represents the ip range where the desired nic is accessed if you would like to configure the maximum transmission unit (the largest data packet that a network connected device will accept) for pulling the stream, enter the mtu in bytes in the mtu field socket buffer specify the socket buffer value in bytes compression enables bandwidth optimization by replacing null packets with signaling information embedded in packet headers this reduces the overall bitrate without affecting content integrity since not all receivers support this compression method, it is optional the system can receive compressed streams, but will only transmit compressed data when this option is explicitly enabled fast connect enables faster session establishment by reducing the time required to initiate the rist connection this is useful in environments where rapid recovery or quick stream startup is required support for this feature may vary depending on the receiving endpoint enable multicast on pull outputs custom multicast address select this checkbox to manually define a specific multicast ip address and port for the output stream, overriding the system's global multicast pool settings multicast ip enter the multicast ip address port specify the port to listen on this port must be open on all firewalls between the zixi broadcaster and other devices it is communicating with