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
Tech

Jitsi Video Conferencing in V70: A Controlled Approach to Privacy

Video conferencing is widely used, but rarely examined in terms of where it runs and who controls the infrastructure behind it. In many cases, video traffic is handled by external systems, introducing dependencies that are often overlooked. This piece explores how integrating Jitsi directly into the PBX brings video into the same environment as voice and communication management, giving organizations clearer boundaries, reduced reliance on third-party platforms, and greater control over how communication is handled.

April 21, 2026
Tech

Skills-Based Routing in V70: Match Calls to the Right Agent

Skills-based routing in V70 helps ensure incoming calls are matched with the most qualified available agents based on defined skills, language, and expertise. By combining IVR input with intelligent call distribution, organizations can reduce unnecessary transfers, improve first-contact resolution, and shorten handling time. With V70, skills can be defined directly within the PBX, allowing teams to set thresholds, prioritize expertise, and control how calls are routed across departments, queues, and different operational environments.

April 7, 2026
Tech

Snapshots in V70: Capture and Restore Your PBX with Confidence

PBX snapshots in V70 provide a reliable way to capture system state before changes are applied, enabling fast recovery, controlled rollback, and more predictable system management when updating configurations, testing call flows, or operating across multiple tenants. By preserving a point-in-time version of the system, administrators can reduce the risk of disruption, restore services quickly when issues arise, and maintain stability while making ongoing changes in complex communication environments.

March 31, 2026