For select APAC-based Signagelive customers, we now have an instance of Signagelive hosted in Sydney, Australia (in the ap-southeast-2 AWS region). This article will outline how customers in this region can access this particular Signagelive instance and what needs to be considered when doing so.
For the sake of this article, we will refer to this as the “Sydney-hosted version” of Signagelive.
How will this new Signagelive instance differ from the Signagelive I already use?
If you have used Signagelive up until this point, you’ll have been using the instance hosted in London (Rackspace).
It’s worth noting that the Sydney-hosted version of Signagelive we discuss in this article (ap-southeast-2) is an entirely new instance of Signagelive. Therefore, it’s best to consider this an entirely new application. As such, the following applies:
Signagelive Networks hosted in Rackspace (all previous Networks you will have had access to up until this point) will not be present in this Syndey-hosted instance of Signagelive
By extension of the above, all previous media players, licences, content (including assets, Playlists and Layouts), and users will also not be present in the Sydney-hosted instance of Signagelive
Based on the above, accessing this version of Signagelive will be as if you are accessing Signagelive for the first time.
In addition, in this first iteration of this Sydney-hosted version of Signagelive, some core Signagelive features and media players will not yet be supported. Please see the relevant section below for more information.
Please Note
Your data (content, media players, licences, networks, users, etc.) from the existing London (Rackspace) instance of Signagelive is still accessible and will remain so via the existing login URL. If you want this to exist in the Sydney-hosted version of Signagelive, you’ll need to create all of this anew in the new Signagelive instance.
Supported Signagelive Players and how to install Signagelive on a Player in the AWS server
One major difference between our Rackspace server and this Sydney-hosted server is the installation URLs for each media player. Therefore should you wish to install Signagelive on a Player that you intend on using in the new Signagelive instance, you’ll need to utilize the following unique Signagelive client installation URLs:
Player Type | Signagelive Version | Install URL | Installation Instructions |
ChromeOS (Web Store) | 2.2.293 | Follow the steps in this article, replacing the install URL with the one outlined in this table instead. | |
ChromeOS (Self-hosted) | 2.2.293 | Follow the steps in this article, replacing the extension ID for ojmmimbdmbckoiolcimkjihjlhagneal and use the URL in this table for your From a Custom URL field | |
Samsung Tizen 3.0+ (Standard) | 1.30 Build 234 | Follow the steps in this article, replacing the install URL with the URL outlined in this table instead. | |
Samsung Tizen 3.0+ (Portrait) | 1.30 Build 234 | Follow the steps in this article, replacing the install URL with the URL outlined in this table instead. | |
LG webOS 3.0+ | 1.997 Build 567 | Follow the steps in this article, replacing the install URL with the URL outlined in this table instead. | |
BrightSign Series 3/4 (Manual & BDeploy) | 1.50 Build 188 | Follow the steps in this article, downloading the specific Signagelive for BrightSign client listed in this table instead. | |
BrightSign Series 5 (Manual & BDeploy) | 1.55 Build 195 | Follow the steps in this article, downloading the specific Signagelive for BrightSign client listed in this table instead. | |
Electron Windows | 2.0.1 Build 161 |
| |
Philips | TBD | Follow the steps in this article, replacing the Signagelive for Philips client with the one outlined in this table instead. | |
Sony | 1.22 Build 10 | Follow the steps in this article, replacing the Signagelive for Sony client with the one outlined in this table instead. |
Unsupported Players
The following media players are currently unsupported on the AWS-hosted version of Signagelive:
IAdea (SMIL), including ViewSonic/Planar
Legacy PC Player
LG webOS 1.0 & 2.0 generations
Samsung (C, D & E Series and Tizen 2.4)
Philips Android 4.4 - Android 10
Supported Signagelive Features
See the table below for a summary of the currently supported Signagelive features in the Sydney-hosted version of Signagelive:
Feature | Supported |
Data Sync Services (all Integration Types) | No |
Google Calendar Integration | Yes |
Granular User Permissions | Yes |
Hierarchies | Yes |
Message Manager / Message Manager Template Editor | No |
O365 Calendar Integration | Yes |
Proactive Monitoring | No |
Approval Notification Emails | No |
Granted Network Access Emails | No |
Proof of Play | Yes |
Screen Takeovers | Beta |
SSO | No |
Weather | Yes This uses a specific MongoDB to store weather data also hosted in ap-southeast-2 |
Web Triggers | Yes This uses a specific Pusher instance also hosted in ap-southeast-2 |
Whilst support for the above-mentioned Signagelive features is not currently available in this new version of Signagelive, we aim to implement support for these features in due course.
How to access Signagelive via the ap-southeast-2 server
You can log into the Sydney-hosted version of Signagelive here: https://ap-southeast-2-1-login.signagelive.com
Please Note
If you are accessing the URL above for the first time, you will not be able to use your existing Signagelive user account as it does not exist in this instance of Signagelive. Please contact our Support Team if you are looking to acquire access to this Sydney-hosted version of Signagelive.
Are there any domains I need to whitelist?
Similarly to the Rackspace-hosted version of Signagelive, if you’re accessing the Signagelive user interface or installing Signagelive on Players hosted on the Sydney-based server, you’ll need to ensure that your devices can reach the following domains:
Domains (UI)
ap-southeast-2-1-login.signagelive.com
ap-southeast-2-1-web-service.signagelive.com
ap-southeast-2-1-ui.signagelive.com
ap-southeast-2-1-ui-networkapi.signagelive.com
ap-southeast-2-1-networkapi.signagelive.com
ap-southeast-2-1-ui-iam.signagelive.com
ap-southeast-2-1-mm.signagelive.com
ap-southeast-2-1-sl.signagelive.com
ap-southeast-2-1-static.signagelive.com
ap-southeast-2-1-proofofplayui.signagelive.com
ap-southeast-2-1-proofofplay-api.signagelive.com
ap-southeast-2-1-upload.signagelive.com
ap-southeast-2-1-weatherapi.signagelive.com
ap-southeast-2-1-calendarintegration.signagelive.com
ap-southeast-2-1-marketplaceapi.signagelive.com
ap-southeast-2-1-marketplace-ui.signagelive.com
ap-southeast-2-1-saml-api.signagelive.com
ap-southeast-2-1-media-update-api.signagelive.com
ap-southeast-2-1-proxy.signagelive.com
Domains (Players)
ap-southeast-2-1-player-api.signagelive.com
ap-southeast-2-1-time-api.signagelive.com
ap-southeast-2-1-iam.signagelive.com
ap-southeast-2-1-player-data-api.signagelive.com
ap-southeast-2-1-screenshot-api.signagelive.com
ap-southeast-2-1-calendar-api.signagelive.com
ap-southeast-2-1-wbt-api.signagelive.com
ap-southeast-2-1-proxy.signagelive.com
ap-southeast-2-1-weather-api.signagelive.com
ap-southeast-2-1-legacy-player-api.signagelive.com