![Monroe Electronics DASDEC-II User Manual Download Page 131](http://html1.mh-extra.com/html/monroe-electronics/dasdec-ii/dasdec-ii_user-manual_1828808131.webp)
One-Net/DASDEC User Manual
5-102
v3.0 | r1016
Remove the check mark from the box that says
All EAS codes trigger
the DVS168/EARS
device to enable EAS forwarding control. When configured, select an EAS code group
that will be used to check against the incoming forwarded alert. If any of the EAS codes
are included in the incoming forwarded alert, the alert will be sent to the DVS-168
client.
When an alert is forwarded to a DVS-168 client, a WAV file of the EAS audio and a
text file of the alert details are constructed. These are FTP’d to the DVS-168 client. A
socket is temporarily opened from the EAS device 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/ failure.
EAS NET
There are three sections on the EAS NET sub-tab: EAS NET Decoding, Web audio
streaming, and EAS NET Clients.
Configure EAS NET Decoding
EAS Net Decoding is included with the EAS NET license key.
Basic Operation
EAS NET operates by sending optional audio, optional text translations, and an EAS
event notification file from an EAS device to a remote device over LAN or WAN. There
are some differences depending on the chosen EAS NET protocol. SSH STDIN Only
does not offer sending of digital audio WAV files or text translations. DVS-168, a legacy
protocol, does not send the same type of event notification data as the other protocols.
For everything but DVS-168, the remote host/server device is sent as 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 DVS-168, 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 or a custom edited schema. The EAS
device EAS NET client interface provides a schema editor to create specialized schemas.
EAS NET Decoding Section