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

Smarter Hotel Communication: Vodia PBX Now Integrates with Shiji PMS

Vodia now offers seamless integration with the Shiji Property Management System (PMS), empowering hotels to streamline operations, automate routine tasks, and enhance guest experiences through smarter communication. From check-in to check-out, the integration connects telephony with front desk functions—enabling features like personalized extension setup, automated call billing, room status updates via maid codes, and effortless room changes. With a secure real-time interface, no complex middleware, and support for cloud, on-prem, or hybrid deployments, the Vodia-Shiji solution is built for reliability, scalability, and modern hospitality.

May 23, 2025

The Vodia - Microsoft Teams Integration Tool

The Vodia-Teams NPM Integration Tool makes it easy for enterprises and SMBs to connect Vodia PBX with Microsoft Teams, enabling secure, seamless voice communication within Teams. Certified by Microsoft for direct routing, this tool automates extension mapping and phone number assignments across multi-tenant Microsoft 365 environments, allowing users to make and receive calls through the PBX via Teams. This integration opens new possibilities in industries like hospitality, healthcare, and education by unifying voice services, supporting door phones, paging, and flexible call routing — all managed centrally for simplicity and scalability.

May 20, 2025

Monitoring Your Vodia PBX: Ensuring Continuous Communication

The Vodia PBX comes equipped with powerful built-in monitoring tools and integration options to ensure seamless, uninterrupted communication. From real-time system graphs and syslog analysis to packet capture tracking and detailed CDRs, Vodia enables proactive issue detection, performance optimization, and enhanced call quality. With support for SNMP, Prometheus, and external services like Pingdom and Site24x7, you can monitor everything from registration anomalies to system resource usage and SIP connectivity across multiple servers—all in one comprehensive solution.

May 15, 2025