<div dir="ltr">Collin,<div><br></div><div>It appears to me that AT&T wireless attempted to fix your problem today. Apparently it didn't go well. Congrats on bringing down their network!</div><div><br></div><div>-jbn<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 20, 2024 at 1:02 PM Collin Rose via VoiceOps <<a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg-610225314277977782">
<div lang="EN-US" style="overflow-wrap: break-word;">
<div class="m_-610225314277977782WordSection1">
<p class="MsoNormal"><span style="font-size:11pt">Well the email is for an STP group of some sort, they can’t create a ticket, but were able to tell me when calls started failing, and that Frontier needs to open a ticket with ATT Mobility since they are directly
connected.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Haven’t been able to convince Frontier to do anything, as they claim AT&T is routing the calls incorrectly to them on the wrong group (AT&T STP folks say the TCICs changed at the time the calls started failing).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Have engaged PSC for assistance, still have been unable to get anyone at ATT to actually accept a ticket from me. We have hundreds of customers complaining, and we have been steering them to ATT. Many of them
are being told it’s not their problem. Others are being told the “local site is degraded” and they are working on it.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Appreciate any help anyone can provide!<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Collin R</span><span style="font-size:11pt"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<div id="m_-610225314277977782mail-editor-reference-message-container">
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal" style="margin-bottom:12pt"><b><span style="color:black">From:
</span></b><span style="color:black">VoiceOps <<a href="mailto:voiceops-bounces@voiceops.org" target="_blank">voiceops-bounces@voiceops.org</a>> on behalf of Collin Rose via VoiceOps <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>><br>
<b>Date: </b>Tuesday, February 20, 2024 at 11:14</span><span style="font-family:Arial,sans-serif;color:black"> </span><span style="color:black">AM<br>
<b>To: </b>Mary Lou Carey <<a href="mailto:marylou@backuptelecom.com" target="_blank">marylou@backuptelecom.com</a>><br>
<b>Cc: </b>VoiceOps <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>><br>
<b>Subject: </b>Re: [VoiceOps] AT&T Wireless / FirstNet routing issue contact<u></u><u></u></span></p>
</div>
<div style="border:1pt solid rgb(204,204,204);padding:8pt;margin-bottom:15pt">
<p>[External Email]: This message is from a sender outside our organization. Exercise caution with links and attachments. Do not share sensitive information unless you verify the sender's identity and trust the content.<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11pt">Well that was phone number was a maze. I managed to get an email address out of somebody
<a href="mailto:dl-ss7trctier2@att.com" target="_blank">dl-ss7trctier2_at_att.com</a>, but nobody could open a ticket.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Going to give the email address a try.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Collin R</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<div id="m_-610225314277977782mail-editor-reference-message-container">
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal" style="margin-bottom:12pt"><b><span style="color:black">From:
</span></b><span style="color:black">Mary Lou Carey <<a href="mailto:marylou@backuptelecom.com" target="_blank">marylou@backuptelecom.com</a>><br>
<b>Date: </b>Monday, February 19, 2024 at 6:10</span><span style="font-family:Arial,sans-serif;color:black"> </span><span style="color:black">PM<br>
<b>To: </b>Collin Rose <<a href="mailto:collin.rose@daystarrfiber.net" target="_blank">collin.rose@daystarrfiber.net</a>><br>
<b>Cc: </b>VoiceOps <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>><br>
<b>Subject: </b>Re: [VoiceOps] AT&T Wireless / FirstNet routing issue contact</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt">[External Email]: This message is from a sender outside our organization. Exercise caution with links and attachments. Do not share sensitive information unless you verify the sender's identity and trust the
content.<br>
<br>
AT&T Wireless NOC<br>
800-638-2822<br>
<br>
If you've put in a ticket and they still haven't fixed it, I also have<br>
escalation contacts.<br>
<br>
MARY LOU CAREY<br>
BackUP Telecom Consulting<br>
Office: 615-791-9969<br>
Cell: 615-796-1111<br>
<br>
On 2024-02-18 05:48 PM, Collin Rose via VoiceOps wrote:<br>
> We appear to have an issue with AT&T Wireless failing to complete<br>
> calls to us and anything behind the local Frontier tandem (which they<br>
> apparently were routing our calls to). We are seeing call failures on<br>
> testing from an AT&T wireless cellular phone to both our numbers, and<br>
> the Frontier exchanges served off the tandem. Any one got any contacts<br>
> to open a ticket? Our end-user ticket, and our FirstNet ticket through<br>
> the local 911 center have both been unsuccessful, and we are going on<br>
> 72 hours of inability to receive calls from AT&T Wireless customers.<br>
><br>
> Thanks,<br>
><br>
> Collin R<br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> <a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</div></blockquote></div>