<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000'>Ah, okay. That does sound interesting, though perhaps more difficult due to needing every single DID versus NPA-NXX-X blocks and LRNs.<br><br><div><span name="x"></span><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br>http://www.ics-il.com<br><br><br><br>Midwest Internet Exchange<br>http://www.midwest-ix.com<br><br><span name="x"></span><br></div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Jared Geiger" <jared@compuwizz.net><br><b>To: </b>"VoiceOps" <voiceops@voiceops.org><br><b>Sent: </b>Friday, March 20, 2020 5:17:16 PM<br><b>Subject: </b>Re: [VoiceOps] Investigating random call completion issues nationwide<br><br><div dir="ltr">Those services look like they are for CLECs that own number ranges. The Intelepeer 10 digit peering service didn't have that requirement. At the time, I gave them a list of all the DIDs that we bought from various vendors and if a call to those numbers transited Intelepeer, they delivered it directly to us at no cost. So the equivalent to an Internet peering exchange but for phone calls. When Peerless bought Intelepeer's wholesale side, they shut it down because they were afraid of running into compensation issues or billing complaints.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 20, 2020 at 2:56 PM Mike Hammett <<a href="mailto:voiceops@ics-il.net" target="_blank">voiceops@ics-il.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">Are you talking about something like Peerless's and Inteliquent's Local Transit services? <br><br><div><span></span><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br><a href="http://www.ics-il.com" target="_blank">http://www.ics-il.com</a><br><br><br><br>Midwest Internet Exchange<br><a href="http://www.midwest-ix.com" target="_blank">http://www.midwest-ix.com</a><br><br><span></span><br></div><br><hr id="gmail-m_8037327731341979924zwchr"><div style="color:rgb(0,0,0);font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>From: </b>"Jared Geiger" <<a href="mailto:jared@compuwizz.net" target="_blank">jared@compuwizz.net</a>><br><b>To: </b>"VoiceOps" <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>><br><b>Sent: </b>Friday, March 20, 2020 2:35:47 PM<br><b>Subject: </b>Re: [VoiceOps] Investigating random call completion issues nationwide<br><br><div dir="ltr">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.<div><br></div><div>Intelepeer had one before Peerless bought the wholesale network.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 20, 2020 at 6:59 AM Mike Hammett <<a href="mailto:voiceops@ics-il.net" target="_blank">voiceops@ics-il.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)">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.<br><br><div><span></span><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br><a href="http://www.ics-il.com" target="_blank">http://www.ics-il.com</a><br><br><br><br>Midwest Internet Exchange<br><a href="http://www.midwest-ix.com" target="_blank">http://www.midwest-ix.com</a><br><br><span></span><br></div><br><hr id="gmail-m_8037327731341979924gmail-m_-3247554162847669645zwchr"><div style="color:rgb(0,0,0);font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>From: </b>"Darren Schreiber" <<a href="mailto:darren@2600hz.com" target="_blank">darren@2600hz.com</a>><br><b>To: </b><a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a><br><b>Sent: </b>Thursday, March 19, 2020 6:29:21 PM<br><b>Subject: </b>[VoiceOps] Investigating random call completion issues nationwide<br><br>
<div>
<p class="MsoNormal"><span style="font-size:11pt">Hi folks,</span></p>
<p class="MsoNormal"><span style="font-size:11pt"> 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.</span></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt"> 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.</span></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt"> 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?</span></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt">- Darren</span></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span></p>
</div>
<br>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br></div><br></div></div>_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div>
<br>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br></div><br></div></div>_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div>
<br>_______________________________________________<br>VoiceOps mailing list<br>VoiceOps@voiceops.org<br>https://puck.nether.net/mailman/listinfo/voiceops<br></div><br></div></body></html>