[VoiceOps] Calls Not Reaching Us

[Josh Tressler]

I've been out of this game "day-to-day" for a year or so now, but before I left, we were finally able to utilize the "rural call completion" contact at the originating carrier to start these inquiries. I spent many many hours working with carriers and the originating customer to try and start a ticket on their end. After the posting of those specific contacts, it became slightly easier to initiate an investigation from the remote end, and the provide SAS (metaswitch shop) information (or lack of) to the carrier to work through the routing issues. 9 times out of 10, adjusting the LCR in and intermediate carrier magically fixed the issue. 

Just my $0.02... 

-- 
Josh Tressler 
Public Safety Network Engineer 
Decatur County Public Safety 
jtressler at decaturcounty.in.gov 


From: "Mike Hammett" <voiceops at ics-il.net> 
To: "VoiceOps" <voiceops at voiceops.org> 
Sent: Wednesday, October 27, 2021 3:07:00 PM 
Subject: [VoiceOps] Calls Not Reaching Us 

I have a customer saying that they are getting reports from their customers that they're getting "number is no longer in service" errors when calling them. 
I checked Metaswitch SAS for a number that experienced this issue and we don't see any inbound attempts from that number. The call would have come in via a traditional TDM connection to a tandem. 

I reached out to the Primary contacts in NPAC for the originating caller (Comcast). They told me to bugger off and to have the end user call support. Did I make the wrong move? 



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



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




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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20211027/09e509d0/attachment.htm>