nanog mailing list archives

RE: txt.att.net outage?


From: "Simmons, Jay via NANOG" <nanog () nanog org>
Date: Fri, 20 Jan 2023 15:43:24 +0000

This may be the issue

Here are some details on this Government protocol implemented by all Telecom Carriers.

Why it is being done? To support FCC mandate for STIR/SHAKEN, an industry set of rules designed to authenticate and 
validate CallerID information associated with phone calls using digital signatures.

SHAKEN/STIR is a framework of interconnected standards. SHAKEN/STIR are acronyms for Signature-based Handling of 
Asserted Information Using tokens (SHAKEN) and the Secure Telephone Identity Revisited (STIR) standards.

What is the benefit to the clients being impacted (what do they get as a result)? Provide a means to mitigate/eliminate 
illegally spoofed calls from RoboCallers.






From: NANOG <nanog-bounces+jsimmons=semmes-murphey.com () nanog org> On Behalf Of Tim Burke
Sent: Friday, January 20, 2023 8:21 AM
To: Dan Walters <dwalters () omnigo com>; nanog () nanog org list <nanog () nanog org>
Subject: Re: txt.att.net outage?

EXTERNAL EMAIL
FWIW, AT&T does not suggest using the txt.att.net<http://txt.att.net> email for anything critical. In a previous role I 
handled public safety CAD, and AT&T (and Verizon, if I remember correctly) made it very clear that if you want to be 
able to send anything other than a miniscule volume of texts through the email-to-SMS gateway, you would need to pay 
for their enterprise messaging service.

If the public safety agency/agencies in question subscribe to the FirstNet service, they should be able to reach out to 
their principal consultant (account team) and get a good resolution.

V/r
Tim

________________________________
From: NANOG <nanog-bounces+tim=mid.net () nanog org<mailto:nanog-bounces+tim=mid.net () nanog org>> on behalf of Dan 
Walters via NANOG <nanog () nanog org<mailto:nanog () nanog org>>
Sent: Thursday, January 19, 2023 10:09 PM
To: nanog () nanog org<mailto:nanog () nanog org>
Subject: txt.att.net<http://txt.att.net> outage?


Know this is a longshot, any chance anyone from the txt.att.net<http://txt.att.net> domain might be able to help us 
with what we believe is a blacklist block or possibly an outage?

We deal with 911 cad dispatching and is affecting first responders so looking to see if there is a faster way to 
resolution.



Thanks, in advance.





Daniel Walters

Sr. Systems Admin

Phone: 866.421.2374 ext.6213

Daniel.Walters () omnigo com<mailto:Daniel.Walters () omnigo com>

[cid:image001.png@01D92C52.BEDD12C0]

[cid:image002.png@01D92C52.BEDD12C0][cid:image003.png@01D92C52.BEDD12C0] [cid:image004.png@01D92C52.BEDD12C0]



Current thread: