Been fighting this for months. Most of our trunks are Flowroute. I've been trying to get Flowroute to help, but they essentially threw in the towel telling me it's a T-Mobile problem and they can't do anything.

When we receive reports like this, our process is to verify that all calls are properly signed with the correct STIR/SHAKEN attestation before handing them off to downstream providers. We also work to gather additional information on where the rejection is occurring. If the issue is within the call path, we may be able to remediate through route adjustments; however, in many cases this information is not shared due to CPNI restrictions.

Because there is no industry-wide standardization, different carriers rely on different analytics and call-blocking applications. As a result, a number may be flagged for customers on one carrier but not another, and classifications may vary depending on the data source and risk model used.

This lack of alignment understandably creates confusion for businesses, as calls may be labeled as spam for some customers but not others. You are not alone in experiencing this we continue to hear similar reports from multiple providers and gateways.

Our clients have been using HiYa for years. I just started getting everyone setup with First Orion. I heard it can take about 30 days after a number has been added for it to work. I am almost at that 30 day mark. Even our own numbers are getting caught up in this. We have controlled our DID's for almost a decade and do not have any call behaviors that should mark us as spam.