Tech

UHLL

Published on:

October 7, 2014

In the past, pbxnsip offered a module connecting the PBX to property management systems (PMS), enabling features like billing international calls and notifying the front desk about room status updates. This functionality was based on the Universal Hospitality Language Layer (UHLL) protocol, which also supported non-telephony tasks within hotels. While this module was useful, it required additional software and added complexity. For the next release (5.2.5 or 5.3), we’ve integrated UHLL directly into the PBX code, simplifying the setup. Those interested in trying out the new features can email us for access to a beta build.

Those who were already using pbxnsip in the old days might remember we had a module connecting the PBX with the property management system (PMS). This module was doing things like putting international phone calls on the guest's bill like you would order a drink at the bar. But it was also doing other things, like telling the front desk a room has been cleaned up or a guest has turned on do-not-disturb on the room phone.

The functions are accomplished using the UHLL protocol, which stands for Universal Hospitality Language Layer. Apart from billing calls, there are many functions that have nothing to do with telephony this protocol can do. Those who frequently stay in hotels might discover more of them during their next stay.

In those old pbxnsip days, we chose to use this piece of software as a glue logic. It was complicating the setup, however, as another piece of software had to be installed and kept running. Considering the actual relatively low complexity of the program itself, compared to the PBX, we decided to fully integrate it with the other PBX code this time, so activating the functionality can be done easily in the license key.

The UHLL will be part of the next release (5.2.5 or maybe 5.3). Anyone who would like to take a peek is welcome to send us an email and request a beta build.

Latest Articles

View All

​Services Changes

Following a critical PHP security advisory affecting installations worldwide, we temporarily restricted public access to some of our backend services while carrying out necessary upgrades. Access has now been restored, and the affected services are operating normally. The Vodia PBX itself does not use PHP and was not directly affected. We explain what happened, the changes to legacy licensing and TLS support, and why customers running older PBX versions should contact us for upgrade guidance.

October 22, 2026

How to submit a support ticket in the Vodia Help Center

Submitting a support ticket with the right information helps our team understand your issue and reduces follow-up questions. This step-by-step guide walks you through the Vodia Help Center, from describing the problem and attaching diagnostic files to setting the business impact and providing your PBX details. You’ll also learn which call details and timestamps to include, alongside practical tips to keep troubleshooting focused and help our support team investigate your issue more efficiently.

October 21, 2026

Make the Switch: The Vodia PBX Migration Tool

Switching phone systems doesn’t have to mean rebuilding everything from scratch. The Vodia PBX migration tool imports key configuration data from backups, including extensions, ring groups, queues, desk phones, and basic auto-attendant settings. Built into the Vodia Admin Portal, it guides administrators through the import process and reduces repetitive manual work, whether you’re moving 10 extensions or 1,000. Explore what transfers, what needs manual setup, and how the built-in tool reduces repetitive work when moving to Vodia.

October 15, 2026