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

HP Poly Edge E400: dual displays, one expansion module and PVOS evidence

Keep 14 physical keys, main and secondary pagination, one supported expansion module, wired-only networking and PVOS state 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. Model label, product number, radio hardware, physical keys, paginated assignments, SIP identities, feature keys, expansion-module positions, power source, provisioning owner, installed firmware, registration, signaling, media and accepted call behavior remain separate evidence. No phone, label, hardware revision, firmware image, checksum, configuration, Poly Lens tenant, provisioning server, switch port, PoE source, Ethernet path, Wi-Fi network, Bluetooth accessory, expansion module, headset, SIP account, FreePBX or Asterisk system, 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 release documentation. Those records do not establish local inventory, remaining support period, provider approval, compatibility or the build installed on a particular phone.

Edge E400: manufacturer-sourced facts
SpecificationDocumented value
Exact identityEdge E400; current HP data sheet c08701844. Confirm product number, region and label on the actual unit Source ↗
Displays and controls3.5-inch primary display plus secondary display; 8 primary and 6 secondary physical line keys Source ↗
Pagination boundaryPrimary keys can map 32 positions across four pages; secondary keys can map 12 positions across two pages Source ↗
Radio boundaryNo Bluetooth and no Wi-Fi on E400 Source ↗
Expansion supportOne Poly Edge E Expansion Module is supported; one module provides up to 66 additional assignments across three pages Source ↗
Network and USBTwo Gigabit Ethernet ports and one USB-C port are documented; module, headset and storage loads share the installed power design Source ↗
Current release recordHP lists PVOS 8.6.1 released August 2026; installed and approved state require local evidence Source ↗
Operator boundaryKeys and module positions can hold lines or features; they do not establish SIP identities, monitored users or call capacity Source ↗

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

Count the E400 control surfaces before assigning roles

The E400 has two displays, eight physical keys beside the primary display and six beside the secondary display. PVOS can paginate the primary positions across four pages and the secondary positions across two.

Keep physical keys, visible pages, assignments, SIP identities, monitored contacts and simultaneous calls as different quantities.

Keep the E400 wired-only radio boundary exact

HP's model matrix lists no Bluetooth and no Wi-Fi for E400. Record the exact label and do not borrow E450 radio features. Verify PoE or local power, Ethernet, VLAN, addressing, DNS, time, provisioning and registration in order.

A family page or saved wireless profile is not evidence of radio hardware.

Treat one expansion module as a separate subsystem

E400 supports one Poly Edge E Expansion Module. The module has 22 physical keys across three pages for up to 66 additional assignments. Preserve module identity, attachment, power, enumeration, firmware, template and every page separately.

Do not convert 66 feature positions into 66 registrations or calls.

Budget phone, USB-C and module together

The phone and module power demand share the installed PoE or approved local-power design. Inventory the USB-C headset, storage device or module, switch budget and cable path. An underpowered or unenumerated module is not a line-template problem.

Power, USB detection, module firmware and stable page operation each need evidence.

Bind PVOS and provisioning to the actual operator layout

HP lists PVOS 8.6.1 released August 2026. Preserve the current build, authoritative configuration owner, requested file, apply event, effective key layout, module state, registration and completed calls separately.

A current release record does not authorize an update or prove that an operator layout will survive it.

Pilot the representative E400 operator workflow

Test every required primary, secondary and module page; BLF or presence state; transfer; hold; park; directory access; headset routing; two-way media; DTMF; power recovery; restart persistence and the approved emergency workflow.

No E400 phone, module, accessory, 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 →
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. Model label, product number, radio hardware, physical keys, paginated assignments, SIP identities, feature keys, expansion-module positions, power source, provisioning owner, installed firmware, registration, signaling, media and accepted call behavior remain separate evidence. No phone, label, hardware revision, firmware image, checksum, configuration, Poly Lens tenant, provisioning server, switch port, PoE source, Ethernet path, Wi-Fi network, Bluetooth accessory, expansion module, headset, SIP account, FreePBX or Asterisk system, registration, packet, call, media stream, emergency workflow, price, inventory, compatibility, certification result, support entitlement or vendor response was inspected or tested

Poly Edge E300, E320, E400 or E450 has wrong keys, radio, expansion or firmware

Find the first mismatch across exact model, physical and paginated keys, wired or wireless path, accessory power, expansion module, provisioning and installed PVOS.

Read guide →