ZEC Adding UDP Streams

this enables the broadcaster to receive a udp stream the udp stream is not protected by the zixi protocol the udp streams can be one of the following types 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 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 instruction in the zec demuxing an mpts stream docid\ lhnzbcxz5kd6ti 6ump7y section to add a udp stream in the zec navigation menu, click the inputs tab in the menu bar, click +new input the add 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\ nlxzehz 9rxlcmx6xie c ) default selected select udp for the input stream new udp input 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\ nms0u6uroxuzmozp2he l if you want to configure the recording parameters , specify them in the respective fields (see input stream parameter table) new udp input (expanded) click ok the “input added” message appears on the top of the screen the udp 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 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 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 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 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 dejiterring 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) enable encryption select this checkbox to encrypt the input stream for more information, see zec encrypting an input stream https //zixidocumentation atlassian net/wiki/spaces/117/pages/4887947322/zec+encrypting+an+input+stream 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 8mil85ijafynoutwwouqi 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