[CRTech] Christian Radio Tech [MSG 83030]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
RE: Sage 3644 EAS box
To: 'CRTech' <crtech@crtech.org>
Subject: RE: Sage 3644 EAS box
From: nathaniel.steele@icloud.com
Date: Fri, 01 Jun 2018 05:16:03 -0500
Content-language: en-us
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1527848166; bh=3SSLNLs1R2ZrGTC07EmX7MeebrxFRm2UhHpCWszLrbU=; h=From:To:Subject:Date:Message-id:MIME-version:Content-type; b=RY6pJ5+AsjbSYmr7a2nsQWYi7UkKGce3jgJY2C2Sfg7we8Sc06q+IFx9OF5L0zRnY 6OIKNsly/NhripVXUA+ycy80oKy9BqerZqTHWnZc9Xuf9vXUJPNLrW3UKKC7vsofIP km9JAHQ1s8qMEvnLPlvwQj4nEhwJTr83h76KkugkO45nHU5U6YLb2YJkAwr3dWE9H/ 6NPA/G7u4E0HT0DHc4BdUrBE4UkfUvyRI4Fxd7efUFHbtjsk6TFL/2BlvRsfpobNZf RosOTI1kuQHClbcsqthP4IJjkpWSQ6LuuVWheAEngiN7+h79PJvr1DHLv0a5v2dhkT Wd26hyZdOL//Q==
In-reply-to: <CAH9-2GQ9PkAMVUA5sgGOXX+zrVxXxPSQPmrxmM0E2Mfd1VuggQ@mail.gmail.com>
References: <1b66cfbd-7eb8-38ba-ddc8-e4854d2489e4@bosscher.org> <002a01d3f82f$cf6e9ac0$6e4bd040$@icloud.com> <CALqA4kzXJj9JeWmv4J2_rhJcd4xn0dwsMJTMnxU+KJywRLdtPQ@mail.gmail.com> <CAH9-2GQ9PkAMVUA5sgGOXX+zrVxXxPSQPmrxmM0E2Mfd1VuggQ@mail.gmail.com>
Thread-index: AQKreFzC+av/imCENA3169mavxDl4gH9tsP3AUct0qwBsnYk/KJ0dzWg

Not sure if it was the firmware update or just the reboot but it works fine now.


Of course, Just reboot it…..




From: Marcos O'Rourke [mailto:mo@kwve.com]
Sent: Thursday, May 31, 2018 11:30 PM
To: CRTech <crtech@crtech.org>
Subject: Re: [CRTech] Sage 3644 EAS box


What does the log say on the sage? That should tell you if the email was successfully sent or not. 


On Thu, May 31, 2018 at 18:05 kgms Tucson <940kgms@gmail.com> wrote:

I haven't had the issue with Sage, but do you use a Google email and are the two units at different IP's? We had an issue like that with our Burk's and you have to go to settings in Google and authorize that IP to be able to send emails on your behalf. 




On Wed, May 30, 2018 at 9:03 AM, <nathaniel.steele@icloud.com> wrote:

I have two sages, setup identically as far as email is concerned. One will not send emails (or the emails don’t go anywhere). Theyre not in junk, they send to the same mail server, thru the same relay, from the same public IP. I seem to recall a post about a similar issue, does anyone remember the resolution? Only difference I noticed was the size of the base code is different, for the same FW on one unit, by a few Kb….


Maybe this new firmware will sort it out….


From: Tom Bosscher [mailto:tom@bosscher.org]
Sent: Tuesday, May 29, 2018 6:42 PM
To: CRTech <crtech@crtech.org>; sbe102@sbemich.org
Subject: [CRTech] Sage 3644 EAS box


if you have a Sage 3644 (blue) EAS Box, there is a firmware up date you will want to install:


>" Sage has released a firmware update that you must install to permit your ENDEC to continue to receive EAS CAP alerts from FEMA. A FEMA signing certificate will expire at 11:45am June 24, 2018; if you do not install this update, you will not receive CAP messages from the IPAWS system after that date.

This release also updates the SSL certificate roots that your ENDEC must have in order to download alert audio files from state or county alert originators."

Tom Bosscher



Marcos O'Rourke, CBRE CBNE
Chief Engineer
K-Wave Radio

Sent from Gmail Mobile

References: Sage 3644 EAS box
(Tom Bosscher <tom@bosscher.org>, 29 May 2018 23:41:58 -0000)
RE: Sage 3644 EAS box
(nathaniel.steele@icloud.com, 30 May 2018 16:04:10 -0000)
Re: Sage 3644 EAS box
(kgms Tucson <940kgms@gmail.com>, 1 Jun 2018 01:05:28 -0000)
Re: Sage 3644 EAS box
("Marcos O'Rourke" <mo@kwve.com>, 1 Jun 2018 04:30:39 -0000)
Prev by date: Re: Sage 3644 EAS box
(Marcos O'Rourke, 1 Jun 2018 04:30:39 -0000)
Next by date: Re: Sage 3644 EAS box
(Willie Barnett, 1 Jun 2018 14:24:45 -0000)
Prev by thread: Re: Sage 3644 EAS box
(Marcos O'Rourke, 1 Jun 2018 04:30:39 -0000)
Next by thread: Re: Sage 3644 EAS box
(Willie Barnett, 1 Jun 2018 14:24:45 -0000)