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

Provisioning templates and configuration ownership

Prevent configuration drift by separating shared policy, model settings and per-device identity.

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

Build a small hierarchy

Keep shared service settings, model-specific keys and per-device identities distinguishable. A common template might define time service and SIP transport; a model layer can define supported line keys; an individual assignment supplies the intended user's account. The phone's actual merge order controls which value wins. For example, Grandstream documents layered custom configuration support on specified GRP firmware, with later files overriding earlier ones. Do not extend that rule to every manufacturer or older release without checking its documentation.

Discovery, authority and applied configuration
DHCP or manufacturer redirection points a phone toward the chosen provisioning authority. The authority combines model policy with the individual identity, serves an authorized configuration and the device applies it.

Choose one configuration owner. A discovery hint or MAC-based filename is not authentication; verify both file access and the resulting device behavior.

Review the generated result

Validate syntax and escaping, then inspect the fully resolved configuration for a pilot device. A template can be syntactically valid while assigning the wrong account, trunk permissions or display label. Keep secrets out of ordinary source-control history and review artifacts. Record a template revision and a change reason. Compare the intended result with the phone's applied settings after provisioning. Define which local user changes are permitted and whether the next management cycle preserves or overwrites them.

Detect drift without creating a fight

If a setting repeatedly changes back, inspect all management sources before editing it again. Cloud management, PBX templates and manual configuration can each be involved. Choose the authoritative owner and remove the unintended competing assignment. Roll out changes by hardware and firmware cohort. Verify a representative phone from each group, then expand. Retain the previous known-good template and the procedure to deliver it to a phone that can no longer reach the usual server. A rollback file is of little use if the failed change removed its delivery path.

Bind a Grandstream template to exact model and revision

A GRP2613, GRP2613W and GRP2615 can require different model, radio, account and firmware assumptions. The device diagnostic checks the matched template before overwriting local state.

Bind Poly Edge E templates to exact software models

Use EdgeE100 with 3111-86980-001 and EdgeE220 with 3111-86990-001 as exact matching evidence. The paired diagnostic checks precedence and flexible-key overrides.

Split HT80x V2 and HT81x V2 templates deliberately

HT802 V2 and HT818 V2 differ in port count, network topology and firmware binary family. Use the paired diagnostic before applying a family template.

Watch the explanation

Video Guide - How to Add and Provision Device - GDMSGrandstreamNetworks · 5:22 · Version-specific

Shows the difference between claiming a device, changing one endpoint and applying a model or site template. Useful for understanding configuration scope before a fleet rollout.

Read applicability and editorial notes →
Watch this video here

Grandstream’s 2023 GDMS interface. Verify the current console, supported models and firmware before following clicks. 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.

Grandstream UCM630x: provision a GRP phone with Zero ConfigVoIP knowledge · Version-specific

Follow the discovery of a GRP phone, model-package preparation and assignment of a PBX extension. The example connects the PBX’s provisioning action with the phone’s registration result, making it a useful companion to understanding what automatic provisioning actually delivers.

Read applicability and editorial notes →
Watch this video here

Local UCM630x Zero Config workflow with a GRP2615. This is distinct from GDMS cloud provisioning, and menu locations vary by UCM release. 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.

Explore all 6 related videos →

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 · Vendor-neutral workflow; exact parameters and precedence depend on model and firmware

Phone firmware deployment and rollback planning

Upgrade a mixed endpoint estate without assuming every model or intermediate release behaves alike.

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

Provisioning credentials and per-device access

Keep a configuration service from becoming a directory of working SIP passwords.

Read guide →
Troubleshooting · Current Sangoma End Point Manager administration, supported-device, basefile, firmware and support-scope documentation reviewed October 1, 2026; no PBX, module, phone, file, credential, firmware or provisioning exchange was inspected or tested

Phone provisioning succeeds but settings stay wrong

Trace device identity, template ownership, generated artifacts, transport, parsing, activation and later overwrite without treating one successful download as complete provisioning.

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 →
Device reference · Grandstream exact-model HT802 V2 and HT818 V2 product pages and datasheets, current HT80x V2 and HT81x V2 administration and user guides, and firmware 1.0.15.3 release notes dated September 17, 2026 were reviewed October 24, 2026. Exact V2 model, hardware, component versions, firmware binary family, network topology, FXS port, profile, identity, registration, hunting role, analog behavior, signaling, media, fax mode, provisioning state and accepted service remain separate evidence. Published firmware and management capabilities do not prove the installed build, provider approval, successful change, compatibility, capacity or availability. No adapter, analog device, cable, line condition, network, VLAN, router, account, PBX, packet, call, fax, image, checksum, price, inventory, support entitlement or vendor response was inspected or tested

Grandstream HT802 V2: two FXS ports, single Ethernet and firmware identity

Keep two analog ports and profiles separate from the single 10/100 network interface, effective provisioning, registration, media and the HT80x V2 firmware image.

Two-port analog telephone adapter
Grandstream maintains an exact-model product page, current HT80x V2 guides and current V2 firmware records. Those records do not establish local inventory, global remaining support, provider approval or the build installed on an individual adapter.

Read guide →
Device reference · Grandstream exact-model HT802 V2 and HT818 V2 product pages and datasheets, current HT80x V2 and HT81x V2 administration and user guides, and firmware 1.0.15.3 release notes dated September 17, 2026 were reviewed October 24, 2026. Exact V2 model, hardware, component versions, firmware binary family, network topology, FXS port, profile, identity, registration, hunting role, analog behavior, signaling, media, fax mode, provisioning state and accepted service remain separate evidence. Published firmware and management capabilities do not prove the installed build, provider approval, successful change, compatibility, capacity or availability. No adapter, analog device, cable, line condition, network, VLAN, router, account, PBX, packet, call, fax, image, checksum, price, inventory, support entitlement or vendor response was inspected or tested

Grandstream HT818 V2: eight FXS ports, two profiles and routed topology

Keep eight analog ports distinct from two SIP profiles, dual-Gigabit routing, hunting, line-test evidence, provisioning and the HT81x V2 firmware image.

Eight-port FXS gateway with integrated NAT router
Grandstream maintains an exact-model product page, current HT81x V2 guides and current V2 firmware records. Those records do not establish local inventory, global remaining support, provider approval or the build installed on an individual gateway.

Read guide →
Troubleshooting · Grandstream exact-model HT802 V2 and HT818 V2 product pages and datasheets, current HT80x V2 and HT81x V2 administration and user guides, and firmware 1.0.15.3 release notes dated September 17, 2026 were reviewed October 24, 2026. Exact V2 model, hardware, component versions, firmware binary family, network topology, FXS port, profile, identity, registration, hunting role, analog behavior, signaling, media, fax mode, provisioning state and accepted service remain separate evidence. Published firmware and management capabilities do not prove the installed build, provider approval, successful change, compatibility, capacity or availability. No adapter, analog device, cable, line condition, network, VLAN, router, account, PBX, packet, call, fax, image, checksum, price, inventory, support entitlement or vendor response was inspected or tested

Grandstream HT802 V2 or HT818 V2 has missing ports, wrong network mode or failed firmware

Find the first mismatch in exact V2 identity, expected port count, single-interface versus routed topology, profile mapping, provisioning or firmware binary family.

Read guide →