[EAS] Ipaws to switch to commercial providors?

[David Turnmire]

On 12/27/2013 5:54 PM, Randall Miller wrote:
> ...
> reinforce my non-understanding of why ALL local CAP messages are to be channeled through IPAWS.
> ...
Where did you get that idea?  That is a state choice.  In some cases, 
probably even a local one.  A number of states have their own CAP 
server... or at least have contracted with a commercial provider for 
that service.  That server may in turn feed a copy to IPAWS for 
redundancy and WEA, but one certainly can't say "ALL local CAP messages" 
are routed via IPAWS.  Indeed, in my state, IPAWS isn't currently 
getting ANY of our CAP messages, though that should change in the coming 
weeks.

Obviously having your own CAP server involves some expense, but it also 
has its upsides, one of which is added redundancy.  Not a bad thing in 
general.  And last I heard (maybe I'm out-of-date on this), some still 
are missing occasional IPAWS RWTS for unknown reasons. Can't say as I 
have ever missed one here (assuming it was in fact originated), but I 
also haven't missed one from MyStateUSA.  So..., I get "two bites at the 
apple" regarding IPAWS originated alerts (since MyStateUSA also forwards 
those), and soon I'll get three chances for the locally generated 
alerts... MyStateUSA, IPAWS, and legacy SAME encoded.  Now, if IPAWS can 
just work out their technology issues with EANs...

Dave