Welcome to the wide world of random call blocking. We've been seeing the same issue for some time now due to the magic of "analytics". Emergency notification calls (school closures, weather events, shootings) are especially great when getting blocked due to random systems deciding that they don't like the call patterns or the ANI.
You are possibly running into where some of your ANIs have been flagged for no reason at all and that your cert or signed level isn't even being looked at before getting rejected. Of course when your customer tries making the same call on their cell phone (or a different carrier) it works just fine so you're left looking like you don't know what you are doing. Best you can do is open tickets and complain. You can also look at trying to fill out the FCR but I haven't seen that help too much. On Wed, Jan 11, 2023 at 7:08 AM Dovid Bender via VoiceOps < voiceops@voiceops.org> wrote: > Hi All, > > We are a small ITSP and every so often we have issues with calls that go > to T-Mobile. We sign all our calls with our cert. Lately we have been > getting 404's, 608's etc through 382, Telnyx and SIPRoutes. Bandwidth has > been worse than the rest as they don't outright reject calls but they send > a 100 trying and leave us hanging for 30 seconds. Peerless and one other > carrier are completing the calls. Anyone know what makes T-Moble special > that so many carriers will just 404 calls to their network? > > TIA. > > Dovid > > _______________________________________________ > VoiceOps mailing list > VoiceOps@voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops >
_______________________________________________ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops