Zixi Receiver - Aws Mediaconnect User Guide: Software Version 12.4 Document Version Doc26-450-0002 All Rights Reserved
Zixi Receiver - Aws Mediaconnect User Guide: Software Version 12.4 Document Version Doc26-450-0002 All Rights Reserved
Zixi Receiver - Aws Mediaconnect User Guide: Software Version 12.4 Document Version Doc26-450-0002 All Rights Reserved
User Guide
Software Version 12.4
Document Version DOC26-450-0002
Copyright © Zixi 2020
All Rights Reserved
Legal Notice
Supported Protocols
Legal Notice
This document contains proprietary and confidential material of Zixi LLC. Any unauthorized
reproduction, use, or disclosure of this material, or any part thereof, is strictly prohibited. This
document is solely for the use of Zixi employees and authorized Zixi customers.
The material furnished in this document is believed to be accurate and reliable. However, no
responsibility is assumed by Zixi LLC. for the use of this document or any material included
herein. Zixi LLC. reserves the right to make changes to this document or any material included
herein at any time and without notice.
Table of Contents
Legal Notice..................................................................................................................................... 2
Introduction to Zixi MediaConnect Receiver .................................................................................. 5
Supported Protocols ................................................................................................................... 5
Zixi Technology............................................................................................................................ 5
Latency Considerations ............................................................................................................... 6
Recording Options ...................................................................................................................... 7
Prerequisites ................................................................................................................................... 8
Firewall Settings .......................................................................................................................... 8
Bandwidth Availability ................................................................................................................ 8
Source/Destination Devices Compatibility ................................................................................. 8
Remote Connection .................................................................................................................... 8
Logging in to Zixi MediaConnect Receiver ...................................................................................... 9
Activating Your Zixi MediaConnect Receiver License ................................................................... 10
Activating Your Zixi Receiver License – Online Activation ........................................................ 10
Loading MediaConnect Receiver License File - Offline Activation ........................................... 10
Reloading the Zixi MediaConnect Receiver License ................................................................. 11
Viewing Current Zixi MediaConnect Receiver License Information ......................................... 11
Viewing Status in Zixi MediaConnect Receiver ............................................................................. 12
Adding Input Streams to Zixi MediaConnect Receiver ................................................................. 14
Adding a Push Stream to MediaConnect Receiver ................................................................... 14
Input Stream Parameters Table ............................................................................................ 15
Adding a Pull Stream to MediaConnect Receiver ..................................................................... 17
Input Stream Parameters Table ............................................................................................ 18
Searching for Input Streams in MediaConnect Receiver .......................................................... 20
Viewing Existing Input Streams in MediaConnect Receiver ..................................................... 20
Performing Actions on Input Streams in MediaConnect Receiver ............................................... 22
Stopping/Starting Incoming Streams in MediaConnect Receiver ............................................ 22
Editing Input Settings in MediaConnect Receiver .................................................................... 22
Deleting Input Streams from MediaConnect Receiver ............................................................. 22
Duplicating an Input Stream in MediaConnect Receiver .......................................................... 23
To enable Zixi protocol protection across the entire delivery path, you need to use the Zixi
protocol as part of the contribution segment to AWS Elemental MediaConnect and as part of
the distribution segments from AWS Elemental MediaConnect. Zixi is integrated in a wide
variety of devices for both encoding and decoding video content. However, if your encoder
does not include an embedded Zixi component (i.e. cannot output a Zixi-protected stream), you
can use the Zixi MediaConnect Feeder software. And in the distribution end, if your decoder
(IRD) does not include Zixi, you can use the Zixi MediaConnect Receiver. Both Zixi
MediaConnect Feeder and Zixi MediaConnect Receiver can be installed on-premise and on the
cloud.
Supported Protocols
Zixi MediaConnect Receiver resides at the point of distribution. The following protocols are
supported:
Inputs:
• Push – the stream is pushed from AWS MediaConnect to the AWS MediaConnect
Receiver.
• Pull – the stream is pulled by the AWS MediaConnect Receiver from AWS MediaConnect
Outputs:
• UDP
• TCP
Zixi Technology
Zixi’s transport stream protocol is a content and network-aware protocol that dynamically
adjusts to varying network conditions and employs error correction techniques for error-free
video streaming over IP. With minimum overhead to physical bandwidth, this dynamic
mechanism provides low end-to-end latency, removes jitter, recovers and re-orders packets,
smooths video delivery and regenerates video to its original form, all in real-time.
Zixi delivers outstanding performance (at low predictable latency), superior reliability (no
packet loss) and broadcast-grade video quality (SD, HD, and UHD) with no tradeoffs to delay,
resolution or stutter.
Streaming from one Zixi-enabled device/server to another Zixi-enabled device/server protects
the stream from quality degradations along the path. It enables the streaming of high-quality
video over any distance, while overcoming the varying network conditions of the public
Internet, where the amount of network errors, packet loss, jitter and out-of-order packets
fluctuate "every second".
The Zixi transport stream protocol can also be deployed on part of the path. For example, from
a Zixi Feeder to a Zixi Broadcaster (Zixi protected path) and on to the end user through UDP or
RTMP. In this case, the path that has challenging conditions (e.g. long distance or unstable
wireless conditions) will be protected by Zixi and then delivered on to the end-user on a
standard UDP or RTMP protocol.
Zixi’s transport stream technology includes the following features for ultimate quality and
security:
• Network sensing
• Dynamic de-jitter
• MPEG specific optimizations
• Z-ARQ error recovery
• Z-FEC - Dynamic content aware forward error correction
• Active multi-path error recovery
• Adaptive bitrate over UDP, unicast or multicast
• Rate control and congestion avoidance
• 256-bit AES transport encryption
Latency Considerations
Latency defines the delay in which the video stream will be delivered to the end-point. This
delay is essentially a buffer that is used for additional processing, thereby improving the quality
of video stream. The latency should be considered based on the importance of immediacy. For
example, if the video requires interaction (e.g. between a reporter in the field and an anchor in
the studio), the latency should be set to a minimum so that the interaction does not suffer from
any delay.
Latency can vary from tens of milliseconds to several seconds.
Zixi protocol can provide a delay of a single frame (30ms), while increasing the latency to
provide more robustness for the error-recovery.
In low latency (below 1500ms) the error recovery is based on a hybrid approach of FEC and
ARQ. FEC will add overhead of up to 30% (adaptive–without congesting the network).
To allow sufficient error-recovery it is recommended to set the Latency at least 3 times larger
than the RTT (i.e Latency >= 3* RTT)
Latency can be set to any value; we recommend two common modes:
1. Interactive mode - 500ms
2. Non-interactive mode – 4000ms
Latency below 1500ms will add an FEC overhead of up to 30%.
Recording Options
Live stream inputs can be stored as MPEG-TS files to a local disk drive or to a mounted drive.
Prerequisites
Before you begin using Zixi MediaConnect Receiver, make sure you prepare your deployment
by following the instructions below.
Firewall Settings
• Make sure UDP traffic coming to and from the Zixi MediaConnect Receiver is not
blocked.
• External firewall should allow communication on UDP port 2088 (inbound & outbound).
• Remote web management should allow TCP port 4444.
• Make sure outgoing TCP 80 to license.zixi.com and UDP 53 to your DNS server.
Bandwidth Availability
Verify that both the uplink and downlink internet bandwidth are sufficient to carry the feeds.
Remote Connection
Allow SSH or TeamViewer Ver.10 remote connection details for support issues.
The Information shown on the Status page is described in the following table:
Field Description
General
Displays the time that the Zixi MediaConnect Receiver began to actively
Start Time
stream content.
Uptime The duration of time that the Zixi MediaConnect Receiver is running.
Remote In [kbps] The cumulative traffic received (in Kbps) from remote sources
The cumulative traffic received (in Kbps) from local sources (e.g. streamed
Local In [kbps]
from a local file)
Remote Out [kbps] The cumulative traffic transmitted (in Kbps) from remote sources
The cumulative traffic transmitted (in Kbps) from local sources (e.g. streamed
Local Out [kbps]
from a local file)
Active – the RTMP server has been enabled (Settings > RTMP Server)
RTMP Server
Off – the RTMP server has been disabled (Settings > RTMP Server)
License Info
2. Enter the unique Stream ID (an internal name) for the Zixi MediaConnect Receiver.
3. Select Push for the Input Source.
4. If the stream is password protected, enter the stream's Password (must be identical to
the string configured on AWS MediaConnect).
5. Specify the maximal latency in milliseconds that will override the latency that was
defined in AWS MediaConnect. Default: Remote configuration (i.e. use the latency was
set in AWS MediaConnect).
6. Specify the Stream Parameters (see Input Stream Parameters Table).
7. Click OK.
The “Input added” message appears on the top of the screen.
The Push Stream is added to the Zixi MediaConnect Receiver and now appears in the list
of Input streams available.
Stream
Parameters
Specify the maximal latency in milliseconds that will override the latency
Latency that was defined in AWS MediaConnect. Default: Remote configuration
(i.e. use the latency was set in AWS MediaConnect).
If the stream has been encrypted, select this checkbox to decrypt the
Decrypt Stream
stream.
Decryption type
(for Decrypt Specify the type of encryption that is being used in the stream.
stream enabled)
Decryption key
(for Decrypt Specify the key for decryption.
stream enabled)
Recording
Select this checkbox to enable recording of the stream
Parameters
Keep recorded
files for Specify the maximum time for storing the recording. Default: 0 hours
[HH:MM]:
Optionally specify a storage location for the recorded files that is relative
Custom Path to the root folder. This location bypasses the location specified as the root
folder in the Settings > General screen.
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
File Name the legitimate structure of the file in Linux and Windows:
Template • %S=stream id - optional.
• %Y=year - optional
• %M=month - optional
• %D=day - optional
• %T=HH.MM.SS creation time - mandatory
For example, the following pattern %Y_recording%T.ts will generate the
following file name 2017_recording15:32:35.ts.
Enter the port through which the Zixi MediaConnect Receiver receives
the stream from AWS MediaConnect server. Default: 2088
Port The default input port is UDP port 2088. This port must be open on any
firewalls between and Zixi MediaConnect Receiver other devices it is
communicating with.
Stream Enter the unique stream ID from the source AWS MediaConnect server.
Ignore TLS When this option is selected, Zixi MediaConnect Receiver will ignore the
certificate TLS certificate errors and transmit the stream to its destination.
Select from the drop-down list the local IP address to be used for this
Bind to IP
Input, OR select Any to enable any IP to be used.
If the stream has been encrypted, select this checkbox to decrypt the
Decrypt Stream
stream.
Decryption type
(for Decrypt Specify the type of encryption that is being used in the stream.
stream enabled)
Recording
Select this checkbox to enable recording of the stream
Parameters
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
File Name maintain the legitimate structure of the file in Linux and Windows:
Template • %S=stream id - optional.
• %Y=year - optional
• %M=month - optional
• %D=day - optional
• %T=HH.MM.SS creation time - mandatory
For example, the following pattern %Y_recording%T.ts will generate the
following file name 2017_recording15:32:35.ts.
Any of the columns in the following table can be sorted in ascending/descending order by
clicking on its heading.
The Search text box in the upper left-hand side of the screen can be used to search for a
specific input stream by entering the desired Stream ID.
Field Description
Status Displays the status of the input stream. The following colored indicators
are displayed:
• Green = Connected
• Yellow = Connecting
• Red = Disconnected with an error condition
• Blue = Offline with no connection attempts
• Grey = Offline and stopped
Source Displays the source host and port number or file name.
TR 101 290 Displays if the TR 101 290 Analyzer is active and the P1 and P2 status.
Adding an Output
To Add an Output:
1. In the Navigation menu, click the Inputs tab.
2. Click the Actions button , and then click New Output. The New Output window with
the settings of the selected output stream is displayed
3. In the drop-down menu, click New Output. The New Output window with the settings
of the selected output stream is displayed.
4. Follow the specific instructions of each output type from one of the following sections:
• Creating a UDP Output
• Creating a TCP Output
5. Click OK.
The New Output with its new settings takes effect.
2. Enter the unique Output Name that you want to configure on the MediaConnect
Receiver.
3. Select the Input Stream from the drop-down list.
Input Stream Select the Input which has been previously configured as Input. You can
assign an input stream later, by selecting None, assign later.
Output Parameters
TTL Specify the time-to-live (TTL). Used mainly to limit the range (or
“scope”) of a multicast transmission. Leaving it as blank uses the
default value specified by the operating system.
Smoothing Enables transmission of the output at the correct rate. Required when
the receiving device is sensitive and can’t lock on to the stream (in such
a case, the recommended latency is 100 - 1000 ms).
Bind to IP Select from the drop-down list the local IP address to be used for this
Output, OR select Any to enable any IP to be used.
Local Port Specify from which local port to source the stream, if desired (instead
of randomly chosen by the operating system).
ReMuxing Select this checkbox to enable remuxing from VBR MPEG-TS to MPEG-TS
CBR (used for professional IRDs).
Remux to bitrate
Specify the CBR bitrate to target for a remuxed stream.
[kbps]:
Parameter Description
Buffer Size [ms] Specify the size of the buffer that will be used for the remixing. A larger
buffer increases the quality, but also increases latency.
Decryption type If the stream has been encrypted, you can decrypt through the output
by selecting this checkbox and specifying the type of encryption that
was used.
Select Automatic to decrypt a stream that has been encrypted using
Automatic encryption.
Only if the stream has not been encrypted, select None (default).
Important Notice: if the stream has been encrypted you must decrypt it
in the output.
Decryption key If the decryption type includes a key, enter the key to decrypt the
stream during output.
2. Type in the unique identifier for this output in the Output Name.
3. Select an Input Stream to be made available on this output from the adjacent drop-
down list.
4. Select TCP.
5. Specify the Output parameters (see Output Stream Parameters Table).
6. If the target is an HTTP server, select the HTTP checkbox. In this case, HTTP headers will
be added to the stream.
7. Select the Enable decryption checkbox to decrypt the Output stream (see Output
Stream Parameters Table).
8. Click OK. The new TCP Output with its settings is created and now appears on the
screen.
If the target is an HTTP server, select the HTTP checkbox. In this case, HTTP headers will
HTTP
be added to the stream.
Enable
Select this checkbox to enable decryption of an encrypted stream.
Decryption
If the stream has been encrypted, you can decrypt through the output by selecting this
checkbox and specifying the type of encryption that was used.
Decryption
type
Select Automatic to decrypt a stream that has been encrypted using Automatic
encryption.
Only if the stream has not been encrypted, select None (default).
Important Notice: if the stream has been encrypted you must decrypt it in the output.
Decryption
Enter the decryption key to decrypt the encrypted stream.
key
Any of the columns in the following table can be sorted in ascending/descending order by
clicking on its heading.
Field Description
Status Displays the status of the output stream. The following colored
indicators are displayed:
• Green = Connected
• Yellow = Connecting
• Red = Disconnected with an error condition
• Blue = Offline with no connection attempts
• Grey = Offline and stopped
Uptime Displays the amount of time the stream has been active.
Field Description
Up Time Displays the amount of time the stream has been active.
Send Errors Displays the number of errors generated after sending the stream.
RTT (ms) Displays the Round Trip Time (RTT) from the source (in milliseconds)
Total Packets Displays the total number of packets that have been transmitted.
Displays the packet loss rate (how many packets were lost out of the
Packet Loss %
total number of packets).
Displays the total number of packets that were dropped since the
Dropped Packets
beginning of the stream.
ARQ Recovered Displays the number of dropped packets recovered via ARQ.
ARQ Duplicates Displays the number of duplicate recovery packets received via ARQ.
2. In the New Input drop-down, select the desired input, and click OK.
The newly designated input is now associated with the selected output.
If you make changes to the settings, you must click Apply to save the changes
before navigating away from the page.
The Parameters shown in the General Settings are described in the table below:
Field Description
Select this checkbox to enable an "Operator" user. This type of user can
Enable read / write user - read and write throughout all of the screens, except for the screens
except for settings under the Settings menu.
screen You can modify the user name (i.e. enter another name instead of
Operator) and password.
Select this checkbox to enable a "User" user. This type of user can read
Enable read-only user throughout all of the screens as well as the ability to switch between
+ability to switch existing streams.
streams You can modify the user name (i.e. enter another name instead of User)
and password.
Select this checkbox to enable an "Observer" user. This type of user can
read throughout all of the screens.
Enable read only user
You can modify the user name (i.e. enter another name instead of
Observer) and password.
HTTPS certificate
If no certificate has been uploaded, click Upload and navigate to the file
uploaded (for HTTPS
location.
enabled)
Displays the configured root folder. You can modify the root folder by
modifying the broadcaster-info.xml, which is located in the
Root folder
MediaConnect installation folder
(<Installation_Folder>\Zixi\MediaConnect\)
Monitoring options:
• None – no monitoring
TR101 analyzer mode
• ATSC
• DVB
The CPU utilization threshold. If this limit is exceeded, the CPU indicator
at the top of the screen will appear in red, and an alarm will be
CPU [%] generated in the event log.
Default: 90
Field Description
Server connection
Specify the Host name or IP address of the remote server for the SSH
Host
connection.
Reverse tunnels
Local Destination Port Displays the port number of the local destination.
Field Description
Logging
Specify the log file name and path where the collected event information
Logs Path
will be stored.
The Severity Level that will be collected in the log, from Info, Warning,
Log Level Error, to Fatal. The default setting is None, since Logging is resource-
intensive and only enabled when necessary.
Field Description
Available ports
Name Specifies the port number used by the ASI protocol
Specifies the direction of the data being transmitted by the ASI
Data Direction
protocol.
------------------------------------------------------------------------------------------
- License for OpenSSL
------------------------------------------------------------------------------------------
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/)
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL
PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by
Tim
Hudson (tjh@cryptsoft.com).
------------------------------------------------------------------------------------------
- License for Libssh2
------------------------------------------------------------------------------------------
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the copyright holder nor the names of any other contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
------------------------------------------------------------------------------------------
- License for DekTec's Linux SDK. Version 1, August 2012
------------------------------------------------------------------------------------------