Queue with mp3 stream started twice

All,

I have just created a PBX with Asterisk 22 en FreePBX 17. I configured it by applying a backup of Raspbx. I got it all working, but there is one thing I don’t understand.

I have two music on Hold applications, both to mp3 stream (e.g. http://stream.bnr.nl/bnr_mp3_128_20) I also created two queues, and set Music On Hold to the appropriate application.

It works as a charme, but … if I issue “sudo systemctl status freepbx” I see that both applications are started twice. I don’t understand why that is?

Can anybody shine a light on this?

pi@raspbx:/etc/asterisk $ sudo systemctl status freepbx
● freepbx.service - FreePBX VoIP Server
     Loaded: loaded (/etc/systemd/system/freepbx.service; enabled; preset: enabled)
     Active: active (exited) since Tue 2025-05-20 21:00:59 CEST; 3min 1s ago
    Process: 722 ExecStart=/usr/sbin/fwconsole start -q (code=exited, status=0/SUCCESS)
   Main PID: 722 (code=exited, status=0/SUCCESS)
      Tasks: 112 (limit: 819)
        CPU: 1min 53.880s
     CGroup: /system.slice/freepbx.service
             ├─1324 /bin/sh /usr/sbin/safe_asterisk -U asterisk -G asterisk
             ├─1326 /usr/sbin/asterisk -f -U asterisk -G asterisk -vvvg -c
             ├─1442 /usr/bin/mpg123 -q -r 8000 -f 8192 -b 1024 --mono -s http://stream.bnr.nl/bnr_mp3_128_20
             ├─1446 /usr/bin/mpg123 -q -r 8000 -f 8192 -b 1024 --mono -s http://22333.live.streamtheworld.com/TLPSTR20.mp3
             ├─1449 /usr/bin/mpg123 -q -r 8000 -f 8192 -b 1024 --mono -s http://22333.live.streamtheworld.com/TLPSTR20.mp3
             ├─1450 /usr/bin/mpg123 -q -r 8000 -f 8192 -b 1024 --mono -s http://stream.bnr.nl/bnr_mp3_128_20
             ├─1517 "PM2 v5.2.2: God Daemon (/home/asterisk/.pm2)"
             ├─1590 php /var/www/html/admin/modules/core/call-transfer-events.php
             ├─1740 "node /var/www/html/admin/modules/core/node/fastagi-server.js"
             └─1845 "node /var/www/html/admin/modules/ucp/node/index.js"

May 20 21:00:49 raspbx runuser[1834]: pam_unix(runuser:session): session closed for user asterisk
May 20 21:00:49 raspbx runuser[1852]: pam_unix(runuser:session): session opened for user asterisk(uid=1001) by (uid=0)
May 20 21:00:51 raspbx runuser[1852]: pam_unix(runuser:session): session closed for user asterisk
May 20 21:00:51 raspbx runuser[1873]: pam_unix(runuser:session): session opened for user asterisk(uid=1001) by (uid=0)
May 20 21:00:54 raspbx runuser[1873]: pam_unix(runuser:session): session closed for user asterisk
May 20 21:00:54 raspbx runuser[1890]: pam_unix(runuser:session): session opened for user asterisk(uid=1001) by (uid=0)
May 20 21:00:56 raspbx runuser[1890]: pam_unix(runuser:session): session closed for user asterisk
May 20 21:00:57 raspbx runuser[1901]: pam_unix(runuser:session): session opened for user asterisk(uid=1001) by (uid=0)
May 20 21:00:59 raspbx runuser[1901]: pam_unix(runuser:session): session closed for user asterisk
May 20 21:00:59 raspbx systemd[1]: Finished freepbx.service - FreePBX VoIP Server.
pi@raspbx:/etc/asterisk $

You have to dig why that mpq123 has duplicated? I do have MoH with live radio on Asterisk (Vanilla) and i don’t see same / similer issue on my side.

● asterisk.service - LSB: Asterisk PBX
     Loaded: loaded (/etc/init.d/asterisk; generated)
     Active: active (running) since Wed 2025-05-14 16:00:52 UTC; 6 days ago
       Docs: man:systemd-sysv-generator(8)
    Process: 951 ExecStart=/etc/init.d/asterisk start (code=exited, status=0/SUCCESS)
      Tasks: 99 (limit: 9389)
     Memory: 212.5M
        CPU: 2h 11min 33.483s
     CGroup: /system.slice/asterisk.service
             ├─1081 /usr/sbin/asterisk -U asterisk -G asterisk
             ├─1303 /bin/bash /etc/asterisk/moh/live_music_stream.sh
             └─1307 /usr/bin/ffmpeg -i http://as-hls-ww-live.akamaized.net/pool_74208725/live/ww/bbc_radio_two/bbc_radio_two.isml/bbc_radio_two-audio%3d96000.norewind.m3u8 -vn -ar 8000 -ac 1 -f s16le -

Also what is the printout for ps command?

ps -aux | grep mpg123

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.