Back to Blog
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 role. However, customization comes with challenges, 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 that any unnecessary changes are removed and that everything works seamlessly.

Christian Stredicke

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

For debugging it was very useful to get the content just out of a directory. We found that this was also very useful for installations, and 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 who is logged in, it was now possible to present different content to different users. This was very useful for multi-tenant deployments.

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

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

The main problem is software upgrades. The web content is far from being static. Every upgrade brings changes in the content area as well. If someone made changes in a file, that file still overlays the changed content. For example, customers who spent a lot of time in customizing templates for version 5 will not be pleasantly surprised with the changes that we have made for version 5.

The other problem zone is the provisioning area. We have made numerous changes in the pnp.xml file, and also 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, nothing could be working any more in the provisioning area.

The same applies for changes in the translations. Usually upgrades introduce new texts, and those texts are not 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; however for the PBX that is not available. Essentially you have to perform that 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
Webinar

Webinar | Real-Time Media Streaming in Vodia PBX: AI, Call Transcription, and Security in V69.5.6

Join Vodia Networks on April 8 for a live, in-depth webinar on how real-time media streaming is powering the future of voice communication. Discover how Vodia PBX version 69.5.6 enables seamless AI integration, live call transcription using the Whisper API, and secure voice data handling. Hosted by Sales Engineer Eric Altman and VoIP Engineer Hamlet Collado, this session will walk you through real-world use cases, including OpenAI and Google Speech-to-Text integrations, MS Teams support, and new security features. You’ll also get a first look at Vodia’s AI roadmap and have the opportunity to ask your questions during a live Q&A.

March 28, 2025
Tech

The Vodia PBX On-Premise Whisper AI Deployment​

Whisper, OpenAI’s Automatic Speech Recognition system, delivers multilingual, noise-tolerant, and technical-language-ready transcription through a streamlined encoder-decoder architecture. With Vodia PBX’s integration, organizations can choose between using OpenAI’s service or hosting Whisper AI locally for complete data sovereignty and control. This on-premise option ensures that sensitive call data stays within your infrastructure while still benefiting from powerful transcription capabilities. To explore deployment options, see our Whisper AI on-premise setup documentation, review a self-hosted integration example, or follow our cloud-based call transcription guide.

March 27, 2025
Announcement

Vodia at Enterprise Connect 2025: Embracing AI and Advancing Communications

Vodia Sales Engineer Eric Altman attended Enterprise Connect 2025 on March 18 and 19, where he connected with partners and gained insight into the future of enterprise communications. AI was the clear focus of the event, with discussions centered on agentic systems, chatbots, and generative technologies. “It was certainly the main element in the atmosphere,” Eric noted. He also shared his excitement about Vodia PBX version 69.5.6, which includes real-time AI integration with OpenAI and call transcription using the Whisper API. The event confirmed that AI is rapidly becoming a core component of modern communication platforms—and Vodia is well-positioned to lead the way.

March 26, 2025