Dial prefix invalid for campaign
Campaign is configured with a dial prefix that doesn't match any Asterisk dialplan extension, every dial fails instantly.
Symptoms
- •Campaign dials 0 calls despite full hopper and ready agents
- •Asterisk CLI shows `Extension does not match pattern`
- •`asterisk -rvvv` during a dial attempt shows the failure
Common causes
- •Campaign `dial_prefix` field doesn't match an include in extensions.conf
- •Someone edited extensions.conf and didn't reload
- •Dialplan context was renamed without updating campaign config
How to fix it
- 1Verify campaign dial_prefix matches an active dialplan extension
- 2Reload dialplan: `asterisk -rx 'dialplan reload'`
- 3In Asterisk CLI: `dialplan show` to confirm the extension exists
- 4Fix the campaign or fix the dialplan so they match
VICIPanel validates dial prefix against the live dialplan at campaign save time, you can't save a campaign with an orphan prefix.
Related issues
More Asterisk errors
Asterisk not running on the dialer box
The Asterisk process is dead, no calls can be placed or received until it's restarted.
Campaign dial level stuck at zero
Campaign auto-dial level drops to 0 and never recovers, dialing stops.
Hopper empty, dialing paused
The pre-dial lead cache is empty and the fill cron hasn't run, dialing stops until new leads enter the hopper.
VICIdial worker process not running
One of VICIdial's background daemons (AST_send_listen, AST_update, etc.) has died.
Stop troubleshooting. Start operating.
VICIPanel's health dashboard catches most of these issues before they impact your agents — with plain-English diagnostics and one-click remediation.