Why Bulk Phone Insert Needs a Manual Conf File Rebuild

You run Bulk Phone Insert, the page says success, and yet none of your new phones can register. Nothing is broken and you did not make a mistake in the form - the reason is almost always the same: submitting the form does not rebuild your Asterisk config. It is one of the most common surprises for admins new to the bulk tools. This post explains the gap and how to close it.

Database rows are not live config

When you submit the form, VICIdial writes a phone row for each Extension into its database. That row is the record of intent - it says this phone should exist, with this password, on this server. But Asterisk does not read VICIdial's database directly to authenticate registrations. It reads its own Conf file entries on disk. Until those files are regenerated from the database, Asterisk has no idea the new phones exist, so Phone registration for a SIP (Session Initiation Protocol) or PJSIP device fails with an authentication error - even though the credentials in the database are perfectly correct.

This split is by design. Rebuilding config touches the running telephony engine, and doing it automatically on every bulk submit could disrupt live calls mid-shift. Imagine inserting a few hundred phones during business hours and having the dialer reload its config under active agents - that is the scenario VICIdial avoids by leaving the timing to you. You get to choose a quiet moment to apply the change.

The two-step picture

flowchart LR
  A[Submit Bulk Phone Insert] --> B[Phone rows written to DB]
  B --> C{Conf rebuilt?}
  C -->|No| D[Asterisk unaware]
  D --> E[Registration fails]
  C -->|Yes - manual rebuild| F[Conf files regenerated]
  F --> G[Asterisk reloads]
  G --> H[Phones register]

How to trigger the rebuild

You have two places to do this, and either one works:

1. From System Settings, trigger a conf file rebuild for the affected server.
2. Or open the Modify Server page for each server you inserted phones onto and rebuild there.

Either path regenerates the SIP peer entries and prompts Asterisk to pick them up. The rebuild runs as part of the normal keepalive and config cycle, so it is not instant - give it a short moment to complete, then test a registration from one of the new phones before assuming the whole batch is good. If that first phone registers, the rest in the same run almost certainly will too.

Multi-server batches

Bulk Phone Insert can populate phones across several servers in one submit. Each of those servers needs its own rebuild - a rebuild on one box does not regenerate config on the others. If you listed three server IPs, plan on three rebuilds, or rebuild each from its Modify Server page.

This step matters no matter which fields you set. Whether you pointed phones at an Agent-nodial context or flipped them to Webphone mode, the new config is inert until the rebuild runs.

Related reading

For the full walkthrough of the page that creates these phones, see how to bulk insert phones across servers. And for the broad map of every batch admin utility, read our VICIdial admin bulk tools guide.

On a managed VICIfast box, conf rebuilds and registration are handled for you, with a branded dialer live in under 40 seconds. See VICIfast pricing.