VoIP.info Current device research

Snom M400 dual-cell DECT base

Evaluate the M400 as a single- or dual-cell DECT system while keeping handset count, narrowband and wideband call capacity, handover, SIP registration, PoE and protection evidence separate.

Reviewed 2026-10-12Current Snom M400 support hub and January 20, 2025 datasheet, M400 v1.01 administration guide, current M30 datasheet, and first-party registration and handover troubleshooting reviewed October 12, 2026; the documents describe product and configuration boundaries rather than an inspected deployment, and no base, handset, repeater, radio survey, PBX, credential, registration, network, PoE source, firmware, protected session, emergency route, audio path or live call was inspected or testedAdvancedDocumentation based · not lab tested

Documented specifications

Open IP Phone Compare →

Snom · Snom listed M400 on its current support hub at review and updated that hub March 30, 2026. Exact regional availability, ordered hardware revision, approved firmware pair, certified PBX interoperability, warranty entitlement and remaining support period were not established.

M400: manufacturer-sourced facts
SpecificationDocumented value
TopologyOne base supports single-cell operation; two M400 bases form the published dual-cell system with seamless handover Source ↗
HandsetsUp to 20 handsets in either the published single- or dual-cell system; this is not a concurrent-call figure Source ↗
Single-cell callsUp to 10 narrowband or 5 G.722 wideband calls Source ↗
Dual-cell callsUp to 20 narrowband or 10 G.722 wideband calls across the published two-base system Source ↗
RepeatersUp to 6 in single-cell or 12 in dual-cell according to the datasheet; placement and channel effects require a surveyed design Source ↗
Published radio rangeUp to 50 m indoors and 300 m outdoors in ideal conditions; the administration guide limits the base itself to indoor installation Source ↗
Network and power10/100 Ethernet with IEEE 802.3af PoE class 2 or a separately scoped 5 V adapter path Source ↗
ProvisioningWeb interface, HTTP, HTTPS or TFTP loading, preinstalled-certificate secure provisioning and cloud zero-touch support are listed Source ↗
Protection claimsSIPS over TLS, SRTP and TLS 1.2 are listed; configured certificate validation and negotiated protection remain deployment evidence Source ↗
Compatible handset setCurrent datasheet lists M25, M30, M65, M70, M80, M85 and M90; regional and firmware compatibility still require confirmation Source ↗

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

Choose one or two cells before applying capacity figures

Snom publishes M400 as a single- or dual-cell system. One base is limited to the single-cell totals; two bases form the dual-cell topology. Record the exact base count, regional part numbers, placement, power source, firmware versions, handset set, repeaters, PBX or service and provisioning owner before accepting any headline total.

The datasheet separates up to twenty handsets from up to ten narrowband or five wideband calls in one cell and twenty narrowband or ten wideband calls in dual cell. Handset enrollment, active calls, ringing branches, local conferencing and external trunk capacity remain different limits. A second base does not turn M400 into an unrestricted M900 multicell deployment.

Survey radio coverage, synchronization and handover

The published 50 m indoor and 300 m outdoor range values are ideal-condition inputs, not a building design radius. The administration guide says M400 is for indoor installation and warns that metal, current lines, water pipes and unsuitable environmental conditions can affect placement. Survey the occupied site with doors, lifts, shelving, walls, crowds and normal interference represented.

For dual cell, preserve each base identity, synchronization relationship, RSSI and one controlled handover path. Snom attributes dropped connections and failed handovers in multicell systems to weak synchronization-source RSSI and identifies -75 dBm as its troubleshooting floor. That vendor diagnostic is not proof of a compliant survey or of performance in an untested building.

Keep handset movement and SIP registration as separate events

Snom documents a roaming case in which a handset moving between bases can cause the new base to register the same SIP account. Its multiple-registration support control changes whether the first base sends a de-REGISTER before the next REGISTER. Record the selected value, the PBX or platform policy, both base identities, Contact values and the actual transition before changing it.

A successful DECT handover does not prove the SIP service accepted the new registration, and a stable registration does not prove audio stayed on the correct radio path. Test registration state, ringing, answer, handover, both media directions and hangup separately. Do not broaden PBX contact limits or disable registration controls merely to hide one failed transition.

Validate power, provisioning and protection independently

Confirm the actual switch port, LLDP or VLAN policy, PoE class, cable path and recovery after the base loses power. The optional adapter is a separate supply path and does not prove backup runtime. Inventory web-interface ownership, provisioning URL, certificate, downloaded configuration, firmware source and rollback before change.

Snom lists SIPS over TLS, SRTP and TLS 1.2, while DECT base-to-handset authentication and encryption are another layer. Confirm server name, certificate chain, SIP transport, SDP result, negotiated media and radio security independently. No M400, handset, repeater, radio, PBX, credential, PoE source, provisioning server, protection control, availability, compatibility, price, emergency route, audio path or live call was inspected or tested for this reference.

Diagnose a dual-cell drop without collapsing radio and SIP state

When a moving call drops or the account becomes unreachable after changing bases, use the M400 dual-cell roaming diagnostic. It separates synchronization RSSI, serving-base transition, SIP registration ownership, PBX contact policy and media.

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.