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

Vodia in 2025: Reflections and What’s Next

Vodia’s 2025 marked a year of pragmatic AI adoption, unprecedented platform robustness, and laying the foundation for the next phase of the PBX. With version 69 reaching exceptional stability, focus has shifted to version 70, which introduces a redesigned admin interface and major architectural improvements in scalability, resilience, and flexibility. Alongside steady expansion of integrations and partner tooling, the roadmap for 2026 emphasizes refined user experiences, modernized apps, and continued investment in reliability over hype.

December 23, 2025

Should You Upgrade Your Vodia PBX? A Practical Guide

Delaying PBX upgrades may feel safe in the short term, but real-world dependencies like security standards, app compatibility, and vendor APIs eventually force reactive upgrades at the worst possible time. Staying reasonably current with Vodia PBX versions, rather than clinging to outdated releases or jumping on every new preview, helps maintain security, compatibility, and performance while avoiding emergency upgrades, especially as newer features and OS requirements become unavoidable.

December 19, 2025

New York City Department of Education Will Move Its Telephony to the Cloud

The New York City Department of Education has issued a Request for Expression of Interest signaling its intent to modernize district-wide communications by moving away from legacy landline PBX systems. Serving 1.1 million students across 1,800 schools, the proposed transition to a cloud-based VoIP platform focuses on resiliency, scalability, multilingual capabilities, hybrid deployment options, and integration with Microsoft Teams for more than 150,000 staff members.

December 16, 2025