Email Notifications

Broadsign Server can send email notifications to you and your staff when events occur on your network.

You can opt in and opt out of notifications for network status changes (connected, disconnected, MIA), incidents of all types and when changes are made to campaigns, ad copies and registrations.

Note: Incidents resolved manually in Broadsign Control Administrator will not trigger an email notification.

Email notifications are sent by Broadsign Server to registered contacts.

By adding a contact to a display unit, player or edge server, that contact will only receive notifications pertaining to that particular resource. However, by adding a contact to the domain, that contact will receive all notifications pertaining to all resources in the entire network.

Note: To receive SMS notifications on a mobile phone, configure a contact with the SMS gateway email address of the desired phone. The gateway email address can be provided by your mobile service provider (if this service exists).

For general information about contacts, see Contacts.

For a brief tutorial about creating a contact and assigning it to a domain, see Create a Contact.

For a brief tutorial about adding a contact to a player, see Monitoring.

The following video describes everything you need to know about creating a contact and enabling notifications for that contact.

Feature Spotlight: How to create contacts and enable notifications in the Broadsign's CMS

Note: This instructional video is also available in French and Spanish.

When a user adds ad copies to a campaign, you can opt in to receive the following email:

Subject Ad Copies added to Campaign 8805843
Body 
Affected Campaign:
Id: 8805843
Name: Random Video ~ C1
Created by User: chris
Created On: 12/30/18 8:19 PM
Start Date: 12/30/18 12:00 AM
End Date: 1/30/50 12:00 AM
Duration: 2 minutes
Saturation: 1 Play per loop

Affected Ad Copies:
Id: 4353938
Name: Least_Likely_PSA
Original File Name: Least_Likely_PSA.mpg
Size: 21 M and 522 K
Mime Type: mpg

When a user removes an ad copy from a campaign, you can opt in to receive the following email:

Subject Ad Copies removed from Campaign 3141013
Body 
Affected Campaign:
Id: 3141013
Name: A Few good Vids
Created by User: chris
Created On: 3/10/18 3:10 PM
Start Date: 3/10/18 12:00 AM
End Date: 4/10/35 12:00 AM
Duration: 15 seconds
Saturation: 1 Play per loop

Affected Ad Copies:
Id: 4353936
Name: BlizzardRetrospectiveUS
Original File Name: BlizzardRetrospectiveUS.avi
Size: 43 M, 625 K and 392 Bytes
Mime Type: avi

When a user approves a new ad copy, you can opt in to receive the following email:

Subject Ad Copy 8805830 approved
Body 
Id: 8805830
Name: wanted-tlr5_h720p
Approved by User: chris
Approved On: 12/30/18 7:54 PM
Size: 113 M, 730 K and 951 Bytes
Original File Name: wanted-tlr5_h720p.mov
Mime Type: mov

When a user deactivates a new ad copy, you can opt in to receive the following email:

Subject Ad Copy 8805823 deactivated
Body 
Id: 8805823
Name: mario_strikers
Deactivated by User: chris
Created On: 12/30/18 7:54 PM
Size: 56 M, 488 K and 548 Bytes
Original File Name: mario_strikers.avi
Mime Type: avi

When a user uploads a new ad copy, you can opt in to receive the following email:

Subject New Ad Copy 8805830 uploaded
Body 
Id: 8805830
Name: wanted-tlr5_h720p
Created by User: chrisc
Created On: 12/30/18 8:10 PM
Size: 113 M, 730 K and 951 Bytes
Original File Name: wanted-tlr5_h720p.mov
Mime Type: mov

When the player encounters an application fault, you can opt in to receive an email:

Subject Player 8492776 - Incident 15182030 Resolved: Application Fault
Body 
Id: 8492776
Name: TR - #27.95 - Windows
Type: Player
IP Address: 192.168.27.95
Private IP Address: 192.168.27.95
Domain: Production
Incident Id: 15182030
Incident Type: Application Fault
Problem Description: This application encountered a problem and needed to be restarted.
Reported On: 30 Dec 2017 21:03:50 (UTC)
Resolved Description: The application was restarted.
Resolved On: 30 Dec 2017 21:03:42 (UTC)

When a Synchronization Set uses a backup master, or when a backup master rejoins a synchronization set as a slave, you can opt in to receive an email:

Subject Incident 6044057 Resolved: Backup Master Activated
Body 
Id: 1929029
Name: player-win7
Type: Player
IP Address: 192.168.1.233
Private IP Address: 192.168.1.233
Domain: qa
Incident Id: 6044057
Incident Type: Backup Master Activated
Problem Description: Player 1929029 took mastership, synchronization set: abc.
Reported On: 21 May 2018 16:10:30 (UTC)
Resolved Description: Player 1929029 end of loop, synchronization set: abc.
Resolved On: 21 May 2018 16:10:32 (UTC)

For information about configuring a synchronization set, see Loop Policy Properties - Settings Section - Synchronization Tab.

For a tutorial that includes the use of a synchronization set, see Frame Synchronization.

For a description of best practices relating to synchronization sets, see Synchronization Set Best Practices.

When a user cancels a new campaign, you can opt in to receive the following email:

Subject Campaign 1977214 canceled
Body 
Id: 1977214
Name: Trial 1 Campaign Music/Book 2
Canceled by User: chris
Created On: 7/27/18 5:47 PM
Start Date: 7/27/18 12:00 AM
End Date: 8/27/18 12:00 AM
Duration: 30 seconds
Saturation: 1 Play per loop

When a user creates a campaign and they miss adding any of the following, you can opt in to receive an email:

The email notification is sent only for campaigns starting at a future date. The notification does not work for inactive campaigns.

Note: The Schedules missing content and Bundles missing content sections are not listed if there is no missing content.

Subject Campaign “name_of_campaign” is not ready - Missing Content
Body 
Problem: Missing Content in Campaign
Campaign Id: 8805830
Campaign Name: name_of_campaign
Campaign Starts On: 2022-01-01 at 00:00:00
Campaign Ends On: 2022-02-01 at 23:59:59
Timezone: Eastern (-400 GMT)
Created by User: username
Schedules missing content:
	8805832   name_of_schedule1
	8805834   name_of_schedule2
Bundles missing content:
	8805820   name_of_content1
	8805821   name_of_content1
	8805822   name_of_content1
	8805823   name_of_content1
	8805824   name_of_content1

Note: You can configure thresholds for this notification by double-clicking it or by selecting it and clicking the Edit button. You can also configure thresholds in both the campaign and customer folder properties. See Campaigns - Folder Properties, Contacts and Notifications and Customers - Folder Properties, Contacts and Notifications.

Note: To receive the notification, it must be checked in the Notifications tab of the contact that must receive the notifications. If notifications are configured both in the campaign or customers folder properties and in the contact settings, the folder configuration takes priority, unless the Override default settings option is checked in the contact settings.

When a user creates a campaign and they miss adding an active bundle, you can opt in to receive an email.

The email notification is sent only for campaigns starting at a future date. The notification does not work for inactive campaigns.

Subject Campaign “name_of_campaign” is not ready - No Content
Body 
Problem: No Media in Campaign
Campaign Id: 8805830
Campaign Name: name_of_campaign
Campaign Starts On: 12/30/18 at 09:00 AM
Campaign Ends On: 12/30/18 at 09:00 AM
Timezone: Eastern (-400 GMT)
Created by User: chrisc

Note: You can configure thresholds for this notification by double-clicking it or by selecting it and clicking the Edit button. You can also configure thresholds in both the campaign and customer folder properties. See Campaigns - Folder Properties, Contacts and Notifications and Customers - Folder Properties, Contacts and Notifications.

Note: To receive the notification, it must be checked in the Notifications tab of the contact that must receive the notifications. If notifications are configured both in the campaign or customers folder properties and in the contact settings, the folder configuration takes priority, unless the Override default settings option is checked in the contact settings.

When a user promotes a campaign from the "Held" state to the "Contracted" state, you can opt in to receive the following email:

Subject Campaign 8805834 promoted
Body 
Id: 8805834
Name: Sharks Tale ~ C1
Promoted by User: chris
Promoted On: 12/30/18 8:17 PM
Start Date: 12/30/18 12:00 AM
End Date: 1/30/50 12:00 AM
Duration: 1 minute
Saturation: 1 Play per loop

When a player freezes and must restart, you can opt in to receive an email:

Subject Player 8492776 - Incident 15182032 Reported: Deadlock
Body 
Id: 8492776
Name: TR - #27.95 - Windows
Type: Player
IP Address: 192.168.27.95
Private IP Address: 192.168.27.95
Domain: Production
Incident Id: 15182032
Incident Type: Deadlock
Problem Description: The application hung and needed to be restarted.
Reported On: 30 Dec 2017 21:11:39 (UTC)

The Device Error incident occurs when a device operation causes an error.

In our example, a device control operation (on player ID #682) erred while executing assert_power. Each device error incident contains a description of its cause and notes that the player's screen is off.

Subject Player 682 – Incident 89880 Reported: Display – Device Error
Body 
Id: 682
Name: DT44 San Francisco
Type: Player
IP Address: 192.168.27.213
Private IP Address: 192.168.27.213
Domain: daniels
Problematic Resource Id: 3077112
Incident Id: 403617
Incident Type: Display - Device Error
Problem Description: Problem with display device. Action "assert_power", value 1 failed on COM port "com_port1". The Device Opcode Id of the failed action is 3077112.
Command sent: "020503"
Expected response: "06"
Actual response: nothing
Reported On: 2/29/2018 5:46:52 PM (UTC)

Once you resolve the incident — in this case, by turning on the screen — Broadsign sends a resolved notification to relevant contacts.

Subject Player 682 – Incident 89880 Resolved: Display – Device Error
Body 
Id: 682
Name: DT44 San Francisco
Type: Player
IP Address: 192.168.28.241
Private IP Address: 192.168.28.241
Domain: DigitalSign
Incident Id: 89880
Incident Type: Display - Device Error
Problem Description: Problem with display device. Action "assert_power" failed.
Reported On: 22 Jun 2018 07:08:03 (UTC)
Resolved Description: Action "assert_power" succeeded.
Resolved On: 22 Jun 2018 14:09:20 (UTC)

When a player is not sending complete data to Broadsign Server during its polling you will be notified of an incident as follows.

Subject Player 2935095 - Incident 400445 Reported: Difficulties Polling
Body 
Id: 2935095
Name: TR # 30 - Player Windows XP
Type: Player
IP Address: 192.168.28.230
Private IP Address: 192.168.28.230
Domain: DigitalSign
Problematic Resource Id: 2935095
Incident Id: 400445
Incident Type: Difficulties Polling
Problem Description: Player 2935095 is having difficulties polling.
Missing Responses: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30.
Reported On: 25 Feb 2018 23:10:56 (UTC)

When a player has a full hard drive and — to continue its operation — deletes content currently scheduled to play, Broadsign creates a Disk Space Error. You will receive an email like this one:

Subject Player 1789920 – Incident 322585 Reported: Playback – Disk Space Error
Body 
Id: 1789920
Name: DT43 San Francisco
Type: Player
IP Address: 192.168.28.196
Private IP Address: 192.168.28.196
Domain: DigitalSign
Problematic Resource Id: 630211
Incident Id: 322585
Incident Type: Playback – Disk Space Error
Problem Description: The ad copy 630211 was deleted from disk to free some space although it is currently still in use.
Reported On: 21 Jun 2018 22:09:04 (UTC)

Once the incident has been resolved, contacts will be notified accordingly.

Subject Player 1789920 – Incident 322585 Resolved: Playback – Disk Space Error
Body 
Id: 1789920
Name: DT43 San Francisco
Type: Player
IP Address: 192.168.28.196
Private IP Address: 192.168.28.196
Domain: DigitalSign
Incident Id: 322585
Incident Type: Playback – Disk Space Error
Problem Description: The ad copy 630211 was deleted from disk to free some space although it is currently still in use.
Reported On: 21 Jun 2018 22:09:04 (UTC)
Resolved Description: The ad copy 630211 was successfully downloaded
Resolved On: 22 Jun 2018 23:27:27 (UTC)

When an outdoor display's temperature enters a range that you consider to be critical, you can opt in to receive an email. The message will indicate a temperature state of:

  • undefined
  • warning
  • critical
  • back to normal
Subject Critical: Player demo-floor-player - Incident 349 Reported: Display - Temperature Critical
Body 
Id: 3022
Name: demo-floor-player
Type: Player
IP Address: 192.168.24.80
Private IP Address: 192.168.24.80
Domain: root
Incident Id: 349
Incident Type: Display - Temperature Critical
Problem Description: The device temperature is now in critical state.
Reported On: 6/26/18 8:09 PM (UTC)

If you exceed your domain quota, Broadsign Server sends the following notification:

Subject Domain 1882067 - Incident 402759 Reported: Domain Quota Exceeded
Body 
Id: 1882067
Name: TR - #18 - Ubuntu
Type: Domain
IP Address: Not Available.
Private IP Address: Not Available.
Domain: DigitalSign
Problematic Resource Id: 1882067
Incident Id: 402759
Incident Type: Domain Quota Exceeded
Problem Description: Quota is exceeded by 341663635 bytes for domain Id 1882067.
Reported On: 2/28/2018 4:07:10 PM (UTC)

Once you have made room on your domain by deactivating ad copies, you will receive the following notification:

Subject Domain 1882067 - Incident 413697 Resolved: Domain Quota Exceeded
Body 
Id: 1882067
Name: TR - #18 - Ubuntu
Type: Domain
IP Address: Not Available.
Private IP Address: Not Available.
Domain: DigitalSign
Problematic Resource Id: 1882067
Incident Id: 413697
Incident Type: Domain Quota Exceeded
Problem Description: Quota is exceeded by 396920384 bytes for domain Id 1882067.
Reported On: 11 Mar 2018 15:39:05 (UTC)
Resolved Description: The following 1 inactive or least recently used content(s) will be archived: 3142869.
Resolved On: 11 Mar 2018 15:36:54 (UTC)

As with players, Broadsign sends an email notification when an edge server connects to Broadsign Server. In our example, an edge server registered for monitoring with Broadsign Server.

Subject Edge Server 75998 Contacted Server
Body 
20 Jun 2018 17:04:05 (UTC)
Id: 75998
Type: Edge Server
Status: Registering to server.
Action: Turning on monitoring.
Name: 192.168.28.237
IP Address: 192.168.28.237
Private IP Address: 192.168.28.237
Domain: DigitalSign

The only edge server incident involves a system going Missing in Action (MIA). The email notification allows you to work out which edge server has gone MIA, the last time that the system polled, and the reported time of the incident.

Subject Edge Server 97498 – Incident 102836 Reported: MIA
Body 
Id: 97498
Name: 192.168.28.118
Type: Edge Server
IP Address: 192.168.28.118
Private IP Address: 192.168.28.118
Domain: DigitalSign
Problematic Resource Id: 97498
Incident Id: 102836
Incident Type: MIA
Problem Description: Has not polled since 07/20/18 15:02:39 (UTC).
Reported On: 20 Jun 2018 15:49:00 (UTC)

Once you have resolved the MIA incident, all of the edge server's contacts will receive a follow-up email.

Subject Edge Server 97498 – Incident 102836 Resolved: MIA
Body 
Id: 97498
Name: 192.168.28.118
Type: Edge Server
IP Address: 192.168.28.118
Private IP Address: 192.168.28.118
Domain: costa
Incident Id: 102836
Incident Type: MIA
Problem Description: Has not polled since 07/20/18 15:02:39 (UTC).
Reported On: 20 Jun 2018 15:49:00 (UTC)
Resolved Description: Contacted Server.
Resolved On: 20 Jun 2018 16:02:39 (UTC)
Subject Edge Server 75998 Shutting Down
Body 
20 Jun 2018 17:04:05 (UTC)
Id: 75998
Type: Edge Server
Status: Unregistering from server.
Action: Turning off monitoring.
Name: 192.168.28.237
IP Address: 192.168.28.237
Private IP Address: 192.168.28.237
Domain: DigitalSign

When an emergency messaging is activated or de-activated, you can opt in to receive an email:

Subject Warning: Player Intel NUC i5 - Incident 987 Reported: Playback - Emergency Message Activated
Body 
Id: 43922
Name: Intel NUC i5
Type: Player
IP Address: 192.168.0.107
Private IP Address: 192.168.0.107
Domain: domain1
Incident Id: 987
Incident Type: Playback - Emergency Message Activated
Problem Description: Emergency mode activated.
Reported On: 10 Jan 2022 15:56:25 (UTC)

When a player runs out of available memory and restarts, you can opt in to receive an email. This notifications work for both regular emergency messaging and "atomic" emergency messaging (via Edge Server).

Subject Player 8492776 - Incident 15182029 Reported: Memory Exhausted
Body 
Id: 8492776
Name: TR - #27.95 - Windows
Type: Player
IP Address: 192.168.27.95
Private IP Address: 192.168.27.95
Domain: Production
Incident Id: 15182029
Incident Type: Memory Exhausted
Problem Description: The computer was rebooted because memory usage thresholds were exceeded.
Reported On: 30 Dec 2017 21:03:50 (UTC)

When a player does not have a local copy of the content scheduled to play, Broadsign generates a missing ad copy incident.

In the first message below, you can see that player ID #90002 should play content ID #92833, but that the player has not downloaded the content. This could mean that the download is not complete.

Viewing the player’s Download Report allows you to gather more information on the content's download progress. For more information about the download report, see Download Report.

Subject Player 90002 – Incident 100869 Reported: Playback – Missing Ad Copy
Body 
Id: 90002
Name: DT42 San Francisco
Type: Player
IP Address: 192.168.28.203
Private IP Address: 192.168.28.203
Domain: DigitalSign
Incident Id: 100869
Incident Type: Playback - Missing Ad Copy
Problem Description: Missing content file for content id 92833
Reported On: 12 Jun 2018 15:02:52 (UTC)

Once the system is able to display the ad copy successfully, Broadsign will message the relevant contacts.

Subject Player 90002 – Incident 100869 Resolved: Playback – Missing Ad Copy
Body 
Id: 90002
Name: DT42 San Francisco
Type: Player
IP Address: 192.168.28.203
Private IP Address: 192.168.28.203
Domain: DigitalSign
Problematic Resource Id: 92833
Incident Id: 100869
Incident Type: Playback - Missing Ad Copy
Problem Description: Missing content file for content id 92833
Reported On: 12 Jun 2018 15:02:52 (UTC)
Resolved Description: Content id 92833 now available.
Resolved On: 12 Jun 2018 15:06:17 (UTC)

When a user creates a new campaign, you can opt in to receive the following email:

Subject New Campaign 8805834 created
Body 
Id: 8805834
Name: Sharks Tale ~ C1
Created by User: chris
Created On: 12/30/18 8:16 PM
Start Date: 12/30/18 12:00 AM
End Date: 1/30/50 12:00 AM
Duration: 1 minute
Saturation: 1 Play per loop

When a user adds a new registration, you can opt in to receive an email:

Subject New Registration Added 8805859
Body 
Registration Id: 8805859
Registration Name: Registration Activated
Primary MAC: ac:23:ac:23:ac:24
Secondary MAC: None
Registration Type: Player
Destination Folder Id: 1997376
Destination Display Unit Id: 8471426
Configuration Id: 1939045
Replacing Resource Id: 0
Requested From IP Address: 192.168.2.60
Registration Method: Wizard

When a display unit contains a player that is without an active campaign (including preemptible campaigns) in the primary share and all secondary shares during opening hours, you can opt in to receive an email:

Subject Frame Fullscreen of DU1 has no scheduled campaigns on any share
Body 
Warning: No Active Campaigns are scheduled on any share for
frame Fullscreen of DU1 after 2018-05-26
Frame Id: 14807
Display Unit Id: 14805
Display Unit External Id: 12
Display Unit Name: DU1
Timezone: America/Montreal
Created by User: davidw
Players: 216 Win7 Android Imaging Box - 192.168.1.215

Note: You can configure thresholds for this notification by double-clicking it or by selecting it and clicking the Edit button. You can also configure thresholds in the display unit folder properties. See Display Units - Folder Properties, Contacts and Notifications.

Note: To receive the notification, it must be checked in the Notifications tab of the contact that must receive the notifications. If notifications are configured both in the display unit folder properties and in the contact settings, the folder configuration takes priority, unless the Override default settings option is checked in the contact settings.

When a display unit contains a player that is without an active campaign in the primary share during opening hours, you can opt in to receive an email:

Subject Frame Fullscreen of DU1 has no scheduled campaigns on primary share
Body 
Warning: No Active Campaigns are scheduled on primary share
of frame Fullscreen of DU1 after 2018-05-26
Frame Id: 14807
Display Unit Id: 14805
Display Unit External Id: 12
Display Unit Name: DU1
Timezone: America/Montreal
Created by User: davidw
Players: 216 Win7 Android Imaging Box - 192.168.1.215

Note: You can configure thresholds for this notification by double-clicking it or by selecting it and clicking the Edit button. You can also configure thresholds in the display unit folder properties. See Display Units - Folder Properties, Contacts and Notifications.

Note: To receive the notification, it must be checked in the Notifications tab of the contact that must receive the notifications. If notifications are configured both in the display unit folder properties and in the contact settings, the folder configuration takes priority, unless the Override default settings option is checked in the contact settings.

Broadsign Control allows a player to start in full-screen mode or minimized mode. If the player starts in minimized mode, Broadsign creates a Not Full Screen incident. You will receive an email like this one:

Subject Player 90002 – Incident 100870 Reported: Display – Not Full Screen
Body 
Id: 90002
Name: DT42 San Francisco
Type: Player
IP Address: 192.168.28.203
Private IP Address: 192.168.28.203
Domain: DigitalSign
Incident Id: 100870
Incident Type: Display - Not Full Screen
Problem Description: Full screen off.
Reported On: 12 Jun 15 15:03:47 (UTC)

Once you maximize the display to resolve the incident, Broadsign sends the following email notification to relevant contacts:

Subject Player 90002 – Incident 100870 Resolved: Display – Not Full Screen
Body 
Id: 90002
Name: DT42 San Francisco
Type: Player
IP Address: 192.168.28.203
Private IP Address: 192.168.28.203
Domain: DigitalSign
Incident Id: 100870
Incident Type: Display - Not Full Screen
Problem Description: Full screen off.
Reported On: 12 Jun 2018 15:03:47 (UTC)
Resolved Description: Full screen on
Resolved On: 22 Jun 2018 23:27:27 (UTC)

In Broadsign Control Administrator, a user can edit a configuration profile to set incident thresholds for CPU performance (the default values are 90% of CPU for over 15 seconds). These incidents show that a player is trying to play content beyond its hardware capabilities (e.g., too many videos playing simultaneously, high definition content on an under-powered machine, etc.).

If a player exceeds these defined thresholds, the player reports an incident and Broadsign Server sends a notification.

Note: The player is unable to resolve this incident on its own. You must manually resolve the incident in Broadsign Control Administrator. When an incident is resolved manually, Broadsign Server refrains from sending a notification.

Subject Player 436 - Incident 400448 Reported: Performance Problem
Body 
Id: 436
Name: TR - #18 - Ubuntu
Type: Player
IP Address: 192.168.28.218
Private IP Address: 192.168.28.218
Domain: DigitalSign
Incident Id: 400448
Incident Type: Performance Problem
Problem Description: The system has encountered a performance problem. The CPU usage threshold of 30% over 60 seconds has been exceeded.
CPU Usage [current/average]: CPU 0 [99%/30%]
Reported On: 25 Feb 2018 23:40:19 (UTC)

When a playback error of a particular ad occurs, Broadsign generates an incident and sends an email notification.

In the following example, we see that a playback error on content ID #74602 occurred on player ID #574. There are two likely causes: missing codecs or the content is not supported. For more information about supported content, see Content Formats.

Subject Player 574 – Incident 100812 Reported: Playback – Error
Body 
Id: 574
Name: DT41 San Francisco
Type: Player
IP Address: 192.168.28.247
Private IP Address: 192.168.28.247
Domain: DigitalSign
Incident Id: 100812
Incident Type: Playback - Error
Problem Description: Could not find an appropriate codec for content id 74602
Reported On: 11 Jun 2018 18:49:27 (UTC)

There are two possible states for a monitored player:

  • service started
  • service stopped

"Service started" occurs when a player registers for monitoring with Broadsign Server:

Subject Player 11537 Contacted Server
Body 
2018-05-25T16:57:33
Id: 11537
Name: Player 11537 - DT40 San Francisco
Status: Registering to server.
Action: Turning on monitoring.
IP Address: 62.107.129.248
Private IP Address: 192.168.35.128
Domain: DigitalSign

Whenever a player has gone Missing in Action (MIA), an incident will be generated. This email allows you to work out which player has gone MIA, the last time that the system polled, and the reported time of the incident.

Subject Player 574 – Incident 100871 Reported: MIA
Body 
Id: 574
Name: DT41 San Francisco
Type: Player
IP Address: 192.168.28.247
Private IP Address: 192.168.28.247
Domain: DigitalSign
Incident Id: 100871
Incident Type: MIA
Problem Description: Has not polled since 12 Jun 2018 14:44:20 (UTC).
Reported On: 12 Jun 2018 15:29:34 (UTC)

Once you resolve the MIA incident, Broadsign Server will send an email to all of the player's contacts.

Subject Player 574 – Incident 100871 Resolved: MIA
Body 
Id: 574
Name: DT41 San Francisco
Type: Player
IP Address: 192.168.28.247
Private IP Address: 192.168.28.247
Domain: DigitalSign
Incident Id: 100871
Incident Type: MIA
Problem Description: Has not polled since 12 Jun 2018 14:44:20 (UTC).
Reported On: 12 Jun 2018 15:29:34 (UTC)
Resolved Description: Contacted Server.
Resolved On: 12 Jun 2018 15:31:22 (UTC)

There are two possible states for a monitored player:

  • service started
  • service stopped

"Service stopped" occurs when a player "unregisters from Broadsign Server":

Note: In this case, the player has shut down properly. Unwanted shutdowns trigger a different notification. See Unexpected Shutdown.

Subject Player 11537 Shutting Down
Body 
2018-04-26T20:53:25
Id: 11537
Name: Player 11537 - DT40 San Francisco
Status: Unregistering from server.
Action: Turning off monitoring.
IP Address: 62.107.129.42
Private IP Address: 192.168.35.128
Domain: DigitalSign

When the scheduled ad copy's duration — specified when booking the campaign — is greater than the reserved slot duration, Broadsign Truncated Ad Copy incident occurs. You will receive an email like this one:

Subject Player 56890 – Incident 89790 Reported: Playback – Truncated Ad Copy
Body 
Id: 56890
Name: DT43 San Francisco
Type: Player
IP Address: 192.168.28.196
Private IP Address: 192.168.28.196
Domain: DigitalSign
Problematic Resource Id: 56856
Incident Id: 89790
Incident Type: Playback - Truncated Ad Copy
Problem Description: Truncated content file for bundle id 56856.
Reported On: 21 Jun 2018 22:09:04 (UTC)

Once you resolve the incident, Broadsign will message the relevant contacts.

Subject Player 56890 – Incident Resolved: Playback – Truncated Ad Copy
Body 
Id: 56890
Name: DT43 San Francisco
Type: Player
IP Address: 192.168.28.196
Private IP Address: 192.168.28.196
Domain: DigitalSign
Problematic Resource Id: 56856
Incident Id: 89790
Incident Type: Playback - Truncated Ad Copy
Problem Description: Truncated content file for ad copy 56856.
Reported On: 06/21/18 22:09:04 (UTC)
Resolved Description: Ad copy 56856 no longer truncated.
Resolved On: 22 Jun 2018 23:27:27 (UTC)

Unexpected Shutdown incidents occur when a player is forced to shut down by abnormal means. The shutdown could happen due to manual intervention (e.g., shutting down the machine using its Master Power switch or Reset button) or unforeseen circumstances (e.g., power outage). In such cases, you will receive an email similar to the one below.

Note: There is no 'Reported' incident notification for this type; as soon as Broadsign sends the email, you can safely resolve the issue.

Subject Player 15285 – Incident 7223 Resolved: Unexpected Shutdown
Body 
Id: 15285
Name: DT41 San Francisco
Type: Player
IP Address: 192.168.28.247
Private IP Address: 192.168.28.247
Domain: DigitalSign
Incident Id: 7223
Incident Type: Unexpected Shutdown
Problem Description: Unexpected Shutdown
Reported On: 12 Jun 2018 15:29:34 (UTC)
Resolved Description: The application was restarted.
Resolved On: 12 Jun 2018 15:31:22 (UTC)