Stream Media refers to a continuous time base medium such as audio, video, or multimedia files using streaming technology in Internet / Intranet. Linux is a pioneer in web applications, as the performance of streaming media platforms is also good. There are currently three mainstream streaming systems, which are RealNetworks's RealMedia, Microsoft's QuickTime for Windows Media and Apple. RealNetworks has released the source code of the Helix Universal Server software that sends digital media through the Web on Windows, UNIX, and Linux platforms. Helix product technology advances, many users, support unicast, multicast, and multi-platform (including Linux, Windows 2000 / NT, AIX, Solaris, and Mac OS). The latest version of Helix Universal Server is 9.0, and 8.51, which mainly joins support for redundant servers and support for content cache. This allows users to connect to the server as quickly as possible, and ensure that they can be automatically repaired in any possible case. Helix is compatible with all common media formats, even including its competitors' WM format. This article describes how to build streaming media servers under Linux with Helix Universal Server 9.0. Software download users are registered on http://www.realnetworks.com/Web website, fill in the name, country, postal coding, and email, with email is the most important. After the registration, RealNetworks will send a license key to the registered user's email address, allowing us to use Helix on the server. The format of the authorization code is .zip package. Please decompress it after saving (file name: RNKEY-HELIX_SERVER-90-1479442709717329.LIC), use it when installing the software. After completion, you can choose Helix Server download, download address is http://get.real.com/RJP1/61.195.68.21/28E23B8AC11FA0CE9001/Serverg2/RS901-Linux-22libc6-ia32.bin, version number is 9.2.0.794. System Requirements Software: Requires the kernel at least 2.4 or more, KDE 2.0, Window System Xfree86 4.03, with a desktop resolution of at least 800 × 600, and the desktop color is at least 16 bits enhance color. Hardware: CPU Pentium II 450MHz or more, memory 128MB, hard disk space 600MB, OSS / Linux compatible, 16MB memory. Installing the software first logs in X-Window with superuser privileges, create a Helix directory, copy the authorization code to the directory, the execution process is as follows: #mkdir helix #cp rnkkey-helix_server-90-1479442709717329.lic / Helix then change the downloaded file Names, group properties, and groups make it an executable file. The command is as follows: #mv rs901-linux-22libc6-ia32.bin helix.bin #chmod x helix.bin The following is the installation command and detailed steps. #. / Helix.bin First, the system first allows the user to list the depository of the authorization code. The reference is written by / root / helix / rnkkey-helix_server-90-1479442709717329.lic. In the second step, a long license agreement will appear, and press Enter keys to accept the agreement at the end of the agreement. In the third step, when the system is inquiry, the user fills in the ROOT / HELIX to press Enter to continue.
In the fourth step, the system requires the user to fill in the username and password of the Helix Universal Server (see Figure 1). Above: Fill in the username and password of the Helix Universal Server fifth step, which port is used to connect PNA (Progressive Networks Audio). The PNA protocol is used to transfer content created by the early RealSystem tools to compatibility with earlier versions. Use the default port 7070 here. In the sixth step, the system is interrogated from which port is used to connect to the RTSP (real-time flow protocol). RTSP is the application level protocol to control the transmission of real-time data. It provides an extensible framework that makes real-time data (such as audio and video). The data source includes field data and data stored in the clip. The protocol is an object of controlling multiple data transmission connections, providing a way to select a transmission channel (such as UDP, multicast UDP and TCP), and provide a method of providing a transmission mechanism based on RTSP. Use the default port 554 (see Figure 2). Above: Setting the RTSP port number Step 7, which port is used to connect to the HTTP protocol. Realization of streaming requires a suitable transfer protocol. Since TCP requires more overhead, it is not suitable for transmitting real-time data. In an implementation of streaming, HTTP / TCP generally employs control information, and RTP / UDP is used to transmit real-time sound data. See Figure 3 on the principle of working transmission of streaming media. The typical HTTP listening port is set to 8080. Above: The third step of streaming file transfer principle, which port is used to connect to the MMS protocol. Helix Universal Server starts supporting the MMS protocol after 8.0. The MMS protocol is used to access unicast content on the WINDOWS Media publishing point, which is the default method to connect to the Windows Media unicast service. If the audience wants to type a URL to connect to the content in Windows Media Player, instead of accessing the content through the hyperlink, they must use the MMS protocol to reference the stream. When connecting to the publishing point using the MMS protocol, use the protocol to get the best connection. The "protocol flip" begins with the client that is connected to the MMSU. The MMSU is the MMS protocol to bind to UDP data transfer. If the MMSU connection is unsuccessful, the server tries to use MMST. MMST is the MMS protocol combined with TCP data transfer. The MMS port is typically set to 1755. In the ninth step, set the system administrator control port of the Helix server. This port can be set yourself, but you must pay attention to not repeating with the already defined port. Here is set to 17965. In the end, the system gives all the summary lists of all options. Please read it carefully. After confirming, press the "F" button to indicate the setting and start installing. This is shown in Figure 4. If there is a problem, press the ESC button to return to reselect. Above: The summary of the system settings will be automatically exited back to the root directory after the system installation is over. Step 12, start the server, do the following to enter the installation directory. $ CD Helix $ CP RNKEY-HELIX_SERVER-90-1479442709717329.LIC / license; $ cd .. $ bin rmserver / root / helix rmserver.cfg Helix startup interface See the figure below. Above: Helix Universal Server boot interface
Manage the Helix Universal Server server Enter the server IP address, administrator port, and index.html in the Linux browser, format http://192.168.0.1:17460/index.html. At this time, the system will pop up a dialog, enter the admin user name and password separately, and press the "OK" button. After a few minutes of system verification, I finally entered the Helix Universal Serve Management Center (see the figure below). Above: The Helix Universal Serve Management Center enters the Helix server settings menu (see Figure 7), the twelve options that the Helix server needs to be set is Ports, IPBing, Mime Type, Connecting Control, Mount Points, URL AliaSing, Http Delivery, Cache Directives, Share Lincesing, User / Group Name and Media Sample. The following details are described in detail. Above: Helix Universal Serve Server Sets Center 1. Port (Port Configuration): In the browser, you can define a variety of different types of ports, including RTSP, PNA, HTTP, Monitor and Admin, and ADMIN. There is a new option "Enable HTTP Fail over Url for asxgen" and ASX file playback. When heLix Server has a WM media file content, it can be set to 5087, and other parts can be skipped. 2. IP Binding: There may be more than one network card on a Helix Server server, or there may be no only IP address on a single network card. In some cases, it is necessary to bind the IP address of Helix Server. This page is used to edit and delete the server for IP address and delete existing bindings. 3. MIME TYPE: Defines how to tell the server how to identify the correct file to ensure that it can be transmitted through the HTTP protocol completely efficiently. Corresponding to the corresponding extension, you can find the relevant definition format here. 4. Connecting Control: Connection options related to HELIX Server, where you can define the maximum number of connections for the server, maximum allowable connection (this is the limitations specified by the authorization) and the user player, For example, only the RealPlayer player is used, or only the PLUS version player is used. Of course, you can also limit the bandwidth of the service to ensure that other services on the same server have sufficient network resources. 5. Redundant Server: The configuration page of the redundant server includes a list of server lists, directory mappings, and exceptions. 6. Mount Points: Here is to set the streaming file loading point. 7. URL AliaSing: A separate name points, through a simple alias, so that users make more convenient memories. Enter the Helix Server Management Center without entering that long string, as long as RTSP: // Server: port / alising can replace it. 8. HTTP Delivery (HTTP Distribution): Helix Server also needs to transfer certain files via HTTP. The following directory is to transfer defined via HTTP protocol. The transfer file via the HTTP protocol is very necessary for users behind the firewall, see the figure below.
