Tech

snom button mode to the rescue

Published on:

May 2, 2018

Addressing a challenge with LDAP, VoIP phones lack the ability to write new contacts to the address book. For users of snom phones, a solution involves utilizing the snom button mode, specifically the "keyevent" mode with the F_ADR_BOOK parameter. This configuration enables users to add phone numbers directly from the phone keyboard, bypassing the need for PBX login and web interface use. This versatile approach can also be applied to other functions and is similarly available for Grandstream, HTek, and Yealink phones.

One problem with LDAP is VoIP phones have no way of writing a new contact to the address book. LDAP is a very powerful protocol, but it seems VoIP phones don’t use it to write an address book entry. If I’m wrong please let me know - I’d be happy to know about it.

We had a customer using snom phones who needed a simpler way for users to add phone numbers right from the phone keyboard, without logging into the PBX and using the web interface. We saw two possibilities for this: the first would be to use the snom XML and program a small application to collect user input and send it back to the PBX; the second would be to use the local phone address book along with the LDAP address book.

The problem with the XML solution is it would be usable only from the snom phones and would obviously require changes in the PBX.

Using the phone address book is a lot easier and is even possible without making any changes in the PBX. We actually already have a "backup mode" for snom phones - we can set anything we want in the button configuration of the phone. By using the "keyevent" mode with the F_ADR_BOOK parameter, we can set the phone to call up the address book when a user presses a specific button.

This seems to be the easiest solution for now. The beauty of it is it can also be used for other functions; the list of available functions on the phones is quite lengthy.

P.S. We have similar modes also for Grandstream, HTek phones and Yealink phones. 

Latest Articles

View All

​Services Changes

Following a critical PHP security advisory affecting installations worldwide, we temporarily restricted public access to some of our backend services while carrying out necessary upgrades. Access has now been restored, and the affected services are operating normally. The Vodia PBX itself does not use PHP and was not directly affected. We explain what happened, the changes to legacy licensing and TLS support, and why customers running older PBX versions should contact us for upgrade guidance.

October 22, 2026

How to submit a support ticket in the Vodia Help Center

Submitting a support ticket with the right information helps our team understand your issue and reduces follow-up questions. This step-by-step guide walks you through the Vodia Help Center, from describing the problem and attaching diagnostic files to setting the business impact and providing your PBX details. You’ll also learn which call details and timestamps to include, alongside practical tips to keep troubleshooting focused and help our support team investigate your issue more efficiently.

October 21, 2026

Make the Switch: The Vodia PBX Migration Tool

Switching phone systems doesn’t have to mean rebuilding everything from scratch. The Vodia PBX migration tool imports key configuration data from backups, including extensions, ring groups, queues, desk phones, and basic auto-attendant settings. Built into the Vodia Admin Portal, it guides administrators through the import process and reduces repetitive manual work, whether you’re moving 10 extensions or 1,000. Explore what transfers, what needs manual setup, and how the built-in tool reduces repetitive work when moving to Vodia.

October 15, 2026