Vodia PBX Integration with PMS (Property Management Systems)
Published on:
July 21, 2019
A Property Management System (PMS) Interface allows the Vodia PBX to communicate with hospitality PMS platforms like Infor Hospitality using protocols such as UHLL (Universal Hospitality Language Layer) and FIAS (Fidelio Interface Application Specification). This integration enables efficient communication by syncing key operational functions, like check-in/check-out status, Do Not Disturb (DND) messages and room service updates. Staff can update room statuses directly from room phones, and the PMS can control call privileges and billing. Additionally, the Vodia PBX sends notifications for wake-up calls and provides call data records to add to guest bills, enhancing service and operational efficiency in hospitality settings.
A property management system (PMS) is a software application used by hospitality providers and commercial residential rental properties. PMS is also used in manufacturing industries and by local governments.
The PBX communicates with property management systems (PMS) using the "UHLL" (Universal Hospitality Language Layer) protocol and the FIAS (Fidelio Interface Application Specification) protocol. The Vodia PBX was certified with the Infor Hospitality platform. The following features are supported:
Send call data records to the PMS and add charges to the guest bill
Send maid codes to the PMS to change the status of the room
Exchange DND messages with the PMS system.
How to Connect
To connect, go to your selected domain on the web interface and navigate to Advanced --> Hospitality
Enter the address and port of the PMS server in the setting PMS Server Address including port (Eg. pmsserver.com:6000 or 192.168.0.8:6000):
If the setting DMM (three-character device identification provided): is not already set to 302, then set it to 302.
Press Save and connect the PBX to the PMS server.
To disconnect, leave the server address setting empty and press save and connect.
Maid Codes
Staff can use the room phone to change the status of the room. The following codes are available:
*57 or *571: Room cleaned
*572: Room cleaning required
*573: Room cleaning in progress
*574: Room inspection required
*575: Room maintenance required
*576: Room out of order
*577: Room pick up
*578: Room passed inspection
*579: Room failed inspection
*5710: Room cleaning skipped
Because FIAS uses different codes, the maid codes 2-6 and 9 are mapped to "Dirty", 8 is mapped to "Inspected" and the other codes are mapped to "Clean".
Room Calls
There is a flag that determines whether room to room calls are allowed or not. If room calls are prohibited, the staff needs to transfer calls.
Depending on the check-in status, the PBX can use different plans for outbound calls. When someone is checked in, the PBX uses either the restricted or the unrestricted dial plan. The restricted status is passed in the check-in message from the PMS and usually depends on whether the guest uses a credit card or cash for check-in. If nobody is checked into the room, the PBX uses the dial plan assigned to that extension or, if no specific dial plan was assigned, the default dial plan of the domain.
When wake-up calls are missed, the PBX can send an email to inform staff about this.
UHLL Messages
Once the connection is set up, the following UHLL messages can be exchanged between the PBX and the PMS server.
From PMs to PBX
PMS can send a check-in message to the PBX with the extension number, which will enable the extension and turn on its voicemail, etc. It will also optionally turn on outgoing calls by changing the dial plan if the dial plan is set to "No Outbound Calls".
PMS can send a check-out message to the PBX with the extension number, which will reset the extension and turn off its voicemail, etc. It will also optionally turn off outgoing calls by changing the dial plan to "No Outbound Calls" if a dial plan by that name exists.
PMS can send the credit message to the PBX with the extension number and credit amount, which will set a credit limit on that extension. This works only if the trunk's rates setting has been set.
PMS can send the DND on or off message to the PBX with the extension for which the DND should be turned on or off.
From PBX to PMS
The PBX will send a call charge message to the PMS on the completion of every outgoing trunk call, with from, to, start time, duration and amount information (if available).
The PBX will send a maid code/room cleaned code to the PMS when you dial the room clean star code (*57 by default) on the phone extension connected to the PBX. This star code default can also be changed on the PBX.
The PBX will send a DND message on or off to the PMS when you dial a Do Not Disturb star code on the phone extension connected to the PBX. Star code *78 (default) turns DND on and *79 (default) turns it off.
If you would like to test the Vodia hospitality management feature, sign up here and ask about the Vodia hosted edition.
Video conferencing is widely used, but rarely examined in terms of where it runs and who controls the infrastructure behind it. In many cases, video traffic is handled by external systems, introducing dependencies that are often overlooked. This piece explores how integrating Jitsi directly into the PBX brings video into the same environment as voice and communication management, giving organizations clearer boundaries, reduced reliance on third-party platforms, and greater control over how communication is handled.
Skills-based routing in V70 helps ensure incoming calls are matched with the most qualified available agents based on defined skills, language, and expertise. By combining IVR input with intelligent call distribution, organizations can reduce unnecessary transfers, improve first-contact resolution, and shorten handling time. With V70, skills can be defined directly within the PBX, allowing teams to set thresholds, prioritize expertise, and control how calls are routed across departments, queues, and different operational environments.
PBX snapshots in V70 provide a reliable way to capture system state before changes are applied, enabling fast recovery, controlled rollback, and more predictable system management when updating configurations, testing call flows, or operating across multiple tenants. By preserving a point-in-time version of the system, administrators can reduce the risk of disruption, restore services quickly when issues arise, and maintain stability while making ongoing changes in complex communication environments.
.svg)
