VoIP.info Device reference

Snom M80 rugged DECT handset

Review the manufacturer-listed IP65 and drop protection, alarm controls, headset options and M-Series base dependency.

Reviewed 2026-10-12Exact-model manufacturer documentation reviewed September 26, 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 firmware, replacement battery supply and remaining support period not established.

M80: manufacturer-sourced facts
SpecificationDocumented value
EnclosureIP65 and MIL-STD 810g listed; drops up to 2 m stated by manufacturer Source ↗
Weight120 g stated by manufacturer Source ↗
DisplayHigh-resolution TFT color display listed Source ↗
HeadsetsIntegrated Bluetooth and 3.5 mm connection Source ↗
BatteryUp to 12 h talk time stated by manufacturer Source ↗
AlertsTop alarm key and vibration alert listed Source ↗
AudioHD audio listed Source ↗
Base familyManufacturer compatibility guide lists M400 and M900 bases Source ↗

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

Treat ruggedness as a bounded claim

Snom lists IP65, MIL-STD 810g and resistance to drops up to two metres. Those are exact-model manufacturer claims, not a blanket approval for every construction site, chemical, cleaning process, temperature or repeated impact. Match the intended exposure to the complete manufacturer documentation and the site's safety requirements.

Inspect the housing, seals, display and charger after a drop or contamination event. A product's original rating does not prove that a damaged unit retains the same protection. No hands-on ingress or drop test is claimed here.

Define the alarm and location workflow

The handset has a top alarm key, vibration alert and Bluetooth support that Snom describes in connection with its optional beacon ecosystem. These controls can participate in a configured workflow, but the product page does not establish a certified life-safety, lone-worker or guaranteed indoor-location system.

Document the trigger, destination, acknowledgement, escalation, coverage, privacy and outage fallback. Test the complete workflow from every intended work area and during a PBX, base or network fault. An ordinary voice call is not alarm-system acceptance.

Plan the handset and base together

The M80 is a DECT handset rather than a standalone Wi-Fi or cellular phone. Snom's compatibility guide lists the M400 and M900 bases. Confirm the exact regional DECT variant, base capacity, codec-dependent calls, cell survey, roaming design, PBX provisioning and firmware combination as one system.

Pilot answer, hold, attended and blind transfer, headset use, roaming and recovery after a battery or handset restart. Record the exact base and handset firmware with the result instead of generalizing from the family catalogue.

Verify accessories, runtime and lifecycle

Snom lists Bluetooth, a 3.5 mm headset connection and up to 12 hours of talk time. Test the exact headset, call controls, audio level, reconnection and charging routine. The maximum talk-time statement is not a guarantee for the selected codec, radio conditions, battery age or shift pattern.

Confirm charger and replacement-battery supply, current regional stock, approved firmware and support dates before procurement. No hardware, radio, roaming, ruggedness, alarm, beacon, battery, headset, PBX, availability, price or remaining-support-period behavior is represented as tested.

Keep the handset requirement separate from the base choice

M80 can be paired with the M400 dual-cell system, while the M30 is a different one-account indoor handset. Select the handset from workplace, alarm, headset, battery and cleaning requirements, then validate that exact model with the chosen base and firmware.

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.