setting up 360° live streaming with giroptic 360cam & wowza

7/26/2019 Setting up 360 Live Streaming with Giroptic 360cam & Wowza

1/14

Wowza Streaming Engine Configuration

for 360cam live Streaming

This guide will help you to configure Wowza Streaming Engine media server for 360cam live

streaming. The camera will push stream to Wowza server. The guide does not explain the

Wowza software installation. For this, refer to these guides:

https://www.wowza.com/forums/content.php?217-How-to-install-and-configure-Wowza-Streaming-Engine

http://www.wowza.com/resources/WowzaStreamingEngine_UsersGuide.pdf

1 - Get your Wowza server configuration

After opening Wowza Streaming Engine Manager in a web browser, you must retrieve the IP

address and the server streaming port.

- Click the Home tab in Wowza Streaming Engine Manager

Server IP/Port

- Retrieve server parameters


2/14

Host - Server 52.26.171.123

Host - Port 1935

Make sure the streaming port is open on your router, firewall, and in your iptables.

2 - Create a configuration file for the camera

After getting streaming settings, you must create a configuration file that will be used by the

camera. The file will be copied to the SD card inserted in the camera.

- File name: stream.txt

- File path (SD card): MISC/

- File content: "Sever IP Address" " StreamingPort" "Streaming Name"

- Example: 52.26.171.123 1935 live/360live

Note: The parameters must be on one line with a space as a separator !!!

3 - Disable security restriction for input sources

Click the Applications tab in Wowza Streaming Engine Manager and then click live

On the live page, go to Source Security

Security settings


3/14

You can edit settings:

Edit security options

4 - Improve Server Performances

For best performance, you must change some parameters whose default values cause

limitations. But, these parameters are not exposed within the Engine Manager web UI. So, you'll

need to edit the XML configuration files from your server.

The XML configuration files are located in the [install-dir]/conf folder of the Wowza Streaming

Engine media server software installation. You can refer to this guide for details about

configuration files.

http://www.wowza.com/resources/WowzaStreamingEngine_ConfigurationReference.pdf

4.1 EC2 instances

If the Wowza Streaming Engine media server software is installed on EC2 instance, youll need

to connect to your Instance Management to retrieve the connection parameters to your server.

For more informations about connection to your instance:

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html?console_help=true


4/14

Server connection parameters

4.1.1 Prerequisites

Download and install winSCP and PuTTY.

Get the ID of the instance Get the public DNS name of the instance

Locate the private key (.pem)

Enable inbound SSH traffic from your IP address to your instance

4.1.2 Converting Your Private Key Using PuTTYgen

PuTTY and winSCP do not natively support the private key format (.pem) generated by Amazon

EC2. PuTTY has a tool named PuTTYgen, which can convert keys to the required PuTTY

format (.ppk). You must convert your private key into this format (.ppk) before attempting to

connect to your instance using PuTTY and winSCP.

Start PuTTYgen (for example, from the Startmenu, click All Programs > PuTTY >

PuTTYgen).

Under Type of key to generate, select SSH-2 RSA.


5/14

Click Load. By default, PuTTYgen displays only files with the extension.ppk. To locate

your.pemfile, select the option to display files of all types.

Select your.pem file for the key pair that you specified when you launch your instance,

and then click Open. Click OK to dismiss the confirmation dialog box.

Click Save private key to save the key in the format that PuTTY an winSCP can use.

PuTTYgen displays a warning about saving the key without a passphrase. ClickYes.

Specify the same name for the key that you used for the key pair (for example,

my-key-pair ). PuTTY automatically adds the.ppk file extension.

Your private key is now in the correct format for use with PuTTY and winSCP. You can now

connect to your instance using PuTTY's SSH client.

4.1.3 Transferring Files to Your Instance Using WinSCP

After installing winSCP,

Start WinSCP.


6/14

At the WinSCP loginscreen, for File protocol, choose SFTP

For Host name, enter the public DNS address for your instance.

For User name, enter the default user name for your AMI. For Amazon Linux AMIs, the

user name isec2-user. For Red Hat AMIs the user name isroot

, and for Ubuntu

AMIs the user name isubuntu .

Specify the private key for your instance.For newer versions of WinSCP, you need to

click Advanced to open the advanced site settings, and then under SSH, click

Authentication to find the Private key file setting.

WinSCP requires a PuTTY private key file (.ppk), that you have generated with

PuTTYgen.

Enter the path to your private key, or click the "" button to browse for the file. Then, click OK.

Click Login to connect, and clickYes to add the host fingerprint to the host cache.


7/14

After the connection is established, in the connection window your Linux instance is on the right

and your local machine is on the left. You can drag and drop files directly into the remote file

system from your local machine.

Drag and drop this files from local machine to the remote machine

- VHostNew.xml

- ApplicationNew.xml

- wowza_conf.sh

For VHostNew.xml, the new parameters are:

true

800000

800000

800000

----

For ApplicationNew.xml

live

-----

Change script (wowza_conf.sh) permissions: Right click on the file name, and then click

Properties. Set the execute permission(X).


8/14

Open session in PuTTY: Click Commandsand click Open in PuTTY.

Run the script on PuTTY console.

Type this command on your console: ./wowza_conf.sh


9/14

4.2 Standalone Server

If the Wowza Streaming Engine media server software is installed on your personal server, you

can do the same procedure from the section 4.1.3.

You can also connect directly to your server and change this two files.

[install-dir]/conf/VHost.xml

[install-dir]/conf/live/Application.xml

5 - Transcoding for Live Application

Click the Applications tab in Wowza Streaming Engine Manager and then click live

On the live page, go to Transcoder

Click Enable Transcoder

Cick Transrate (Default) for transrate template


10/14

Disable/Modify defaults encode output (checked)

a) Click on Encode name, then you can Editor Disable Encode

b) Click Return to Transcoder Template


11/14

c) Repeat action a) and b) for each Encode name that you want modify or disable

Add new Encode output

a) Click Add Encode

b) Fill the various parameters (Encode Name, Outgoing Stream Name, Video Settings,

Audio Settings)

c) Click Add to confirm the configuration. You should see the new configuration at the

end of Encode list (but not enabled yet).

d) Click on the new Encode name and then click Enable Encode

e) Click Return to Transcoder Template

f) Repeat action a) to e) for each new output

Set Adaptive Bitrate Stream Name Groups

a) Click Stream Name Group


12/14

b) Click on pen ("Edit this stream name group") for all group


13/14

c) Select the right Encode names to add, and the left Encode names to remove

d) Click Save

e) You can do the same for mobile group

Restart Application

Click Restart

Restart your server

- Click the Server tab in Wowza Streaming Engine Manager

- On the Server page, go to Server Setup

- Click Restart


14/14

Note that the explanations located to the right of the Wowza Streaming Engine Manager

pages can help you. Do not hesitate to read them to understand the configurations.

setting up 360° live streaming with giroptic 360cam & wowza

Documents