A fraudulent call can travel through several legitimate telecom networks before anyone recognises it as a threat. By the time a customer reports suspicious activity, the traffic may have already crossed multiple providers and reached thousands of recipients.
For telecom providers, preventing voice fraud requires more than blocking suspicious numbers. It calls for a coordinated strategy that combines network visibility, caller ID authentication, customer verification, traffic analysis and effective incident response. Each layer addresses a different weakness in the calling ecosystem.
PeeringHub supports an important part of this strategy through its STIR/SHAKEN Certificate Authority services, certificate lifecycle tools and Identity Header inspection capabilities. These technologies help providers strengthen caller ID authentication while complementing the wider fraud prevention controls they operate across their networks.
Start by Understanding Where Voice Fraud Enters the Network
A strong prevention strategy begins with understanding how fraudulent traffic reaches a provider's infrastructure. Voice fraud is not limited to spoofed caller IDs. It can involve compromised accounts, illegal robocalls, toll fraud and abuse of wholesale calling routes.
Identify the Main Types of Voice Fraud
Telecom providers should recognise several common threats:
Caller ID spoofing: Fraudsters manipulate displayed telephone numbers to impersonate trusted individuals or organisations.
Illegal robocalling: Automated campaigns generate unwanted or deceptive calls at scale.
International revenue share fraud: Attackers exploit compromised systems or calling routes to generate unauthorised calls to high-cost destinations.
Account takeover: Stolen credentials allow attackers to access legitimate business phone accounts and place calls.
Traffic pumping: Artificial call activity is generated to exploit intercarrier compensation or other revenue arrangements.
Upstream provider abuse: A wholesale or intermediate provider introduces suspicious traffic into the network without adequate controls.
These threats require different responses. STIR/SHAKEN can help authenticate caller ID information but it cannot independently detect every compromised account or unusual billing pattern.
Map the Call Journey
Providers should examine where they originate, receive, route and terminate calls. This helps identify which systems have visibility into customer identity, caller authentication and traffic behaviour.
For example, a suspicious call may enter through a wholesale partner before reaching a domestic carrier. If the receiving provider only examines the displayed number it may overlook the upstream source responsible for introducing the traffic.
Mapping the call journey makes it easier to assign responsibility and determine where monitoring controls should operate.
Strengthen Caller ID Authentication with STIR/SHAKEN
Caller ID authentication is a foundational component of voice fraud prevention, particularly for providers operating in the United States.
How STIR/SHAKEN Establishes Caller Identity
STIR/SHAKEN uses digital certificates and cryptographic signatures to help authenticate caller ID information on IP-based voice networks.
When an originating provider signs a call, it creates a PASSporT identity token and carries it in the SIP Identity header. The receiving provider can retrieve the associated certificate and validate the signature.
The framework also communicates the originating provider's level of confidence through three attestation levels:
A – Full Attestation: The provider knows the customer and has verified their authority to use the calling number.
B – Partial Attestation: The provider knows the customer but cannot verify their authority to use the specific number.
C – Gateway Attestation: The provider can identify the point where the call entered its network but does not have a direct relationship with the original caller.
These levels provide useful authentication context but should not be treated as automatic fraud classifications. A C-level call is not necessarily fraudulent and an A-level call is not necessarily safe.
Make Certificate Management Part of the Security Strategy
STIR/SHAKEN depends on correctly issued and managed certificates. Providers need processes for private key protection, certificate renewal, revocation and certificate availability.
PeeringHub supports these workflows through its STI-ACME server which follows RFC 8555 and provides automated certificate issuance for eligible service providers. Providers must have their own OCN and approved STIR/SHAKEN Service Provider status from the STI-PA before completing the required onboarding process.
This gives providers access to a dedicated certificate infrastructure without having to develop the entire certificate issuance workflow themselves.
Build Better Visibility Through Traffic Monitoring and Analytics
Authentication tells providers something about caller ID integrity. Traffic analytics help them understand whether calling activity behaves normally.
Monitor Behaviour Instead of Just Blocking Numbers
Fraud campaigns frequently change the numbers they display. Blocking individual caller IDs may therefore have limited effectiveness against high-volume campaigns.
Providers should monitor indicators such as:
Sudden increases in outbound call volume.
Unusual international calling destinations.
Repeated short-duration calls.
Unexpected calling activity outside normal business hours.
High call attempts from newly created accounts.
Unusual changes in call completion rates.
Repeated authentication failures or missing authentication information.
For example, a business account that normally makes a modest number of domestic calls suddenly begins generating hundreds of international calls within a short period. A monitoring system can flag this change for investigation before the activity creates a substantial financial loss.
Combine Multiple Signals
A stronger detection process evaluates several indicators together. A call with missing authentication information may not be fraudulent by itself. However, if it also comes from an unusual upstream source and forms part of a high-volume calling pattern it may deserve closer examination.
This layered approach reduces dependence on any single detection rule.
Providers can develop their own analytics systems or integrate specialist third-party solutions. The important requirement is to ensure that alerts lead to clear investigation and response procedures rather than simply generating more notifications.
Improve Customer and Upstream Provider Verification
A provider's fraud prevention strategy is only as strong as its understanding of the organisations and customers using its network.
Apply Know Your Customer Controls
Customer onboarding should establish who is using the service and whether the requested calling activity is consistent with the customer's business.
Useful checks include:
Verifying business identity and contact information.
Confirming authorised account representatives.
Reviewing expected calling destinations and volumes.
Establishing controls for number ownership or authorisation.
Monitoring significant changes in account behaviour.
Applying appropriate access restrictions to calling credentials.
For example, a newly registered account requesting unusually high international calling capacity may require additional verification before those capabilities are activated.
Know Your Upstream Providers
Wholesale and intermediate relationships also need scrutiny. Providers should understand who supplies their traffic and have a process for reviewing suspicious activity associated with upstream partners.
This includes checking business information, reviewing available compliance records and monitoring traffic quality over time.
The FCC's robocall mitigation framework requires providers to take reasonable steps to mitigate illegal robocalls and address their customer and upstream-provider responsibilities. In its 2026 proposed rulemaking, the FCC also proposed more specific Know-Your-Upstream-Provider requirements and stronger oversight of STIR/SHAKEN practices. Those additional measures are proposals and should not be confused with already-finalised requirements.
The practical lesson is clear: providers should not assume that a traffic source is trustworthy simply because it has an established commercial relationship.
Establish a Clear Response Process for Suspicious Traffic
Detection is valuable only when providers can act on what they discover. A fraud prevention programme needs defined procedures for investigating alerts, containing threats and preserving relevant records.
Create an Incident Response Workflow
A practical response process can follow five stages:
Detect: Identify suspicious call patterns through authentication results, analytics or customer reports.
Investigate: Review call records, account activity, Identity headers and upstream routing information.
Contain: Apply appropriate controls such as restricting compromised accounts or blocking traffic where permitted.
Trace: Work with relevant providers and industry traceback organisations to identify the source.
Review: Document the incident and update detection rules or operational controls to reduce recurrence.
Consider a provider that discovers an account generating unauthorised international calls. Its response should include restricting the compromised credentials, reviewing call records and investigating how the account was accessed. Blocking the destination numbers alone would not address the underlying account compromise.
Maintain Traceback Readiness
In the United States, applicable providers must commit to responding fully within 24 hours to traceback requests from the FCC, law enforcement and the industry traceback consortium and cooperate with investigations into illegal robocalls.
This makes recordkeeping and internal coordination important operational requirements. Providers should know who handles traceback requests and how relevant call information can be retrieved without unnecessary delays.
Treat Compliance and Operational Security as Continuous Processes
Voice fraud prevention is not a one-time deployment. Network conditions, customer behaviour and fraud techniques change, so controls must be reviewed regularly.
Maintain Accurate Robocall Mitigation Records
For providers subject to the US FCC framework, Robocall Mitigation Database obligations are an important part of operational compliance.
The FCC's 2024 Report and Order strengthened the accuracy and maintenance of database filings. It introduced requirements for prompt updates when relevant information changes and annual recertification of filings. The FCC also highlighted the importance of accurate provider information and documented mitigation practices.
Providers should ensure that their documented mitigation programme reflects the controls they actually operate. A written policy that is not followed in practice offers little protection.
Review Security Controls Regularly
A useful review should examine:
Certificate validity and renewal status.
Private key access and storage.
Authentication failures and unusual verification results.
Customer onboarding and account access controls.
Upstream provider performance.
Fraud alerts and incident response times.
Accuracy of regulatory filings and contact information.
This creates a feedback loop in which each investigation helps improve the prevention strategy.
How PeeringHub Supports the Caller Authentication Layer
A complete voice fraud prevention programme requires multiple technologies. PeeringHub focuses on the STIR/SHAKEN certificate infrastructure and supporting tools that help providers manage and inspect caller authentication information.
STI-ACME and Certificate Lifecycle Automation
PeeringHub's STI-ACME server supports automated STIR/SHAKEN certificate issuance through the ACME protocol. Its ACME API supports certificate issue, renewal and revocation workflows which can be integrated into provider systems.
Certificate Repository
A certificate must be accessible to the systems that need to validate signed calls. PeeringHub provides a Certificate Repository for hosting STIR/SHAKEN certificates and making them available through an appropriate certificate URL. ACME issuance and certificate hosting are separate functions.
Identity Header Parser and Certificate Inspector
PeeringHub's Identity Header Parser helps technical teams decode SIP Identity headers and inspect PASSporT information including attestation, origination, destination and certificate URL.
Its Certificate Inspector allows users to examine certificate details through pasted content, a certificate URL or an uploaded certificate file. These tools can support troubleshooting and investigation when authentication information needs closer examination.
STI API and Developer Tools
The STI API supports authentication token generation, private key generation and certificate requests. PeeringHub's Python-based STIR/SHAKEN Toolkit also provides utilities for certificate issuance workflows, inspection and validation.
These capabilities strengthen the certificate and caller authentication layer of a provider's security strategy. Traffic analytics, customer verification, account protection and call blocking remain separate responsibilities that providers must implement through their own systems and operational policies.
Conclusion: Build Voice Fraud Prevention Around Multiple Layers of Trust
A stronger voice fraud prevention strategy is built by connecting several operational controls rather than depending on one technology. Caller ID authentication establishes a foundation for trust while traffic analytics identify suspicious behaviour. Customer verification reduces opportunities for account abuse and upstream-provider oversight helps prevent illegal traffic from entering the network. Effective incident response then ensures that detected threats lead to meaningful action.
For telecom providers, the objective should be to create a security process that is measurable, maintainable and capable of adapting as threats evolve.
PeeringHub helps strengthen the caller authentication foundation through its STIR/SHAKEN Certificate Authority services, ACME automation, Certificate Repository and developer-focused inspection tools.
Strengthen your STIR/SHAKEN infrastructure and build a more reliable approach to caller authentication.
Explore PeeringHub's solutions at https://www.peeringhub.io/.

Post a Comment