Contacts

A contact represents any person involved with, or interested in, your network. They can be internal employees or external stakeholders, e.g., installers.

Use contacts to set up email notifications. To monitor the status of network assets, you can assign contacts to various resources.

The “Contacts” training video is part of the “Network Operations” playlist:

Contacts: Outlines how to add and edit contacts, and how to set up notifications.

The Contact Book lists all the contacts created in the network, organized by contact Folder. It also contains a string search function which allows one to quickly search for a contact, either by their name or their email address.

The main function of a contact is to be able to monitor equipment on the network. More specifically, Broadsign Player systems, represented by Players, Display Units, and Broadsign Edge Server systems, represented by Edge Servers.

When a contact is assigned to a Player or Edge Server, the Broadsign Server sends notifications to that contact’s email address, informing him about any pertinent event involving that resource. When a contact is assigned on a Display Unit the Server will send notifications involving incidents with the Players in that Display Unit.

These events include when the corresponding Player or Edge Server goes into the MIA (Missing In Action) state, meaning it has unexpectedly stopped communicating with the Server, and when it has regained its connection. Additionally for Players, notifications are sent when an Incident involving them is opened, and when that incident is resolved.

A contact can also be assigned to receive notifications for all Players, Edge Servers and Display Units on their network by a network administrator.

The Contact Book

For detailed instructions about how to add a contact, see Network Operations – Create a Contact.

A contact’s general contact information can be viewed and edited in the General tab of the Contact Properties dialog. This includes the type of contact that he is, his phone number and extension, and his email address. While the other information is for filing and informational reasons only, the email address is used by the Server to send notification emails.

A contact can have one or more mailing addresses entered for them in the Address tab of the Contact Properties dialog for the Broadsign Administrator user’s bookkeeping needs.

resources-contacts-general

resources-contacts-information

resources-customers-contacts-notifications

A Contact that has been registered to receive email notifications can choose which notifications to receive in the Notification Tab of the Contact Properties Dialog.

resources-customers-contacts-notifications

The possible notification types are:

    • Contacted Server Notifications: Receive an email every time a Player or Edge Server comes online.
    • Unregistered To Server Notifications: Receive an email every time a Player or Edge Server shuts down and goes offline.
    • Missing in Action Incident Notifications: Receive an email every time a Player or Edge Server misses it’s next expected poll period and when a Missing In Action Incident changes status (Warning, Critical, Resolved).
    • Display Device Error Incident Notifications: Receive an email every time a Player fails to properly execute an RS232 screen control command and when a Display Device Error Incident changes status (Warning, Critical, Resolved).
    • Display Not Full Screen Incident Notifications: Receive an email every time a Player is not running full screen and when a Not Full Screen Incident changes status (Warning, Critical, Resolved).
    • Playback Error Incident Notifications: Receive an email every time a Player fails to properly play back an Ad Copy and when a Playback Error Incident changes status (Warning, Critical, Resolved).
    • Missing File Incident Notifications: Receive an email every time a Player needs to play a specify file but that file is not present locally. Also receive an email when a Missing File Incident changes status (Warning, Critical, Resolved).
    • Truncated File Incident Notifications: Receive an email every time a Player fails to play an ad copy for its specified length and when a Truncated File Incident changes status (Warning, Critical, Resolved).
    • Disk Space Incident Notifications: Receive an email every time a Player fails to write information to the hard drive and when a Disk Space Incident changes status (Warning, Critical, Resolved).
    • Unexpected Shutdown Incident: Receive an email every time a Player is unexpectedly shut down and when an Unexpected Shutdown Incident changes status (Warning, Critical, Resolved).
    • Difficulties Polling Incident Notifications: Receive an email every time a Player fails to receive a complete response from the Server.
    • Performance Problem Incident Notifications: Receive an email every time a Player exceeds its performance threshold.
    • Domain Quota Exceeded Incident Notifications: Receive an email every time Ad Copies are archived Player and when a Domain Quota Error Incident changes status (Warning, Critical, Resolved).
    • Ad Copy Uploaded Notifications: Receive an email every time a user uploads a new Ad Copy.
    • Ad Copy Approved Notifications: Receive an email every time a user approves an Ad Copy.
    • Ad Copy Deactivated Notifications: Receive an email every time a user deactivates an Ad Copy.
    • New Reservation Created Notifications: Receive an email every time a user creates a new reservation or Campaign.
    • Campaign Promoted Notifications: Receive an email every time a reservation is promoted to a Campaign.
    • Campaign Canceled Notifications: Receive an email every time a Campaign is cancelled.
    • Ad Copy Added to Campaign Notifications: Receive an email every time an Ad Copy is added to a Campaign.
    • Ad Copy Removed from Campaign Notification: Receive an email every time an Ad Copy is removed from a Campaign.
    • Registration Activated Notification: Receive an email every time a registration is activated and promoted into an active Player resource.
    • Application Fault Incident Notifications: Receive an email notification every time a Player encounters an application fault.
    • Memory Exhausted Incident Notifications: Receive an email notification every time a Player runs out of memory.
    • Deadlock Incident Notifications: Receive an email notification every time the shell restarts the Player process due to a deadlock.
    • Backup Master Activated Notifications: Receive an email notification when a Synchronization Set uses a backup master, and when a backup master rejoins a synchronization set as a slave.
    • No Scheduled Campaign Notifications: Receive an email notification when a Display Unit contains a player that is without an active campaign during opening hours.