Voicemail Transcription Issues after 5.4 Upgrade

U

UCtech

Member
Jan 9, 2019
45
8
8
Have not been able to get transcribe working after upgrading from 5.3 to 5.4. Voicemail to email is still working but where the transcription normally is located instead just shows ${message_text}. Was working fine before the upgrade. Using Watson. Transcribe queue shows nothing. Have tested in shell that it is running using systemctl status email_queue as follows:
root@xxxxx:~# systemctl status transcribe_queue
● transcribe_queue.service - Audio Transcribe Queue Service
Loaded: loaded (/etc/systemd/system/transcribe_queue.service; enabled; preset: enabled)
Active: active (running) since Wed 2025-12-17 15:03:35 CST; 12min ago
Main PID: 604 (php)
Tasks: 1 (limit: 9385)
Memory: 15.8M
CPU: 314ms
CGroup: /system.slice/transcribe_queue.service
└─604 /usr/bin/php /var/www/fusionpbx/app/transcribe/resources/service/transcribe_queue.php
Dec 17 15:03:35 UAU-VoIP systemd[1]: Started transcribe_queue.service - Audio Transcribe Queue Service.
Dec 17 15:03:37 UAU-VoIP php[604]: PHP Warning: file_put_contents(/tmp/autoloader_interface_cache.php): Failed to open stream: Permission denied in /var/www/fusionpbx/resources/classes/a>
Dec 17 15:03:37 UAU-VoIP php[604]: [NOTICE] Starting up...

For the upgrade I followed the steps in 5.3 to 5.4 here:

Version Upgrade — FusionPBX Docs documentation

docs.fusionpbx.com docs.fusionpbx.com
All of that went well but not sure what the "Domains member feature" is or where the "application manager" is so I did nothing with that part of the upgrade. Could that be part of the problem?
How do I fix the "Failed to open stream: Permission denied"?
Thanks in advance!
 
Sorry didn't see the warning line was truncated. The full warning is:
Failed to open stream: Permission denied in /var/www/fusionpbx/resources/classes/auto_loader.php on line 208
auto_loader.php line 208 is:
$interface_result = file_put_contents(self::$interfaces_file, "<?php\n return " . $interfaces_array . ";\n");
 
So after a few weeks I checked and there were a bunch of updates to the transcription files, so I updated and ran all the upgrade steps like usual. Rebooted server, and tested. Now voicemail does not work at all. Any ideas?
 
I've been there many times. Once, I was down for a month after updates. Lost two large clients. Then I decided to fork the project, fixed all bugs, and improved it. Ever since then, we have had zero issues. We open-sourced it too - FS PBX (www.fspbx.com)
 
  • Love
  • Like
Reactions: ja133 and kenn10
@UCtech, if you called the FusionPBX support number, I would help you with this for free. I helped someone earlier today with transcription, and it worked fine.

We have many companies on 5.4, and voicemail is working for the companies we support. Did you run upgrade -> schema -> data types? Did you upgrade to Master branch and then switch back to 5.4?

Transcription does require adding the ffmpeg dependency.

apt install ffmpeg
Click to expand...

FusionPBX support number is available here.
- https://www.fusionpbx.com/support

FusionPBX isn't static; many of the complaints brought up by the previous response on this forum have been fixed. Many bug fixes, efficiency, and speed improvements.
 
Last edited:
  • Like
Reactions: krooney
pbxgeek said:
I've been there many times. Once, I was down for a month after updates. Lost two large clients. Then I decided to fork the project, fixed all bugs, and improved it. Ever since then, we have had zero issues. We open-sourced it too - FS PBX (www.fspbx.com)
Click to expand...

It is pretty well known there is no such thing as bug free code. Maybe your solution is better -- I may have a look some time, but the support and effort Mark has put in make me want to stay in the FusionPBX camp for now. The fact that Mark allows you to post poach messages like this says a lot about who he is too. I probably wouldn't have if I were in his shoes!
 
  • Like
Reactions: AnthonyDC
UCtech said:
It is pretty well known there is no such thing as bug free code. Maybe your solution is better -- I may have a look some time, but the support and effort Mark has put in make me want to stay in the FusionPBX camp for now. The fact that Mark allows you to post poach messages like this says a lot about who he is too. I probably wouldn't have if I were in his shoes!
Click to expand...
Mark doesn't own this forum. Otherwise, he wouldn't.

Totally understand the “stick with what you know” approach. For what it’s worth, FS PBX isn’t meant to be a dig at FusionPBX — it came out of real operational needs on our side. Years ago we were hitting limitations and spending too much time working around issues, so we made the decision to invest heavily in improving reliability, usability, and adding features we needed for our customers.
 
@UCtech This is a third-party forum. Please call tomorrow (Wednesday) so I can help you if you are available. I will help solve whatever problem you are having, and then I'll give a tour of some of the recent improvements.
 
@UCtech I have to jump in and side with @pbxgeek on this.

Mark and the Fusion team really are great people, and they’ve always been solid to work with. This isn’t a knock on them personally at all. But from an operational standpoint, we hit a point where we had to try something else because upgrades kept turning into “upgrade + cleanup project.” We ended up tinkering with FS PBX and then later moving it to production so that our historical upgrade complications were significantly suppressed.

For us it wasn’t just the occasional hiccup, it was the pattern- apply an update, then spend time chasing down regressions, fixing edge cases, revalidating things that should’ve been routine, and generally babysitting the platform back to a stable state. That created a big hesitation internally. We went from being legitimately nervous (and yes, scared as hell) to run updates, to finally being in a place where updates are just updates. No dread, no weekend fire drills, no “what broke this time” rundown

That shift matters. When you’re running this in production and supporting customers, the difference between “updates are routine” and “updates are risky” is massive. It affects staffing, response time, confidence, and the overall customer experience at the end of the day

So yeah, all respect to Mark/Fusion, but I completely understand why someone would look into FS PBX, as we did, if the post upgrade cleanup becomes the norm rather than the exception.
 
Last edited:
  • Like
Reactions: pbxgeek and kenn10
Looks like the issue is resolved. Appears to have had something to do with the default value for the "Voicemail File" setting for each extension. For transcription to work it must be set as "Audio File Attachment". Updating to the latest code released 12/31 resolved the issue for me.

Many thanks to Mark and the dev team.
 
@UCtech it was nice to talk with you and work with you.

Summary
The voicemail box was set to send a link only. This broke the transcription we changed it to send an attachment. Adding a new voicemail box defaults to attachment and has done so for sometime. However, an older system, when upgraded did need a small adjustment. Upgrading to the latest 5.4, master branch will fix that issue permanently.
 
I wish we could run updates without fear. Maybe it's difficult... maybe it's not possible... but it seems the testing platform is not adequate to verify updates. For this reason, I don't perform updates on my own. I always use support staff to run the updates, then fix the issues. Not once has an update gone without the need to fix something later.

FusionPBX is still the most effective solution for me to use; therefore, I work within the confines of the ecosystem. Hopefully, the project will reach a point where updates can be performed without the fear and post-update rabbit hole.
 
We are making progress on FusionPBX and succeeding in making it more robust.
- Our development team is more knowledgeable than ever
- We are using better development tools than we have ever had
- We have more resources to improve things than we have ever had
- FusionPBX benefits
- Broader support for more phone vendors than likely any other system.
- We have been around long enough to gain experience on many systems.
- FusionPBX maintains fewer dependencies than our competition. Less things that can fail.
- Our software is flexible and provides many options
- A customizable dashboard
- We are improving faster than our competitors know or would want to admit
- Security
- Has been tested by many security professionals
- Has been tested by many hackers
- We have learned security from both professionals and hackers
- We have real-world experience
- FusionPBX uses one framework instead of 2 frameworks.
- Our competitors have mentioned some of our weaknesses.
- We fixed many of them already
- The ones that been fixed or improved will be fixed soon.
 
Last edited:
volkswagner said:
I wish we could run updates without fear. Maybe it's difficult... maybe it's not possible... but it seems the testing platform is not adequate to verify updates. For this reason, I don't perform updates on my own. I always use support staff to run the updates, then fix the issues. Not once has an update gone without the need to fix something later.
Click to expand...
You basically just validated what I wrote. I can't recall having to coordinate with my vendors every time I need to upgrade their software. Imagine having to call Apple every time you need to update your iPhone? Do I have to take my Tesla to the service center every time I need to upgrade that software?
 
You must log in or register to reply here.
Top Bottom