Editorial

The good, the Bad and the Ugly about Web Page Customization

Published on:

March 12, 2013

snom ONE allows extensive customization of web pages, emails, and device configurations, making it easy for customers to adjust content through the web interface. This feature is particularly useful for multi-tenant setups, as content can be tailored for different users based on their roles. Customization comes with challenges, however, especially during software upgrades. Changes made to templates, provisioning files or translations can be overwritten by new updates, causing issues in the system. To avoid problems, users must review and adjust their customizations after each upgrade, ensuring any unnecessary changes are removed and that everything works seamlessly.

Our PBX comes with a number of built-in templates for web pages, email, and device configuration. In the old days, those pages were hard coded, and we offered a couple of settings for minimal adjustments of the view (e.g., different header images).

For debugging it was very useful to get the content just out of a directory. We found this was also very useful for installations, and we have made the “html” directory accessible in the release mode.

Because file system access can be problematic, especially for the embedded devices, we made the content accessible through the web interface. Now customers could make their changes right from the web browser. The next step was to make that customization dependent on the content. A web page was now being rendered in the context of the extension, the domain, and the system. Depending on whom is logged in, it was now possible to present different content to different users. This was very useful for multi-tenant deployments.

Along with this, the translations were also made customizable. Although the file was available only on a system level, it added additional flexibility regarding customization.

So far, so good. Now to the bad and ugly part.

The main problem is software upgrades. The web content is far from static. Every upgrade brings changes in the content area, so if someone made changes in a file, that file still overlaid the changed content. For example, customers who spent a lot of time in customizing templates for version 5 won't be pleasantly surprised with the changes we have made in version 5.

The other problem zone is the provisioning area. We have made numerous changes in the pnp.xml file, as well as changes in other provisioning files. When manual changes were made, this could create quite a mess with the automatic provisioning: at the end of the day it might be possible nothing would be working in the provisioning area.

The same applies for changes in the translations. Usually upgrades introduce new texts, and those texts aren't visible after an upgrade.

Because of this, when you make changes in the templates, you must double check if you still need those changes after an upgrade. Revision management tools have a “merging” function that patches the changes in, but this isn't available for the PBX. Essentially you have to perform this function manually after an upgrade.

Many of the manual changes of the templates are to fix problems. When an upgrade is available, those fixes should become unnecessary and should be removed.

Anyway, there is one clear action item when upgrading: check if you still need the changes in the templates; if not, remove them.

Latest Articles

View All

Transforming Customer Service: Vodia PBX Integrates Seamlessly with Freshdesk

Vodia PBX now integrates seamlessly with Freshdesk, an AI-powered customer service platform used by over 73,000 companies worldwide. This integration combines intelligent ticketing and automation with enterprise-grade telephony, enabling automatic contact creation, detailed call tracking, and streamlined agent workflows. By improving call center efficiency and customer interaction management, it helps businesses enhance productivity and customer satisfaction. Vodia continues to strengthen its ecosystem with integrations to leading business software, delivering top-tier cloud PBX solutions.

July 29, 2025

Prepaid Cloud Instances: The Future of PBX Deployment

Prepaid cloud instances are transforming how PBX systems are deployed by offering a faster, simpler, and more flexible approach. With Vodia PBX now available on AWS, Azure, and DigitalOcean, businesses can launch a fully licensed, production-ready phone system in just minutes, without complicated setup or licensing delays. These preconfigured environments allow IT teams, decision-makers, and MSPs to test real-world VoIP performance, MS Teams integration, and mobile apps directly within their own cloud account. By removing traditional friction and offering full control, Vodia’s prepaid cloud instances provide a smarter and more efficient way to evaluate and deploy a modern PBX.

July 25, 2025

Vodia to Attend ChannelCon 2025

Vodia will participate in ChannelCon 2025, taking place in Nashville, TN, from July 29 to 31, with Sales Engineer Eric Altman attending on behalf of the company. ChannelCon, hosted by the Global Technology Industry Alliance (GTIA), is the premier vendor-neutral event dedicated to the worldwide IT channel. It brings together MSPs, service providers, vendors, and distributors for three days of expert panels, networking sessions, and special events designed to foster innovation and collaboration in the tech industry. Altman will highlight Vodia’s latest CRM integrations underscoring Vodia’s commitment to equipping partners with dynamic, enterprise-grade phone systems.

July 24, 2025