[VoiceOps] Who do we call - 3rd plus party carrier issues affecting local customers

Wed Aug 21 08:50:46 EDT 2019

Always perform a LNP query on the originating number to determine the originating company and start with them, realizing they may not provide the LD, doesn’t matter they have to work with you.

You say CenturyLink was removed from route by Inteliquent and it cleared T-Mobile so this wouldn’t seem to be a facilities issue but have you examined the TCIC’s the calls come in on from ATT, are they confined to a range?
There are a number of ways to get in touch with ATT but they will say they are passing what they receive.  The best be is to start with the originating company.

At this point who would you file a FCC complaint against?

Mark Timm
Switch Engineer
Aureon Technology
7760 Office Plaza Drive South
West Des Moines
, IA

50266
Mark.Timm at aureon.com
515-830-0478
www.aureon.com
This message contains confidential information and is intended only for the intended recipients. If you are not an intended recipient you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Brandon Svec
Sent: Tuesday, August 20, 2019 10:58 PM
To: Jamie Montgomery <Jamie.Montgomery at comporium.com>
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] Who do we call - 3rd plus party carrier issues affecting local customers

[External Email] This message was sent from outside the company with a URL. Please do not click links unless you recognize the source of this email and know the content is safe.

It sounds like you have done more than half the troubleshooting already.

I would continue to work the AT&T escalation angle as it sounds they should be the ones in a position to identify the trouble route and resolve it.

Maybe through out the idea of a potential FCC complaint by someone in your organization it could help move things along.

Good luck

On Tue, Aug 20, 2019 at 7:45 PM Jamie Montgomery <Jamie.Montgomery at comporium.com<mailto:Jamie.Montgomery at comporium.com>> wrote:
Greetings..

Looking for the proper way to identify a third party carrier..

We have had a monthlong ongoing issue with external calls into our switch with terrible quality. It’s random, but it’s calls to ported numbers into one of our CLEC areas. When an affected call comes in, it is reported as static or delay. We have obtained an audio capture of a couple of these calls from the ingress point of our TDM network, and the audio is severely delayed and choppy as if it was delayed within an IP network. We’re assuming the call has been routed through an IP low-cost carrier somewhere. (Working with T-Mobile below, we found that their switches would route calls that originates and terminates locally in South Carolina through Washington state carriers.)

All of the calls with an issue come into us from a legacy ATT tandem, but not all of the calls from the ATT tandem are affected. We’ve been trying to get in touch with ATT for a month, and have recently spoken to some people with no resolution. We continue to call them daily. We worked with T-Mobile on issues with their wireless customers calling our CLEC customers experiencing this problem. The guys at T-Mobile were excellent to work with. (They reached out to their 3rd party carrier Inteloquent who had rerouted calls away from CenturyLink, which resolved calls from T-Mobile devices.) We’re getting dozens of trouble calls a day from several of our CLEC customers on calls originating from many other sources (Verizon, local ILEC  landlines, etc.). We’ve explained to our customer that the trouble is not ours, that we’re doing our best to track down the problem carrier, but we’re been notified by our customers that we’re going to lose them, regardless.

Our last idea is to file a complaint with the FCC, but that’s leaving issues unresolved. My questions to the community are:

  *   What’s the most effective way to zero in on the problem carrier  to troubleshoot the issue?
  *   What legal means do we have to empower somebody to support us in finding the issue?
  *   What would you do if your hands were tied like ours seem to be?
  *   (What other questions should I be asking the community that come to mind?)

My background is switching and some at work experience of the SS7 network. I’m of the opinion that I’m not the most qualified in our organization to engage the FCC or twist ATT’s arm to work with us.. but no one else beside the on-point technician is making any effort. Internal responsibilities aside: How do we make the extra effort to keep our customers?

I appreciate the time you took from your day reading this.

Jamie Montgomery | Comporium

Network Facilities Engineering | Voice Network Engineering Associate

www.comporium.com<http://www.comporium.com>

jamie.montgomery at comporium.com<mailto:jamie.montgomery at comporium.com>

The information contained in this e-mail message and any attachments thereto are confidential, privileged, or otherwise protected from disclosure, and are intended for the use of the individual or entity named above. Dissemination, distribution or copying of this message and any attachments by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this communication in error, please immediately notify the sender by telephone or e-mail and destroy the original message, attachments, and all copies.

_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
--
Brandon Svec
15106862204 voice | fax | sms

teamonesolutions.com<http://teamonesolutions.com>
14729 Catalina St. San Leandro, CA 94577

.ılı.ılı. Cisco Meraki CMNA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190821/0f3ebd9d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image739129.jpg
Type: image/jpeg
Size: 21564 bytes
Desc: image739129.jpg
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190821/0f3ebd9d/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image955925.png
Type: image/png
Size: 573 bytes
Desc: image955925.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190821/0f3ebd9d/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image522869.png
Type: image/png
Size: 472 bytes
Desc: image522869.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190821/0f3ebd9d/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image416373.png
Type: image/png
Size: 541 bytes
Desc: image416373.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190821/0f3ebd9d/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image271845.png
Type: image/png
Size: 732 bytes
Desc: image271845.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190821/0f3ebd9d/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image807412.png
Type: image/png
Size: 641 bytes
Desc: image807412.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190821/0f3ebd9d/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image414846.png
Type: image/png
Size: 642 bytes
Desc: image414846.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190821/0f3ebd9d/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image296850.png
Type: image/png
Size: 675 bytes
Desc: image296850.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190821/0f3ebd9d/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image427844.png
Type: image/png
Size: 611 bytes
Desc: image427844.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190821/0f3ebd9d/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image271671.png
Type: image/png
Size: 886 bytes
Desc: image271671.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20190821/0f3ebd9d/attachment-0017.png>