One-Net/DASDEC User Manual
5-107
v3.0 | r1016
option is licensed. A TCP socket is used to communicate an EAS event notification
as per the Minerva protocol.
•
WideOrbit
–
This is a special protocol bundled under EAS NET when the EAS NET
Automation option is licensed.
•
RCS Nexgen
– This
is a special protocol bundled under EAS NET when the EAS NET
Automation option is licensed.
Event Data IP control options
(or Event/Ancillary Data IP control options)
Remote EAS NET Host IP Address
– Enter the host name or IP address of the remote
host computer
EAS_NET Event Transfer Protocol
•
Secure Copy
•
Secure Shell STDIN Only
•
Secure Shell STDIN & Copy
•
FTP Copy
•
TCP Event Notification
•
DVS168/EARS
•
Legacy Mediaroom
•
Mediaroom2
•
MINERVA
•
WideOrbit
•
RCS Nexgen
Remote EAS NET Host Port
- The field displays the port on the remote EAS NET host
where the EAS NET event info is sent.
FTP Ancillary Data File control options
EAS NET User
- Displays the user account name on the remote device. Files sent to the
remote host will by default be copied relative to this account home directory.
Current Schema
The schema determines key names of the information fields sent to the EAS NET
client’s remote host. It also determines file names and paths for any files sent to the
remote host. The schema can be edited by clicking on the
Edit/Review Schema
button.
Other possible EAS NET Client Configuration Options
Not all of these options will appear for every EAS NET transfer protocol.
Client sends EAS NET alert info during alert play-out
When this option is enabled (checked) the EAS NET alert info is sent out prior to alert
play-out. EAS NET prior send is only needed with EAS NET compatible equipment that
depends upon GPI controlled delayed alert play-out.
SSH Public Encryption Key
link.
The SSH based protocols provide this link to the display of the EAS device public key.
This must be copied to the remote host’s authorization file.
Note
T
he schema does not set
the values of the client
interface fields.