[EAS] Sage update coming in Sept.

[Mike McCarthy]

This is why I threw out the inhibit function. The automation has control
to the extent the EAS box filters define the inhibit and for how long,
eventually timing out by box rule to forward or die if not released by the
automation.  The EAS box then sends back a closure to say "I'm done". It's
a handshake arrangement.

I know "immediate" means without delay. I recall the thread where it was
debated whether the message forward must be started before incoming
reception is complete (near real time), or where the forward begins upon
completion of the incoming message.

To honest, I feel it's the former if it can be done. I say this based on
the fact the EAN does not have a time limit.  So any trailing end of
message (The EAT) time is undefined. It could be 30 seconds, or an
hour...or a half day....assuming we're around for that long....  But if a
box waits for that EAT, then it will not start the forward process.

Food for thought.

So....

MM

On Fri, July 19, 2019 2:06 pm, Sean Donelan wrote:

> 15 years later, the FCC still can't explain what "live" or "immediate"
> means.  Which makes it hard to define specifications for automation
> integration.