Digital Alert Systems DASDEC-II MANUAL - Manual (Page 93)

Digital Alert Systems: DASDEC User Manual
87
Setup > Net Alerts > DVS168: FIPS and EAS Options
When an alert is forwarded to a DVS-168 client, a WAV file of the EAS audio is constructed and a text file of
the alert details is constructed. These are FTPed to the DVS-168 client. Then a socket is temporarily opened
from the One-NetSE to the DVS-168 client, and a control message is sent that describes the alert. The
Operation Log will log each of these actions and their success or failure.
4.10.2 EAS NET
There are three sections on the EAS NET sub-page to configure: EAS NET Decoding, Web audio streaming,
EAS NET Clients.
1. Configure EAS NET Decoding
EAS Net Decoding is included with the EAS NET license key.
Discussion: EAS NET Basic Operation
EAS NET operates by sending optional audio, optional text translations, and an EAS event notification file
from a DASDEC II to a remote device over a LAN or WAN. There are some differences depending upon the
chosen EAS NET protocol. SSH STDIN Only does not offer sending of digital audio WAV files or text
translations. DVS168, being a legacy protocol, does not send the same type of event notification data as the
other protocols. For everything but DVS168, the remote host/server device is sent an event text file or ASCII
data sequence that contains a set of key=value style data lines describing the EAS alert. For every protocol
but SSH STDIN Only and DVS168, the text event file by default is copied into the remote host file
EAS_NET_ALERT under the remote user home directory. This filename and path can be overridden when
configuring the client schema file. A standard set of information fields is sent in the text file, but the actual
names of the keys can be custom edited per client according to a programmable schema. Each client can
be set to use the Default schema or can use a custom edited schema. The DASDEC II EAS NET client
interface provides a schema editor to create specialized schemas.
There is only one toggle button to enable EAS NET decode. Check the toggle labeled "EAS_NET decode
from remote EAS NET sending devices". The DASDEC II will then be able to receive alerts sent via EAS
NET send from a properly configured remote DASDEC II. EAS NET decoded alerts are clearly labeled in the
Decoder > Decoded Alerts status page as being received from input channel EASNET. The alert event
files are stored in a separate disk storage area from audio decoded alerts. Other than those differences,