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
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 did see this in the UK yesterday from mobiles calling various numbers, including our own VoIP numbers. First dial always failed. Thought the same as you but was various landlines and mobiles. I think it was the mobile network (O2). Maybe a symptom of a congested core mobile network? Thanks. -- Kind Regards, Gavin Henry.
Yeah we are debating congestion too but can't seem to pin it down. What troubles me is that even our upstream carriers (both bandwidth and Peerless) can't even find the call examples we've received (which are from different clients) in their switches at all. So that rules our systems out to some degree. So I either have two clients sending me invalid information, orrrr.... yeah out of ideas a bit. Anyway, thanks for the responses already. ?On 3/19/20, 4:33 PM, "Gavin Henry" <ghenry at suretec.co.uk> wrote: > 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 did see this in the UK yesterday from mobiles calling various numbers, including our own VoIP numbers. First dial always failed. Thought the same as you but was various landlines and mobiles. I think it was the mobile network (O2). Maybe a symptom of a congested core mobile network? Thanks. -- Kind Regards, Gavin Henry.
When we pulled up our Homer traces we only saw the successful attempt, nothing else, nor our carriers. Same story. I reckon mobile core.
We are seeing similar things in Australia over the last few days. I can generally get calls out of our network (being that we are so well connected to almost every other sizeable carrier in-country), however, we are definitely seeing some inbound traffic "go missing" as you are talking about. The calls simply never hit our network. I know of one carrier in country with fairly massive confirmed capacity issues. Another has unofficially mentioned that if current traffic volumes continue to increase they are going to hit issues. I just think everyone is seeing unprecedented traffic growth. I don't think it's just working from home. - I think its people calling to check up on loved ones. - People calling co-workers rather than IM while working from home. (we are seeing an increase in this in our own staff... when in isolation people want to talk not IM, so they get some human contact) - Then I know for sure of "Covid 19 response lines" setup by governments that are now carrying huge amount of calls On that note, if I can help anyone in Australia or NZ right now.. contact me. ( yes I'm with a smaller Tier 1 in Aus ) More than happy to help where we can. but I hope you all get through this as best you can. On Fri, 20 Mar 2020 at 09:40, Gavin Henry <ghenry at suretec.co.uk> wrote:
When we pulled up our Homer traces we only saw the successful attempt, nothing else, nor our carriers. Same story. I reckon mobile core. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- Sincerely Jay
We've had ILEC confirmed instances of congestion in Canada. Mostly to toll free numbers. And sometimes it's between ILEC's wireless and ILEC's toll free network, i.e. same company. On Thu., Mar. 19, 2020, 7:37 p.m. Darren Schreiber, <darren at 2600hz.com> wrote:
Yeah we are debating congestion too but can't seem to pin it down. What troubles me is that even our upstream carriers (both bandwidth and Peerless) can't even find the call examples we've received (which are from different clients) in their switches at all. So that rules our systems out to some degree.
So I either have two clients sending me invalid information, orrrr.... yeah out of ideas a bit.
Anyway, thanks for the responses already.
?On 3/19/20, 4:33 PM, "Gavin Henry" <ghenry at suretec.co.uk> wrote:
> 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 did see this in the UK yesterday from mobiles calling various numbers, including our own VoIP numbers. First dial always failed. Thought the same as you but was various landlines and mobiles. I think it was the mobile network (O2). Maybe a symptom of a congested core mobile network?
Thanks.
-- Kind Regards, Gavin Henry.
_______________________________________________ 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.
We've been seeing issues on outbound related to (supposedly) tandem overload in some areas through Verizon Business at a minimum, it would be unsuprising to see that affect incoming to other carriers, since by definition, it's outgoing calls from us to other carriers that are affected. Verizon also mentioned something about a software licensing issue on something of their network.
On Mar 19, 2020, at 7:29 PM, Darren Schreiber <darren at 2600hz.com> wrote:
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 <mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops <https://puck.nether.net/mailman/listinfo/voiceops>
If the calls originate from AT&T and Verizon, their SS7 network should be able to see where the call failed. I'd have them put a trouble ticket in with their carrier. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796-1111 On 2020-03-19 06:29 PM, Darren Schreiber wrote:
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
i experienced the same issues Peerless says: We?re sorry for the calling issues you?re experiencing today. As you may know, these are extraordinary times and we are currently seeing network congestion industry wide ? the events of the past week have had a direct impact on all telecommunication carriers. Due to the sheer volume of individuals and businesses that are now working remotely, blocking or congestion outside our network is impacting call completion. peerless is relentlessly pursuing all options with all of our partners, and working to ensure that they?re aware of the call completion issues. While peerless can and will address some of these issues directly, our troubleshooting indicates that many congestion-related issues are occurring within networks of our carrier customers or other intermediaries which we cannot control. Nonetheless, we are working tirelessly to resolve capacity issues wherever they exist. Thanks for your understanding. On Thu, Mar 19, 2020 at 7:29 PM Darren Schreiber <darren at 2600hz.com> wrote:
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
-- Izzy Goldstein Chief Technology Officer Main: (212) 477-1000 x 2085 <(212)%20477-1000> Direct: (929) 477-2085 Website: www.telego.com <http://www.telego.net/> <http://www.telego.com/> Confidentiality Notice: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify us immediately by email reply and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of TeleGo (T). Employees of TeleGo are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to TeleGo policy and outside the scope of the employment of the individual concerned. TeleGo will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
They have that up as an auto-responder (they sent it to me twice heh). Then they wrote back to try and find the calls, but did not find them hitting their network. That?s why I thought it was their issue at first, but then we had the same report on a bandwidth.com number. Then a few more reports. And you know for each report we get there?s 10 people that aren?t saying anything and just redial. Well, I guess it depends on the customer. Anyway, we?ll keep an eye on it. We also hit record calling this week so that?s another data point that it?s just high traffic. Many people seem to be doing remote ?check-in? meetings with all their employees daily, in the morning, so I suspect that?s the issue. From: Izzy Goldstein - TeleGo <igoldstein at telego.net> Date: Thursday, March 19, 2020 at 9:12 PM To: Darren Schreiber <darren at 2600hz.com> Cc: "voiceops at voiceops.org" <voiceops at voiceops.org> Subject: Re: [VoiceOps] Investigating random call completion issues nationwide i experienced the same issues Peerless says: We?re sorry for the calling issues you?re experiencing today. As you may know, these are extraordinary times and we are currently seeing network congestion industry wide ? the events of the past week have had a direct impact on all telecommunication carriers. Due to the sheer volume of individuals and businesses that are now working remotely, blocking or congestion outside our network is impacting call completion. peerless is relentlessly pursuing all options with all of our partners, and working to ensure that they?re aware of the call completion issues. While peerless can and will address some of these issues directly, our troubleshooting indicates that many congestion-related issues are occurring within networks of our carrier customers or other intermediaries which we cannot control. Nonetheless, we are working tirelessly to resolve capacity issues wherever they exist. Thanks for your understanding. On Thu, Mar 19, 2020 at 7:29 PM Darren Schreiber <darren at 2600hz.com<mailto:darren at 2600hz.com>> wrote: 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<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops -- Izzy Goldstein Chief Technology Officer Main: (212) 477-1000 x 2085<tel:(212)%20477-1000> Direct: (929) 477-2085<tel:(929)%20477-2085> Website: www.telego.com<http://www.telego.net/> [https://lh4.googleusercontent.com/Ze7NkT2QtotXfVWbpWXrpSMRIcAdqb0Ci0_RZsAjQzmRrd-_v02-O86QlqwZnGUE8SlBECXBvJUPXSH7ZRyDvDVeaXQFSS5SiA4gan112DN-0s2D3prRdt2UeUprZQEo1YmUFfZ7]<http://www.telego.com/> Confidentiality Notice: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify us immediately by email reply and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of TeleGo (T). Employees of TeleGo are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to TeleGo policy and outside the scope of the employment of the individual concerned. TeleGo will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. TeleGo Hosted PBX<https://youtu.be/DaT8YAZ4V0w>
ive also had issues with DIDWW DID's in israel, being called from israel cell phones didnt connect. seems to be industry standard On Fri, Mar 20, 2020 at 12:15 AM Darren Schreiber <darren at 2600hz.com> wrote:
They have that up as an auto-responder (they sent it to me twice heh). Then they wrote back to try and find the calls, but did not find them hitting their network. That?s why I thought it was their issue at first, but then we had the same report on a bandwidth.com number. Then a few more reports. And you know for each report we get there?s 10 people that aren?t saying anything and just redial. Well, I guess it depends on the customer.
Anyway, we?ll keep an eye on it. We also hit record calling this week so that?s another data point that it?s just high traffic. Many people seem to be doing remote ?check-in? meetings with all their employees daily, in the morning, so I suspect that?s the issue.
*From: *Izzy Goldstein - TeleGo <igoldstein at telego.net> *Date: *Thursday, March 19, 2020 at 9:12 PM *To: *Darren Schreiber <darren at 2600hz.com> *Cc: *"voiceops at voiceops.org" <voiceops at voiceops.org> *Subject: *Re: [VoiceOps] Investigating random call completion issues nationwide
i experienced the same issues
Peerless says:
We?re sorry for the calling issues you?re experiencing today. As you may know, these are extraordinary times and we are currently seeing network congestion industry wide ? the events of the past week have had a direct impact on all telecommunication carriers. Due to the sheer volume of individuals and businesses that are now working remotely, blocking or congestion outside our network is impacting call completion. peerless is relentlessly pursuing all options with all of our partners, and working to ensure that they?re aware of the call completion issues. While peerless can and will address some of these issues directly, our troubleshooting indicates that many congestion-related issues are occurring within networks of our carrier customers or other intermediaries which we cannot control. Nonetheless, we are working tirelessly to resolve capacity issues wherever they exist. Thanks for your understanding.
On Thu, Mar 19, 2020 at 7:29 PM Darren Schreiber <darren at 2600hz.com> wrote:
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
--
*Izzy Goldstein *
*Chief Technology Officer *
Main: *(212) 477-1000 x 2085 <(212)%20477-1000>*
Direct: *(929) 477-2085 <(929)%20477-2085>*
Website: www.telego.com <http://www.telego.net/>
*Confidentiality Notice: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify us immediately by email reply and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of TeleGo (T). Employees of TeleGo are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to TeleGo policy and outside the scope of the employment of the individual concerned. TeleGo will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising.*
TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
-- Izzy Goldstein Chief Technology Officer Main: (212) 477-1000 x 2085 <(212)%20477-1000> Direct: (929) 477-2085 Website: www.telego.com <http://www.telego.net/> <http://www.telego.com/> Confidentiality Notice: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify us immediately by email reply and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of TeleGo (T). Employees of TeleGo are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to TeleGo policy and outside the scope of the employment of the individual concerned. TeleGo will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. TeleGo Hosted PBX <https://youtu.be/DaT8YAZ4V0w>
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 ----- Original Message ----- 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
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
Are you talking about something like Peerless's and Inteliquent's Local Transit services? ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ----- Original Message ----- From: "Jared Geiger" <jared at compuwizz.net> To: "VoiceOps" <voiceops at voiceops.org> Sent: Friday, March 20, 2020 2:35:47 PM Subject: Re: [VoiceOps] Investigating random call completion issues nationwide 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 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
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. On Fri, Mar 20, 2020 at 2:56 PM Mike Hammett <voiceops at ics-il.net> wrote:
Are you talking about something like Peerless's and Inteliquent's Local Transit services?
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
Midwest Internet Exchange http://www.midwest-ix.com
------------------------------ *From: *"Jared Geiger" <jared at compuwizz.net> *To: *"VoiceOps" <voiceops at voiceops.org> *Sent: *Friday, March 20, 2020 2:35:47 PM *Subject: *Re: [VoiceOps] Investigating random call completion issues nationwide
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
_______________________________________________ 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
Ah, okay. That does sound interesting, though perhaps more difficult due to needing every single DID versus NPA-NXX-X blocks and LRNs. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ----- Original Message ----- From: "Jared Geiger" <jared at compuwizz.net> To: "VoiceOps" <voiceops at voiceops.org> Sent: Friday, March 20, 2020 5:17:16 PM Subject: Re: [VoiceOps] Investigating random call completion issues nationwide 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. On Fri, Mar 20, 2020 at 2:56 PM Mike Hammett < voiceops at ics-il.net > wrote: Are you talking about something like Peerless's and Inteliquent's Local Transit services? ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com From: "Jared Geiger" < jared at compuwizz.net > To: "VoiceOps" < voiceops at voiceops.org > Sent: Friday, March 20, 2020 2:35:47 PM Subject: Re: [VoiceOps] Investigating random call completion issues nationwide 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: <blockquote> 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 _______________________________________________ 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 </blockquote> _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (9)
-
darren＠2600hz.com -
ghenry＠suretec.co.uk -
igoldstein＠telego.net -
ivan.kovacevic＠startelecom.ca -
jared＠compuwizz.net -
jaybinks＠gmail.com -
marylou＠backuptelecom.com -
paul＠timmins.net -
voiceops＠ics-il.net