[EAS] EAS Digest, Vol 15, Issue 19

[Harold Price]

Tom,

The legacy box would see whatever FIPS code the converter sent.  It 
would be compared to the filters in the legacy box and would be acted 
upon accordingly, and if relayed, would be relayed with the FIPS 
code(s) it saw.  Further, anyone receiving that relayed alert would 
see that same FIPS code.

An EAS message must contain at least one location code.  The Sage 
ENDEC will ignore any messages that do not contain at least one location code.

Since the 000000 code wasn't specified in the spec, it isn't clear 
what will happen to a particular vendors legacy device if one is 
received, without testing.

Harold

At 05:05 PM 1/21/2012, Tom Spencer wrote:
>Er. would the legacy box following such a transferred location code even
>see an EAN with location code "000000", regardless of source?  If so (if
>the EAN will actually trigger regardless of location code), then what's
>all the shouting about?  It was my understanding that unless the EAS
>header contained the location code(s) enabled in the box, the box would
>ignore the alert.  If that's not the case, then there would be no need
>for the EAN to carry any location code at all... and the header could be
>filled with an ASCII space (CHR(32)) or something and still get the SAME
>(pun) results.
>
>The second objection has more merit, though.  But at least my proposal
>is a start...