Back to Blog
Tech

Snom Mode Button Provisioning

Published on:

July 20, 2022

snom phones are highly customizable and work seamlessly with the Vodia phone system, making deployment simple. In certain cases, however, like configuring the internal directory on a line key, special settings may be needed. To achieve this, Vodia's snom mode allows users to define and provision settings for snom phones. For example, by using the keyevent F_ADR_BOOK, you can assign a line key for the internal directory. After saving, Vodia will automatically push the new configuration to the phone, eliminating the need for manual reboots.

Hamlet Collado

snom phones are great units to work with. They are very customizable and easy to plug and play with the Vodia phone system. Sometimes, however, the technician deploying the Vodia system with snom phones faces a few challenges.

Here's a scenario:

The customer wants the internal directory feature of the phone on one of the line keys. To check which feature you would like to use, see the list in Key+Events to identify the provisioning value.

snom Mode

Vodia has developed the snom mode: here you will be able to define any setting you would like on the user buttons and provision those values on the snom phone.

When deploying your snom phone, make sure the phone is provisioned correctly. Check our docs on how to provision a snom phone.

Next, navigate to the user buttons and choose snom. You will need to enter the text below to inform the phone system this will be a key+event. You will need to choose your provisioning value.

In this case it will be key+event F_ADR_BOOK - make sure you label your button so the user isn't confused.  Save the setting. The Vodia phone system will push the new configuration to the phone, so there's no need to reboot the unit.

snom mode

‍

Latest Articles

View All
Announcement

Vodia Announces Integration with ElevenLabs Voice AI Platform

A streamlined integration connects the Vodia PBX with the ElevenLabs Voice AI Platform using a lightweight IVR JavaScript script and native SIP REFER for call transfers. Audio and call control are handled entirely through standard SIP signaling, while all conversational logic, prompts, voice selection, and routing rules are configured in the ElevenLabs dashboard. This approach removes the need for webhooks or WebSocket connections and keeps the PBX side intentionally minimal, making the deployment clean and production-ready.

January 22, 2026
Editorial

Why Multi-Tenant Still Matters for MSPs

Multi-tenant architecture allows MSPs to manage multiple customers efficiently on a single, secure PBX while maintaining strict tenant isolation. By sharing infrastructure, MSPs can reduce operational costs, apply updates and security patches centrally, scale customers on demand, and onboard faster without increasing complexity. As cloud and SaaS models continue to dominate, a well-designed multi-tenant phone system provides the control, flexibility, and reliability MSPs need to support growth, evolving requirements, and modern communications workloads.

January 19, 2026
Editorial

Start 2026 with a cloud PBX built for real-world deployments

A flexible, cloud-neutral PBX built for real-world deployments in 2026, Vodia supports MSPs, enterprises, and service providers with an open, SIP-compliant platform designed for scale. With Vodia PBX version 70 arriving in Q1 2026, the platform brings multi-tenant hosting, reuse of existing IP phones through centralized provisioning, built-in WebRTC softphones, transparent licensing, and partner-driven support, giving organizations full control over modern business telephony without lock-in or hidden costs.

January 13, 2026