Apart from the "I ought to fix this, it just ain't right" instinct... The practical solution is for the caller to open a ticket with their provider. You'll go crazy trying to get to the big-carrier engineering team and to someone who knows how to investigate and solve the problem... unless they are lurking on this list.... I've pulled much hair trying to right telecom wrongs... and the type you are running into, is better delegated to the user/caller. (assuming you are 100% certain it isn't on your end) [image: Star Telecom - Cloud Communications and Customer Experience Solutions] <https://www.startelecom.ca/> *Ivan Kovacevic* *Co-Founder and VP Client Services* On Wed, Oct 27, 2021 at 3:12 PM Mike Hammett <voiceops at ics-il.net> wrote:
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
-- NOTE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by replying to this email, and destroy all copies of the original message.