Documented specifications
Snom · Manufacturer documentation available at review; exact SKU availability, remaining support period and approved firmware not established.
| Specification | Documented value |
|---|---|
| Topology | Up to two bases in the published dual-cell system Source ↗ |
| Power | Power over Ethernet supported Source ↗ |
| Security | TLS/SRTP listed; deployment setting still requires validation Source ↗ |
| Handsets | M55 and M58 named as compatible examples Source ↗ |
| Updates | Handset over-the-air software updates listed Source ↗ |
Unlisted fields remain unverified. Platform compatibility and remaining support life require confirmation for the exact ordered model.
What the base provides
The M500 is a DECT base that can be paired with a second base for a dual-cell system. The product page lists PoE, TLS/SRTP and over-the-air handset updates. These are base-system capabilities, not features of every compatible handset or PBX service.
Capacity needs confirmation
The same current manufacturer page gives different figures: a feature list says up to 10/8 handsets in single/dual-cell use and eight simultaneous narrowband calls, while later copy mentions 16 phones and 16 parallel calls in a two-base system. Do not publish one figure as the verified capacity. Ask Snom for a firmware- and configuration-specific table before sizing a site.
Deployment checks
Survey coverage in the occupied building, including stairwells and areas behind heavy walls. Pair the intended M55/M58 devices and test handoff between bases during an active call. Confirm the actual PoE class, network addressing, SIP accounts, firmware and supported management method.
Security and lifecycle
The manufacturer describes TLS/SRTP and mutual-TLS provisioning, but they require matching server configuration and trust. Validate both signaling and media settings. Confirm regional stock and support dates before procurement; a live product page does not establish inventory.
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.