How to Test a VoIP Route Before Sending Production Traffic

Why test before you scale

A published per-minute rate tells you what a call costs, not how the route behaves for your traffic. Answer rates, post-dial delay, audio quality, DTMF handling and caller-ID presentation all depend on the destination, the time of day and the traffic profile. A short, structured test is the cheapest way to find a problem before it is multiplied across a full campaign.

Before the first call

• Choose 2–5 target prefixes that represent your real traffic (for example a fixed-line and a mobile prefix in each destination you will call).
• Prepare a list of numbers you are permitted to call — your own handsets, colleagues in the destination, or numbers you have consent to contact. Never test against purchased or scraped lists.
• Decide the caller ID you will present and confirm you are authorised to use it.
• Confirm the authentication method (SIP credentials or a fixed source IP), the codec your dialer offers, and the DTMF method it uses.
• Make sure your own network is stable: test from the same server and network path that production traffic will use.

A simple three-stage test plan

• Stage 1 — Connectivity (5–10 calls): calls set up, both parties hear each other clearly, the call clears cleanly on both sides and the dialer logs the expected SIP responses.
• Stage 2 — Behaviour (30–100 calls spread over at least two time windows): record answered vs. attempted calls, post-dial delay, average connected duration, DTMF success if you use IVR/Press 1, and what caller ID the called party actually sees.
• Stage 3 — Controlled ramp: increase concurrency and calls per second gradually up to your planned peak, watching for 503/486 rejections, rising PDD or audio degradation as load increases.

What to measure and how to read it

• ASR (Answer Seizure Ratio) = answered calls ÷ attempted calls. It depends heavily on your own lists and calling times, so compare routes on the same list and time window rather than against a "typical" figure.
• ACD (Average Call Duration) = total connected minutes ÷ answered calls. An unusually short ACD with many answered calls can indicate false answer supervision (calls billed as answered when they were not).
• PDD (Post-Dial Delay) = time from sending the INVITE to receiving ringing or answer. Consistently long PDD causes callers to hang up before the call connects and lowers answer rates for predictive dialers.
• Audio: listen for one-way audio, choppy or robotic sound, echo and silence on answer. Note the codec negotiated in the SDP.
• Caller ID: confirm on a real handset that the number presented is exactly the number you sent.
• Billing: compare your dialer's connected durations with the published billing increment for the prefix (see Understanding 1/1, 6/6, 60/1 and 60/60 Billing).

Red flags that should stop a ramp-up

• Calls marked answered that play ringback, silence or a recorded message instead of the destination (possible false answer supervision).
• Caller ID altered, missing or replaced when your route is meant to present it.
• A sudden rise in 503 or 486 responses as concurrency increases — usually a capacity or CPS limit, not a destination problem.
• DTMF digits not detected on IVR or Press 1 flows.

How route testing works at CallCenterBoost

Route tests are requested through the route-test form and reviewed manually; they are not provisioned instantly. The review considers the destination, intended lawful traffic, expected daily minutes and concurrency, your dialer or PBX, and whether you prefer SIP credentials or IP authentication. Availability, test terms and pricing are confirmed by the team before activation — nothing on this page is a promise that a particular route, figure or result is available.

If a test shows a problem, open a VoIP Route support ticket with the affected prefixes, timestamps (with time zone) and any SIP response codes, as described in What to Include in a Call-Quality Ticket.