TIPS Incredible PBX 2027 - MOH errors

Code:
MariaDB [asterisk]> select * from music;
+----+-------------+--------+--------+-------------------------------------------------------------------------------------------------------------+--------+
| id | category    | type   | random | application                                                                                                 | format |
+----+-------------+--------+--------+-------------------------------------------------------------------------------------------------------------+--------+
|  1 | default     | files  |      1 |                                                                                                             |        |
|  4 | Queues      | files  |      0 |                                                                                                             |        |
|  5 | Park        | files  |      0 |                                                                                                             |        |
|  6 | RecordStart | files  |      1 |                                                                                                             |        |
|  7 | RecordStop  | files  |      1 |                                                                                                             |        |
|  8 | Christmas   | files  |      1 |                                                                                                             |        |
|  9 | stream      | custom |      1 | /usr/bin/mpg123 -q -r 8000 -f 8192 -b 1024 --mono -s http://stream.live.vc.bbcmedia.co.uk/bbc_world_service | NULL   |
+----+-------------+--------+--------+-------------------------------------------------------------------------------------------------------------+--------+
7 rows in set (0.001 sec)
 
@wardmundy : I didn't mention before, but that was one of the first things I tried, namely going back to older music modules which I downloaded from freepbx's repositories. As you said, they load fine but the same problems continue to show up.
I actually went crazy mixing and matching many modules, including core, framework and you name it, until I got completely lost and had to blow up the instance as it became unmanageable.
You know it's not the end of the world. For what my business needs freepbx 15 is good enough and we will stick to it until there is a better outcome some day.
 
More issues: If you try to change any of the MOH settings like change one of your music types for random, it aborts. @Halea see if you see that too.

If I delete the streaming entry in the MOH screens, normal MOH changes can be made.
 
My guess is they've written this module for their proprietary FreePBX platform which probably uses a very old version of MySQL since they're still on CentOS 7.
 
More issues: If you try to change any of the MOH settings like change one of your music types for random, it aborts. @Halea see if you see that too.

If I delete the streaming entry in the MOH screens, normal MOH changes can be made.
We are a streaming Internet Radio Station. We use the MOH function for cueing and standard "on hold". It has always worked for our needs and after upgrading lost this feature.
 
@wardmundy using the old module gives the same error in FreePBX-16. I took a string for the mpg123 player and manually inserted it into the database with both the old and new module with the same results. It will play but my version of the stream is distorted and sounds more like white noise but it does play and I may have incorrect parameters.

I used: /usr/bin/mpg123 -q -r 8000 -f 8192 -b 1024 --mono -s http://stream.live.vc.bbcmedia.co.uk/bbc_world_service but may have incorrect parameters.

Either module absolutely gives the same error if you try to add a stream. Manually adding the stream name to the MOH screen first and then manually inputting the stream into the database works.
Hello.. Mind sharing how to manually add the stream URL to the database? Thanks!
 
IF you are running FreePBX-16 and IncrediblePBX-2027, it won't work.
 
We are running IncrediblePBX-2007! Thanks for the reply.
If MOH with live streaming is vital (like for us) you might want to switch to IncrediblePBX-2021 on the Debian 10 platform.

Although it's an older version I think it has many years of life still left in it. I find it to be fully functional (although I don't use the built in faxing and sms features) and very robust on every platform we use.

We use Debian 10.x or Ubuntu 20.04-LTS on branded/unbranded desktop PCs and top name or generic servers. As well as Proxmox v7.4 and 6.4, or still pure KVM.
Linux based Virtualbox v6.1.44 also works very well although we don't use Virtualbox 7.x which has issues - at least in our use conditions.
 
If MOH with live streaming is vital (like for us) you might want to switch to IncrediblePBX-2021 on the Debian 10 platform.

Although it's an older version I think it has many years of life still left in it. I find it to be fully functional (although I don't use the built in faxing and sms features) and very robust on every platform we use.

We use Debian 10.x or Ubuntu 20.04-LTS on branded/unbranded desktop PCs and top name or generic servers. As well as Proxmox v7.4 and 6.4, or still pure KVM.
Linux based Virtualbox v6.1.44 also works very well although we don't use Virtualbox 7.x which has issues - at least in our use conditions.
Thanks.. we will try it! Best wishes
 
We switched over to FreePBX 16 and it works fine.
@Wonecue : Thnk you. I've just installed stock FreePBX 16 from Sangoma and MOH works indeed!

Actually, I haven't done much testing yet. I have a system up and running as a proxmox VM and I was able to create a couple of MOH streams without hitting that SQL database error. So, I am assuming that the streams actually work.

@wardmundy : any thoughts about where to look at to get this thing fixed in incrediblepbx 2027?
 
My guess is they've written this module for their proprietary FreePBX platform which probably uses a very old version of MySQL since they're still on CentOS 7.
FreePBX has been using MariaDB since FreePBX v14. I still have access to a FreePBX v14 distro box that hasn't been touched/updated since 2020, it runs MariaDB 5.5. I also couldn't replicate any MoH issues using the examples posted in this thread.

I have a FreePBX v15 distro box, runs MariaDB 5.5.x and as well, could not replicate any issues with MoH when adding the stream applications. The same with the FreePBX v16 distro boxes I have out there, running MariaDB and can't replicate.

That being said I was able to replicate this on a FreePBX v16 system I built on Debian 12 which is running MariaDB 10.11.x and that is where I run into the issues because any version of MySQL/MariaDB greater than 5.x has much harsher and stricter policies out of the box.

So this is a bug in FreePBX but only if you are using strict MySQL/MariaDB policies of any version greater than 5.x and since there's no issue tracker, I opened a thread on the forum.
 
@Wonecue : Thnk you. I've just installed stock FreePBX 16 from Sangoma and MOH works indeed!

Actually, I haven't done much testing yet. I have a system up and running as a proxmox VM and I was able to create a couple of MOH streams without hitting that SQL database error. So, I am assuming that the streams actually work.

@wardmundy : any thoughts about where to look at to get this thing fixed in incrediblepbx 2027?
Probably have to edit installer and start over... or get Sangoma to FIX THEIR BUG. Tips are below:

 
Last edited:
Probably have to edit installer and start over... or get Sangoma to FIX THEIR BUG. Tips are below:

You could just adjust the MariaDB policies in 10.11.x to match 5.5.x to avoid having to install 5.5.x
 

Members online

Forum statistics

Threads
26,687
Messages
174,410
Members
20,257
Latest member
Dempan
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top