Re: [VoiceOps] Investigating random call completion issues nationwide

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 wrote: > They have that up as an auto-responder (they sent it to me twice heh). > Then they wrote back to try and

Re: [VoiceOps] Investigating random call completion issues nationwide

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

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

Re: [VoiceOps] E911 - Working from home

I guess one phone dispatched to a home working location does not qualify as “Multi-Line Telephone System” MLTS i.e. PBX with SIP trunk or ISDN PRI etc. However, the RAY BAUM’S Act , which kicks in next year 2021, may sharpen FCC’s oversight of location, accompanying a 911 call. The Act

Re: [VoiceOps] Investigating random call completion issues nationwide

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.

Re: [VoiceOps] E911 - Working from home

Because when people have an emergency their brain cells don't work as well. They see a phone and expect it to work regardless. That's why the FCC mandated that if you can make an originating call.you have to provide 911 and be able to update the location accurately! MARY LOU CAREY BackUP

Re: [VoiceOps] Investigating random call completion issues nationwide

If the calls originate from AT 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- On 2020-03-19 06:29 PM, Darren Schreiber wrote:

Re: [VoiceOps] Investigating random call completion issues nationwide

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

Re: [VoiceOps] Investigating random call completion issues nationwide

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, wrote: > Yeah we are debating congestion too but can't seem to

Re: [VoiceOps] Investigating random call completion issues nationwide

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@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Investigating random call completion issues nationwide

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

Re: [VoiceOps] Investigating random call completion issues nationwide

> 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 callers. We check our logs, don’t see > any attempt to even reach our system (we log freakin

[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

Re: [VoiceOps] E911 - Working from home

Just sayin but they have phones ... why do they need your 911 routing -- J. Hellenthal The fact that there's a highway to Hell but only a stairway to Heaven says a lot about anticipated traffic volume. > On Mar 19, 2020, at 13:56, Izzy Goldstein - TeleGo > wrote: > >  > how messy is

Re: [VoiceOps] E911 - Working from home

Did they bring their phones home with them? If so, you'll need to update the ALI database with their new addresses. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796- On 2020-03-19 01:53 PM, Izzy Goldstein - TeleGo wrote: how messy is this needing to change many

[VoiceOps] E911 ruling

not a tech topic but a tax one. https://www.jdsupra.com/legalnews/oregon-tax-court-in-ooma-inc-v-dor-89325/ Oregon Tax Court rules VoIP Providers have to pay E911 taxes despite no physical presence Thank you. Regards, Peter Radizeski @ RAD-INFO INC (813) 963-5884

[VoiceOps] E911 - Working from home

how messy is this needing to change many E911 locations for Remote Employees -- Izzy Goldstein Chief Technology Officer Main: (212) 477-1000 x 2085 <(212)%20477-1000> Direct: (929) 477-2085 Website: www.telego.com Confidentiality Notice:

[VoiceOps] Testing DTMF to known conference numbers

At the end of the day yesterday I decided to test our product to make sure that our customers could reach conferencing services and not get FAS, excessive PDD or DTMF failures especially to international destinations. I went through old calendar invites that had a link to extra numbers for