====== Alerts ======

The DV2000 provides the option to have email alerts sent to one or more email addresses for various system events, such as startup and shutdown of the main service.  You can administer the list of recipients as well as which events will generate alerts.  This will open the System Alerts dialog, as shown below.

{{:images:vs8:vsconfig:alerts-addresslist.png?direct|}}

===== Address List =====

The address list tab, shown above, is used to manage the list of email addresses that will be receiving the system alerts.  All addresses listed in the Address table will receive all email alerts.

==== Add an address ====

To add an address to the list, enter it in the Address edit box (shown above with the address ''bar@domain.com'') and then click **Add**.  The address will then be added to the table displayed on the lower part of the tab.

==== Delete an address ====

To delete an address, select it in the table and then click **Delete** to remove it from the list.

==== SysLog ====

Events can be sent to a local or remote SysLog server. 

^Setting^Description^
|//Listenser Address//|IP address or DNS name of server listening for SysLog messages.|
|//Port//|Port number for SysLog messages. Default is 514.|

===== Events =====

To configure which events will generate alerts, select the Events tab, as shown below.

{{:images:vs8:vsconfig:alerts-events.png?direct|}}

This tab shows an ordered list of checkboxes that you can select to enable alerting for each specific event.  The checkbox next to each top-level entry may be checked to select or deselect all sub-items; this is shown in the System section in the figure above.  Alternatively, you can check or uncheck individual sub-items, as shown in the //PMS// section.

==== System ====

System events are those affecting the DV2000 service as a whole:  //Startup, Shutdown, Restart// and //Warning//.  A Restart alert occurs when the system decides it needs to shutdown and restart itself, usually because a critical service the system depends upon is not functioning properly and needs to be restarted.  Warning alerts are sent when non-critical services have to be restarted.  (A non-critical service is one that can be restarted by itself without requiring a full system restart.)

==== Ping address ====
An address requested to be pinged has either been disconnected or connected. 

==== Telephony ====
The telephony system has been started, shutdown, connected or disconnected. Connected and Disconnected are used only for alerting about SIP PBX networking events including if a line was not registered.

==== PMS ====

PMS events are those relating to the hospitality server and its connection to the PMS.  //Startup// and //Shutdown// alerts are sent when the hospitality service starts up and shuts down, respectively.  Likewise, the //Connected// alert would be sent when the serial or TCP connection with the PMS has been established and a Disconnected alert would be sent if the connection is lost or has been disconnected during a shutdown.

==== Inventory server ====

Inventory server events are generated by the Inventory Server Interface (ISI) IVR application.  A //Disconnected// alert would be sent if the server loses its connection to the remote server.  A //Warning// alert is sent whenever a message packet fails due to maximum unsuccessful attempts to communicate the packet to the remote server.

==== Room status server ====

Room status server events are generated by the Room Status Interface (RSI) IVR application.  A //Disconnected// alert would be sent if the server loses its connection to the remote server.  A //Warning// alert is sent whenever a message packet fails due to maximum unsuccessful attempts to communicate the packet to the remote server.

===== Ping list =====
IP or DNS entries placed here will be pinged every **minute**. If it doesn't respond the system will log this in the DuVoice Event Report and Line Activity. When the device starts responding the amount of time the device was unreachable will be logged allowing techs to know how long.

The system will not log successful pings in order to keep the log database from filling up the hard drive. The DuVoice service is responsible for performing these pings and when a failure occurs it will be logged in it's TraceDisplay log.

Items from the list can be added or deleted while the system is running.

{{:images:vs8:vsconfig:alerts-ping.png?direct|}}

====== Example ======

===== Startup =====
This is an example of an alert about the system starting up.

**Subject**
<code>
System alert: System Startup at 14:24:36 on 2023/04/03 
</code>

**Body**
<code>
System alert: System Startup
Posted on 2023/04/03 at 14:24:36.

System Information:
Serial number: 10003
Version: 8.0.9
</code>

===== Ping source =====
**Subject**
<code>
System alert: ALERT 192.168.1.2 did not respond to a ping at 15:30:02 on 2023/04/03 
</code>

**Body**
<code>
System alert: ALERT 192.168.1.2 did not respond to a ping
Posted on 2023/04/03 at 15:30:02.

System Information:
Serial number: 10003
Version: 8.0.9
</code>