Digital Alert Systems DASDEC II User Manual page 99

Setup > Net Alerts > EAS_NET Client Configuration > FIPS trigger interface
All EAS codes trigger
If enabled, all EAS codes will trigger the EAS NET client interface. In the next screen shot this option is
enabled. Set the checkbox to enable/disable EAS code filtered trigger control. If disabled, then the alert EAS
code is filtered for a specific match as a way to control whether or not EAS NET is triggered. If All EAS is
disabled, select EAS codes from the provided lists and add to the client EAS list. If the EAS FIPS codes of
an active forwarded/originated alert match any of these EAS FIPS codes, the alert will be sent using the
EAS NET client. With careful use of this feature, and with multiple clients, one DASDEC II can serve many
different cable regions at the same time.
When you finish making changes, click to save the configuration.
Discussion: Since EAS NET is used in conjunction with third-party management software (on the remote
host), typically, configuration details will depend upon the exact third-party solution. Often instructions will be
provided by this party. Configure the EAS NET client interface as required.
DVS168/EARS devices
DVS168/EARS can be selected as an option on the EAS NET Event Transfer Protocol selector. See the
screen shot below. Like the other EAS NET protocols, the EAS NET remote host IP address and port must
be entered. This would be the address and port of the DVS168/EARS server. Standard DVS168 uses FTP
to send data files, so an EAS NET FTP user and password value must also be entered for a standard client
configuration. However, there is an option to disable the FTP send. This is for servers that do not support
handling digital file data but can be alerted by the DVS168 event protocol. If this option is checked the FTP
user and password values are not displayed or needed since the audio and video files will not be sent.
93
Digital Alert Systems: DASDEC User Manual