Robocall prevention

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

  • 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.

TransNexus offers a suite of software solutions that enable you to protect your enterprise and residential customers from receiving unwanted, disruptive robocalls. These robocall prevention solutions include:

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

SIP Analytics

SIP Analytics 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.

montage of robocall words, such as fines, technology, regulators and so forth

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 information

* 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

Dec 5, 2022

STIR/SHAKEN statistics from November 2022

Nov 28, 2022

Webinar — Get ready for STIR/SHAKEN

Nov 21, 2022

ATIS Robocalling Testbed adds features

Nov 9, 2022

Legal Entity Identifiers and call authentication

Nov 2, 2022

STIR/SHAKEN statistics from October 2022

Oct 26, 2022

Reply comments on SHAKEN extensions and effectiveness

Oct 19, 2022

NTCA suggestions for FCC non-IP SHAKEN inquiry

Oct 17, 2022

Proposed updates to SHAKEN governance standards

Oct 10, 2022

FCC to consider SHAKEN for TDM

Oct 5, 2022

Comments on SHAKEN extensions and effectiveness

Sep 29, 2022

Proposed updates to delegate certificate standards

Sep 19, 2022

Reply comments on proposed SHAKEN and robocall mitigation rules

Aug 29, 2022

Updated SHAKEN standard improves security

Aug 22, 2022

Comments on proposed SHAKEN and robocall mitigation rules

Jul 18, 2022

Final gateway provider SHAKEN rules published

Jul 13, 2022

Third-party signing undermines SHAKEN

May 31, 2022

Best practices for terminating providers using STIR/SHAKEN

May 23, 2022

New SHAKEN and robocall rules for gateway providers

Mar 30, 2022

Delegate certificate roles and benefits

Mar 7, 2022

The evolution of SHAKEN implementation claims

Feb 21, 2022

Impact of FCC challenges to robocall mitigation filings

Feb 14, 2022

FCC questions some SHAKEN implementation claims

Dec 13, 2021

FCC order accelerates SHAKEN deadline for some small providers

Nov 1, 2021

Canadian SHAKEN token access policy revised

Oct 20, 2021

STI-GA announces support for enhanced SHAKEN functionality

August 16, 2021

Canadian regulator changes service provider SHAKEN qualifications

July 15, 2021

SHAKEN for TDM standards approved