Outbound routing where quality is the constraint
Direct interconnects, quality-gated least-cost logic and verified caller identity — so your outbound calls arrive clean, attributed to you, and actually get answered.
Least cost routing, with a floor under it
Every wholesale carrier runs least-cost routing. The difference is whether quality is a constraint on that decision or a report you read afterwards.
Our routing engine treats a quality floor as a hard constraint. A cheaper route is only selected if it clears the ASR, ACD and MOS thresholds for that destination. Routes that degrade are withdrawn from rotation automatically and re-tested before they return.
We hold direct interconnects rather than buying through layers of intermediaries. Fewer hops means fewer transcodes, lower post-dial delay, and fewer places for a call to be lost or its identity stripped. It also means that when something breaks, we can fix it rather than open a ticket with the carrier we bought from.
We do not refile, re-originate or misrepresent jurisdiction to lower a cost — those practices are prohibited on our own network under Section 4.4 of our Acceptable Use Policy, and they are a principal reason caller identity gets stripped in transit elsewhere.
- Quality-gated LCR. Cheaper routes are only used when they clear the destination quality floor.
- Direct interconnects. Fewer hops, lower post-dial delay, fewer places for identity to be stripped.
- Automatic withdrawal. Degrading routes leave rotation on their own and are re-tested before returning.
- Verified identity. STIR/SHAKEN signing with attestation based on verified number ownership.
- No refiling. We never disguise jurisdiction or re-originate traffic to lower a rate.
What you get
Quality-gated routing
ASR, ACD and MOS thresholds per destination act as hard constraints on route selection, not as after-the-fact reporting.
Direct interconnects
Direct carrier relationships per destination, with diversity so a single carrier event is a reroute rather than an outage.
STIR/SHAKEN signing
Calls signed with the attestation your verified number ownership supports, protecting delivery on terminating networks.
Per-route telemetry
Live quality metrics by destination and route, so a degradation is visible to you as it happens.
Fraud controls
Velocity limits, destination blocking, concurrency caps and spend thresholds enforced in real time per account.
Automatic failover
Route withdrawal and re-selection typically inside a minute, without manual intervention.
Bringing outbound onto our routes
Profile destinations
We review your destination mix, volumes, duration profile and quality expectations — and confirm the traffic fits our policy.
Verify numbering
Evidence of your right to use the calling numbers you present, which is what sets your attestation level.
Configure routing
Route plan, quality thresholds, fraud controls and spend caps agreed and configured per destination.
Test and migrate
A supervised test window on live traffic, compared against your current numbers, then a phased migration.
Technical summary
| Signalling | SIP over UDP, TCP or TLS 1.2+ |
|---|---|
| Media | RTP and SRTP with media release supported |
| Route selection | Least cost within destination-level ASR, ACD and MOS thresholds |
| Failover | Automatic route withdrawal and re-selection, typically under 60 seconds |
| Caller identity | STIR/SHAKEN signing; attestation set by verified number ownership |
| Fraud controls | Velocity limits, destination blocks, concurrency caps, spend thresholds |
| Billing increment | Six-second increments after a six-second minimum on domestic traffic |
| Reporting | CDR export and live per-route quality telemetry |
What customers ask
The routing engine cannot select a route that is below the quality threshold for that destination — it is a constraint on the selection, not a preference weighted against price. If every route to a destination is below threshold, the traffic is held and we are alerted, rather than quietly delivered badly.
Attestation reflects what we have actually verified. Full (A) attestation requires that we know you through KYC, that the call originated from your authenticated endpoint, and that you have evidenced your right to use the calling number. Present a number we cannot verify and attestation drops accordingly — which is how the framework is meant to work.
Yes, subject to the same policy and quality standards, and subject to scoping during onboarding. International destinations carry tighter fraud controls by default — velocity limits, destination blocking and spend caps — because international revenue share fraud is the most common way a compromised PBX turns into a very large invoice.
Our fraud controls are designed to catch it in minutes rather than on the invoice: anomaly detection baselines your normal call patterns, and velocity, concurrency and spend thresholds stop runaway traffic automatically. Contact the 24/7 NOC immediately if you suspect compromise. Under our Terms you remain responsible for charges incurred through your account, so those controls protect both of us.
No. There is no price at which we carry predictive dialer, short-duration or robocall traffic, because the cost is not paid by us — it is paid by every other customer whose calls share the route. That refusal is the product.
Often bought together
Compare our routes against yours
Send your destination mix and current quality numbers. We will scope a route plan and run a supervised test so the comparison is measured rather than promised.