VICIfast
Feature · Trunk Management

Trunk Management.

BYO SIP. Templated PJSIP for Twilio, Bandwidth, Telnyx, Skyetel — fill three fields and the endpoint, identify, and aor blocks render correctly. Inbound and outbound directions are split; you can dedicate a carrier to origination and another to DIDs. 4-digit dialplan prefixes auto-allocate per trunk so VICIdial campaigns bind cleanly. Failover routes wrap multiple trunks in priority order, with per-leg timeouts. Built-in diagnostics tell you why a trunk is failing without an SSH session — endpoint state, OPTIONS handshake, carrier-IP reachability, last 50 dial attempts, plus a live SIP trace you can share with carrier support.
See pricing

7-day free trial · Cancel anytime · Pay with card, PayPal, or USDT

vicifast — trunk-management
[twilio-out]
type=endpoint
context=trunkoutbound
disallow=all
allow=ulaw
outbound_auth=twilio-out-auth
aors=twilio-out-aor
from_domain=your-sub.pstn.twilio.com

; dialplan generated from your trunk's allocated prefix 9742:
exten => _9742X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9742X.,n,Dial(PJSIP/${EXTEN:4}@twilio-out,,tor)
exten => _9742X.,n,Hangup
40smedian deploy time
99.94%fleet uptime · last 30d
6regions live
Auditedevery state change

What you get

The full trunk management surface, end-to-end.

Every card below is a shipped capability. Hover for emphasis; click any matching feature for the deep page.

BYO SIP, never resold

Use Twilio, Bandwidth, Telnyx, Skyetel, Voxbeam, Plivo, or anything that speaks PJSIP. We do not resell minutes. We do not take a cut. Your invoice from the carrier never sees our name.

Inbound + outbound split

Dedicate one carrier to outbound, another to inbound DIDs. Each direction has its own template, its own IPs, its own context — exactly how production VICIdial deployments actually run.

Auto-allocated dialplan prefix

Every trunk gets a unique 4-digit dialplan prefix (range 9000–9499). VICIdial campaigns set the same prefix and route lands on the right carrier. No more manually editing extensions.conf when you add a trunk.

Failover routes

Group 2–8 outbound trunks into a route with priority + per-leg timeout. Primary fails over to secondary within seconds. The route gets its own prefix in the 9500–9999 pool; campaigns bind to that.

Self-serve diagnostics

Per-trunk Diagnose button runs four checks in parallel: PJSIP endpoint state, a SIP OPTIONS handshake at the carrier, TCP/5060 reachability for each published carrier IP, and the last 50 dial attempts through this trunk in the past 7 days. The verdict card translates SIP response codes into action items — Twilio 403 maps to "add this IPv4 to your Twilio IP ACL" with a deep link into the right console page. Same treatment for Telnyx, Bandwidth, Skyetel. No SSH session, no support ticket.

Live SIP trace

A 10/30/60-second toggle that turns on Asterisk's PJSIP logger, captures every SIP frame touching the trunk, filters to the relevant endpoint, and hands you back a copyable trace. The exact wire format your carrier support team asks for, without you SSHing anywhere. Capped + auto-purged after 7 days.

No carrier markup

We make money on the server, not your minutes. If a SIP vendor offers you a better rate, you switch carriers in 10 minutes without leaving us.

Carrier IP allowlist auto-synced

Partner carriers (Twilio, Bandwidth, Telnyx, Skyetel and others) publish IP ranges. We pull the lists daily and update your iptables ACCEPT chain — your trunk does not break the day a carrier rotates infrastructure.

pjsip.conf + extensions.conf snippet for a Twilio outbound trunk. Templated from the partner you pick, with the 4-digit prefix auto-allocated so VICIdial campaigns bind cleanly. You never edit this by hand.

FAQ

Questions worth answering

Your SIP carrier. Your prefix. Your trunk.

Start the trial. Bring any PJSIP-speaking carrier; we render the config from the nine-template menu. Auto-allocated dial prefix, failover routes, diagnose button on every trunk.

All features