Phone Downloads Config but Won't Take It — Provisioning Failures

Provisioning failures sit one layer below registration problems: the phone boots and has network, but never fetches or applies its Signal configuration. Four causes account for nearly all cases — a wrong MAC in the portal, a model mismatch, a phone still pointed at a previous provider, or a local DHCP server overriding the provisioning URL.

1. Wrong MAC entry

The portal serves configuration keyed to the exact MAC. Compare the label on the phone to the portal entry character by character — 0 vs O and transposed pairs are the classics. The portal normalizes case and separators, but it cannot fix a wrong digit.

2. Model mismatch

A device entered as the wrong model receives a template its firmware may reject — symptoms range from ignored line keys to boot loops. VVX 400 vs 401 and Edge E350 vs E450 are distinct models; check the label, not memory.

3. Phone locked to a previous provider

Phones bought used or moved from another service often have a custom provisioning URL saved — they boot, contact the old server, and never ask Signal for anything. Factory-reset the phone (procedure per family: VVX, Edge, Yealink), which clears the stored URL.

4. DHCP option 66 conflicts

If your DHCP server advertises option 66/67 (TFTP/provisioning server) for another system, phones may obey it instead of their default. Either remove the option for voice VLANs/scopes or set it to Signal's provisioning URL. Mixed-vendor offices with a legacy PBX are the usual scene of this crime.

Verifying the fix

Watch the portal's Last Seen for the device while the phone boots: a timestamp appearing means provisioning succeeded; registration follows within a minute. Still nothing? Capture the phone's status-menu provisioning server value and open a case with the MAC and model.

Related articles

• How auto-provisioning works
• Phone won't register