VoIP.info Device reference

Snom M70 office-rugged DECT handset

Review the manufacturer-listed two-metre drop claim, alarm key, headset options, battery figures and exact M-Series base dependency.

Reviewed 2026-09-27Exact-model manufacturer product page, datasheet, compatibility and firmware resources reviewed September 27, 2026IntermediateDocumentation based · not lab tested

Documented specifications

Open IP Phone Compare →

Snom · Listed in the current M-Series catalogue at review; exact regional availability, approved PBX firmware, replacement-battery supply and remaining support period not established.

M70: manufacturer-sourced facts
SpecificationDocumented value
Drop claimManufacturer lists MIL-STD-810g 516.6 and drop testing up to 2 m; no IP ingress rating is established by the reviewed M70 sources Source ↗
WeightApproximately 120 g with battery and belt clip Source ↗
Display2.0-inch backlit TFT LCD, 240 × 320 pixels Source ↗
HeadsetsBluetooth LE and 3.5 mm headset connection listed Source ↗
BatteryUp to 12 h wideband or 17 h narrowband talk time and 200 h standby stated by manufacturer Source ↗
AlertsProgrammable top alarm key and vibration alert listed Source ↗
EnvironmentOperating range −10°C to 55°C stated in technical specification Source ↗
Base familyManufacturer compatibility material lists M300, M400, M700 and M900; exact regional and firmware combination still requires verification Source ↗

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

Keep the M70's protection boundary exact

Snom lists the M70 as ruggedized and cites MIL-STD-810g 516.6 drop testing up to two metres. The reviewed exact-model material does not give it the M80 or M90's separate IP65 ingress claim. Do not transfer dust, water, cleaning or hazardous-location suitability from a sibling handset.

Match the purchased unit to the complete technical specification and workplace exposure. Inspect the housing, display, battery cover and charger after a drop. A factory test does not prove that a damaged or repeatedly dropped handset retains its original condition, and no hands-on drop or contamination test is claimed here.

Plan handset, base and firmware as one system

The M70 is a DECT handset, not a standalone Wi-Fi or cellular SIP phone. Snom's compatibility material lists M300, M400, M700 and M900 bases, while the current product family emphasizes supported M-Series deployments. Confirm the exact base, regional DECT variant, PBX provisioning path, cell design and manufacturer-approved firmware combination before procurement.

The firmware centre and update guidance are operational inputs, not a promise that every release is approved by the selected PBX. Record both base and handset versions, back up the configuration, preserve a rollback path and pilot registration, roaming and recovery after an update.

Define alarm and Bluetooth behavior without a safety claim

Snom lists a programmable top alarm key, vibration alert and Bluetooth LE. These controls can participate in a configured assistance or workflow path, but the product page does not establish a certified life-safety, lone-worker, door-control or guaranteed indoor-location system.

Document the trigger, call or message destination, acknowledgement, escalation, coverage, privacy and outage fallback. Pair and test the exact headset, including call controls, audio level and reconnection. An ordinary voice call or a button press is not acceptance of the wider response workflow.

Verify runtime, accessories and deployment fit

The technical specification lists approximately 120 g with battery and belt clip, a 2.0-inch 240 × 320 display, up to 12 hours of wideband or 17 hours of narrowband talk time, 200 hours of standby and an operating range of −10°C to 55°C. Treat every maximum as a manufacturer condition, not a shift guarantee.

Pilot the exact codec, signal conditions, headset, charger, roaming pattern and battery age across a real workday. Confirm regional stock, charger and replacement-battery supply, approved firmware and support dates before fleet purchase. No hardware, drop resistance, environmental, radio, roaming, alarm, Bluetooth, battery, PBX, availability, price or support-period behavior was tested for this guide.

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.