Adding TS over HTTP (Push) Streams

in this mode, zixi broadcaster will receive a transport stream over tcp from an http server in this case, the stream is initiated by the source http server, while the zixi broadcaster remains in “listening mode” until the stream (with the specified stream id) is initiated to add a ts over http (push) stream in the zixi broadcaster 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 i d note this must be identical (case sensitive) to the stream name configured in zec enter 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 using the matrix https //zixidocumentation atlassian net/wiki/spaces/117/pages/4887944270/using+the+matrix ) default selected select ts over http for the input stream in the type field, select push specify the stream parameters (see adding ts over http (pull) streams docid\ kccojve1pjwgsps3jf2me ) 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 stream parameters table) if you want to enable encryption select this checkbox (see input stream parameters table) for more information, see encrypting an input stream in zixi broadcaster docid 5sh sqkz1lgkmgzjsqrzq if you want to configure the recording parameters , specify them in the respective fields (see input stream parameters table) click ok input stream parameters table parameter description stream parameters smoothing the smoothing feature uses a buffer to time packets according to the stream's clock this is useful when there are bursts in the rate in which the stream arrives the smoothing features creates a queue in the buffer, allowing smoother entry into the broadcaster the smoothing parameter defines the size of the buffer in milliseconds a larger the buffer enables smoother entry however, it may influence the latency rate user if the stream is password protected, enter the username to access the stream password if the stream is password protected, enter the password 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 https //zixidocumentation atlassian net/wiki/spaces/113/pages/746127861/adding+delayed+streams ) maximum delay \[hh\ mm\ ss] (for time shift enabled) specify the time of a delayed transmission of this stream maximum 24 hours enable multicast on pull outputs select this checkbox to enable the transmission of this stream’s outputs as multicast a zixi broadcaster 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 selecting this checkbox will force the transmission of this stream only in multicast enable encryption select this checkbox to encrypt the input stream for more information, see https //zixidocumentation atlassian net/wiki/spaces/117/pages/4887940495/encrypting+an+input+stream+in+zixi+broadcaster 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 using an external storage https //zixidocumentation atlassian net/wiki/spaces/114/pages/2052980737/using+an+external+storage section · record to s3 – the file is saved to your aws s3 bucket the mechanism uses aws multipart upload amazon advises to define a lifetime rule for objects on 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 in the table 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 general latency offset \[ms] support scte 35 injection scte 35 pid inject metadata remove old scte 35 packets keep stream cbr enable multicast on pull outputs custom multicast address multicast ip port