In my experience, they will investigate and let you know what's going on. For 
us, usually, it's a problem with a Verizon Wireless circuit causing Verizon 
Wireless reachability issues. 




----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 



Midwest Internet Exchange 
http://www.midwest-ix.com 



----- Original Message -----

From: "Collin Rose" <collin.r...@daystarrfiber.net> 
To: "Mike Hammett" <voice...@ics-il.net> 
Cc: "VoiceOps" <voiceops@voiceops.org> 
Sent: Sunday, February 18, 2024 10:04:57 PM 
Subject: Re: [VoiceOps] AT&T Wireless / FirstNet routing issue contact 



Yes. Trying this, don’t have high hopes. Opened against my local trunking 
circuit ID. 

Collin R 




From: Mike Hammett <voice...@ics-il.net> 
Date: Sunday, February 18, 2024 at 7:30 PM 
To: Collin Rose <collin.r...@daystarrfiber.net> 
Cc: VoiceOps <voiceops@voiceops.org> 
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. 


Are you a Frontier customer and have access to VFO? 



----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 



Midwest Internet Exchange 
http://www.midwest-ix.com 







From: "Collin Rose via VoiceOps" <voiceops@voiceops.org> 
To: "VoiceOps" <voiceops@voiceops.org> 
Sent: Sunday, February 18, 2024 5:48:13 PM 
Subject: [VoiceOps] AT&T Wireless / FirstNet routing issue contact 

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 
VoiceOps@voiceops.org 
https://puck.nether.net/mailman/listinfo/voiceops 

_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Reply via email to