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
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
