Dialer Account Suspended? What to Do Now

A suspended dialer account calls for four moves today: export your CDRs, recordings, and lead lists from your own dialer servers; save the suspension notice and your DID inventory; start porting the numbers — FCC rules bar the losing provider from refusing a port over an unpaid balance; and stand up a trunk with a carrier that accepts dialer traffic.

This page assumes the worst case: campaigns dark, agents idle, revenue stopped. The pitch waits until the end — the checklist comes first.

Do this right now

Work the list in order. Every step protects something you cannot get back later.

1. Export your call detail records. On VICIdial, the Export Calls Report (there is a carrier-fields variant) pulls your full dial history — evidence of your traffic profile and of what actually happened before the suspension.

2. Locate your recordings. VICIdial’s Recording Lookup searches recordings and links to where each file lives. Recordings and CDRs are stored on your own dialer servers, not at the carrier — the suspension does not take them, but a panicked server teardown later can.

3. Export your leads. The Export Leads Report pulls lists out of the dialer. Same logic: get a clean copy outside the system before you change anything.

4. Download the carrier-portal CDRs too. The carrier’s own billing portal keeps a separate record of your traffic. If the account is headed for closure, pull those now — after closure you may lose portal access entirely.

5. Save the suspension notice and document the stated reason. Screenshot the email or portal message, note the date, and write down every DID on the account. You will need both when you talk to the next carrier and when you port.

6. Confirm the numbers can port out. Under FCC rules, the losing provider cannot refuse to port your numbers even if you owe an outstanding balance or a termination fee. Do not close the account before the port completes. Our number porting guide covers the mechanics.

7. Stand up a second trunk. The dialer is fine; only its route to the phone network is gone. A new carrier trunk gets agents dialing again while the porting and the post-mortem run in parallel.

One more fact while you wait: FCC rules require simple ports — single-line ports, including ports to VoIP — to complete within one business day. Your numbers are not hostages.

Why SIP providers shut off dialer accounts

If you searched “sip provider shut off my dialer account,” the honest answer is that the account probably tripped an acceptable-use rule that was there all along. Suspension notices across the industry tend to cite the same few categories.

• Complaint and answer-rate signals. High-volume outbound traffic that draws spam complaints or scam-likely labeling gets flagged, and upstream carriers pressure whoever is carrying it.
• Short-duration traffic on the wrong plan. Predictive dialers generate thousands of short calls. Retail and CPaaS voice plans are priced and policed for conversational traffic; a dialer’s call profile stands out immediately in their metrics.
• Registration and attestation problems. Outbound calling programs carry regulatory paperwork — robocall-mitigation registration, STIR/SHAKEN signing, campaign registration for messaging. Traffic that arrives without the paperwork looks like the traffic the rules exist to stop.

None of that makes your business illegitimate. It means dialer traffic was flowing through a provider that never intended to carry it — a mismatch that surfaces as a suspension, often without much warning. Our rundown of SIP providers that allow autodialers maps which providers actually want this traffic.

Twilio suspended the account? Their rules fit their platform

A large share of the operators who land on this page ran cold calling through Twilio. We will not pile on: Twilio’s rules make sense for Twilio’s platform, which is built around APIs and transactional traffic, not predictive-dialer campaigns. Cold calling — short calls at high attempt volume — simply is not the profile the platform is designed around.

The economics tell the same story. Twilio bills voice at 60/60, rounding every call up to a full minute, with no per-channel fees — the rounding is the cost driver, and pricing built that way assumes calls that last. The fix is not a workaround on the same platform. It is moving the dialer traffic to a carrier whose acceptable-use policy, billing increments, and vetting process were written for it.

SIP 503 after suspension: what your dialer logs are telling you

When a carrier suspends a trunk, your dialer often finds out one call at a time. A carrier rejecting an INVITE with SIP 503 Service Unavailable triggers a specific chain in Asterisk’s chan_sip (the channel driver VICIdial uses): the 503 maps to congestion — Q.850 cause 34 — and the channel receives a CONGESTION control frame. VICIdial logs the attempt with a congestion dial status rather than retrying the same carrier.

So a sudden wall of congestion statuses on every attempt, in a system that dialed normally yesterday, is a trunk-level rejection — not a network problem to debug for hours. A second failure mode reads the same: if the carrier stops responding to INVITEs entirely, Asterisk’s auto-congest timer fires and congests the call by a different path. Either way, the route is gone.

VICIdial’s Carrier Log Report summarizes those outcomes for a date range — counts grouped by dial status and hangup cause, and by SIP hangup cause. It is the fastest way to timestamp exactly when the carrier went dark, which is worth having in writing when you dispute the suspension.

How a dialer-friendly carrier vets you instead

The alternative to being suspended mid-campaign is being vetted up front. A carrier that wants dialer traffic asks the awkward questions before the first call: what you dial, at what volume, with what consent basis, what your average call duration looks like, and what happened at your last carrier. That conversation is the point — a carrier that knows your traffic profile on day one has no reason to be surprised by it on day forty.

That is how SIPNEX onboards VICIdial and outbound operations. We are an FCC-licensed carrier, we sign outbound calls with our own STIR/SHAKEN certificate at A-level attestation, and we are registered in the Robocall Mitigation Database. KYC happens before activation, not as a mid-campaign ambush. Bias disclosed: this page exists because suspended operators call us.

Migrating the trunk in under an hour

Once a new carrier has activated you, the VICIdial cutover itself is the under-an-hour part, because nothing that matters lives at the old carrier. Your leads, campaigns, recordings, and CDRs are all on your own servers. What changes is one carrier record and the routing that points campaigns at it.

In the VICIdial admin, carriers live under Admin → Carriers. Each carrier record has an Active field, so you can deactivate the suspended carrier without deleting its configuration — keep it as a record. Add the new carrier, then repoint your campaigns: campaign-to-carrier routing in VICIdial is done with dial prefixes matched against the carrier’s dialplan patterns, so cutting over is a prefix change, not a rebuild.

The full configuration walkthrough — authentication, sip.conf, dialplan, DID routing — is in our VICIdial SIP trunk setup guide; we won’t duplicate it here. And once you are live again, set up a second route before you need it: our backup carrier and failover guide covers keeping a standby trunk configured so the next outage — carrier-caused or otherwise — is a routing change instead of a dark day.

How to avoid round two

A new trunk with the same traffic habits ends the same way. The durable fix is traffic hygiene.

• Watch your own signals before someone else does. The Carrier Log Report and the hangup-cause data give you dial-outcome trends; per-carrier comparisons come from the exported call data. Falling answer rates are the earliest warning that your caller IDs are getting labeled.
• Get attestation right. Calls signed at A-level attestation by the carrier that knows the traffic start from a better reputation position than calls signed weakly by an intermediary.
• Put short-duration traffic on billing built for it. SIPNEX bills dialer traffic 12/6 — a 12-second minimum, then 6-second increments — because we expect short calls instead of penalizing them. Pricing that matches the traffic is also a signal that the AUP does.
• Keep the paperwork current. Registrations, consent records, and DNC scrubbing are what separate a legitimate outbound operation from the traffic carriers are required to block.

Frequently asked questions

If the account went dark today, skip the form queue: call (833) 665-2220 or contact us with your suspension notice, traffic profile, and DID list. We vet fast because we vet properly — and dialer traffic is the traffic we built the carrier for.