[sbe-eas] Need help identifying a IPAWS message in Arizona

[Dan Mettler]

Ken

If the viewer was watching on cable, is it possible that the cable head end is centralized in Maryland and is actually using an encoder/decoder based in Maryland to provide EAS information for Arizona?

Dan Mettler
Chairperson, IN SECC



> On Jan 18, 2023, at 2:50 PM, Ken Evans <ken_evans at wmdt.com> wrote:
> 
> 
> 
> I have received a very strange message today from an Emergency Management official in Arizona asking how someone in Arizona could receive a MARYLAND EAS RMT?
> 
> Not over the air!  That would take some skip.
> 
> The photo shown was not from Maryland from what I see.  
> 
> But the time was 10:40 AM (Arizona time) on January 11, 2023.  Originated by "...onz Department of Publ.."  all that is visible in the photo.
> 
> Message came from IPAWSCAP.
> 
> Maryland sends out a RWT on Wednesdays.  But that was not it.  Went at 00:15:00 on the 11th so wrong date and time.  Marylands RMT is always on the LAST Wednesday of the month.
> 
> First photo shows only Arizona county names.
> 
> So as IPAWS has to have a verifiable user, how do we find out where it came from.  I figure someone has something wrong going on.  
> 
> Oh yes, the viewer who sent out a tweet about it was watching cable.  
> 
> Any suggestions on how this could happen?  
> 
> Thanks for the help.
> 
> Regards,
> Ken Evans
> Chairperson, MD SECC
> ken_evans at wmdt.com <mailto:ken_evans at wmdt.com>
> 
> 
> _______________________________________________
> sbe-eas mailing list
> sbe-eas at sbe.org <mailto:sbe-eas at sbe.org>
> https://pairlist7.pair.net/mailman/listinfo/sbe-eas <https://pairlist7.pair.net/mailman/listinfo/sbe-eas>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist7.pair.net/pipermail/sbe-eas/attachments/20230118/aacaa3fb/attachment-0001.htm>