IPRNVOICE › Guides › IPRN fraud protection

IPRN guide

IPRN fraud protection: CLI limits and traffic control

In IPRN, bad traffic is expensive twice: it isn't paid, and it gets ranges and accounts blocked. This guide explains where fraudulent and unwanted IPRN traffic comes from, the warning signs, and the controls — CLI rules, limits, real-time monitoring and alerts — that keep your traffic clean.

Why traffic control matters in IPRN

IPRN payouts flow down a chain: carrier → terminating operator → IPRN provider → you → your agents. Every party in that chain checks traffic quality. When traffic looks artificial, the minutes are disputed, payments are withheld and the range may be closed. The cheapest fraud protection is to stop bad calls before they are answered and paid to an agent.

Where bad traffic comes from

International Revenue Share Fraud (IRSF) — calls generated through hacked PBX systems, compromised SIP accounts or stolen and cloned SIM cards.
Wangiri — missed-call scams that trick people into calling premium numbers back.
Robotic or looped traffic — automated calls with unnatural patterns, repeated CLIs or identical durations.
An agent's bad source — one agent sending low-quality or fraudulent traffic that puts the whole range at risk.

Warning signs in your reports

Signal	What it can mean
Same CLI calling again and again	A dialler, a compromised line or a test loop
Sudden spike on one number or range	A new, unverified traffic source
Calls at odd local hours	Traffic not coming from real people in that country
Very uniform call durations	Automated traffic
CLIs from unexpected countries or prefixes	Spoofed or hijacked origins
ASR or ACD far from normal for the range	Changed routing or artificial traffic

CLI controls: whitelist, blocklist, per-CLI limits

The caller's number (CLI) is the most useful signal you have. Good CLI control works on two levels:

Whitelist per range — only approved CLIs are accepted on sensitive ranges.
Blocklist — known bad CLIs or prefixes are rejected everywhere.
Per-CLI limits — cap calls or minutes per CLI per day so one caller can't flood a number.
Shareable CLI links — agents load their own approved CLIs through a link, and you can see who added each CLI.

Limits per range, number, agent, country and timezone

Limits turn a disaster into a small, contained problem. Set daily and weekly caps on:

Range — total minutes or calls the range may take.
Number — so no single number gets an impossible amount of traffic.
Agent — so one agent's source can't use up a whole range.
Country and prefix — accept traffic only from where you expect it.
Timezone — limits and reports in the range's local time, so "daily" means the right day.

Call duration control

Fixed or random duration rules per range keep call lengths inside what your provider accepts, and multi-duration rules let different ranges behave differently. Combined with limits, this stops a single source from building up unrealistic minutes.

Real-time monitoring and alerts

Live calls grouped by range, provider, agent, number or CLI — see a spike as it happens.
Traffic-pattern detection — automatic flags when patterns look abnormal.
Instant alerts on Telegram, plus a daily summary.
Act from your phone — block a number or CLI, or disable an agent or range, with a yes/no confirmation.

Rejected-call logs and audits

Every call your system rejects should be logged with source IP, number, CLI, reason and SIP code. This shows that your rules are working, helps you answer provider questions, and shows which agents or sources are sending bad traffic. Login history for admins, agents and sub-agents completes the audit trail.

Built into IPRNVOICE

Two-level CLI control with whitelist, blocklist and shareable CLI links; daily and weekly limits per range, number, agent, CLI, prefix, country and timezone; multi-duration control; rejected-call logs with SIP codes; AI traffic-pattern detection; and a Telegram bot for alerts and instant blocking.

Request a demo panel login See CLI limits & rejected calls

Daily checklist

Check the daily summary for spikes by range and agent.
Review the top CLIs — any repeating or unexpected ones?
Look at the rejected-call log: which rules fired, for which agent?
Compare ACD and ASR per range with normal levels.
Check which ranges or numbers are close to their limits.
Disable sources that keep tripping rules, and tell the agent why.

FAQ

What is IRSF?

International Revenue Share Fraud: criminals generate calls to premium or high-cost international numbers through hacked phone systems, compromised SIP accounts, stolen SIMs or call-back scams, and try to collect the revenue share. It is illegal, and IPRN platforms must block it.

What is a CLI limit in IPRN?

A CLI limit caps how many calls or minutes a single caller number (CLI) can make to a number or range in a day or week. It stops one source from flooding your numbers.

Why does fraud traffic hurt the range holder?

Providers and carriers detect artificial traffic and refuse to pay for it, and they may close the range. If you have already paid an agent for those minutes, you lose that money too.

Can I block traffic from my phone?

Yes. With IPRNVOICE's Telegram bot you can block or unblock a number or CLI and enable or disable an agent or range, after a yes/no confirmation.

Should limits be set per agent or per range?

Both. Range limits protect your provider relationship; agent limits make sure one agent's traffic source can't use up or endanger a whole range.

Last updated: 22 October 2026 · IPRNVOICE