Robocall prevention

Robocalls are overwhelming the telephone network. New laws and regulations, and increasing market demand, require voice service providers to respond.

  • Regulators want you to prevent illegal robocalls from originating on your network. In the U.S., the TRACED Act, and the FCC regulation that come from that, requires you to use either STIR/SHAKEN call authentication or a robocall mitigation program to prevent robocalls from originating on your network, even if your network is unlikely to have any robocallers.
  • Enterprise customers want you to block or divert inbound robocalls that can tie up their phones and cripple their business.
  • Consumers want you to block or divert annoying scam robocalls.

For these reasons, you need robocall mitigation for call origination and termination.

Robocall mitigation at origination and termination

Robocall mitigation at origination and termination

TransNexus offers a suite of software solutions that enable you to:

  • Implement a robocall mitigation program to prevent unlawful robocalls from originating on your network
  • Protect your enterprise and residential customers from receiving unwanted, disruptive robocalls

These robocall mitigation solutions include:

  • Dynamic traffic analysis
  • Reputation service
  • Blacklisting to prevent neighbor-spoofing
  • Customer-maintained blacklists
  • Shield detection of high-risk and invalid numbers
  • STIR/SHAKEN call authentication

Dynamic traffic analysis

Realtime dynamic traffic analysis monitors call traffic from specific calling numbers. If the number of calls from a number exceeds thresholds, then the software will perform the action you chose during setup: either block the call, divert it to another call handling system (like our CAPTCHA gateway), or complete the call and log it in a report for your review.

Reputation service

This service checks the reputation of the calling number using crowdsourced databases of robocall caller IDs.

With the reputation service, you can set up policies that will either block call from a number with poor reputation, divert it, or report only. For example, some carriers have set it up to divert calls from a low-reputation calling number to the customer’s voicemail. Alternatively, you could divert such calls to a CAPTCHA gateway.

Blacklisting to prevent neighbor-spoofing

The whitelist/blacklist service has powerful capabilities that can be used for a variety of purposes. One use is to screen calls when the calling number is like the called party’s number, a robocall tactic called neighbor spoofing.

You can blacklist calls that arrive at your peering SBC where the calling number is assigned to your OCN/SPID. Normally, such calls would be internal to your network. If they arrive from the external network at the edge of your network, they probably involve neighbor spoofing. Blacklisting your own OCN/SPID at the edge of your network can block a lot of robocalls.

You can set up the blacklist to divert such calls to a CAPTCHA gateway.

Customer-maintained blacklists

Our software products provide APIs (application program interface) that you can use with your customer web portal to allow your customers to set up their own blacklists. You would need a web portal that authenticates subscribers before they can enter a request to block calls to their number from a specific calling number.

Shield detection of high-risk and invalid numbers

TransNexus maintains a database of high-risk numbers compiled from many sources. These numbers include premium-rate numbers, for example, and numbers known to be used in robocalls. You can enable the Shield service to block, divert or report those calls to protect yourself from robocalls and fraud attacks.

The Shield service can also identify invalid calling numbers. You can configure similar responses when such calls are detected. For example, the CRTC has mandated that terminating service providers in Canada block calls with invalid calling numbers. The Shield service makes this easy.

STIR/SHAKEN call authentication

STIR/SHAKEN is a framework where the originating service provider attests to the validity of caller ID information and adds a cryptographically-signed caller ID authentication. At the other end of the call path, the terminating service provider checks the attestation, verifies the cryptographic signature and presents the verification status to the called party.

Call authentication makes called parties trust authenticated caller ID. They’re more likely to answer such calls. Call authentication also makes the other robocall analytics methods above more effective.

Get started today

Let us show you how easy it can be to get started with robocall prevention. Contact us today to learn more.

Request info about our products and services

* required

This information will only be used to respond to your inquiry. TransNexus will not share your data with any third parties. We will retain your information for as long as needed to retain a record of your inquiry. For more information about how we use personal data, please see our privacy statement.

More on TransNexus.com

September 22, 2020

SHAKEN, robocall mitigation, or both?

September 22, 2020

Initial reactions to FCC Second Order on SHAKEN

September 16, 2020

Robocall mitigation program mandate

September 9, 2020

FCC issues further rules on SHAKEN and robocall blocking

September 2, 2020

Comments filed on FCC robocalling fourth FNPRM

August 26, 2020

Update to SHAKEN standard improves authentication of forwarded and diverted calls

August 24, 2020

Robocalls trending up again in the U.S.

June 29, 2020

FCC issues staff report on robocall blocking tools

June 25, 2020

Open source Call Placement Service advances SHAKEN call authentication for all

April 7, 2020

Who may authenticate calls for STIR/SHAKEN

April 1, 2020

FCC issues STIR/SHAKEN mandate

January 20, 2020

NTCA discusses barriers to SHAKEN faced by rural carriers

January 2, 2020

STIR/SHAKEN mandate signed into U. S. law

October 1, 2019

FCC filings calling for Out-of-Band STIR

August 15, 2019

ClearIP now supports Rich Call Data in STIR/SHAKEN

April 29, 2019

ClearIP now supports out-of-band STIR/SHAKEN