ZEC Adding RIST Streams

this enables the broadcaster to receive an rist stream rist seeks to provide reliable, high performance media transport by using udp at the transport layer to avoid the inefficiencies of tcp, then layering on top forward error correction and retransmits to add the reliability inherently absent from udp zec supports rist streams from any compliant rist device zixi supports the following rist profiles simple profile – the rist simple profile provides best in class packet protection, as well as support for multi link bonding and seamless switching main profile – the rist main profile builds upon the features of the simple profile to provide backwards compatibility, while opening the door for additional features, including the use of industry standard dtls with a variety of available cyphers to ensure the most up to date protection, while being flexible to accommodate local legal regulations support for pre shared keys is also included, which makes rist main profile compatible with one to many environments such as satellite or multicast distribution contact your zixi representative to learn more about interoperability testing between zec and 3rd party devices more details about rist can be found at www rist tv http //www rist tv/ to add a rist stream in the zec navigation menu, click the inputs tab in the menu bar, click new input the add a new input stream window is displayed enter the unique stream id note this must be identical (case sensitive) to the stream name configured in the sending zixi broadcaster or mediaconnect select the maximum concurrent connections to this stream from the max outputs drop down list default unlimited select the show in matrix check box to display this stream in the matrix (see zec using the matrix docid\ skrtx3wdiaaoohem3 s r ) default selected select rist for the input stream specify the stream parameters (see the input stream parameter table below) if you want to enable encryption , select this checkbox (see input stream parameters table) for more information, see zec encrypting an input stream docid\ ctvrjainwk9qjrmvwznyc if you want to configure the recording parameters , specify them in the respective fields (see input stream parameter table) click ok the “input added” message appears on the top of the screen the rist stream is added to zec and now appears in the list of streams available in the zec inputs ui input stream parameters table parameter description stream parameters profile select one of the following rist profiles that matches the input stream simple profile (default) main profile simple profile parameters local port specify the port to listen on this port must be open on all firewalls between the zec 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 specify the source ip for a source specific multicast remote port specify the remote port in the source rist device default 0 (any port) type select one of the following protocol types from the drop down list rtp rtp + smpte 2022 fec 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 max latency \[ms] specify the maximum latency of the stream in milliseconds default 1000 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 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 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 main profile – push parameters local port specify the port to listen on this port must be open on all firewalls between the zec 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 specify the source ip for a source specific multicast remote port specify the remote port in the source rist device default 0 (any port) type select one of the following protocol types from the drop down list rtp rtp + smpte 2022 fec 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 max latency \[ms] specify the maximum latency of the stream in milliseconds default 1000 use dtls select this checkbox to encrypt the stream dynamically using dtls 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 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 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 main profile – pul l parameters remote host specify the ip address of the remote rist device from which the stream will be pulled remote port specify the port of the remote rist device from which the stream will be pulled default 0 (any port) local port specify the local port to which the stream will be pulled default 0 (any port) type select one of the following protocol types from the drop down list rtp rtp + smpte 2022 fec 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 max latency \[ms] specify the maximum latency of the stream in milliseconds default 1000 use dtls select this checkbox to encrypt the stream dynamically using dtls ignore tls certificate errors when this option is selected, zec will ignore the tls certificate errors and transmit the stream to its destination 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 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 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 enable encryption select this checkbox to encrypt the input stream for more information, see zec encrypting an input stream docid\ ctvrjainwk9qjrmvwznyc 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 zec using an external storage docid\ p4thzrqp6b0fqx38sqjkl section record to s3 – the file is saved to your aws s3 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 2022 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 2022 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, zec 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