IPRNVOICE › Guides › IPRN test numbers
IPRN guideIPRN test numbers explained: what they are and how to manage them
Every IPRN range comes with test numbers. Providers use them to prove a range works, and buyers use them to check routing, audio and call duration before they send real traffic. Test numbers look simple, but if you manage them badly they can mix with live traffic, distort your reports and even cost you payouts. This guide explains how IPRN test numbers work and how to keep them under control.
What is an IPRN test number?
An IPRN test number is a number from a range that is used to test the route instead of carrying paying traffic. When a provider gives you a new range, they usually share one or more test numbers with it. You (or your agents) call the test number to confirm three things: the call reaches your platform, it is answered correctly, and the CDR is recorded on both sides.
Test numbers belong to the same range and prefix as the live numbers, so a successful test is a good sign the whole range is routed correctly. The difference is in how the calls are treated: test calls are for checking, not for earning.
Why test numbers matter
- They prove the route before money is involved. A range that fails on a test number will fail on live numbers too.
- They let agents check their setup. An agent can confirm that their traffic source reaches your switch before sending volume.
- They help when something breaks. If live calls stop, a quick test call tells you whether the problem is the range, the provider or the traffic source.
- They protect your reports. Test calls should not inflate minutes, ACD or payouts. Keeping them separate keeps your margin numbers honest.
How a test call works
1. Call the test number
A call is placed to the test number from a normal phone or a test tool, through the same path that live traffic will use.
2. Provider routes it
The IPRN provider sends the call to your platform's IP address. Your switch authenticates the provider by IP.
3. Your switch answers
The number is matched to its range, and the range's audio or IVR plays for the configured duration.
4. Both sides record it
A CDR is written on your platform and on the provider side, so you can compare time, duration and result.
What to check on a test call
| Check | What good looks like | If it fails |
|---|---|---|
| Call arrives | The call appears in live calls on your panel | Provider IP not whitelisted, or the range is not routed to you yet |
| Number matched | The call is linked to the correct range and number | Wrong prefix or the number is missing in the range |
| Audio / IVR | The right prompt or audio plays clearly | Audio file missing or wrong file set on the range |
| Duration | The call lasts as configured and ends cleanly | Duration rule wrong, or the provider cuts calls early |
| CDR | Time, number, CLI and duration match the provider's record | Clock or billing-increment mismatch to resolve before going live |
| Rejections | No unexpected rejected calls | Check the rejected-call log and SIP code to see which rule blocked it |
Common test-number mistakes
- Treating test numbers like live numbers. If test calls get the same payout as live traffic, agents can earn from "testing". Test numbers need their own rules.
- Leaving test numbers allocated forever. A test number that stays assigned to an agent after the test becomes a quiet leak.
- Mixing test calls into reports. Test minutes make ACD and margin look better or worse than they really are.
- No limits on test numbers. Without limits, one source can send heavy traffic to a test number and the provider may refuse to pay for it.
- Not keeping the test results. When a provider disputes minutes later, a clean record of the original test helps.
How to manage test numbers properly
- Mark test numbers clearly in your system, so everyone knows which numbers are for testing.
- Keep their limits and payouts separate from live numbers.
- Allocate them only for the test, then clear them so they return to the pool.
- Use CLI and daily limits on test numbers so they cannot become a traffic channel.
- Check the rejected-call log after each test so you can fix rule problems before live traffic arrives.
- Compare CDRs with the provider on the first day of a new range.
Test number management in IPRNVOICE
In IPRNVOICE you can mark any number as a test number and clear it instantly. Test numbers keep their limits and payouts separate from live traffic, every call shows in live calls and the CDR, and the rejected-call log shows the SIP code for any blocked test. You can also control numbers from the Telegram bot.
FAQ
What is an IPRN test number?
It is a number from an IPRN range that is used to test the route: it confirms that calls reach your platform, are answered correctly and are recorded, before real traffic is sent to the range.
Do test numbers pay like live numbers?
Usually not. Test numbers are for checking the route, so their payouts and limits should be kept separate from live numbers. Check the terms with your provider for each range.
Why is my test call not connecting?
The most common reasons are that the provider's IP is not authorised on your switch, the range is not routed to you yet, the number is missing from the range, or a limit or CLI rule rejected the call. The rejected-call log and SIP code show which one it is.
How long should a test call last?
Long enough to hear the audio and confirm the call ends cleanly and the CDR matches the provider's record. Follow the duration rules set for the range.
Should agents get their own test numbers?
They can get a test number to check their setup, but it should be allocated only for the test and cleared afterwards, with limits so it cannot be used as a live traffic channel.
Last updated: 23 October 2026 · IPRNVOICE