In development · early access

Your CDRs say the call connected.
QTest tells you if anyone answered.

Active testing for wholesale voice. QTest originates controlled calls across the route you want to verify, terminates them on infrastructure we control, and records what actually happened — signalling, media, identity and timing.

The problem

A CDR cannot tell you what it never saw

Between your switch and the ringing handset there may be six carriers. Each one is a place where a call can be answered early to start billing, where the Caller ID can be rewritten, or where a route sold as premium direct is quietly least-cost routed. Your billing record shows none of it.

What the CDR shows

destination  +34 6xx xxx xxx
disposition  ANSWERED
duration     00:00:42
cause        16 — Normal clearing
billed       42 s

verdict      looks fine

What QTest recorded

200 OK at     +3.10 s
true answer   never
post-answer   ringback, 42 s
CLI sent      +1 305 555 0142
CLI received  +34 91 000 0000
media         inbound only

verdict       CONFIRMED FAS

How it works

A real call, watched from both ends

The difference between guessing and knowing is controlling the terminating side. When QTest owns both ends of the call, it knows the exact moment the far end truly answered — so a premature 200 OK is not an inference, it is a measurement.

QTest origination Your SBC trunk Route under test carrier A → B → … QTest node known answer time INVITE → ← 18x / 200 / RTP captured on every call SIP trace · RTP · audio · PCAP · timings · CLI

Capabilities

Everything the call actually did

Each test produces a complete technical record, not a pass/fail flag.

False Answer Supervision

Because QTest controls the terminating side, the true answer moment is known. A 200 OK that arrives before it is measured, not guessed.

  • answer before true pickup
  • answer with no media
  • answer onto an announcement
  • answer while ringback continues
  • early media billed as answer

Caller ID verification

What you sent, against what actually arrived — compared across every identity header, because carriers often rewrite only one.

  • stripped · replaced · truncated
  • prefix altered · anonymised
  • local CLI substitution
  • From vs PAI vs RPID mismatch

Audio capture and analysis

A known reference signal is played from the far end, so received audio is compared against what was truly sent.

  • silence · one-way audio
  • dropouts · robotisation
  • unexpected announcements
  • DTMF pass-through

SIP signalling

The full dialogue with millisecond timestamps, rendered as a ladder diagram, with anomalies called out.

  • INVITE · 18x · 200 · ACK · BYE
  • release cause and Q.850
  • SDP and negotiated codec
  • 200 OK with no provisional

PCAP evidence

A per-call capture, filtered to that call alone, that opens in Wireshark with no post-processing.

  • SIP and RTP together
  • optional payload stripping
  • SHA-256 manifest

Timing metrics

Every stage of setup, and the gap that matters most: signalled duration against real media duration.

  • post-dial delay (PDD)
  • time to ringback
  • ring duration · answer delay
  • duration delta

RTP quality

Transport measured from the packets themselves, separating a routing problem from a network problem.

  • packet loss · jitter
  • reordering · gaps
  • mid-call interruption
  • carried vs negotiated codec

Scheduled campaigns

Turn testing into a standing part of NOC operations rather than something done after a complaint.

  • from every 5 minutes
  • destination lists per country
  • randomised timing
  • API-triggered on alarm

Route comparison

The same destination across several vendors, side by side, so routing decisions rest on measurements rather than on price per minute alone.

  • FAS and CLI integrity rate
  • PDD · ASR · duration delta
  • by country and mobile operator
  • trend over time

Disputes

Stop arguing. Start attaching files.

A claim without evidence is a conversation. A claim with SIP traces, recordings and PCAPs is a credit note. QTest assembles the whole file for you.

  • Evidence pack — summary, per-call results, traces, audio, PCAPs, as one archive or a PDF
  • Route as it was — the route definition at execution time, not today's edited version
  • SHA-256 manifest — so the recipient can prove nothing was altered after export
  • UTC everywhere — ambiguous local timestamps are worthless in a dispute
Instead of "the route has FAS" Between 14:00 and 14:30 UTC we ran 20 test calls to the affected destination over route ES-MOBILE-PREMIUM / Carrier B. In 17 of them a 200 OK was returned a mean of 2.8 s before the terminating node answered, with ringback continuing for the full billed duration. Recordings, SIP traces, test ids and PCAPs are attached, with a SHA-256 manifest.

Integration

Built to be driven by your NOC, not just by people

Everything the portal does is available over a versioned REST API with an OpenAPI 3.1 specification, scoped API keys, signed webhooks and a sandbox that returns realistic results without placing a single billable call.

POST /api/v1/tests
{
  "route_id":    "rt_es_mobile_premium",
  "destination": "+346XXXXXXXX",
  "ani":         "+13055550142",
  "codecs":      ["g729", "ulaw"],
  "topology":    "controlled_termination",
  "webhook_url": "https://noc.example/qtest"
}

→ 202 Accepted
{ "test_id": "tst_01J8ZQ…", "state": "queued" }
webhook · test.completed
{
  "test_id": "tst_01J8ZQ…",
  "outcome": "completed",
  "fas": {
    "verdict":    "confirmed_fas",
    "rules":      ["FAS-1", "FAS-4"],
    "answer_gap_ms": 2810
  },
  "cli": { "result": "replaced" },
  "timings": { "pdd_ms": 1840 },
  "artifacts": ["recording", "pcap", "sip_trace"]
}

Early access

QTest is in active development

We are onboarding a small number of carriers and wholesale operators to shape the platform before general availability. If you route international voice and you have ever suspected a vendor without being able to prove it, we would like to talk.

QTest is pre-release. Capabilities on this page describe the platform as specified; availability by phase is shared during onboarding. Test calls are real calls — customers confirm they are authorised to test the destinations they select.