How do Players communicate with the CMS?


All signage players supporting the Xibo CMS communicate over “web services”. These are available on the CMS via normal HTTP (the same communication method used to view web pages).

Each player has a Collection Interval which determines how often they connect to the CMS to download updated schedule information and new content.

There are 8 pieces of information regularly exchanged between Players and the CMS.

  • Register
  • Required Files
  • Schedule
  • File Download
  • Resource Download *
  • Media Inventory Status
  • Logging
  • Proof of Play Statistics

The 1.7 CMS introduced 2 more

  • Screenshot *
  • Status *

The starred services communicate outside the collection interval because they are driven be events that occur during normal running of the player.

Resource Download

Resources include anything required by the Player which is not a media file stored in the library. Examples of this are RSS Feeds, Twitter Feeds, Text on Layouts. How often these are requested is controlled by the update interval set on that media. If there isn’t an update interval then a default of 5 minutes is applied.

After the first time resources are downloaded, they are only updated when they are shown on a Layout.

External Sources

Widgets like web pages and embedded HTML make also request connection to external resources (or even the CMS, depending how the widget has been designed). These will only be requested when they are shown on a Layout.

Expiring all the schedules and playing a default layout on a button click
Android Clients connect CMS too often (> 1.7 R52)
No layout change after an expired schedule
Many connections to CMS Server
Group assignment doesn't trigger Xibo client
“Display is out of date but has not yet checked in with the server”
Debugging Xibo client 1.8.2 in visual studio
Layout not updated by watch dog
Weather layout problem