Funny thing about that, they did get our stuff restored after 5pm yesterday (emergent reinstall of the trunkgroup to the Frontier tandem they had just disconnected), but we couldn’t call any of our customers to tell them this morning because they were all OOS!
Collin R From: Justin B Newman <[email protected]> Date: Thursday, February 22, 2024 at 12:46 PM To: Collin Rose <[email protected]> Cc: VoiceOps <[email protected]> Subject: Re: [VoiceOps] AT&T Wireless / FirstNet routing issue contact [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. Collin, 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! -jbn On Tue, Feb 20, 2024 at 1:02 PM Collin Rose via VoiceOps <[email protected]<mailto:[email protected]>> wrote: 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. 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). 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. Appreciate any help anyone can provide! Collin R From: VoiceOps <[email protected]<mailto:[email protected]>> on behalf of Collin Rose via VoiceOps <[email protected]<mailto:[email protected]>> Date: Tuesday, February 20, 2024 at 11:14 AM To: Mary Lou Carey <[email protected]<mailto:[email protected]>> Cc: VoiceOps <[email protected]<mailto:[email protected]>> Subject: Re: [VoiceOps] AT&T Wireless / FirstNet routing issue contact [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. Well that was phone number was a maze. I managed to get an email address out of somebody dl-ss7trctier2_at_att.com<mailto:[email protected]>, but nobody could open a ticket. Going to give the email address a try. Collin R From: Mary Lou Carey <[email protected]<mailto:[email protected]>> Date: Monday, February 19, 2024 at 6:10 PM To: Collin Rose <[email protected]<mailto:[email protected]>> Cc: VoiceOps <[email protected]<mailto:[email protected]>> Subject: Re: [VoiceOps] AT&T Wireless / FirstNet routing issue contact [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. AT&T Wireless NOC 800-638-2822 If you've put in a ticket and they still haven't fixed it, I also have escalation contacts. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796-1111 On 2024-02-18 05:48 PM, Collin Rose via VoiceOps wrote: > We appear to have an issue with AT&T Wireless failing to complete > calls to us and anything behind the local Frontier tandem (which they > apparently were routing our calls to). We are seeing call failures on > testing from an AT&T wireless cellular phone to both our numbers, and > the Frontier exchanges served off the tandem. Any one got any contacts > to open a ticket? Our end-user ticket, and our FirstNet ticket through > the local 911 center have both been unsuccessful, and we are going on > 72 hours of inability to receive calls from AT&T Wireless customers. > > Thanks, > > Collin R > _______________________________________________ > VoiceOps mailing list > [email protected]<mailto:[email protected]> > https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
