Recording phone calls is essential for compliance, particularly in industries like brokerage, where proof of phone agreements is required. In the snom ONE PBX, recordings are categorized into automatic and manual types. While manual recordings are handled like voicemail messages, automatic recordings, often generated in bulk in busy call centers, present a challenge for archiving and access. The solution is organizing them in a file system by domain and date for easy retrieval and storage on remote services. The 5.1.3 release introduces HTML5 audio playback for seamless in-browser listening, allowing restricted access to specific recordings without altering file system permissions, though IE users face limitations due to unsupported WAV formats.
Recording phone calls is an important feature of any PBX. Phone calls sometime need to be recorded for legal purposes, e.g., for brokerage firms that need proof when trading agreements are made over the phone.
On the snom ONE PBX, we differentiate between automatically made recordings and recordings started manually. The manual recordings are treated similar to voicemail messages and are shown in the voicemail section of the web interface. Because there are usually only a handful of such recordings, the manual recordings are not a big problem. The automatic recordings are mostly generated in bulk. Especially in busy call centers, with thousands of calls every day, this poses a difficult question as to how to archive and access the recordings.
The first answer to this question is the file system. By putting the recordings into directories organized by the domain and the date, we make it easy to access files for those who have file system access; it's also easy to permanently store these files on remote storage services. There are several synchronization services for this.
There was always the demand to have the playback for the recordings directly from the web interface, however: HTML5 has added the audio element, which makes it possible to stream the audio directly to the browser without the need to store it and then play it externally. In other words, it becomes possible to play a recording back with a simple click. It also makes it possible to grant access to only certain recordings - for example, only to those made by a certain agent group - without having to tweak file system access. This is what we have added to the upcoming 5.1.3 release. For the various recording locations, we have put a little triangle next to the recording record: when the user clicks on it, it makes the audio player visible and starts the playback.
While we were on it, we also started to add the playback feature in other places like the auto attendant IVR control (see screenshot). This makes it easier, faster and more fun to set the attendant up.
Most desktop browsers support this method. Unfortunately, Internet Explorer is again an exception here because it is unable to play back simple WAV files. Encoding the recordings in MP3 or even AAC isn't an option for the PBX, so we are unable to offer this feature for IE users. In most installations, however, users also have other browsers installed, so it will be possible for practically all users to use this new feature. The feature availability for mobile users is limited, but we expect that over time more and more mobile devices will support the HTML5 audio tag with the WAV format.
Vodia is heading to CVx EXPO26, November 17–18 in Glendale, Arizona. Visit Booth 2009 to meet the Vodia team, learn more about our business communications platform, Partner Program, white-label capabilities and the latest V70 developments, and discuss how Vodia can support your customers. The event brings together MSPs, VARs, technology advisors, service providers and other channel professionals, making it a great opportunity to connect directly with the team, ask questions and explore how Vodia can support your business.
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.
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.