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

Vodia Announces Partnership with Comms Group Global

Vodia Networks has announced a strategic distribution partnership with Comms Group Global (ASX: CCG), aiming to expand the reach of its feature-rich cloud PBX solutions across APAC and EMEA. Through this collaboration, Comms Group Global will serve as an official reseller, providing businesses of all sizes with scalable, secure, and integrated telephony solutions. Customers will benefit from advanced call management features, Microsoft Teams integration, and robust security standards, while also gaining access to Comms Group’s SIP coverage in over 65 countries. The partnership enables a streamlined “one-touch” provisioning process, ensuring fast and seamless deployment for enterprises and SMEs seeking to improve efficiency.

September 8, 2025

Why Fax Still Matters in 2025 and How Vodia Makes It Easy

Although many consider fax outdated, it continues to play a crucial role in sectors where compliance, confidentiality, and legal proof of delivery are non-negotiable. Healthcare providers rely on fax to meet HIPAA requirements, while industries such as finance, law, and real estate depend on it for contracts and documents that require signatures or legally verifiable transmission. Unlike email, fax offers confirmation reports that serve as proof of receipt, along with time-stamped records that hold up in legal proceedings. With Vodia’s PBX, digital fax becomes faster, easier, and more accessible than ever before, enabling users to drag and drop documents, monitor transmission progress, and receive immediate confirmations.

September 5, 2025

The Vodia PBX and SAML Integration

Vodia PBX now supports SAML integration, offering a secure and standards-based method for enterprise users to access their phone system through single sign-on. SAML, or Security Assertion Markup Language, allows employees to authenticate in one system and access other systems without managing multiple passwords, improving both security and user experience. By exchanging digitally signed SAML Assertions between Identity Providers and Service Providers, Vodia ensures seamless authentication across internal and external applications. With this integration, IT teams can simplify user management, reduce login complexity, and maintain strong security controls for business communications.

September 2, 2025