The Broadcasters' Desktop Resource

EAS News Archive: 2019

The idea is to bring some clarity to the issues and answer your questions.
For more detail on EAS and some Q&A, please check the EAS Issues.

12/2/19 – The IPAWS test this morning happened, but was one hour late in all time zones.

11/25/19 – If you did not get an IPAWS test this week, still no need to panic – there was no RWT. The FEMA did not express a reason, but did confirm all time zones did not get a test today.

11/13/19 – If you did not get an IPAWS test this week, there is no need to panic. It is probably due to the needed changes in the TLS security protocol and/or certificate.

11/6/19 – Due to the inability of sage alerting to deliver the necessary software update for handing security protocol TLS 1.2 (Part 11.56) until this week, the FCC has issued a Public Notice stating that stations unable to install the update may operate until January 7, 2020 without further authority.

The FCC expects most stations to accomplish the update much more rapidly, but has noted the 60 day period in the Rules (Part 11.35) to help contractors with many stations, for example, not to be consumed with the upgrades to the exclusion of all else. Also, some entities require purchase orders to buy the upgrade, which now can be expedited.

If your station is unable to accomplish the upgrade by November 8th, a note in the EAS log is sufficient for the time being. (Users of any EAS receiver are also allowed the same period of time, but as the upgrade has been available for long time, the FCC is not noting the period merely for those who have no good reason for the delay. While there is no indication they are doing this at this time, it is not beyond possibilities for the FEMA to identify which stations are not polling IPAWS with TLS 1.2)

11/4/19 – The FEMA has notified manufacturers that the new Federal Bridge certificate, needed to receive IPAWS/CAP tests and alerts after November 8th is now available.

NOTE: In addition to the new certificate, you need to be upgraded to TLS V1.2 protocols. DASDEC notes that their versions 3.1 and 4.1 are already TLS 1.2 ready. For sage units, you must get the upgrade Rev95.

IF YOU CANNOT DO IT BEFORE 11/8: IPAWS/CAP alerts/tests will not be received. If you are doing your best to update, but have time/availability problems, you should note it in the EAS log, that you were unable to accomplish this on time due to manufacturer delays. This is especially true for those of you who contact for a lot of stations.

8/26/19 – Today’s IPAWS RWT from the FEMA was missed in the Central and Mountain Time Zones – due to a FEMA server issue. Stations may wish to make a note in the logs, or wait for the FEMA’s monthly report in a week or so, and attach that. The FEMA reports that all was OK in the Pacific Time Zone.

8/15/19 – The FCC released a Public Notice and a list of settlements (totaling $634,000) from the Enforcement Bureau for misuse/abuse of the EAS (and WEA) tones. The settlements range from broadcast television (ABC’s Jimmy Kimmel Live! – $395,000) and radio (KDAY/KDEY – $67,000) to cable channels (AMC and Discovery). The FCC has said for some time it is serious about using EAS tones in promos, news, or commercials, although it has been somewhat lenient for news items following the Hawaii false alert.

There is one exception, the FEMA has produced a set of “simulated tones” which sound similar, but will not set off an EAS receiver, and that may be used for promos, news, etc.

8/7/19 – Well, the 2019 NPT came. Perhaps the best way to comment is that there is a lot work to do with the PEP (PEP Map is here) and daisy-chain – the way the EAS works when the Internet is down. Reports from Test Day noted quite a few stations reporting clean audio, and forwarded the test. However, other reports  noted a number of issues:
          1. The test did not reach some areas and states. Florida generally missed the test, as did the upper peninsula of Michigan, and parts of Georgia.
          2. In many places, there was no audio. Wisconsin generally had no audio due to a receiver failure. Some stations in ND, CO, NC, and NH also got no audio.
          3. Many sites reported “scratchy,” “unintelligible,” or audio with something underneath the NPT.
          4. Stations pulling from Sirius got overly hot audio, fairly distorted.
          5. It appears that Sirius sent a second NPT an hour later, perhaps in error.
          6. Some stations reported the same problem with the FCC’s ETRS site, where they were unable to file Form Two, but received messages essentially saying “the server is too busy.” Those that got to file Form Two, sometimes had to wait for well over an hour (or more) to get confirmation emails.

Already, some of the problems have been identified, and a few places are planning a “statewide re-do” to see if the daisy chain can be improved and made more reliable.

On the other hand, several states had severe storms occurring, which made reception of some sources difficult (or impossible) or crowded a bit by the local storms. Also, there were a number of RWT’s launched during the day by stations – nothing bad, but unnecessary.

There is no date for the FCC to report on the test, but we can hope they are able to summarize things quickly, so SECC’s and LECC’s can work on corrections.

7/28/19 – The Federal Register has published the FCC’s August 2018 changes to the EAS rules, which now require reporting false alerts – known to be false – to the FCC within 24 hours, and SECC’s filing news plans electronically.

7/25/19 – The FCC sent out letters today to a large number of stations – presumably testing the contact information from the Form One filings. Some person Kamal … no phone or other contact info, although the FCC servers do appear in the headers. After some calling to the FCC, it appears this was an attempt by someone at the FCC to push out a Public Notice. The link to the Public Notice is at here.

A later email says that there was some error on their part at

“You are receiving this email because you have filed in the ETRS or because you are an EAS Participant registered within an FCC database.?

“Some of you received an email earlier today from FCC Alerting.  The email was sent in error.  We apologize for the inconvenience.”

7/18/19 – Sage Alerting announced a required update on their EAS boxes. The update, required by November 8th, in needed to continue using IPAWS CAP feeds from the FEMA, which will be using TLS 1.2/1.3 (Transport Layer Security, previously known as SSL). This update is apparently NOT NEEDED before the NPT. At this time, it is understood that the upgrade will cost $349 per receiver.

Most other EAS boxes will not need an update to comply with the TLS 1.2/1.3. DASDEC reports that anyone with Version 3.1 or later (4.0) will be fine, with no further update needed now, nor in the fall.

7/12/19 – The FCC has again extended the Form One deadline. According to the ETRS site, the Form One deadline is now August 5th. If you have any questions on what to, there are now videos at the top of the ETRS page.  Additionally, the quickest way to get help – contact is at In case ETRS cannot help (they seem to rely quickly), the Public Notice shows legal issues may be addressed to Elizabeth Cuttner, Attorney Advisor, Policy and Licensing Division, Public Safety and Homeland Security Bureau, at or Maureen Bizhko, Attorney Advisor, Policy and Licensing Division, Public Safety and Homeland Security Bureau, at