IPRNVOICE › Guides › IPRN switch vs IPRN panel

IPRN guide

IPRN switch vs IPRN panel: what do you actually need?

People searching for IPRN software usually see two terms: IPRN switch and IPRN panel. They are not the same thing. The switch handles the calls; the panel is where you manage the business. This guide explains what each one does, how they work together, the three common setups, and how to choose.

The short answer

An IPRN switch is the telephony engine: it receives calls from your IPRN providers, answers them, plays audio and records every call. An IPRN panel (control panel) is the web application on top: it lets you manage providers, ranges, numbers, agents, limits, reports and payouts. To run an IPRN business properly you need both — the only question is whether they come as separate products or as one system.

What an IPRN switch does

The switch sits where the calls land. Your IPRN providers send SIP traffic to its IP address, and it has to:

Authenticate providers by IP so only your providers can send calls.
Match each call to a range and number using the dialled number.
Answer and play audio / IVR — prompts, recorded content or music per range.
Control call duration (fixed or random) and disconnect calls at the right time.
Apply limits in real time — reject calls that break CLI, country, timezone or number limits.
Handle concurrency — hundreds of simultaneous calls (ports) without dropping audio.
Write a CDR for every call: time, number, CLI, provider, duration and result.

Without a switch, there is nothing to answer the calls. A switch alone, however, gives you raw CDRs and configuration files — not a business tool.

What an IPRN panel does

The panel is where you and your team work every day. A good IPRN control panel lets you:

Manage providers, ranges and numbers, including test numbers and range payouts.
Run agents and sub-agents — give resellers their own logins, numbers and payout tiers.
Set traffic rules — CLI whitelist/blocklist, daily and weekly limits per range, number, agent, country and timezone.
Watch live calls and dashboards in real time.
Report — CDR, provider, agent, margin, timezone and rejected-call reports.
Bill and pay — usage, running balances, statements and payments for every agent.
Get alerts — for example on Telegram when traffic looks abnormal.

Side-by-side comparison

	IPRN switch	IPRN panel
Main job	Receive and answer calls	Manage the business
Used by	The system (and your engineer)	You, your team, agents and resellers
Works with	SIP, IP authentication, audio, ports	Ranges, numbers, agents, limits, money
Output	Answered calls + CDRs	Reports, statements, payouts, alerts
If it is missing	No calls can be answered	Spreadsheets, manual payouts, no fraud control
Fraud control	Enforces the rules on each call	Where you define and review the rules

Three common setups

1. Switch only

A general-purpose softswitch configured for IPRN. Calls work, but ranges, agents and payouts live in spreadsheets and limits need an engineer to change. Cheap to start, expensive to run.

2. Panel on someone else's switch

You get a reseller login on a provider's or vendor's platform. Quick to start, but you don't control the routing, limits or data, and you can't build your own agent network.

3. Switch + panel in one system

A complete IPRN management system: the call engine and the control panel share the same data, so a limit set in the panel is enforced on the next call and every report matches the CDRs.

Hosted option

If you don't want to run any server at all, a fully hosted IPRN IVR platform such as LCR ONE IPRN Tool runs the switch for you.

Which one do you need?

You are testing IPRN with one provider and a few ranges — a hosted platform or a panel login is enough to learn the business.
You have your own traffic and several providers — you need your own switch and panel so you control routing, limits and data.
You run agents or resellers — you need a panel with multi-level agent portals, payout tiers and statements; a switch alone cannot do this.
You need to stop fraud and unpaid traffic — you need CLI and limit rules defined in the panel and enforced by the switch on every call.

IPRNVOICE: IPRN switch and panel in one

IPRNVOICE combines a built-in call engine with a full admin control panel, agent and sub-agent portals, per-range traffic control, test numbers, CLI limits, reports and statements. No separate softswitch to buy or integrate. 100–1000 concurrent ports, from $300 per month.

Request a demo panel login See the panel

Checklist before you buy IPRN software

Is the call engine included, or do I need a separate softswitch?
How many concurrent ports per server, and can I add more?
Can I set limits per range, number, agent, CLI, country and timezone — and are they enforced live?
Do agents and sub-agents get their own portal, numbers and payout tiers?
Are test numbers, rejected-call logs and margin reports built in?
Do statements and balances come from the same CDRs as the reports?
Who hosts it, who has access to my data, and what support is included?
Can I see a live demo login before paying?

FAQ

What is the difference between an IPRN switch and an IPRN panel?

The IPRN switch is the call engine that receives, answers and records IPRN calls. The IPRN panel is the web control panel where you manage providers, ranges, numbers, agents, limits, reports and payouts. You need both to run an IPRN business.

Can I use a normal softswitch as an IPRN switch?

Yes, a general-purpose softswitch can answer IPRN calls, but you will still need a way to manage ranges, agents, limits and payouts. Without an IPRN panel this is usually done manually in spreadsheets.

Is a reseller panel login enough?

A panel login on someone else's platform is a quick way to start, but you do not control routing, limits or the data, and you cannot run your own agent network on it.

Do I need a separate softswitch with IPRNVOICE?

No. IPRNVOICE has a built-in FreeSWITCH call engine with provider IP authentication, so the switch and the control panel come as one system.

How many ports do I need?

It depends on your traffic. Ports are the number of simultaneous calls. IPRNVOICE plans run from 100 to 1000 concurrent ports per server, and you can start small and add more.

Last updated: 22 October 2026 · IPRNVOICE