Echo360 is a web-based application that uses a browser to view content and as such has certain browser requirements. Beyond ensuring you're using a supported browser, there are also some configuration settings you may need to check or change to successfully use Echo360.
If you access Echo360 directly through the Echo360 URL, you may not need to change any of your browser configurations. However if you access Echo360 through an LMS such as Canvas or Moodle or Blackboard, and PARTICULARLY if the Echo360 window is opened inside of a browser frame, the below-listed changes to the Google Chrome and Mozilla Firefox browser settings may be necessary in order to view Echo360 class recordings and LIVE streams as provided.
Enabling Cookies in Chrome
Cookies contain some of the current session and authorization information we need to know who you are and to allow you to view content. This is especially important where a main website such as the LMS or your University Portal tries to open Echo360 inside of a frame. In this case, the cookies are necessary for the two authentication mechanisms to talk to each other and open Echo360 content for you.
Cookies are enabled in Chrome by default. However, in the event they are blocked, you may need to allow them to view Echo360 content. If you are using Chrome across mobile devices (and are signed in with a Google login) the Advanced settings described here are configured on the Primary device and are typically applied across ALL devices.
Chrome retains its cookie settings in the Advanced portion of the Settings page.
To allow cookies in Chrome
- Open Chrome
- Click the Configuration and Customization button on the top right of your Chrome toolbar, then select Settings from the menu that appears, as shown in the below figure.
- Type the word "cookies" in the search box at the top of the Settings page to be directed to the Cookies settings in Chrome.
- Select Content settings as identified both by the "cookies" search and in the above figure.
- Select Cookies to review current cookie settings.
- In the Cookies page, check or change the following settings as needed to match those shown in the below figure:
- That the Allow sites to save and read cookie data toggle is turned ON.
- That the Block third-party cookies setting is turned OFF.
- Close the Settings tab.
Configuring Chrome to use Flash for LIVE Streaming
Live streams are tested on and supported for viewing using all of the supported browsers, as long as your installed version of Adobe Flash is reasonably recent. (Adobe will probably let you know if it needs to be updated...they're good like that.) For reference, at the time of this writing the current version is 29.
Because Flash is used to provide Live streams, your browser must have permission to play Flash content. The thing is that Chrome does not natively allow websites to play Adobe Flash content. While you may receive a message that your Flash Player is out of date, it is more likely that you need to update your browser permissions to either always allow Flash to play, or set an exception for the Echo360 URL to allow Flash. If you choose to set an exception, be sure to list your region's URL specifically. The procedure below is the easiest way to set an exception to allow Echo360 to play Flash content.
To enable Flash for Echo360 in Chrome
- Open Chrome and navigate directly to the Echo360 login site. The URL will differ slightly depending on your region: US=echo360.org, UK/EU=echo360.org.uk, AU/ANZ=echo360.org.au, or CA=echo360.ca.
YOU DO NOT NEED TO LOG IN!!
- To the left of the URL in the URL address bar you should see a Green Lock icon. Click it.
- In the popup that appears, use the drop-down list for the Flash entry to select Always allow on this site, as shown in the below figure.
- When finished, click outside of the popup to close it.
If viewing the Live stream on a mobile device, Echo360 automatically buffers 40 seconds of the stream to ensure smooth playback. This means you may experience a delay in the start of the stream, and that your view will lag anywhere from 30 seconds to a minute behind the real-time action.