VoIP.infoThe independent guide to business communications.
VoIP.info Guide

DHCP options for phone provisioning

Interpret provisioning discovery by model instead of assuming option 66 means the same thing on every phone.

Reviewed 2026-10-24Vendor-neutral workflow; exact parameters and precedence depend on model and firmwareIntermediateDocumentation based · not lab tested

DHCP can advertise more than an address

A phone can learn network parameters and a provisioning hint from DHCP. Option 66 is defined as a TFTP server name, but manufacturers may interpret supported values or URLs differently. Vendor-specific options and model settings can also affect discovery. A DHCP server's configuration screen is not evidence of what reached the phone. Capture the actual response on the phone's network and compare it with the exact firmware's provisioning documentation.

Follow discovery precedence

Record any manually configured server, manufacturer redirection assignment and DHCP provisioning option. Determine which one wins for this model. A phone that keeps returning to an old provider may be following a cloud assignment rather than ignoring the new DHCP server. If the device moves to a voice VLAN after LLDP-MED discovery, inspect DHCP on the resulting VLAN too. The initial untagged lease may not be the lease used for final provisioning. Confirm DNS and the provisioning server are reachable from the phone's eventual subnet.

Change a bounded scope

Test one reservation, vendor class or isolated deployment scope where supported. Avoid advertising a phone provisioning URL indiscriminately to every device on a mixed network. Never treat a MAC address in a filename as authentication. After the phone downloads its configuration, check the applied revision and make an authorized test call. Then renew or reboot to confirm the same source remains authoritative. Keep the old scope configuration available for rollback and document any model-specific exceptions rather than silently relying on undocumented discovery behavior.

Keep Grandstream discovery separate from successful apply

The GRP2613/GRP2615 diagnostic treats a DHCP or LLDP result, requested URL, downloaded artifact, applied configuration and rebooted state as separate evidence.

Keep Edge E discovery separate from apply

The E100/E220 workflow separates LLDP or DHCP discovery, requested file, downloaded configuration, applied values and post-reboot state.

Treat DHCP option 42 as an input to endpoint time selection

The wrong-time diagnostic follows the offered option, accepted lease, effective setting, resolved server and actual exchange.

Watch the explanation

How DHCP Works // DHCP EXPLAINEDChris Greer · 9:56 · Conceptual

Follows an initial DHCP exchange through packet fields, requested options and server replies. Useful when a phone receives an address but the wrong network settings.

Read applicability and editorial notes →
Watch this video here

An IPv4 initial-acquisition walkthrough from 2022; it does not cover every renewal or DHCPv6 flow. Review used the available transcript and primary references; audio and screen readability remain unverified.

Open on YouTube ↗

The player loads only when you choose Watch here. Playback uses YouTube’s privacy-enhanced embed; YouTube processes playback data.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Guide

DHCP for IP phones

Check address assignment before treating a handset startup problem as SIP failure.

Read guide →
Guide · Vendor-neutral workflow; exact parameters and precedence depend on model and firmware

LLDP and LLDP-MED for voice endpoints

Distinguish neighbor discovery and advertised voice policy from actual switch forwarding and access control.

Read guide →
Guide · Vendor-neutral workflow; exact parameters and precedence depend on model and firmware

Zero-touch provisioning and manufacturer ownership

Understand redirection, cloud management and why a factory reset may not release a phone from a provider.

Read guide →
Device reference · Current Grandstream GRP2613(W) and GRP2615 product material plus the GRP261x user, administration, VPK and firmware records were reviewed October 23, 2026. Product label, hardware revision, exact model suffix, installed firmware, eligible image family, transition image, certificates, backup, provisioning owner, downloaded configuration, effective keys, network path, registration and completed call remain separate evidence. Grandstream's current guide identifies revision-1 hardware as legacy, excludes legacy hardware from firmware 1.0.15.x and lists a narrower currently supported hardware set, while live product pages still describe later product and hardware capabilities. This mixed documentation does not establish current stock, regional sale, certification, compatibility or a remaining support period. No phone, label, hardware revision, firmware image, downgrade, configuration, backup, certificate, GDMS tenant, provisioning server, switch port, PoE source, Ethernet path, WLAN, VLAN, Bluetooth accessory, expansion module, SIP account, PBX, registration, packet, call, media stream, price, availability, compatibility or support response was inspected or tested

Grandstream GRP2613 and GRP2613W: hardware, keys and firmware boundaries

Separate the wired GRP2613 from the GRP2613W radio model, then bind accounts, VPK pages and firmware to the exact label and hardware revision.

Carrier-grade desk phone
Grandstream maintains a live combined product page and current family documentation. The current guide labels revision-1 hardware as legacy and not eligible for 1.0.15.x, while its currently supported list omits GRP2613 and GRP2613W. Confirm the exact suffix, part number, hardware revision, regional status and supported firmware with Grandstream or an authorized channel before purchase or change.

Read guide →
Grandstream GRP2615Product image: Grandstream Networks
Device reference · Current Grandstream GRP2613(W) and GRP2615 product material plus the GRP261x user, administration, VPK and firmware records were reviewed October 23, 2026. Product label, hardware revision, exact model suffix, installed firmware, eligible image family, transition image, certificates, backup, provisioning owner, downloaded configuration, effective keys, network path, registration and completed call remain separate evidence. Grandstream's current guide identifies revision-1 hardware as legacy, excludes legacy hardware from firmware 1.0.15.x and lists a narrower currently supported hardware set, while live product pages still describe later product and hardware capabilities. This mixed documentation does not establish current stock, regional sale, certification, compatibility or a remaining support period. No phone, label, hardware revision, firmware image, downgrade, configuration, backup, certificate, GDMS tenant, provisioning server, switch port, PoE source, Ethernet path, WLAN, VLAN, Bluetooth accessory, expansion module, SIP account, PBX, registration, packet, call, media stream, price, availability, compatibility or support response was inspected or tested

Grandstream GRP2615: hardware revision, VPK, Wi-Fi and firmware boundaries

Treat GRP2615 account, key, Wi-Fi 6, GBX20 and firmware claims as hardware- and version-specific before using it at a busy call-handling desk.

Carrier-grade desk phone
Grandstream maintains a live product page and current family documentation, but the October 12 guide labels revision-1 hardware as legacy and excludes GRP2615 from its currently supported hardware list. The product page and datasheet describe later hardware-specific Wi-Fi 6 and extension-module capabilities. Confirm part number, hardware revision, regional status and supported firmware before purchase or change.

Read guide →
Troubleshooting · Current Grandstream GRP2613(W) and GRP2615 product material plus the GRP261x user, administration, VPK and firmware records were reviewed October 23, 2026. Product label, hardware revision, exact model suffix, installed firmware, eligible image family, transition image, certificates, backup, provisioning owner, downloaded configuration, effective keys, network path, registration and completed call remain separate evidence. Grandstream's current guide identifies revision-1 hardware as legacy, excludes legacy hardware from firmware 1.0.15.x and lists a narrower currently supported hardware set, while live product pages still describe later product and hardware capabilities. This mixed documentation does not establish current stock, regional sale, certification, compatibility or a remaining support period. No phone, label, hardware revision, firmware image, downgrade, configuration, backup, certificate, GDMS tenant, provisioning server, switch port, PoE source, Ethernet path, WLAN, VLAN, Bluetooth accessory, expansion module, SIP account, PBX, registration, packet, call, media stream, price, availability, compatibility or support response was inspected or tested

Grandstream GRP2613 or GRP2615 has wrong keys, network or firmware

Find the first mismatch in exact model, hardware revision, firmware family, discovery path, authoritative template, applied VPK layout, VLAN, registration or PBX feature state.

Read guide →
Device reference · Current HP Poly Edge E family material, PVOS 8.2.1 administration and user guides, flexible-line-key profile, PVOS 8.0.0 capability matrix, PVOS 8.6.1 release record, specification sheet and safety notices were reviewed October 23, 2026. The current support index lists PVOS 8.6.1 with an August 2026 release date, while detailed operational claims here remain tied to the cited guides and release records. Model label, software model, installed build, approved upgrade path, configuration owner, downloaded file, effective line-key assignment, network path, registration, headset path, emergency location and completed call remain separate evidence. No phone, firmware image, backup, configuration, Poly Lens tenant, provisioning server, switch port, PoE source, Ethernet path, VLAN, Bluetooth accessory, wired or EHS headset, SIP account, PBX, registration, packet, call, media stream, emergency call, price, availability, compatibility, certification, support entitlement or vendor response was inspected or tested

HP Poly Edge E100: line keys, wired headset and firmware boundaries

Keep two physical keys, eight paginated assignments, wired networking and headset paths separate from SIP identities, PBX state and family-level radio claims.

Entry-level IP desk phone
HP maintains a live Edge E family page, model-specific manuals and a current PVOS 8.6.1 release record. Those records do not establish local stock, remaining support period, provider approval or the build installed on a particular phone.

Read guide →
Poly Edge E220Product image: HP / Poly
Device reference · Current HP Poly Edge E family material, PVOS 8.2.1 administration and user guides, flexible-line-key profile, PVOS 8.0.0 capability matrix, PVOS 8.6.1 release record, specification sheet and safety notices were reviewed October 23, 2026. The current support index lists PVOS 8.6.1 with an August 2026 release date, while detailed operational claims here remain tied to the cited guides and release records. Model label, software model, installed build, approved upgrade path, configuration owner, downloaded file, effective line-key assignment, network path, registration, headset path, emergency location and completed call remain separate evidence. No phone, firmware image, backup, configuration, Poly Lens tenant, provisioning server, switch port, PoE source, Ethernet path, VLAN, Bluetooth accessory, wired or EHS headset, SIP account, PBX, registration, packet, call, media stream, emergency call, price, availability, compatibility, certification, support entitlement or vendor response was inspected or tested

HP Poly Edge E220: line keys, Bluetooth and firmware boundaries

Keep four physical keys, sixteen paginated assignments and E220 Bluetooth separate from Wi-Fi, SIP identities, PBX state and tested headset control.

Entry-level Bluetooth IP desk phone
HP maintains a live Edge E family page, model-specific manuals and a current PVOS 8.6.1 release record. Those records do not establish local stock, remaining support period, provider approval or the build installed on a particular phone.

Read guide →
Troubleshooting · Current HP Poly Edge E family material, PVOS 8.2.1 administration and user guides, flexible-line-key profile, PVOS 8.0.0 capability matrix, PVOS 8.6.1 release record, specification sheet and safety notices were reviewed October 23, 2026. The current support index lists PVOS 8.6.1 with an August 2026 release date, while detailed operational claims here remain tied to the cited guides and release records. Model label, software model, installed build, approved upgrade path, configuration owner, downloaded file, effective line-key assignment, network path, registration, headset path, emergency location and completed call remain separate evidence. No phone, firmware image, backup, configuration, Poly Lens tenant, provisioning server, switch port, PoE source, Ethernet path, VLAN, Bluetooth accessory, wired or EHS headset, SIP account, PBX, registration, packet, call, media stream, emergency call, price, availability, compatibility, certification, support entitlement or vendor response was inspected or tested

Poly Edge E100 or E220 has wrong lines, headset, network or firmware

Find the first mismatch in exact model, physical and paginated line keys, configuration precedence, wired network, E220 Bluetooth, registration or approved PVOS path.

Read guide →
Provisioning guide · Current NTP standards, best-current-practice, DHCP-option, Network Time Security, Yealink, Grandstream and Cisco endpoint documentation was reviewed October 24, 2026. UTC synchronization, displayed local time, time-zone and daylight-saving policy, manual time, DHCP options, configured servers, DNS answers, selected source, last successful synchronization, authenticated-time support, certificate validity, log timestamps and scheduled behavior remain separate evidence. Vendor examples, defaults, intervals and supported controls are model- and firmware-specific documentation rather than proof of an installed setting or result. No phone, base, PBX, DHCP server, DNS resolver, NTP server, NTS service, key, certificate, firewall, packet, provisioning job, scheduled task, call, alert, clock offset, availability, compatibility or support response was inspected or tested

IP phone NTP, time-zone and daylight-saving evidence

Separate clock synchronization from displayed local time, DHCP overrides, manual settings, authenticated time, certificate validity, logs and scheduled endpoint behavior.

Read guide →
Troubleshooting · Current NTP standards, best-current-practice, DHCP-option, Network Time Security, Yealink, Grandstream and Cisco endpoint documentation was reviewed October 24, 2026. UTC synchronization, displayed local time, time-zone and daylight-saving policy, manual time, DHCP options, configured servers, DNS answers, selected source, last successful synchronization, authenticated-time support, certificate validity, log timestamps and scheduled behavior remain separate evidence. Vendor examples, defaults, intervals and supported controls are model- and firmware-specific documentation rather than proof of an installed setting or result. No phone, base, PBX, DHCP server, DNS resolver, NTP server, NTS service, key, certificate, firewall, packet, provisioning job, scheduled task, call, alert, clock offset, availability, compatibility or support response was inspected or tested

IP phone time is wrong, scheduled behavior drifts or certificates fail

Find the first mismatch across DHCP, DNS, NTP reachability, source selection, UTC, time zone, daylight saving, manual overrides, certificate validity and device scheduling.

Read guide →