When to use Conf Override Settings on a phone

Most VICIdial phones do fine with default settings or a shared template. Now and then one device needs something special — a custom audio rule, a non-standard context, a tweak the rest of the fleet shouldn't get. That's what the Conf Override Settings field is for. It's the escape hatch for a single phone.

Conf Override Settings is a free-text field where you paste the raw Conf file entries you want for this one phone. When it's populated, VICIdial drops those lines straight into the generated Asterisk config for the device instead of using the defaults.

The two conditions

The field only works when two things are true. First, the Template ID must be set to none — a template always wins, so an assigned template makes the override do nothing. Second, generate_VICIdial_conf for the phone's server must be set to Y, otherwise the box never writes the device's SIP peer block at all.

flowchart TD
  A[Conf Override filled] --> B{Template ID is none}
  B -->|No| X[Override ignored]
  B -->|Yes| C{generate conf is Y}
  C -->|No| Y[Block not written]
  C -->|Yes| D[Override lines used]
  D --> E[Generate conf file]
  E --> F[Phone registers]

When it's the right tool

Use the override for genuine one-offs. A lab device that needs a specific Codec, a phone that must sit in a different context than its peers, or a quick test you don't want to bake into a shared template. Anything that more than one phone needs belongs in a template instead, so you maintain it in one place.

• Good fit: a single device with a unique requirement.
• Bad fit: settings several phones share — use a template.
• Never include the bracketed extension header line.

After you fill the field, save the phone and let the config regenerate. The override lines won't reach Asterisk until that regeneration runs, so a change you typed can sit dormant until the next cycle. If you need it live immediately, trigger a rebuild rather than waiting. Then confirm the device still registers — a typo in the override block can leave the phone unable to come back online, which is exactly the kind of failure templates are meant to avoid for shared devices.

One more habit worth keeping: write down why a given phone has an override. Six months later, a one-off block with no explanation looks like a mistake, and someone will be tempted to delete it. A short note on the entry saves a future debugging session.

To see how this field sits next to Template ID and the rest of the phone settings, read the phones and aliases guide. Since the override depends on the right server IP being set, setting the phone's server IP is worth a look too.

Hand-editing raw config is exactly the kind of footgun a managed setup removes. VICIfast keeps conf generation and overrides sane for you — see our pricing.