Message -
From: "Jared Geiger"
To: "VoiceOps"
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
;
> --
> *From: *"Jared Geiger"
> *To: *"VoiceOps"
> *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 s
eiger"
To: "VoiceOps"
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
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
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
employees daily, in the
> morning, so I suspect that’s the issue.
>
>
>
> *From: *Izzy Goldstein - TeleGo
> *Date: *Thursday, March 19, 2020 at 9:12 PM
> *To: *Darren Schreiber
> *Cc: *"voiceops@voiceops.org"
> *Subject: *Re: [VoiceOps] Investigating rand
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
Date: Thursday, March 19, 2020 at 9:12 PM
To: Darren Schreiber
Cc: "voiceops@voiceops.org"
Subject: Re: [VoiceOps] Investigating random call
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
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.
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:
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
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
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
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
> 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
15 matches
Mail list logo