Versions Compared

Version Old Version 1 New Version Current
Changes made by

Hannah Petty

Hannah Petty

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Panel

In this section:

Table of Contents
maxLevel2
minLevel2

...

  • You are upgrading from a prior EchoSystem release to version 5.4 5 and already have an external Wowza Media Server instance configured for on-demand and live Echo content.
  • You are upgrading an external Wowza 3.x installation to version 4.0.

Use the instructions below to properly upgrade and configure your external Wowza Media Server instance for full functionality with version 5.4 5 of the EchoSystem.

Please ensure that the Wowza service is shut down before proceeding with these steps.

...

  1. Navigate to the /lib/ directory under your Wowza installation root and move all existing Echo360-specific JAR files to a safe location outside this directory. The files present will depend on the version you're currently using:

    Version 5.1 JAR Files

    Code Block
    echo360-live-app-monitor-5.1.0.jar
echo360-text-chat-5.1.0.jar

    Version 5.2 JAR Files

    Code Block
    echo360-live-app-monitor-5.2.0.jar
echo360-text-chat-5.2.0.jar
echo360-mediacaster-5.2.0.jar
  2. Download the latest External Wowza bundle, available from the Customer Support Portal.
  3. Extract the contents of the downloaded ZIP file to a temporary location.

  4. Copy the contents of the extracted /lib/ directory to the /lib/ directory under your Wowza installation root. The Wowza installation /lib/ directory should now contain the following files:

    Code Block
    echo360-live-app-monitor-5.4.1.jar
echo360-text-chat-5.4.1.jar
echo360-mediacaster-5.4.1.jar
echo360-captioning-5.4.1.jar
  5. Ensure that the ownership and permissions of these files match the rest of the files in the directory.

...


The next steps cover required modifications to enable Echo live streaming to iOS devices.

  1. In the /conf/ folder under your Wowza installation root, open the Server.xml in a text editor and make the following changes:

    NOTE: If you have previously upgraded your Wowza installation to enable live streaming, then these attributes may already be present in the Server.xml file. We strongly recommend verifying these changes are still present to ensure proper functionality, as in some cases the Server.xml file can be overwritten when upgrading a Wowza instance. If these changes are not present, please add them to the file as directed.
     

  2. Insert the following text between the <ServerListeners> and </ServerListeners> tags:

    Code Block
    <ServerListener>
	<BaseClass>com.echo360.streaming.live.MediaCaster</BaseClass>
</ServerListener>

  3. Insert the following text after the final <Properties> tag and before the </Properties> tag:

    Code Block
    <Property>
    <!-- the directory that contains the streams.txt file -->
    <Name>StreamMonitorDir</Name>
    <Value> ${com.wowza.wms.context.VHostConfigHome}/monitor</Value>
</Property>


<Property>
    <!-- the wowza application that the streams will be activated on. Default is echolive -->
    <Name>EchoLiveApplication</Name>
    <Value>echolive</Value>
</Property>


<Property>
    <!-- time the thread waits between checks of the streams.txt file. Default is 5 seconds -->
    <Name>WaitInterval</Name>
    <Value>5000</Value>
</Property>


  4. Replace the ${com.wowza.wms.context.VHostConfigHome} string with the location of your Echo Flash folder.  If you are not certain what this location is, refer to the StorageDir attribute in Application.xml file located under /conf/echolive in your Wowza installation root.

Enabling Closed Captioning for Live Streams

To enable the new Live Closed Captioning functionality available in EchoSystem 5.4, the following changes need to be made:

  1. Copy the entire echocaption directory from the /conf/ subfolder in extracted bundle location (from the Replacing the Echo360 Libraries section above) to the /conf/ directory under your Wowza installation root.
  2. Navigate to the /applications/ subdirectory of your Wowza installation root and create a new empty folder labeled echocaption
  3. In the newly copied /conf/echocaption directory of your Wowza installation root, open the Application.xml file in a text editor.

  4. Near the bottom of the file, the document contains a set of property values encoded like so:

    Code Block
    <Properties>
	<Property>
		<Name>objectstoragedirectory</Name>
		<Value>${com.wowza.wms.context.VHostConfigHome}/content/echocaption/rso</Value>
	</Property>
    <Property>
        <Name>captionlogstoragedirectory</Name>
        <Value>${com.wowza.wms.context.VHostConfigHome}/content/echocaption/captionlogs</Value>
    </Property>
    <Property>
        <Name>echosystemdirectory</Name>
        <Value>${com.wowza.wms.context.VHostConfigHome}</Value>
    </Property>
</Properties>

  5. Replace the ${com.wowza.wms.context.VHostConfigHome} string with the location of your Echo Flash directory. If you are not certain what this location is, refer to the StorageDir attribute in Application.xml file located under /conf/echolive in your Wowza installation root.

  6. Next, edit the layout.xml in the template directory of the EchoSystem Server

The default location on windows for this is: C:\echo360\content\templates\1f80f82f-91ba-408a-9a23-c74d701fe3f1\echo_files\layout.xml       Edit the file and update the <enable-live-caption> field to true.  If you are using the built-in wowza server, simply uncomment the <enable-live-caption> option.

Required Modification for Wowza 4.0

An external Wowza 4.0 instance is supported as of EchoSystem Server 5.4. The The following change is required for Wowza 4.0 to function properly with the EchoSystem Server. Failure to make this change will result in all on-demand and live streaming features ceasing to function.

  1. Under the /conf folder in your Wowza installation root, edit the Server.xml file. Find the following line:

    Code Block
    <DefaultStreamPrefix>mp4</DefaultStreamPrefix>

  2. Modify the value to change mp4 to flv, like so:

    Code Block
    <DefaultStreamPrefix>flv</DefaultStreamPrefix>

Once all the configuration files have been edited and saved according to these instructions, restart the Wowza service.

 

...