Wholesale VoIP Termination: How to Evaluate and Test a Provider

Every outbound call that leaves your platform has to be handed to a carrier that can deliver it to a number on the public telephone network. That hand-off is wholesale VoIP termination. Buyers usually compare providers on price per minute, and then discover that the cheapest route has poor answer rates, long post-dial delay, or an invoice that does not match their own records.

This guide is written for the person who has to choose and test a provider: a carrier operations lead, a UCaaS or contact center engineer, or a reseller building a route table. It defines the quality metrics precisely, shows how to run a fair side-by-side test, lists the rate-card traps that cost real money, and ends with a checklist you can paste into an RFP.

Explore MeraTalk's Wholesale VoIP solutions — built for carriers, resellers, and enterprises.

Termination is the process of delivering a call that begins as a SIP session to its destination on the PSTN or a mobile network. 'Wholesale' means the minutes are bought in bulk from a carrier at per-minute rates, rather than inside a retail seat plan.

Your platform sends a SIP INVITE to the provider's session border controller. The provider selects a route, which may be its own direct interconnect or a downstream carrier, and passes the call along until it reaches the carrier that serves the called number. Each additional carrier in the chain adds delay and another point where quality or billing can go wrong. The inbound direction, VoIP origination, has its own routing and cost model and should be evaluated separately.

Termination vs origination

• Termination is outbound: your system sends calls to a PSTN destination and you pay a per-minute rate.
• Origination is inbound: calls to your numbers are delivered to your platform. That side has its own costs and quality questions, which we cover in our guide to VoIP origination.
• Many wholesale contracts cover both directions, but the two should be evaluated separately.

Quality in termination is measured with a small set of standard metrics. Know exactly how each is calculated, because providers and dashboards define them slightly differently, and a number is only meaningful with its denominator.

A useful habit is to track the distribution, not just the mean. A route with a good average PDD and a long tail of slow calls will feel worse to users than the average suggests.

A test is only useful if the routes are compared under the same conditions. Most disappointing evaluations come from sending different traffic to different providers and then comparing numbers that were never comparable.

1. 1Pick your real destinations. Test the countries and number ranges you will actually send, including mobile as well as fixed, weighted by the traffic mix you expect.
2. 2Use the same traffic on every route. Split live calls randomly, or run the same test list across the routes in the same time windows, so that time of day does not favour one provider.
3. 3Use the same signalling settings. Same CLI mode, same codecs, same caller ID, same SIP headers, so you are comparing routes and not configurations.
4. 4Collect enough calls. For example, a few hundred attempts per destination per route gives a rough picture and a few thousand starts to separate real differences from noise. Treat these figures as illustrative: the right sample depends on how close the routes are.
5. 5Repeat across days. Test on at least a weekday and a weekend, and in the destination's busy hour, because routes often degrade under load.
6. 6Review the failures, not only the percentages. Check SIP response codes and the point in the call where failures occur, and listen to a sample of answered calls for audio problems, one-way audio and clipping.
7. 7Reconcile the bill. Compare the provider's CDRs and invoice with your own CDRs for the test period. A route that is cheaper on paper but bills differently is not cheaper.

Run the test with three routes where you can. Two routes show who is better; three show which differences are the provider and which are the destination.

Get Wholesale VoIP rates with transparent wholesale pricing.

The headline rate is only one input to what a minute costs. These terms change the effective price and are usually where disputes start.

• Billing increments. A 60/60 increment rounds every call up to the next full minute. A 1/1 increment bills per second. A 60/1 increment has a one-minute minimum and then bills per second. Short calls make the difference large.
• Minimum call duration. Some rate cards bill a minimum duration, or a connection fee, even on very short answered calls.
• Rounding. Ask whether durations are rounded per call or aggregated and then rounded, and which direction.
• Rate-change notice. Find the notice period for rate increases and whether the provider may change rates without notice. A short notice window means your margin can change overnight.
• Rate-card structure. Check whether rates are per country, per prefix or per mobile operator, how special ranges are priced, and what happens to unlisted prefixes.
• Failed-attempt and early-media billing. Confirm that unanswered or failed calls are not billed and when billing starts.
• Commitments and caps. Understand minimum monthly commitments, concurrent-channel and CPS limits, and what is charged if you exceed them.

A worked example (illustrative numbers)

For example, suppose a route is priced at 1.0 cent per minute and your calls to a destination are often short. A 31-second call costs about 0.52 cents at 1/1 billing, but 1.0 cent at 60/60, almost double. If a large share of your traffic is short calls, a provider offering a slightly higher rate with finer billing increments can be cheaper overall. Always model your own duration distribution before comparing rate cards.

CLI (calling line identification) routes deliver the original caller ID presented by your system to the called party. Non-CLI routes do not guarantee that. The caller ID may be replaced with a number chosen by the provider, may be blank, or may differ between calls.

• CLI routes are the right choice where the called party needs to see and call back a recognisable number, such as business calling, appointment reminders and customer service.
• Non-CLI routes are usually cheaper because they use paths that do not pass caller ID reliably. They fit traffic where caller ID does not matter, such as some verification and machine-to-machine flows.
• On a CLI route you are responsible for presenting only numbers you have the right to use. Presenting numbers you do not control can breach regulations and will get traffic blocked.

Whichever you choose, test your own caller ID end to end on a real phone in each destination country, because some networks overwrite or drop caller ID regardless of what the route promises. If you are comparing carriers specifically for international voice termination, MeraTalk's wholesale voice service covers A-Z destinations with CLI and non-CLI route options.

International revenue share fraud (IRSF) is when attackers generate calls to premium or high-cost destinations that share revenue with them, often by compromising a PBX or SIP account. The cost lands on the account that carried the traffic, usually within hours and often over a weekend.

A provider cannot make fraud impossible, but the controls it offers tell you how seriously it treats the risk. Look for:

• Destination controls: block-by-default or allow-list of countries and prefixes, with high-risk ranges closed unless requested.
• Spend and velocity limits: per-account daily caps, and limits on calls per second and concurrent channels.
• Real-time alerting: notification when traffic to a new destination or an unusual volume appears, with a documented process for suspending traffic.
• Account security: IP allow-listing, strong credentials and multi-factor authentication on the portal.
• Clear liability terms: what the contract says about fraudulent traffic that passed through your account, and the dispute window.

Apply the same controls on your side: lock down SIP credentials, disable international dialing for users who do not need it, and review call detail records daily.

For US traffic, regulatory standing is part of route quality, because carriers downstream increasingly refuse traffic from providers that are not registered. Ask for evidence of each of these, and for how STIR/SHAKEN attestation is handled on your traffic, rather than a statement that they are in place.

• FCC Form 499: telecommunications providers file a 499 registration and report revenues for universal service and related contributions. A 499 filer ID is a baseline sign that a carrier is a registered provider.
• Section 214: carriers that provide international telecommunications services hold international Section 214 authority from the FCC.
• Robocall Mitigation Database: providers must file a certification in the FCC's Robocall Mitigation Database, and the FCC requires intermediate and terminating providers to refuse traffic from providers that are not listed.
• STIR/SHAKEN: originating providers sign calls with an attestation level (A, B or C), and intermediate providers must pass the signature on. Ask how attestation is determined for your traffic and how it is preserved across transit.

Regulatory requirements change. Ask the provider for its current filing identifiers and confirm them in the FCC's public databases rather than relying on a marketing page.

Grey routes

Grey routes bypass the official interconnect path, often by delivering international traffic as if it were local. They can look cheap, but they put you at risk of failed attestation, blocked traffic and, in some countries, regulatory exposure. A provider that cannot describe how its routes reach the destination carrier is often selling one.

Capacity has two limits: concurrent channels and calls per second (CPS). A dialer can exhaust CPS while using few channels, so confirm both limits and what happens when you exceed them: queueing, or an immediate busy response.

Resilience comes from running at least two routes for important destinations, with automated failover on SIP failure codes and quality thresholds, plus a steady trickle of live traffic on the backup so you know that it works.

Finally, reconcile your CDRs with the provider's each billing cycle. Common sources of variance are rounding differences, clock drift between switches, calls rated to the wrong destination code, and disagreement over what counts as answered. Raise disputes within the contractual window with matched CDR samples as evidence.

Copy this list into a request for proposal or a vendor questionnaire. A good provider will answer each point in writing.

1. 1Which destinations are covered A-Z, and which are direct routes versus transit through other carriers?
2. 2Are CLI and non-CLI routes both available, and how is each labelled on the rate card?
3. 3What billing increments, minimum durations and connection fees apply, and how are durations rounded?
4. 4What is the notice period for rate changes, and how are changes published?
5. 5How are ASR, ACD, PDD and NER reported, at what granularity and delay, and can I export raw CDRs?
6. 6What test arrangement is offered, and can I run a trial on my own destinations before committing volume?
7. 7What limits apply to channels and CPS, and how is exceeding them handled?
8. 8What fraud controls exist: destination blocking, spend caps, velocity limits, real-time alerts?
9. 9Provide your FCC 499 filer ID, evidence of international Section 214 authority and your Robocall Mitigation Database listing.
10. 10How is STIR/SHAKEN attestation applied and preserved across your network?
11. 11What are the support hours, escalation path and incident communication process?
12. 12What are the dispute window, payment terms and the process for suspension?

Ready to get started with Wholesale VoIP termination?

Join thousands of businesses using MeraTalk for Wholesale Voice, VoIP, and phone number services.

Frequently Asked Questions