[VoiceOps] Investigating random call completion issues nationwide

[Jared Geiger]

Are there any 10 digit peering exchanges still functioning for things other
than TF calls? Where we would build a trunk and send a list of numbers on
net. If the call is 503d, just send it out normal routing.

Intelepeer had one before Peerless bought the wholesale network.

On Fri, Mar 20, 2020 at 6:59 AM Mike Hammett <voiceops at ics-il.net> wrote:

> This is one place the IP world (while far from perfect) is vastly superior
> to the PSTN. Any given IP address can have many paths to success and they
> can be changed on a whim. You don't have to wait forever for LERG updates.
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
>
>
> ------------------------------
> *From: *"Darren Schreiber" <darren at 2600hz.com>
> *To: *voiceops at voiceops.org
> *Sent: *Thursday, March 19, 2020 6:29:21 PM
> *Subject: *[VoiceOps] Investigating random call completion issues
> nationwide
>
> Hi folks,
>
>                 We’ve been getting occasional, very infrequent, reports of
> people hitting busy signals or intercept messages when calling numbers
> routed to us. At first we thought the issue was between us and Peerless but
> we now have reports with bandwidth and Inteliquent. So, then of course
> naturally we thought the issue was in our systems. But again, we’ve come up
> empty. We also thought it may be trunk or port limitations upstream. Have
> checked those. No dice.
>
>
>
>                 The issue seems to always be the same. Customer from cell
> phone or landline dials a number, reaches a busy signal or intercept
> message. All reports are from Verizon or AT&T callers. We check our logs,
> don’t see any attempt to even reach our system (we log freakin everything).
> So we reach out to the upstream provider, and they too claim it never
> reached their tandem/network.
>
>
>
>                 I know everyone on earth is currently WFH so perhaps that
> warrants just shutting up & dealing with it but I’ve been surprised not to
> see any chatter on this list or elsewhere in this regard. Is anyone else
> having indications of capacity issues (and are y’all just not talking about
> it) or is it just us and we should keep looking?
>
>
>
> - Darren
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> 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/20200320/6e0e9c9f/attachment-0001.htm>