VoIP.info Device reference

Snom D815WB: Wi-Fi, Bluetooth, SmartLabel and expansion boundaries

Evaluate the D815WB without confusing its colour variant, SIP identities, simultaneous calls, SmartLabel pages, D8C expansion, radio paths or published security capabilities.

Reviewed 2026-10-09Snom's live D815WB product page, datasheet version 26 August 2026, safety instructions version 6 February 2026, current firmware index and white-model announcement were reviewed October 9, 2026; no phone, label, colour variant, display, key page, expansion module, headset, radio path, network, power source, firmware, provisioning service, account, PBX, protected session, emergency workflow, availability, compatibility, price, audio result or live call was inspected or testedIntermediateDocumentation based · not lab tested

Documented specifications

Open IP Phone Compare →

Snom · Snom retained gunmetal-black and white D815WB variants on its live product pages and published datasheet version 26 August 2026. Exact part number, regional radio approval, stock, installed firmware, PBX acceptance, accessory pairing and remaining support period remain deployment-specific.

D815WB: manufacturer-sourced facts
SpecificationDocumented value
Exact variantsGunmetal-black PN 00004727 and white PN 00004793; Snom says the 2026 white model is technically identical to the base model Source ↗
Display and keys5-inch 480×272 IPS display, ten physical SmartLabel keys and up to 40 mapped functions across four pages; physical and virtual positions are not simultaneous calls Source ↗
Accounts and calls12 SIP identities or accounts and up to 12 simultaneous calls are published device limits; provider channels, PBX resources and usable call starts remain separate Source ↗
Network and powerDual Gigabit Ethernet, IEEE 802.3af class 3 PoE or separate 5 V/2 A adapter; package and UPS design require the exact order Source ↗
Wireless interfacesIntegrated Wi-Fi 4 and Wi-Fi 5 plus integrated Bluetooth headset connectivity; association or pairing is not SIP or audio-path evidence Source ↗
Expansion and USBOne USB 2.0 Type-A port and published support for up to three D8C modules; module chain, host power, accessory sharing and firmware remain one acceptance set Source ↗
Audio and signalingPublished codecs include G.711, G.722, G.723.1, G.726, G.729AB, GSM 6.10 and Opus; DTMF lists SIP INFO, in-band and out-of-band Source ↗
Provisioning and securityHTTP, HTTPS and TFTP provisioning, SRAPS, TR-069/TR-111/TR-369, TLS 1.3, SIPS, SRTP, SRTCP, 802.1X, OpenVPN and dual firmware partitions are listed capabilities, not effective-state evidence Source ↗
Safety boundaryIndoor-only use; the safety guide restricts the Ethernet connection to PoE networks without routing to outside plant and specifies the recommended adapter Source ↗

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

Identify the D815WB and colour variant exactly

Snom's August 2026 datasheet identifies the gunmetal-black D815WB as part number 00004727 and the white model as part number 00004793. Snom's April 2026 announcement says the white version is technically identical to the base model. Keep those exact labels with procurement and fleet records; do not collapse the D815WB into the D815W, D812 or another D8xx device because the enclosure and display look similar.

Capture the rear label, part number, regional package, hardware revision and installed firmware before provisioning. A current product page or series image does not prove the delivered unit, radio approval, firmware lane, availability or PBX acceptance.

Separate SmartLabel positions, identities and calls

The datasheet publishes ten physical SmartLabel keys with up to 40 mapped functions across four pages, 12 SIP identities or accounts and up to 12 simultaneous calls. These are different capacities. Forty mapped actions are not forty physical controls, and neither the account nor call headline establishes provider channels, PBX resources, visible appearances or usable call-start rate.

Preserve the configured identity set, page map, labels, line behavior and actual service limits separately. Pilot hold, transfer, park, pickup, BLF, voicemail, conference and failed-action recovery on the intended PBX rather than treating a key label as server support.

Commission Ethernet, Wi-Fi and Bluetooth as separate paths

The D815WB lists dual Gigabit Ethernet, integrated Wi-Fi 4 and Wi-Fi 5, and integrated Bluetooth for headsets. Each path has a different owner and failure mode. A Wi-Fi association does not prove DHCP, DNS, time, certificate validation, registration or media; Bluetooth pairing does not prove answer, hang-up, mute, volume or recovery.

For Ethernet, retain switch port, VLAN, LLDP-MED, 802.1X, DHCP, DNS, QoS, PoE and UPS evidence. For Wi-Fi, retain band, SSID, authentication, coverage, roaming and recovery. For the exact headset, validate control and two-way audio before and after restart, radio loss and reprovisioning.

Treat D8C expansion, USB and power as one workstation

Snom publishes one USB 2.0 Type-A port and support for up to three D8C modules. The same phone can also use USB recording and accessories, while the device itself can use class 3 PoE or a separate 5 V/2 A adapter. Headline compatibility does not establish that the intended module chain and other USB devices can coexist or remain powered.

Inventory every module, cable, headset, storage device and power source. Confirm the supported topology, module firmware, key-page ownership, boot order, current draw and recovery after restart or a provisioning change. A D8C position is not a SIP identity, provider channel or authorization right.

Translate security and provisioning claims into loaded evidence

The datasheet lists SIPS over TLS, SRTP, SRTCP, TLS 1.3, HTTPS, 802.1X, OpenVPN, SRAPS, TR-069, TR-111, TR-369 and dual firmware partitions. These controls protect different boundaries. They do not prove the active administrator password, trusted provisioning source, certificate chain, protected SIP leg, protected media or approved firmware.

Assign owners for provisioning, firmware, certificates, exports and administrator access. Inspect the loaded server, effective transport, certificate validation, media negotiation and management reachability separately. Recheck Snom's firmware index and the PBX-approved target immediately before change; a public image is not an installed or supported result.

Respect the indoor, PoE and maintenance boundaries

Snom's safety instructions identify the D815WB as indoor equipment and warn that it should connect only to PoE networks without routing to outside plant. They also identify the recommended 5 V adapter and warn against substitutions. Treat wall mounting, cable routing, radio placement, temperature, cleaning and power resilience as deployment evidence rather than general office assumptions.

Stage clean provisioning, registration, inbound and outbound calls, caller identity, mute, hold, transfer, voicemail indication, BLF, directories, headset, speaker, expansion modules, restart, network and power recovery, and an approved firmware update. Preserve number and location evidence for the provider-approved emergency validation method without an uncoordinated live emergency call.

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.