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

Why Vodia is the Ideal PBX for Microsoft Environments

Many organizations rely on Microsoft as the foundation of their daily operations, but their communication systems often exist in parallel rather than in harmony. Vodia closes that gap by bringing telephony into the same environment where teams already work, turning separate systems into one connected structure. This approach removes friction between platforms, simplifies management, and gives IT teams better control and visibility over daily communication. It also creates a more seamless experience for employees, reduces operational overhead, and builds a stronger, more flexible foundation that supports growth, collaboration, and long-term scalability.

October 17, 2025

Vodia to Attend CVxExpo 2025 in Glendale, Arizona

Vodia will be attending CVxExpo 2025 in Glendale, Arizona, from November 3–5. Sales Engineer Eric Altman will be on site to meet with current and prospective partners, demonstrating how Vodia’s PBX solutions can strengthen technology roadmaps for 2026. This year, Vodia highlights new integrations with ActiveCampaign, Freshdesk, HighLevel, Microsoft 365, Microsoft Presence, monday.com, and Odoo Cloud, along with enhanced call center capabilities such as agent activity dashboards, call recordings, and transcription features. Partners and attendees can schedule meetings with Eric to learn more about scalable, feature-rich, and cost-effective telecommunications solutions built for enterprises and SMBs.

October 14, 2025

Enterprise Call Analytics: Real-Time Insights Built Right Into Your PBX

Vodia Enterprise Call Analytics gives businesses comprehensive, real-time insights into every aspect of their call operations. Built natively into the PBX, it delivers live, color-coded dashboards, detailed call records, smart filtering, and exportable data. Enterprises can track key metrics such as answer rates, call volume, peak hours, talk times, and top performers, while also monitoring call quality through integrated MOS scoring. By turning call data into actionable intelligence, Vodia helps organizations optimize team productivity, improve customer experience, manage costs effectively, streamline workflows efficiently, and make smarter, data-driven decisions that contribute directly to revenue, operational performance, and long-term ROI.

October 10, 2025