Current module
Detect fraudulent A2P SMS traffic carried as P2P
WebCDR A2P Revenue Protection applies explainable heuristics to SMS usage records so a mobile operator can identify likely A2P activity, review the evidence, and control its commercial treatment.
Why the traffic matters
A2P traffic presented and carried as P2P can bypass the route and price intended for application messaging. It often originates with parties defrauding mobile networks, or arrives through an operator that is unable or unwilling to detect the fraud. Identifying it creates evidence for revenue protection, partner management, and operational investigation.
How the current module works
- Analyzes a rolling 90-day history of SMS traffic records.
- Applies deterministic, rule-based heuristics to activity associated with each originating address (OA).
- Records explainable rule evidence so a classification can be reviewed.
- Provides a web UI for a manager to override treatment per OA; routine per-OA approval is not required.
- Produces A2P/P2P split files and OA lists for downstream processing and investigation.
From heuristic evidence to carrier action
Revenue treatment
Use classified outputs within agreed rating, billing, partner, and assurance workflows.
Dealer-channel investigation
When SIMs or eSIMs are distributed by independent retailers, cross-reference offending P2P OAs with dealer distribution records to identify non-compliant or fraud-enabling channels.
Partner engagement
Use OA lists and rule evidence to support investigation of transit traffic and conversations with interconnected operators.
Current boundary: input compatibility is confirmed during technical discovery; additional XML or binary formats require development. Rotating OAs are not represented as a specifically correlated capability. Processing cadence and orchestration are defined for each implementation. Classification supports operational telecom-fraud management; it is not a legal adjudication.
Assess A2P leakage in your SMS traffic
Start with a non-sensitive overview of record format, volume, interconnect context, and current A2P/P2P treatment.