Mailing List Archive

And, for your further amusement…
…apparently Slack still don’t know why they’re down.

Probably because they try to use Slack to discuss it.

https://status.slack.com/2021-09/06c1e17de93e7dc2



-Bill



_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages
Re: And, for your further amusement… [ In reply to ]
Perhaps they're also not aware of the Letsencrypt intermediate certificate
expiring as well and they have some internal stuff encrypted with LE?
https://community.letsencrypt.org/t/r3-intermediate-certificate-has-expired-it-issued-certs-past-its-expiration-date/160797
The timings seem to be consistent

On Thu, 30 Sept 2021 at 12:48, Bill Woodcock via Outages <
outages@outages.org> wrote:

> …apparently Slack still don’t know why they’re down.
>
> Probably because they try to use Slack to discuss it.
>
> https://status.slack.com/2021-09/06c1e17de93e7dc2
>
>
>
> -Bill
>
>
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
Re: And, for your further amusement… [ In reply to ]
I have a handful of clients that use LE on their FreePBX phone
servers...and it's starting to look like the Digium D-series phones don't
trust the new root certificate yet.
No SIP-TLS, no SRTP, no "phone apps".
Trying to debug those phones via syslog without being able to SSH into them
and run commands and look at files is horrible.

"State phone.idle, process event:
error.sip_transport.SIP_TLS_CERT_INVALID.0x00000004"

Maybe it's a coincidence, but the http://digium.com/ website is down too.
I know they merged with Sangoma recently, but I couldn't imagine they'd
just dump the domain.

-A

On Thu, Sep 30, 2021 at 12:39 PM Ken Gilmour via Outages <
outages@outages.org> wrote:

> Perhaps they're also not aware of the Letsencrypt intermediate certificate
> expiring as well and they have some internal stuff encrypted with LE?
> https://community.letsencrypt.org/t/r3-intermediate-certificate-has-expired-it-issued-certs-past-its-expiration-date/160797
> The timings seem to be consistent
>
> On Thu, 30 Sept 2021 at 12:48, Bill Woodcock via Outages <
> outages@outages.org> wrote:
>
>> …apparently Slack still don’t know why they’re down.
>>
>> Probably because they try to use Slack to discuss it.
>>
>> https://status.slack.com/2021-09/06c1e17de93e7dc2
>>
>>
>>
>> -Bill
>>
>>
>>
>> _______________________________________________
>> Outages mailing list
>> Outages@outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
Re: And, for your further amusement… [ In reply to ]
There is an update to FreePBX you'll want to install for the "certman"
module. Install it from the edge repo, and it should fix the local LE
intermediate cert issue on the PBX. Unsure of D-series phone
operation/interaction though.

"digium.com" (un)availability is due to some changes in site hosting
the web heads are working on. Should be clear now!

--Tim (CloudNetEng @sangoma)

On Thu, Sep 30, 2021 at 3:48 PM Aaron C. de Bruyn via Outages
<outages@outages.org> wrote:
>
> I have a handful of clients that use LE on their FreePBX phone servers...and it's starting to look like the Digium D-series phones don't trust the new root certificate yet.
> No SIP-TLS, no SRTP, no "phone apps".
> Trying to debug those phones via syslog without being able to SSH into them and run commands and look at files is horrible.
>
> "State phone.idle, process event: error.sip_transport.SIP_TLS_CERT_INVALID.0x00000004"
>
> Maybe it's a coincidence, but the http://digium.com/ website is down too. I know they merged with Sangoma recently, but I couldn't imagine they'd just dump the domain.
>
> -A
>
> On Thu, Sep 30, 2021 at 12:39 PM Ken Gilmour via Outages <outages@outages.org> wrote:
>>
>> Perhaps they're also not aware of the Letsencrypt intermediate certificate expiring as well and they have some internal stuff encrypted with LE? https://community.letsencrypt.org/t/r3-intermediate-certificate-has-expired-it-issued-certs-past-its-expiration-date/160797 The timings seem to be consistent
>>
>> On Thu, 30 Sept 2021 at 12:48, Bill Woodcock via Outages <outages@outages.org> wrote:
>>>
>>> …apparently Slack still don’t know why they’re down.
>>>
>>> Probably because they try to use Slack to discuss it.
>>>
>>> https://status.slack.com/2021-09/06c1e17de93e7dc2
>>>
>>>
>>>
>>> -Bill
>>>
>>>
>>>
>>> _______________________________________________
>>> Outages mailing list
>>> Outages@outages.org
>>> https://puck.nether.net/mailman/listinfo/outages
>>
>> _______________________________________________
>> Outages mailing list
>> Outages@outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>
> _______________________________________________
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
_______________________________________________
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages
Re: And, for your further amusement… [ In reply to ]
Back in the day, I was responsible for an SMSC in one of the early GSM carriers. It meant that I had to carry a pager AND my phone because I needed to get alerts of the phone's messaging system didn't work.

On September 30, 2021 11:28:19 AM PDT, Bill Woodcock via Outages <outages@outages.org> wrote:
>…apparently Slack still don’t know why they’re down.
>
>Probably because they try to use Slack to discuss it.
>
>https://status.slack.com/2021-09/06c1e17de93e7dc2
>
>
>
> -Bill
>
>
>
>_______________________________________________
>Outages mailing list
>Outages@outages.org
>https://puck.nether.net/mailman/listinfo/outages