VoIP.infoThe independent guide to business communications.
VoIP.info Device reference

HP Poly Edge E500: 12 keys, wired network, two modules and power evidence

Keep 12 physical keys, 48 paginated assignments, 34 supported registrations, wired-only networking, two expansion modules and their power path separate.

Reviewed 2026-10-24Current HP Poly Edge E family, exact-model data sheets, PVOS 8.5.0 administration guide, PVOS 8.6.0 user guide, PVOS 8.6.x release record, model setup hubs, quick-start guides and HP-hosted radio matrix were reviewed October 24, 2026. HP lists PVOS 8.6.1 with an August 2026 release date, but a current release record is not proof of the installed image, provider approval, completed update or resolved deployment. Exact model, software model, physical keys, paginated assignments, supported registrations, radio hardware, expansion attachment, power source, provisioning owner, installed firmware, signaling, media and accepted call behavior remain separate evidence. No phone, label, hardware revision, firmware image, configuration, Poly Lens tenant, provisioning server, switch port, PoE or PoE+ source, AC adapter, Ethernet path, Wi-Fi network, Bluetooth accessory, NFC workflow, expansion module, USB device, headset, SIP account, PBX, registration, packet, call, media stream, emergency workflow, price, inventory, compatibility, certification result, support entitlement or vendor response was inspected or testedIntermediateDocumentation based · not lab tested

Documented specifications

Open IP Phone Compare →

HP Poly · HP maintains a live Edge E family page, exact-model data sheet, setup hub and current PVOS documentation. Those records do not establish local inventory, remaining support period, provider approval, compatibility or the build installed on a particular phone.

Edge E500: manufacturer-sourced facts
SpecificationDocumented value
Exact identityEdge E500; software model 3111-87855-001. Confirm product number, region and label on the actual unit Source ↗
Display and controls5-inch color IPS display, secondary display and 12 physical line keys Source ↗
Keys and registrations12 keys expose up to 48 positions with pagination; E500 Series supports 34 registrations Source ↗
Radio boundaryNo Bluetooth and no Wi-Fi on E500; NFC is not either radio path Source ↗
Expansion supportUp to two Edge E expansion modules; each has 22 physical keys and 66 positions across three pages Source ↗
Pagination with modulesConnecting an expansion module disables host pagination; the first module position follows the 12 host keys Source ↗
Second-module powerA second module requires PoE+ 802.3at or an approved AC adapter Source ↗
Current release recordHP lists PVOS 8.6.1 released August 2026; installed and approved state require local evidence Source ↗

Unlisted fields remain unverified. Platform compatibility and remaining support life require confirmation for the exact ordered model.

Identify the wired E500 exactly

Record the bottom label, product number, software model 3111-87855-001, MAC address and installed PVOS. HP identifies E500 as the wired member without Bluetooth or Wi-Fi. NFC support does not create either radio path.

Do not inherit E550 wireless capabilities from the shared series name.

Separate 12 keys, 48 positions and 34 registrations

Without an expansion module, 12 physical keys can expose up to 48 positions through pagination. PVOS documents 34 supported registrations for E500 Series. These figures describe different layers and neither is concurrent-call capacity.

Record keys, pages, assignments, registrations, monitored targets and active calls independently.

Recalculate the layout when a module is attached

E500 supports up to two Edge E expansion modules. Each module has 22 physical keys and up to 66 assignments across three pages. Connecting a module disables host pagination, so the host contributes 12 positions before the first module.

Do not add 48 paginated host positions to module totals after pagination is disabled.

Prove power before troubleshooting templates

A second expansion module requires PoE+ or an approved AC adapter. Inventory the host, each module, interconnect, USB load, headset and actual power source. Verify boot, enumeration, firmware handling and stable pages before changing key assignments.

A lit module is not proof that its feature is supported by the calling platform.

Bind provisioning and PVOS to the operator layout

HP lists PVOS 8.6.1 released August 2026. Preserve the configuration owner, current and target builds, requested file, apply event, effective host and module layout, registration state, pilot and rollback.

A current release record does not authorize an update or prove that a reception layout survives it.

Pilot the complete E500 operator desk

Test every required host and module page, BLF or presence, headset answer, hold, attended and blind transfer, failed-transfer recovery, directory, DTMF, two-way media, power recovery, restart persistence and the approved emergency workflow.

No E500 phone, module, power source, firmware, platform, registration or call was tested for this reference.

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

Hub

HP Poly phones

Separate desk, cordless and room devices, then verify the exact platform and firmware combination.

Explore topic →
Buying guide · Current Yealink IP phone catalogue, HP Poly Edge E portfolio and Cisco Desk Phone 9800 Series data sheet reviewed October 1, 2026; no phone, accessory, switch, PoE budget, provisioning service, platform, call, emergency workflow, price, stock or compatibility was tested

Choosing an IP phone

Turn each desk role into an exact-model, platform, power, accessory and lifecycle requirement that can be proven before fleet purchase.

Read guide →
Buying guide

Receptionist phones and expansion keys

Evaluate visible colleagues, transfer workflows and fallback coverage.

Read guide →
Buying guide

IP phone headsets and accessories

Check interfaces, call controls and power before purchasing accessories.

Read guide →
Hub · Vendor-neutral endpoint workflow plus Acrobits Cloud Softphone platform provisioning documentation reviewed October 8, 2026; exact parameters and precedence remain product-, service- and deployment-specific and no device or application was tested

Phone provisioning: repeatable endpoint deployment

Build a controlled path from a newly connected phone to the right identity, firmware and calling policy.

Explore topic →
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

PoE for IP phones

Check power standard, port capability, aggregate budget and outage behavior before selecting a switch.

Read guide →
Guide

Voice VLANs

Separate phone traffic operationally while keeping routing, security and QoS responsibilities explicit.

Read guide →
Hub

VoIP security

Reduce PBX exposure, constrain calling permissions and prepare for accountable recovery.

Explore topic →
Guide · FreePBX 17 · Debian 12; Sangoma field reference is explicitly labelled PBX GUI version 13, reviewed September 30, 2026

Register an IP phone with FreePBX: contact and call evidence

Map registrar, SIP identity, authentication and transport without treating a registration indicator as completed-call evidence.

Read guide →
Troubleshooting · Current HP Poly Edge E family, exact-model data sheets, PVOS 8.5.0 administration guide, PVOS 8.6.0 user guide, PVOS 8.6.x release record, model setup hubs, quick-start guides and HP-hosted radio matrix were reviewed October 24, 2026. HP lists PVOS 8.6.1 with an August 2026 release date, but a current release record is not proof of the installed image, provider approval, completed update or resolved deployment. Exact model, software model, physical keys, paginated assignments, supported registrations, radio hardware, expansion attachment, power source, provisioning owner, installed firmware, signaling, media and accepted call behavior remain separate evidence. No phone, label, hardware revision, firmware image, configuration, Poly Lens tenant, provisioning server, switch port, PoE or PoE+ source, AC adapter, Ethernet path, Wi-Fi network, Bluetooth accessory, NFC workflow, expansion module, USB device, headset, SIP account, PBX, registration, packet, call, media stream, emergency workflow, price, inventory, compatibility, certification result, support entitlement or vendor response was inspected or tested

Poly Edge E350, E500 or E550 has wrong radio, keys, expansion or power

Find the first mismatch across exact model, keys and pagination, registrations, Ethernet or Wi-Fi, Bluetooth, module attachment, power, provisioning and installed PVOS.

Read guide →