Where are my trunks in VICIdial admin?

If you opened VICIdial admin → Admin → Carriers and saw nothing, that's expected. VICIfast doesn't write to the vicidial_carriers table. Outbound routing lives entirely in our managed file at /etc/asterisk/vicifast-trunks-dialplan.conf, included from your extensions.conf.

Why we don't write the Carriers table

VICIdial's Carriers tab was built for hand-managed Asterisk installs where the only way to inject a dialplan entry was through admin's textarea. We render the dialplan file directly from the platform DB, so the Carriers row would just duplicate state — and a second source of truth is how customer-built configs go wrong.

What to use instead

• Add / edit / disable trunks: VICIfast dashboard → your server → Manage Trunks.

• Bind a campaign to a trunk: in Manage Trunks click Link campaigns next to the trunk. We set vicidial_campaigns.dial_prefix to the trunk's 4-digit prefix.

• Build a failover route: same modal, Failover routes section. Routes get their own prefix in the 9500–9999 pool.

• TCPA / BLA per-trunk: the TCPA button on each trunk row.

If you'd rather not use the dashboard

You can edit /etc/asterisk/vicifast-trunks.conf and /etc/asterisk/vicifast-trunks-dialplan.conf directly on your box — but any change you make there will be overwritten the next time you save anything in Manage Trunks. The platform owns those files end-to-end. If you need a custom dialplan for a specific trunk, the Modify trunk → Custom dialplan path (Phase K4) preserves your edits across applies.

Migrating from a pre-K1 install

Test boxes provisioned before Phase K1 had trunks installed via inline edits to pjsip.conf. An admin can trigger a one-shot migration from /admin/servers/[id] → Migrate trunks that:

1. strips the legacy ;;; vicifast-trunk-begin/end regions from your pjsip.conf

2. writes the two managed files from current platform state

3. reloads PJSIP + dialplan

It's idempotent — safe to run on a box that's already migrated.